Cleaning up the code set: How to influence ICD-10-CM Index and Tabular List changes

Why This Topic Matters

Addenda changes can affect code lookup, documentation review, and the way coded data supports reporting and analysis. Understanding the submission process helps CDI and coding teams contribute to cleaner code set maintenance and stay aware of upcoming ICD-10-CM changes.

Article Sections

1. NCHS’ process for addenda

   Describes the public process for proposed updates to ICD-10-CM index and tabular entries, including how suggestions are reviewed and how meeting materials are made available. It also notes the role of the ICD-10 Coordination and Maintenance Committee and the timing of proposals and comment periods.

2. Addenda’s effects

   Discusses the broader ways Addenda can affect coding, data reporting, severity measures, and query workflows. The section uses examples to show why changes to index or tabular entries may matter to CDI and coding teams.

3. Types of corrections

   Outlines common categories of suggested changes, such as terminology updates, spelling adjustments, and responses to evolving guidance. It also notes who often submits these suggestions.

4. What not to submit

   Explains the general boundaries of the suggestion process and identifies topics that are outside the scope of Addenda requests. It distinguishes between code set maintenance questions and other coding resources or review processes.

5. Process for submitting

   Provides practical guidance for organizing and documenting potential suggestions before sending them to NCHS. It covers submission preparation, supporting materials, and ways to review the impact of proposed changes.

6. Feedback

   Summarizes what submitters may hear back from NCHS after sending a suggestion and notes that additional information may be requested. It also discusses the possibility of resubmission when proposals are not immediately adopted.

7. Get involved

   Encourages CDI and coding professionals to participate in the process and collaborate with others when relevant. The section emphasizes the value of comments and shared input in maintaining a usable code set.