7.6 Record Review Prioritization and Deficiency Escalation

Prioritize by coding risk

Record review is a time-management problem as much as a knowledge problem. The CCS exam gives limited time, and real coding operations have productivity expectations. The solution is not superficial review; it is risk-based review. Focus first on documents and conditions that determine principal or first-listed diagnosis, major procedures, sequencing, POA status, complications, modifiers, medical necessity, and high-impact secondary diagnoses.

Start with the record type. Inpatient accounts usually require a discharge summary, history and physical, progress notes, consults, operative reports, pathology, orders, medication records, nursing documentation, labs, imaging, and discharge disposition review. Outpatient surgery requires orders, consent context when relevant, operative or procedure note, pathology, anesthesia, implants, laterality, approach, and payer edit awareness.

Emergency department records require chief complaint, provider assessment, diagnostic results, treatments, final diagnosis, disposition, and whether the encounter is diagnostic, therapeutic, screening, or aftercare related.

Prioritization should not mean ignoring lower-dollar issues. A wrong modifier, missed NCCI edit, unsupported medical necessity diagnosis, or incorrect first-listed diagnosis can create denials even when the claim is not high dollar. The priority lens asks where documentation uncertainty is most likely to change code assignment or compliance. If an issue does not affect coding, billing, reporting, or record completeness, it may be provider education rather than an urgent query.

High-yield review order

1. Identify encounter setting, payer context, and applicable code sets.
2. Determine principal or first-listed diagnosis based on the full record and setting rules.
3. Review major procedures and procedure details before finalizing sequencing.
4. Scan for high-impact secondary diagnoses, complications, POA uncertainty, and quality-sensitive conditions.
5. Check clinical indicators when a documented high-impact diagnosis seems weak or a likely diagnosis is undocumented.
6. Review edits, medical necessity, modifiers, and payer-specific guidance.
7. Escalate only the gaps that block accurate coding, billing, reporting, or record integrity.

Deficiency escalation should be specific. A weak escalation says documentation unclear. A strong escalation says the operative report documents debridement of the right heel ulcer but does not state excisional versus nonexcisional method or depth, and this blocks accurate procedure code assignment. The second version tells the provider what is missing, why it matters, and how to respond without suggesting the answer.

Different deficiencies go to different channels. Missing signature, late authentication, incomplete operative report, or missing discharge summary may go through health information management deficiency processes. Diagnosis ambiguity may go through CDI or coding query workflow. Unsupported clinical validity may go through physician advisor review. Repeated provider patterns may go through education. Potential compliance concerns may go to coding leadership, compliance, or audit depending on policy.

Escalation routing table

The timing of escalation matters. Concurrent CDI review can clarify documentation before discharge, while the provider still remembers the case and the patient is still under care. Retrospective coding queries may still be appropriate, but they should be tightly written and based on the final record. Late queries should not be used to rewrite the case for convenience. They should clarify genuine uncertainty or missing detail.

A good reviewer also knows when to stop. If the final documentation supports a valid code at lower specificity and no compliant query opportunity exists, finalize the supported code. If the provider responds unable to determine, code what remains supported. If a query goes unanswered after policy-defined follow-up, use facility procedures for unresolved accounts. Do not hold records indefinitely because a more desirable answer might appear.

Exam traps often involve over-escalation or under-escalation. Over-escalation occurs when the coder queries for every abnormal lab even when no codeable diagnosis is at issue. Under-escalation occurs when the coder ignores a conflict that changes principal diagnosis, POA status, or complication reporting. The best answer usually names the blocked coding decision, performs full record review, and escalates through the proper channel.

Risk-based review also supports audit defense. When an external reviewer asks why a diagnosis was coded, the organization should be able to show provider documentation, clinical support when needed, query history if applicable, and coding guideline rationale. When a diagnosis was not coded, the organization should be able to show that it lacked provider support, did not meet reporting criteria, was ruled out, or was otherwise not codeable in that setting. Both decisions require evidence.