CMS has posted the FY2027 ICD-10-CM diagnosis code files to its website, and the changes take effect October 1, 2026 — roughly 100 days from now. The update adds 238 new codes, revises four, and deletes 21. AAPC’s Revenue Cycle Insider reviewed the full update on June 17, 2026, flagging the clinical areas with the most meaningful coding impact. For medical coders, CDI specialists, and anyone managing HCC or oncology risk, the window to start preparing is now.
238 new codes sounds like a flood, but the real question is where the codes land. FY2027 is not a structural rewrite. It is a precision update — expanding existing categories into more specific options, splitting broad catch-all codes into distinct diagnoses, and adding long-overdue codes for conditions that have been under-captured for years. Each of those changes carries documentation implications that neither coders nor clinical staff can absorb on October 1 without advance preparation.
Why Annual Code Set Updates Still Catch Teams Off Guard
Most healthcare organizations know the October 1 deadline exists. Far fewer have a formal workflow for pre-updating CDI query templates, encoder rule sets, and coder training ahead of the effective date. The result is a consistent pattern: the new codes appear in the system, coders default to the legacy code they know, and specificity is lost for weeks or months before auditors catch it.
FY2027 compounds that risk in several specialty areas where the new codes carry HCC weight or oncology billing consequences. If the clinical record doesn’t capture the right level of detail before October 1, the new code may be unavailable to the coder even after the effective date — because the documentation does not support it.
Oncology and Hematology: Where Specificity Has the Most Leverage
Secondary Malignant Neoplasms Get More Anatomical Precision
The C78 and C79 categories — covering secondary malignant neoplasms of the respiratory, digestive, and other organ sites — are expanding with three new codes to pinpoint specific anatomical locations of metastatic disease. Under the current code set, coders often assign C78 or C79 codes with limited site specificity when the clinical record is ambiguous. Starting October 1, payers and auditors will expect greater specificity where the documentation supports it.
For oncology and inpatient coders, this means CDI queries for metastatic patients need to explicitly identify the anatomical site of secondary involvement. A documentation note that says “metastatic disease” without specifying the secondary site will not support the new codes.
Platelet Defect Codes Split Into Distinct Diagnoses
Currently, code D69.1 (Qualitative platelet defects) covers multiple conditions through inclusion terms, including Glanzmann thrombasthenia and Bernard-Soulier syndrome. FY2027 retires those inclusion terms and replaces them with two distinct codes: D69.11 for Glanzmann thrombasthenia specifically, and D69.19 for other qualitative platelet defects, which includes Bernard-Soulier (giant platelet) syndrome, grey platelet syndrome, and thrombocytopathy.
This is a high-specificity change that affects hematology and inpatient coders. After October 1, assigning D69.1 will be incorrect for either condition. CDI teams managing hematology encounters should update query templates now to ensure providers document the specific diagnosis rather than the generic umbrella term.
Cardiac Coding Gets More Granular
I42.0, Dilated cardiomyopathy, is one of the most frequently coded cardiac diagnoses in inpatient settings and carries HCC V28 risk weight for Medicare Advantage plans. FY2027 expands it into three distinct codes: I42.00 (dilated cardiomyopathy, unspecified), I42.01 (familial-genetic dilated cardiomyopathy), and I42.09 (other dilated cardiomyopathy).
The practical implication is significant for HCC coding teams. A patient with documented familial-genetic DCM can be coded with specificity that better reflects the clinical complexity of the case. But only if the cardiologist’s documentation actually uses that distinction. CDI programs that touch cardiology and heart failure encounters should add a DCM query field — familial vs. non-familial — to their standard workflows before September 30.
Other Notable Changes Across Specialties
The FY2027 update contains meaningful changes in several other areas that coders should flag before October 1:
- Postprocedural hypoglycemia gets new specificity with E89.83 as a parent code and two children: E89.830 for post bariatric hypoglycemia specifically, and E89.838 for other postprocedural hypoglycemia. This matters for bariatric surgery coding and any post-surgical encounter where blood sugar management is documented.
- Odontogenic sinusitis is finally addressable with specific codes under J34.83, with a 6th character to identify the affected sinus (maxillary, ethmoid, frontal, or sphenoid). ENT and oral surgery coders who have been using nonspecific sinusitis codes will need to capture sinus site from clinical documentation.
- Plantar fasciitis moves from M72.2 (Plantar fascial fibromatosis) to its own dedicated subcategory M67.A. Podiatry and musculoskeletal coders should verify their encoder updates this mapping on October 1.
- Ectopic pregnancy receives a significant expansion, with 56 new codes added across the O category to capture anatomical site and laterality with much greater precision. OB and ED coders managing ectopic pregnancy encounters will see the most direct workflow impact.
- Sex and gender Z codes are refined to add greater specificity in reporting, which affects health information management teams maintaining patient demographic coding standards.
What CDI Teams Need to Do Before October 1
Not all 238 new codes warrant the same urgency. The highest-priority areas for CDI preparation are the ones where specificity affects payment, HCC risk, or audit risk: oncology secondary neoplasms, dilated cardiomyopathy, platelet defect diagnoses, and ectopic pregnancy. Those areas should get updated query templates and provider education before the end of the summer.
For encoder and grouper users, verify with your vendor that the FY2027 code set will be active in your system on October 1 and that any crosswalk tables for split codes (like D69.1 into D69.11 and D69.19) are handled correctly. Some platforms update automatically; others require manual activation. Discovering that your encoder is still running FY2026 codes on October 2 is an avoidable problem.
It is also worth reviewing the carcinoma in situ of breast rules. FY2027 removes the ability to report codes from C50 and D05 together when a patient has both conditions — a change from current guidance. Oncology billing teams should confirm how their compliance workflows handle dual-condition documentation in breast cancer cases.
How Agentic AI Handles Annual Code Set Transitions
Annual ICD-10-CM transitions are one of the most fragile moments in the medical coding calendar. Manual workflows depend on coder awareness, encoder update timing, and CDI query template revisions — all of which can slip. When they do, the result is specificity lag: the right code exists, but the coding team doesn’t apply it consistently until weeks or months after the effective date.
Agentic AI coding platforms that stay synchronized with the active code set eliminate that lag. A system that ingests the FY2027 code set and applies it automatically from October 1 will surface I42.01 when a cardiology note documents familial-genetic dilated cardiomyopathy, flag D69.11 for Glanzmann thrombasthenia diagnoses, and route ectopic pregnancy cases to the correct O category code — without waiting for a human coder to check a crosswalk table. The coding precision of October 1 no longer depends on whether the coder got to the webinar.
With 100 days until the FY2027 code set goes live, organizations running autonomous coding workflows have a real advantage: they can validate AI output against the new codes in a test environment before the go-live date. Medikode’s automated medical coding platform is designed to stay current with CMS code set updates and apply the active code set accurately from the effective date — so your team’s first day with FY2027 codes looks like any other day, not a scramble.