Good ICD-10-CM practice starts with the record, the care setting and the applicable coding instructions. These five fictional examples show how to choose a defensible coding approach before searching for a final code. They are guided explanations, not a scored test or instructions for coding an actual patient’s claim.
Each example deliberately identifies what the documentation supports and what is still missing. The goal is to avoid a common learning mistake: finding a code that sounds plausible and then fitting the record to it. For a scored knowledge check after the examples, use the ICD-10 practice quiz with answer explanations.
Set up a repeatable lookup worksheet
- Record the setting and the applicable reporting date. Outpatient and specified inpatient rules are not interchangeable.
- Extract the documented condition and details relevant to coding. Separate confirmed facts from suspected diagnoses.
- Locate the condition in the Alphabetic Index, then verify the candidate in the Tabular List.
- Read category-level notes, inclusion terms, exclusions, sequencing instructions and required characters.
- Record any missing or conflicting information that prevents a supported selection.
The official ICD-10-CM guidelines provide the conventions and setting-specific rules behind this process. The examples below focus on those decisions rather than giving a code string without the surrounding instructions. A code search result is a candidate to verify, not the final reasoning.
Example 1: “Possible pneumonia” in an outpatient visit
Fictional record: An outpatient clinician evaluates a patient for a cough, documents “possible pneumonia,” and orders further testing. The visit record does not establish pneumonia as a confirmed diagnosis.
Decision: Do not report the uncertain pneumonia as though it were established. Under Section IV.H, outpatient coding uses the highest degree of certainty for the encounter, such as the documented symptoms, signs or reason for the visit. Look up the supported finding, then verify the candidate code and its instructions.
Why the tempting answer fails: Coding pneumonia because it is the most serious possibility converts a diagnostic question into a documented conclusion. Coding is not a prediction of what a later test will show. A clinician’s plan to investigate a condition does not itself confirm the condition.
Change the setting: A qualifying inpatient discharge record has different uncertain-diagnosis guidance under Section II.H. The answer can therefore change when the setting changes even if the phrase “possible pneumonia” remains. This is why a practice question that omits the setting may be ambiguous.
Example 2: Right-sided documentation and an unspecified code
Fictional record: A clinician documents a right-sided condition. Your Index search leads to a category offering right, left and unspecified-side choices.
Decision: Verify the right-sided option and the remaining details in the Tabular List. Selecting an unspecified-side code merely because it is shorter discards information the record already supplies. Laterality is one part of specificity; other required distinctions still need checking.
Why the tempting answer fails: “Unspecified” does not mean “safe default whenever I am unsure which code to choose.” It describes a lack of the relevant documented detail. If the detail is available, uncertainty about the lookup should lead you back to the reference.
Change the record: If the documentation gives no side, do not infer right or left from a likely pattern. Review the full record and applicable rules, and seek clarification when appropriate. If both sides are documented, check whether a bilateral code exists; when it does not, laterality guidance may require separate right and left codes. Do not invent a bilateral extension.
Example 3: An “initial encounter” after an earlier visit
Fictional record: A patient receives active treatment for an injury from a new clinician after an earlier evaluation elsewhere. The relevant injury category uses seventh characters for encounter phase.
Decision: Determine the treatment phase from the documentation. Under the injury guidelines in Section I.C.19, an initial-encounter character is used during active treatment; it does not simply mean the first visit on a calendar or the first time this clinician sees the patient.
Why the tempting answer fails: Selecting a subsequent-encounter character solely because “someone already saw the patient” mistakes visit order for treatment phase. Routine healing or recovery care and a residual effect after the acute phase require different reasoning.
Finish the lookup: Check which seventh characters the specific category permits. If a placeholder is needed to put the encounter character in position seven, include it as instructed. Count the alphanumeric characters, not the decimal. This example does not supply a complete injury diagnosis, so it intentionally stops short of assigning a final code.
Example 4: Two diagnoses connected by an Index entry
Fictional record: Two conditions are documented. The Alphabetic Index links the conditions using “with,” and you are deciding whether to look for a combination code or report unrelated codes.
Decision: Apply the classification’s “with” convention, then inspect the candidate combination code and any additional-code instructions. Section I.A.15 explains presumed relationships where the classification links conditions, with exceptions such as documentation clearly stating that the conditions are unrelated or guidance requiring an explicit documented link.
Why the tempting answer fails: Two blanket rules are both unsafe: “always assume related” and “never use a relationship unless the clinician writes caused by.” The Index, Tabular List and specific guideline determine whether a presumed relationship applies. Merely having two conditions in the same record is not enough by itself.
Change the record: If the clinician clearly states that the conditions are unrelated, revisit the assumption rather than forcing the combination code. If a combination code does apply, inspect whether another code is still required to capture a manifestation, stage or other detail. “Combination code” does not automatically mean that exactly one code finishes the entire case.
Example 5: Conflicting notes and an Excludes instruction
Fictional record: Two notes describe conditions that appear to fall under an Excludes1 relationship. It is unclear whether the notes describe the same problem or two unrelated conditions.
Decision: Read the exclusion at the applicable code or category and examine whether the conditions are related. Section I.A.12 describes Excludes1 and its exception for unrelated conditions. When the relationship is unclear, the guideline directs a provider query. Do not resolve an ambiguous record by picking the code that produces the preferred reimbursement.
Why the tempting answer fails: Treating Excludes1 as an unconditional instruction to delete one diagnosis can miss the unrelated-condition exception. Treating it as permission to report both whenever both appear in a chart ignores the exclusion. The missing information is the relationship, not a more convenient code.
Compare Excludes2: Excludes2 means the excluded condition is not part of the code’s condition, but both may be reported when both are present and otherwise supported. It is a different convention, not a softer spelling of Excludes1.
How should you review your answers?
For each case, write one sentence explaining the rule, one naming the supporting documentation and one naming what would change your answer. This makes a useful error log: “I applied an inpatient rule to an outpatient visit” gives you a specific correction; “I need to memorize more codes” does not describe that mistake.
Then test a variation without looking at the explanation. Switch outpatient to inpatient, right to undocumented side, or active treatment to routine recovery. Ask whether the change affects the rule, the code detail or the need for clarification. Avoid changing several facts at once until you can explain the effect of each one.
These cases were checked September 29, 2026 against the FY 2026 CM guidelines, including the April 1 update. Use the CDC release resources to select the code set and guidelines for the date you are practicing; reporting dates beginning October 1, 2026 require checking the applicable FY 2027 release. These simplified exercises do not replace the full record or official instructions.
If you are unsure which system a question belongs to, read ICD-10-CM versus ICD-10-PCS before attempting procedure examples. Then take the 20-question ICD-10 quiz and review the explanations for missed conventions. The SimpuTech medical-coding AI coach can help discuss fictional practice scenarios; verify its suggestions against the official code set.