10.4 Coding Audits, Monitoring, and Corrective Action
Key Takeaways
- Coding audits are a named revenue integrity activity in AHIMA's current RHIA Domain 4.
- Audit design should define scope, criteria, sample method, reviewer qualifications, dispute process, and corrective action.
- Audit results should be trended by error type, coder, provider, service line, payer, and financial or quality impact when appropriate.
- Corrective action may include education, policy revision, system edits, CDI changes, rebilling, refund review, or compliance escalation.
Audits That Improve the System
The current AHIMA RHIA Domain 4 includes coding audits as part of revenue integrity. A coding audit is not useful merely because charts were reviewed. It is useful when it answers a defined question, uses consistent criteria, reports findings clearly, and leads to corrective action that reduces future error.
Audit design starts with purpose. Leadership may need a baseline accuracy rate, validation after coder education, monitoring for a new service, review after a payer denial pattern, or assessment of a high-risk code family. The purpose influences the sample. Random samples estimate overall performance. Targeted samples find risk in a specific area. Both can be legitimate, but they should not be interpreted the same way.
| Audit design choice | RHIA question | Why it matters |
|---|---|---|
| Scope | Which setting, code type, service line, payer, or date range is included? | Prevents unclear conclusions |
| Criteria | Which official guidelines, policies, and payer rules apply? | Keeps review evidence-based |
| Sample method | Random, targeted, probe, retrospective, or prebill? | Shapes how findings can be generalized |
| Reviewer process | Who reviews, and how are disagreements resolved? | Supports consistency and fairness |
| Reporting | What error types, root causes, and impacts are tracked? | Turns findings into action |
| Follow-up | What education, correction, or escalation is required? | Closes the loop |
RHIA candidates should pay attention to corrective action. A coding error may require coder education, but not always. If the record lacks specificity, provider education or CDI query workflow may be needed. If a system edit is wrong, information technology and revenue integrity may need to update logic. If a payer policy changed, billing and coding may need a new work instruction. If unsupported billing has already occurred, compliance may need to review correction and refund obligations under organizational policy.
Audits also require a communication plan. Results should be shared with enough detail to improve performance, but not in a way that shames staff or encourages defensive behavior. Individual feedback may be appropriate for coder coaching. Aggregated trends may be appropriate for provider education or committee reporting. Compliance-sensitive findings should follow approved channels.
A practical audit follow-up cycle includes:
- Validate the finding and resolve disagreements.
- Classify the root cause: documentation, coding, query, system, charge, payer, or education.
- Correct affected accounts when policy requires.
- Educate the responsible group.
- Update policy, edits, templates, or workflows if needed.
- Reaudit to determine whether the error rate improved.
For the exam, avoid answers that stop at measuring accuracy. Measurement without corrective action does not improve revenue integrity. Also avoid answers that make payment the only audit outcome. Coding audits protect claims, quality data, compliance posture, provider education, and organizational decision making.
The best RHIA answer is disciplined and traceable: define the audit, apply official criteria, trend the findings, fix the accounts when appropriate, address the cause, and monitor again.
Which audit design element is most important for making coding findings defensible?
An audit finds repeated errors caused by missing provider specificity rather than coder misunderstanding. What corrective action fits best?
Why should audit results be trended by error type and root cause?