This guide organizes sixty teaching concepts into ten sequenced groups, moving from CDI program foundations and record requirements through privacy, compliance, queries, quality measures, MS-DRG payment, and ICD-10-CM/PCS application. Study the groups in order, since later material assumes earlier distinctions. Each concept pairs a rule with a resolved hypothetical example and a common mistake, so you can self-test decisions rather than memorize definitions. Use it alongside the official study guide, the ICD-10-CM Official Guidelines, and current code books.
CDI Program Foundations and the CDEI Role
1. CDEI Role: Proactive Review Versus Final Coding
The CDEI performs preliminary and ongoing chart reviews, assigns working ICD-10-CM and ICD-10-PCS codes to establish a working MS-DRG, and clarifies clinical indicators, diagnosis support, and POA status; the coding department verifies and finalizes what is actually reported.
Example: A CDEI assigns a working DRG for a GI bleed stay but flags missing MCC support; the coder later finalizes after the query response resolves the documentation gap.
Mistake to avoid: Treating the CDEI's preliminary codes as final billed codes that bypass coding department verification.
Reference: AAPC CDEI study guide sample
2. CDI Purpose: Care Quality Before Revenue
The central focus of clinical documentation is demonstrating quality of care with detail and accuracy; programs designed mainly to maximize revenue create compliance risk, especially if they lead providers or the facility toward upcoding. Accurate CMI follows from supporting documented conditions, treatment, and outcomes.
Example: A hospital CDI mission statement emphasizing severity capture to raise reimbursement is reworded to emphasize documented clinical support, because a revenue-first design invites upcoding findings.
Mistake to avoid: Building CDI metrics around revenue lift rather than documentation accuracy and integrity.
Reference: AAPC CDEI study guide sample
3. Front-End CDI Prevents Deficiencies
CDI should begin at the front end of all services and care, so prevention of documentation deficiencies is the key; the CDEI develops and monitors policies affecting the documentation process and works with everyone in the facility who plays a role in documenting.
Example: A CDEI builds an admission checklist prompting providers to record POA status and laterality up front, preventing retrospective queries and deficient records at discharge.
Mistake to avoid: Waiting until discharge to review charts, which converts preventable deficiencies into costly queries and denials.
Reference: AAPC CDEI study guide sample
4. Measurable Benefits of an Effective CDI Program
Benefits of an effective CDI program include supporting ICD-10-CM and PCS code selection, proper MS-DRG reimbursement, improvement in quality measures, avoidance of denials, superior physician communication, decreased physician queries, and opportunity for internal growth.
Example: After a year of concurrent reviews, a hospital's denial rate falls and repeat queries on sepsis documentation drop because providers now link indicators to diagnoses.
Mistake to avoid: Judging CDI success only by reimbursement change while ignoring denial and query trends.
Reference: AAPC CDEI study guide sample
5. Records Serve Many Non-Reimbursement Requestors
Medical record requests come from CMS contractors, patients, attorneys, other providers, workers' compensation, payers for precertification, pre-employment applications, military applications, and SSI applications; the record must therefore stand up to scrutiny far beyond billing purposes.
Example: An SSI application reviewer relies on the hospital record to verify impairment; incomplete progress notes weaken the patient's claim regardless of correct billing.
Mistake to avoid: Assuming the chart only matters to coders and payers, and letting non-billing entries deteriorate.
Reference: AAPC CDEI study guide sample
6. CMI Reflects Severity, Not Coding Aggressiveness
Inpatient reimbursement correlates to case mix index because CMI reflects the severity of procedures and care required; MS-DRG selection depends on the principal diagnosis, CC and MCC conditions, and surgical procedures, so documentation drives severity, never coder inference.
Example: A stay documents only sepsis without organ dysfunction support; the CDEI queries rather than assuming severe sepsis, keeping the CMI defensible.
Mistake to avoid: Chasing a higher CMI by assigning severity levels the record never actually documents.
Reference: AAPC CDEI study guide sample
Medical Record Requirements and Legal Integrity
7. Four Functions Every Record Must Fulfill
Per the CMS Interpretive Guidelines for section 482.24, a medical record should identify the patient, support the diagnosis or condition, justify the treatment, and document the course and results of treatment; every entry can be measured against these four functions.
Example: A progress note listing medications without describing response to therapy fails the course-and-results function, prompting a documentation deficiency flag at review.
Mistake to avoid: Auditing only for diagnoses present, while ignoring whether treatment course and results are documented.
Reference: AAPC CDEI study guide sample
8. Conditions of Participation: Justify Admission and Continued Stay
Under the Condition of Participation for medical record services, the record must contain information to justify admission and continued stay; hospitals must meet these standards to participate in Medicare, making admission and stay documentation a compliance requirement, not a courtesy.
Example: A utilization reviewer cannot find documentation supporting continued stay on day four; the CDEI prompts the provider to record ongoing acute needs.
Mistake to avoid: Letting continued-stay documentation lapse after a thorough admission note was written.
Reference: AAPC CDEI study guide sample
9. Dangerous Abbreviations: Write Unit, Not U
The abbreviation U or u for unit can be mistaken for zero, the number four, or cc, so the word unit should be written instead; standardized formats for numeric values add precision that reduces the risk of error in medication doses and laboratory values.
Example: An order reading 6U insulin is corrected to 6 units because U could be misread as 0 or 4, changing the dose tenfold.
Mistake to avoid: Accepting U, u, or other error-prone abbreviations in orders during record review.
Reference: AAPC CDEI study guide sample
10. Trailing Zero Rules Differ by Context
A trailing zero may be used only when required to demonstrate the level of precision of a reported value, such as laboratory results, imaging lesion sizes, or catheter and tube sizes; it may never be used in medication orders or other medication-related documentation.
Example: A lab result of 5.0 mmol/L is acceptable precision, but a medication order of 5.0 mg must be rewritten as 5 mg to prevent tenfold errors.
Mistake to avoid: Applying lab-style precision conventions to medication orders, where trailing zeros are prohibited.
Reference: AAPC CDEI study guide sample
11. Copy-Paste and Template Cloning Hazards
Copying previous notes can import outdated or inaccurate information into the current note, causing inaccurate coding and billing; pre-filled templates applied to all patients without individualization to the specific condition produce the same defect and compliance exposure.
Example: A cloned cardiac note repeats no chest pain from last admission despite today's documented angina; the CDEI flags the contradiction for correction.
Mistake to avoid: Treating cloned text as current clinical findings without verifying against this encounter's data.
Reference: AAPC CDEI study guide sample
12. The Record as Legal Evidence of Care
The medical record is a legal document that validates level of care, medical necessity for services provided, coding accuracy, and identity of the provider; it is the only evidence of the clinician's veracity and the quality of care the facility delivered.
Example: In a malpractice dispute, the hospital relies on timed, signed entries showing who evaluated the patient and why transfer was medically necessary.
Mistake to avoid: Leaving entries unsigned, untimed, or unattributed, which undermines the record's evidentiary value.
Reference: AAPC CDEI study guide sample
HIPAA Privacy and Information Handling
13. Who Is a Covered Entity
The Privacy Rule applies to health plans, health care clearinghouses, and any health care provider that transmits health information electronically in connection with standard HIPAA transactions such as claims or eligibility inquiries; hospitals and physicians billing electronically are covered.
Example: A small physician practice submitting electronic claims through a billing service is still a covered entity because transmission occurs on its behalf.
Mistake to avoid: Assuming a provider escapes coverage because a third-party biller handles its electronic transactions.
Reference: HHS Summary of the HIPAA Privacy Rule
14. PHI Spans Every Medium
Protected health information is individually identifiable health information held or transmitted by a covered entity or its business associate in any form — electronic, paper, or oral — including demographic data relating to health, care, or payment for care.
Example: A hallway conversation naming a patient and diagnosis is a disclosure of PHI just as much as a faxed chart page.
Mistake to avoid: Limiting privacy safeguards to electronic records while ignoring verbal and paper disclosures.
Reference: HHS Summary of the HIPAA Privacy Rule
15. Minimum Necessary and Its Exceptions
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; treatment, individual access, authorization, HHS, and legally required disclosures are exempt.
Example: A payer requests the full record for a single-stay review; the hospital sends the relevant encounter documentation because the whole record is not justified.
Mistake to avoid: Routinely releasing entire charts for payment purposes when a narrower set suffices.
Reference: HHS Summary of the HIPAA Privacy Rule
16. Treatment, Payment, Operations Without Authorization
A covered entity may use and disclose PHI without individual authorization for its own treatment, payment, and health care operations, including quality assessment, credentialing, audits, and compliance programs; psychotherapy notes generally require authorization even for these purposes.
Example: The hospital's CDI staff review a chart concurrently for quality improvement without patient authorization because this is a health care operation.
Mistake to avoid: Treating psychotherapy notes like ordinary records usable for payment and operations without authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
17. De-Identification Removes Restrictions
De-identified information, which neither identifies nor provides a reasonable basis to identify an individual, carries no use or disclosure restrictions; it is achieved either by a qualified statistician's formal determination or by removing specified identifiers with no actual knowledge of re-identifiability.
Example: A CDI educator strips names, dates, and identifiers from sample charts for training materials, relying on the safe-harbor removal method with no knowledge of re-identification.
Mistake to avoid: Removing only the patient name and assuming the record is de-identified under safe harbor.
Reference: HHS Summary of the HIPAA Privacy Rule
18. Only Two Disclosures Are Required
A covered entity must disclose PHI in only two situations: to individuals or their personal representatives when they request access or an accounting of disclosures, and to HHS when it undertakes compliance investigation, review, or enforcement; all other permitted disclosures are optional.
Example: A patient demands the hospital send records to an insurer; the hospital may do so under other rules, but only the access request itself is mandatory.
Mistake to avoid: Believing public-interest permissions, such as public health reporting, obligate disclosure rather than permit it.
Reference: HHS Summary of the HIPAA Privacy Rule
Fraud, Abuse, and Federal Compliance
19. Fraud Versus Abuse Under CMS Definitions
CMS defines fraud as knowingly making false statements or misrepresenting facts to obtain an undeserved benefit or payment from a federal healthcare program; abuse is action resulting in unnecessary costs to such a program, directly or indirectly, without the knowing falsity element.
Example: Billing a higher level than provided reflects fraud; routinely ordering unnecessary but honestly believed services reflects abuse, which changes the compliance response.
Mistake to avoid: Using fraud and abuse interchangeably, which misstates the knowledge element central to each.
Reference: AAPC CDEI study guide sample
20. FCA Liability Requires Knowing Conduct
The False Claims Act is violated not merely by submitting a false claim but by submitting or causing submission with knowledge of falsity; knowing includes deliberate ignorance or reckless disregard of truth, and liability can exist even without any intent to defraud.
Example: A supervisor ignores repeated warnings that cloned notes inflate visit levels and submits the claims anyway; reckless disregard satisfies the knowing standard.
Mistake to avoid: Assuming an upcoding scheme is safe because no one intended to defraud.
Reference: AAPC CDEI study guide sample
21. Qui Tam Whistleblower Mechanics
A relator files a qui tam action for themselves and the United States; the complaint is served on the government and filed under seal, the Department of Justice has 60 days to investigate and decide whether to intervene, and the relator may proceed alone if it declines.
Example: A coder reports systematic DRG upcoding; after DOJ intervenes and recovers funds, the relator receives a percentage of the proceeds as the reward.
Mistake to avoid: Thinking a declined intervention ends the case; the relator can pursue it alone.
Reference: AAPC CDEI study guide sample
22. Reverse False Claims
The reverse false claims provision creates liability when a person knowingly conceals or improperly avoids or decreases an obligation to pay money to the government; keeping overpayments rather than returning them is the classic healthcare example of this theory.
Example: A hospital discovers audit-identified DRG overpayments but delays repayment; the continued retention creates reverse false claims exposure, even though no new claim was submitted.
Mistake to avoid: Focusing compliance reviews only on false submissions while ignoring obligations to return overpayments.
Reference: AAPC CDEI study guide sample
23. Recognizing Fraudulent Billing Patterns
Healthcare conduct subject to the False Claims Act includes billing for services not furnished, altering claim forms for higher payment, misrepresenting diagnoses to justify payment, upcoding, unbundling, falsifying chart notations, submitting claims for expired drugs, and billing physician services by non-physician providers without incident-to compliance.
Example: A clinic bills a physician visit although only a medical assistant saw the patient, ignoring incident-to requirements; this is a false claim.
Mistake to avoid: Treating upcoding or unbundling as mere billing errors rather than potential FCA conduct.
Reference: AAPC CDEI study guide sample
24. Audits and Recoupment of Incorrect DRGs
CMS and the OIG routinely conduct audits to detect overpayments; data errors, intentional or not, that place an admission in a higher-paying MS-DRG can result in Medicare recouping some or all payments, and recovery audit contractors actively pursue such findings.
Example: An audit finds an unsupported MCC moved a stay to a higher-weighted DRG; the hospital repays the difference and re-educates providers.
Mistake to avoid: Assuming unintentional coding errors carry no recoupment or audit consequence for the facility.
Reference: AAPC CDEI study guide sample
Physician Queries and Provider Communication
25. When a Query Is Appropriate
Complete concurrent queries when documentation does not support a diagnosis or procedure, when a deficiently documented diagnosis or procedure needs practitioner clarification, or when record documentation conflicts; queries resolve uncertainty rather than suggest conclusions the clinician has not reached.
Example: A discharge summary lists encephalopathy, but the nursing notes record consistently normal mental status and no provider assessment describes confusion or asterixis; the CDEI queries whether the diagnosis stands instead of coding it.
Mistake to avoid: Coding an unsupported diagnosis silently instead of querying the provider for clarification.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
26. Building a Compliant, Non-Leading Query
A compliant query presents the clinical indicators from the record and asks an open question with clinically reasonable options, including the ability to state that no diagnosis applies; it must not lead the provider toward a specific diagnosis or a reimbursement outcome.
Example: On postoperative day two a patient spikes a fever with a new infiltrate on chest imaging and a rising white count; the query lists these indicators alongside the accepted clinical definition of pneumonia and asks the provider to state which diagnosis applies, or that none applies, without suggesting an answer or a reimbursement outcome.
Mistake to avoid: Phrasing queries as yes-or-no confirmations of the higher-severity diagnosis you want.
Reference: AAPC CDEI study guide sample
27. Borderline Diagnoses Are Coded as Confirmed
When the provider documents a borderline diagnosis at discharge, it is coded as confirmed unless the classification provides a specific entry for the borderline condition, in which case that specific entry is assigned instead. Borderline conditions are not uncertain diagnoses, so no distinction is made between inpatient and outpatient settings, and coders are encouraged to query whenever the borderline documentation is unclear.
Example: A discharge note reads borderline diabetes; the Alphabetic Index provides a specific entry for the borderline condition, so that entry is assigned rather than a confirmed diabetes code, while a borderline condition with no specific entry would be coded as confirmed at discharge.
Mistake to avoid: Treating a documented borderline diagnosis as suspected or unconfirmed and dropping it from the claim.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Code From the Provider's Diagnostic Statement
Code assignment is based on the provider's diagnostic statement that the condition exists; clinical criteria used by the provider to establish the diagnosis do not govern code assignment, and conflicting medical record documentation requires a query rather than coder adjudication.
Example: A provider documents pneumonia despite atypical imaging; the coder assigns the pneumonia code because the statement controls, not the diagnostic criteria.
Mistake to avoid: Second-guessing a documented diagnosis by re-applying clinical criteria on your own.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Laterality and Conflicting Clinician Documentation
When the patient's provider does not document laterality, code assignment may rely on documentation from other clinicians; if record documentation conflicts about the affected side, query the provider, and use unspecified-side codes rarely, only when clarification is impossible.
Example: Nursing notes say left ulcer while the physician writes right; the CDEI queries the provider rather than picking either side.
Mistake to avoid: Defaulting to an unspecified laterality code when a simple query would resolve the side.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Clinical Indicators Versus Clinical Definitions
Effective queries pair the record's clinical indicators — labs, findings, imaging — with accepted clinical definitions of the candidate condition, letting the provider judge whether the definition is met; the CDEI supplies evidence and definitions, never the diagnostic conclusion.
Example: A query attaches fever, infiltrate, and hypoxia alongside the sepsis definition, asking the provider to confirm or refute that diagnosis for this patient.
Mistake to avoid: Citing indicators without the clinical definition, leaving the provider without a decision standard.
Reference: AAPC CDEI study guide sample
Quality Measures and Present on Admission
31. POA Definition Anchors to the Admission Order
Present on admission means present at the time the order for inpatient admission occurs; conditions that develop during an outpatient encounter, including the emergency department, observation, or outpatient surgery before the admission order, are considered present on admission for POA purposes.
Example: A patient's pneumonia is diagnosed in the ED just before the inpatient order; POA is Y because it developed before admission was ordered.
Mistake to avoid: Assigning N to conditions that arose in the ED or observation before the admission order.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
32. Choosing Among Y, N, U, and W Indicators
Assign Y when the provider documents the condition present on admission or diagnosed earlier; N when explicitly not present; U only in very limited circumstances when documentation is unclear; W when the provider states it cannot clinically be determined at admission.
Example: Nothing in the chart indicates when a stage 3 ulcer appeared; after an unproductive query, U is assigned rather than a guessed N.
Mistake to avoid: Routinely defaulting to U instead of querying when POA documentation is unclear.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
33. Suspected at Admission, Confirmed Later
Diagnoses subsequently confirmed after admission are considered present on admission when, at admission, they were documented as suspected, possible, rule out, or differential, or constitute an underlying cause of an admission symptom; there is no required timeframe for reaching the definitive diagnosis.
Example: Sepsis is suspected on day one and confirmed by culture on day three; POA is Y because suspicion was documented at admission.
Mistake to avoid: Assigning N merely because confirmation came days after the admission order.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
34. POA Exempt Codes and Blank Fields
Certain ICD-10-CM codes are exempt from POA reporting because they describe circumstances of the encounter or conditions always present on admission; the POA field may be left blank only for these exempt codes, and no indicator is reported for conditions that would not be coded at all.
Example: A Z-code for a circumstance rather than a current disease is on the exempt list; the facility leaves the POA field blank.
Mistake to avoid: Leaving POA blank for ordinary diagnoses, which is permitted only for exempt codes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
35. Hospital-Acquired Conditions and Quality Programs
Hospital-acquired conditions reflect harm arising during the stay rather than on admission, which is why POA accuracy matters; quality frameworks including value-based purchasing, Joint Commission accountability measures, star ratings, HEDIS, and readmission reduction programs all draw on documented inpatient data.
Example: A fall with injury on day five is flagged as hospital-acquired because POA was documented as N, affecting quality reporting.
Mistake to avoid: Treating quality measure data as separate from the coded record that feeds it.
Reference: AAPC CDEI study guide sample
36. Working Denials Into Provider Education
The CDEI reviews denials with revenue cycle, responds to them, and works with practitioners to improve documentation going forward; denial patterns are a primary source of targeted provider education because they reveal exactly where documented support fell short.
Example: Repeated medical-necessity denials for a procedure prompt a documentation tip sheet specifying indication statements providers must include, reducing future denials.
Mistake to avoid: Handling denials purely as appeals while never converting their root causes into education.
Reference: AAPC CDEI study guide sample
IPPS and MS-DRG Assignment
37. Grouper Logic Sequence
The grouper first tests for pre-MDC qualification such as tracheostomy, ECMO, or major organ transplant; otherwise the principal diagnosis places the encounter in an MDC, a valid OR procedure selects the surgical section, then CC/MCC conditions, gender, discharge disposition, and neonatal gestational age refine the DRG.
Example: A major organ transplant admission groups to a pre-MDC DRG immediately, so the later MDC and CC analysis steps are entirely disregarded.
Mistake to avoid: Skipping the pre-MDC check and grouping a transplant case through the standard MDC path.
Reference: AAPC CDEI study guide sample
38. DRG 999: The Ungroupable Claim
Invalid ICD-10-CM codes, invalid age, incorrect sex, or an invalid discharge disposition submitted on a claim produce DRG 999, Ungroupable, which reimburses zero dollars and is returned to the facility for correction and resubmission before any payment is made.
Example: A claim for a male patient carries a diagnosis code valid only for pregnancy; the grouper assigns DRG 999, Ungroupable, which reimburses zero dollars, and the claim is returned to the facility for correction and resubmission before any payment is made.
Mistake to avoid: Assuming an incomplete code still groups; it must be complete and valid before submission.
Reference: AAPC CDEI study guide sample
39. Principal Diagnosis Under UHDDS
The principal diagnosis is defined in the Uniform Hospital Discharge Data Set as the condition established after study to be chiefly responsible for occasioning the admission of the patient for care; the circumstances of inpatient admission always govern its selection, not which condition pays most.
Example: A patient admitted for chest pain is studied and found to have a STEMI; the STEMI becomes the principal diagnosis for grouping.
Mistake to avoid: Choosing the principal diagnosis by reimbursement weight instead of what occasioned the admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
40. CC and MCC Documentation Drives DRG Weight
MS-DRG selection depends on the principal diagnosis plus conditions treated during the stay classifiable as complications or comorbidities or major complications or comorbidities, and on surgical procedures; relative weights differ across with-MCC, with-CC, and without tiers for the same clinical group.
Example: Appendix procedure DRGs split into with-MCC, with-CC, and without tiers; documenting a supported CC moves the claim into the middle tier.
Mistake to avoid: Reporting a CC or MCC that lacks documented clinical support in the record.
Reference: AAPC CDEI study guide sample
41. Special IPPS Payment Adjustments
Beyond base DRG payments, IPPS provides additional payments through disproportionate share hospital status for qualifying facilities serving low-income patients, indirect medical education adjustments for approved teaching hospitals, outlier payments, and new technology add-ons; each has its own qualification path.
Example: A teaching hospital with an approved graduate medical education program receives an IME adjustment reflecting its resident-to-bed ratio and multiplier.
Mistake to avoid: Treating these payment adjustments as automatic rather than tied to qualifying facility status.
Reference: AAPC CDEI study guide sample
42. Outlier Payments for Extraordinary Costs
Encounters whose costs extraordinarily exceed the average for the MS-DRG may earn an outlier payment when costs exceed a fixed-loss cost threshold; the hospital's Medicare-approved charges are converted to costs using a cost-to-charge ratio and compared against that threshold.
Example: A prolonged ICU stay with charges converted via the cost-to-charge ratio exceeds the fixed-loss threshold, triggering an outlier payment for excess costs.
Mistake to avoid: Assuming any expensive stay qualifies; only costs above the fixed-loss threshold count.
Reference: AAPC CDEI study guide sample
ICD-10-CM Diagnosis Coding Rules
43. Index First, Then Tabular Verification
Locate the documented term in the Alphabetic Index, then verify the code in the Tabular List, reading all instructional notes; an index code is never final until the tabular confirms completeness, such as required additional characters indicated by symbols in the code book.
Example: The Alphabetic Index entry for a documented fracture of the right ulnar shaft directs to an incomplete code; the Tabular List requires additional characters, including laterality and the seventh-character episode-of-care extension, so the coder verifies and completes the code there before it can group.
Mistake to avoid: Stopping at the Alphabetic Index and submitting an incomplete code that cannot group.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
44. The With Presumption
When with or in links two conditions in a code title, the Alphabetic Index, or a tabular note, the classification presumes a causal relationship, and the conditions are coded as related even without explicit provider linkage, unless the documentation clearly states they are unrelated.
Example: Diabetes with neuropathy in the classification links the two conditions, so related coding applies even though the note lists them separately without linkage.
Mistake to avoid: Ignoring the with presumption and demanding documented linkage the classification already supplies.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
45. Confirmed-Only Diseases Exception
HIV, Zika, COVID-19, and identified influenza are exceptions to the inpatient uncertain-diagnosis practice: only confirmed cases are coded, and confirmation means the provider's diagnostic statement, not necessarily a positive test; suspected, possible, or probable cases are not coded as confirmed.
Example: The provider documents suspected novel influenza; the unidentified-virus influenza category is assigned instead of the identified-strain category, per the guideline.
Mistake to avoid: Coding suspected HIV or COVID as confirmed based on pending or absent test results.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
46. Data Other Clinicians May Supply
Code assignment otherwise rests on the patient's provider's documentation, but BMI, non-pressure ulcer depth, pressure ulcer stage, coma scale, stroke scale, social determinants, laterality, blood alcohol level, underimmunization status, and firearm injury intent may come from other clinicians; the associated diagnosis still requires the provider.
Example: A dietitian documents the BMI value, but the obesity diagnosis must come from the provider before obesity coding applies to the claim.
Mistake to avoid: Coding obesity from a dietitian's BMI entry alone without the provider's diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
47. Use, Abuse, Dependence Hierarchy
When documentation refers to use, abuse, and dependence of the same substance, only one code is assigned by hierarchy: abuse over use, and dependence over abuse and use; if use, abuse, and dependence are all documented, only the dependence code is reported.
Example: A discharge note mentions alcohol use, abuse, and dependence; only the dependence code from category F10 is assigned per the hierarchy.
Mistake to avoid: Assigning separate codes for each documented pattern of use of the same substance.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
48. Complications Require Cause and Effect
Code assignment for complications of care rests on the provider's documentation of the relationship between the condition and the care or procedure; a cause-and-effect relationship and clinical significance must be supported, though the word complication itself need not appear.
Example: Bleeding alters the operative course per the operative report, so a complication code applies even though the word complication was never documented.
Mistake to avoid: Coding every post-procedure condition as a complication without a documented cause-and-effect relationship.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
ICD-10-PCS Procedure Coding
49. Excision Versus Resection
In PCS, excision removes only a portion of a body part while resection removes the entire body part; the documented extent of removal, not the surgeon's loose wording, tells you which root operation applies, and the distinction changes the third character of the code.
Example: A surgeon removes the sigmoid colon segment containing a tumor; because only a portion of the colon is taken, the root operation is excision. A total colectomy removing the entire colon codes to resection instead.
Mistake to avoid: Coding a documented total removal as excision because the surgeon used the word excision loosely.
Reference: AAPC CDEI study guide sample
50. CABG Coding: Body Part and Qualifier Direction
For coronary bypass, the body part character specifies the artery bypassed to and the qualifier specifies the source bypassed from; an internal mammary artery left attached at its origin is a pedicle graft, so the device character is Z, no device, while a detached vein graft carries the autologous venous tissue device.
Example: A reversed saphenous vein graft harvested from the left thigh is anastomosed from the aorta to an occluded right coronary artery. The body part character is coronary artery, one artery — the artery bypassed TO — while the qualifier identifies the aorta as the source bypassed FROM; because the vein is fully detached rather than left attached at its origin, the device character is autologous venous tissue, not the Z used for an internal mammary pedicle graft.
Mistake to avoid: Reversing the to and from values, which selects the wrong body part and qualifier pair.
Reference: AAPC CDEI study guide sample
51. Bilateral Procedures Need Two Codes
When the same root operation is performed on different body parts with distinct body part character values during the same operative episode, multiple codes are assigned per guideline B3.2a; where the tables offer only unilateral body part values, one code per side is required.
Example: An open removal of both ovaries for bilateral masses is coded with two resection codes — one for the right ovary and one for the left — because the PCS tables define the ovaries as distinct unilateral body part values and no bilateral value exists to capture both in one code.
Mistake to avoid: Assigning a single code for a bilateral procedure when the table offers only unilateral body part values.
Reference: AAPC CDEI study guide sample
52. Inspection Coded Separately by Different Approach
When both an inspection procedure and another procedure are performed on the same body part during the same episode, the inspection procedure is coded separately if it is performed using a different approach than the other procedure, per guideline B3.11c.
Example: A knee is inspected arthroscopically and then an open arthrotomy is performed on the same knee during the same episode; the inspection is coded separately because its percutaneous endoscopic approach differs from the open approach of the other procedure, per guideline B3.11c.
Mistake to avoid: Bundling the inspection into the other procedure despite a different approach.
Reference: AAPC CDEI study guide sample
53. Replacement Root Operation and Device Values
Replacement codes use root operation R with a device character identifying what was put in, such as zooplastic tissue for an animal-tissue valve prosthesis; the table then supplies body part, approach, and qualifier values to complete all seven characters of the code.
Example: A patient with severe aortic stenosis undergoes open replacement of the aortic valve with a bovine tissue prosthesis; the root operation is replacement with a device character for zooplastic tissue, because the prosthesis is tissue transferred from an animal to a human, and the remaining characters complete the code.
Mistake to avoid: Coding a valve replacement as repair when the native valve was exchanged for a prosthesis.
Reference: AAPC CDEI study guide sample
54. PCS Carries No Diagnosis Information
PCS codes contain no diagnostic information, so the reason for a procedure never affects code selection; supportive services like cardiopulmonary bypass are separately reportable under the performance root operation in the physiological systems section.
Example: An interventional radiologist percutaneously embolizes a bleeding gastroduodenal artery with coils; the PCS code captures the root operation, the artery, the percutaneous approach, and the intraluminal device, while the cause of the hemorrhage never enters code selection.
Mistake to avoid: Letting the documented diagnosis steer PCS code choice, which the code set cannot represent.
Reference: AAPC CDEI study guide sample
Clinical Conditions and Documentation Specifics
55. Malnutrition: Type and Degree Must Be Documented
Malnutrition documentation should capture pertinent history such as weight loss or cachexia, clinical findings, and supporting labs, plus the type, such as protein calorie or protein energy, and the degree, mild, moderate, or severe; criteria sets like ASPEN frame the clinical assessment.
Example: A note stating only malnutrition prompts a query for type and degree, since the documented severity determines which condition is reported.
Mistake to avoid: Assigning a severe malnutrition code when degree is absent from the documentation.
Reference: AAPC CDEI study guide sample
56. Long-Term Insulin and Oral Therapy Z Codes
Z79.4 reports long-term current insulin use and is not reported when insulin is given only temporarily to bring blood sugar under control during the encounter; oral antidiabetic or hypoglycemic therapy takes Z79.84, combined therapy takes both, and injectable non-insulin drugs add Z79.85.
Example: A type 2 diabetes patient on metformin with long-standing insulin gets both Z79.4 and Z79.84; a one-dose inpatient insulin correction gets neither.
Mistake to avoid: Coding Z79.4 for sliding-scale insulin used briefly during a single admission.
Reference: AAPC CDEI study guide sample
57. Postpancreatectomy Diabetes Coding
For diabetes following pancreatectomy, assign the postprocedural hypoinsulinemia code, then a category E13 code and the acquired absence of pancreas code as additional codes, following the use additional note that also captures insulin use and related status.
Example: After total pancreatectomy with insulin dependence, the coder reports the postprocedural code plus E13, the absence code, and insulin use per the notes.
Mistake to avoid: Coding pancreatectomy-related diabetes as ordinary type 1 or type 2 diabetes.
Reference: AAPC CDEI study guide sample
58. BMI Thresholds and Who Documents What
WHO classification treats BMI of 25 or greater as overweight and 30 or greater as obese; BMI values may be taken from other clinicians' documentation, but the associated overweight or obesity diagnosis itself must come from the patient's provider to be coded.
Example: A nurse records BMI 32 and the provider documents obesity; both elements together support the obesity code, with BMI as secondary.
Mistake to avoid: Coding obesity from the BMI figure alone when no provider diagnosed the condition.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
59. Query the Underlying Cause Before Linking Conditions
For conditions not specifically linked by relational terms in the classification, provider documentation must link the conditions before they can be coded as related; when the record shows treatment of a condition but never names an underlying cause, a query asking whether one exists is the compliant way to clarify the relationship, and the coder must not assume causation.
Example: A patient with long-standing rheumatoid arthritis is admitted for cellulitis of the right hand; the note documents intravenous antibiotics and ongoing immunosuppressive therapy but never states that a contributing condition underlies the infection. The CDEI asks whether an underlying cause of the cellulitis exists before coding any relationship between the two conditions.
Mistake to avoid: Assuming a causal link between two documented conditions without either a classification linkage or documented provider linkage.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
60. Recognizing an Unnamed Definitive Diagnosis
Clinical indicators in the record — such as new symptoms, changing laboratory values, and worsening findings — can point toward a definitive diagnosis the provider never named; documentation suggesting a more definitive diagnosis warrants a query, since only the physician can clarify the outcome.
Example: A patient admitted for a COPD exacerbation develops new-onset confusion, a rising blood urea nitrogen, and urine output under 400 mL over the past day; the indicators suggest an unnamed definitive diagnosis such as acute kidney injury, and only a query to the physician can clarify whether that diagnosis applies.
Mistake to avoid: Coding only the symptoms when indicators clearly point toward a specific unnamed diagnosis.
Reference: AAPC CDEI study guide sample
References and further reading
Source links checked on Oct 2, 2026.