Full V28 Implementation: Operational Strategies for Post-Transition Risk Adjustment

The phase-in period for the CMS-HCC V28 risk adjustment model has concluded, marking a complete shift to a model designed to curb coding inflation, align diagnostic severity, and reflect modern clinical practices. For Medicare Advantage (MA) health plans and risk-bearing provider organizations, navigating V28 is no longer a matter of future preparation—it is the operational reality driving current risk adjustment factor (RAF) scores and financial projections.

Transitioning from V24 to V28 brought sweeping changes: over 2,000 diagnosis codes were removed from payment mapping, coefficient weights across several major disease categories were reduced, and diagnostic categories were restructured.

To maintain financial accuracy and clinical fidelity under full V28 implementation, organizations must evolve beyond traditional retrospective coding sweeps and focus on prospective clinical documentation, specificity, and care team alignment.

1. Navigating the Structural Realities of V28

The transition to V28 introduced key changes that redefine how clinical documentation translates into risk capture:

• Elimination of Non-Specific Codes: High-volume codes without specific clinical indicators—such as unspecified diabetes or general vascular disease—no longer map to payment Hierarchical Condition Categories (HCCs).

  
  

• Restructuring of Key Categories: Major clinical domains, including Cardiovascular Disease, Diabetes, and Psychiatry, underwent significant category consolidation and weight adjustments.

  
  

• Focus on Severe Manifestations: Under V28, payment mapping heavily favors severe, secondary, or complicated manifestations of conditions over uncomplicated diagnoses.

  
  

Area of Impact	V24 Baseline Pattern	Full V28 Operational Reality	Actionable Mitigation Strategy
Depression & Behavioral Health	Unspecified depression mapped to HCC 58	Removed from payment mapping unless documented with severity (e.g., major depressive disorder, severe)	Implement structured EHR screening tools to capture severity and episode status at point of care
Vascular & Cardiac Disease	Broad inclusion of peripheral vascular disease (PVD) codes	Excludes generic PVD codes; requires specific documentation of severe manifestations	Train clinicians on documenting specific arterial disease stages and associated complications
Diabetes Complications	Unspecified diabetes with secondary manifestations mapped easily	Requires explicit causal linkages between diabetes and end-organ manifestations	Deploy EHR templates that prompt clinicians to document direct causality (e.g., "diabetic nephropathy" vs. separate entries)

2. Transitioning from Retrospective Sweeps to Prospective Precision

Historically, many health plans relied heavily on post-encounter retrospective chart reviews to capture missing diagnoses. Under V28, this strategy yields diminishing returns because general, unspecific codes captured historically no longer yield payment mapping.

Key Shift: Pre-Encounter Preparation

• Actionable Suspecting: Leverage historical lab values, prescription data, and specialist notes to highlight suspected severe conditions before the patient enters the exam room.

  
  

• Point-of-Care Insights: Deliver targeted alerts within the EHR workflow, prompting the clinician to evaluate specific manifestations rather than submitting generic diagnosis codes.

  
  

Key Shift: Concurrent Clinical Documentation Improvement (CDI)

• Real-Time Queries: Establish CDI support during or immediately following patient encounters to resolve ambiguous documentation before claim submission.

  
  

• Clinical Accuracy Over Volume: Focus CDI efforts on validating diagnostic specificity and supporting documentation rather than volume-driven code expansion.

  
  

3. Optimizing EHR Workflows and Clinical Templates

Clinical documentation improvement relies on the tools clinicians use daily. Updating EHR templates and order sets ensures documentation satisfies V28 mapping requirements without increasing provider burden.

[Patient Encounter]
       │
       ▼
[Point-of-Care EHR Alert: Suspected Condition]
       │
       ▼
[Clinician Evaluation & Specific Diagnosis Entry]
  ├── Document Specificity (e.g., Severity, Manifestation)
  └── Establish Causality (e.g., "due to", "manifested by")
       │
       ▼
[Concurrent CDI Review / Validation]
       │
       ▼
[Clean Claim Submission under V28 Rules]

• Replace Dropdown Menus with Specificity Decision Trees: Ensure diagnosis search tools prioritize specific clinical terms (e.g., "Major Depressive Disorder, Recurrent, Moderate") over general terms ("Depression").

  
  

• Embed Causality Prompts: Configure clinical templates to prompt for causal relationships when documenting chronic conditions alongside organ dysfunction (e.g., linking chronic kidney disease stage to hypertension or diabetes).

  
  

• Audit Active Problem Lists: Conduct ongoing hygiene of EHR active problem lists to prune outdated, non-mapping, or duplicate diagnosis codes that create confusion.

  
  

4. Provider Engagement: Education Grounded in Clinical Fidelity

Provider burnout remains a primary challenge in risk adjustment efforts. Frameworks that frame V28 documentation requirements as administrative burdens often face resistance. Success depends on framing specificity as clinical accuracy.

1. Focus on Quality of Care: Accurate documentation under V28 reflects the true acuity of the patient population, directly impacting care management resources and risk-stratified care plans.

   
   

2. Provide Specialty-Specific Feedback: Share documentation performance metrics tailored to specific specialties (e.g., Cardiology, Endocrinology, Primary Care) rather than high-level health plan averages.

   
   

3. Streamline the Administrative Burden: Ensure that any documentation tool or alert added to the clinical workflow replaces an existing manual task, maintaining net neutral administrative effort for providers.