Two Approaches, Two Different Problems
A Medicare Advantage plan with 18,000 members recently completed a retrospective chart review and recovered meaningful RAF credit from conditions that had been documented by physicians but never coded. The wins were real. The problem was that some of those conditions had been unaddressed at the encounter level for an entire plan year, meaning the patient never received a targeted care intervention for a chronic condition the physician had technically noted. The RAF gap and the care gap were the same gap, and retrospective review caught the coding side of it too late to fix the clinical side.
That scenario captures the core tension in the prospective vs retrospective risk adjustment debate. Both approaches serve legitimate purposes. Neither is a complete solution on its own. Organizations that treat them as competing strategies, choosing one and ignoring the other, consistently leave RAF accuracy on the table and create unnecessary audit exposure.
What Prospective Risk Adjustment Review Actually Is
Prospective review happens before or during the patient encounter. A trained coder, CDI specialist, or technology-assisted workflow reviews the patient's historical claims data, prior HCC captures, clinical notes, and known chronic condition history before the physician walks into the exam room.
The output is typically a gap list or suspecting report, sometimes called a pre-visit prep summary, that surfaces conditions previously diagnosed, HCC categories that have lapsed because they were not recaptured in the current plan year, and potential condition gaps suggested by the patient's medication list, lab values, or problem list. That summary reaches the physician, through the EHR workflow, a pre-visit huddle, or a printed encounter guide, before the visit begins.
The Goal: Get Documentation Right the First Time
Prospective review is not about telling physicians what to diagnose. It is about making sure a physician who already knows this patient has diabetes with peripheral neuropathy does not walk out of a 20-minute wellness visit having documented only "DM2, controlled" and missing the neuropathy that maps to a separate, higher-weighted HCC entirely.
When prospective prep works correctly, the physician addresses the condition, documents specificity, and the coder captures the HCC on the first submission. The RAF is accurate from day one of that encounter date. No correction, no addendum, no late-year scramble.
This approach requires real infrastructure. Someone has to pull and review the pre-visit data. The physician has to engage with the gap list during an already compressed schedule. The EHR workflow has to surface the right information without becoming noise. That is not a small lift, which is why many organizations have not fully implemented it even when they understand its value. Investing in CDI program support is often what makes prospective review operationally sustainable rather than a pilot that stalls after three months.
What Retrospective Risk Adjustment Review Actually Is
Retrospective review happens after the encounter is complete, sometimes weeks or months later, and sometimes after the claim has already been submitted to CMS. A coder or auditor reviews the chart, the documentation, and the codes submitted, looking for one of two failure modes: conditions that were documented but not coded, and codes that were submitted without sufficient clinical documentation to support them.
The first type generates addenda and late-year submissions that recover RAF credit. The second type generates corrections that reduce RAF and audit risk. Both are necessary.
Why Retrospective Review Is Easier to Implement
Retrospective review does not require changing what physicians do at the point of care. It is a pure coding and audit function. You can scale it by adding certified coders who specialize in risk adjustment and HCC coding, by running periodic chart pulls against your member population, or by targeting specific high-gap cohorts such as members with multiple chronic conditions whose HCC recapture rates have dropped year over year.
Because it does not touch clinical workflow, you can start it quickly. You do not need physician buy-in to begin. You do not need to redesign your EHR templates. You pull charts, you audit, you submit corrections or addenda.
The tradeoff is significant, though. By the time retrospective review finds a gap, the encounter has already ended. If the physician did not document the condition with enough specificity to support the HCC, an addendum can sometimes fix that, but it introduces medical record integrity risk and requires a physician to go back and revisit a visit that happened weeks ago. If the condition was never addressed at the encounter at all, no addendum fixes the underlying clinical gap. The RAF window for that encounter is effectively closed unless another visit occurs within the plan year.
Downloading our free HCC audit checklist can help your team structure retrospective review so that common documentation gaps, such as missing etiology specificity, vague manifestation linkage, or unsigned addenda, are flagged consistently rather than caught inconsistently depending on which coder pulls the chart.
Comparing the Two Models on Timing and Impact
Timing is where the difference between these two approaches matters most, and where most organizations underestimate the cost of relying on only one.
Prospective review prevents the gap from being created. That is categorically more valuable per chart because it produces an accurate RAF on the first submission, generates no compliance risk from addenda, and closes the care gap at the same time it closes the coding gap. One encounter done right is worth more than one encounter done wrong followed by a correction cycle.
Retrospective review catches what already happened. That is still valuable, particularly in large member populations where no prospective program can achieve 100 percent encounter coverage. But it is corrective by nature. It adds cost in the form of addendum workflows, physician rework, and potential RADV exposure if corrections draw scrutiny. Organizations subject to CMS Risk Adjustment Data Validation audits need to be especially careful that retrospective-driven addenda reflect genuine clinical support documented contemporaneously, not reconstructed clinical rationale added after the fact to support a code.
One clear takeaway: for conditions that are likely to recur year over year in a chronic disease population, failing to address them prospectively means running a retrospective recovery program for the same conditions on the same patients, year after year, at ongoing cost.
Comparing the Two Models on Cost and Organizational Effort
Prospective review carries a front-loaded infrastructure cost. You need pre-visit prep capacity, either staff time from coders or CDI specialists or a technology platform that surfaces gap lists from claims and clinical data. You need physician engagement, which may require internal champions, leadership support, and iterative workflow design to keep the gap list from being ignored. You need EHR configuration or workarounds. And you need a feedback loop so that coders know whether the physician acted on the gap list or not.
None of that is cheap or fast to build. It is also hard to outsource entirely, because the physician engagement component is inherently internal.
Retrospective review, by contrast, is a function that can be staffed, scaled, and managed as a discrete coding operation. It can be partially or fully outsourced to a specialized firm without requiring any change to clinical workflow. The work happens after the fact, the output is a coding or correction action, and the quality of that output depends entirely on coder expertise and audit methodology, not on physician participation.
If your organization is considering how to scale its audit function independently of clinical workflow, a dedicated coding quality audit program is a practical starting point that produces both RAF recovery and compliance assurance simultaneously.
The Case for Running Both Together
The strongest RAF accuracy programs treat prospective and retrospective review as layers in the same system, not as alternative choices.
Prospective review reduces the rate at which gaps are created. It handles the conditions the physician already knows about, already manages, and simply needs a structured prompt to document completely. For a high-volume Medicare Advantage practice with strong EHR workflow control, a well-implemented prospective program can substantially reduce the volume of work the retrospective program has to do.
Retrospective review then acts as a safety net for what prospective missed. No prospective program catches everything. Physicians will still see patients in ways that diverge from the pre-visit prep. New conditions will emerge during the encounter that were not on the gap list. Documentation specificity will still sometimes fall short even when the condition was addressed. Retrospective review catches those residual gaps before the plan year closes and before the next RADV cycle creates an exposure.
The organizations that achieve the highest RAF accuracy rates are running both, because the failure modes they address are genuinely different. For additional context on how to build the internal coding infrastructure that supports both models, the post on when to outsource HCC risk adjustment coding walks through which functions benefit most from external support and which need to stay close to the clinical team.
Where to Start When Resources Are Limited
Most organizations cannot build both programs simultaneously. The practical question is which one to prioritize first.
Start Prospective If You Have These Conditions
Prioritize building a prospective program first if your organization has strong physician leadership support for closing care gaps, existing EHR infrastructure that can surface problem lists and medication data reliably, a CDI team or the budget to build one, and a member population concentrated enough that pre-visit prep is operationally feasible rather than overwhelming.
Primary care-heavy Medicare Advantage groups and accountable care organizations with attribution-based incentives tend to fit this profile. The prospective model aligns naturally with their existing quality program structure.
Start Retrospective If You Have These Conditions
Prioritize retrospective review first if your organization cannot yet move clinical workflow, if physician engagement is nascent or inconsistent, if you are trying to establish a baseline of RAF accuracy before building the case for prospective investment, or if you are facing a near-term RADV audit and need to identify and correct documentation deficiencies quickly.
Retrospective findings also make the internal business case for prospective investment concrete. When leadership can see, in specific condition categories and specific physician cohorts, exactly where documentation gaps are recurring year over year, the argument for pre-visit prep infrastructure becomes much easier to make. Read more about preventing those recurring gaps in the companion post on avoiding common HCC coding errors, which covers the specific documentation failures that retrospective auditors find most consistently.
The Decision Is Not Either/Or
Prospective vs retrospective risk adjustment is not a binary choice for any organization serious about RAF accuracy and CMS compliance. The two models solve different problems at different points in the encounter lifecycle. Relying on prospective review alone assumes your pre-visit prep and physician engagement will be comprehensive enough to catch every gap before it becomes a missed HCC. Relying on retrospective review alone means you will always be correcting yesterday's problems instead of preventing tomorrow's.
The organizations that treat this as a complementary system rather than a competitive choice build more accurate RAF scores, carry less RADV exposure, and create a closer connection between their coding outcomes and their clinical quality data.
Contact the MedCodex risk adjustment team to discuss how a layered prospective and retrospective review program can be structured for your specific member population and organizational capacity.