Study guide
1.2 General Coding Conventions, Punctuation & Instructional Notes
AHIMA Certified Documentation Integrity Practitioner CDIP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Authoritative Coding Resources & Conventions
1.1 Official Coding Resources: Scope, Authority & Research 1.2 General Coding Conventions, Punctuation & Instructional Notes 1.3 Chapter-Specific and Setting-Specific Coding Guidelines
2 Chapter 2: Principal & Secondary Diagnosis Determination
2.1 UHDDS Definitions & Principal Diagnosis Selection 2.2 Two or More Diagnoses Equally Meeting Criteria 2.3 Secondary Diagnosis Reporting Standards & POA Status
3 Chapter 3: Procedure Coding & Sequencing Standards
3.1 ICD-10-PCS Root Operations & Inpatient Procedure Coding 3.2 Principal Procedure Selection & Surgical Sequencing 3.3 Applying Official References to Ambiguous Records
4 Chapter 4: Inpatient Prospective Payment & DRG Grouping
4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels 4.2 Working vs. Final DRG Assignment & Optimization vs. Maximization 4.3 CDI-Coding Reconciliation & Annual Regulatory Updates
5 Chapter 5: Enterprise CDI Promotion & Program Value
5.1 Articulating CDI Value to C-Suite & Hospital Leadership 5.2 Organizational Models, Inpatient/Outpatient Scope & Staffing 5.3 Cross-Functional Collaboration: HIM, Quality & Case Management
6 Chapter 6: Cross-Functional Alignment & Improvement Projects
6.1 Partnering with Nursing, Pharmacy & Allied Health Professionals 6.2 Documentation Improvement Project Identification & Scoping 6.3 Executing, Piloting & Measuring CDI Project Outcomes
7 Chapter 7: Physician Champion Engagement & Clinical Advocacy
7.1 Selection, Role & Credibility of the CDI Physician Champion 7.2 Peer-to-Peer Engagement, Coaching & Overcoming Resistance 7.3 Developing Standard CDI Operational Policies & Procedures
8 Chapter 8: Compliant Policy Architecture & Query Governance
8.1 AHIMA/ACDIS Practice Brief Standards in Policy Construction 8.2 Medical Record Integration of Provider Query Responses 8.3 Policies for Electronic, Paper, and Verbal Query Communications
9 Chapter 9: Query Escalation & Professional Communication
9.1 Chain of Command & Protocols for Unanswered Queries 9.2 Conflict Resolution & Professional Feedback Mechanisms 9.3 Assessing Stakeholder Learning Needs & Specialty Curricula
10 Chapter 10: Educational Delivery & Broader Healthcare Impacts
10.1 Delivery Methods: Microlearning, Case Studies & Grand Rounds 10.2 Documentation Impacts on Clinical Research & Epidemiology 10.3 Documentation Impacts on Case Management, LOS & Reimbursement
11 Chapter 11: Clinical Record Synthesis & Encounter Trajectory
11.1 Synthesizing Provider Notes, Consults & Progress Trajectory 11.2 Interpreting Diagnostic Imaging, Pathology & Labs 11.3 Resolving Conflicting, Ambiguous & Copy-Forward Entries
12 Chapter 12: Advanced Clinical Concepts & Review Prioritization
12.1 Pharmacotherapy, Clinical Trajectories & Disease Correlations 12.2 Inpatient Review Prioritization: High-Risk & High-Volume 12.3 Payer Prioritization, Length of Stay & Re-Review Cadence
13 Chapter 13: Clinical Indicator Mapping & Gap Recognition
13.1 Systematic Identification of Documentation Gaps 13.2 Sepsis Definitions, SEP-1, and Coding 13.3 AKI Criteria, Tubular Injury, and CKD Staging
14 Chapter 14: Diagnostic Precision in High-Impact Conditions
14.1 Respiratory Failure: Acuity, Evidence, and Sequencing 14.2 Heart Failure Phenotype, Acuity, and Hypertensive Combinations 14.3 Encephalopathy, Delirium, and Acute Cognitive Change
15 Chapter 15: Clinical Validation & Complication Discrepancies
15.1 Malnutrition Assessment, Severity, and Provider Documentation 15.2 Principles of a Compliant, Nonleading Query 15.3 Open-Ended, Multiple-Choice, and Yes/No Queries
16 Chapter 16: Query Mechanics & Direct Provider Collaboration
16.1 Electronic Query Systems, Templates, and Technology Oversight 16.2 Collaborating With the Appropriate Query Recipient 16.3 Capturing and Clarifying Query Responses
17 Chapter 17: Quality Indicators & Post-Discharge Clarification
17.1 Present on Admission Clarification and Selected HAC Rules 17.2 Clarifying Acuity, Cause, Site and Severity 17.3 Post-Discharge Query Opportunities and Limits 17.4 Managing Post-Discharge Query Workflows
18 Chapter 18: CDI Operational Dashboards & Quality Auditing
18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use 18.2 Internal CDI Quality Audits and Reviewer Calibration 18.3 Query Trends: Understanding the Process and Provider Experience
19 Chapter 19: Benchmarking, Productivity & Data-Driven Workflow
19.1 Provider Documentation Benchmarking 19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay 19.3 Evaluating CDI Professional Performance 19.4 Using Data to Design CDI Workflow and Staffing
20 Chapter 20: Ethical CDI Standards & Regulatory Frameworks
20.1 Applying AHIMA Ethics to CDI Decisions 20.2 Responding to Financial Pressure and Upcoding Risks 20.3 Maintaining Competence and Professional Integrity
21 Chapter 21: Regulatory Compliance & Enforcement Landscapes
21.1 False Claims, Overpayments and Referral Laws 21.2 Regulatory Agencies, Review Contractors and Appeals 21.3 EHR Templates, Copied Text and Record Integrity
22 Chapter 22: Technology Risks & Second-Level Review Protocols
22.1 CAC, NLP and AI: Context, Oversight and Performance 22.2 Selecting Cases for Second-Level Review 22.3 Conducting and Closing a Second-Level Review
23 Chapter 23: Clinical Validation Queries & Risk Mitigation
23.1 Clinical Validation and Coding Clarification 23.2 Clinical Validation Queries and Denial Evidence 23.3 Detecting Leading, Biased and Unsupported Queries
24 Chapter 24: Noncompliant Query Remediation & Query Lifecycle Management
24.1 Query Remediation and Corrective Action 24.2 Query Timeframes, Aging and Measurement 24.3 Query Records, Retention and Evidence Preservation
1.2 General Coding Conventions, Punctuation & Instructional Notes
Key Takeaways Explain This Topic AI
Only complete ICD-10-CM codes are reportable; required placeholders and seventh characters must occupy their specified positions.
Excludes1 generally prevents simultaneous assignment, with an exception for unrelated conditions; Excludes2 permits both codes when appropriate.
Code first and use additional code instructions establish code relationships and sequencing, including uses beyond etiology/manifestation pairs.
The with/in convention applies to relationships specified by the classification, subject to unrelated documentation and guidelines that require explicit linkage.
Acute on chronic systolic heart failure is I50.23, whereas I50.21 describes acute systolic heart failure.
Last updated: October 2026
Conventions turn documentation into consistent code assignment
ICD-10-CM uses structural rules and instructional notes to make the same documented condition reportable consistently. A CDI reviewer needs to recognize when the documentation supports a code, when a classification instruction supplies a relationship or sequence, and when clarification is needed. The FY2027 Official Guidelines, Section I.A , explain these conventions. Classification instructions and conventions take precedence over the guidelines.
Categories, complete codes, and required characters
Categories have three characters. A three-character category is reportable as a code only when it has no further subdivision. Complete codes may have three through seven characters; the decimal point does not count as a character. Do not infer completeness from the length alone. A four-character entry can still be a subdivided category requiring more detail.
For example, A38 is the category for scarlet fever, with further subdivisions. It is not a complete reportable code. A38.9 , scarlet fever, uncomplicated, is a complete code; the Tabular List includes scarlet fever NOS under that code. Similarly, N18.3 , chronic kidney disease, stage 3 (moderate), has additional subdivisions. The reviewer must select the supported complete code, rather than submit the parent entry.
The placeholder X preserves required positions in designated codes. Where a seventh character applies, it must occupy position seven. If there are fewer than six preceding characters, placeholders fill the necessary positions. X also serves the classification's expansion structure; follow the actual entry rather than adding or removing it from memory.
Consider T42.4X1A , poisoning by benzodiazepines, accidental (unintentional), initial encounter:
- Position 1 2 3 4 5 6 7
- Character T 4 2 4 X 1 A
The decimal follows the third character in the displayed code. Removing X produces an invalid structure. That invalidity is a coding conclusion; the specific clearinghouse rejection, claim-edit response, or payment outcome depends on the receiving system and applicable process.
Seventh characters have meanings defined by their category. Do not assume every seventh character describes encounter phase. Injury categories may describe treatment phase or fracture healing, while obstetric categories may identify the fetus. Read the applicable instructions before assigning the character.
Read punctuation in its location
Mark Meaning Practical consequence
Brackets in the Tabular List Synonyms, alternative wording, or explanatory phrases Read them as part of understanding the entry
Brackets in the Alphabetic Index Manifestation-code notation Sequence the bracketed manifestation after its underlying etiology
Parentheses Nonessential modifiers The enclosed wording may be present or absent without changing the assigned entry, subject to the Index structure
Colon in the Tabular List An incomplete term followed by necessary modifiers Read the indented terms to complete the meaning
Nonessential modifiers do not override a mutually exclusive subentry. The guidelines illustrate this with the Index entry for enteritis: acute is a nonessential modifier, but chronic is a separate subentry. Reading only the main line would miss that distinction. A CDI reviewer should therefore examine the indentation and subterms instead of treating every parenthetical modifier as universally applicable to all descendants.
NEC , not elsewhere classifiable, generally points to an other-specified code when the documented condition has no dedicated code. NOS , not otherwise specified, corresponds to unspecified. Missing documentation and a classification that lacks a unique code are different problems. More detail cannot create a code that does not exist; conversely, an unspecified entry should not replace supported available specificity.
Excludes1 and Excludes2
An Excludes1 note generally bars using the excluded code with the code above the note. The guidelines recognize an exception when the two conditions are unrelated. If their relationship is unclear, query the provider. Do not resolve the issue by assuming that any conditions in different organs are necessarily unrelated.
The guidelines' example involves F45.8 , other somatoform disorders, and G47.63 , sleep related bruxism. F45.8 includes teeth grinding and excludes sleep-related teeth grinding. The same teeth-grinding condition should not be represented twice through those entries. However, the guidelines permit F45.8 for psychogenic dysmenorrhea together with G47.63 for sleep-related teeth grinding when those are the two unrelated conditions. The documented conditions and actual note determine the result.
An Excludes2 note means the excluded condition is not included in the code. Both conditions may be reported when appropriate. It does not waive documentation, reportability, or other classification requirements. In either case, verify that the note actually exists in the applicable release, including inherited notes at the parent level; do not manufacture an Excludes2 note merely because two diagnoses can coexist.
Sequencing instructions have distinct effects
Code first and use additional code instructions govern code relationships and order. In an etiology/manifestation pair, sequence the underlying disease before the manifestation. Codes titled in diseases classified elsewhere cannot be principal or first-listed and require the underlying condition. The instruction establishes relative order; it does not impose a universal requirement that the codes occupy immediately adjacent claim positions.
These instructions also occur outside classic etiology/manifestation pairs. Read the actual note and all applicable guidelines. A use-additional-code instruction may require information such as the type or stage of a condition. Do not assume it always means that the second condition is a manifestation code that can never be principal under any circumstances.
For example, I11.0 , hypertensive heart disease with heart failure, instructs use of an additional code to identify the heart failure type. I50.23 describes acute on chronic systolic (congestive) heart failure; I50.21 describes acute systolic (congestive) heart failure. Those descriptions are not interchangeable. Select the supported acuity and apply the sequencing instruction rather than stopping at a generic heart-failure label.
A code also note indicates that two codes may be necessary, but does not itself direct sequencing. Determine order from the encounter circumstances and other applicable instructions. This is not permission to disregard a separate code-first requirement.
Relational terms and the limits of presumed linkage
In code titles, and is interpreted as and/or. The general with/in convention in Section I.A.15 presumes an association where the classification specifically links the conditions. It does not mean that every pair of coexisting diagnoses is related. The presumption does not apply when documentation clearly states that the conditions are unrelated or another guideline specifically requires documented linkage.
Hypertension and heart failure illustrate a supported presumption. Under Section I.C.9.a.1, the classification presumes their relationship unless documentation clearly states otherwise. For a patient with hypertension and acute on chronic systolic heart failure, without chronic kidney disease or another relevant modifying circumstance, I11.0 with I50.23 represents that relationship and specified heart failure type. The mere absence of the provider's words due to does not require a linkage query.
Sepsis with an acute organ dysfunction illustrates why the exception matters. Section I.C.1.d requires association between the acute organ dysfunction and sepsis to assign severe sepsis. If the record does not clearly establish whether the dysfunction is related to sepsis or another condition, query the provider. Coexistence alone does not supply the required relationship.
For an exam scenario, use four checks: verify the complete code, read inherited notes, apply the correct relationship and sequence, and resolve actual documentation uncertainty. This process prevents a correct disease name from producing an incomplete code or an unsupported combination.
Examples above were checked against the official FY2027 Tabular List and Index and complete code descriptions .