DRG Impact without Upcoding
Key Takeaways
- DRG assignment is affected by principal diagnosis, secondary diagnoses, procedures, POA status, discharge disposition, and patient factors.
- A coder may validate DRG impact but may not add unsupported diagnoses or procedures to increase payment.
- CC and MCC capture must be based on provider documentation and UHDDS criteria.
- Queries should clarify clinically supported ambiguity, not lead the provider to a higher-paying answer.
DRG-Aware, Not DRG-Driven
MS-DRG grouping uses coded data to classify inpatient stays. The principal diagnosis usually places the case in a major diagnostic category. Significant procedures can move the stay to a surgical DRG. Secondary diagnoses may act as CCs or MCCs when they are documented, reportable, and not excluded by grouping logic.
Coders should understand DRG impact because it helps validate the final claim. A missed principal procedure, unsupported principal diagnosis, incorrect POA indicator, or omitted reportable complication can change reimbursement, quality data, and audit risk. Validation is part of accurate coding.
DRG awareness becomes upcoding when the coder selects codes because they raise payment rather than because documentation and guidelines support them. Do not code abnormal labs as diagnoses, choose a more severe condition without provider documentation, or sequence a diagnosis as principal solely because it groups higher.
A compliant query is appropriate when clinical indicators support ambiguity. For example, if respiratory notes, oxygen needs, ABGs, and treatment raise a documented uncertainty between hypoxia and acute respiratory failure, a neutral query can ask the provider to clarify the diagnosis. The query must offer clinically reasonable options and allow other or unable to determine.
POA status can affect payment and quality outcomes. A complication that develops after admission may still be reportable when it meets UHDDS criteria, but it should receive the correct POA indicator. Hiding hospital-acquired conditions or changing POA status for reimbursement is not compliant.
| DRG factor | Compliant coder action |
|---|---|
| Principal diagnosis | Validate after-study admission reason |
| Secondary diagnosis | Confirm provider documentation and UHDDS impact |
| Procedure | Verify PCS code, date, and operative support |
| CC or MCC | Capture only when supported and reportable |
| POA | Assign based on timing and documentation |
| Query | Clarify ambiguity without leading |
A record shows low oxygen saturation, ABG abnormalities, high-flow oxygen, and provider documentation of hypoxia, but acute respiratory failure is not documented. What is the compliant next step if clarification could affect coding?
Which action is an example of upcoding risk?
A postoperative infection develops during an inpatient stay, is documented by the provider, treated with IV antibiotics, and meets reporting criteria. What should the coder do?