Claim Preparation, Compliance Audit, and EHR Documentation

Claim Preparation, Compliance Audit, and EHR Documentation

This lab brings together every skill you have built in this program. You will enter real coded data into practice management software, generate clean electronic claims, and then audit your own work using the same compliance framework that professional billing departments and federal investigators use. Accuracy here is not optional — errors on claims affect patient care, practice revenue, and your professional reputation.

Preparing the CMS-1500 and UB-04 Claim Forms

The CMS-1500 is the standard paper claim form used by non-institutional providers such as physician offices. The UB-04 (also called the CMS-1450) is used by institutional providers such as hospitals and outpatient facilities. Although most claims travel electronically as HIPAA-mandated transaction sets (the 837P for professional claims and the 837I for institutional claims), the printed forms remain the visual reference that coders and billers use to verify data entry.

When entering claims into the practice management software, work through the form fields in a logical order: patient demographics first, then insurance information, then the provider data, and finally the coded encounter data (diagnoses, procedure codes, modifiers, units, place of service, and dates). Every field that a payer requires must be populated exactly as it appears in the source documentation. A mismatch between the patient's name on the claim and the name on file with the payer is enough to trigger a rejection.

After data entry, run the software's built-in claim scrubber. A claim scrubber is an automated rule engine that checks for common errors before the claim leaves your system — things such as missing required fields, diagnosis codes that do not support the procedure billed (medical necessity edits), invalid code combinations, and modifier conflicts. Read every edit flag carefully. An edit is not always an error; sometimes the software flags a situation that is actually correct, and you must understand the rule well enough to know whether to correct the claim or document why it stands. Do not simply click through edits without reading them. Resolve or document every flag before you print the final clean claim.

Applying the Compliance Audit Tool

Compliance auditing is the process of reviewing completed claims against established rules to find billing errors before — or after — a payer or government investigator does. The Office of Inspector General (OIG) of the U.S. Department of Health and Human Services publishes an annual Work Plan that lists the billing practices it intends to review. Familiarity with the OIG Work Plan tells you where scrutiny is highest.

Your audit checklist for this lab covers five key areas:

Medical necessity — Does the diagnosis code documented in the medical record support the procedure billed? Payers, including Medicare, will only reimburse services that are medically necessary. Local Coverage Determinations (LCDs) published by Medicare Administrative Contractors define which diagnoses support specific procedures.

Correct modifier use — Modifiers change the meaning of a CPT or HCPCS code. An incorrect modifier can constitute upcoding (billing for a higher level of service than provided) or can create a false claim.

Unbundling — Billing separately for services that CPT or the National Correct Coding Initiative (NCCI) requires to be billed together is called unbundling. It artificially inflates reimbursement and is a compliance risk.

Upcoding indicators — Review E/M levels, surgical codes, and add-on codes to confirm that the code selected matches the documentation, not a higher-paying alternative.

HIPAA minimum-necessary standard — Any patient information included in billing and coding work must be limited to what is needed to accomplish the billing purpose. Do not request, use, or disclose more protected health information than necessary.

For each finding, assign a risk level using OIG audit methodology language: low (unlikely to result in overpayment or regulatory action), moderate (pattern or repeated occurrence that could attract attention), or high (clear overpayment, false claim potential, or HIPAA violation). Risk level drives urgency of corrective action.

Writing the Compliance Summary

The compliance summary is a professional document. Organize it clearly: list each finding, identify the applicable authority (for example, HIPAA Privacy Rule, a CMS transmittal, an AMA CPT guideline, or a payer policy), state the risk level, and describe the corrective action taken or recommended. Be specific but general enough where exact regulatory citation numbers are beyond your current reference — it is better to write "per CMS medical necessity policy" than to invent a specific rule number.

Close the document with a personal compliance statement — a short paragraph affirming your ethical commitment to honest, accurate billing. This reflects the professional standards expected by both AAPC and AHIMA and is a real component of many compliance programs in the field.

Patient Safety and Scope of Practice

Accurate coding and billing directly affect patient safety. Upcoding or falsifying diagnoses can alter a patient's permanent health record, affect future insurance coverage, and distort clinical data used for public health decisions. Never alter documentation to support a code — code only what is documented. If documentation is insufficient, query the provider through the appropriate channel; do not guess or assume. Maintain strict confidentiality of all patient data used in this lab, even in a training environment. Treat every practice record as you would a real patient's information.