CDEO Domain 9: Cases Complete Study Guide 2026

What Domain 9 Actually Tests

The Certified Documentation Expert Outpatient (CDEO) credential, offered by AHIMA, positions Domain 9 - Cases - as the capstone domain of the entire examination. At 20% of total exam weight, it ties with Domain 3: Clinical Conditions as the heaviest single domain on the test. That parity is not coincidental. Cases are the applied expression of clinical knowledge: you cannot answer a case question correctly without first understanding the clinical picture being described.

What separates Domain 9 from every other domain is its integrative nature. A single case vignette can simultaneously test your knowledge of outpatient documentation requirements (Domain 5), correct diagnosis code selection under ICD-10-CM outpatient guidelines (Domain 4), the appropriate procedure code assignment (Domain 7), whether a quality measure is implicated in the patient encounter (Domain 8), and whether a provider query is warranted and how to word it (Domain 2). In other words, Domain 9 does not introduce new knowledge - it demands that all prior knowledge be applied together under realistic conditions.

The outpatient setting is the defining frame for every case. CDEO cases will not present inpatient scenarios. The documentation rules that govern outpatient coding - first-encounter coding conventions, the prohibition on coding uncertain diagnoses as confirmed, the first-listed versus additional diagnosis logic under Uniform Hospital Discharge Data Set (UHDDS) outpatient guidelines - are the exact rules being tested. Candidates who have inpatient CDI experience must actively retrain their default assumptions before sitting for this exam.

Why Cases Carry 20% of the Exam

The CDEO credential exists because outpatient documentation integrity is a distinct, complex professional competency. Payers, compliance officers, and health system quality departments need CDI professionals who can read an encounter note, identify documentation gaps, recognize when a clinical condition is inadequately specified, and take corrective action - all without disrupting the patient-provider relationship or crossing into physician direction.

Domain 9 validates that operational competency. It answers the question: can this candidate actually do the work in a realistic scenario? The eight other domains test whether you understand the principles. Domain 9 tests whether you can apply them. That is why it weighs as much as it does, and why candidates who under-prepare for case questions - even those with strong clinical or coding backgrounds - are surprised by their results.

Anatomy of a CDEO Case Question

Understanding how CDEO case questions are constructed is itself a form of preparation. These are not simple recall questions. They typically present a condensed clinical vignette - a physician's progress note, an operative report excerpt, a hospital outpatient clinic note, or a procedure documentation snippet - followed by one or more questions that require analysis rather than memory retrieval.

A typical case question structure works like this: the vignette establishes a patient presentation and the provider's documentation. The stem then asks something like: "What is the most appropriate first-listed diagnosis code?" or "Which of the following queries would be compliant and appropriate given this documentation?" or "Which quality measure is at risk based on the documentation as written?" The correct answer requires you to process the clinical information, apply the relevant guideline, and identify the option that reflects CDEO-level thinking.

Multi-part case scenarios may appear where two or three questions draw from the same vignette. In these formats, getting the first question wrong can cascade into errors on subsequent questions if the logic is connected. This is another reason timed practice with full case vignettes - not just isolated questions - is essential preparation. You can access realistic CDEO case-style practice questions at our CDEO practice test platform, which is built specifically around the domain structure of the outpatient exam.

Clinical Conditions You Must Recognize Instantly

Because Domain 3: Clinical Conditions (20%) feeds directly into Domain 9 case performance, the clinical knowledge you develop studying Domain 3 is the foundation every case question stands on. In the outpatient setting, certain condition categories appear with particular frequency in documentation integrity work, and the exam reflects that reality.

Chronic condition management is a major case theme. Diabetes mellitus with complications, hypertension, chronic kidney disease staging, heart failure, chronic obstructive pulmonary disease, and obesity are all conditions where outpatient documentation specificity directly impacts code assignment and, downstream, risk adjustment, quality measurement, and reimbursement. A case may present a patient with "uncontrolled diabetes" in a provider's note and ask whether that documentation is sufficient or whether a query is warranted to specify the type and any complications.

Acute conditions presenting in outpatient settings - chest pain of uncertain etiology, syncope, acute respiratory illness - test the outpatient coding rule about signs and symptoms. When a definitive diagnosis has not been established by the end of an outpatient encounter, the sign or symptom is coded, not the suspected condition. Case questions routinely test whether candidates correctly apply this rule rather than defaulting to inpatient logic.

