DRG Upcoding: How Severity Coding Inflates Inpatient Claims

How inpatient stays get priced

Most inpatient hospital stays are paid using a Diagnosis-Related Group, or DRG. Instead of paying line by line, the plan pays a single amount for the stay, based on the DRG the claim resolves to and a relative weight that reflects how resource-intensive that group is. Multiply the weight by the plan's contracted base rate and you have the payment.

Many DRG families are split into severity tiers. A condition might map to one DRG on its own, a higher-paying DRG when the patient also has a complication or comorbidity (a CC), and a higher one still when there is a major complication or comorbidity (an MCC). The clinical story is the same admission; the tier, and the payment, depend on which secondary diagnoses are coded alongside it.

Where upcoding enters

Because severity tiers are driven by secondary diagnoses, a single coded condition can move a stay up a tier and change the payment by thousands of dollars. That is the mechanism behind most DRG upcoding. It is usually not dramatic fraud. More often it is a mismatch between what was coded and what the medical record actually supports.

A diagnosis only belongs on the claim if it was clinically relevant to that stay: evaluated, monitored, treated, or affecting the length of stay. A condition that was noted in passing but never worked up does not meet that bar. The Present on Admission (POA) indicator matters here too, since it distinguishes conditions the patient arrived with from those that developed during care, and it affects how some diagnoses may be counted.

A single secondary diagnosis can move an inpatient stay into a higher-paying tier, sometimes by several thousand dollars.

Why automated adjudication clears it

An adjudication engine checks a claim against itself. It confirms the codes are valid, the principal and secondary diagnoses group cleanly, the POA field carries a permitted value, and the totals balance. Every one of those checks can be answered from the electronic claim alone, without ever opening the chart.

The grouper then does exactly what it is designed to do: given a valid qualifying diagnosis, it returns the higher-severity DRG. It holds no opinion on whether the documentation underneath supports that diagnosis. So a stay can pass every automated check and still be coded a tier too high.

What a documentation audit checks

Validating a DRG means reading the record against the codes, which is a slower and more clinical task than an engine performs. An auditor confirms each CC and MCC against the documentation and the coding guidelines, checks the POA assignment, and looks at whether the secondary diagnosis appears where you would expect it if it were real, such as the discharge summary. Then the grouper is re-run on only the codes the chart actually supports.

When a tier is not supported, the useful output is not a risk score. It is a specific determination: the billed DRG, the supported DRG, the diagnosis driving the difference, the change in relative weight, the dollar impact against the plan's fee schedule, and the contract reference. A finding stated that precisely can be rebutted with a chart page or conceded; either way it moves.

What it means for self-funded plans

Inpatient claims are large, so even a small rate of unsupported severity coding adds up across a year. Catching it before payment matters: once a claim is paid, recovery means clawback, which is slower, harder, and tends to strain provider relationships. Reviewing DRG assignment pre-pay keeps the cleanest version of the claim in front of everyone.

This is the kind of review CodaHx runs as part of pre-pay claims auditing, with flags that cite the supported DRG, the driving code, and the contract term rather than a confidence score.