Key takeaways
- V28 shrinks valid diagnosis codes and flattens coefficients, so risk score accuracy is decided at the point of care, not in the coding queue.
- Documentation, CMS acceptance, and eligibility are often checked by different systems, so problems surface at reconciliation, when it’s often too late to fix them.
- Protecting reimbursement means running documentation, coding, and compliance as one connected process.
- Medicare Advantage’s experience shows how much a model change alone can move risk scores, but it isn’t a forecast for PACE.
When CMS began blending V28 into PACE risk score calculations alongside V22, many organizations naturally turned to their coding and compliance teams. Their assumption: update code sets, adjust query templates, and our coders will navigate the model shift.
But V28 puts pressure on operations far beyond the coding queue.
With valid diagnosis codes reduced from nearly 9,800 to 7,700, constrained disease hierarchy coefficients, and a mandatory transition to the Encounter Data System (EDS), the V28 burden can’t sit squarely on a coding team’s shoulders. If a provider doesn’t document their evaluation or management of the condition at a face-to-face encounter, there’s no clinical basis for a medical coder to build a submission. Even well-documented diagnoses can fall short of CMS requirements.
A diagnosis only counts toward reimbursement if it clears three separate checks:
- Does the documentation support the diagnosis?
- Does CMS accept the submission?
- Is the diagnosis eligible for risk adjustment reimbursement?
Often, these answers sit in separate systems or with different teams. When that’s the case, problems can go unnoticed until reconciliation. By then, the window to query a provider, correct a documentation gap, or address a submission issue may have passed.
Protecting reimbursement under V28 means running documentation, coding, and compliance as one connected risk adjustment process. This process starts with the moment a provider sits down with a participant.
Two places V28 performance can break down
As industry analyses like AAPC’s 2026 PACE Risk Adjustment e-brief emphasize, knowing the new rules is no longer the hard part. The challenge is making sure your workflows hold up where V28 puts the most pressure on them.
The table below pairs each breakdown with what IRIS, IntusCare’s risk adjustment platform for PACE, makes visible at each point.
Breakdown point | What goes wrong | What IRIS risk adjustment makes visible |
Point-of-care specificity | Specificity that isn’t documented at the visit can’t be added later. V28 flattens hierarchy weights, so providers need to document specific diagnostic nuances during care delivery. Compliant queries and timely addenda can clarify documentation that exists, but they can’t substitute for an assessment that never happened. | Suspect conditions are surfaced before annual and semi-annual assessments. Through pre-encounter preparation (PEP), these conditions are AI-surfaced and expert-validated, so providers can target them during the visit and are less likely to miss anything in their documentation.
|
Encounter Data System (EDS) transition | Encounters stall or are rejected by CMS, and conditions become ineligible. Moving from legacy RAPS to EDS brings stricter CMS data validation. Technical errors can cause an encounter to stall in the pipeline or be rejected by CMS, and missing provider linkages or unsupported encounter types can make conditions ineligible, which directly diminishes risk adjustment value.
| Submissions are tracked through the CMS lifecycle. IRIS flags stalled files, uncovers specific rejection reasons (EDPS errors), and identifies conditions CMS marks ineligible. |
These breakdowns don’t all carry the same kind of risk. A stalled submission can often be caught, investigated, and corrected before CMS deadlines close. Missing documentation is different. If the visit note doesn’t capture the specificity needed to support the diagnosis, no coding review, chart audit, or compliance process can add it afterward. The reimbursement opportunity may be lost before coding even begins.
What’s possible later starts at the point of care
Many PACE programs put their safety net after the visit, relying on internal coders or outsourced risk adjustment vendors to catch what point-of-care documentation didn’t capture. This review matters; it’s often the only chance to surface a condition before submission. But it has a fundamental limitation: coders can only work with what the clinical record contains. While they can connect a diagnosis buried in a specialist note or a prior encounter, they can’t create clinical specificity that was never documented at all.
A strong defense against this limit is pre-encounter preparation (PEP). By moving suspect-condition identification earlier, surfacing likely conditions from the existing record before the next assessment, providers know what to probe for and document specifically while they’re still in the room with the participant.
This shift in habits matters more under V28 than it did under V22, because the two models don’t ask the same thing of a chart note. Here’s how they differ.
What changed | V22 | V28 |
Valid diagnosis codes | Nearly 9,800 | 7,700: CMS removed 2,294 diagnosis codes, net of 268 additions |
Coefficients | Severity mattered. Congestive heart failure with complications carried a meaningfully higher coefficient | Several coefficients are constrained, so related conditions carry the same weight regardless of severity. Congestive heart failure now scores the same with or without complications. |
Documentation | Certain documented diagnoses could map to qualifying HCCs, even when the documentation was less specific. | The provider documents their evaluation or management of the condition during a face-to-face encounter. |
Submission | Legacy RAPS | Mandatory transition to EDS, with stricter CMS data validation |
But habits don’t update as fast as models do. Documentation that consistently produced accurate risk scores under V22 rules can leave meaningful risk adjustment factor (RAF) value uncaptured under V28.
A missing detail at the point of care can ripple through the entire risk adjustment process. Under V28, clinical specificity influences what coding can capture, what CMS will ultimately accept, and what finance eventually sees in risk-adjusted revenue.
The V28 impact: What MA confirms, and what it doesn’t
PACE is still early in the V28 blend, but Medicare Advantage already went through a comparable model shift, and researchers have estimated its effect on risk scores.
In a 2026 study published in Health Affairs Scholar, researchers applied the V28 model to 2021 Medicare Advantage (MA) data and compared the results with the previous V24 model. Scores varied substantially across the insurers, and a model revision alone was enough to move them.
What Medicare Advantage’s V28 experience shows
- 8% average decline in MA risk scores under V28, compared with the previous V24 model
- Nearly 18% drop in risk scores for some plans; some plans saw almost no change
- MA’s experience isn’t a forecast for PACE, which starts from a different model (V22) and has a different diagnosis mix.
Because PACE programs calculate risk scores using the same CMS-HCC methodology, the MA experience shows what kind of change is possible. But it’s not a direct forecast. The Health Affairs Scholar study measured MA’s V24-to-V28 transition. PACE is moving from the older V22 model straight to V28.
PACE organizations also carry a different diagnosis mix than the typical MA plan, and PACE leaders disagree on what the implications mean. Some expect PACE’s higher-acuity population to soften the impact relative to MA. Others point to PACE’s disproportionate share of conditions like depression, where only moderate or severe major depression still counts toward a risk score, and expect an impact similar or larger than what MA saw. Which effect dominates will vary by organization, which is precisely why MA’s percentage drop in risk scores won’t transfer to PACE.
A phased transition is no reason to wait
A phased V28 transition can make the work ahead feel gradual. It isn’t. The documentation, coding, and compliance adjustments V28 requires don’t arrive on a blend schedule the way the risk scores do, and the work doesn’t sit with one team.
Clinical teams need documentation practices that support accurate coding at the point of care. Coding and compliance teams need to validate the information being reported and monitor how data moves through the CMS process. Finance needs to understand how the resulting risk scores and diagnosis eligibility decisions affect the organization’s overall financial picture.
A clean handoff at one stage doesn’t guarantee the next one goes smoothly. A coder can close out a chart correctly and still have no idea a submission stalled in EDS two steps later. Catching problems like this early, and understanding why they happened, requires visibility into the whole risk adjustment cycle, not just the part your team owns.
The coding team was never going to carry V28 alone, and it shouldn’t have to. When every team can see how its work affects the others, from the encounter through reimbursement, the V28 burden is finally shared.
See how IRIS gives PACE leadership end-to-end visibility across the risk adjustment lifecycle.
Request a demo and talk with our team. For a related perspective on how PACE organizations can fine-tune their operations for better margin protection, read The Margin Window.
