Risk adjustment's hardest part: finding the condition while the patient is in the room

The hardest part of risk adjustment isn't finding the missed condition. It's finding it while the patient is still in the room.

The first part is the more familiar problem. Suspecting models can look at claims history, medications, and lab results and point to conditions that are probably present but not yet documented this year. What they struggle with is the second part. The suspect arrives, but it arrives late. That is the real argument for prospective risk adjustment: it is not a better way of finding conditions. It is a better moment for finding them.

Why does most suspecting work in reverse?

Picture the usual sequence. A model flags a likely condition: a diabetes complication not yet documented this year, or heart failure suspected from a medication list. The flag lands in a report weeks after the visit where it could have been confirmed or ruled out. The patient has gone home. The clinician has seen a long list of other patients since.

Now the suspect needs another encounter, a chart query, or a fourth-quarter sweep to close. The clinical truth was knowable in March. The documentation waits until October.

Nobody designed it this way on purpose. It falls out of how the work is usually organized. Suspecting often runs as a batch job on data that arrives on a lag. Claims trail the visits they describe. Chart reviews often get scheduled for the fourth quarter, after most visits are over. Each step makes sense on its own. Together they all but ensure the insight reaches the clinician after the one moment they could act on it cleanly.

The condition exists, the signal exists, the encounter happened. The suspect just showed up after the visit was over.

That lag is the Insight Gap in risk adjustment. Here it has an unusually sharp edge, because the moment to act is a single appointment.

What does the lag cost patients and care teams?

Chronic conditions have to be documented every calendar year to count. A diagnosis captured last year counts for nothing this year unless it is addressed again. So a condition that slips past a visit can become a small chase later in the year, and those chases pile up.

For the patient, the cost is quiet but real. A condition worth evaluating was not evaluated when they were sitting in front of their primary care doctor. If it surfaces later, the patient may be asked to come back, or the question gets answered from the chart instead of the exam room. Either way, the care conversation that should have happened did not.

For care teams, the cost shows up as work. Coders and clinical documentation staff can spend the back half of the year sending queries and pulling charts. Clinicians get asked about visits they barely remember. Practice staff try to bring patients back in during the busiest stretch of the calendar. All of it is effort spent reconstructing something that could have been handled once, in the moment.

And across a whole population, conditions that never get documented make patients look healthier on paper than they are. The risk picture understates how sick the panel is, and the resources meant for care management, outreach, and the programs those patients depend on shrink with it. If the roster underneath is also out of date, the problem compounds, as we described in why a stale roster poisons every workflow built on top of it.

Why is retrospective review the riskier path?

There is a second reason the timing matters, beyond patient care. Diagnoses added through retroactive chart review can draw federal audit scrutiny. A diagnosis that rests on a chart pulled months later is harder to defend than a condition a clinician evaluated with the patient present.

That is why the healthiest framing for risk adjustment is accurate, not aggressive. The goal is not to find more conditions. It is to make sure the conditions that are really there get evaluated when they can be evaluated properly, and that the ones that are not there get ruled out. Prospective work serves both halves of that.

What does prospective risk adjustment look like in practice?

Close the loop and the whole exercise changes. The suspect surfaces before the visit, in the workflow the clinician already uses. Here is how a single appointment looks when the timing is right, as an illustration:

1. Before the visitDana, a primary care doctor, opens her morning schedule. For a patient later that morning, a short summary lists conditions worth evaluating this year, each with the evidence behind it: the medication, the lab result, the earlier note.
2. In the roomShe asks the questions and does the exam she would want to do anyway. She confirms one suspected condition and rules out another. Only what the clinical evidence supports goes into the record.
3. After the visitThere is nothing to chase. No query lands in her inbox in October, and the patient is not asked to come back to answer a question that could have been answered today.

The condition gets documented because it is real and the patient is present, not chased down afterward to satisfy a coding queue. Over a year, the risk picture comes to reflect how sick the panel actually is, which is the only number worth having.

Notice what did not change in that scene. The model is the same. The data sources are the same. Dana did not learn a new coding technique. The only thing that moved was when the insight arrived. As we argued in the model was never the bottleneck, the intelligence is usually not wrong. It is late.

What changes in a team's week?

• Clinical documentation staff spend their time preparing upcoming visits instead of reopening finished ones.
• Clinicians see suspected conditions alongside the evidence, and they make the call. The suggestion informs judgment rather than replacing it.
• Leaders can see where documentation gaps cluster, by provider or by condition, while there is still time in the year to support those clinicians.
• The fourth quarter stops being a sweep. Some catch-up work always remains, but it becomes the exception rather than the plan.

Prospective isn't a coding strategy. It's a timing one: getting the insight to the clinician inside the encounter, not after it. It means treating the whole year as the window, the same way quality teams approach year-round care gap work.

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