The CDIP exam maps to five domains in AHIMA's published content outline, and the largest share of weight sits in record review and document clarification. That means your study time pays off fastest when you practice judgment tasks: deciding what a record supports, what is missing, which query type fits, and how documentation gaps affect codes and the DRG. Work through paper chart scenarios, write actual queries, and score them against a compliance rubric rather than only rereading guidelines. This guide shows you how, with two worked scenarios and an adaptable sequence.
Reading CDIP items as documentation decisions, not code lookups
CDIP questions frame coding inside a documentation context: what the record supports, what is ambiguous, and how assignment and sequencing change the DRG. Approach every item by asking those three questions before touching an answer choice.
Domain 1 tasks in the content outline include using reference resources, identifying principal and secondary diagnoses, assigning and sequencing ICD-10-CM/PCS codes, applying conventions and guidelines, and understanding working and final DRG assignment. Notice how each task presupposes a record. Practice by pairing every guideline you review with a short paper scenario showing where that guideline changes the code or its sequence.
Build a translation habit: when a stem describes a hospital course, first state the documentation gaps in plain language, then the code consequence, then the query or review action. For example, missing laterality, unspecified acuity, or an absent link between a condition and a complication are documentation problems first. Answering the documentation question usually makes the coding question answerable, and this mirrors how Domain 3 review tasks are written.
- For each practice item, write one sentence naming the documentation gap before selecting an answer.
- After coding practice, state which DRG impact (complication, principal diagnosis change, sequencing) the scenario turned on.
- Review ICD-10-CM Guidelines for Coding and Reporting sections that govern unspecified codes and POA assignment.
Clarification query or clinical validation query: choosing the right tool
A clarification query resolves ambiguous, conflicting, or incomplete documentation; a clinical validation query confirms whether a documented condition is clinically supported. Distinguishing them is a named Domain 5 task and changes both wording and purpose.
Worked scenario 1: a paper record documents 'CHF' with elevated BNP, pulmonary edema on imaging, and IV diuretics, but never states acuity or type. A reviewer sends a binary yes/no message: 'Does the patient have acute decompensated heart failure?' That is the mistake: it suggests an answer, offers no options, and cites no indicators, which is the pattern of a non-compliant leading query that Domain 5 asks you to identify and address.
The better decision is a non-leading multiple-choice clarification query listing clinically reasonable options — for example, acute systolic, acute diastolic, acute on chronic systolic, chronic — each with the supporting indicators cited from the record, and space for the provider to document something else. Why it matters: the acuity answer drives code specificity and DRG impact, and compliant query construction spans Domain 3's best-practice task and Domain 5's non-compliant-query task, so one scenario can be examined from both angles.
| Query type | Purpose | Trigger in the record | Compliant form |
|---|---|---|---|
| Clarification query | Resolve ambiguity, conflict, or incompleteness so code assignment reflects the encounter | Missing acuity, unclear principal diagnosis, conflicting notes | Non-leading, multiple clinically plausible options, indicators cited, provider may add another answer |
| Clinical validation query | Confirm a documented condition is clinically supported | Documentation lacks clinical evidence for a stated diagnosis | Neutral request for confirmation or clarification, no suggested answer, evidence referenced |
| Leading query (non-compliant) | None legitimate | Reviewer suggests a diagnosis the record does not support | Yes/no framing that implies the desired response; must be identified and corrected in workflow |
Prioritizing which records to review first
Domain 3 asks you to identify and prioritize cases in the CDI review process. Prioritization should follow case profiles tied to documentation gaps, quality indicators, and code or DRG impact — not arrival order.
Worked scenario 2: a reviewer works a census strictly first-come, first-served and spends the morning on a short, routine stay while a longer record with possible sepsis and organ dysfunction sits unreviewed. The mistake is treating the queue as neutral. The sepsis record carries higher stakes: documentation of the infection, the organ dysfunction, and their link affects code assignment, severity level, and quality data.
The better decision is to triage by defined criteria drawn from Domain 3 tasks: cases where documentation may not support stated diagnoses (clinical validation opportunities), cases with POA implications, complications, or acuity/chronicity questions, and cases likely to change code assignment or reimbursement. Why it matters: the outline explicitly lists 'identify and prioritize cases' and 'identify gaps in documentation,' so practicing an explicit, criteria-based triage prepares you for both the exam item and the daily workflow it describes.
- Write your own triage checklist from Domain 3 task language: clinical validation, POA, complications, acuity/chronicity, post-discharge query potential.
- Sort a mock census of six paper cases and record a one-line justification for each priority rank.
- Note which cases justify a second-level review rather than a standard query.
Working DRG versus final DRG: what to reconcile and with whom
A working DRG is the provisional assignment during the stay's review; the final DRG reflects completed coding. Domain 1 expects you to spot discrepancies between them and resolve them with coding and HIM staff.
Treat these as two snapshots of the same record. The working DRG may rest on preliminary documentation and CDI review; the final DRG incorporates the completed, coder-assigned codes. The content outline's Domain 1 tasks include communicating with coding and HIM staff to resolve discrepancies between the two and to ensure coding and reimbursement updates are incorporated into practice. That communication step is a tested competency, not background color.
Practice the reconciliation chain on paper: documentation, to assigned codes, to DRG, to the question of which link broke. If the working and final DRGs differ, trace whether the cause is a documentation gap never queried, a query that was never answered, a sequencing difference, or a guideline application issue. Naming the cause determines the fix — a provider education item, a workflow item, or a coding collaboration item — and that diagnostic reasoning is the transferable skill.
Interpreting CDI dashboards without misreading the numbers
Domain 4 covers dashboard metrics, query-process trends, physician benchmarking, and external comparison. Learn what each metric measures and whose perspective it reflects before interpreting any trend.
Core metric families to master: query volume and response rates from the CDI perspective, physician response and agreement rates from the provider perspective, and case-mix or reimbursement impact measures. The outline specifically asks you to track metrics and interpret trends related to the physician query process, noting where CDI and provider perspectives differ. Practice explaining that difference: a low physician agreement rate may reflect query quality, education needs, or case mix rather than physician noncompliance.
Do small arithmetic drills with labeled examples. For instance, if a physician receives 40 queries and agrees with 30, the agreement rate is 75 percent; the learning task is not the division but the interpretation — compare against internal trend and external benchmarks before drawing conclusions, and ask what workflow adjustment the data supports. The outline lists using CDI data to adjust departmental workflow as a task, so end every metric exercise with one concrete workflow implication.
- Define each metric in one sentence before computing it: what it counts, over what denominator, from whose perspective.
- Interpret agreement-rate changes only against both internal trend and external benchmarks, never a single number alone.
- Match every interpreted metric to a possible workflow adjustment, such as education targeting or review criteria revision.
Compliance risk in EHR, CAC, and NLP workflows
Domain 5 asks you to identify risks from technology such as EHRs, computer-assisted coding, and natural language processing, and to manage query retention, timeframes, and second-level reviews within policy.
Study technology risk through concrete failure modes rather than generalities. Copy-forward text can propagate documentation that was never validated, which is precisely where a clinical validation query becomes appropriate. NLP and CAC output can suggest codes the record only weakly supports, so the reviewer's judgment remains the compliance control. The outline also lists identifying situations when second-level reviews are appropriate — practice naming them, such as high-impact diagnoses or weakly supported conditions, from case facts.
Query lifecycle rules are the other compliance pillar: policies on query stages, timeframes, and retention exist to avoid compliance risk, and unanswered queries follow a defined chain of command under Domain 2. On paper scenarios, mark every query with its status — sent, answered, escalated — and note what documentation of the response belongs in the record. This connects compliance (Domain 5) with leadership and policy development (Domain 2) as one system rather than two topics.
A six-week sequence with a query-writing exercise and readiness checks
Sequence study by domain weight and skill transfer: coding practice and review skills first, query craft throughout, then metrics, compliance, and leadership integration, finishing with mixed scenario work and scored self-checks.
An adaptable six-week sequence: weeks one and two, Domain 1 — coding conventions, sequencing, and the working-to-final DRG chain using paper cases; weeks two and three overlap Domain 3 — record review triage, gap identification, and daily query writing; week four, Domain 2 — education delivery methods, physician champions, and policy development framed around your own query examples; week five, Domains 4 and 5 — metric drills plus compliance analysis of your week's queries; week six, mixed scenarios and a full review of your accumulated query log.
Core exercise: take one de-identified paper chart excerpt and write one clarification query and one clinical validation query. Score each against this rubric — non-leading wording (yes/no), all plausible options offered (yes/no), indicators cited from the record (yes/no), provider free-text option included (yes/no), correct query type chosen for the gap (yes/no). Expected observation: check early drafts for yes/no framing or a missing free-text option; if either appears, the rewrite should fix it. Treat a rubric score as a learning milestone, not a passing prediction. Readiness checks: you can trace documentation to DRG impact, state the difference between the two query types in one sentence each, triage a mock census with written justifications, and interpret an agreement-rate trend with a workflow implication.
Note: for administrative details such as eligibility, scheduling, and current exam logistics, rely on AHIMA's official CDIP page and the Candidate Guide rather than secondary summaries.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.