2.7 Abstraction Foundations Case Lab

How to set up a CCS case

A case scenario should be handled like a small audit, not a race to the answer choices. First identify the encounter type. Then identify the record boundary, final provider documentation, procedures, reportable diagnoses, missing specificity, and sequencing rule. Finally, validate candidate codes and reject unsupported options. The order matters because answer choices often contain clinically plausible but legally unsupported codes.

Start with a one-line case label. For example: inpatient admission for abdominal pain, final acute appendicitis, laparoscopic appendectomy, secondary diabetes managed with insulin. Or: ED treated and released for ankle injury, x-ray negative, final sprain, splint applied. This label forces you to anchor the case in setting and final documentation. It also helps you notice when an option uses an inpatient-only concept in an outpatient case or codes a suspected diagnosis as confirmed.

Next, make a source list. The attending discharge summary may control final inpatient diagnosis. The operative report may control PCS root operation. The ED provider note may control a treated-and-released ED diagnosis. The pathology report may supply findings that need provider interpretation. Nursing notes may support resource use or query indicators. Orders may support medical necessity but may not prove a final diagnosis. Each source gets used for the question it is strong enough to answer.

Case setup template

Lab case 1: An adult is admitted through the ED with right lower quadrant pain, fever, and leukocytosis. The H and P lists possible appendicitis. CT supports appendicitis. The surgeon performs laparoscopic removal of the appendix. The discharge summary states acute suppurative appendicitis. Diabetes mellitus type 2 is continued on home insulin with glucose monitoring. The patient is discharged home.

For this inpatient case, the coder does not sequence abdominal pain as principal when a definitive diagnosis explains it. The principal diagnosis is based on the condition after study that chiefly occasioned admission, subject to guideline validation. Diabetes may be a reportable secondary diagnosis because it was actively managed with insulin and monitoring. The procedure is abstracted from the operative report, not merely the title, to determine the correct PCS elements. POA for appendicitis and diabetes should be considered from admission evidence.

Lab case 2: A patient presents to the ED after twisting the left ankle. Triage documents rule out fracture. The ED provider documents swelling and tenderness. X-ray is negative for acute fracture. Final diagnosis is left ankle sprain. A splint is applied, crutches are provided, and the patient is discharged. The answer choice that codes ankle fracture is unsupported because the final provider diagnosis and imaging do not establish fracture. The coder should evaluate diagnosis, supplies, procedure support, laterality, and any modifier or facility coding rules applicable to the ED service.

Lab case 3: An outpatient colonoscopy is performed for screening. A polyp is removed by snare technique, and pathology later identifies a benign adenomatous polyp. The coder must determine how facility policy and coding guidance handle screening encounters with findings, whether the pathology result has been incorporated appropriately, and which CPT code is supported by the technique. A diagnostic-sounding polyp code alone may miss the screening context. A procedure code without technique support may also be wrong.

Abstraction note format

• Encounter type: inpatient, outpatient, ED, observation, or ancillary service.
• Final diagnosis evidence: provider, date, note type, and whether the diagnosis is confirmed, suspected, ruled out, or historical.
• Procedure evidence: report title, body details, objective, body part, approach, device, and technique.
• Secondary diagnosis support: treatment, evaluation, monitoring, medication, consult, diagnostics, or resource effect.
• Quality data: POA, discharge disposition, complication language, HAC or PSI relevance, and documentation source.
• Query triggers: conflict, missing specificity, unclear linkage, unsupported severity, or ambiguous complication relationship.
• Rejected options: why each tempting code is not supported.

Case lab work should also include negative findings. If the provider says no pneumonia, do not code pneumonia because antibiotics were initially started. If imaging says possible mass but the provider documents benign cyst, do not code malignancy. If a procedure note documents inspection only, do not code excision because a biopsy tray was opened. If a problem list imports chronic respiratory failure but the current encounter has no oxygen dependence, treatment, or provider assessment, review before reporting it.

The last step is answer defense. For each final answer, state the source and the rule. Discharge summary documents acute appendicitis after study, so abdominal pain is not separately sequenced as principal. Operative report documents laparoscopic removal of the appendix, so procedure abstraction comes from the operative details. ED final diagnosis is left ankle sprain, so fracture is not coded. This defense style is useful on the exam and in production coding because it keeps the coder tied to documentation, guideline navigation, and abstraction logic.

A final warning: do not let the answer choices create facts. If one option includes a complication, organism, MCC, modifier, or PCS device that the case did not document, treat it as unsupported until proven. If an option includes all documented facts but violates sequencing or a codebook instruction, it is still wrong. CCS-level abstraction combines evidence, official rules, and restraint.