Choose the FY2027 file from the question: use the Index to locate a term, the Tabular List to verify its complete context, the guidelines to check general rules, the addenda to find release changes, and code descriptions for labels or data work. A label or change line alone cannot establish a current code assignment.
Which file answers the question in front of you?
Start with the purpose of the lookup. If you have a documented diagnostic term, open the FY2027 Alphabetic Index and then verify the result in the Tabular List. If you need the current hierarchy and its notes, start in the Tabular List. For a general convention or setting rule, open the FY2027 Official Guidelines alongside the classification. For what changed from the previous release, consult the addenda and then the complete released entry. For a short or long title in a data file, use the code descriptions, but return to the Tabular List before drawing a coding conclusion.
This map is for the U.S. ICD-10-CM diagnosis classification, FY2027. The CDC/NCHS release page identifies October 1, 2026 through September 30, 2027 as the applicable period for the October FY2027 release, subject to any later official update. The date, setting and classification belong on a saved source note. Our date-boundary guide explains why “2027” does not mean calendar-year 2027.
A question-to-file map for the FY2027 release
The official CDC/NCHS FY2027 folder groups several different diagnosis files. They are companions, not interchangeable copies of one answer. The CMS ICD-10 files page also lists FY2027 ICD-10-CM files under a separate heading from ICD-10-PCS procedure files.
| Your question | Open first | Confirm before relying on it |
|---|---|---|
| Where is a documented diagnosis term indexed? | Alphabetic Index in the FY2027 Table and Index package | Follow the Index directions; inspect the complete Tabular entry and applicable parent notes. |
| What is the current code hierarchy or instruction? | Tabular List in that same full package | Read chapter, block and category context as applicable, not only the leaf title. |
| What general rule applies to this lookup? | FY2027 Official Guidelines | Read the relevant section with the Index and Tabular conventions and the setting in view. |
| What was added, deleted or revised? | FY2027 addenda | Match the changed line to its complete current entry and note the release date. |
| What is a code’s short or long label in a file? | FY2027 code descriptions | Use the full Tabular List for instructions and hierarchy; a label is not a coding rule. |
The versioned FY2027 source library is a convenient starting point when switching between files. It does not replace the official release documents linked above.
Once you know which FY2027 file answers your question, the next choice is how to use it. Our CDC Browser versus named-download guide explains when interactive navigation helps and when retaining the exact released package helps a later review. Either way, follow the FY2027 Index-to-Tabular verification rule in I.B.1 before relying on a candidate entry.
Why do the Index and Tabular List travel together?
The FY2027 Official Guidelines, section I.B.1, directs readers to locate a code in the Alphabetic Index and verify it in the Tabular List. The Index is the route from a documented term; its entry may point to a category or require following a cross-reference. The Tabular List supplies the hierarchy and instructions that a search result or isolated Index line cannot show. The guidelines introduce both components in section I.A.1 and explain that the classification’s conventions and instructions take precedence over guideline text.
For instance, a broad parent heading can carry a note that applies below it. A title in a code-description file does not show that relationship. Start with the FY2027 Alphabetic Index, then inspect the relevant versioned Tabular path; our Index-to-Tabular guide describes the method, and the parent-note guide explains what may be missed by reading only a leaf page. This is a source trail, not a suggestion to select any particular diagnosis code.
Why are the addenda and descriptions separate?
The addenda answer a difference question: what changed in the FY2027 release. A change line often names a parent or a fragment of an instruction. It does not show every current neighboring note. After finding a line, open the full released Tabular List or Index and verify where it landed. Our addenda checklist covers that comparison in detail. The Chapter 1 note example shows why the change type and full chapter context matter.
The code-description package serves a different job. It is useful for a title lookup, a data import or checking whether a displayed label matches the released file. It does not reproduce all inclusion, exclusion, sequencing and parent instructions. A title can remain familiar while the surrounding instructions change. When a question is about an actual code choice, return to the Index, Tabular List and applicable guidelines instead of promoting a description row into an authority it does not carry.
Check the classification and release before opening a file
Record the exact source name, FY2027 release and date used in the question. The official file pages may gain later updates, so a claim about a newer correction needs its own dated source. Do not treat a download timestamp, filename alone or a search snippet as proof that an update applies to a particular service. The CDC/NCHS files page and CMS page are the checkpoints for newly posted official files.
Keep a short, reviewable source trail
A practical note can fit on one line: question → first official FY2027 file → complete Index and Tabular context where relevant → applicable guideline → date and classification. For a change question, insert the addendum before the full entry. For a label question, record that the description file established the label only. This gives another reader enough context to repeat the check without implying that the article decided a real chart.
If you use ICD Code Hub on several devices, a versioned reference link helps retain the FY2027 label. The Android, iPhone and Mac apps provide access to available reference pages, while the CDC/NCHS release and official guidelines remain the primary sources for this guide. Patient-specific or specialty coding decisions require the complete record and qualified human review.
Common questions
Can the FY2027 code-description file settle a diagnosis code choice?
No. The description file supplies labels, while the full FY2027 Tabular List and Index contain the hierarchy and directions to verify. Guideline I.B.1 directs readers to use both the Index and Tabular List.
Which official file tells me what changed for FY2027?
Start with the CDC/NCHS FY2027 addenda for additions, deletions and revisions. Then inspect the affected entry in the complete released Table and Index package; a change line does not show all current context.
Is an Alphabetic Index result the final code?
No. The Index directs the lookup, and the official FY2027 guideline I.B.1 says to verify the code in the Tabular List. Read applicable parent instructions as well as the leaf entry.
Do the FY2027 guidelines override a Tabular convention?
No. The FY2027 Official Guidelines say that the classification’s conventions and instructions in the Tabular List and Alphabetic Index take precedence over guideline text. Read the relevant guideline with those entries, not in isolation.
Sources & editorial notes
- CDC/NCHS: FY2027 ICD-10-CM release dates and files
- CDC/NCHS: official FY2027 diagnosis file folder
- CDC/NCHS: FY2027 Table and Index package
- CDC/NCHS: FY2027 code descriptions
- CDC/NCHS: FY2027 addenda
- CMS/NCHS: FY2027 Official Guidelines, sections I.A and I.B.1
- CMS: classification-specific FY2027 ICD-10 files
Scope: U.S. FY2027 ICD-10-CM diagnosis source navigation, October 1, 2026–September 30, 2027, subject to later official updates; not a patient-specific code assignment. Educational reference content, prepared with AI assistance; not independently reviewed by a credentialed clinical coding specialist. Verify official instructions and the applicable documentation before assigning codes. Our editorial approach.
Found an error? Send a correction.



