The V28 Cliff Is Here. What Matters Now Is Not More Codes. It’s Better Evidence.
- Pudji Siregar-Perk
- 1 day ago
- 5 min read
Updated: 22 hours ago
TL;DR
As of 2026, the CMS-HCC V28 model is fully in effect for Medicare Advantage organizations. Within CMS-HCC V28 risk adjustment, risk scores are now calculated using 100% of the 2024 model. Fewer ICD‑10 codes drive payment, and RADV extrapolation is a real and persistent risk.
The takeaway is simple: Finding more diagnoses is no longer the goal.
What matters now is the ability to identify evidence-backed, model-relevant opportunities that are specific enough to support submission and defensible enough to withstand audit.
Organizations that continue to rely on broad suspecting and opaque workflows will feel increasing operational and financial strain. Those that adapt will focus on prioritization, traceability, and workflow discipline.
For years, the CMS-HCC V28 transition was discussed as something approaching the horizon. Now it is here.
For Medicare Advantage organizations, CMS has completed the phase‑in. Risk scores for 2026 are calculated using 100% of the 2024 CMS-HCC model. This is not a technical footnote. It is a structural change in how risk adjustment works day to day. (CMS)
Many organizations are already experiencing the effects. Risk scores look different. Longstanding assumptions are less reliable. Diagnoses that once “counted” now require greater specificity, clearer linkage, and stronger documentation logic.
The most important question in 2026 is no longer, “How do we find more codes?” It is, “Which opportunities are real, defensible, and worth acting on?”
CMS-HCC V28 Workflow Changes More Than Just Coding Logic
V28 is often described as a coding update. That framing is incomplete.
CMS restructured condition categories, incorporated more recent fee‑for‑service diagnosis and cost data, and introduced clinical revisions aimed specifically at conditions with high coding variation. The stated goal was to improve predictive accuracy. The operational consequence is tighter payment logic. (CMS Factsheet)
The code-mapping change alone is telling. The 2020 CMS-HCC model mapped 9,797 ICD‑10 codes to payment. The finalized 2024 model maps are 7,770.
That reduction fundamentally changes the math behind broad suspecting. When fewer diagnoses drive payment, imprecision carries a higher cost. Workflows that surface large numbers of weak or outdated suspects now create noise before they create value.
That noise is not theoretical. It shows up as reviewer fatigue, repeated chart review, rework, and delayed attention to cases that are actually defensible. V28, in practice, is as much a workflow problem as it is a reimbursement one.
The Problem Is No Longer Detection Alone
For years, many risk adjustment workflows were built around a single promise: more opportunity.
Under V28, that promise is no longer sufficient.
The more relevant question is whether a workflow helps a clinician, coder, or operations leader quickly answer four things:
Is this diagnosis still relevant under current model logic?
Does the documentation support it with enough specificity?
Can the supporting evidence be verified without excessive chart navigation?
Is this worth acting on now?
This is where many “intelligent” solutions break down. Generating a long list of suggestions does not improve outcomes if users still have to manually piece together context, hunt for support, and decide whether a recommendation is usable.
In the current environment, a smaller set of evidence‑linked, defensible opportunities is far more valuable than a large queue of weak suspects. The market is shifting from code discovery to evidence‑guided action.
In a Tighter Audit Environment, Traceability Matters
At the same time V28 tightens payment logic, the audit environment has become less forgiving.
CMS now extrapolates RADV audit findings beginning with payment year 2018. That means unsupported diagnoses expose organizations to risk well beyond individual charts or isolated submissions.
This shift materially raises the bar for V28 documentation requirements.
Accuracy alone is no longer enough. Organizations must be able to explain why a diagnosis surfaced and where the supporting evidence lives. Documentation must be specific, traceable, and aligned with current model logic. If a recommendation cannot be traced directly to a clinician note, lab result, or other source documentation, the burden of validation remains manual.
This is why opacity is becoming operationally dangerous. A system that produces output without visible evidence may look productive on the surface, but it does not create confidence. Instead, it shifts validation work—and audit risk—back to already stretched clinical and operational teams.
In 2026, accuracy without traceability is not sufficient.
What Strong Workflows Need to Do Now
If V28 has exposed anything, it is that many workflows were designed for a less demanding environment.
Going forward, effective systems will not be the ones that generate the most activity. They will be the ones that help teams focus on the right work. Practically, that means answering five questions well:
Is the logic current? Teams should not have to guess whether recommendations reflect the finalized V28 model. This is a present‑tense requirement.
Is the evidence visible? Users should be able to move directly from a suggestion to its supporting documentation without excessive navigation.
Is the opportunity actionable? The goal is not a longer queue. It is a clearer prioritization.
Does it reduce review burden—or just relocate it? Real improvement means less chart‑chasing, not chart‑chasing in a different place.
Can it support trust across stakeholders? Clinicians, coders, operational leaders, and executives all need to understand the reasoning behind what gets acted on.
These are no longer differentiators. They are operating requirements.
Why Workflow Visibility Matters More Under V28
One of the most expensive failures in risk adjustment is not lack of effort. It is a lack of visibility.
In many organizations, data exists. The notes exist. The review queues exist. Yet leaders cannot clearly see where work is stalling, which suspects are weak, or where documentation gaps are emerging until the problem is already costly.
Under V28, that delay is harder to absorb.
Organizations need visibility into the workflow itself: where high‑value opportunities are getting stuck, where weak suspects consume time, and where rework is being created upstream. That visibility allows teams to intervene earlier, rather than cleaning up later.
This is not a reporting convenience. It is a management tool.
The Real ROI Is Revenue Integrity
Risk adjustment is still too often framed as a volume of exercise. That framing no longer fits reality.
The more relevant measure today is revenue integrity: improving confidence in what gets submitted while reducing wasted effort and downstream correction.
That includes fewer weak opportunities entering the workflow, less time hunting for justification, tighter alignment between documentation and coding action, and stronger defensibility when decisions are questioned later.
In SNF and LTC environments, especially, operational discipline matters as much as technical capability. The value of a strong workflow is not simply that it identifies opportunity. It is that it helps teams act with confidence and restraint.
A Clearer Way to Think About the Transition
The Medicare Advantage V28 transition makes one thing clear: the strategy of “finding everything and sorting it out later” is no longer sustainable.
What organizations need now is not more output. They need a better signal.
They need workflows aligned to current model logic, grounded in visible evidence, usable by real clinical teams, and capable of withstanding scrutiny.
V28 did not just change the rules. It made evidence, traceability, and prioritization non-negotiable.
And it did not just change the map. It clarified what will actually hold up in today's risk adjustment environment.
At ParaDocs, this is how we think about V28 shift: the question is no longer whether a system can surface opportunity, but whether it can surface the right opportunity—supported by clear evidence and presented in a way teams can actually act on.
In the current phase of risk adjustment, that distinction is no longer subtle. It is decisive.
Want to see what evidence-linked workflow visibility looks like in practice?
Contact ParaDocs to learn how we think about V28-ready workflows.
Reference:
Comments