Administrative details such as scheduling, fees, and the current required codebook list are maintained by AHIMA on its CCS certification page; this guide focuses on the coding decisions themselves. The core habit to build is identifying the setting first, then applying the rule set that setting governs, with a stated rationale for every assignment.
The Uncertain-Diagnosis Rule That Flips Between Settings
Inpatient ICD-10-CM guidance codes conditions documented as probable, suspected, or equivocal at discharge as if established. Outpatient guidance does the opposite: code only confirmed conditions, or the signs and symptoms that prompted the encounter.
This asymmetry exists because an inpatient stay gives providers the entire admission to reach a conclusion, so hedged language on the discharge summary is treated as a final clinical determination. Outpatient and ED encounters typically end before confirmation, and coding a condition that was never established misrepresents the encounter. Keep the two rules as a matched pair on a single flashcard rather than memorizing either alone, and label every practice scenario INPATIENT or OUTPATIENT before you open the index.
Scenario A: an ED note ends with 'chest pain, likely GERD, discharged home on antacids.' Assigning a GERD code is the tempting error; the better decision is coding the chest pain symptom, because the outpatient rule forbids coding 'likely' conditions and the symptom also supports the workup that was performed. Contrast an inpatient discharge summary reading 'probable aspiration pneumonia, treated with IV antibiotics' - there, the guideline directs you to code the pneumonia as if established. Same qualifier, opposite handling, entirely because of setting.
Principal Diagnosis, UHDDS Definitions, and POA in One Pass
UHDDS defines principal diagnosis as the condition, after study, established as chiefly responsible for admission. Sequencing follows official guidelines, secondary diagnoses must meet reportability criteria, and each reported diagnosis carries a present-on-admission indicator.
Work sequencing questions from the UHDDS definition rather than instinct. When two related conditions are treated concurrently and neither clearly meets the 'after study, chiefly responsible' test, the guideline provisions for that admission situation decide the order - so name, aloud, which provision you are relying on. Also screen every secondary diagnosis against the reportability criteria: clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care and monitoring. A borderline finding that drove none of those does not belong on the coded record.
Attach a POA indicator to every principal and secondary diagnosis, not only the dramatic ones. The options are present at admission, not present at admission, unknown, and clinically undetermined. A urinary tract infection first documented on day three, in a patient whose catheter was placed after admission, is not present on admission - and that determination is precisely what hospital-acquired-condition logic examines. Practicing POA as a per-diagnosis habit keeps it from collapsing into an afterthought when a scenario carries many secondary conditions.
Writing and Judging a Query That Stays Non-Leading
A compliant query is non-leading, presents clinically reasonable answer options, includes the clinical indicators that raised the question, and never references reimbursement or financial impact. The exam tasks cover both spotting query opportunities and judging query language.
Scenario B: a chart documents 'possible sepsis' alongside hypotension, an elevated lactate, and broadened antibiotics. A query asking 'Can you confirm sepsis?' is the mistake - it pressures the provider toward one predetermined answer. A compliant version states the indicators and offers balanced options: sepsis confirmed, sepsis clinically not supported, sepsis still under evaluation, or unable to determine, plus an open response option. Both versions cite the same documentation; only one respects the provider's independent clinical judgment.
Train two directions on this skill. First, evaluate a given query: check for leading phrasing, yes-or-no framing that favors a higher-specificity answer, missing clinical indicators, and any mention of payment consequences - any one of these makes the query non-compliant. Second, scan documentation for query opportunities: ambiguous qualifiers, conflicting statements between providers, or a clinically significant condition documented only as possible. Writing your own two-line compliant queries from practice charts gives faster feedback than reading examples alone.
NCCI Edits, Medical Necessity, and Modifiers on Outpatient Charts
Outpatient scenarios test whether a procedure pair triggers a National Correct Coding Initiative edit, whether any modifier is supported by documentation, and whether the reported diagnosis establishes medical necessity for the service performed.
When two reported procedures appear on an edit pair list, the question is not 'which modifier clears the edit' but 'does the record show two distinct, independent services?' Assigning a modifier without distinct documentation is the error to train against. A modifier is justified when the chart separately supports each service, and the edit itself is a flag to re-examine the documentation, not an obstacle to route around. Read each scenario's procedure notes specifically for distinct sites, separate sessions, or independent lesions before touching the modifier.
Medical necessity works in the other direction: the diagnosis reported must support why the service was performed. Reporting a screening test with a symptom diagnosis, or a diagnostic study with an unrelated chronic condition, produces a mismatch that edits are designed to surface. In scenarios, link each procedure back to a documented reason for the encounter - often the symptom or the order itself - and check that your first-listed diagnosis on the outpatient side reflects the circumstance of the encounter rather than inpatient-style sequencing habits.
DRG Versus APC: One Chart, Two Payment Logics
Inpatient coding feeds diagnosis-related group assignment, where principal diagnosis, CCs and MCCs, procedures, and POA drive the result. Outpatient coding feeds Ambulatory Payment Classification logic built around CPT and HCPCS work.
The practical consequence is that identical documentation invites different questions depending on setting. Inpatient practice should end with you naming the principal diagnosis, listing which secondaries qualify as CC or MCC, and stating a POA value for each. Outpatient practice should end with the CPT or HCPCS codes, any justified modifiers, and the first-listed diagnosis supporting medical necessity. Rehearsing both endings from similar charts forces the payment-model distinction into your reflexes instead of leaving it buried in your notes.
Keep the comparison table beside you during mixed review. When you catch yourself applying inpatient reasoning - such as hunting for an MCC - on an outpatient or ED scenario, stop and reset to the outpatient lens of edits, modifiers, and necessity. That self-correction is a trainable skill, and the table is the specific tool for training it.
table_placeholder
| Dimension | Inpatient record | Outpatient / ED encounter |
|---|---|---|
| Primary code sets | ICD-10-CM and ICD-10-PCS | ICD-10-CM plus CPT and HCPCS |
| Selection concept | Principal diagnosis plus reportable secondary diagnoses | First-listed diagnosis supporting medical necessity |
| Payment lens | DRG assignment, MCC/CC capture, POA indicators | APC logic, NCCI edits, modifiers |
| Documentation focus | Discharge summary and full-stay course with POA evidence | Order, procedure note, and reason for the encounter |
Resolving Documentation Conflicts Without Guessing
Conflicting documentation - laterality, admission type, dates, or disagreements between providers - must be resolved from the record itself or through a compliant query, never from coder inference or silent assumption.
The documentation domain asks you to verify that everything a specific code requires actually exists within the body of the health record. Some codes carry built-in prerequisites: a laterality value, a specified technique, a distinct episode marker. Assigning the code while assuming the missing element is the classic scenario trap. Before finalizing any assignment, list what the candidate code requires and locate each element in the chart; anything unlocatable becomes a verification step or a query, not a quiet assumption you carry forward.
Compliance framing reinforces the same habit. Complete and accurate records underpin patient safety indicator and hospital-acquired condition identification, HIPAA governs how you handle the record while working, and the AHIMA Standards of Ethical Coding bar assigning codes from incomplete or unsupported documentation. Treat 'this code needs a fact I cannot find' as a legitimate professional finding in its own right - the scenarios reward surfacing that gap rather than papering over it with a convenient code.
A Six-Point Scenario Audit, Rubric, and Preparation Sequence
Code each practice scenario, then audit it against a six-point rubric: setting rule applied, sequencing rationale, POA per diagnosis, CC/MCC screen, query opportunity, and edit or necessity check.
Exercise: take one inpatient scenario and code it cold, without references on the first pass. Then audit aloud: state the setting and which uncertain-diagnosis rule applies; justify the principal diagnosis sequencing under the UHDDS definition; give a POA value for every secondary diagnosis; name which secondaries are CC or MCC and why; identify one query opportunity or state that none exists; and check any procedure against edit and necessity logic. Expected observation: the audit surfaces at least one decision you made silently, which is exactly the habit to break.
Score each audit point as clean, shaky, or missed, and use a personal milestone of five of six points rated clean across three consecutive scenarios before moving to timed practice - a learning milestone, not a pass prediction. A workable sequence: two weeks on official guideline sections; two weeks on setting-split scenario drills; one week writing compliant queries; one week on edits, DRG, and APC logic; then mixed timed review rotating inpatient, outpatient, and ED cases. Stretch or compress each block according to your own audit results.
- You can state both uncertain-diagnosis rules and name which setting each governs, without looking at notes.
- You can assign a POA value to every secondary diagnosis in a multi-diagnosis scenario and defend each choice.
- You can rewrite a leading query into a compliant one with balanced options and cited clinical indicators.
- You can explain, for any modifier you assign, which specific documentation element makes the services distinct.
- Audit milestone reached: five of six rubric points rated clean across three consecutive mixed-setting scenarios.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.