1.2 General Coding Conventions, Punctuation & Instructional Notes

Conventions turn documentation into consistent code assignment

ICD-10-CM uses structural rules and instructional notes to make the same documented condition reportable consistently. A CDI reviewer needs to recognize when the documentation supports a code, when a classification instruction supplies a relationship or sequence, and when clarification is needed. The FY2027 Official Guidelines, Section I.A, explain these conventions. Classification instructions and conventions take precedence over the guidelines.

Categories, complete codes, and required characters

Categories have three characters. A three-character category is reportable as a code only when it has no further subdivision. Complete codes may have three through seven characters; the decimal point does not count as a character. Do not infer completeness from the length alone. A four-character entry can still be a subdivided category requiring more detail.

For example, A38 is the category for scarlet fever, with further subdivisions. It is not a complete reportable code. A38.9, scarlet fever, uncomplicated, is a complete code; the Tabular List includes scarlet fever NOS under that code. Similarly, N18.3, chronic kidney disease, stage 3 (moderate), has additional subdivisions. The reviewer must select the supported complete code, rather than submit the parent entry.

The placeholder X preserves required positions in designated codes. Where a seventh character applies, it must occupy position seven. If there are fewer than six preceding characters, placeholders fill the necessary positions. X also serves the classification's expansion structure; follow the actual entry rather than adding or removing it from memory.

Consider T42.4X1A, poisoning by benzodiazepines, accidental (unintentional), initial encounter:

The decimal follows the third character in the displayed code. Removing X produces an invalid structure. That invalidity is a coding conclusion; the specific clearinghouse rejection, claim-edit response, or payment outcome depends on the receiving system and applicable process.

Seventh characters have meanings defined by their category. Do not assume every seventh character describes encounter phase. Injury categories may describe treatment phase or fracture healing, while obstetric categories may identify the fetus. Read the applicable instructions before assigning the character.

Read punctuation in its location

Nonessential modifiers do not override a mutually exclusive subentry. The guidelines illustrate this with the Index entry for enteritis: acute is a nonessential modifier, but chronic is a separate subentry. Reading only the main line would miss that distinction. A CDI reviewer should therefore examine the indentation and subterms instead of treating every parenthetical modifier as universally applicable to all descendants.

NEC, not elsewhere classifiable, generally points to an other-specified code when the documented condition has no dedicated code. NOS, not otherwise specified, corresponds to unspecified. Missing documentation and a classification that lacks a unique code are different problems. More detail cannot create a code that does not exist; conversely, an unspecified entry should not replace supported available specificity.

Excludes1 and Excludes2

An Excludes1 note generally bars using the excluded code with the code above the note. The guidelines recognize an exception when the two conditions are unrelated. If their relationship is unclear, query the provider. Do not resolve the issue by assuming that any conditions in different organs are necessarily unrelated.

The guidelines' example involves F45.8, other somatoform disorders, and G47.63, sleep related bruxism. F45.8 includes teeth grinding and excludes sleep-related teeth grinding. The same teeth-grinding condition should not be represented twice through those entries. However, the guidelines permit F45.8 for psychogenic dysmenorrhea together with G47.63 for sleep-related teeth grinding when those are the two unrelated conditions. The documented conditions and actual note determine the result.

An Excludes2 note means the excluded condition is not included in the code. Both conditions may be reported when appropriate. It does not waive documentation, reportability, or other classification requirements. In either case, verify that the note actually exists in the applicable release, including inherited notes at the parent level; do not manufacture an Excludes2 note merely because two diagnoses can coexist.

Sequencing instructions have distinct effects

Code first and use additional code instructions govern code relationships and order. In an etiology/manifestation pair, sequence the underlying disease before the manifestation. Codes titled in diseases classified elsewhere cannot be principal or first-listed and require the underlying condition. The instruction establishes relative order; it does not impose a universal requirement that the codes occupy immediately adjacent claim positions.

These instructions also occur outside classic etiology/manifestation pairs. Read the actual note and all applicable guidelines. A use-additional-code instruction may require information such as the type or stage of a condition. Do not assume it always means that the second condition is a manifestation code that can never be principal under any circumstances.

For example, I11.0, hypertensive heart disease with heart failure, instructs use of an additional code to identify the heart failure type. I50.23 describes acute on chronic systolic (congestive) heart failure; I50.21 describes acute systolic (congestive) heart failure. Those descriptions are not interchangeable. Select the supported acuity and apply the sequencing instruction rather than stopping at a generic heart-failure label.

A code also note indicates that two codes may be necessary, but does not itself direct sequencing. Determine order from the encounter circumstances and other applicable instructions. This is not permission to disregard a separate code-first requirement.

Relational terms and the limits of presumed linkage

In code titles, and is interpreted as and/or. The general with/in convention in Section I.A.15 presumes an association where the classification specifically links the conditions. It does not mean that every pair of coexisting diagnoses is related. The presumption does not apply when documentation clearly states that the conditions are unrelated or another guideline specifically requires documented linkage.

Hypertension and heart failure illustrate a supported presumption. Under Section I.C.9.a.1, the classification presumes their relationship unless documentation clearly states otherwise. For a patient with hypertension and acute on chronic systolic heart failure, without chronic kidney disease or another relevant modifying circumstance, I11.0 with I50.23 represents that relationship and specified heart failure type. The mere absence of the provider's words due to does not require a linkage query.

Sepsis with an acute organ dysfunction illustrates why the exception matters. Section I.C.1.d requires association between the acute organ dysfunction and sepsis to assign severe sepsis. If the record does not clearly establish whether the dysfunction is related to sepsis or another condition, query the provider. Coexistence alone does not supply the required relationship.

For an exam scenario, use four checks: verify the complete code, read inherited notes, apply the correct relationship and sequence, and resolve actual documentation uncertainty. This process prevents a correct disease name from producing an incomplete code or an unsupported combination.

Examples above were checked against the official FY2027 Tabular List and Index and complete code descriptions.