3.7 ICD-10-CM Diagnosis Coding Case Lab

Key Takeaways

  • Case coding requires a full-record workflow: setting, encounter purpose, documented diagnoses, reportability, guideline checks, sequencing, POA, and query opportunities.
  • A defensible answer includes why diagnoses were not coded, not only which codes were selected.
  • Exam scenarios often embed distractors such as unresolved rule-out conditions, incidental chronic problems, integral symptoms, and unsupported complications.
  • POA and secondary-diagnosis logic should be applied diagnosis by diagnosis after principal or first-listed selection.
  • The fastest accurate case strategy is to build a small timeline and a code-support table before choosing answer options.
Last updated: May 2026

Case lab method

A CCS case item may give you an H&P, ED note, discharge summary, labs, imaging, procedures, medications, and final diagnoses. You will not have time to code every word in the record from scratch. You need a compact workflow that turns the record into a defensible sequence. The goal is not to list all clinical facts. The goal is to identify reportable diagnoses, validate code families, assign sequence, and recognize when a query would be required.

Use a two-pass read. On the first pass, identify setting and storyline. Why did the patient present? Was there an inpatient admission order? What changed after study? What was treated? What conditions were ruled out, confirmed, or left uncertain? On the second pass, abstract diagnoses and evidence. Mark principal or first-listed candidates, secondary diagnoses, symptoms, chronic conditions, complications, and POA timing.

Structured aid: case coding table

StepQuestionOutput
1What is the setting?Inpatient, outpatient, ED, observation, surgery, diagnostic test
2What occasioned the encounter or admission?Principal or first-listed candidates
3What was established after study?Definitive diagnoses or highest certainty conditions
4Which additional diagnoses affected care?Reportable secondary diagnosis list with reason
5What notes or guidelines control sequence?Code first, use additional code, chapter rules, manifestation logic
6What timing applies?POA Y, N, U, W, or exempt when inpatient reporting applies
7What cannot be coded without clarification?Query opportunities or excluded diagnoses

Mini-case 1: inpatient shortness of breath

A 72-year-old is admitted from the ED with worsening shortness of breath, productive cough, fever, and hypoxia. The admitting impression is pneumonia versus acute heart failure. After study, the discharge summary documents acute hypoxic respiratory failure due to community-acquired pneumonia, chronic diastolic heart failure, and type 2 diabetes mellitus with chronic kidney disease stage 3b. The patient receives IV antibiotics, oxygen, respiratory therapy, glucose monitoring, insulin adjustment, renal-dose medication review, and daily basic metabolic panels. No provider documents sepsis.

Blood cultures are negative. The patient had symptoms and abnormal chest imaging at admission.

The principal diagnosis question starts with the admission reason and final cause. If the provider documents acute hypoxic respiratory failure due to pneumonia and both were present on admission, you must review whether respiratory failure or pneumonia chiefly occasioned admission and whether facility policy or guideline permits either based on circumstances. In many cases, either acute respiratory failure or pneumonia may be principal when both meet the definition and no sequencing rule controls, but the record facts decide.

Chronic diastolic heart failure is secondary only if it affected care; if it was assessed and monitored but not the cause of admission, report it when it meets criteria. Diabetes with CKD requires combination-code thinking plus CKD stage detail if instructed. Sepsis is not coded because clinical indicators and antibiotics do not replace provider documentation.

POA assignment follows the timeline. Pneumonia and respiratory failure appear present at admission based on symptoms, ED findings, and provider documentation. Diabetes, CKD, and chronic heart failure likely are POA if documented as chronic preexisting conditions. If the provider did not clarify whether respiratory failure was present at admission, clinical indicators may support POA Y, but unclear documentation could require a query depending on record detail.

Mini-case 2: outpatient abdominal pain

A patient presents to the ED with right lower quadrant pain, nausea, and elevated white blood cell count. CT is equivocal. The provider documents 'rule out appendicitis' and discharges the patient with instructions for repeat exam if symptoms worsen. Final diagnosis is abdominal pain. No appendicitis is confirmed.

This is not an inpatient discharge uncertain-diagnosis scenario. The first-listed diagnosis should reflect the highest degree of certainty, which is abdominal pain or the documented symptoms as appropriate. Do not code appendicitis as established. Nausea may or may not be separately coded depending on whether the classification and documentation support it as an additional reason for care or integral to the abdominal pain presentation. The key CCS lesson is setting: outpatient and ED final coding does not convert rule-out wording into a confirmed diagnosis.

Mini-case 3: postoperative condition

A patient undergoes colon resection for diverticular disease. On day three, the patient develops fever and leukocytosis. Imaging shows a pelvic abscess. The provider documents pelvic abscess after surgery and treats it with drainage and antibiotics. The note does not state whether the abscess is a postoperative complication, expected condition, residual infection, or unrelated disease process.

The abscess is likely reportable because it required diagnostic workup, drainage, and antibiotics. The complication code is not automatic. If the provider does not document a cause-and-effect relationship to the surgery or a specific postoperative complication, the coder should not infer one solely from timing. A compliant query may ask whether the pelvic abscess is a postoperative complication, unrelated infection, residual condition, other, or unable to determine, supported by clinical indicators.

POA is likely N if it developed after admission and was not present at the inpatient admission order, but timing and provider documentation still control.

Final answer habits for CCS cases

  • Write the setting first: inpatient, outpatient, ED, observation, surgery, or diagnostic test.
  • Circle the reason for admission or encounter before reading answer options.
  • Separate confirmed diagnoses from rule-out, suspected, history, status, and symptom terms.
  • For each secondary diagnosis, write a one-word support reason: treated, monitored, evaluated, affected, queried, or not reportable.
  • Check for combination codes before adding separate component codes.
  • Check for code first and use additional code notes before final sequence.
  • Assign POA after diagnosis selection, using the inpatient admission order as the timing anchor.
  • Identify at least one thing not to code. This prevents overcoding distractors.

A good CCS case answer is usually modest. It does not code every abnormal result, every symptom, every remote condition, or every possible complication. It codes what the provider documented, what the classification supports, what the encounter required, and what the official sequencing rules allow. That discipline is what separates exam-level diagnosis coding from keyword extraction.

Test Your Knowledge

In Mini-case 1, why is sepsis not coded from fever, hypoxia, antibiotics, and abnormal findings alone?

A
B
C
D
Test Your Knowledge

In Mini-case 2, what is the main reason appendicitis is not coded?

A
B
C
D
Test Your Knowledge

In Mini-case 3, what is the best response to the pelvic abscess documentation?

A
B
C
D