How to Audit Inpatient DRG Coding for Accuracy

Learn how to audit inpatient DRG coding with a focused review of documentation, sequencing, CC/MCCs, discharge status, and audit-ready findings and reports
How to Audit Inpatient DRG Coding for Accuracy

A single diagnosis that is not clinically supported, incorrectly sequenced, or omitted from the final coded record can change an inpatient DRG, alter expected reimbursement, and create an avoidable audit target. To audit inpatient DRG coding effectively, organizations need more than a DRG grouper comparison. They need a disciplined review of the record, the coding logic, and the documentation that supports every payment-driving decision.

For Medicare Severity Diagnosis Related Groups (MS-DRGs), the audit question is not simply whether a higher-weighted DRG was assigned. The question is whether the principal diagnosis, secondary diagnoses, procedures, discharge information, and clinical record support the assigned DRG under the Official Guidelines for Coding and Reporting and applicable payer requirements. That distinction matters when a payer, Recovery Audit Contractor, or internal compliance team reviews the claim months after discharge.

Start an inpatient DRG coding audit with the right scope

An inpatient DRG audit should begin with a defined purpose. A prospective audit before final billing is designed to prevent coding and documentation errors from reaching the claim. A retrospective audit may focus on denial trends, payment variance, compliance exposure, or a suspected pattern involving a service line, provider, or DRG family.

FasterCoder Advertisement

The scope should also identify the payment methodology. MS-DRGs are central to traditional Medicare inpatient prospective payment system claims, but some facilities and payers use other groupers, including APR-DRGs. The core record-review principles overlap, but the grouping logic, severity methodology, and reporting expectations are not interchangeable. Auditors should not apply MS-DRG assumptions to an APR-DRG review without confirming the contract and payer rules.

A useful audit population is risk-based rather than purely random. Cases warranting closer review commonly include one-day stays with high relative weights, cases that moved because of a single CC or MCC, sepsis and respiratory failure admissions, major operating room procedures, transfers, deaths, and claims with diagnoses added after a clinical documentation integrity query. High-volume DRGs with recurring denials also deserve attention, even when each individual payment difference appears modest.

Verify the principal diagnosis before reviewing severity

The principal diagnosis drives the DRG pathway. Under the inpatient coding guidelines, it is the condition established after study to be chiefly responsible for occasioning the admission. That definition does not mean the most resource-intensive condition, the most serious diagnosis listed in the record, or the condition that extended the stay.

Auditors should trace the admission story from the emergency department or direct-admission documentation through the history and physical, diagnostic workup, progress notes, consultant notes, operative report when applicable, and discharge summary. The final code must reflect the provider’s documented diagnosis and the facts established after study.

This is where sequencing errors often begin. A patient may arrive with chest pain, hypotension, altered mental status, or acute kidney injury, but the final principal diagnosis depends on what the record establishes as the reason for admission. When two or more diagnoses potentially meet the definition, the auditor should apply the applicable coding guideline, tabular instruction, and sequencing convention rather than relying on clinical intuition alone.

A query may be appropriate when documentation is conflicting, incomplete, or clinically unclear. It should not be used to steer the provider toward a reimbursable answer. The audit record should distinguish between a valid clarification opportunity and a query that appears leading, unsupported by the clinical indicators, or inconsistent with the organization’s query policy.

Review secondary diagnoses for reportability and support

Secondary diagnoses can materially affect the DRG, particularly when they qualify as a complication or comorbidity (CC) or major complication or comorbidity (MCC). But a diagnosis is not reportable merely because it appears on a problem list or changes the grouper result.

The auditor should confirm that each secondary condition meets reporting requirements: it was present on admission or developed during the stay, was documented by an appropriate provider, and required clinical evaluation, therapeutic treatment, diagnostic workup, increased nursing care or monitoring, or affected the length of stay. Conditions integral to a confirmed diagnosis, historical conditions without current relevance, and ruled-out conditions require careful guideline-based treatment.

Clinical validation is a separate but connected concern. A diagnosis can be coded correctly from a documentation standpoint and still face payer challenge if the clinical record does not substantiate it. This risk is especially visible in sepsis, acute respiratory failure, acute blood loss anemia, encephalopathy, malnutrition, acute kidney injury, and certain heart failure cases. Coding staff should not independently negate a provider diagnosis, but internal audit findings should identify cases where the documentation and clinical indicators leave the claim vulnerable.

Test every CC and MCC that changes the DRG

A practical DRG audit isolates the conditions that affect the assigned DRG. Run the case through the grouper with and without the CC or MCC to determine whether that diagnosis changes the result. Then review that condition with a higher level of scrutiny.

The review should answer several questions: Is the diagnosis clearly documented? Is it coded to the highest supported specificity? Does an Excludes note, code-first instruction, manifestation rule, or combination code change the code selection? Was the condition present on admission accurately reported? Is there evidence of treatment, monitoring, evaluation, or clinical relevance? And does the record support the acuity captured by the code?

This process is not an argument against complete coding. Legitimate CCs and MCCs should be captured consistently because undercoding has its own revenue, quality, and compliance consequences. The goal is defensible specificity, not automatic downcoding. An audit team that only looks for overpayments will miss the operational value of identifying missed reportable conditions and recurring documentation gaps.

Do not treat procedure coding as a secondary check

Procedure coding can determine the surgical versus medical partition, change the base DRG, and affect reimbursement significantly. Auditors should validate ICD-10-PCS code assignment against the operative report and other relevant procedural documentation, including the body part, approach, device, qualifier, and root operation.

Common errors arise when the documented objective of a procedure is misunderstood. Excision, resection, drainage, dilation, insertion, replacement, and bypass have precise PCS definitions. A familiar clinical term does not automatically establish the correct root operation. When multiple procedures occur, the auditor should also confirm whether each code is separately reportable and whether the combination of procedures groups as expected.

The discharge disposition deserves the same attention. Incorrectly reporting transfer status, discharge to home health, or post-acute care can affect payment under transfer policies. Audit staff should compare the claim disposition with the discharge order, case management documentation, and available post-discharge evidence under the facility’s established workflow.

Build findings that operations can act on

A DRG audit has limited value if its findings stop at “code changed” or “DRG changed.” Each finding should identify the original code and DRG, the recommended code and DRG when applicable, the estimated payment impact, the governing rationale, and the supporting or missing documentation. When clinical validation is a concern, state that clearly without converting the coding audit into an unsupported clinical judgment.

Trend reporting should separate coder error, provider documentation gap, query-process issue, system edit failure, and payer-specific policy risk. These categories call for different fixes. A repeated principal diagnosis sequencing problem may require targeted coder education and a second-level review. Frequent unsupported acute respiratory failure cases may require CDI-provider education, clinical criteria alignment, and prebill escalation. Transfer-status errors may point to a registration or case-management handoff problem rather than a coding issue.

Organizations should also measure whether corrective action works. Reaudit a focused sample after education, compare denial rates and DRG shifts over time, and monitor whether the same error returns when staffing changes or annual code updates take effect. A clean audit rate means little if it comes from reviewing only low-risk accounts.

The right inpatient DRG audit protects compliant reimbursement while exposing the documentation and workflow weaknesses that put future claims at risk. Treat each finding as a chance to strengthen the next chart before it becomes a denial, repayment, or external audit issue.

CPC Exam Study Guide
CCA Exam Study Guide
CCS Exam Study Guide
CCS-P Exam Study Guide
CPB Exam Study Guide
Facebook
Twitter
LinkedIn
Pinterest

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.