Elevance’s $342M Medicare Advantage Repayment: What HCC Coders Must Know

On May 27, 2026, Elevance Health wired $342,209,085.30 to the Centers for Medicare & Medicaid Services. The payment — disclosed in a June 22 court filing and reported by KFF Health News on June 26 — was described by the company itself as a “remittance of the total overpayment amount” estimated by government audits. For anyone working in Medicare Advantage coding, risk adjustment, or CDI, this is the most consequential enforcement action in years.

This was not a False Claims Act settlement driven by a whistleblower lawsuit. It was CMS using its enrollment authority to force repayment directly — and it worked. Legal and policy experts called it unprecedented. Medical coders and compliance teams should take it seriously.

What Happened and Why It Matters

The backstory starts in February 2026, when CMS issued an enforcement action threatening to bar Elevance from enrolling new Medicare Advantage members. The agency cited “substantial and persistent noncompliance” with federal regulations requiring plans to submit accurate billing data and return any overpayments when identified. Elevance, which covers approximately 2 million Medicare beneficiaries, challenged the action as unprecedented — and then paid the $342 million anyway.

Government auditors had estimated the overpayment from years of HCC coding submissions that CMS said were not supported by patient medical records. Elevance’s own April 2026 SEC filing placed the company’s “current best estimate” of total potential exposure at approximately $935 million — meaning the $342M payment may be only a partial resolution.

David Lipschutz, an attorney with the Center for Medicare Advocacy, put it plainly: “I’ve never heard of something like this before. Usually plans seem to tie everything up and try to delay any repayment of anything for years.” Matthew Fiedler of the Brookings Institution called the payment “not trivial” while noting it represents only a small fraction of Elevance’s total Medicare revenue — and that meaningful dent in industry-wide overpayments would require similar collections from every major MA insurer.

The HCC Coding Problem at the Core

Medicare Advantage plans are paid risk-adjusted rates through Hierarchical Condition Categories. The sicker a patient’s documented diagnoses, the higher the plan’s per-member payment. Plans have a strong financial incentive to ensure every valid HCC condition is coded — but that same incentive creates pressure to over-document or submit codes that aren’t adequately supported in the medical record.

CMS requires that MA plans bill only for conditions that are properly documented. When a diagnosis appears in a plan’s risk adjustment data but no supporting clinical documentation exists in the patient record, that code becomes an overpayment. At scale — across millions of members — small coding inconsistencies compound into nine-figure liabilities.

The Elevance case follows Kaiser Permanente’s January 2026 payment of $556 million to settle Justice Department allegations that it billed the government for medical conditions patients didn’t have. That remains the largest single penalty, but both cases reflect the same underlying problem: HCC coding that exceeds what the clinical documentation supports.

What This Means for Coders and CDI Teams

Whether you work for a Medicare Advantage plan, a health system contracting with MA payers, or a coding vendor touching risk adjustment submissions, the Elevance enforcement action sends a clear message about documentation specificity. Several immediate implications stand out:

• Documentation must support every submitted HCC. A diagnosis code in the problem list or a historical note is not sufficient if it isn’t clinically addressed and documented in the encounter record for the applicable date of service.
• Chart review programs are under greater scrutiny. Plans that conduct retrospective chart reviews to identify additional HCCs — without concurrent clinical confirmation — face the highest audit risk. CMS has proposed new restrictions on chart-review-only code additions for 2027 payment years.
• Deletion of unsupported codes is now expected, not optional. Federal regulations require plans to delete codes not supported by documentation when they are discovered. Failing to do so — and failing to return the resulting overpayment — is the core of the Elevance action.
• Specificity matters more than volume. Coders should focus on accurately and specifically documenting the conditions that exist, not capturing every possible HCC. An auditor asking “where is this condition addressed in today’s note?” must find a clear answer.
• AI-assisted coding tools need the same compliance guardrails. If a CAC or agentic AI tool suggests an HCC-relevant code, the coder reviewing that suggestion must verify clinical support before accepting it. The submission is what matters — not the source of the suggestion.

The Broader Enforcement Shift

CMS has known about MA overbilling for years. The agency’s own auditors have repeatedly found overpayments, but past enforcement collected only a fraction of what was identified. A 2014 proposed rule to crack down on overbilling was quietly shelved after industry opposition. For more than a decade, whistleblower lawsuits — not CMS itself — served as the primary recovery mechanism.

The February 2026 enforcement action against Elevance represents a different approach: using the agency’s enrollment authority as leverage. The threat of blocking new enrollments is an existential business risk for any MA plan. It appears to have produced a result that years of audit findings had not.

David Meyers, associate professor at Brown University School of Public Health, said the payment was “a step in the right direction” but added: “It remains to be seen whether this is a sea change.” Richard Kronick, a former federal health policy official and professor at UC San Diego, described it as “still a sizable check to write” — and noted it reflects “perhaps a bit of muscle flexing” by CMS to tighten enforcement.

Whether CMS pursues similar actions against other MA plans remains unknown. What is clear is that the agency now has a demonstrated model for applying pressure, and it worked.

Preparing Your Coding Program for This Environment

The Elevance case is a useful stress test for any organization’s risk adjustment coding program. The questions worth asking now are straightforward: Can you demonstrate that every submitted HCC is supported by a clinician-documented condition, addressed in the medical record, for the encounter date associated with the code? Do your deletion and correction workflows function correctly when unsupported codes are identified after submission? Are your chart review processes designed to confirm what’s already in the record — or to generate new codes retrospectively?

If the answers are uncertain, the current enforcement climate makes that uncertainty more expensive than it used to be.

Automation can help — both with surfacing supporting documentation at the point of coding and with flagging codes that lack the clinical specificity CMS requires. Medikode’s automated medical coding platform is built to support accurate, audit-ready HCC coding — ensuring that every code submitted reflects what’s actually in the clinical record, not what the payment model rewards.