CMS Just Cut Unlinked Chart Reviews Out of 2027 Risk Scores. What HCC Coders Should Do Next.

Quick Answer

CMS finalized a 2027 payment policy that excludes diagnoses from unlinked chart review records from risk score calculation in most cases. That means diagnoses found through retrospective chart mining, without a specific beneficiary encounter tied to them, will no longer drive Medicare Advantage risk scores the way many organizations have relied on in recent years.

This is not a minor technical tweak. It is a loud policy signal. CMS is telling plans, vendors, compliance teams, and coders that the future of risk adjustment is encounter-based, documentation-supported, and less dependent on retrospective chart review lift.

Source: CMS April 6, 2026 press release.

The One Sentence Everyone In MA Should Understand

Starting in CY 2027, diagnoses that are not associated with a service will not be considered for risk adjustment, except in the limited scenario CMS described for beneficiaries who switch from one Medicare Advantage organization to another.

CMS states this directly in the April 6, 2026 rate-announcement release. The agency also said it expects the payment impact to be greater for MA organizations that heavily rely on unlinked chart review records to report risk-adjustment-eligible diagnoses.

That is the line that should get every coding manager's attention.

Why This Matters More Than The Average Rate Story

Most coders hear "rate announcement" and assume it is mostly plan-finance news. But this rate announcement included something far more operational for HCC teams:

In plain language, this means plans can no longer assume retrospective chart review will rescue weak point-of-care capture. The encounter itself matters more. The provider note matters more. The coder's ability to identify documentation gaps before submission matters more.

What HCC Coders Should Do Right Now

If you code, audit, or manage risk-adjustment workflows, this is the moment to shift from retrospective comfort to encounter-first discipline.

Start here:

1. Review problem-list-only diagnoses. If the condition appears on the problem list but not in the encounter assessment, treat it as a support risk.

2. Audit recaptured HCCs with weak current-year support. Chronic conditions that used to survive on chart-review cleanup deserve a stricter second look.

3. Push specificity at the encounter, not after it. V28 already raised the cost of vague coding. This policy raises the cost of late coding.

4. Strengthen compliant provider-query workflows. Queries are more valuable when they fix the current encounter, not when they patch old revenue gaps.

5. Separate mapped diagnoses from defensible diagnoses. A code can map to an HCC and still fail if the encounter does not support it.

This is where the workflow should tighten:

The Workflows That Just Got Riskier

Three workflows deserve immediate scrutiny.

1. Retrospective chart mining without encounter support

If the diagnosis was found later in the chart but not clearly tied to a face-to-face encounter, the business value of that workflow just changed materially.

2. Query strategies that chase revenue instead of documentation clarity

Provider queries should clarify what the chart supports. They should not function as retroactive diagnosis extraction. If your query culture drifts toward "find another HCC," this policy makes that drift more dangerous.

For compliant examples, review provider query templates.

3. Teams that treat chart review as a safety net for weak encounter capture

That safety net is getting smaller. The stronger long-term investment is better point-of-care documentation, stronger MEAT review habits, and cleaner coder workflows inside the encounter window.

What Teams Should Build Instead

The winning posture now is not panic. It is operational maturity.

The teams that handle this best will:

That is exactly why the SOE and evidence-checker workflow matters. It is not just another feature. It is the tool posture that matches where CMS is pushing the market.

The Bigger Shift

Read the April 6 release closely and the pattern is clear. CMS is trying to align payment more closely to documented beneficiary care and less closely to coding lift that happens outside the encounter. That trend also lines up with ongoing RADV pressure and the broader compliance environment.

So if you want the practical takeaway:

The future is not "code harder after the visit." The future is "document and validate better during the workflow."

The HCC teams that adapt to that now will be in much better shape than the teams still depending on retrospective cleanup to hold their numbers together.