Understanding CMS HCC V24 to V28: What It Means for Risk Adjustment Software Capabilities
As organizations adapt to the transition from CMS HCC V24 to V28, many are discovering that legacy tools no longer meet the demands of today’s risk adjustment requirements. V28 brings tighter coding criteria, condition exclusions, and a greater emphasis on clinical specificity—none of which can be efficiently addressed with outdated workflows or static platforms. This shift puts a new spotlight on the flexibility and intelligence of Risk Adjustment Software, which must now evolve to support smarter coding, better documentation alignment, and audit-readiness in real time.
What Changed from V24 to V28—and Why It Matters
1. Fewer Eligible HCCs:
V28 eliminates a significant number of previously valid codes due to their low predictive value. Conditions once contributing to risk scores have been removed, meaning that coders can no longer rely on historical coding patterns to secure the same RAF impact.
2. Reclassification of Condition Groups:
CMS has restructured condition categories for improved clinical coherence and alignment with cost predictability. The result is a hierarchy that mirrors clinical reality more closely but also introduces more complexity in coding decisions.
3. Greater Emphasis on Specificity:
Generic diagnoses such as “unspecified heart failure” or “diabetes without complications” are no longer sufficient. Clinical documentation must be precise and directly support the assigned code.
4. Increased Audit Visibility:
CMS continues to advance its oversight capabilities. With V28, the risks of over-coding and unsupported diagnoses triggering RADV or OIG audits are higher, requiring deeper scrutiny and evidence-backed documentation.
Together, these changes affect not just coders, but also how software systems must parse, suggest, and validate codes linked to revenue.
What Risk Adjustment Software Needs to Do in the V28 Era
1. Update HCC Logic and Hierarchies in Real Time
Software must be updated continuously to reflect the latest V28 HCC mappings. Hierarchical shifts mean older models can’t simply be patched—they need redesigned logic that prioritizes high-value conditions under the new schema.
2. Flag Gaps with Precision, Not Just Volume
Volume-based alerts have become noise. Effective platforms now prioritize suggestions by likelihood, relevance, and evidence strength. Systems should synthesize claims history, encounter data, and documented trends to suggest codes with clear justification—minimizing false positives that slow teams and increase compliance risk.
3. Support MEAT Criteria at the Point of Documentation
The MEAT (Monitoring, Evaluation, Assessment, Treatment) framework has become non-negotiable. Platforms must surface not just suspected conditions but their corresponding documentation evidence. If the EHR notes don’t meet MEAT, the software should flag the risk before it reaches submission.
4. Integrate Seamlessly with EHRs and CDI Workflows
CDI specialists and coders need these tools embedded in their day-to-day systems—not siloed in separate dashboards. Whether it’s through middleware, APIs, or native integration, suggestions and alerts should surface directly in the EHR environment.
5. Adapt to Organizational Policies and Value-Based Contracts
Different payers and contracts come with varying rules. Whether you’re a Medicare Advantage plan, MSSP ACO, or provider group, your software should be configurable enough to align with your benchmarks, logic rules, and audit strategies.
Real-World Impact: How V28 is Changing Operational Realities
HCC Recapture is Harder:
With broad categories gone, the bar for documentation and coding is higher. Systems must enable providers to capture chronic conditions accurately—ideally before or during the patient encounter.
Revenue Variability is Greater:
As conditions fall off the HCC list or lose value, RAF scores can drop unexpectedly. Real-time analytics are essential to spot trends and adjust strategies to maintain reimbursement integrity.
Compliance Risks Are Elevated:
Unsupported coding is more visible than ever. Tools that merely “suggest” codes without context or evidence are liabilities. Platforms must build defensible audit trails.
What to Look for When Evaluating or Updating Your Risk Adjustment Platform
- Dynamic HCC Mapping
Ensure your system reflects the latest CMS logic and doesn’t require manual updates or yearly overhauls. - AI or Rules-Based Suggestion with Provider Context
Look for platforms that learn from your documentation patterns and provider styles—not just static rule engines. - Integration Across Outpatient and Inpatient Workflows
Risk doesn’t only live in the primary care office. Your platform must track and code wherever care is delivered. - Audit Trail Transparency
Every code must be traceable—backed by MEAT evidence, encounter data, and user justification. This is your defense in a RADV audit.
Common Missteps That Undermine V28 Readiness
- Delaying Software Updates Until Denials Occur
Waiting for a drop in revenue before reacting can cost millions. Organizations need to proactively validate their systems against V28 benchmarks now. - Relying on V24 Reports for Benchmarking
Old data and models no longer provide a clear view of current performance. New tools must generate V28-aligned performance metrics. - Skipping Provider Training
No platform is effective if the users aren’t aligned with the logic behind the codes. Coders and providers need to understand what qualifies under V28 and why. - Assuming Automation Removes All Risk
Human-in-the-loop workflows remain essential. Even the best AI tools need review and governance to remain compliant.
Reframing the Transition as an Opportunity
The transition from CMS HCC V24 to V28 isn’t just about staying compliant—it’s a chance to modernize how risk is captured, coded, and protected across your organization. With the right Risk Adjustment Software, you don’t just follow the rules—you anticipate them, adapt quickly, and build a system that supports accuracy without adding complexity. Now is the time to upgrade not just your tools, but your entire approach to risk-based care.