What is HCC Recapture? Definition, Formula, and Benchmark

HCC recapture addresses a foundational feature of the CMS-HCC and HHS-HCC models: risk scores reset every calendar year, requiring that each chronic condition be re-documented annually with MEAT support to remain in the score. A member coded with diabetes with complications in 2025 does not automatically remain coded for 2026; the condition must be evaluated and documented by a qualifying provider during 2026 to contribute to the 2026 risk score.

This annual-reset architecture has substantial operational consequences. Chronic conditions that tend to be stable — diabetes, CHF, CKD, dementia, COPD — require active recapture each year even when clinically unchanged. A provider who does not address a chronic condition during the year (perhaps because the specialty managing the condition is not the risk-coding primary care) can lose the HCC from that member's score for the year, reducing plan or group risk-adjusted revenue.

Recapture rates are a core risk-adjustment metric. A plan with 10,000 members having prior-year HCCs for diabetes expects to recapture most of those members' diabetes coding in the current year — baseline clinical persistence of diabetes is near 100%. A recapture rate of 70% indicates that 30% of those members went uncoded for diabetes despite almost-certain clinical presence, representing significant forgone revenue.

Operational interventions focus on primary-care annual wellness visits (which provide a structured visit for comprehensive chronic condition review), pre-visit planning that includes prior HCCs in provider huddles, and suspect-condition lists that surface prior-year HCCs for re-evaluation. Concurrent coding review provides a secondary safety net by flagging any encounter where a likely-present chronic condition was not addressed.

Recapture is the single largest source of year-over-year RAF retention. Plans and risk-sharing groups typically divide the risk-adjustment workflow into recapture of persistent conditions, new-year capture of conditions newly documented (fresh diagnoses, conditions not previously recorded), and specificity improvement of previously-coded conditions to more granular HCCs. Recapture is usually the largest of these three buckets.

RADV auditors evaluate each reported HCC independently, so recapture does not reduce audit risk — each year's coding must stand on its own documentation. The compliance standard is identical: MEAT must be present in the current-year note regardless of prior-year documentation. Providers sometimes default to "diabetes, stable, continue current regimen" which is not alone sufficient MEAT; the note must show the condition was actually evaluated or acted upon.

From a coding-compliance standpoint, HCC Recapture lives at the intersection of CPT-category specificity, payer-specific guidance, and internal documentation standards. Practices that run a quarterly HCC Recapture audit against hierarchical condition category and raf score consistently close the coder-provider feedback loop faster than practices that wait for the annual OIG or payer audit to surface the pattern. Reviewers on this site flag HCC Recapture entries whenever payer guidance shifts materially so the associated claim-scrubber logic is updated before the next billing cycle.