Prospective vs Retrospective Risk Adjustment Explained

Prospective risk adjustment finds conditions before the visit and retrospective finds them after. Both depend on the same thing, and that decides your mix.

Prospective risk adjustment identifies likely conditions before or during a patient visit, so the clinician documents them and the diagnosis goes out on a live encounter. Retrospective risk adjustment finds them afterward, by reviewing charts for conditions that were documented but never coded. Prospective costs less per capture. Retrospective is easier to run. Most plans use both.

That is the standard answer and it is accurate. It also hides the thing that actually determines your results, which is that both approaches depend on the same event, and neither one creates it.

What Prospective and Retrospective Risk Adjustment Each Require

Prospective work needs a visit that has not happened yet. The condition is surfaced, the member is seen, the clinician documents it, and the encounter that carries the diagnosis is created by the visit itself.

Retrospective work needs a chart that already exists. The condition was documented at some point and never made it onto a risk-eligible claim, so a reviewer finds it and submits it.

Different timing, different cost, different operational owners. One shared requirement: a member who saw a provider. Prospective needs the visit to happen. Retrospective needs the visit to have happened. Neither program can manufacture a visit, and a member who does not see anyone produces nothing for either.

This sounds obvious written down. It is not how program decisions get made. Plans compare vendors, cost per chart, and turnaround time, and rarely start from the question of how much of their gap population is reachable at all.

The Number That Decides Your Mix

Take your gap population and split it three ways before you compare any vendors.

Members with a visit already on the calendar. These are prospective candidates today. The question for this group is whether the condition reaches the clinician in time to be acted on, which is a workflow question rather than an analytics one.

Members with recent utilization but no upcoming visit. These are retrospective candidates now and prospective candidates if outreach can produce a visit. This group is where the two programs genuinely compete, and where the choice is a real choice.

Members with neither. No upcoming visit, no recent encounter to review. No program reaches them. Outreach, scheduling, and provider engagement are the only things that change this number, and no risk adjustment vendor sells them.

The size of that third group is the ceiling on everything else. A plan where it is small can run either program well. A plan where it is large has a member access problem that a larger suspect list will not touch, and that is worth knowing before signing anything.

Want to see your gap population split this way?

Book a Demo

Where Each Approach Actually Breaks

Prospective programs break in the handoff. The identification is usually sound. What fails is delivery: the gap arrives after the encounter closed, or it arrives inside a workflow the clinician does not use, or it arrives without the evidence that would let someone act on it in the time a visit allows. None of that is visible in the analytics, because the analytics did their job.

Retrospective programs break at submission. The condition is found and confirmed, and then the diagnosis does not reach the risk score, because the encounter was rejected, or the diagnosis was filtered as not risk-eligible, or a void removed it. The chart review vendor reports a successful find. The risk score does not move.

Both failures share a trait. They happen after the step that reports on itself, so the function holding the dashboard gets the questions and the function holding the problem does not.

Why 2027 Narrows the Choice

The CY 2027 Rate Announcement ends unlinked chart reviews beginning with the 2027 payment year, so a chart review diagnosis has to tie back to an encounter CMS accepted. The July HPMS memo on CY 2027 risk adjustment implementation sets out what has to be in place.

Read that against the shared requirement above. Retrospective review has always depended on a visit having occurred. Now it depends on that visit having produced an encounter CMS accepted. The dependency did not appear, it tightened.

V28 pushes the same way by removing a large share of diagnosis codes from risk-adjustment mapping, so fewer conditions carry payment and each one carries more.

The practical effect is that prospective work gets more valuable without becoming any easier to execute. A plan that cannot get members seen is not helped by a rule change that rewards getting members seen.

How Invent Health Handles Both

Invent Health runs risk adjustment as one connected loop rather than separate tools that integrate, and it starts with analytics, not coding.

Risk Analytics decides what is worth working. Suspect logic runs across historical, lab, pharmacy, comorbidity, and chart-derived signals, drawing on EMR data through CCD and FHIR. Conditions are ranked by how much they move the score and how likely they are to close this year, so a high-value condition on a member nobody will see does not sit at the top of a worklist that cannot be finished.

