FY 2026 ICD-10-CM Guidelines: What HCC Coders Should Recheck

Quick answer

The FY 2026 ICD-10-CM Official Guidelines are not just a code-book update. For HCC coders, they are a reminder to slow down at the exact points where risk adjustment errors usually start: the code path, billable status, Excludes notes, laterality, severity, combination-code logic, and documentation support.

Before you finalize an HCC-relevant ICD-10-CM code, check three things:

1. Does the ICD-10-CM code exist for the service date and is it reportable to the full required character length?

2. Does the Tabular List support the way you are using the code, including instructional notes and required additional codes?

3. Does the provider note support the diagnosis for risk adjustment, with current documentation and MEAT-style evidence?

Then, and only then, check the 2026 CMS-HCC mapping and RAF impact.

Start with the current code set

CMS publishes the FY 2026 ICD-10-CM files on its ICD-10 page, including code descriptions, addenda, tabular and index files, conversion tables, and the FY 2026 ICD-10-CM Official Guidelines. The FY 2026 diagnosis files apply by date range, so coders should verify that they are using the right code set for the encounter date.

That sounds basic, but it is where a lot of HCC cleanup starts. If a code changed, became invalid, needs another character, or has new instructional notes, the HCC mapping is not the first question. The first question is whether the ICD-10-CM code assignment is valid.

For production coding, this means:

Recheck the code path, not just the code you remember

The FY 2026 guidelines repeat a rule experienced coders already know: start in the Alphabetic Index, then verify in the Tabular List. Memory is useful, but memory can also lock you into last year's habits.

For HCC work, that matters because many diagnosis families have more than one plausible code path. Diabetes with complications, chronic kidney disease, heart failure, vascular disease, chronic respiratory failure, pressure ulcers, and substance use disorders all reward careful navigation. A one-click lookup can get you close. The Tabular List tells you whether the code is actually right.

When you land on a likely ICD-10-CM code, pause long enough to ask:

This is not about squeezing extra RAF from the chart. It is about assigning the ICD-10-CM code that the documentation actually supports.

Excludes notes still deserve a second look

HCC coders should treat Excludes notes as audit-risk signs, not footnotes. The FY 2026 guidelines define Excludes1 as a "not coded here" instruction and Excludes2 as "not included here." That difference affects whether two documented conditions can be reported together.

Practical coder translation:

This can affect HCC capture when one or both codes map to a payment HCC under V28. But the Excludes note does not create documentation. If the provider note does not support both conditions, the fact that two codes are allowed together does not make both reportable.

If you want a deeper refresher, HCC Buddy already has an Excludes1 vs Excludes2 guide. Use that together with the official FY 2026 files when a code pair looks risky.

Check specificity before checking RAF

The 2026 risk-adjustment workflow should start with ICD-10-CM accuracy and then move to HCC mapping. CMS lists the 2026 Model Software and ICD-10 Mappings, including initial and midyear/final mapping files. Those files tell you which ICD-10-CM codes map to CMS-HCC categories for the payment year.

They do not tell you whether the chart supports the code.

For HCC coders, the safe order is:

1. Confirm the diagnosis is documented by an acceptable provider for the encounter.

2. Confirm the code path and billable ICD-10-CM code.

3. Confirm specificity, laterality, acuity, stage, severity, and combination-code logic.

4. Confirm documentation support and MEAT-style evidence.

5. Check V28 HCC mapping and hierarchy impact.

6. Model the RAF effect only after the code is defensible.

That order keeps the work clean. RAF matters, but it is the last layer, not the starting point.

V28 makes unsupported specificity more visible

CMS says CY 2026 completes the phase-in of the 2024 CMS-HCC model for organizations other than PACE, with risk scores calculated using 100% of that model in the CY 2026 risk adjustment implementation memo. In coder shorthand, that means V28 is now the main CMS-HCC reality for non-PACE Medicare Advantage risk scores.

That does not change the ICD-10-CM guidelines, but it changes the consequences of weak code selection. V28 mapping is more specific in many areas. A familiar V24-era code may no longer map the way a coder expects, and a more specific code may only be available when the provider note clearly supports it.

This is why the FY 2026 guideline check and the V28 mapping check belong together. One answers, "Is this the right ICD-10-CM code?" The other answers, "Does this code map to an HCC under the current model?" You need both answers before treating the RAF impact as real.

Documentation pass: what the provider note has to carry

After the code and mapping checks, do one more pass through the provider note. HCC coding is not supported by the problem list alone. The note should show that the diagnosis is current and relevant to the encounter.

Use a simple MEAT-style review:

You do not need all four elements every time, but you do need enough documentation to defend that the condition was addressed. If you cannot point to the support in the note, do not let the HCC mapping talk you into the code.

A practical finalization checklist

Before submitting or accepting an HCC-relevant diagnosis code, ask:

If the answer is no, the next step is not to force the code. The next step is to query, clarify, or leave it out.

Where HCC Buddy fits

HCC Buddy is built for this exact recheck workflow. Use the ICD-10 encoder to look up the code path, billable status, HCC mapping, V24/V28 details, and related coding context. Use ICD-10 to HCC mapping when you need to verify whether a diagnosis maps under the current model. Use the RAF calculator only after the code is supported. Use the Evidence Checker and Smart Notes to tighten documentation review before the code becomes audit risk.

The goal is not to code more. The goal is to code what the note supports, with the current ICD-10-CM rules and current CMS-HCC mapping in view.