Coding Audit Finds a Pattern of Unsupported Secondary Diagnoses
An internal audit of 60 inpatient records from one hospitalist group finds that 14 records (23%) carry a secondary diagnosis of severe malnutrition supported only by a dietitian note written on day 3, with no provider documentation, no clinical indicators in the record, and no treatment beyond a standard diet order. In 9 of the 14, the malnutrition code increased the MS-DRG payment, with an average payment difference of $4,100 per case. The group's lead physician argues that the dietitian is the malnutrition expert and that the note is legitimate clinical documentation. The compliance officer asks the HIM director whether these should be reported as overpayments.
1. Evaluate the coding and documentation compliance question. Is the dietitian's assessment sufficient support for the diagnosis code?
Read the worked answer
No. The code reports a diagnosis made by a provider, and coding rules require that a condition be documented by the provider responsible for the patient's care, supported by clinical evidence in the record, and consistent with the treatment rendered.
A dietitian's note is a valuable clinical assessment and can support the diagnosis when the provider reviews it, agrees, and documents the diagnosis with supporting clinical indicators. Here none of those elements is present: the note stands alone on day 3, no provider documents malnutrition, no clinical indicators (such as weight loss percentage, BMI, or lab values) appear in the record, and the only intervention is a standard diet order, which does not reflect treatment of a severe condition.
Three failures converge:
- Documentation - no provider diagnosis.
- Clinical validation - no supporting indicators.
- Medical necessity/consistency - treatment does not match a severe malnutrition diagnosis.
The physician's argument conflates clinical expertise with documentation authority. The dietitian may be the expert; the provider must still make and document the diagnosis. Coding the condition without that support is unsupported coding regardless of who identified it.
2. Advise the compliance officer on whether the 9 cases with payment impact should be treated as identified overpayments, and describe the analysis needed before any repayment decision.
Read the worked answer
They should be treated as potential overpayments pending case-level review, not automatically as confirmed overpayments. The distinction drives the obligation and the timeline.
Analysis needed for each of the 9 cases:
- Determine whether the DRG change was actually caused by the malnutrition code, or whether another secondary diagnosis would have produced the same DRG. If another valid CC/MCC is present, removing malnutrition may not change payment at all.
- Re-review the full record for provider documentation elsewhere (discharge summary, progress notes, consultant notes) that may support the diagnosis. The audit sample may have missed it.
- Apply the organization's clinical validation criteria consistently, and have a physician advisor or peer reviewer confirm the determination.
- Quantify the actual overpayment per case - the payment difference, not the average.
Once confirmed, identified overpayments generally must be reported and returned within the timeframe set by the applicable payment rules (commonly 60 days from identification for Medicare). The clock starts on identification, so the review should be scoped and time-bound. Legal counsel should be involved before any self-disclosure decision, and the pattern should be assessed for whether it reflects isolated error or a systemic documentation practice requiring broader look-back.
3. Recommend corrective actions that address the root cause rather than the individual cases.
Read the worked answer
The root cause is a workflow in which a dietitian documents a diagnosis that no provider adopts, and coders code it because it is in the record and it pays. Corrective action must close that loop.
Documentation:
- Establish a malnutrition documentation protocol: the dietitian's assessment triggers a provider query or a co-signature requirement, and the provider documents the diagnosis with the clinical criteria used.
- Provide education to the hospitalist group on the clinical indicators required and on why the dietitian note alone is insufficient.
Coding:
- Add a hard-stop or secondary review for malnutrition codes lacking provider documentation and clinical indicators.
- Revise the query process so coders query when support is absent, rather than coding on the dietitian note.
Monitoring:
- Track malnutrition coding frequency by physician and by DRG impact monthly; a spike is a signal.
- Re-audit a sample in 90 days to confirm the rate has fallen.
- Feed findings to the compliance committee and document the corrective action plan.
The measure of success is not the repayment; it is a sustained drop in unsupported malnutrition coding and a documented, repeatable provider-dietitian-coder workflow.