Use this guide as a sequenced study companion rather than a memorization list. Work through the ten groups in order, because later topics assume the documentation and coding foundations built earlier. Each concept pairs a rule with a short resolved case and a common error, so you practice making the distinction, not just naming the topic. References below point to the underlying guideline texts for deeper reading. This guide supports your preparation but does not replace the official handbook, the classification, or the guidelines themselves.
The Clinical Documentation Specialist Role
1. CDS Responsibilities Versus the Coding Department
The clinical documentation specialist performs preliminary and ongoing chart reviews, clarifies clinical indicator support, and assigns working ICD-10-CM and PCS codes to establish a tentative MS-DRG; the coding department verifies and finalizes what is actually reported. This handoff defines accountability for the billed claim.
Example: A CDS drafts a working DRG for a stay with a documented MCC; final code assignment stays with the coding department after query responses return.
Mistake to avoid: Treating preliminary CDS working codes as final billed codes without coder verification.
Reference: Certified Clinical Documentation Specialist (CCDS); AAPC CDEI study guide sample
2. Documentation Integrity as the Program Mission
CDI programs exist primarily to improve documentation accuracy and patient care, not to maximize revenue. Programs built to drive reimbursement upward create compliance exposure when they lead providers toward unsupported higher-severity coding; an accurate case mix index follows from honest documentation, not from targets.
Example: A program goal states capture of all clinically supported conditions rather than increased MCC capture, keeping every query grounded in documented evidence.
Mistake to avoid: Writing CDI program goals around revenue targets that pressure providers toward upcoding.
Reference: AAPC CDEI study guide sample
3. The Multidisciplinary Knowledge Base
CCDS competency spans anatomy, physiology, pathophysiology, pharmacology, official coding guidelines, CMS and payer rules tied to inpatient prospective payment, medical record review, physician query technique, quality program metrics, and data mining. Breadth matters because the specialist must judge when clinical evidence does or does not support a documented diagnosis.
Example: A CDS with pharmacology knowledge recognizes documented insulin dose adjustment as treatment evidence supporting the diabetes diagnosis during review.
Mistake to avoid: Reviewing charts for wording alone without understanding the clinical science behind the documentation.
Reference: Certified Clinical Documentation Specialist (CCDS)
4. Proactive Front-End Review
CDI should begin at the front end of all services and care, preventing documentation deficiencies rather than repairing them after discharge. Concurrent review during the stay lets the specialist query while the provider still remembers the patient, an advantage retrospective review cannot recover.
Example: A CDS reviews the chart on day two, notices undocumented POA status, and queries the hospitalist before discharge rather than weeks afterward.
Mistake to avoid: Running CDI only retrospectively after claims are ready, when providers can no longer recall details.
Reference: AAPC CDEI study guide sample
5. Real-Time Quality Department Coordination
The specialist works with the quality department to address documentation deficiencies affecting quality measures in real time, because reportable diagnoses feed CMS quality metrics. Coordinated timing means missing specificity can be corrected before data submission windows close rather than discovered afterward.
Example: A quality nurse flags a possible hospital-acquired condition; the CDS immediately verifies POA documentation with the attending before the abstraction deadline.
Mistake to avoid: Letting quality data abstract first and discovering documentation gaps only at reporting time.
Reference: Certified Clinical Documentation Specialist (CCDS); AAPC CDEI study guide sample
6. Benchmarking CDI Program Performance
A clinical documentation specialist must be able to benchmark and analyze program performance, comparing documentation, query, and denial trends over time. Benchmarking distinguishes a systemic documentation gap from an individual provider pattern and directs education where it will actually change outcomes.
Example: Quarterly review shows one service line generating most clarification requests, so education targets that department's note templates specifically.
Mistake to avoid: Measuring CDI success only by revenue lift instead of documentation accuracy and denial trends.
Reference: Certified Clinical Documentation Specialist (CCDS); AAPC CDEI study guide sample
Medical Record Fundamentals
7. The Record as Legal Evidence of Care
The medical record is a legal document and the only durable evidence of care quality; it validates level of care, medical necessity, coding accuracy, and provider identity. Care that is not documented is treated as though it never happened, regardless of what actually occurred at the bedside.
Example: A physician provides excellent sepsis care, but the note never links organ dysfunction to infection; auditors cannot verify severity from memory.
Mistake to avoid: Assuming verbal reports or personal recollections can substitute for what the record actually states.
Reference: AAPC CDEI study guide sample
8. Conditions of Participation Record Content
Federal Conditions of Participation require the record to contain information justifying admission and continued stay, and CMS interpretive guidance expects the record to identify the patient, support the diagnosis, justify treatment, and document the course and results of treatment. Missing any element undermines defensibility.
Example: A record lacks any note explaining why inpatient care continued past day three, so continued-stay justification fails external review.
Mistake to avoid: Treating admission documentation as complete without evidence supporting the continued stay.
Reference: AAPC CDEI study guide sample
9. Copy-Forward and Cloning Risks
Copying prior notes forward can import outdated or inaccurate information into the current note, producing cloned documentation that misrepresents today's findings. The specialist works with providers to minimize inappropriate cloning because cloned content drives inaccurate codes, claims, and quality data.
Example: A day-four note repeats wound dry and intact copied from admission although day-three nursing notes record a new sacral ulcer.
Mistake to avoid: Accepting copied physical findings as current-day evidence without checking the dated original entries.
Reference: AAPC CDEI study guide sample
10. Template Individualization
Pre-filled templates applied to all patients without individualization produce generic notes that fail to describe each patient's specific condition. Templates themselves are acceptable tools; the failure is not editing them to reflect the actual encounter, which leads directly to inaccurate coding and billing.
Example: Every admission on a service uses identical review-of-systems text; the CDS educates the group to document patient-specific findings instead.
Mistake to avoid: Blaming the template itself rather than the failure to tailor it to the individual patient.
Reference: AAPC CDEI study guide sample
11. Dangerous Abbreviations
The abbreviation U or u for unit can be misread as zero, the number four, or cc, so documentation standards call for writing unit in full. Abbreviation discipline protects the record's accuracy for every downstream user, including pharmacists and coders relying on the entry.
Example: An order reading insulin 6U is misread as 60 units; writing six units removes the ambiguity entirely for every downstream user.
Mistake to avoid: Leaving ambiguous unit abbreviations uncorrected in records you are responsible for reviewing.
Reference: AAPC CDEI study guide sample
12. Trailing Zero Rules
A trailing zero may be used only where precision of the reported value requires it, such as laboratory results, lesion sizes on imaging, or catheter and tube sizes; it may not appear in medication orders or medication-related documentation, where a decimal misread as a whole number changes the dose.
Example: A medication entry reading 5.0 mg is corrected to 5 mg because medication documentation forbids trailing zeros.
Mistake to avoid: Applying laboratory-style precision conventions to medication orders and medication documentation.
Reference: AAPC CDEI study guide sample
HIPAA Privacy in CDI Practice
13. Who Is a Covered Entity
The Privacy Rule covers health plans, health care clearinghouses, and any healthcare provider that transmits health information electronically in connection with standard HIPAA transactions such as claims. Simply using email or computers does not make a provider covered; the transmission must relate to a standard transaction.
Example: A small clinic emailing appointment reminders is not covered by that act alone; the same clinic billing electronically through a clearinghouse is covered.
Mistake to avoid: Assuming any provider using computers or email is automatically a covered entity.
Reference: HHS Summary of the HIPAA Privacy Rule
14. What Counts as Protected Health Information
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 tied to health, care, or payment. Verbal discussion of identifiable patients falls squarely within scope.
Example: A CDS discussing a named patient's abnormal pathology result with an unrelated colleague orally still implicates the Privacy Rule.
Mistake to avoid: Thinking privacy rules apply only to records stored or sent electronically.
Reference: HHS Summary of the HIPAA Privacy Rule
15. Treatment, Payment, and Operations Permissions
A covered entity may use and disclose protected health information without authorization for its own treatment, payment, and health care operations, which include quality assessment, medical review, audits, and compliance programs. CDI review activity fits within operations, so routine chart review requires no patient authorization.
Example: A CDS reviews charts for documentation improvement under the hospital's operations activities without obtaining any patient sign-off.
Mistake to avoid: Delaying internal CDI review while waiting for authorizations the Privacy Rule does not require.
Reference: HHS Summary of the HIPAA Privacy Rule
16. Minimum Necessary Access
Covered entities must make reasonable efforts to limit uses, disclosures, and requests of PHI to the minimum necessary for the purpose, implemented through role-based access policies. The entire record may be used only when specifically justified; the standard does not apply to disclosures for treatment.
Example: A denial-analysis response to a payer includes only the stay's relevant pages, not the full chart, because no whole-record justification exists.
Mistake to avoid: Granting all CDI staff unrestricted whole-record access regardless of their actual role needs.
Reference: HHS Summary of the HIPAA Privacy Rule
17. De-Identification Versus Limited Data Sets
De-identified information, created by removing specified identifiers with no actual knowledge of re-identifiability, carries no use restrictions. A limited data set removes fewer direct identifiers and may be used only for research, public health, or operations, and only under a data use agreement promising safeguards.
Example: A CDI benchmarking project uses a limited data set with a signed data use agreement because visit dates must be retained for analysis.
Mistake to avoid: Treating a limited data set as fully de-identified and sharing it without a data use agreement.
Reference: HHS Summary of the HIPAA Privacy Rule
18. Business Associate Obligations
A business associate is a non-workforce person or organization performing functions for a covered entity that involve PHI, such as claims processing, data analysis, utilization review, or billing, and written agreements must impose specified safeguards. A vendor whose PHI access is merely incidental is not a business associate.
Example: An external coding analytics firm reviewing identifiable charts for the hospital must operate under a signed business associate agreement.
Mistake to avoid: Engaging PHI-handling consultants without a written business associate agreement in place.
Reference: HHS Summary of the HIPAA Privacy Rule
ICD-10-CM Conventions
19. Index First, Then Tabular Verification
Code selection starts in the Alphabetic Index, and the resulting code must be verified in the Tabular List, where required additional characters and instructional notes appear. An index code left incomplete at verification is invalid for reporting and can derail the entire DRG assignment.
Example: A STEMI indexed to I21.0 fails verification because the Tabular List requires a fifth character identifying the involved coronary artery.
Mistake to avoid: Reporting an index code without completing the characters required in the Tabular List.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AAPC CDEI study guide sample
20. The With Presumption
When with or in links two conditions in a code title, index entry, or instructional note, the classification presumes a causal relationship, and the conditions are coded as related even without explicit provider linkage, unless documentation clearly states they are unrelated or a guideline requires documented linkage.
Example: Documented hypertension and chronic heart failure are coded as related because the classification links them, absent a provider statement clearly separating the conditions.
Mistake to avoid: Querying for linkage the classification already presumes, or coding as related what documentation clearly separates.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
21. And Means And or Or
In code titles the word and is interpreted as meaning and or or, so tuberculosis of bones, tuberculosis of joints, and tuberculosis of bones and joints all classify to the same subcategory. Reading and as requiring both conditions over-restricts code selection and drops valid assignments.
Example: A note documenting tuberculosis of a single joint still assigns the bones-and-joints subcategory because and includes or.
Mistake to avoid: Withholding a combined-title code because only one of the named sites is documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
22. Default Codes
A default code listed beside a main term represents the most common presentation or the unspecified form of the condition. When a condition is documented without qualifiers such as acute or chronic, the default code is assigned rather than a more specific code chosen by assumption.
Example: Appendicitis documented with no acuity indicator is coded to the default entry rather than assuming an acute presentation.
Mistake to avoid: Assigning a specific acuity code based on assumption instead of the documented default entry.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
23. Other Versus Unspecified Codes
Other codes apply when documentation describes a condition the classification recognizes but for which no specific code exists; unspecified codes apply when the documentation itself lacks the detail. The choice depends on what the record actually states, never on coder inference about the likely entity.
Example: Pneumonia confirmed but type undocumented takes the unspecified pneumonia code, not an other code implying an identified atypical form.
Mistake to avoid: Using other codes as catch-alls when the record simply lacks the needed detail.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. Code Also Notes Give No Sequence
A code also note signals that two codes may be required to fully describe a single condition, but it provides no sequencing direction; sequencing depends on the circumstances of the encounter and other applicable guidelines. Treating the note as a sequencing rule misorders the claim.
Example: Hypertensive retinopathy is coded along with a code from the hypertension categories, and which of the two is principal depends on whether this encounter is for the retinal condition or for blood pressure control.
Mistake to avoid: Assuming the code also note dictates which of the two codes must be sequenced first.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Diagnosis Documentation Authority
25. The Provider Statement Governs
Code assignment rests on the provider's diagnostic statement that the condition exists, not on whether the coder believes the clinical criteria were met; conflicting documentation is resolved by querying the provider. The specialist evaluates support and asks, but cannot overturn or substitute a diagnosis independently.
Example: A documented hypokalemia with an in-range potassium value is queried to the provider rather than silently deleted by the coder.
Mistake to avoid: Striking a provider's diagnosis because the coder judges the laboratory evidence insufficient.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AAPC CDEI study guide sample
26. Clinician Documentation Exceptions
Non-provider clinicians may document 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 must still come from the patient's provider.
Example: A dietitian's BMI entry supports the BMI code, but only the physician's obesity diagnosis allows reporting obesity itself.
Mistake to avoid: Coding obesity from a dietitian's BMI documentation alone without any provider diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
27. Resolving Conflicting Documentation
When medical record documentation conflicts — between different clinicians or within one clinician's notes — the patient's provider must be queried for clarification rather than one version being silently preferred. Conflicts also block laterality and present-on-admission determinations until resolved.
Example: One note says right-sided cellulitis and another says left; the CDS queries the treating provider instead of picking the more recent entry.
Mistake to avoid: Defaulting to the latest note or the specialist's note without querying the documented conflict.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Uncertain Diagnoses and the HIV Exception
Inpatient guidelines permit coding a condition documented at discharge as suspected, possible, or ruled out as though confirmed, reflecting the working diagnosis at discharge; HIV is an explicit exception requiring confirmed status before the HIV disease code is assigned.
Example: Possible pneumonia documented at discharge on an inpatient record is coded as pneumonia; possible HIV is not coded to B20 without confirmation.
Mistake to avoid: Applying the inpatient uncertain-diagnosis rule to HIV, or the HIV confirmation rule to every diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Borderline Diagnoses
A provider-documented borderline condition at discharge is coded as confirmed unless the classification provides a specific entry for that borderline condition, and this treatment applies equally in inpatient and outpatient settings because borderline is not an uncertain diagnosis.
Example: Borderline hypertension documented at discharge is coded as hypertension where no specific borderline entry exists in the classification.
Mistake to avoid: Treating borderline like suspected or possible and suppressing the code at discharge.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Legitimate Use of Symptom and Unspecified Codes
Sign, symptom, and unspecified codes are appropriate when no definitive diagnosis was established by the end of the encounter or when clinical detail is genuinely unknown; each encounter is coded to its level of certainty, and conducting medically unnecessary testing to force specificity is improper.
Example: A discharge listing only fever and cough, with workup incomplete, is coded to symptoms rather than an assumed pneumonia.
Mistake to avoid: Selecting a specific diagnosis code unsupported by the record just to avoid unspecified codes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Chapter-Specific Coding Decisions
31. Urosepsis Is Not Sepsis
The term urosepsis is nonspecific, is not considered synonymous with sepsis, and has no default code in the Alphabetic Index; when a provider uses it, a clarifying query is required before any sepsis code may be assigned for the encounter.
Example: A note reads urosepsis treated with IV antibiotics; the CDS queries whether sepsis or a urinary infection is meant before coding.
Mistake to avoid: Assigning a sepsis code from the term urosepsis without querying the provider first.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
32. Severe Sepsis Needs Associated Organ Dysfunction
Severe sepsis coding requires the underlying infection code, a severe sepsis code, and codes for associated acute organ dysfunction; when documentation attributes the dysfunction to a condition other than sepsis, the severe code is not assigned, and unclear relationships are queried.
Example: Acute kidney injury documented as due to contrast exposure in a septic patient does not support the severe sepsis code.
Mistake to avoid: Attaching every documented organ dysfunction to sepsis without a documented association.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
33. HIV Coding Tiers
Confirmed symptomatic HIV disease codes to the HIV disease code, which then persists on every subsequent encounter; asymptomatic positive status codes to the asymptomatic code, inconclusive serology to its own code, and a patient ever assigned the disease code never returns to the asymptomatic or inconclusive codes.
Example: A patient with an old AIDS-related illness admitted for a fracture still receives the HIV disease code as a secondary diagnosis.
Mistake to avoid: Coding a previously HIV-disease patient as asymptomatic because the current stay shows no HIV symptoms.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
34. Substance Use Hierarchy
When documentation refers to use, abuse, and dependence of the same substance, only one code is assigned to identify the pattern: dependence outranks abuse, and abuse outranks use. The hierarchy resolves internal documentation variation without generating a query or duplicate codes.
Example: Notes mention alcohol use and alcohol dependence in the same stay; only the dependence code is assigned for that substance.
Mistake to avoid: Reporting separate codes for use and dependence of the same substance in one stay.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
35. Pressure Ulcer Stage Coding
Pressure ulcer codes identify site and stage; unstageable applies when the stage cannot be clinically determined, such as eschar coverage or grafting, while unspecified stage applies when the stage is simply not documented; after debridement reveals a stage, only that revealed stage is coded.
Example: A sacral ulcer documented as covered by eschar is coded unstageable; after debridement exposes full-thickness loss, only the stage code is assigned.
Mistake to avoid: Confusing unstageable with unspecified stage, or coding both after debridement reveals the stage.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
36. Complications Without the Word Complication
A complication code requires a documented cause-and-effect relationship between the care provided and a clinically significant condition, but the provider need not use the word complication; a condition that alters the course of surgery, as shown in the operative report, qualifies. Unclear relationships are queried.
Example: An operative note describes bleeding forcing abandonment of the planned approach; the complication code is supported without the label.
Mistake to avoid: Coding every post-procedure condition as a complication absent a documented causal link.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Present on Admission and Quality Data
37. POA Timing Definition
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 — preceding that order count as present on admission and take the Y indicator.
Example: A patient develops pneumonia in the ED before the inpatient order is written; the pneumonia is present on admission.
Mistake to avoid: Assigning N because the diagnosis was made before the inpatient order existed.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
38. POA Indicator Values and the Exempt List
Indicators are Y for present, N for not present, U when documentation is insufficient to determine, W when the provider clinically cannot determine, and blank only for codes on the exempt list covering circumstances or conditions always present on admission; U should be rare and should prompt a query.
Example: A documented condition with no timing evidence anywhere in the record is queried rather than routinely assigned U.
Mistake to avoid: Using U as a default filler instead of querying, or leaving non-exempt codes blank.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
39. Diagnosed Later but Present Earlier
Conditions diagnosed before admission take Y, and conditions diagnosed during the stay but clearly present beforehand also take Y, including those documented at admission as suspected, possible, ruled out, or as an underlying cause of an admission symptom and later confirmed.
Example: Possible stroke documented in the admission note and confirmed on day two is present on admission.
Mistake to avoid: Assigning N merely because definitive confirmation came after the first admission day.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
40. No Required POA Documentation Timeframe
No rule requires a provider to identify or document a condition within a set period after admission; a diagnosis reached days later can still be present on admission, and the determination rests on the applicable guideline or the provider's best clinical judgment, with queries used when timing is unclear.
Example: A wound infection recognized on day five but described as evolving since admission is queried for POA rather than assumed N.
Mistake to avoid: Treating a delayed diagnosis as automatic evidence of not present on admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
41. POA and Hospital-Acquired Conditions
Present-on-admission status separates conditions present at admission from hospital-acquired conditions, which feed quality reporting and payment consequences; the specialist clarifies POA precisely because hospital-acquired condition categories and quality metrics depend on that single documented timing element.
Example: A stage three pressure ulcer documented without timing is queried so the hospital can correctly classify it as present or acquired.
Mistake to avoid: Abstracting hospital-acquired condition data before present-on-admission documentation is resolved.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
42. Reportable Diagnoses and Quality Programs
CMS quality programs, including value-based purchasing, readmission reduction, and patient safety indicators, draw on reportable diagnoses, so documentation specificity directly moves quality metrics; the specialist coordinates with quality staff on these reportable diagnoses in real time during the stay.
Example: A stay worked up for cough and fever that confirms pneumonia is abstracted into quality reporting only when the definitive diagnosis is documented; symptoms alone are not reportable diagnoses, so the metric moves only when the confirmed condition appears in the record.
Mistake to avoid: Treating quality measure data as separate from the coding and documentation improvement process.
Reference: Certified Clinical Documentation Specialist (CCDS); CDC ICD-10-CM Official Guidelines, FY 2027
MS-DRG and Inpatient Payment Logic
43. What Drives MS-DRG Assignment
The MS-DRG reflects the principal diagnosis, secondary conditions qualifying as complications or comorbidities or major complications or comorbidities, and the type of surgical procedures performed; documentation of each element determines the assignment and the relative weight applied to the hospital's payment.
Example: Documenting an MCC on an appendix procedure stay shifts the assignment from the without-CC/MCC group to the with-MCC group.
Mistake to avoid: Reviewing only the principal diagnosis while ignoring CC and MCC documentation entirely.
Reference: AAPC CDEI study guide sample
44. Grouper Sequence
The grouper first tests for pre-MDC qualifications such as tracheostomy, ECMO, or major organ transplant; otherwise the principal diagnosis places the case in a diagnostic category, a valid operating-room procedure routes it to the surgical section, then CC/MCC status, discharge disposition, gender, and neonatal gestational age refine it; patient age matters only for neonates.
Example: A stay including ECMO qualifies as a pre-MDC and short-circuits the usual MDC pathway entirely.
Mistake to avoid: Assuming patient age or secondary diagnoses alone determine the final DRG assignment.
Reference: AAPC CDEI study guide sample
45. The Ungroupable DRG and Invalid Data
Invalid ICD-10-CM codes, invalid age, incorrect sex, or an invalid discharge disposition produce the ungroupable DRG, which pays nothing and returns the claim to the facility for correction and resubmission. Complete, valid data entry is therefore a documentation integrity issue, not just a billing formality.
Example: A claim carrying an incomplete five-character myocardial infarction code groups to the ungroupable DRG and bounces back for correction.
Mistake to avoid: Assuming an incomplete code will group to the nearest reasonable DRG instead of failing.
Reference: AAPC CDEI study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
46. Principal Diagnosis Errors Change Payment
Choosing the wrong principal diagnosis produces the wrong MS-DRG, and missing data can understate severity; errors in the other direction assign higher-paying groups and expose the hospital to recoupment when CMS or OIG audits detect the overpayment. Both directions demand principal diagnosis review.
Example: Sequencing a symptom instead of the established definitive etiology drops the stay to a lower-weighted medical group.
Mistake to avoid: Fixating on CC capture while leaving principal diagnosis selection unreviewed.
Reference: AAPC CDEI study guide sample
47. Case Mix Index Integrity
The case mix index reflects the severity of procedures and care required to treat patients, and it is accurate only when documentation supports the coded conditions; an honest index is the byproduct of complete documentation, not a target to engineer through query pressure or severity chasing.
Example: A program tracks case mix index alongside query agreement rates to confirm severity gains reflect genuine documentation.
Mistake to avoid: Chasing case mix index growth through query pressure rather than documentation accuracy.
Reference: AAPC CDEI study guide sample
48. Supplemental IPPS Payments
Beyond base DRG payments, the inpatient system provides additional payments for outlier cases with extraordinarily high costs, disproportionate share hospitals serving low-income patients, indirect medical education adjustments for approved teaching hospitals, and new technology add-ons; each has its own qualification logic the specialist should recognize.
Example: A stay with exceptional costs converts charges to costs and may qualify for an outlier payment above the standard DRG amount.
Mistake to avoid: Assuming the DRG relative weight is the only payment variable for every inpatient stay.
Reference: AAPC CDEI study guide sample
Compliance, Fraud, and Abuse
49. Fraud Versus Abuse
CMS defines fraud as knowingly making false statements or misrepresenting facts to obtain an undeserved benefit or payment from a federal healthcare program, while abuse describes actions creating unnecessary costs without necessarily intentional deception; the distinction shapes which enforcement expectations and internal responses apply.
Example: Misusing a code through sloppy documentation is abuse; knowingly altering a claim to a higher-paying code is fraud.
Mistake to avoid: Using fraud and abuse interchangeably when describing documentation compliance risks.
Reference: AAPC CDEI study guide sample
50. Knowledge Standard Under the FCA
False Claims Act liability requires acting with knowledge that a claim is false, and knowledge is defined to include deliberate ignorance of the truth and reckless disregard of truth or falsity; no specific intent to defraud is required, so willful blindness about documentation problems provides no protection.
Example: A supervisor ignores repeated warnings that cloned notes inflate severity and remains liable despite never intending fraud.
Mistake to avoid: Believing the absence of intent to defraud shields reckless or ignored documentation problems.
Reference: AAPC CDEI study guide sample
51. Reverse False Claims
Beyond submitting false claims, liability arises under the reverse false claims provision when a person knowingly conceals or improperly avoids an obligation to pay money owed to the government, such as retaining identified overpayments rather than returning them promptly.
Example: A hospital discovers documentation errors caused overpayment and delays repayment, creating reverse false claims exposure.
Mistake to avoid: Thinking False Claims Act risk only involves claims sent out, never money withheld.
Reference: AAPC CDEI study guide sample
52. Upcoding and Unbundling as Fraud Examples
Healthcare conduct subject to the False Claims Act includes upcoding, unbundling services, billing for services not furnished, misrepresenting diagnoses to justify payment, and falsifying chart notations; each converts weak documentation into a false claim, which is why documentation integrity is the compliance front line.
Example: Querying a provider to confirm sepsis the record does not support, then billing the severe DRG, fits the upcoding pattern.
Mistake to avoid: Framing upcoding as a coding technicality rather than a false claims exposure.
Reference: AAPC CDEI study guide sample
53. Compliant Versus Leading Queries
A compliant query presents the clinical indicators from the record and asks the provider to clarify the documentation, without suggesting a desired answer or implying reimbursement consequences; leading queries that steer toward higher-severity diagnoses create compliance risk and undermine the integrity of the coded data.
Example: A query lists fever, hypoxia, and infiltrates and asks the provider to clarify the respiratory diagnosis, offering clinically reasonable options.
Mistake to avoid: Writing queries that name only the higher-paying diagnosis as the response option.
Reference: AAPC CDEI study guide sample
54. Oversight Bodies and Audit Exposure
The Office of Inspector General publishes work plan priorities, compliance programs structure internal controls, and recovery audit contractors detect and recoup overpayments; CMS and the OIG routinely audit for DRG errors. Concurrent CDI work is a primary defense because it fixes documentation before claims leave the building.
Example: A recovery audit questions an MCC; concurrent documentation showing the provider's own diagnostic statement supports upholding the claim.
Mistake to avoid: Treating audits as billing-department problems disconnected from documentation quality.
Reference: AAPC CDEI study guide sample
Procedure Documentation and PCS Logic
55. Excision Versus Resection
In the procedure classification, excision removes a portion of a body part while resection removes the entire body part; the operative wording determines the root operation, so whether removal was partial or total must be documented clearly before the code is selected.
Example: A total axillary lymph node chain removal codes to resection; a sampled portion of the chain codes to excision.
Mistake to avoid: Coding resection when the operative note describes removal of only part of the structure.
Reference: AAPC CDEI study guide sample
56. Bilateral Procedures Need Two Codes
When the same root operation is performed on different body parts during one operative episode, multiple codes are assigned; where the table provides distinct left and right body part values but no bilateral value, two separate codes are required to report the complete bilateral procedure.
Example: Open resection of both axillary node chains requires one code for the left side and one for the right side.
Mistake to avoid: Reporting a single code for a bilateral procedure when no bilateral body part value exists.
Reference: AAPC CDEI study guide sample
57. Bypass Coding Direction
For coronary bypass, the body part character names the artery bypassed to, and the qualifier names the source bypassed from; an internal mammary artery left attached at its origin is a pedicle graft, coded with no device value because the conduit remains a living body part.
Example: A left internal mammary to LAD graft codes to one coronary artery, open approach, no device, with a left internal mammary qualifier.
Mistake to avoid: Reversing the from and to body parts, or coding a device for a pedicled mammary graft.
Reference: AAPC CDEI study guide sample
58. Separate Coding of Different-Approach Inspection
When an inspection procedure and another procedure are performed on the same body part in the same episode, the inspection is coded separately only if it used a different approach than the other procedure; same-approach inspections are not separately reported. Approach wording in the note drives the decision.
Example: An open repair preceded by a percutaneous endoscopic inspection of the same site yields both the inspection and the repair codes.
Mistake to avoid: Dropping the inspection code solely because it shared the body part with the repair.
Reference: AAPC CDEI study guide sample
59. PCS Carries No Diagnosis Information
Procedure codes contain operative detail only; the reason for the procedure, such as an underlying tumor or disease process, does not influence procedure code selection and is captured separately through diagnosis coding. Hunting for a code that reflects the disease wastes review time and misstates the system.
Example: Embolization of an intracranial artery feeding a meningioma codes to the vessel occlusion; the meningioma never enters the procedure code.
Mistake to avoid: Searching for a procedure code that reflects the tumor or disease indication behind it.
Reference: AAPC CDEI study guide sample
60. Root Operation Follows Procedure Purpose
The root operation reflects the objective of the procedure, such as bypass chosen because the intent is rerouting flow around an occlusion, rather than the incision or technique used; reading the stated purpose in the operative report, not the surgical vocabulary, drives correct root operation selection.
Example: A graft restoring flow past an occluded coronary is coded to bypass even though the note emphasizes the anastomosis technique.
Mistake to avoid: Selecting root operations from technique vocabulary instead of the stated procedural intent.
Reference: AAPC CDEI study guide sample
References and further reading
Source links checked on Oct 2, 2026.