The HCC Triple Threat Draining Your Medicare Advantage Revenue in 2026

Executive Briefing:

• The V28 Shock: As of January 1, 2026, the CMS-HCC V28 model is 100% in effect — removing 2,264 diagnosis codes from risk scoring and demanding specificity levels most practices are not yet capturing. The phase-in buffer is gone.
• The January Cliff: RAF scores reset to zero every January 1st. Every chronic condition must be re-documented with V28-compliant specificity in a 2026 encounter or it does not count. There is no carry-forward.
• The RADV Escalation: CMS expanded from auditing 60 Medicare Advantage contracts to 550+ in 2025, grew its reviewer workforce from 40 to 2,000, and is targeting $4.7 billion in extrapolated recoveries through 2032. Every MA contract is now exposed.
• The Per-Member Math: Undercoding gaps average $3,000 per member annually. A single missed HCC on one patient costs approximately $2,080 per year. Across a panel of 500 MA members, a 15% recapture failure represents a six-figure PMPM shortfall.
• The Structural Fix: The practices protecting their Medicare Advantage revenue in 2026 are not buying more software. They are deploying prospective, human-led coding teams who work inside the EHR at the point of care — capturing conditions before the encounter closes, documenting MEAT criteria in the clinical note in real time, and building RADV defensibility from the first keystroke.

---

Part I. The Situation: Three Clocks Running at Once

It is a Tuesday morning in late May 2026.

Your front desk is checking in the first wave of Medicare Advantage patients. Your physicians are already behind. The EHR queue has seventeen pre-loaded appointments, a mix of chronic disease management visits, annual wellness exams, and acute follow-ups.

Somewhere in that queue are patients with Type 2 diabetes, chronic kidney disease, heart failure, COPD, and major depressive disorder. Each of those conditions, if captured correctly today, contributes meaningfully to your RAF score and your PMPM capitation payment. Each one missed, undercoded, or documented without the clinical narrative to back it up does the opposite — it silently shrinks the revenue your practice will receive for managing those patients all year.

This is not a hypothetical scenario. It is the operational reality of Medicare Advantage in 2026. And for the first time in the history of the program, three separate financial threats have converged simultaneously — each one damaging on its own, genuinely dangerous in combination.

Understanding all three is the first step toward protecting your revenue before this coding year closes.

---

Part II. Threat One — The V28 Model Is Now Fully Live and Most Practices Are Not Ready

For three years, the CMS-HCC V28 model was a phase-in. A future concern. Something to plan for.

As of January 1, 2026, the phase-in is over. V28 is 100% in effect. Risk scores are calculated entirely under the new model. There is no V24 blending, no transition buffer, and no grace period.¹

The structural change is more severe than most revenue cycle teams have internalized. V28 did not simply swap some codes. It fundamentally restructured how CMS measures clinical complexity:

2,264 diagnosis codes were removed from risk scoring entirely. Conditions your coders have been capturing for years — conditions that contributed to RAF scores under V24 — now generate zero RAF value under V28. If your coding workflows have not been audited and updated against V28 mappings since January, you have been submitting RAF-neutral codes for five months and receiving capitation payments that do not reflect your patient population's true acuity.

Specificity requirements increased dramatically. The clearest example is diabetes. Under V24, broad diabetes coding was sufficient. Under V28, CMS requires your practice to distinguish between 38 separate diabetes-related HCC mappings. The financial difference is not academic: E11.9 (Type 2 diabetes without complications) carries a RAF coefficient of approximately 0.105. E11.42 (Type 2 diabetes with diabetic neuropathy) carries approximately 0.302 — nearly three times higher. If your patient has neuropathy and it is not documented and coded to that level of specificity, your practice is collecting roughly one-third of the reimbursement it has earned for that patient's complexity.²

Most organizations are not yet capturing at V28 standards. Industry data shows that practices relying on manual chart review workflows capture less than 60% of legitimate HCC codes even under V24 standards. Under V28's tighter specificity requirements, that capture rate is almost certainly lower — because the documentation bar for each code is higher, and the mapping logic is more granular than most EHR dropdown workflows are designed to handle.³

