Most risk adjustment analytics produce more lists. What a team actually needs is fewer, better decisions. Whether you run a health plan, a provider group taking risk, or a health system that owns its own plan, the reports pile up while the same question goes unanswered. Of everything the model flagged, what will actually change the score this year, and can you prove every piece of it when CMS looks back?
A dashboard full of suspects and theoretical RAF does not answer that. It tells you what might be out there, not what is real, not what will close, and not what already counted. So teams work long lists, the score moves less than the report promised, and nobody can say why.
This is what strong risk adjustment analytics should tell you, how plans and provider organizations measure real performance, and why analytics that only look backward are about to cost more than they used to.
What Risk Adjustment Analytics Should Tell You
Good analytics answer three questions, in order. Most tools answer only the first.
Is it real? A suspect is a lead, not a capture. Analytics should show the evidence behind each condition, the line in the chart or the lab or the medication that supports it, so a coder can confirm it instead of hunting for proof. A flag with no evidence just moves work around.
Will it close? A condition is only worth working if the member can be reached and seen this year. Analytics that ignore whether a visit is scheduled, whether the member has an active primary care relationship, or whether an outreach opt-out is on file will keep sending high-RAF names that never close. Ranking by RAF value alone is the most common reason a worklist underperforms.
Did it count? This is the one almost nobody measures. A diagnosis your team captured is not the same as a diagnosis CMS accepted. Until analytics reconcile what you submitted against what came back, your reports are showing captured conditions that never reached the score. That gap between captured and counted is where real money quietly sits, and it never appears on a chart-based dashboard.
The Numbers That Actually Measure Performance
Volume metrics make a platform look busy. They do not tell you if it is working. A few real measures do.
Recapture rate. Of the chronic HCCs a member carried last year, how many came back this year? Chronic conditions do not resolve, so a low recapture rate is the cleanest signal of documentation and coding falling out of step. This is the number that tracks accuracy over time.
Encounter acceptance rate. Of everything you submitted, how much did CMS actually accept and keep? A high capture rate on your internal report means nothing if acceptance is low. This is the number that separates work done from work that counted.
Gap closure rate on the reachable population. Not raw suspects generated, but the share of workable gaps your team actually closed. Measured against the members who could realistically be seen, this tells you whether your outreach and coding capacity is aimed at the right people.
None of these is about finding more codes. They are about accurate, complete capture you can defend, which is the only kind that survives an audit.
Who Runs Risk Adjustment Analytics Now
Risk adjustment used to be a health plan job. It is not anymore, and the search for better analytics has widened with it.
Provider groups in capitated and delegated arrangements carry real risk today, which means they own the accuracy of their own risk scores. ACOs live and die by it. In both the Medicare Shared Savings Program and ACO REACH, the benchmark and the shared savings depend on a risk score that has to be accurate and defensible, so the analytics problem lands squarely on the provider organization. And a growing share of health plans are owned by health systems. Intermountain owns Select Health, Baylor Scott & White runs its own plan, and industry trackers count more than forty health-system-owned plans. For those systems, coding, analytics, and submission are all in-house, and the same three questions apply end to end.
The shape of the problem is identical whether you sit on the plan side or the provider side. Know what is real, know what will close, and know what counted. A platform that only speaks to plans leaves the provider groups and systems doing the same work without the same tools.
Want to see this run on your own population?
Prospective and Retrospective, and Why the Balance Is Shifting
Retrospective analytics look back. Find the gaps after the year, pull the charts, submit the chart reviews, catch what the year missed. Prospective analytics look forward. Surface the likely conditions before or during the visit, so the provider documents and codes them on a live encounter while the member is in the room.
Both have a place, but the balance is moving toward prospective, and provider organizations feel it first because they are at the point of care. A condition confirmed during the visit costs less to close and carries cleaner evidence than the same condition chased through a chart review nine months later. Analytics that only score after submission miss the one window where closing a gap is cheap and clean.
How Invent Health’s Analytics Work
Invent Health runs analytics across the whole loop rather than at one stop in it. Coding, risk analytics, and encounter submission work as one connected system, so every number traces back to the chart it came from.
Risk Analytics is the engine. Suspect logic runs across historical, lab, pharmacy, comorbidity, and chart-derived signals, drawing on EMR data through CCD and FHIR, and it scores both the medical HCC RAF and the pharmacy RXC so you see the full risk picture, not half of it. Conditions are ranked by how much they affect the score, and the platform surfaces the supporting evidence with each one so it can be confirmed, not just counted. Invent Health’s NLP detects that supporting evidence with 85 percent or higher accuracy out of the box.
Encounter Submissions closes the loop and answers the “did it count” question. One engine validates and submits clean encounters, then reconciles what comes back, matching MAO-002 and MAO-004 for Medicare and the RARSD, RACSD, and ECD for ACA. A diagnosis that did not count returns as a known condition needing a corrected encounter, ranked by its RAF or RXC value, instead of reappearing as a fresh suspect.
Every diagnosis stays linked to the chart it came from, which gives audit-defensible lineage for RADV. Because Invent Health also works with delegated provider groups and IPAs, the same analytics roll up to the provider group level, so a health system, an ACO, or a plan can all see where captures succeed and where they fail. The platform supports CMS-HCC V24 and V28, ESRD, RxHCC, and HHS-HCC for ACA, and new CMS or HHS models are typically live within 30 to 60 days of advance notice.
Why Backward-Looking Analytics Cost More in 2027
Right now most organizations still lean retrospective. That model is losing its safety net.
The CY 2027 Rate Announcement ends unlinked chart reviews beginning with the 2027 payment year, so a diagnosis found in a chart review has to tie back to an encounter CMS accepted. Analytics that surface a condition in December, with no accepted encounter to attach it to, have found it too late. The July HPMS memo on CY 2027 risk adjustment implementation spells out what plans and their delegated partners need in place.
Two more pressures point the same way. The V28 model removed a large share of diagnosis codes from risk-adjustment mapping and re-based the values, so fewer conditions carry payment and each one has to hold up on its own. And RADV audits are moving toward every contract every year, with sample findings extrapolated across the contract, which makes a weakly supported capture far more expensive than the single code it looks like. Analytics that cannot show the evidence and the acceptance behind every score are a liability in that environment, not an asset.
The organizations in the best position for 2027, plan or provider, are the ones whose analytics look forward and reconcile backward at the same time.
See What Your Current Analytics Are Missing
The fastest way to judge any risk adjustment analytics is to run it against a population you have already worked. Look at what it finds, what it can prove, and how much of it was captured and then lost somewhere between the chart and the CMS response file.
Frequently asked questions
What is risk adjustment analytics?
Risk adjustment analytics is the process of finding, ranking, and verifying the diagnoses that determine a member’s risk score. Strong analytics show which conditions are supported by evidence, which can realistically be closed this year, and which the payer actually accepted, so teams work the right conditions and can defend every one.
What is the difference between prospective and retrospective risk adjustment?
Prospective risk adjustment surfaces likely conditions before or during a visit, so they get documented and coded on a live encounter. Retrospective risk adjustment finds them afterward through chart review and supplemental submissions. Prospective work costs less per closed gap and carries cleaner evidence, and it is becoming more important as CMS tightens the rules on unlinked chart reviews.
How do you measure risk adjustment performance?
Three measures matter most. Recapture rate, meaning how many of last year’s chronic HCCs came back this year. Encounter acceptance rate, meaning how much of what you submitted CMS actually accepted. And gap closure rate on the reachable population, meaning the share of workable gaps your team actually closed. Raw suspect counts measure activity, not performance.
What is HCC recapture rate?
HCC recapture rate is the share of a member’s chronic hierarchical condition categories from last year that are reported again this year. Because chronic conditions do not resolve, a low recapture rate usually signals documentation and coding gaps rather than real clinical change, which makes it one of the clearest measures of coding accuracy over time.
Do provider groups and health systems need risk adjustment analytics?
Yes. Provider groups in capitated or delegated arrangements carry real risk, ACOs in MSSP and ACO REACH depend on accurate scores for their benchmarks, and many health systems own their own plans and run coding, analytics, and submission in-house. All of them need the same thing a plan does: to know what is real, what will close, and what counted.
How is risk adjustment used in value-based care?
In value-based care, a provider organization’s payment and shared savings depend on an accurate risk score that reflects how sick its population really is. Under-documenting understates risk and payment, while unsupported capture creates audit exposure. Accurate, defensible risk adjustment analytics let value-based organizations reflect true risk and hold up under review.
What is the difference between medical and pharmacy risk scoring?
Medical risk scoring builds the HCC RAF from diagnosis codes on claims and encounters. Pharmacy risk scoring builds a separate RXC score from the medications a member is on. A complete view uses both, because a medication can point to a condition no claim ever coded, and missing that signal costs on the pharmacy side and the medical side.
Why do risk adjustment dashboards overstate performance?
Because most dashboards report what was captured internally, not what CMS accepted. A diagnosis that was coded, submitted, and then rejected or voided still shows as captured on the internal report even though it never reached the score. Only reconciling submissions against the CMS response files reveals the difference between captured and counted.
What is encounter acceptance rate?
Encounter acceptance rate is the share of submitted encounters, and the diagnoses on them, that CMS accepts and keeps for risk adjustment. It is a truer measure of performance than internal capture, because work that is rejected or later voided does not count toward the score no matter how well the chart supports it.
How does risk adjustment analytics support audit defense?
Audit-defensible analytics link every scored diagnosis back to the chart evidence and the accepted encounter behind it. When RADV findings are extrapolated across a contract, a weakly supported code is expensive, so analytics that show clear lineage from chart to CMS acceptance turn audit response from a scramble into a lookup.
What data do you need for risk adjustment analytics?
At minimum: enrollment files, professional and institutional claims, pharmacy and lab feeds, supplemental data, and the CMS response files, including the MMR, the MOR, and MAO-004, plus the Edge Server reports for ACA. EMR clinical data through CCD or FHIR adds the chart-level evidence where the deepest gaps usually sit.
How does Invent Health’s risk adjustment analytics work?
Invent Health scores both the medical HCC RAF and the pharmacy RXC, runs suspect logic across historical, lab, pharmacy, comorbidity, and chart signals, and surfaces the evidence with each one. Because coding, analytics, and encounter submission share one platform, it also reconciles what CMS accepted, so captured-but-not-counted diagnoses come back as corrections.
