Close chronic-condition recapture gaps the chart can defend
Here is the short answer. Recapture surfaces chronic conditions your documentation already supports but that nobody coded this year. Upcoding invents risk the record cannot back up. The line between them is not volume. It is the note. Suspect analytics that respects that line is the only kind worth running.
A geo-grid of suspected-but-undocumented chronic conditions
Read the panel like a map. Each region is a slice of your population. Each tile is a chronic HCC family the analytics flagged as a likely recapture. Green tiles are ready to code today. Amber tiles are real suspects that need a clinician to confirm and document. Red tiles were flagged by an algorithm but the chart does not support them, so they never touch a claim.
The archetypes above stand in for real client panels. No client data is shown. The point is the discipline: every amber becomes a gap closed only after a clinician confirms it in the encounter, and every red stays off the claim.
Closing a gap versus manufacturing risk
Both start from the same suspect list. They diverge the moment you ask what the chart actually says. OIG audits and CMS RADV reviews live in exactly this gap, so the engine has to enforce it, not just suggest it.
Recapture Closes a real gap
The condition is chronic, it exists, and it was addressed this year. You are correcting an omission.
- ✓ The condition is documented in a face-to-face encounter during the current calendar year.
- ✓ The note carries MEAT: it is monitored, evaluated, assessed, or treated.
- ✓ The ICD-10-CM FY2026 code matches the specificity the record supports, including laterality and stage.
- ✓ A provider signs the assessment. The suspect flag informed the review, it did not write the diagnosis.
Upcoding Manufactures risk
The signal came from an algorithm, a stale problem list, or a med the patient no longer takes. The chart is silent.
- ✗ The diagnosis appears only on the claim, never in a current, signed clinical note.
- ✗ It is pulled forward from a prior year with no evidence it was assessed again.
- ✗ Specificity is inflated beyond what the documentation states to reach a higher HCC.
- ✗ It cannot survive a RADV medical-record request or an OIG extrapolated audit.
MEAT is the recapture checkpoint, not a formality
A suspect condition only becomes a codeable diagnosis when the encounter shows at least one element of MEAT. The V28 engine routes every amber tile through this gate before it is ever allowed onto a claim.
Monitor
Signs, symptoms, disease progression, or lab trends are being watched over time.
Evaluate
Test results, medication response, or exam findings are reviewed and interpreted.
Assess
The condition is discussed, ordered, counseled, or recorded in the clinical impression.
Treat
Medications, referrals, therapies, or a care plan tie directly to the diagnosis.
Every chronic condition resets on January 1
Risk scores do not carry a diagnosis forward. Under CMS-HCC rules, a chronic condition must be documented and coded again in each calendar year it is assessed. That single fact is why recapture exists, and why the suspect map has to be rebuilt every year rather than copied from the last one.
CMS-HCC V28 makes precise recapture harder and more valuable
The V28 model reached full weight this payment year. It reorganized the condition categories, pruned many codes that used to map to an HCC, and constrained several coefficients. Broad suspect lists that worked under V24 now produce more noise, so the analytics has to be sharper.
The three-year V24-to-V28 blend is complete. Payment now runs entirely on the V28 crosswalk, so a code that no longer maps to an HCC quietly stops earning.
V28 consolidated and removed categories, especially in diabetes and vascular disease. Specificity in ICD-10-CM FY2026 decides whether a condition still lands in a paying HCC.
CMS finalized extrapolated RADV recovery. A pattern of unsupported codes is no longer a single-chart problem, which is exactly why the red tiles never ship.
Every rule points to a named source
The 2026 payment model, fully phased in at 100% weight, defining which ICD-10-CM codes map to a payment HCC.
Effective October 1, 2025. Governs the specificity, laterality, and combination codes a recapture must match.
The requirement that each chronic HCC be documented and coded again in every calendar year it is assessed.
Office of Inspector General audit work and toolkits on high-risk and unsupported diagnosis codes in Medicare Advantage risk adjustment.
The finalized RADV rule permitting extrapolated recovery of payments tied to unsupported diagnoses.
Monitor, Evaluate, Assess, Treat. The widely used test for whether an encounter supports coding a chronic condition.
See your panel as a suspect map, with the red tiles already filtered out
The ASP-RCM V28 Risk Adjustment engine builds this geo-grid from your own population, routes every suspect through the MEAT gate, and hands your clinicians a confirm-or-drop worklist. You recapture the gaps the chart supports and leave the rest where it belongs. That is revenue you were already owed, defended for the audit that may follow.
Map my recapture gaps → Talk to a risk-adjustment leadThis page is educational and reflects publicly named 2026 CMS, OIG, and ICD-10-CM guidance current as of publication. Panel figures shown are illustrative archetypes, not client data. It is not coding, billing, or legal advice. Confirm every diagnosis against the signed clinical record before submission.
Related reading
Chronic-condition recapture under V28: suspect it, document it, map it every year.
A six-step annual chronic condition recapture checklist for 2026, from building the suspect list to mapping IC
Read →InsightThe 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 →Field noteHCC V28 is fully phased in for 2026. Here is what it does to your RAF.
CY2026 completes the 3-year CMS-HCC V28 phase-in at 100 percent. Use our V24-vs-V28 RAF calculator to see whic
Read →