The key point

The FY2027 guidelines say bold marks narrative changes, underline marks material moved since the April 2026 FY2026 edition, and italics mark revised headings. None of those marks alone proves that an ICD-10-CM code was added. Read the whole current section, compare the prior edition, and check the separate official code files or addenda for code changes.

The short answer: bold flags guideline prose, not a new code

No. On the title page of the FY2027 ICD-10-CM Official Guidelines for Coding and Reporting, CMS and NCHS explain that bold text identifies narrative changes. Underlining identifies items moved within the guidelines since the April 2026 FY2026 version; italics identify revisions to headings. These are reading marks in the guideline document. A bold sentence does not, by itself, show that a diagnosis code was added, removed or retitled.

This article answers a document-review question: how to notice a changed FY2027 guideline section and verify its meaning. The separate FY2027 addenda checklist explains how to review changes to the classification files. For a code lookup, the full FY2027 reference and official source files still govern the entry.

Source: CMS/NCHS: FY2027 ICD-10-CM Official Guidelines, title page and introduction

Read the three marks before comparing editions

The document itself supplies the key. Start there rather than guessing from typography or a search result:

Mark in the FY2027 guideline PDFWhat its title page saysWhat it does not prove alone
Bold narrative textNarrative wording changedThat a new ICD-10-CM code exists
Underlined itemMaterial moved within the guidelines since the April 2026 FY2026 versionThat the moved rule is newly created or substantively different
Italic headingA revision to heading wordingThat the instruction beneath it changed in the same way

The underlining note names a specific comparison baseline: the April 2026 FY2026 guidelines. A moved paragraph still needs a content comparison; placement alone is not a safe measure of changed meaning. Conversely, a small bold clause can affect how a section is read, so do not dismiss it simply because it is short.

Source: CDC/NCHS: April 2026 FY2026 Official Guidelines

Set the right editions and dates before you compare

The FY2027 guideline cover says “updated October 1, 2026” and gives the period October 1, 2026–September 30, 2027. CDC/NCHS confirms that FY2027 ICD-10-CM codes apply to healthcare services in that period, replacing the April 2026 FY2026 release. For work tied to September 2026, use the applicable FY2026 material; the fact that an FY2027 PDF is already downloadable does not move the release boundary. Our October 1 date-boundary guide explains that decision separately.

Use the current CDC/NCHS FY2027 guideline copy or the CMS copy, and keep the prior April 2026 FY2026 PDF open beside it. Record each file's title and version date. The change marks are meaningful only when you know which editions they compare.

Source: CDC/NCHS: FY2027 ICD-10-CM release dates and files

A five-step review of one changed guideline section

  1. Find the marked passage in FY2027. Write down its section identifier and heading, then read the complete paragraph and neighboring instructions. A bold phrase removed from context can reverse the point.
  2. Find the corresponding text in the April 2026 edition. Search by section topic as well as number, because the FY2027 title page says some material moved. Compare the wording, not only the page number.
  3. Classify what you actually observed. Was the narrative revised, was text relocated, or was a heading changed? If the words differ, summarize the difference in ordinary language without inferring an unverified code change.
  4. Check the classification separately when a code entry matters. The guidelines are a companion to the official ICD-10-CM classification. Inspect the FY2027 Alphabetic Index, full Tabular entry, and the source-file library; use the official code and addenda files to verify an actual code change.
  5. Keep a reproducible note. Save the two edition dates, section identifier, exact source URLs, what changed, and any separate code-file finding. Mark an unresolved point for qualified review instead of turning it into a coding instruction.

This path deliberately stops at source comparison. It is not a substitute for interpreting an encounter, selecting a diagnosis code or determining a payment result. The FY2027 introduction describes the guidelines as a companion to the official ICD-10-CM version published by NCHS.

Source: CMS/NCHS: FY2027 ICD-10-CM Official Guidelines, title page and introduction

Keep guideline edits and code-file edits on separate tracks

Track A: narrative guidance. Read the FY2027 PDF's change marks, compare the prior edition, and describe the changed instruction in its full section. Track B: classification content. Use the CDC/NCHS FY2027 release folder for the official Index and Tabular files, addenda and descriptions. The presence of a bold guideline sentence is not a shortcut to Track B. Likewise, a code or Tabular note can change in the official files without being explained by bold formatting in the guideline PDF.

For a diagram-ready takeaway, draw two parallel lanes: FY2027 guideline PDF → marked narrative → prior-edition comparison and FY2027 code files → addendum → full Index/Tabular verification. Connect the lanes only when the actual sources show a relationship. Our addendum revision walkthrough demonstrates the second lane with a verified source path; this guide is about reading the first lane.

Source: CDC/NCHS: FY2027 official release folder

Share the finding with enough context to check it

A useful review note can say: “U.S. ICD-10-CM FY2027 guidelines, updated October 1, 2026; section [identifier]; compared with April 2026 FY2026; narrative/placement/heading finding; official links.” Fill in the actual section and finding only after reading both documents. If the question concerns a code, add the separate FY2027 Index, Tabular or addendum link. Avoid a headline such as “new code” unless the official classification files establish it.

The ICD Code Hub apps for iPhone, Android and Mac make the available versioned reference convenient to revisit, but a saved entry should retain its release and official source. The shared app links below lead to the verified store listings. For a real coding decision, read the applicable official instructions and seek qualified review when the documentation or interpretation is uncertain.

Source: CDC/NCHS: FY2027 ICD-10-CM release dates and files

Common questions

Does bold text in the FY2027 guidelines mean a new ICD-10-CM code?

No. The FY2027 title page says bold identifies narrative changes. Check the separate CDC/NCHS code files and addenda before describing a code as new.

Does an underlined paragraph always contain a new rule?

No. Underline marks material moved within the guidelines since the April 2026 FY2026 edition. Compare the full wording in both places to determine whether the substance also changed.

What do italic headings indicate in the FY2027 PDF?

Its title page says italics indicate revisions to heading changes. Read the instruction beneath a revised heading before drawing a conclusion about the rule itself.

Which edition should I compare with FY2027?

The FY2027 title page specifically names the April 2026 FY2026 version as the baseline for moved items. Keep both edition dates in your note; use the applicable release for the service or discharge date.

Sources & editorial notes

  1. CMS/NCHS: FY2027 ICD-10-CM Official Guidelines, title page and introduction
  2. CDC/NCHS: April 2026 FY2026 Official Guidelines
  3. CDC/NCHS: FY2027 ICD-10-CM release dates and files
  4. CDC/NCHS: FY2027 official release folder

Scope: U.S. ICD-10-CM Official Guidelines for Coding and Reporting, FY2027 edition updated October 1, 2026; comparison with the April 2026 FY2026 edition, not patient-specific code selection. 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.

Share this guideLinkedIn Facebook X