The Coder Workbench confirms the condition is real. AI-assisted coding reads the clinical documentation, shows the supporting evidence, and recommends ICD-10-CM codes for a certified coder to confirm and sign. It recommends and never assigns. The NLP detects supporting evidence with 85 percent accuracy out of the box and reaches 90 percent as it learns from coder feedback, and the Coder Workbench averages 95 percent coding accuracy across more than 100,000 charts coded.

Encounter Submissions is built to carry that confirmed diagnosis the rest of the way, into 837 files for Medicare and Edge Server XML for ACA, so the identity of the condition holds through submission.

Quality Analytics looks at the same member on the same platform, so a visit that closes a risk gap and a visit that closes a quality measure are one outreach rather than two.

Running prospective and retrospective work off one record is what makes the split above measurable. The same member, the same condition, and one answer about what happened to it.

Start With the Population, Not the Program

Before comparing a prospective vendor to a retrospective one, split your gap population by whether those members can be reached at all. That number decides which program can work for you, and it is the one piece of the decision no vendor can answer.

Book a Demo

Questions, answered

Frequently asked questions


What is the difference between prospective and retrospective risk adjustment?

Prospective risk adjustment identifies likely conditions before or during a visit so they are documented and coded on a live encounter. Retrospective risk adjustment finds conditions afterward by reviewing charts for documentation that never became a coded diagnosis.

Which is better, prospective or retrospective risk adjustment?

Prospective costs less per capture because the visit creates the encounter. Retrospective is easier to operate because the documentation already exists. The better fit depends on how much of a plan’s gap population can realistically be seen, which is a question about member access.

What is prospective risk adjustment?

Prospective risk adjustment surfaces conditions a member likely has before or during an upcoming visit, so the clinician can evaluate and document them. The diagnosis then rides out on the encounter that visit generates, rather than needing a separate submission path.

What is retrospective risk adjustment?

Retrospective risk adjustment reviews existing clinical documentation to find conditions that were recorded in a chart but never coded on a risk-eligible claim. It corrects for capture that was missed during the year, using records that already exist.

What is concurrent risk adjustment?

Concurrent risk adjustment works on documentation close to the time of service, after the visit but before the claim or encounter is finalized. It sits between prospective and retrospective work and is often run by organizations that control the coding workflow directly.

Do prospective and retrospective risk adjustment depend on the same thing?

Yes. Both require a member who saw a provider. Prospective needs the visit to happen and retrospective needs it to have happened. Neither program creates a visit, so members with no upcoming appointment and no recent encounter are out of reach for both.

How should a plan decide its prospective and retrospective mix?

By splitting the gap population into members with a scheduled visit, members with recent utilization but no upcoming visit, and members with neither. The size of the third group caps what any program can produce and points to outreach rather than identification.

Why do prospective risk adjustment programs fall short?

Often in delivery rather than identification. The condition may reach the chart after the encounter closed, arrive in a workflow the clinician does not use, or arrive without the supporting evidence needed to act on it within a visit.

Why do retrospective findings sometimes produce no revenue?

Because a confirmed condition still has to reach the risk score. If the encounter is rejected, the diagnosis is filtered as not risk-eligible, or a later void removes it, the chart review succeeded and the risk score did not change.

Does ending unlinked chart reviews eliminate retrospective review?

No, it tightens its dependency. Starting with the 2027 payment year, chart review diagnoses must tie back to an encounter CMS accepted, so conditions without a qualifying encounter behind them lose their path to payment.

Does prospective risk adjustment work for provider groups?

Often better than for plans, because the group controls scheduling, the EMR workflow, and the documentation. More of the steps sit inside one organization, which removes handoffs where prospective programs commonly lose conditions.

How does Invent Health support prospective and retrospective work?

Risk Analytics ranks conditions by score impact and closure likelihood so reachable members rise first, the Coder Workbench confirms each condition against evidence with a certified coder, and running both off one record makes it possible to see what happened to a given condition.