Coding and Documentation Applied in Case Context

Domain 4: Diagnosis Coding (10%) and Domain 5: Documentation Requirements (15%) are the two technical pillars that Domain 9 cases most directly activate. In isolation, these domains test whether you know the rules. Inside a case, they test whether you can recognize when the rules are being violated - or when they create an opportunity to improve a record.

Outpatient diagnosis coding operates under guidelines that are distinct from inpatient coding. The first-listed diagnosis follows specific sequencing logic. Z codes for encounters for specific reasons - screenings, follow-up, supervision - appear regularly in outpatient settings and their correct use is testable. External cause codes, status codes, and the interaction between chronic conditions and the presenting reason for the visit all surface in case scenarios.

Documentation requirement cases often present notes where the provider's language is clinically understandable but not codeable. "The patient's sugar was high" is not ICD-10-CM codeable specificity. A case built around that documentation will test whether you recognize the gap, whether a query is the appropriate response, and how to formulate it compliantly. Domain 5 overlaps with Domain 2: Provider Communication and Compliance (10%) in exactly these scenarios.

Domain 7: Procedure Coding (10%) enters case questions when the outpatient encounter involves a procedure. CPT coding for evaluation and management services, the correct level of service selection, and procedure-specific documentation requirements are all areas where a case vignette might reveal an audit risk or a missed coding opportunity. The CDEO candidate is expected to recognize these issues as a documentation integrity professional, not necessarily to function as a full-time coder - but the knowledge base is required.

Quality Measures and Payment Models Inside Cases

Domain 8: Quality Measures (5%) and Domain 6: Payment Models (5%) each represent smaller exam weights individually, but they frequently appear embedded within Domain 9 case scenarios rather than as standalone questions. A case about a diabetic patient's A1c documentation may simultaneously implicate HEDIS measure compliance. A case about a high-complexity outpatient visit may touch on how evaluation and management level selection interacts with value-based payment arrangements.

This embedding is intentional. In real outpatient CDI work, a documentation integrity professional does not encounter quality measures or payment models in isolation - they appear as consequences of documentation decisions. The exam mirrors that reality. Candidates who study Domains 6 and 8 only as isolated topic lists and never connect them to clinical scenarios will miss the integration that case questions demand.

Provider Communication Scenarios in Case Questions

Domain 2: Provider Communication and Compliance (10%) generates some of the most nuanced case questions on the CDEO exam. A case will present a documentation situation and ask whether a query is appropriate, and if so, which query format is compliant. The answer depends on whether the clinical indicators in the record support the query, whether the query is leading, and whether the format meets AHIMA and ACDIS query practice guidelines.

A common case scenario presents conflicting documentation - a physician's progress note says one thing, a nurse's note says another, and a lab value points in a third direction. The candidate must determine whether a query is indicated, what the query should ask, and what format is appropriate. Multiple choice distractors will include queries that are clinically logical but non-compliant in structure, or compliant in structure but clinically unsupported by the record as written.

Understanding the Purpose of CDI (Domain 1, 5%) also grounds case scenarios in the right professional frame. Domain 1 establishes that outpatient CDI exists to improve documentation accuracy and completeness - not to drive up codes or influence clinical judgment. Case questions that present ethical edge cases - situations where improving documentation could increase reimbursement but where the clinical indicators do not fully support the documentation change - test whether candidates understand that boundary.

A Realistic Study Plan Built Around Domain 9

Because Domain 9 is integrative, it should not be scheduled first in your study sequence. You need the domain-specific knowledge before you can apply it. A structured approach that maps to the CDEO domain weights looks like this:

Common Errors Candidates Make on Case Questions

Candidates who underperform on Domain 9 consistently make identifiable errors. Recognizing these patterns before your exam date is a form of targeted preparation.

Each of these errors is correctable through targeted practice. The CDEO Domain 9: Cases Complete Study Guide 2026 resources are built specifically to expose these error patterns before they cost you exam points. Pair that preparation with consistent case-based practice through our full CDEO practice exam platform to systematically reduce each error type before test day.

Before you finalize your study schedule, confirm that your testing date, location, and registration deadlines are secured. The CDEO Exam Schedule and Testing Locations 2026 page has current details on available windows - building your Domain 9 study plan backward from a confirmed exam date is far more effective than studying without a deadline anchor.

Frequently Asked Questions