Chronic-condition recapture under V28: suspect it, document it, map it every year.
2026 is the first payment year that runs on 100% CMS-HCC V28. HCCs do not carry forward. Every chronic condition resets to zero on January 1 and has to be earned back through a face-to-face encounter before December 31.
Recapture is the annual discipline of re-documenting and re-coding each of a patient's chronic conditions inside the calendar year, then confirming every ICD-10-CM code still maps to a payment HCC under the V28 crosswalk. Miss the encounter, or code a diagnosis that V28 dropped, and the condition simply disappears from the risk score. The checklist below is how our V28 engine works a panel from suspecting to mapping.
The risk score resets. The chart does not remind you.
A diabetic with CKD coded perfectly last year contributes nothing to this year's score until a clinician sees the patient and documents it again inside the service year. Recapture is a calendar problem before it is a coding problem.
The 2026 recapture clock
One panel, one calendar year. The earlier a suspect closes, the more runway you have to fix documentation before the sweep deadline.
Six steps: from suspecting a condition to mapping it under V28.
This is the workflow our V28 engine runs on every panel. Print it, tape it to the wall, hold every recapture visit against it.
Build the suspect list before the visit
Recapture starts with a hypothesis, not a blank chart. Pull every signal that a chronic condition is likely present but unconfirmed this year.
Get the patient in front of a clinician
No face-to-face, no capture. The Annual Wellness Visit is the natural container for a full chronic-condition review.
MEAT on every chronic condition
A condition named in the assessment but not worked is a RADV target. Each condition needs evidence it was actively managed.
Code to the FY2026 ICD-10-CM specificity
The score is only as good as the code. General codes and unconfirmed statuses leak risk even when the documentation is strong.
Run the code through the V28 crosswalk
This is where 2026 bites. A code that mapped cleanly under V24 may map to nothing, or to a different HCC, under V28. Never assume it carried over.
Reconcile suspect vs captured, make it RADV-ready
Recapture is not done when the claim drops. It is done when the gap is closed and the documentation would survive an audit.
V24 habits will silently under-capture on the V28 crosswalk.
The model transition finished for the 2026 payment year. Coding on last year's muscle memory is the most common way a well-run panel loses risk it earned.
| Dimension | CMS-HCC V24 | CMS-HCC V28 (2026) |
|---|---|---|
| Payment blend | Phased down across 2024 and 2025 | 100% V28, no blend |
| Payment HCC categories | 86 categories | 115 categories, restructured and renumbered |
| Diagnosis-to-HCC map | Broader; many codes mapped | Constrained; a set of previously mapped codes no longer map to any HCC |
| Category numbering | Familiar legacy HCC numbers | Renumbered; old numbers do not translate directly |
| Recapture requirement | Annual, face-to-face, in-year | Unchanged, and less forgiving because fewer codes map |
| Coding base | Earlier ICD-10-CM revision | Clinically re-based; pair with FY2026 ICD-10-CM at point of care |
Three traps that drain a V28 panel
"It mapped last year."
A code copied forward from a V24 workflow that no longer maps under V28. It looks captured on the claim and contributes zero to the score.
Named, not worked
The condition appears in the assessment but has no monitoring, evaluation, or treatment tied to it. A clean RADV takedown.
The December scramble
Suspects left open until Q4 collide with no-shows and holiday scheduling. The panel runs out of calendar before it runs out of conditions.
Everything here traces to a named 2026 source.
- CMS-HCC V28 ICD-10-CM to HCC mappingThe official diagnosis-to-HCC crosswalk that governs which codes map for the 2026 payment year.
- ICD-10-CM FY2026 code setEffective October 1, 2025. The diagnosis codes coders assign at the point of care.
- CY2026 Medicare Advantage & Part D Rate AnnouncementConfirms the completed phase-in to 100% CMS-HCC V28.
- CMS Risk Adjustment Data Validation (RADV)The audit standard your recapture documentation has to survive.
- Annual chronic-condition recapture principleHCCs reset each calendar year and must be re-documented via a face-to-face encounter.
- MEAT documentation standardMonitor, Evaluate, Assess, Treat. The evidence bar for a validly captured condition.
Recapture is a workflow problem. We run the workflow.
Our V28 risk-adjustment engine builds the suspect list, drives the in-year encounter, checks MEAT, and confirms every code still maps on the current crosswalk, so your panel keeps the risk it actually earned. No fabricated lift, just the conditions that are documented, coded, and mapped correctly.
Educational reference for risk-adjustment and coding teams. Category counts and phase-in status reflect the CMS-HCC V28 model and the CY2026 Rate Announcement; always validate specific codes against the current CMS-HCC V28 ICD-10-to-HCC mapping and the FY2026 ICD-10-CM code set. Not coding, billing, or legal advice. Patient scenarios are illustrative archetypes.
Related reading
The chronic conditions your engine should flag before the reset closes
A calculator view of unrecaptured chronic HCCs under CMS-HCC V28 and the exact documentation each needs before
Read →BriefingV28 hits full weight in 2026. The blend that cushioned you is gone.
In 2026 the CMS-HCC V28 model lands at 100 percent weight. See, in one stat wall, where a group that coded fin
Read →WhitepaperRADV-Ready: Building MEAT-Standard Documentation Into the Risk Workflow
RADV audit readiness starts upstream, not at the audit letter. See how an HCC V28 risk workflow runs every cha
Read →