The practices that will close 2026 with accurate RAF scores are those whose coding workflows reflect V28 from every encounter forward — not those planning a retrospective cleanup in November.

---

Part III. Threat Two — The January RAF Reset Is Already Four Months Deep

This is the threat most practices understand intellectually but chronically underact on — because its consequences are invisible until they are irreversible.

Every Medicare Advantage RAF score resets to zero on January 1st. Chronic conditions do not carry forward automatically. A patient with diabetes mellitus, chronic kidney disease stage 3, and major depressive disorder who was perfectly coded in 2025 is, from CMS's perspective, a blank slate on January 1, 2026 — until each of those conditions is re-documented with V28-compliant specificity in a qualifying 2026 encounter.⁴

It is now late May. That means approximately five months of the coding year have already elapsed. Every Medicare Advantage patient who has not had a qualifying encounter where their chronic conditions were properly recaptured represents a RAF gap that is compounding daily.

The Per-Member Math

The financial arithmetic is specific enough to bring to a board meeting:

• Undercoding gaps average $3,000 per member per year across Medicare Advantage populations — a figure that reflects the aggregate impact of conditions managed but not documented to the level CMS requires.⁵
• For a single missed chronic condition, the math is equally concrete: losing one HCC with a coefficient of 0.20 costs approximately $2,080 in annual capitation revenue for that one patient alone.⁶
• Industry data shows that 15–25% of chronic condition HCCs are lost annually to incomplete recapture — not because the conditions do not exist, but because the qualifying encounter did not produce the documentation to prove they were addressed.⁶

Scale that across a panel. A practice managing 500 Medicare Advantage members with a 20% annual recapture failure rate is not experiencing a documentation inconvenience. It is experiencing a six-figure annual PMPM shortfall that is structurally baked into its capitation payments for the rest of the year.

The retrospective correction window exists — but it closes. And every month of delay is a month of lost payments that cannot be fully recovered.

---

Part IV. Threat Three — CMS Just Turned RADV Audits Into an Existential Risk

If V28 and the RAF reset are the revenue threats, RADV is the compliance threat — and in 2026, it has escalated to a scale the Medicare Advantage industry has never seen before.

On May 21, 2025, CMS announced a fundamental restructuring of its audit program. The scope of that announcement deserves to be stated plainly, because most providers have not yet absorbed its implications:

The audit pool expanded from 60 contracts to 550+. Historically, CMS audited approximately 60 Medicare Advantage contracts per year — a small fraction of all eligible organizations. Starting with Payment Year 2018, CMS has committed to auditing every eligible MA contract, covering PY 2018 through PY 2024. What was a statistical improbability is now a near-certainty.⁷

The reviewer workforce expanded from 40 to 2,000. This is not a policy change. It is an operational mobilization. CMS did not announce an intent to audit more plans; it built the infrastructure to do it.⁸

The extrapolation methodology makes small errors catastrophically expensive. Under CMS's current RADV framework, auditors review a sample of approximately 200 records per plan per payment year. If that sample reveals unsupported diagnoses, CMS extrapolates the error rate across the entire contract. A 5% documentation error rate on a 200-record sample can generate millions of dollars in recoupment demands — projected across every claim in the contract for that payment year. CMS estimates $4.7 billion in total recoveries through 2032 using this methodology.⁹

Downstream providers are directly exposed. If your practice has a risk-sharing arrangement with a Medicare Advantage plan — capitation contracts, shared savings agreements, value-based care partnerships — read your contract's clawback provisions carefully. Many MA contracts allow the plan to seek recoupment from at-risk providers if CMS identifies unsupported diagnoses in shared-risk populations. The audit lands at the plan level. The financial consequence can travel downstream to your practice.¹⁰

What RADV Auditors Are Actually Looking For

Understanding the audit mechanics is the first step toward defensibility. CMS auditors are not looking for fraud. They are looking for the gap between what was coded and what was documented.

The most common finding is also the most preventable: a physician selects an ICD-10 code from the EHR dropdown for a chronic condition — diabetes, heart failure, CKD — but the clinical note for that encounter does not contain the documentation to support it. There is no evidence the condition was Monitored, Evaluated, Assessed, or Treated during that visit. The code exists in the system. The clinical justification does not exist in the note.

