Medical Coding Audits: What They Find and When You Need One
Your claims are going out. Some are getting paid. That still leaves an important question: do the codes accurately represent the services documented in the record?
A medical coding audit reviews selected encounters and compares the reported codes with the documentation and the rules that apply to that service, payer, and date. It can identify errors, documentation gaps, and questions that need closer review. Its value depends on a clear scope and what your practice does with the findings.
Start with the question you need answered
An audit may focus on a provider, a service family, recurring denials, or a documentation concern. A broad request to “check our coding” can leave everyone with a different idea of the assignment.
Define the date range, payer mix, types of encounters, and reason for selecting the sample. A targeted review of denied claims answers a different question from a sample designed to assess routine coding. Record those choices so nobody mistakes a narrow finding for a conclusion about the entire practice.
Compare the claim with the record
The review follows the encounter from documentation to the codes submitted. Does the record support the diagnosis reported? Does the service code reflect what was documented? Were units, modifiers, and code combinations appropriate under the applicable rules?
For evaluation and management services, a reviewer may examine whether the documented information supports the selected level under the rules for that encounter. A code should not be selected simply because it is the practice’s usual choice.
Medicare’s National Correct Coding Initiative includes edits addressing certain code combinations and units. Those edits are one part of a coding review. They do not replace the underlying documentation, coverage requirements, or the need to check the relevant payer’s policies.
A paid claim is not the end of the review
Payment tells you how the payer processed a claim; it does not resolve every question about the accuracy of the coding or the supporting record. Likewise, a denial is a starting point for investigation, not proof that the code was wrong.
Some issues begin in documentation. Others involve code selection, a payer rule, or a workflow that carries an earlier mistake forward. A useful report separates those possibilities and states what additional information is needed.
When a focused review makes sense
Consider a coding review when the same denials keep returning, a provider or service has changed, staff are giving conflicting answers about a rule, or an insurer has requested records. Reviews can also support routine internal monitoring and staff education.
The HHS Office of Inspector General includes internal monitoring and auditing, training, and corrective action among the components of a physician compliance program. An audit is most useful when its findings connect to a process for addressing the issues.
Ask for findings you can use
Before a review begins, agree on the deliverables. Useful findings identify the issue, the supporting record, the applicable reference, and the recommended next step. They distinguish confirmed errors from questions still needing clarification.
If the sample is limited, the report should say so. A finding in selected encounters cannot automatically be extrapolated across all claims. Avoid turning an estimate into a promise of collections or assuming that every change increases reimbursement.
Then give someone responsibility for the next action: provider clarification, staff education, a workflow change, or further review. Set a follow-up point to see whether the same issue appears again.
Get help with the specific coding question
I’m Bambie Cleveland, a medical billing and audit consultant based in Joplin. I help practices examine coding, documentation, and payer questions and give their teams practical guidance. Start by telling me which services or claims are causing concern, without sending patient information through the public contact form.
Comments