Evolving CMS Expectations

A RADV audit compliance program is the standing organizational infrastructure — encompassing governance, documentation standards, provider education, internal monitoring, and technology systems — that Medicare Advantage plans maintain year-round to ensure risk adjustment submissions are accurate, defensible, and aligned with CMS requirements before an audit notification is ever received.

CMS has progressively raised the bar on what constitutes an acceptable RADV compliance program. The agency's expectations for payment year 2027 reflect lessons learned from a decade of RADV audits, OIG investigations, and the finalization of extrapolation methodology that amplifies the financial consequences of every unsupported diagnosis.

Historically, many Medicare Advantage plans treated RADV compliance as a reactive exercise — conduct chart reviews when CMS sends a data request, assemble documentation, and respond within the audit timeline. That approach is no longer viable. CMS now evaluates whether plans have standing compliance infrastructure that operates continuously, not just during audit response periods.

The shift is driven by several factors. First, CMS has finalized RADV payment recovery with extrapolation for payment years 2018 forward, meaning audit findings from a sample of 200 beneficiaries can generate payment recoveries extrapolated across the entire contract population. Second, OIG audits have consistently found that plans with weak compliance programs have higher error rates. Third, CMS is investing in data analytics that identify coding anomalies across the MA program before selecting audit targets.

Extrapolation Impact

Under extrapolation, a 10% unsupported diagnosis rate in a 200-member audit sample can generate payment recoveries of $10-50 million when extrapolated across a 100,000-member contract. The financial case for proactive compliance has never been stronger.

Compliance as Defense

Plans that demonstrate robust, continuous compliance programs may receive more favorable treatment in audit dispute resolution. CMS views proactive self-correction as evidence of good faith that factors into enforcement decisions.

New Compliance Requirements for 2027

Building on the foundational elements of a RADV-ready compliance program, CMS has raised expectations for payment year 2027 in several specific areas.

  • Proactive Self-Audit Requirements: Plans must conduct ongoing internal audits using statistically valid sampling methodologies. CMS expects quarterly audit cycles — not annual point-in-time reviews. Sampling must cover all contract segments, provider types, and HCC categories with sufficient volume to detect error patterns.
  • Pre-Submission Diagnosis Validation: CMS now expects plans to scrub diagnoses before submission rather than correcting errors after the fact. Pre-submission validation should verify that every diagnosis code has a supporting encounter from a qualified provider with documentation that meets RADV standards.
  • Delegated Entity Oversight: Plans that delegate risk adjustment activities to third-party vendors, provider groups, or coding companies must demonstrate oversight of those entities' compliance. Delegation does not transfer compliance responsibility. CMS holds the MA organization accountable regardless of who performs the coding or chart review.
  • Error Rate Benchmarking: Plans should establish internal error rate thresholds and take corrective action when those thresholds are exceeded. CMS views plans that cannot articulate their own error rates as deficient in compliance monitoring.
  • Documentation Retention Standards: Medical records supporting risk adjustment diagnoses must be retrievable within 30 days of a CMS data request. Plans must maintain documentation retrieval processes that can scale to full RADV audit volume without degradation.

Program Structure and Governance

CMS expects RADV compliance programs to have clear organizational structure, defined accountability, and board-level visibility. A compliance program that exists only in policy documents without operational governance is insufficient.

  • Compliance Officer: A designated individual with authority and resources to manage the RADV compliance program. This role must have direct reporting access to the board or a board-level compliance committee. The compliance officer should not report exclusively through operations or finance chains that create potential conflicts.
  • Cross-Functional Governance Committee: RADV compliance requires coordination across coding, clinical operations, data management, legal, and finance. A standing governance committee with representatives from each function should meet at least monthly to review compliance metrics, address emerging issues, and approve corrective actions.
  • Board Reporting: The board of directors must receive regular updates on RADV compliance status, including audit readiness assessments, internal error rates, corrective action plans, and financial exposure estimates. CMS views board awareness as an indicator of organizational commitment to risk adjustment integrity.
  • Policy Documentation: Written policies and procedures must cover every aspect of the risk adjustment data submission process — from provider documentation requirements through coding standards, submission protocols, and audit response procedures. Policies must be reviewed and updated annually.
  • Training Programs: All staff involved in risk adjustment activities must receive annual compliance training. This includes providers, coders, chart reviewers, data analysts, and submission specialists. Training should cover current CMS guidance, common error patterns, and the consequences of non-compliance.
Free Resources

Three downloads risk adjustment teams actually use

Checklists, playbooks, and frameworks — built for analysts, auditors, and VPs working RAF, RADV, and HCC.

Checklist

2026 RADV Audit Readiness Checklist

12-point compliance checklist for documentation, diagnosis code validation, extrapolation defense, and pre-audit scrub workflows.

Playbook

RAF Score Optimization Playbook

Tactical guide for analysts: HCC recapture workflows, V28 transition impacts, prospective gap-closure plays, and KPIs that move RAF lift.

Playbook

Risk Adjustment Analytics Playbook