That gap — between the submitted code and the supporting documentation — is what triggers recoupment. And it is not a coding error. It is a documentation workflow failure.

---

Part V. Why the Standard Solutions Are Not Enough in 2026

Before we discuss the structural fix, it is worth being direct about why the two most common responses to this environment are insufficient.

Response 1: "We will do a retrospective chart review in Q4."

Retrospective review is the industry's default fallback, and in 2026 it carries three specific liabilities it did not carry in prior years. First, a retrospective review in November cannot recapture the PMPM revenue lost on every month of the year where RAF gaps existed — those payments are gone. Second, under V28's increased specificity requirements, retrospective corrections require more clinical evidence than V24 corrections did — conditions that can be inferred from a V24 chart often require explicit current-year documentation under V28. Third, and most critically in a RADV audit environment, retrospective corrections submitted close to the year-end submission deadline receive disproportionate auditor scrutiny. A pattern of late-cycle diagnosis additions is one of the indicators CMS has specifically cited as a risk factor in its audit targeting criteria.

Response 2: "We will implement an AI coding platform."

The software-based risk adjustment market is mature, well-funded, and highly capable at one specific task: identifying coding opportunities in completed documentation. What AI platforms cannot do is change the documentation itself. They can flag that a patient likely has diabetic neuropathy based on clinical data patterns and suggest E11.42 instead of E11.9. But if the physician's note does not contain the clinical narrative supporting that code — the examination finding, the treatment decision, the MEAT-criteria documentation — the suggested code is not defensible in an audit regardless of how accurately it was suggested.

The RADV audit does not review the software output. It reviews the physician's note.

The gap between "correctly coded" and "defensibly documented" is the gap that AI platforms cannot close — because closing it requires someone to write the clinical note correctly in the first place.

---

Part VI. The Structural Fix: Prospective, Human-Led, Point-of-Care

The practices protecting their Medicare Advantage revenue in 2026 share a structural characteristic that distinguishes them from those running retrospective cleanup cycles: they have moved the coding workflow from after the encounter to before and during it.

This is the prospective model. And it works for a reason that is specific to how CMS auditors evaluate documentation: a clinical note written correctly at the time of service is categorically more defensible than a note amended afterward. Prospective coding does not produce corrections. It produces original, accurate, MEAT-compliant documentation — from the first keystroke.

Here is what that looks like in a concrete clinical workflow:

Before the encounter: A dedicated risk adjustment coder reviews the patient's chart against their 2025 HCC history and current V28 mappings. Every suspected chronic condition requiring recapture is flagged. The V28-specific ICD-10 code that accurately reflects the patient's current acuity is identified. The physician receives a pre-visit summary: the conditions to address, the specificity required, and the clinical evidence needed to support each one. The physician walks into the room informed, not hunting.

During the encounter: A specialized medical scribe documents the clinical narrative in real time — ensuring the physician's examination findings, treatment decisions, and clinical judgments are captured in the note with the MEAT-criteria language that directly supports each billed HCC. The physician focuses entirely on the patient. The documentation is built for RADV defensibility from the first sentence.

After the encounter: The note is complete. The HCC is supported. The code and the documentation align. There is nothing to correct, nothing to add retrospectively, and nothing that will surprise an auditor.

This model produces three outcomes simultaneously that no other approach can deliver together: accurate V28-specific coding, MEAT-compliant documentation, and a prospective recapture workflow that closes the January RAF gap month by month rather than attempting to recover it at year-end.

---

Part VII. How iRevMed Delivers This Model — Inside Your EHR, From Day One

This is where iRevMed's HCC Coding and Audit services operate differently from every software platform and every traditional coding vendor in this market — and the difference is structural, not incremental.

Every AI-based coding platform in the market performs the same function: it reviews completed documentation and suggests coding additions or corrections. The physician or coder then acts on those suggestions. That is still a retrospective workflow, even when it happens on the day of the encounter. The note was written first. The coding review happens after.

