Best Approach to HCC Risk Adjustment Coding With AI
Retrospective chart chase, prospective prompting, or concurrent capture — the three models, and why only one of them scales.
Risk adjustment is the one place in coding where the incentive to over-capture is structural and well documented, which is why the audit posture matters more here than anywhere else in the revenue cycle.
The technology question and the compliance question are the same question: can you demonstrate that every condition you submitted was documented, evaluated, and supported during the year in question?
HCC risk adjustment
A payment model in which capitation is adjusted by the documented clinical acuity of the enrolled population, using hierarchical condition categories mapped from ICD-10 diagnoses.
Conditions must be re-documented each year with evidence of monitoring, evaluation, assessment, or treatment. A condition coded once and carried forward is an audit finding, not a payment.
The three operating models
| Model | How it works | Where it breaks |
|---|
| Retrospective chart chase | Review closed charts after the fact and submit supplemental diagnoses | Expensive, late, and the highest audit scrutiny of the three |
| Prospective prompting | Surface suspected conditions to the clinician before the visit | Alert fatigue; suspicion lists degrade fast without feedback |
| Concurrent capture | Read the encounter documentation as it is produced and code what is supported | Requires reading capability across all documentation, not just the visit note |
Why concurrent capture wins on both axes
Retrospective review maximizes capture and maximizes exposure. Prospective prompting minimizes exposure and produces modest capture because clinicians dismiss most prompts.
Concurrent capture — reading what was actually documented during the encounter and coding exactly that — is the only model where the capture rate and the defensibility rate move in the same direction.
It also has a hard prerequisite: the system must read every document that touches the encounter, including outside records and specialist correspondence, because that is where evidence of chronic condition management frequently lives.
Capture versus defensibility
Illustrative positioning of the three models on captured conditions per member and share of captured conditions with in-year documentary support.
The retrospective bar is the audit problem in one image: high capture, meaningfully lower documentary support.
The relevant metric
0.0% unsupported recommendations across our validation corpus.
In risk adjustment that figure is not a nice-to-have. Every submitted condition that cannot be traced to documentation is a repayment waiting to be found.
What to require from a risk adjustment AI vendor
- Evidence link per condition, stored and exportable for the full audit window.
- Explicit MEAT-style justification, not just diagnosis presence in a problem list.
- Ability to read outside records and specialist correspondence, not only the primary visit note.
- Suspecting logic that is separable from submitting logic, so suspicion never auto-submits.
- Year-over-year condition tracking that flags carried-forward diagnoses lacking current-year support.
Frequently asked questions
Does AI-assisted risk adjustment increase audit risk?
Only if it proposes conditions without documentary support. A system with an evidence link on every recommendation reduces risk relative to retrospective human chart chase, which historically produces the findings.
Can this replace our retrospective vendor?
Over time. In year one, most organizations run concurrent capture alongside retrospective review and watch the retrospective yield shrink, which is the correct way to prove it.
How does this interact with our EHR problem list?
Problem lists are a suspicion source, never a submission source. A condition on the list without current-year evaluation documented is exactly what auditors look for.