First-hand experience: Submitting an ICD-10-CM code proposal

Why This Topic Matters

It helps readers understand how coding change proposals move through the official review pathway and what kinds of collaboration, documentation, and public input are involved.

Article Sections

1. Troublesome reporting

   Introduces the clinical reporting problem that motivated the proposal and explains why more specific classification was being sought. It also places the issue in a research and trauma-care context.

2. How to create an ICD-10 code

   Describes the public committee process for proposing changes, including attendance, registration, commenting, and review timing. It also notes the roles of meeting access and continuing education.

3. Writing the proposal

   Summarizes the types of information included in a proposal and the preparatory research used to support it. It also outlines how the submission is coordinated before presentation.

4. Determine detail needs

   Covers how the proposal team identified the level of clinical detail needed and aligned terminology with the information clinicians use. It also discusses how supporting rationale was developed.

5. Consider code set structure

   Explains how the proposed change was matched to the structure of the classification system and how related notes and sequencing concepts were considered. It also addresses how the proposal fit within the broader injury chapter.

6. Presenting the proposal

   Describes what happens when a proposal is formally presented and who may speak on behalf of the submitters. It also summarizes the meeting discussion and initial feedback.

7. Post meeting: Public comment period and beyond

   Summarizes the written comment phase and the continued review process after the meeting. It also notes that final approval and downstream implications are still considered later.

8. Summary

   Recaps the overall effort involved in preparing a proposal and reflects on the experience from the submitters' perspective. It emphasizes the planning and collaboration required.