iRevMed operates upstream of that. Our certified risk adjustment coders and specialized medical scribes work concurrently inside your EHR via secure VPN — no data migration, no new software to install, no parallel system to manage. We connect directly to your existing Epic, Cerner, or eClinicalWorks instance. Your workflow does not change. The documentation quality does.

What that means in practice:

V28 compliance is built into every encounter. Our coders work from V28-native workflows. The specificity gap that exists between E11.9 and E11.42 is not something we flag after the note is written — it is something we address in the pre-visit chart sweep, so the physician knows to document neuropathy findings before the encounter begins.

MEAT documentation is written into the clinical note, not reviewed against it. This is the critical distinction. When a CMS auditor reads the record for your diabetic patient with peripheral neuropathy, they are not reading a coding suggestion. They are reading a physician note that contains examination findings, a treatment decision, and a clinical assessment — all of which directly support the E11.42 code. The audit trail is the note itself.

The RAF gap closes prospectively, not retrospectively. Every qualifying encounter produces a recaptured HCC. By the time the annual submission window opens, your RAF score reflects the actual clinical complexity of your patient population — not the portion of it that survived a retrospective cleanup in November.

The outcome our clients experience is captured in a single verified metric: a 21%+ average RAF score lift within the first 12 months. That lift is not the result of more aggressive coding. It is the result of accurate coding — capturing the conditions that exist, at the specificity V28 requires, with the documentation that makes them audit-proof.

Combined with a 98%+ coding accuracy rate and a dedicated team of certified professionals working inside your existing infrastructure, this is what closing the HCC triple threat looks like in practice.

---

Part VIII. The Three-Number Self-Audit

Before your next revenue cycle meeting, three numbers are worth pulling from your data. Together they tell you whether the HCC triple threat is already inside your margins.

Number 1 — Your 2026 RAF score vs. your 2025 baseline. If your average RAF score has declined from January to May without a corresponding change in your patient population's acuity, you have a recapture failure. V28's 2,264 removed codes and increased specificity requirements mean that a flat RAF score in 2026 almost certainly reflects a real decline in capture quality, not stable patient complexity.

Number 2 — Your chronic condition recapture rate by HCC category. Specifically: what percentage of patients with a 2025 diabetes HCC have had that condition re-documented in a 2026 encounter with V28-compliant specificity? If that number is below 85%, you have a systematic recapture gap that is compounding with every passing month.

Number 3 — Your documentation error rate on recent HCC submissions. Pull a sample of 20 recent Medicare Advantage encounters where a chronic condition HCC was coded. For each one, verify that the clinical note contains explicit MEAT-criteria documentation supporting that specific code. If more than 2 or 3 of those 20 notes contain codes unsupported by the clinical narrative, your RADV exposure under the extrapolation methodology is material.

If any of these numbers are moving in the wrong direction, the triple threat is already affecting your revenue. The question is whether you address it prospectively — while there is still time to recapture 2026 conditions — or reactively, after the submission window closes.

See how iRevMed clients have secured their RAF revenue →

---

Part IX. A Final Word on Timing

The HCC coding year does not give unlimited recovery windows. Every month that passes without a prospective recapture workflow in place is a month of PMPM capitation that arrives below what your patient population's complexity justifies.

The practices that will enter 2027 with strong RAF baselines are making structural changes to their coding workflows now — in May and June — not in October when the retrospective correction scramble begins. The window for prospective impact is open. It will not stay open indefinitely.

The data is unambiguous. The per-member math is calculable. The audit exposure is documented. The only variable is whether your practice acts on it before the window closes — or after.

---

(This content is intended for informational and educational purposes only. The financial projections, per-member revenue estimates, and audit risk assessments referenced in this article are derived from published industry research and CMS regulatory announcements. Actual outcomes vary based on practice size, specialty, patient population, payer mix, and existing documentation and coding infrastructure. Nothing in this article constitutes legal, compliance, or financial advice. Organizations facing active RADV audit activity or specific compliance concerns should consult qualified legal counsel and certified compliance professionals. iRevMed's service outcomes, including RAF score improvements and coding accuracy rates, reflect verified client results and are not guaranteed for all organizations.)