How payer leaders sequence prospective and retrospective risk adjustment for compounding RAF lift. Deployment patterns, KPIs, and a VP-level operating rhythm.

Build Your 2027 Compliance Foundation: Our RADV Scrubber provides the continuous validation and audit-readiness monitoring that CMS expects from compliant MA plans. See the RADV Scrubber →

Documentation Standards

The documentation standard for RADV is straightforward in principle but demanding in practice: every diagnosis code submitted for risk adjustment must be supported by the medical record from a face-to-face encounter with a qualified provider during the applicable dates of service. Meeting this standard consistently across millions of encounters requires systematic processes.

  • Face-to-Face Requirement: Only diagnoses from encounters where the provider directly examined or treated the patient qualify. Telephone calls, patient portal messages, and administrative reviews do not satisfy the face-to-face standard for HCC-supporting diagnoses.
  • Provider Qualification: The documenting provider must be a physician (MD/DO), physician assistant, nurse practitioner, or clinical nurse specialist operating within their scope of practice. Diagnoses documented solely by clinical staff without qualifying credentials are not RADV-defensible.
  • Clinical Specificity: Documentation must support the specific ICD-10 code submitted. A note that references "kidney disease" without staging information does not support a stage-specific CKD code. The coding must match the documentation exactly — no inference, no assumption.
  • Active Assessment Evidence: CMS auditors look for evidence that the condition was actively assessed, not merely listed. The MEAT criteria (Monitor, Evaluate, Assess, Treat) provide a framework for demonstrating active management of each reported condition.
  • Legibility and Completeness: Records must be legible, dated, signed by the treating provider, and include the patient's name and date of birth. Incomplete or illegible records are treated as non-supportive during RADV review, regardless of the clinical reality.

Monitoring and Reporting

Continuous monitoring is the operational backbone of a 2027-ready RADV compliance program. CMS no longer views annual retrospective reviews as sufficient — plans must demonstrate real-time or near-real-time awareness of their risk adjustment data quality.

  • Provider Coding Pattern Analysis: Monitor individual provider coding profiles for outliers — providers whose HCC capture rates, diagnosis specificity, or condition frequency distributions deviate significantly from peers. Outlier patterns may indicate either under-documentation or overcoding, both of which require investigation.
  • Diagnosis Frequency Monitoring: Track the frequency of specific HCC codes relative to historical baselines and industry benchmarks. Sudden increases in high-value HCCs without corresponding changes in patient population demographics warrant immediate review.
  • Chart Review Pass Rates: Measure the percentage of sampled diagnoses that survive internal chart review. Plans should target 90% or higher pass rates. Pass rates below 85% indicate systemic documentation or coding issues requiring corrective action.
  • Deletion and Correction Tracking: Monitor the volume and pattern of diagnosis deletions and corrections. A high correction rate may indicate that the initial submission process has quality gaps. CMS views proactive self-correction favorably, but persistent high correction rates suggest upstream process failures.
  • Financial Exposure Estimation: Maintain ongoing estimates of RADV financial exposure based on internal error rates and current extrapolation methodology. This enables the organization to prioritize compliance investments based on financial risk.

Technology Requirements

Manual compliance processes cannot scale to meet 2027 RADV expectations for plans with significant Medicare Advantage enrollment. CMS increasingly evaluates whether plans have invested in technology infrastructure that enables systematic, repeatable compliance operations.

  • Automated Pre-Submission Scrubbing: Technology that validates diagnosis codes against encounter data, provider credentials, and documentation availability before CMS submission. Automated scrubbing catches errors that manual review processes miss at scale.
  • Chart Retrieval and Management: Platforms that manage chart request workflows, track retrieval status, maintain document repositories, and support reviewer workflows. Plans auditing hundreds of thousands of encounters need technology to manage the operational complexity.
  • Analytics and Dashboarding: Real-time dashboards displaying compliance metrics — error rates, provider outliers, HCC distribution patterns, and audit readiness scores. Decision-makers need visibility without waiting for quarterly report cycles.
  • Audit Trail and Documentation: Every compliance action — reviews performed, corrections made, training delivered, policies updated — must be documented with timestamps, responsible parties, and outcomes. Complete audit trails demonstrate compliance program maturity to CMS.
  • Integration with Risk Adjustment Platforms: Compliance technology should integrate with the organization's risk adjustment analytics platform and submission systems. Siloed compliance tools that operate independently of the risk adjustment data pipeline create gaps that CMS audits exploit.

The technology investment required is significant, but the alternative — manual processes that cannot keep pace with RADV expectations and extrapolated payment recoveries — carries far greater financial risk.

Key Insight: RADV compliance in 2027 is not about passing audits — it is about building an organizational capability that ensures risk adjustment data integrity as a continuous operating standard. Plans that treat compliance as a program rather than a project will protect revenue, reduce audit exposure, and demonstrate the institutional maturity that CMS increasingly demands.

Ready to Meet 2027 Compliance Standards?

See how our RADV audit scrubber platform helps plans validate diagnoses pre-submission, monitor compliance metrics in real time, and build audit-defensible risk adjustment programs.

Schedule a Demo