On October 1, 2026, the FY2027 ICD-10-CM update takes effect for all discharges and encounters from that date forward. By the numbers, it is a quieter year: 190 new reportable diagnosis codes, 30 formerly reportable codes deleted, and four revised code titles, compared with 487 new codes in FY2026.
Quiet is not the same as low-risk. Smaller updates concentrate their impact in deletions and restructured code families, and those are the changes that break claims. A new code you never use costs you nothing. A deleted code that still sits in a charge template, a payer policy, or a favorites list generates denials from day one.
The complete files, including the conversion table and addendum, are posted on the CMS ICD-10 page and the CDC/NCHS ICD-10-CM files page.
Most of this year's risk sits in one pattern: previously billable codes demoted to non-billable category headers. Dilated cardiomyopathy is the clearest example. On October 1 it stops being reportable, and every workflow that still produces it, from charge templates to CAC suggestions to payer medical policies, produces a rejected claim instead.
Nothing looks wrong in September. In October, claims built on deleted codes start returning, and by the time the pattern shows up in a denials report, weeks of rework have already accumulated.
Early analyses of the FY2027 Official Guidelines indicate a light year: one entirely new guideline (family history of diethylstilbestrol exposure) and a small number of reworded guidelines, including refinements around hypertension and genetic conditions in the congenital anomaly chapter. Review the final published guidelines directly rather than relying on summaries, since the official CM guidelines file posted later than the code files this cycle.
For organizations coding manually, an annual update is a training event: every coder must learn the changes, and consistency arrives gradually, with an audit cycle to confirm it. An AI-powered autonomous coding solution absorbs the update differently. At Nym, our engine is updated with the new code set and guidelines once, centrally, and applied the same way to each chart the solution codes from the effective date. Each code assignment is also traceable to the documentation and rule that produced it. The update still demands the organizational work above, but the variability of a few hundred people internalizing change at different speeds comes off the list.
That difference is easy to verify. Ask any vendor, Nym included, to show exactly how and when the FY2027 changes enter production, and how you would audit the first week of October's output.
Learn more about how Nym's engine handles coding updates.