Certification Alone Doesn't Equal Competency (And Your Denial Rate Proves It)

Here's a sentence I hear in almost every HIM leadership conversation I have:

I get why that's confusing. A credential is supposed to be the proof. It's the thing that says "this person knows what they're doing." So when a fully certified coder is still generating avoidable denials, it feels like the system is broken.

It's not broken. It's just measuring the wrong thing.

What a certification actually proves

A CIC, CCS, or CPC exam proves someone can answer questions about coding under test conditions — multiple choice logic, clean vignettes, a defined universe of right answers. That's a real, useful skill. It is not the same skill as opening a real chart.

Real charts are messy. They contradict themselves. The documentation you need is buried on page 14 of an EHR note, notes written by three different providers who never talked to each other say three different things. Passing an exam tells you someone can apply rules to a curated scenario. It tells you nothing about whether they can find the correct codes amongst the inconsistencies of a real chart.

What actually predicts competency

If certification isn't the signal, what is?

Repetition on complete, messy charts — not exam scores.

Every coder I've watched go from shaky to sharp got there the same way: by working real charts, getting real feedback, and doing it again. And again. And again. Not by re-reading guidelines. Not by re-taking practice tests. By repetition.

This is the same reason a new driver with a license still isn't a confident driver until they've actually driven in traffic. The test proves eligibility. The reps build the skill.

If your onboarding process for new hires is "they're certified, so they're ready," you've skipped the step that actually builds the competency you're hiring for. And if you’re passing up experienced coders who lack a certain certification because you believe they don’t have what you need, that’s another layer to the competency issue and denials you’re seeing. Certification is the gold standard, it should never be the only standard.

Reframe your denial rate

Here's the mindset shift I want to leave you with this week:

It's tempting to treat every denial as an individual mistake to correct. Flag the chart, note the error, move on. But when denials cluster around the same document type, the same DRG family, or the same newer hires, that's not noise. That's your training program telling you exactly where the gap is.

This week's Wednesday Validation case — hyponatremia — is a great example of this in action. It's a diagnosis that looks straightforward on paper (a lab value, a clear clinical threshold) but gets missed or under-coded constantly because the documentation supporting it is inconsistent — labeled differently by different providers, buried in progress notes instead of stated as a diagnosis or, in many cases, not a reportable diagnosis because the documentation doesn’t support it. A certified coder who's only seen it in textbook form will miss it in the wild. A coder with experience on real charts won't.

What to do with this

If you're a coding leader reading your team's denial report this week, try this: instead of asking "who made this error," ask "what pattern of chart does our team consistently misread, and have we actually trained on charts that look like that? Or did we just train them on the rules?"

That's the difference between managing individual mistakes and closing a real competency gap.

Want help closing that gap on your team?

If your denial rate has you looking at your training pipeline differently, this is exactly what our team training and corporate onboarding and coaching packages are built for — real chart reps, not just rule review. Set your team up for success so they are building the right instincts from day one instead of after six months of denials.

Reply to this email: contact@reillycodingstrategies.com to talk through what that could look like for your team.