Why Does I42.0 Still Appear in the FY2027 ICD-10-CM Order File?

In the official FY2027 code-description ZIP, icd10cm-codes-2027.txt includes I4200 Dilated cardiomyopathy, unspecified but no complete-code row for I420. The separate icd10cm-order-2027.txt includes I420 0 Dilated cardiomyopathy and I4200 1 Dilated cardiomyopathy, unspecified. We checked the publisher's ZIP on October 29, 2026. The 0 and 1 values distinguish an ordering heading from a complete code in that file; they are not quality or payment scores.

Open the FY2027 I42.0 hierarchy page and its I42.00 child page to see how a versioned reference presents the parent and child. The CDC/NCHS release listing remains the authoritative entry point for the official file set.

The code-list addendum inside the FY2027 descriptions ZIP records Delete: I420 Dilated cardiomyopathy and Add: I4200 Dilated cardiomyopathy, unspecified. The order-file addendum tells a more detailed structural story: it deletes the old 1 I420 complete-code row, adds 0 I420 as a heading, and adds 1 I4200 as a complete code. The two addenda are consistent once their file populations are kept separate.

“Deleted” in the complete-code change list does not mean the characters can never appear anywhere in the released data. It means the old complete-code row changed status in the FY2027 structure. The Tabular/Index addenda package and full released Tabular List provide further context when the exact hierarchy and instructions matter.

The FY2026 April Tabular XML contains an I42.0 entry titled “Dilated cardiomyopathy.” FY2027 began October 1, 2026 and is scheduled through September 30, 2027, subject to later official updates. A saved FY2026 link or exported complete-code list therefore cannot be assumed to describe the FY2027 structure. Check the date and release before interpreting a missing row or a new child entry.

This structural example does not establish that I42.00 is the right choice for a record. It also does not summarize every child of I42.0 or every instruction in that hierarchy. The October 1 boundary guide explains how to keep the release period visible during a comparison.

1. Identify which member of the official ZIP an exported row came from: codes, order, or addenda.
2. Check the exact code without the display decimal: I420 versus I4200.
3. Preserve the complete-code flag if parsing the order file. Never infer it from character length alone.
4. Compare the release date and the current full Tabular hierarchy before treating a missing codes-file row as an error.
5. Document the source URL, member name and retrieval date with any derived dataset.

For format choices, read the FY2027 TXT-to-CSV guide. For the meaning and limits of the complete-code label, see the billable and unspecified guide.

A file-format check can tell you that I42.0 is a heading and I42.00 is a complete FY2027 code. It cannot choose among the current descendants, interpret a clinical note, establish sequencing, or predict reimbursement. A qualified reviewer must use the documentation, the complete FY2027 classification, and official FY2027 coding guidelines for an actual record. Our example is deliberately limited to a verifiable release-file question.