Use this guide as a sequenced companion to your CDIP preparation materials. Concepts are grouped into ten topics ordered from foundations to advanced application, mirroring the credential's five tested domains: clinical coding practice, education and leadership, record review and clarification, metrics, and compliance. Work through each concept's rule, resolved example, and common mistake, then revisit groups where errors cluster. The examples are hypothetical teaching cases, not exam questions, and the guide supplements rather than replaces official preparation resources and current coding guidelines.
CDI Foundations and the CDIP Role
1. CDI Professional Scope of Practice
The CDIP role blends three competencies that must work together: clinical coding ability, knowledge of documentation requirements supporting compliant coding and billing, and enough EHR functionality understanding to know how documentation gets captured. Holders come from health information, nursing, and physician backgrounds, so the common thread is documentation expertise, not a single license.
Example: A nurse moving into CDI must build ICD-10-CM/PCS guideline knowledge and query skills, because the role blends coding rules with clinical record assessment rather than bedside care alone.
Mistake to avoid: Treating CDI as bedside utilization review with no coding or classification responsibility.
Reference: Certified Documentation Improvement Practitioner (CDIP); AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
2. The Five Domains of CDI Practice
The credential tests five domains: clinical coding practice, education and leadership development, record review and document clarification, CDI metrics and statistics, and compliance. Record review carries the largest weight, so preparation should mirror that emphasis while still covering the smaller domains that contain distinct, testable rules.
Example: A learner allocates the most drill time to record review and document clarification because that domain carries the largest percentage weight, then rotates through coding practice questions.
Mistake to avoid: Studying every domain for equal time regardless of its stated weight range.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
3. Working DRG Versus Final DRG
A working DRG is assigned early from preliminary documentation to estimate the encounter's classification, while the final DRG reflects the complete coded record. CDI professionals communicate with coding and HIM staff to resolve discrepancies between the two and to make sure coding and reimbursement updates are incorporated into practice.
Example: A chart's working DRG reflects only day-one documentation; acute kidney injury documented on day three must be verified and communicated so the final DRG captures it.
Mistake to avoid: Letting the working DRG stand without reconciling documentation that appeared later in the stay.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
4. CDI as Liaison Between Coding and Providers
CDI serves as the communication bridge between coding or HIM staff and clinical providers. When coding questions arise from ambiguous terminology, missing linkage, or conflicting entries, the CDI professional facilitates clarification through compliant queries instead of allowing either side to resolve the gap unilaterally or by assumption.
Example: A coder sees the term urosepsis and cannot map it; the CDI specialist opens a provider query rather than leaving the coder to guess at an interpretation.
Mistake to avoid: Letting coders and providers negotiate terminology gaps without a structured CDI process.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
5. Documentation Integrity Beyond Reimbursement
Accurate documentation carries consequences beyond reimbursement: it shapes research data, public health reporting, and case management decisions. CDI education that articulates these downstream effects persuades clinicians that specificity matters for patient populations and safety, not only for the hospital's revenue, which strengthens long-term engagement.
Example: Teaching physicians that specifying diabetes type and control status improves disease surveillance data gives the request a purpose beyond payment.
Mistake to avoid: Justifying the entire CDI program to clinicians on revenue lift alone.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
6. CDI Policy Built on Practice Briefs
CDI policies and procedures should be developed in accordance with AHIMA practice briefs rather than local habit. Facilities must also establish official policy for how query responses are documented in the record, because inconsistent handling of query documentation creates both compliance exposure and unreliable records for future coders and auditors.
Example: A facility adopts a written policy stating every query and its response becomes part of the permanent health record, applied uniformly across all CDI staff.
Mistake to avoid: Running query activity on informal department custom instead of written, brief-aligned policy.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
ICD-10-CM Conventions and Code Assignment
7. Index First, Then Tabular Verification
Code selection always begins in the Alphabetic Index and ends with verification in the Tabular List. The Tabular List contains excludes notes, inclusion terms, and required additional characters that can change or invalidate the index result, so reading and following those instructions during verification is what makes the assignment correct rather than merely plausible.
Example: An index entry points to a code the Tabular List excludes with an instructional note; the note controls, so you follow it and adjust the assignment.
Mistake to avoid: Assigning a code directly from the Alphabetic Index without tabular verification.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
8. The Placeholder Character X
The placeholder character X occupies empty sixth-character positions when a code requires a seventh character but has fewer than six characters of its own. Without the X, the code fails validation and cannot express the episode-of-care detail the classification demands, so the placeholder is structural, not optional formatting.
Example: A laceration code requiring a seventh character for the initial encounter takes a placeholder X in the sixth position so the code length is valid.
Mistake to avoid: Dropping the X and submitting a code that is one character too short.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
9. The 'With' Convention Presumes Causation
When the word with or in appears in a code title, index subterm, or tabular note, the classification presumes a causal or associative relationship between the linked conditions. Code them as related even without provider documentation explicitly connecting them, unless the record clearly states they are unrelated or another guideline, such as the sepsis organ-dysfunction rule, requires documented linkage.
Example: The index links diabetes with neuropathy, so both are coded as related even without an explicit provider linkage, unless the record calls them unrelated.
Mistake to avoid: Querying for linkage the classification itself already presumes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
10. 'And' in Titles Means And/Or
The word 'and' in a code title should be interpreted as either 'and' or 'or.' A combined title covering two sites or two conditions is therefore available when only one of them is documented, which affects whether a single combined code applies or you are over-requiring documentation before using a valid title.
Example: A record documents thrombophlebitis of the left femoral vein with no separate mention of phlebitis; the assignment still comes from the subcategory titled 'Phlebitis and thrombophlebitis,' because the 'and' in the title lets it apply when either condition alone is documented.
Mistake to avoid: Withholding a combined 'and' title because only one of the named conditions appears in the documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
11. Default Codes for Unqualified Diagnoses
A default code is the one printed next to a main term in the Alphabetic Index, representing the most common presentation or the unspecified form. When a condition is documented without qualifying detail, the default code is the correct assignment, and upgrading beyond it requires documentation that actually supports greater specificity.
Example: A discharge summary documents dermatitis with no subtype qualifier; the default code printed beside that main term, the unspecified dermatitis code, is the correct assignment, and selecting atopic or contact dermatitis would require documentation the record does not contain.
Mistake to avoid: Selecting a specific subtype the record never documents.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
12. 'Code Also' Notes Do Not Sequence
A code also note signals that two codes may be required to fully describe a single condition, but it deliberately provides no sequencing direction. The order depends on the circumstances of the encounter, so you must apply principal-diagnosis logic separately rather than reading the note as an instruction about which code comes first.
Example: A code also note for a toxic effect tells you a second code is needed, but the reason for the encounter still sequences first based on circumstances.
Mistake to avoid: Treating a code also note as if it dictated which code is principal.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Provider Documentation Authority
13. Provider Statement Over Clinical Criteria
Code assignment rests on the provider's diagnostic statement that a condition exists, not on the clinical criteria the provider used to reach it. CDI staff and coders cannot withhold or add a diagnosis by re-weighing laboratory values or imaging against the provider's conclusion; if the record contains conflicting statements, the correct action is a query.
Example: A provider documents pneumonia despite an atypical imaging result; the pneumonia code stands because the diagnostic statement governs, not the chart audit.
Mistake to avoid: Suppressing a coded diagnosis because the supporting labs look insufficient to you.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
14. Documentation Exceptions for Non-Provider Clinicians
A short list of data elements may be taken from clinicians other than the patient's provider: BMI, non-pressure ulcer depth, pressure ulcer stage, coma scale, NIH stroke scale, social determinants of health, laterality, blood alcohol level, underimmunization status, and firearm injury intent. The associated diagnosis itself, such as obesity, acute stroke, or an alcohol-related disorder, must still come from the provider, and several of these element codes are secondary-only.
Example: The laboratory reports a blood alcohol level of 0.18 g/dL, and that result supports assigning the blood alcohol level code even though it was documented by a clinician other than the patient's provider; however, any alcohol-related disorder must be documented by the patient's provider before a category F10 code is assigned, and the blood alcohol level code itself may only be reported as a secondary diagnosis.
Mistake to avoid: Coding an associated diagnosis such as an alcohol-related disorder from an allied clinician's data element alone.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
15. Laterality from Other Clinicians
When the patient's provider does not document laterality, code assignment for the affected side may rely on documentation from other clinicians involved in care. If documentation conflicts about the affected side, query the provider. Codes for unspecified side should rarely be used, reserved for situations where clarification is genuinely unobtainable.
Example: A nurse documents a left heel pressure injury while the provider is silent on side; the nurse's laterality supports the specific left-side code.
Mistake to avoid: Defaulting to an unspecified-side code when another clinician already documented the side.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
16. Resolving Conflicting Documentation
When medical record documentation conflicts, whether the conflict comes from the same clinician at different times or from different clinicians, the resolution path is a query to the patient's provider. Choosing between conflicting entries by recency or seniority is not sanctioned; the provider who is legally accountable for the diagnosis is the one who must reconcile the discrepancy.
Example: One progress note says right-sided cellulitis and another says left-sided; a provider query resolves the conflict before any code is assigned.
Mistake to avoid: Picking the most recent entry as authoritative without provider clarification.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
17. Borderline Diagnoses Count as Confirmed
A borderline diagnosis documented at discharge is coded as confirmed, unless the classification provides a specific entry for that borderline condition, as it does for borderline diabetes. Borderline conditions are not uncertain diagnoses, so no inpatient versus outpatient distinction applies; when the documentation is unclear about what borderline means, query for clarification.
Example: A discharge note reads borderline hypertension; because no specific index entry exists for it, the condition is coded as established hypertension.
Mistake to avoid: Dropping a borderline condition as uncertain instead of coding it as confirmed.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
18. Confirmed-Only Diseases Override Inpatient Uncertainty
Certain infectious conditions, including HIV, Zika, and COVID-19, are exceptions to the inpatient rule that allows coding uncertain diagnoses established at discharge. These are confirmed-only: the provider's statement that the condition exists is sufficient confirmation without a positive test, but suspected, possible, probable, or inconclusive wording means the condition itself cannot be coded.
Example: An inpatient note says probable COVID-19; you code the documented fever and cough rather than the confirmed COVID code, despite the inpatient setting.
Mistake to avoid: Coding suspected COVID or HIV as confirmed because the encounter is inpatient.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Principal Diagnosis and Additional Reporting
19. Principal Diagnosis Selection
The principal diagnosis is the condition established after study to be chiefly responsible for occasioning the admission. When a neoplasm mainly occasions the encounter for treatment, the malignancy is principal; when another condition dominates, that condition leads. The determination is made after the workup, not from the admitting symptom alone.
Example: A patient is admitted chiefly for chemotherapy; the primary malignancy is the principal diagnosis even though fatigue prompted the visit.
Mistake to avoid: Sequencing the admitting symptom after a definitive reason has been established.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
20. Guidelines That Override Normal Sequencing
Some guidelines deliberately override ordinary principal-diagnosis logic: obstetric Chapter 15 codes always take sequencing priority, sepsis rules place the systemic infection first, and transplant complication rules can reorder codes. When a specific guideline imposes a sequence, it displaces the general rule about which condition occasioned the admission.
Example: A COVID patient develops sepsis; the sepsis sequencing rules control, so the underlying infection code is sequenced before the COVID code.
Mistake to avoid: Assuming the admission reason always sequences first regardless of chapter rules.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
21. Signs and Symptoms in Lieu of a Diagnosis
When no definitive diagnosis has been established by the end of the encounter, codes for the documented signs and symptoms are reported in place of a definitive diagnosis. Each encounter is coded to the level of certainty actually known at that time, which makes symptom codes a correct final answer rather than a placeholder awaiting something better.
Example: An outpatient workup for cough and fever ends without a diagnosis; code the cough and the fever rather than the condition the clinician suspected.
Mistake to avoid: Coding a suspected diagnosis the provider never confirmed as present.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
22. Appropriate Use of Unspecified Codes
Unspecified codes have acceptable and even necessary uses: when sufficient clinical information is not known or available, the unspecified code is the accurate reflection of what is known at that encounter. It is inappropriate to select a specific code unsupported by documentation or to pursue medically unnecessary diagnostic testing just to obtain a more specific code.
Example: A workup ends with the provider documenting anemia with no type identified; the unspecified anemia code accurately reflects what is known at that encounter, and ordering hemoglobin electrophoresis solely to convert the code to a specific type would be the medically unnecessary testing the guideline prohibits.
Mistake to avoid: Assigning a specific anemia type when no etiology is documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
23. External Cause Codes Are Never Principal
External cause of morbidity codes are supplemental and may never be recorded as the principal diagnosis, or as first-listed in non-inpatient settings. The appropriate injury code is sequenced before any external cause codes, which capture how the injury happened; external cause codes add context but never lead the code set.
Example: A patient is treated for a radial fracture after falling from a ladder at home; the fracture code is sequenced first, and the external cause code identifying the fall is assigned afterward as a supplemental code that can never serve as the principal or first-listed diagnosis.
Mistake to avoid: Sequencing an external cause code as the principal or first-listed diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. Neoplasm Admissions for Treatment
When the malignancy is chiefly responsible for occasioning the admission, such as encounters for treatment of the primary site, the malignancy code is the principal diagnosis. Symptoms and other conditions present during the stay are reported as additional diagnoses, so the treatment purpose, not the incidental findings, drives the first-listed code.
Example: An admission for radiation treatment of a lung primary makes the lung malignancy the principal diagnosis, even with a documented cough during the stay.
Mistake to avoid: Sequencing a symptom like cough above the malignancy being treated.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Sepsis and Infectious Disease Coding
25. Sepsis Needs the Underlying Infection First
Coding sepsis requires a code for the underlying systemic infection sequenced first. When the causal organism is not documented, the unspecified organism sepsis code fills that role. Additional codes for associated organ dysfunction follow, so a sepsis code never stands alone without an underlying infection code leading it.
Example: Sepsis is documented with no organism identified; A41.9 is assigned first, followed by codes for any acute organ dysfunction.
Mistake to avoid: Coding sepsis by itself without an underlying systemic infection code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
26. Severe Sepsis Minimum Code Set
Severe sepsis requires a minimum of two codes: the underlying systemic infection followed by a code from the severe sepsis subcategory, plus additional codes for the associated acute organ dysfunction. The severe sepsis code can never be assigned as principal; when severe sepsis is present on admission and meets the principal definition, the infection code still leads.
Example: Sepsis with acute encephalopathy codes the infection first, then the severe sepsis code, then the encephalopathy; the severe sepsis code never leads.
Mistake to avoid: Assigning the severe sepsis code as the principal diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
27. Urosepsis Is a Nonspecific Term
The term urosepsis is nonspecific and is not considered synonymous with sepsis; it has no default code in the Alphabetic Index. A provider using this term must be queried for clarification before any sepsis or urinary tract infection code is assigned, because guessing at the intended meaning changes both the code set and severity classification.
Example: A note reads urosepsis; because the term has no default code, a query asks whether the provider means sepsis or a urinary tract infection.
Mistake to avoid: Mapping urosepsis directly to a sepsis code without querying.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Negative Cultures Do Not Exclude Sepsis
Negative or inconclusive blood cultures do not preclude a sepsis diagnosis in a patient with clinical evidence of the condition. However, the guideline directs that the provider be queried, so the laboratory result creates a verification step rather than a deletion of the diagnosis from the coded record.
Example: Blood cultures are negative but the provider documents sepsis on clinical grounds; a query confirms the diagnosis before sepsis coding proceeds.
Mistake to avoid: Removing sepsis coding solely because cultures came back negative.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Organ Dysfunction Must Relate to the Sepsis
An acute organ dysfunction must be associated with the sepsis to assign the severe sepsis code. When documentation indicates the dysfunction relates to another medical condition, the severe sepsis code is not assigned; when the relationship is unclear, query the provider rather than assuming the dysfunction is sepsis-related.
Example: Sepsis coexists with acute kidney injury documented as contrast-induced; the severe sepsis code is not assigned because the dysfunction is attributed elsewhere.
Mistake to avoid: Assuming any organ failure during sepsis automatically equals severe sepsis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. MRSA Colonization Versus Infection
MRSA colonization, such as a positive nasal screen, is a carrier state coded to the carrier code and is not itself a disease process. Current MRSA infection uses a combination code when one exists, or the condition code plus the MRSA organism code when it does not; both carrier and infection codes may be assigned when both are documented during the admission.
Example: A positive MRSA nasal screen plus a MRSA wound infection yields both the carrier code and the infection code, since colonization and infection coexist.
Mistake to avoid: Coding a positive MRSA screen as an active MRSA infection.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Confirmed Versus Suspected in Specific Conditions
31. HIV Coding Levels: Disease, Status, Inconclusive
HIV coding has three levels: the HIV disease code for AIDS, HIV disease, or any HIV-related illness; the asymptomatic infection status code for HIV positive without symptoms or related illness; and the inconclusive serology code. Once an HIV-related illness has developed, the HIV disease code is assigned on every subsequent encounter and never reverts to status or inconclusive codes.
Example: A patient previously treated for an HIV-related illness is admitted for a fracture; the fracture is principal and the HIV disease code is secondary.
Mistake to avoid: Assigning the asymptomatic status code to a patient with prior HIV-related illness.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
32. HIV Sequencing by Reason for Admission
When a patient is admitted for an HIV-related condition, the HIV disease code is the principal diagnosis, followed by codes for all reported HIV-related conditions. When a patient with HIV disease is admitted for an unrelated condition such as traumatic injury, the unrelated condition is principal and the HIV disease code is secondary; whether the diagnosis is new or longstanding does not change the sequencing decision.
Example: Admission for HIV-related pneumonia makes the HIV disease code principal, followed by the pneumonia code; a traumatic injury admission reverses that order.
Mistake to avoid: Always sequencing the HIV code first regardless of why the patient came in.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
33. COVID-19: Confirmed Diagnosis Only
The confirmed COVID code is assigned only when the provider documents the diagnosis; a positive laboratory result alone is not enough. For suspected, possible, probable, or inconclusive COVID, code the reported signs and symptoms. For asymptomatic individuals with a positive test and no provider diagnosis, query the provider, who is responsible for confirming and documenting the diagnosis.
Example: An asymptomatic patient tests positive with no provider diagnosis of COVID; a query goes to the provider because a false positive is possible.
Mistake to avoid: Assigning the COVID code from a lab result without provider documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
34. Post-COVID Condition Versus Active Infection
The post-COVID condition code identifies conditions associated with a previous COVID infection and is not assigned for manifestations of an active infection. When a patient has both a condition linked to prior COVID and a new active infection, the active COVID code and the post-COVID code may be assigned together, along with codes for the specific conditions in each category.
Example: A patient with lasting fatigue from prior COVID catches a new active infection; both the active COVID code and the post-COVID condition code are assigned together.
Mistake to avoid: Using the post-COVID code to capture pneumonia from a current infection.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
35. Zika: Confirmed Only, Exposure Code for Suspected
Zika virus disease is coded only when confirmed by the provider's diagnostic statement, which suffices without documentation of the test type. When the provider documents suspected, possible, or probable Zika, do not assign the disease code; instead code the reason for the encounter, such as fever, rash, or joint pain, and add the contact or suspected exposure code when applicable.
Example: A traveler has fever and rash with documentation of possible Zika; code the fever and rash, adding the exposure code, but not the Zika disease code.
Mistake to avoid: Assigning the confirmed Zika disease code for a suspected case.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
36. Complications Need Documented Cause and Effect
Complication coding depends on the provider's documentation of a relationship between the condition and the care or procedure, and the word complication itself is not required. Not every condition arising during or after care qualifies: there must be a cause-and-effect relationship and clinical significance, such as a condition that alters the surgical course as shown in the operative report.
Example: Bleeding alters the operative course per the operative report; the complication code is reported even though the word complication never appears.
Mistake to avoid: Coding every postoperative condition as a complication without a documented relationship.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Query Development and Record Review
37. Clinical Validation Versus Clarification Queries
A clinical validation query challenges whether a documented diagnosis is clinically supported by the indicators in the record, while a clarification query seeks missing detail about a diagnosis already clinically established. Choosing the wrong type wastes the provider's time: validity problems need indicator-level discussion, while specificity problems need option-based clarification.
Example: Documented sepsis lacking supporting clinical indicators triggers a validation query; documented sepsis lacking an organism triggers a clarification query instead.
Mistake to avoid: Sending a clarification query when the real issue is clinical validity of the diagnosis.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline; CDC ICD-10-CM Official Guidelines, FY 2027
38. Identifying Non-Compliant Queries
Non-compliant queries introduce new diagnoses without clinical support or steer the provider toward a desired answer, and identifying them is an explicit CDI workflow task. A compliant query presents the clinical evidence found in the record and asks the provider to interpret it, rather than embedding the financially favorable conclusion in the question or its options.
Example: A query reading 'is this sepsis due to the urinary tract infection?' with only agree options is leading; it is rewritten around open clinical indicators.
Mistake to avoid: Embedding a target diagnosis in query options without documented clinical basis.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
39. Documenting Query Responses in the Record
Strategies for obtaining responses must ensure the provider's answer is documented in the health record, and each facility sets its own official policy for how query responses appear there. A verbal answer that never enters the record cannot support code assignment, so the CDI process must convert every response into record documentation through the sanctioned mechanism.
Example: A provider answers a query verbally on rounds; the CDI specialist ensures the answer is entered into the health record as facility policy requires.
Mistake to avoid: Accepting verbal query answers that never become part of the record.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
40. POA Indicators Apply to the Final Code Set
Present on Admission guidelines apply the POA indicator to the final set of assigned codes, after Sections I through III have determined what is coded. Documentation from any provider involved in the care and treatment may support whether a condition existed at admission, so the POA determination is broader than the attending physician's own notes.
Example: The emergency department note establishes that encephalopathy was present on admission, even though the hospitalist first documented it two days later.
Mistake to avoid: Assigning POA indicators before the final diagnosis codes are settled.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
41. Post-Discharge Query Opportunities
Query opportunities do not end at discharge. Reviewing the completed record can reveal documentation gaps that affected code assignment, and post-discharge queries capture the provider's clarification after the patient has left. This step recovers accuracy for the final coded record even though the patient is no longer on site.
Example: After discharge, the labs reveal acute renal failure never addressed in progress notes; a post-discharge query asks the provider to confirm or rule it out.
Mistake to avoid: Assuming the CDI review window closes when the patient is discharged.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
42. Escalating Unanswered Queries
CDI programs need a recognized chain of command for resolving unanswered queries. When a provider does not respond through normal channels, escalation follows a defined path, such as to a physician advisor or department leadership, so that documentation gaps are formally addressed rather than silently closed or left to distort the coded record.
Example: After repeated unanswered queries on a documentation gap, the CDI specialist escalates through the chain to the department chair for resolution.
Mistake to avoid: Closing unanswered queries silently without following the escalation path.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
Education and Leadership Development
43. Engaging Physician Champions
Physician champions are clinicians who lend credibility to CDI initiatives inside their own specialty. Collaborating with them means peer-to-peer messaging about documentation standards, which lands differently than feedback from administrative staff; a champion translating CDI goals into departmental practice sustains engagement that external pressure cannot.
Example: A hospitalist champion presents sepsis documentation feedback at a department meeting, and query response rates improve that quarter.
Mistake to avoid: Pushing CDI initiatives through administrative channels with no physician allies.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
44. Matching Education to Audience and Method
Effective CDI education requires identifying both the right topics and the right delivery methods for the specific audience. A surgeon group, a coding team, and nursing staff have different documentation responsibilities and learning constraints, so the same material must be reshaped in depth, format, and clinical framing for each group to actually change behavior.
Example: Surgeons receive two-minute case-based huddle tips while coders attend a full guideline workshop; the content matches each audience's role.
Mistake to avoid: Delivering identical lectures to every audience regardless of role.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
45. Promoting CDI to Administration and the System
Promoting CDI efforts throughout the organization, including administration, is a distinct leadership task. Program survival depends on executives understanding what CDI accomplishes, so results must be translated into leadership-relevant terms and delivered on a rhythm, rather than expecting the work to speak for itself inside HIM.
Example: Quarterly CDI results go to executive leadership with trend interpretation, keeping the program visible and funded beyond the HIM department.
Mistake to avoid: Keeping CDI reporting confined to the HIM department.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
46. Building Multidisciplinary Relationships
Creating and nurturing working relationships across multidisciplinary teams is an ongoing task, not a one-time introduction. Case management, coding, nursing, and physician teams each hold pieces of the documentation picture, and durable relationships mean information flows proactively between them instead of surfacing only during audits or disputes.
Example: A CDI specialist joins case management huddles to align acuity documentation with discharge planning, catching severity gaps in real time.
Mistake to avoid: Working in isolation from case management, coding, and clinical teams.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
47. Developing Documentation Improvement Projects
Documentation improvement projects target specific, measurable gaps rather than general quality aspirations. A well-built project defines the documentation problem, the intervention, and the before-and-after measurement, so the program can demonstrate which educational or workflow changes actually moved the metric and deserves scaling.
Example: A project targets encephalopathy specificity, measuring documentation rates before and after focused education to prove the intervention worked.
Mistake to avoid: Launching projects without a defined, measurable documentation target.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
48. Naming the Stakeholder Who Uses the Documentation
Accurate documentation and coding feed four distinct downstream uses: research, public health reporting, case management, and reimbursement. Education lands harder when each documentation request names the specific stakeholder whose work depends on the element being requested: registries and researchers rely on diagnostic specificity, public health reporting relies on complete condition capture, and case management relies on coded acuity. Tailoring the 'why' to the stakeholder makes the request concrete instead of a generic list of benefits.
Example: When a hospitalist asks why present-on-admission indicators and acuity detail matter for a patient cleared for discharge, the CDI specialist names two concrete users of that data: case management, which relies on coded acuity to arrange appropriate post-acute placement, and public health reporting, which uses the same coded conditions for surveillance, neither of which involves the hospital's revenue.
Mistake to avoid: Answering every documentation question with a reimbursement rationale instead of naming the stakeholder who actually uses the data.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
CDI Metrics and Statistics
49. Monitoring Dashboard Metrics
Common dashboard metrics exist to monitor CDI departmental performance, and their value comes from interpretation and response. A dashboard that is populated but never acted on is decoration; the professional's job is to recognize which metric movement signals a process problem, a staffing issue, or a documentation trend needing education.
Example: A monthly dashboard shows query response rate dipping; the dip triggers a workflow review rather than just being filed as a statistic.
Mistake to avoid: Collecting dashboard numbers without acting on the trends they reveal.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
50. Query Metrics from Two Perspectives
Query process metrics must be tracked and interpreted from both the CDI perspective and the provider perspective. The two sides can count the same activity differently, and reconciling those views reveals whether perceived provider burden reflects real volume, duplicate queries, or routing problems that the CDI team can eliminate.
Example: CDI counts queries sent while providers count queries received; the differing tallies expose a routing or duplication problem worth fixing.
Mistake to avoid: Evaluating provider burden using only the CDI-side query count.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
51. Physician Benchmarking and Trending
Tracking and interpreting data for physician benchmarking means comparing individual clinicians' documentation and query behaviors against peers and over time. The purpose is targeted education and trend detection, so the data must be interpreted in context, such as specialty mix and patient complexity, before drawing conclusions about any individual physician.
Example: Comparing individual physicians' response times against peer norms identifies who needs targeted education, presented privately rather than as a ranking.
Mistake to avoid: Publicly ranking physicians instead of using trends for private targeted education.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
52. External Benchmark Comparison
Comparing the institution with external institutional benchmarks places internal performance in context. A metric that looks weak against the hospital's own history may be normal for its program age and case mix, or vice versa; external comparison is what distinguishes a genuine performance problem from an artifact of local expectations.
Example: The hospital's query agreement rate is compared against peer facility benchmarks, revealing the program is newer and needs different goals.
Mistake to avoid: Judging CDI performance only against the facility's own internal history.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
53. Quality Audits of CDI Content
Quality audits of CDI content check whether queries, responses, and documentation practices comply with institutional policies and procedures or national guidelines. Auditing only the coded output while ignoring the query content itself misses the primary compliance exposure, because non-compliant query language contaminates everything downstream of it.
Example: A quarterly audit samples queries for leading language and checks retention compliance against written policy, with findings fed back to staff.
Mistake to avoid: Auditing coded output while never reviewing the queries that produced it.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
54. Using Data to Adjust Workflow
CDI data should drive departmental workflow adjustments. When metrics show that documentation opportunities concentrate at particular points in the stay, or that certain unit types generate disproportionate queries, staffing and review priorities should shift accordingly; a fixed workflow maintained against the evidence wastes review capacity.
Example: Data shows clarification opportunities cluster in the first 48 hours, so staff are reallocated to early review instead of spread evenly.
Mistake to avoid: Keeping fixed review priorities regardless of what the CDI data shows.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
Compliance, Privacy, and Technology Risk
55. Who Counts as a HIPAA Covered Entity
The Privacy Rule covers health plans, health care clearinghouses, and health care providers that transmit health information electronically in connection with standard HIPAA transactions such as claims and eligibility inquiries. Simply using email or an EHR does not make a provider covered; the trigger is transmitting information in connection with a standard transaction, directly or through a billing service.
Example: A clinic that only emails appointment reminders is not covered by that fact alone, while a hospital billing electronic standard claims is.
Mistake to avoid: Assuming any EHR or email use automatically makes a provider a covered entity.
Reference: HHS Summary of the HIPAA Privacy Rule
56. PHI and the De-Identification Standard
Protected health information is individually identifiable health information in any form, electronic, paper, or oral. De-identified information, achieved by removing specified identifiers with no actual knowledge of re-identifiability, carries no use restrictions. A limited data set is a different, lesser standard that still requires a data use agreement, so the two must not be conflated.
Example: Removing names, full dates, and small-area geography lets a dataset support benchmarking without authorization, but a limited data set is not de-identified.
Mistake to avoid: Treating a limited data set as if it were fully de-identified health information.
Reference: HHS Summary of the HIPAA Privacy Rule
57. The Minimum Necessary Standard
Covered entities must make reasonable efforts to use, disclose, and request only the minimum PHI needed for the purpose, and may not send an entire medical record unless the whole record is specifically justified. The standard does not apply to disclosures for treatment, to the individual, under authorization, to HHS enforcement, or when required by law.
Example: A CDI metrics report uses aggregate counts rather than full records, because operational reporting must stay within minimum necessary limits.
Mistake to avoid: Sending whole records for operational reporting without a documented justification.
Reference: HHS Summary of the HIPAA Privacy Rule
58. Permitted Uses Versus Required Authorizations
A covered entity may use and disclose PHI without individual authorization for its own treatment, payment, and health care operations, including quality assessment and compliance activities. Uses outside these categories, such as disclosures to a life insurer, an employer for a pre-employment physical, or a pharmaceutical firm's marketing, require a written authorization meeting the Rule's content requirements.
Example: An internal CDI quality review proceeds as health care operations without authorization, but sending results to a life insurer requires written authorization.
Mistake to avoid: Releasing PHI to an employer or insurer for non-TPO purposes without authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
59. Technology Risk: EHR, NLP, and CAC
CDI compliance includes identifying risks associated with technology, including EHRs, natural language processing, and computer-assisted coding. These tools can propagate copy-forward documentation, misread negation, or suggest codes unsupported by clinical evidence, so technology output must be validated against the actual record rather than treated as authoritative.
Example: Computer-assisted coding proposes a sepsis code from copy-forward text; the CDI specialist validates the indicators before any query is generated.
Mistake to avoid: Accepting auto-suggested codes without validating the underlying documentation.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
60. Knowing When Second-Level Reviews Apply
Certain situations warrant second-level reviews: high-impact code changes, disputed clinical validation, or recurring discrepancies between working and final DRGs. A defined escalation to a senior reviewer adds a check before contentious documentation changes become final, protecting both the record's integrity and the program's defensibility.
Example: A contested clinical validation query on a high-impact DRG goes to a senior CDI or coding reviewer before the record is finalized.
Mistake to avoid: Letting a single reviewer's judgment finalize contentious, high-impact documentation changes.
Reference: AHIMA: Certified Documentation Improvement Practitioner (CDIP) exam content outline
References and further reading
Source links checked on Oct 2, 2026.