This guide organizes sixty teaching concepts into ten sequenced groups, moving from ICD-10-CM conventions through principal diagnosis selection, infection coding, inpatient depth, outpatient reporting, documentation integrity, provider queries, regulatory compliance, and health information technology. Work the groups in order, since later material assumes earlier rules. Each concept pairs a rule with a resolved example and a common error. Use it alongside the official codebooks, official guidelines, and current AHIMA materials; it is independent study support, not an official syllabus or a substitute for primary sources.
ICD-10-CM Structure and Conventions
1. Index-Then-Tabular Workflow
Locate every diagnosis term first in the Alphabetic Index, then verify the code in the Tabular List before assignment. The classification's own conventions and instructions always take precedence over the official guidelines, so a Tabular note can override a general guideline you remember.
Example: Index leads to a code, but the Tabular entry carries an Excludes1 blocking it. Decision: follow the Tabular note and choose the alternative code, because conventions outrank guidelines.
Mistake to avoid: Assigning a code straight from the Alphabetic Index without verifying Tabular instructions and notes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
2. Placeholder Character X
When a code requires a seventh character but has fewer than six characters, fill the empty positions with the placeholder X so the code reaches the required length. A code with an applicable seventh character is invalid without that character, making placeholder use a validity requirement, not a style choice.
Example: A five-character code needs an extension character for episode of care and is invalid as written. Decision: insert X placeholders, then the seventh character, because the code is incomplete otherwise.
Mistake to avoid: Submitting a shortened code without X placeholders when a seventh character applies.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
3. Excludes1 Versus Excludes2
An Excludes1 note means the excluded code is never reported with the code above it, because the conditions cannot coexist, such as congenital versus acquired forms. An Excludes2 note means the excluded condition is separate but may be coded together when both exist. The unrelated-conditions exception can override an Excludes1.
Example: A patient has two conditions linked by an Excludes1 note but they are clearly unrelated. Decision: report both codes, because the exception applies when the conditions are independent.
Mistake to avoid: Treating every Excludes note as a prohibition and dropping a legitimately coexisting condition.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
4. The With Presumption
In titles, index subterms, and instructional notes, the word with or in means associated with or due to, and the classification presumes a causal link even without provider documentation connecting the conditions. Code them as related unless documentation states they are unrelated or a specific guideline demands documented linkage.
Example: Diabetes with a listed complication term is indexed together without explicit linkage. Decision: code the combination as related, because the classification presumes the association.
Mistake to avoid: Splitting conditions the classification links with with just because the provider did not restate the connection.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
5. Interpreting And in Titles
The word and in a code title or index entry should be read as and or, so a single subcategory can cover either component alone or both together. This prevents coders from requiring both elements before using a code that actually applies to either presentation.
Example: Documentation mentions bone involvement only, under a bones-and-joints subcategory. Decision: assign that subcategory, because and means and or in the classification.
Mistake to avoid: Withholding a code because only one of the and-linked sites is documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
6. Default Codes
A default code is the one printed next to a main term in the Alphabetic Index, representing the most common condition or the unspecified form. When a condition is documented without qualifying detail such as acute or chronic, assign the default code rather than guessing a more specific subtype.
Example: Appendicitis is documented with no acuity qualifier. Decision: assign the default code listed at the main term, because no detail supports a different choice.
Mistake to avoid: Selecting an acute or otherwise specific code when the record lacks the qualifying detail.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
General Diagnosis Coding Rules
7. Provider Statement Over Clinical Criteria
Code assignment rests on the provider's diagnostic statement that a condition exists, not on the clinical criteria or test results the provider used to reach it. If the record contains conflicting diagnostic statements, the correct response is a provider query, not an independent weighing of evidence.
Example: Labs suggest a condition the provider never names. Decision: do not code it, because only the provider's stated diagnosis drives assignment.
Mistake to avoid: Coding a diagnosis inferred from laboratory values or clinical findings the provider did not state.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
8. Other-Clinician Documentation Exceptions
Only the patient's provider establishes diagnoses, with narrow exceptions: 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 itself still requires provider documentation.
Example: A nurse stages a pressure ulcer, and the provider documents the ulcer diagnosis. Decision: use the nurse's stage with the provider's diagnosis, because staging is an allowed exception.
Mistake to avoid: Coding obesity or another associated diagnosis from a dietitian's note without provider documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
9. Acute and Chronic Together
When the same condition is documented as both acute and chronic, and separate subentries exist at the same indentation level in the Alphabetic Index, assign both codes and sequence the acute code first. If only one subentry exists, that single code covers the combined presentation.
Example: The record documents acute and chronic forms of one condition with separate index subentries. Decision: code both, acute first, per the sequencing rule.
Mistake to avoid: Sequencing the chronic code first or dropping one of the two documented forms.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
10. Combination Code Priority
A combination code captures two diagnoses, a diagnosis with a manifestation, or a diagnosis with a complication in one code. When a combination code fully identifies all documented elements, assign only it; multiple coding is wrong when the classification already provides the combination.
Example: Two related documented conditions map to one combination code. Decision: assign only the combination code, because multiple coding is not permitted when it fully identifies the picture.
Mistake to avoid: Reporting separate codes for elements a single combination code already captures.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
11. Laterality Conflicts
When the provider does not document the affected side, laterality may be taken from other clinicians' documentation. If record entries conflict about the side, query the provider rather than choosing one. Unspecified-side codes should be rare, used only when clarification is impossible.
Example: One note says right and another says left for the same condition. Decision: query the provider, because conflicting laterality cannot be resolved by the coder.
Mistake to avoid: Assigning an unspecified-side code when a query could resolve the conflicting documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
12. Signs, Symptoms, and Unspecified Codes
Sign, symptom, and unspecified codes have legitimate uses: report them when no definitive diagnosis is established by encounter end, or when documentation supports only a general condition. Never select a specific code unsupported by the record or push for medically unnecessary testing to gain specificity.
Example: Pneumonia is diagnosed but the type is not identified. Decision: assign the unspecified pneumonia code, because it best reflects what is known.
Mistake to avoid: Choosing a bacterial or other specific code without documentation identifying the type.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Principal Diagnosis Selection and Sequencing
13. Principal Versus First-Listed Framework
Section II of the official guidelines governs principal diagnosis selection for non-outpatient settings, Section III covers additional diagnoses there, and Section IV governs outpatient reporting with a first-listed condition. Determining the setting first tells you which rule set applies before any sequencing decision.
Example: A hospital inpatient discharge and a clinic visit both list several conditions. Decision: apply Section II rules to the inpatient stay and Section IV rules to the clinic visit.
Mistake to avoid: Applying outpatient first-listed logic to an inpatient stay, or inpatient logic to outpatient visits.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AHIMA: Certified Coding Specialist (CCS) exam content outline
14. Symptoms When No Definitive Diagnosis
For inpatient stays, when no definitive diagnosis is established by discharge, the principal diagnosis may be a symptom, sign, or ill-defined condition. This rule exists specifically for non-outpatient settings and should not be exported to outpatient encounters, which follow different guidance.
Example: A patient is discharged after workup with only symptoms documented. Decision: use the symptom code as principal, because no definitive diagnosis was reached.
Mistake to avoid: Forcing a suspected diagnosis into principal position after an inconclusive inpatient workup.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
15. Two Interrelated Conditions
When two or more interrelated conditions each potentially meet the definition of principal diagnosis, either condition may be sequenced first, unless the circumstances of the admission, the therapy provided, the Tabular List, or another guideline indicate a specific sequencing order. This flexibility does not extend to a symptom followed by a related definitive diagnosis at discharge: in that situation, the definitive diagnosis is sequenced as the principal diagnosis.
Example: Abdominal pain prompts the admission, and appendicitis is confirmed at discharge. Decision: sequence appendicitis as the principal diagnosis, because a symptom followed by its related definitive diagnosis is not an either-or choice.
Mistake to avoid: Sequencing the admission symptom as principal after the related definitive diagnosis was established at discharge, or assuming a fixed order is required for truly interrelated conditions.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
16. Uncertain Diagnosis by Setting
At inpatient discharge, documented uncertain diagnoses such as suspected or probable conditions are coded as if confirmed, with HIV as a notable exception requiring confirmed cases only. In outpatient settings, uncertain diagnoses are not coded; report signs, symptoms, or related confirmed findings instead.
Example: A discharge note says probable condition, and the setting is inpatient. Decision: code it as confirmed, because the inpatient rule applies, unlike outpatient reporting.
Mistake to avoid: Coding an outpatient probable diagnosis as if confirmed, ignoring the setting distinction.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
17. Manifestation Codes Never Principal
Codes titled in diseases classified elsewhere are manifestation codes that must never serve as principal or first-listed diagnoses. They follow the underlying etiology code, which is identified by code first notes and by bracketed entries in the Alphabetic Index that always sequence second.
Example: Dementia in another disease is documented with an underlying disease present. Decision: sequence the underlying disease first, because the dementia code is a manifestation.
Mistake to avoid: Listing a manifestation code as principal without its required underlying etiology code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
18. Code-Also Notes Lack Sequencing
A code also note signals that two codes may be needed to fully describe one condition but gives no sequencing direction; order depends on encounter circumstances. Distinguish it from code first and use additional code notes, which do fix sequence, and from code, if applicable, any causal condition first notes.
Example: A code also note appears under a condition needing a companion code. Decision: assign both, then sequence by encounter circumstances, because the note sets no order.
Mistake to avoid: Treating a code also note as a mandatory sequencing instruction like code first.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Infection Coding: HIV and Sepsis
19. HIV Confirmed Cases Only
Code only confirmed cases of HIV infection or illness, an exception to the inpatient rule that codes uncertain diagnoses as confirmed. Confirmation does not require positive serology or culture; the provider's statement that the patient is HIV positive or has an HIV-related illness suffices.
Example: An inpatient note says suspected HIV with no provider confirmation. Decision: do not assign the HIV code, because only confirmed cases are coded.
Mistake to avoid: Assigning HIV codes from a pending or suspected status, or demanding lab proof the guideline does not require.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
20. B20, Z21, and R75 Distinctions
Assign B20 for HIV disease, AIDS, or any HIV-related illness, and once B20 applies it stays on every subsequent encounter. Z21 describes asymptomatic HIV positive status, and R75 covers inconclusive serology. Patients previously coded B20 never revert to R75 or Z21.
Example: A patient with past HIV-related illness returns for an unrelated injury. Decision: report B20 as secondary, because prior B20 status persists.
Mistake to avoid: Assigning Z21 or R75 to a patient with documented previous HIV-related illness.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
21. HIV Sequencing Scenarios
When admission is for an HIV-related condition, B20 is principal, followed by codes for the related conditions. When a patient with HIV disease is admitted for an unrelated condition, the unrelated condition is principal and B20 is secondary. New versus previous diagnosis does not change sequencing.
Example: A patient with HIV disease is admitted for a traumatic injury. Decision: sequence the injury as principal, with B20 secondary, per the unrelated-condition rule.
Mistake to avoid: Automatically sequencing B20 first regardless of the actual reason for this admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
22. HIV in Pregnancy
When a patient presents during pregnancy, childbirth, or the puerperium with symptomatic HIV disease, assign the obstetric complication code from the relevant subcategory first, then B20, then codes for HIV-related illness. Chapter 15 obstetric codes always take sequencing priority in these combinations.
Example: A pregnant patient with documented HIV disease receives care. Decision: sequence the pregnancy complication code first, then B20, because Chapter 15 takes priority.
Mistake to avoid: Sequencing B20 before the obstetric complication code during pregnancy, childbirth, or puerperium.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
23. Sepsis and Severe Sepsis Sequencing
Coding severe sepsis requires the underlying systemic infection code first, then the severe sepsis subcategory code, then codes for associated acute organ dysfunction. When sepsis follows a localized infection such as pneumonia, the systemic infection code precedes the localized infection code.
Example: Pneumonia progresses to severe sepsis with organ dysfunction. Decision: sequence the systemic infection, then severe sepsis, then the dysfunction and pneumonia codes.
Mistake to avoid: Sequencing the localized infection or organ dysfunction before the systemic infection and severe sepsis codes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. Urosepsis Requires a Query
The term urosepsis is nonspecific and is not synonymous with sepsis; it has no default code in the Alphabetic Index. When a provider documents urosepsis, query for clarification rather than assuming sepsis. Similarly, negative or inconclusive blood cultures do not rule out sepsis but warrant a query.
Example: A note lists urosepsis with no further detail. Decision: query the provider, because the term cannot be coded as sepsis by assumption.
Mistake to avoid: Coding urosepsis as sepsis without querying, or treating negative cultures as disproving sepsis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Inpatient Reporting Depth
25. Additional Diagnoses in Non-Outpatient Settings
Section III governs which additional diagnoses are reported beyond the principal diagnosis in non-outpatient settings. Review the entire record to identify conditions treated or monitored during the stay, distinguishing conditions that meet reporting criteria from historical mentions requiring no code.
Example: A chronic condition is actively monitored during the stay and another is only listed as history. Decision: report the monitored condition as additional, omit the historical one.
Mistake to avoid: Reporting every mentioned condition without evaluating its role in the current admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AHIMA: Certified Coding Specialist (CCS) exam content outline
26. Present on Admission Application
Present on admission guidelines, found in the official guidelines appendix, require determining whether each reported condition existed at admission. POA reporting interacts with hospital-acquired condition identification, so accurate indicator assignment depends on documentation timing rather than coder assumption.
Example: A condition is first documented two days into the stay with no admission evidence. Decision: report it as not present on admission, because documentation timing drives the indicator.
Mistake to avoid: Defaulting POA indicators without checking when each condition was first documented in the record.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline; CDC ICD-10-CM Official Guidelines, FY 2027
27. Identifying MCC and CC Conditions
A CCS competency is identifying major comorbid conditions and comorbid conditions from provider documentation, because these classifications affect diagnosis-related grouping and reimbursement. Identification rests on documented conditions meeting defined criteria, never on coder speculation about what would raise reimbursement.
Example: A documented comorbid condition meets major comorbid criteria under the grouping logic. Decision: report it accurately as documented, letting the grouper assign the category.
Mistake to avoid: Searching for or inferring comorbidities to elevate grouping rather than coding what is documented.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline; Certified Coding Specialist (CCS)
28. Complications of Care
Code assignment for complications depends on the provider documenting a relationship between the condition and the care or procedure. A cause-and-effect link and clinical significance must be supported, though the word complication need not appear; a condition altering the surgical course qualifies. Query when the relationship is unclear.
Example: A postoperative condition is documented as altering the operative course. Decision: assign the complication code, because the documented relationship qualifies even without the label.
Mistake to avoid: Coding every post-surgery condition as a complication without documented cause and effect.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Postprocedural Sepsis Sequencing
For sepsis following a postprocedural surgical site infection, sequence the code identifying the infection site first, then the code for sepsis following a procedure, then an organism code, and severe sepsis and organ dysfunction codes when applicable. The provider must document the relationship between infection and procedure.
Example: Documented surgical site infection progresses to sepsis after the operation. Decision: sequence the site infection code, then postprocedural sepsis, because the relationship is documented.
Mistake to avoid: Sequencing sepsis before the postprocedural site infection code, or coding the link without provider documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Abstracting Record Data
Beyond code assignment, the CCS role includes abstracting applicable data from the health record, such as discharge details and other required data set elements. Abstraction means faithfully extracting documented elements; it never includes creating or estimating values absent from the record.
Example: A required discharge data element is missing from the record. Decision: leave it unabstracted and follow facility correction processes, because abstraction cannot invent values.
Mistake to avoid: Filling in missing data elements from memory or assumption instead of the record.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
Outpatient and Ambulatory Coding
31. Outpatient First-Listed Selection
Section IV provides the rules for selecting the first-listed condition in outpatient settings, parallel to principal diagnosis rules for inpatients. The first-listed condition is generally the reason for the encounter as established after reviewing the entire record, not simply the first condition mentioned.
Example: A clinic note lists several chronic conditions but the visit addressed one acute problem. Decision: sequence the acute reason as first-listed after full record review.
Mistake to avoid: Sequencing the first condition written in the note rather than the reason for the encounter.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AHIMA: Certified Coding Specialist (CCS) exam content outline
32. Outpatient Surgery First-Listed
For outpatient surgery, code the reason for the surgery as the first-listed diagnosis, unless the surgery was performed for a postoperative complication, in which case the complication code comes first. This distinction mirrors inpatient logic but lives in the outpatient section.
Example: A patient returns to the ambulatory suite for a documented postoperative complication. Decision: sequence the complication first, because the surgery addressed it.
Mistake to avoid: Always sequencing the original reason when the procedure actually treated a complication.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
33. Observation Stay Coding
The official guidelines address observation stays within the outpatient section, providing direction for selecting the first-listed condition when a patient is placed in observation rather than admitted. Apply the outpatient rule set to these stays rather than inpatient principal diagnosis rules.
Example: A patient spends the encounter in observation status with several documented conditions. Decision: apply outpatient first-listed guidance, because observation falls under Section IV.
Mistake to avoid: Applying inpatient principal diagnosis selection rules to a stay in observation status.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
34. Chronic Disease and Therapeutic Services
The outpatient guidelines address encounters for chronic diseases and for patients receiving therapeutic services only. When the encounter is for management of a chronic condition, that condition is reported as the first-listed diagnosis rather than a symptom or incidental finding.
Example: A patient presents solely for ongoing management of a documented chronic disease. Decision: report that disease as first-listed, because the encounter is therapeutic management.
Mistake to avoid: Coding a symptom as first-listed when the documented purpose was chronic disease management.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
35. CPT/HCPCS Modifiers on Outpatient Procedures
A CCS competency is attaching CPT/HCPCS modifiers to outpatient procedures to convey circumstances that affect reporting. Modifier choice must follow codebook instructions and payer guidance for the specific encounter; there is no universal modifier shortcut that fits every scenario.
Example: An outpatient procedure carries a documented circumstance requiring modifier reporting. Decision: attach the modifier supported by that documentation and the codebook instruction, not habit.
Mistake to avoid: Appending a favorite modifier routinely without matching it to documented circumstances.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
36. Screening Versus Exam With Findings
The outpatient guidelines distinguish encounters for general medical examinations with abnormal findings from routine health screenings. When a screening exam yields abnormal findings, report the finding; a routine screening encounter without findings is reported with the screening reason.
Example: A routine screening encounter documents an abnormal finding. Decision: code the abnormal finding as the reason, because the guidelines direct reporting the finding.
Mistake to avoid: Reporting only the screening reason code when the exam documented an abnormal finding.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Documentation Integrity
37. Resolving Conflicting Documentation
A core CCS task is resolving conflicting documentation in the health record, including admission type and laterality discrepancies. Where the conflict affects code assignment, the resolution path is a provider query; the coder never arbitrates between conflicting entries independently.
Example: The history lists one admission type and the order another. Decision: query for clarification, because admission type drives rule selection and cannot be coder-chosen.
Mistake to avoid: Picking whichever conflicting entry appears latest or seems most clinically plausible.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline; CDC ICD-10-CM Official Guidelines, FY 2027
38. Required Documentation Completeness
Before assigning a specified code, ensure all required documentation exists within the body of the health record. A code demanding laterality, acuity, or other specificity cannot be assigned at that level if the supporting element is absent, regardless of how likely the detail seems.
Example: A specified code requires a detail the record never documents. Decision: use the less specified code or query, because the required element is missing.
Mistake to avoid: Assigning the specified code on the assumption the missing detail was intended.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
39. Verifying and Validating the Record
Verification and validation mean confirming that documentation supporting each code actually exists and is internally consistent, including authorship, dates, and amendments. This is a distinct skill from code lookup: a correctly chosen code is still wrong if its documentation fails validation.
Example: A code is supported by an entry that fails validation checks. Decision: hold the code and resolve the documentation issue, because assignment depends on valid documentation.
Mistake to avoid: Treating accurate code selection as sufficient without validating the underlying record documentation.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
40. Entire Record Review
The official guidelines direct reviewing the entire record to determine the specific reason for the encounter and the conditions treated. Complete, consistent documentation is the precondition for accurate coding, so partial review risks missing reportable conditions or the true reason for care.
Example: The discharge summary names one reason, but the full record shows another condition drove the stay. Decision: base selection on the entire record, because full review is required.
Mistake to avoid: Coding from the discharge summary alone without reviewing the full encounter record.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
41. Borderline Diagnoses
A provider-documented borderline diagnosis at discharge is coded as confirmed unless the classification provides a specific entry for that borderline condition, in which case the specific code applies. No inpatient versus outpatient distinction exists for borderline conditions; query whenever the documentation is unclear.
Example: A borderline condition without a specific index entry is documented at discharge. Decision: code it as confirmed, because borderline conditions are not uncertain diagnoses.
Mistake to avoid: Treating borderline documentation as uncertain and refusing to code it as confirmed.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
42. Coding Syndromes
For syndromes, follow the Alphabetic Index guidance first. In the absence of index direction, assign codes for the documented manifestations of the syndrome, and additional codes for manifestations that are not integral to the disease process when no unique code exists.
Example: A documented syndrome has no index entry listing a single code for it. Decision: code the documented manifestations, because index guidance is absent here.
Mistake to avoid: Inventing a single syndrome code when the index offers none and manifestations are documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Provider Queries
43. Elements of a Compliant Query
An ethical, compliant query presents a non-leading question with appropriate clinical indicators from the record and offers the clinically reasonable options for the provider to consider. It documents the issue, invites the provider's independent judgment, and never implies a preferred answer.
Example: A query lists record-based indicators and multiple diagnostic options without favoring one. Decision: accept it as compliant, because it is non-leading and indicator-based.
Mistake to avoid: Omitting clinical indicators or building the query around a desired reimbursement outcome.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
44. Non-Leading Question Construction
Determining query compliance centers on whether the question is non-leading and contains appropriate clinical indicators. Leading language suggests, implies, or pressures a particular diagnosis; compliant language asks what the provider concludes from the documented indicators, leaving the answer open.
Example: A draft asks whether a condition is present given listed indicators, offering several options. Decision: approve the wording, because it does not steer toward one answer.
Mistake to avoid: Phrasing a query so the documented indicators point to only one acceptable answer.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
45. Identifying Query Opportunities
Analyze current documentation to spot query opportunities: conflicting entries, ambiguous terminology like urosepsis, uncertain relationships between conditions and care, and missing specificity a code requires. A query is triggered by documentation gaps, not by a desire to change a code's financial effect.
Example: Documentation shows sepsis with organ dysfunction of unclear relationship. Decision: query the provider, because the linkage is ambiguous and affects code choice.
Mistake to avoid: Querying to upgrade reimbursement rather than to resolve a genuine documentation ambiguity.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline; CDC ICD-10-CM Official Guidelines, FY 2027
46. Querying Laterality and Conflicts
Conflicting documentation about the affected side, admission type, or similar elements requires querying the patient's provider for clarification. Other clinicians' documentation can supply laterality when the provider is silent, but a conflict between sources always escalates to a provider query.
Example: Radiology says one side and the progress note the other. Decision: query the provider, because conflicting laterality cannot be resolved from ancillary documentation.
Mistake to avoid: Resolving a laterality conflict by preferring the specialist note over the provider's documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AHIMA: Certified Coding Specialist (CCS) exam content outline
47. Querying Unclear Excludes1 Relationships
When two conditions tied by an Excludes1 note may actually be unrelated, and the record does not make the relationship clear, the guideline directs the coder to query the provider. Only documented unrelatedness justifies reporting both codes despite the Excludes1 note, making this a convention-driven query trigger.
Example: Two Excludes1-linked conditions appear in the record with no stated relationship between them. Decision: query the provider, because reporting both requires documented unrelatedness.
Mistake to avoid: Reporting both Excludes1-linked codes on coder judgment without documented unrelatedness or a query.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
48. Querying Complication Relationships
For complications of care, code assignment depends on the provider documenting the relationship between the condition and the care or procedure. When documentation is unclear about that relationship, query rather than assuming; not every condition following surgery qualifies as a complication.
Example: A condition arises after surgery with no documented link to the procedure. Decision: query about the relationship, because complication coding requires documented cause and effect.
Mistake to avoid: Assuming that timing alone establishes a complication relationship without documented provider linkage.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027; AHIMA: Certified Coding Specialist (CCS) exam content outline
Regulatory Compliance
49. UHDDS Compliance
The Uniform Hospital Discharge Data Set defines standard data elements and definitions, such as the principal diagnosis definition, that hospital discharge reporting must follow. CCS work includes ensuring coded discharge data conforms to these uniform definitions so hospital data remains comparable across facilities and over time.
Example: A facility defines principal diagnosis differently than the uniform data set. Decision: apply the uniform definition, because discharge data compliance overrides local custom.
Mistake to avoid: Applying a facility-specific principal diagnosis definition that conflicts with the uniform data set.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
50. PSIs and HACs From Documentation
Patient safety indicators and hospital-acquired conditions are identified based on the provider's documentation, not on coder suspicion. Distinguish conditions present at admission from those developing during care; a condition documented only after admission is not automatically acquired, but timing evidence matters.
Example: A condition is first documented days after admission with no prior mention. Decision: evaluate it against hospital-acquired criteria using documentation timing, without assuming acquisition.
Mistake to avoid: Flagging a hospital-acquired condition from coder inference rather than documented evidence and timing.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
51. HIPAA Covered Entities
The Privacy Rule covers health plans, health care clearinghouses, and providers who transmit health information electronically in connection with standard transactions such as claims. Using email alone does not make a provider covered; the transmission must relate to a standard transaction. Business associates performing services need written agreements.
Example: A small practice bills electronically through a clearinghouse. Decision: treat it as a covered provider, because standard transactions occur on its behalf.
Mistake to avoid: Assuming a provider is covered merely because it uses email, or ignoring business associate agreements.
Reference: HHS Summary of the HIPAA Privacy Rule
52. PHI Scope and De-Identification
Protected health information is individually identifiable health information in any form, electronic, paper, or oral, held by a covered entity or business associate. De-identified information, achieved by removing specified identifiers with no actual knowledge of re-identifiability, carries no use or disclosure restrictions.
Example: A dataset has the specified identifiers removed with no known re-identification risk. Decision: treat it as de-identified, because the removal method satisfies the rule.
Mistake to avoid: Stripping only the patient name and assuming the remaining data is de-identified.
Reference: HHS Summary of the HIPAA Privacy Rule
53. Minimum Necessary Standard
Covered entities must make reasonable efforts to use, disclose, and request only the minimum protected health information needed for the purpose, and generally may not send whole records without specific justification. The standard does not apply to treatment disclosures, individual access, authorized uses, or legally required disclosures.
Example: A routine request could be fulfilled with a code summary rather than the whole record. Decision: send the minimum, because no exception applies to that disclosure.
Mistake to avoid: Releasing entire medical records for routine purposes without a specific justification for the whole record.
Reference: HHS Summary of the HIPAA Privacy Rule
54. Ethical Coding Standards
CCS work must adhere to the AHIMA Standards of Ethical Coding: assign codes only from documentation in the record, refuse to change codes solely to manipulate reimbursement, and query when documentation is inadequate. Ethical violations by credentialed professionals are reviewable through a formal complaint process.
Example: A supervisor asks for a higher-paying code unsupported by documentation. Decision: refuse and follow the documented code, because ethical standards prohibit unsupported assignment.
Mistake to avoid: Adjusting code assignment under reimbursement pressure rather than the record's documentation.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline; Certified Coding Specialist (CCS)
Information Technology and Reimbursement
55. EHR Types
A CCS competency is distinguishing various types of electronic health records, such as records differing by care setting and architecture. Recognizing how a record system organizes encounters, notes, and results affects where the coder locates authoritative documentation for assignment decisions.
Example: An encounter-based record separates visits from a longitudinal record. Decision: search the correct structure for the discharge documentation, because record type determines location.
Mistake to avoid: Assuming all record systems present documentation identically regardless of type or setting.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
56. Encoder and Grouper Software
Encoding software assists code lookup and logic checking, while grouper software assigns payment categories from the coded data. The coder validates both outputs: software suggestions are decision support, and final assignment responsibility remains with the credentialed coder, not the tool.
Example: The grouper returns a payment category from entered codes. Decision: verify the codes first, because the grouping is only as valid as the coded data.
Mistake to avoid: Accepting encoder or grouper output as final without validating the underlying code assignment.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
57. Computer-Assisted Coding
Computer-assisted coding software analyzes record text and suggests codes, affecting coder workflow by accelerating identification of candidate diagnoses and procedures. Its impact requires coder review: suggestions remain unverified until a coder confirms documentation support for each proposed code before it is reported.
Example: CAC software proposes several codes from the discharge text. Decision: review each suggestion against the documentation, because proposals are drafts requiring coder validation.
Mistake to avoid: Reporting computer-suggested codes without confirming documentation support for each individual suggestion.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
58. HITECH Compliance
The CCS information technology domain includes ensuring compliance with HITECH guidelines, the federal framework that strengthened health information technology adoption and reinforced privacy and security expectations for electronic records. Coders working with electronic records operate within these safeguards when accessing and transmitting data.
Example: A coding workflow moves record data through an electronic portal. Decision: follow the entity's HITECH-aligned safeguards, because electronic handling falls under these requirements.
Mistake to avoid: Treating electronic record handling as outside privacy and security compliance obligations entirely.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline
59. Coding Edits and Medical Necessity
A CCS competency includes knowledge of coding edits, such as National Correct Coding Initiative edits and medical necessity checks. Edits flag code combinations and coverage questions; resolving them requires distinguishing codebook rules from payer-specific policy, since a code pair may be valid under CPT yet flagged by payer edits.
Example: An edit flags a code pair the codebook permits. Decision: resolve per payer policy for that claim, because edits reflect payer rules beyond the codebook.
Mistake to avoid: Assuming an edit failure always means the CPT codes themselves are invalid.
Reference: AHIMA: Certified Coding Specialist (CCS) exam content outline; Certified Coding Specialist (CCS)
60. DRG and APC Methodologies
Reimbursement methodologies differ by setting: diagnosis-related grouping drives inpatient hospital payment, while ambulatory payment classifications apply to outpatient hospital services. Both derive from coded data, which is why diagnosis sequencing and completeness directly shape hospital reimbursement across settings.
Example: The same condition is coded for an inpatient stay and an outpatient visit. Decision: expect different payment groupings, because each setting uses its own methodology.
Mistake to avoid: Applying inpatient grouping logic to outpatient hospital claims, or assuming one methodology fits both.
Reference: Certified Coding Specialist (CCS); AHIMA: Certified Coding Specialist (CCS) exam content outline
References and further reading
Source links checked on Oct 2, 2026.