Audit & RADV

The problem list is not documentation

Mike Garrett, CPC, CRC · September 3, 2026

Ask what the most common finding in a coding quality audit is and people guess wrong codes — the wrong diabetes complication, an outdated combination code. Those happen. But the finding we see most often is different: the code is plausible, the condition may well be real, and the documentation behind it is a problem list entry that has been carried forward, unexamined, for years.

How a problem list decays

Problem lists start out honest. A condition gets diagnosed, someone adds it, and for a while the list reflects reality. Then entropy does its work. Resolved conditions never come off. Acute events harden into permanent residents — a pulmonary embolism from 2019 still listed as if it were current. Duplicates accumulate with slightly different wording. A rule-out diagnosis entered during a workup stays after the workup ruled it out.

None of this is negligence. It’s what happens to any list that many people can add to and nobody owns. But it means the problem list, in most EHRs, is a mixture of current conditions, historical conditions, and conditions that were never confirmed at all — with no reliable way to tell which is which.

Why coding from it fails

Risk-adjustment coding requires that a diagnosis be supported by the documentation of a face-to-face encounter — the note has to show the condition was monitored, evaluated, assessed, or treated. This is the standard commonly taught as MEAT, and it’s the lens an auditor applies to a sampled chart.

A problem list entry, by itself, shows none of that. It shows that at some point, someone put the condition on a list.

When a Risk Adjustment Data Validation audit pulls a chart, the question is never “was this condition on the problem list?” It’s “does the medical record for this encounter support this diagnosis?” A code that rests on a carried-forward entry has nothing to stand on — and the fact that the condition is genuinely present doesn’t rescue it, because the record has to show the work, not just the conclusion.

The fix belongs to providers and coders together

For providers, the discipline is bringing real conditions out of the list and into the note. If the diabetes is being managed at this visit, the assessment should say so — its status, what was reviewed, and what the plan is. Two sentences of actual clinical thinking outweigh ten problem-list lines.

Providers can also close the loop the other way: retire what’s resolved, correct what was never confirmed, and date what remains. A problem list that gets pruned is a genuinely useful clinical tool. One that only grows is a liability wearing a clinical costume.

For coders, the discipline is refusing the shortcut. The problem list can prompt a question — is this condition addressed anywhere in the encounter documentation? — but it can’t answer it. If the note doesn’t support the code, the code doesn’t go on the claim, however tempting the list makes it.

An audit finding is rarely about a condition the patient didn’t have. It’s almost always about a record that couldn’t prove what everyone believed was true. That’s the gap worth closing — and it closes one note at a time.