Risk adjustment accuracy and audit exposure usually pull apart. They don't have to.

Ask a risk adjustment leader what keeps them up at night and you will usually get one of two answers. The first is that the population looks healthier on paper than it really is. The second is a risk adjustment audit. Most organizations treat these as a trade-off: push harder on capturing conditions and you raise your audit exposure; play it safe and the risk picture falls short.

Accuracy and audit exposure do usually move in opposite directions. They don't have to. The tension doesn't come from the goal. It comes from the order the work happens in.

What does an incomplete risk picture cost patients?

Chronic conditions have to be documented every calendar year to count. Busy schedules, scattered records, and visits that run short mean some of them never make it into this year's record. Across a population, the gaps add up. The average practice misses eligible risk-adjusting diagnoses every year, so the population looks healthier on paper than it is.

The risk score is meant to summarize how sick a population is. When conditions go undocumented, it understates that, and the resources meant to care for those members shrink with it. Care management capacity, outreach, and the programs the sickest members depend on are sized to a population that looks healthier than the one actually walking into the clinic.

So the pressure to close the gap is real, and it's about patients. The question is how organizations go about closing it.

Why does year-end chart review increase risk adjustment audit exposure?

The familiar approach is retrospective. Late in the year, a team sweeps the records, looks for conditions that were supported somewhere in the chart but never coded, and submits them. It feels responsible. The evidence is in the chart; the team is just making sure it counts.

The trouble is the pattern this creates. A diagnosis added through retroactive chart review, months after the visit, by someone who wasn't in the room, is the kind of documentation that draws federal audit scrutiny. Audit scrutiny isn't aimed at low risk scores. It focuses on whether the diagnoses behind a risk score are supported by the documentation of how care was actually delivered.

Audits don't target low risk scores. They test whether the diagnoses behind a score match how care was delivered.

Picture it from the reviewer's side, as an illustration. A member's record shows a routine visit in the spring, with notes about blood pressure and a medication refill. Months later, a chronic condition from that chart appears on a submission, added by a reviewer who never saw the patient, with little in the visit note to show it was assessed that day. The condition may well be real. But the record tells the story of a chart that was mined, not a patient who was assessed.

That is how accuracy and exposure end up pulling apart. The harder a retrospective program works to close the gap, the more of its captured conditions carry that pattern. A complete risk picture gets bought with a less defensible record.

How does prospective capture change the math?

The alternative is to move the work earlier. Surface the likely condition before the encounter, not months after it, so the clinician can evaluate it with the patient present and document what the clinical evidence supports, where it should be and when it should be.

We have written about why prospective risk adjustment is a timing problem from the clinician's chair. The audit side of the same idea is just as important. When conditions are evaluated and documented at the visit, the risk score reflects the population's true clinical risk because the documentation reflects how care actually happened. That narrows the gap a reviewer would look for.

That's not a coding tactic. It's a sequencing change. The same conditions get captured, with less audit risk. Defensibility is built into the chart instead of bolted on at year-end. And the resources to care for those members are more likely to show up where they're needed.

1. Retrospective sequenceVisit happens. Months pass. A reviewer who wasn't in the room combs the chart, finds a condition that never got coded, and submits it.
2. Prospective sequenceA suspected condition, with its supporting evidence, reaches the clinician before the visit. The clinician confirms or rules it out with the patient in the room. Only what the evidence supports is documented.

Notice that prospective work also rules conditions out. A suspect that doesn't hold up in the exam room never reaches the record. That's part of what makes the result defensible: the aim is an accurate record, not a bigger one.

What changes for the risk adjustment team?

The plans making progress on this aren't getting there through volume, meaning more charts pulled or more reviewers added to the year-end push. They're doing it by changing where their risk adjustment team spends its time. The team gets rebuilt around the medical record and the upcoming visit, not around the year-end chart room.

• Clinical documentation staff prepare upcoming visits instead of reopening finished ones.
• Clinicians see each suspected condition alongside its source evidence, and they make the call.
• Leaders can see where documentation gaps cluster, by provider or by condition, while there's still time in the year to support those clinicians.
• The year-end review shrinks from the main event to a backstop.

It depends on knowing which patients are actually on each clinician's panel, too. Prospective preparation for a member who left months ago is wasted effort, which is why a stale roster undermines risk work along with everything else. And like year-round care gap closure, it treats the whole year as the window rather than the last few months.

That's the approach behind ElevateCare 360's risk adjustment accuracy work: suspected conditions surfaced before each visit, every suggestion linked to its source evidence, and clinicians making the final call with the patient there.