Documentation Support and Code Validation
Key Takeaways
- Every reported code must be supported by provider documentation and applicable coding guidelines.
- Provider-selected, encoder-selected, and CAC-suggested codes still require coder validation.
- Discrepancies should be researched through the record, guidelines, and facility policy before a code is changed.
- When documentation is unclear or conflicting, a compliant query is safer than guessing.
What Documentation Support Means
A code is compliant only when the health record supports it. For CCA exam purposes, support means the diagnosis, procedure, service, modifier, sequencing, or charge can be traced to provider documentation, official coding guidance, payer rule when applicable, and facility policy.
Do not treat a diagnosis list, order, charge, problem list, encoder result, or computer-assisted coding suggestion as final by itself. These tools may point the coder toward a possible code, but the coder must validate the clinical facts and coding rule before reporting it.
Validation Workflow
- Confirm the patient encounter and setting.
- Read the relevant report, note, order, result, or operative documentation.
- Compare the assigned code to the documented condition, service, procedure, laterality, timing, and status.
- Check sequencing, modifier, and medical necessity implications.
- Resolve missing, conflicting, vague, or inconsistent documentation through the approved query or escalation process.
A common exam trap is a code that is clinically plausible but not documented. Another trap is a code that appears in an electronic system because it was copied from a prior encounter. The compliant answer is to use the current encounter documentation.
Discrepancy Examples
| Finding | Concern | Safer action |
|---|---|---|
| CAC assigns acute respiratory failure, but provider documents only shortness of breath | No provider diagnosis | Review and query only if indicators support clarification |
| Fee ticket lists a higher E/M than the note supports | Charge mismatch | Validate E/M criteria and follow correction workflow |
| Op report documents biopsy, but code selected is excision | Procedure overstated | Code from op report or query if unclear |
| Provider notes conflict | Data may be inaccurate | Clarify through query or policy |
CCA scenarios usually reward the answer that protects data integrity. The coder should not maximize reimbursement, copy a provider choice without review, or code only from memory. A defensible code has a clear trail back to documentation and guidelines.
A CAC tool assigns a code for acute kidney failure. The provider documentation states elevated creatinine and dehydration, but does not diagnose acute kidney failure. What should the coder do first?
A provider selects a procedure code on a fee ticket, but the note describes a less extensive service. Which action best supports compliance?
Which record element is usually the strongest support for coding the extent of a surgical procedure?