Health Information & Coding · Independent exam preparation

CCDS-O: Outpatient Documentation Decisions, Risk Adjustment, and Compliance Study Guide

Practise outpatient diagnosis selection, clinical clarification, CMS-HCC reasoning, query compliance, and CDI metrics through focused cases and calculations.

By CertMedbry · Updated 29 October 2026

60 concepts explainedWorked examples & common pitfallsOfficial blueprint references

Learn to distinguish reportable diagnoses from clinical clues, resolve documentation gaps without leading providers, interpret risk adjustment, and evaluate outpatient CDI performance. Cases connect chart evidence to coding, payment, quality, and compliance decisions in U.S. outpatient settings. These 60 concepts provide selective coverage across all five CCDS-O domains; the official ACDIS content outline defines the full examination scope.

Try 20 free practice questions

What is the exam format?

Check the question types, timing and outline before planning your revision.

Which credential and eligibility pathways does this guide address?

The guide addresses CCDS-O. The May 2024 handbook requires an RN, MD, DO, or specified coding credential, plus either two years of outpatient CDI experience or one year each of inpatient and outpatient CDI experience using U.S. reimbursement systems. Both eligibility pathways lead to the same CCDS-O examination. Clinical documentation performed solely as a treating clinician does not satisfy the CDI experience requirement.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

How many questions are scored, and which item styles are verified?

The CCDS-O examination contains 140 multiple-choice questions: 120 scored questions and 20 unscored pretest questions distributed throughout the examination. Candidates cannot identify the pretest questions. The handbook describes recall, application, and analysis questions. It does not establish additional item formats for CCDS-O.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

What duration, delivery options, and navigation features are documented?

The handbook allows three hours for the timed examination and describes computer delivery through Prometric testing centers or remote proctoring. Candidates can bookmark questions and return to unanswered items while time remains. One unscheduled 10-minute break is permitted, with the examination timer continuing. The handbook does not describe the examination as computer adaptive.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

Which outline applies, and are official domain weights available?

The currently linked May 2024 handbook gives the five CCDS-O domains on printed pages 14–17. No separate outline effective date, domain percentages, or domain item allocations are stated. ACDIS separately updated the examination to CMS-HCC Version 28 effective October 1, 2024. This guide uses shortened domain labels mapped by Roman numeral and allocates 12 concepts, four questions, and four cards to each domain as an editorial coverage choice.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · About the CCDS-O Certification

Which reference versions does ACDIS currently list for examination preparation?

The application page lists CMS-HCC Version 28, AHA Coding Clinic through First Quarter 2019, FY 2019 ICD-10-CM Official Guidelines, Guidelines for Achieving a Compliant Query Practice, and Queries in Outpatient CDI: Developing a Compliant, Effective Process. The dedicated credential page recommends the second edition of the CCDS-O Exam Study Guide and identifies its first edition as outdated.

How to Apply for the CCDS-O · About the CCDS-O Certification

How should examination reference cutoffs and current practice guidance be distinguished?

The issuer’s listed historical coding cutoffs remain examination references unless ACDIS announces otherwise. Current-practice examples here also use FY 2027 coding guidance, effective October 1, 2026, and the August 2026 ACDIS/AHIMA query guidance, which supersedes earlier query guidance. Those publications do not establish a replacement CCDS-O blueprint. The issuer materials supplied for this guide were checked on October 29, 2026.

How to Apply for the CCDS-O · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice—2026 Update

Which reference book may candidates bring?

ACDIS permits one listed standard drug reference, including Davis’s Drug Guide and the other titles specified in the handbook. Tabs and previously handwritten margin notes are permitted; inserted or attached loose notes and additional pages are prohibited. Candidates may not write in the book during the examination. The inpatient CCDS permission for a DRG reference should not be transferred to CCDS-O.

About the CCDS-O Certification · The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

How should the practice test and calculations be used?

The 20 questions are independent four-option, single-best-answer drills covering all five domains. They are not official examination items or a pass predictor. Risk coefficients, mappings, hierarchies, and departmental datasets identified as hypothetical are teaching assumptions, not official release entries. Real scoring requires the applicable CMS model resources; real metrics require the organization’s defined populations and denominators.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · 2026 Model Software/ICD-10 Mappings

This independent guide prepares for ACDIS’s Certified Clinical Documentation Specialist—Outpatient credential, an experience-based CDI certification using U.S. reimbursement systems. It is distinct from the inpatient CCDS credential and from nursing licensure or advanced-practice certification. The questions are original learning exercises.

Outline used: ACDIS currently linked CCDS/CCDS-O Exam Candidate Handbook, dated May 2024, CCDS-O outline on printed pages 14–17; supplemented by the issuer's CMS-HCC Version 28 exam update effective October 1, 2024. Verified on October 11, 2026. The workbook label maps directly to the official CCDS-O credential, with punctuation differences only; the assigned slug is preserved.

60 key concepts: understand, apply and avoid the traps

Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.

I. Outpatient coding and reimbursementnot stated

1.How is the outpatient first-listed diagnosis selected?

The first-listed diagnosis is the condition, problem, or other reason chiefly responsible for the services provided, evaluated at the highest degree of certainty established for that encounter. Review the actual purpose of the visit rather than choosing the most severe lifelong disease. A symptom can be first-listed when no definitive diagnosis is established. Encounter-specific sequencing instructions, including applicable chapter rules, can modify the general selection process and must be checked before final coding.

Apply it

A patient with stable diabetes attends an urgent visit for new shoulder pain. The clinician evaluates the shoulder and establishes no cause. Shoulder pain supports first-listed selection; diabetes does not displace it merely because it is chronic.

Common pitfall: Selecting the diagnosis with the greatest risk-adjustment impact confuses reimbursement significance with encounter sequencing. The condition chiefly responsible for services remains the starting point.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

2.How are uncertain diagnoses handled in outpatient care?

Outpatient coding does not treat diagnoses documented as probable, suspected, questionable, rule out, or similar uncertainty language as established conditions. Instead, report the highest degree of certainty known for the encounter, such as symptoms, signs, abnormal test results, or another documented reason for the visit. This rule applies to emergency department and observation encounters. Distinguish an unconfirmed disease from a confirmed diagnosis whose severity or subtype remains unspecified.

Apply it

An emergency clinician documents pleuritic chest pain and possible pulmonary embolism, with further testing arranged. No definitive diagnosis is established. The documented chest pain supports reporting; the possible embolism does not become a confirmed outpatient diagnosis.

Common pitfall: Importing the inpatient discharge uncertainty rule into an emergency or observation encounter produces unsupported disease reporting. Hospital location alone does not establish inpatient coding rules.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

3.Which additional conditions belong on an outpatient claim?

Report documented conditions that coexist at the encounter and require or affect patient care, treatment, or management. A diagnosis need not drive the chief complaint to qualify, but its relevance must extend beyond appearing somewhere in the chart. Review assessment, medication decisions, monitoring, and other management connections. Conditions previously treated and no longer present generally are not reported as active diseases; a history code may be appropriate when the history affects current care.

Apply it

During treatment of a skin infection, the clinician adjusts the plan because the patient’s documented CKD limits medication selection. CKD affects management and may be an additional diagnosis even though the infection prompted the visit.

Common pitfall: Automatically transferring every problem-list entry treats historical storage as evidence of encounter relevance. Conversely, reporting only the chief complaint can omit actively managed comorbid conditions.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

4.When can a stable chronic condition be reported?

A chronic condition can be reported repeatedly when the patient receives treatment and care for it. Stability does not mean the disease has resolved, and continued management can support reporting without a medication change. Look for a current assessment, continued therapy, monitoring, or an effect on another care decision. At the same time, chronicity does not authorize automatic carryforward when the encounter contains no support for the condition’s current presence or relevance.

Apply it

At a follow-up visit, the provider documents hypertension as controlled and continues the established treatment plan. The condition remains current and managed. An unchanged prescription does not make the diagnosis historical or unreportable.

Common pitfall: Equating stable with inactive loses legitimate chronic disease information. The opposite error is assuming every longstanding diagnosis qualifies at every encounter without current documentation.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

5.When are symptoms reported with a confirmed disease?

Signs and symptoms routinely associated with a confirmed disease generally are not separately coded unless classification instructions direct otherwise. Symptoms that are not routinely associated may be reported when they meet reporting criteria. First establish whether the provider reached a definitive diagnosis and whether the symptom has a distinct clinical role. This prevents both duplicate representation of one disease process and loss of a separately evaluated problem that remains clinically meaningful.

Apply it

A clinician confirms a respiratory infection and documents cough as part of that illness. Separately evaluated wrist pain has no established relationship to the infection. Review the cough as integral and the wrist pain as a distinct reportable problem.

Common pitfall: Coding every symptom independently can duplicate a confirmed disease’s expected manifestations. Suppressing every symptom once any diagnosis exists can erase unrelated, separately managed problems.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

6.How do history and status codes differ from active disease codes?

A personal history code describes a past condition that no longer exists and is not receiving treatment, but whose history can influence care. A status code describes a current state, such as the presence of a device or an acquired absence, rather than necessarily identifying active disease. Determine what is present now, what treatment continues, and why the information matters today. Disease, history, and status codes represent different clinical facts and are not interchangeable.

Apply it

A patient’s remote malignancy has been eradicated, with no remaining disease or treatment directed to that site. Its history affects surveillance planning. Review history coding rather than carrying the former cancer forward as active solely because surveillance continues.

Common pitfall: A past diagnosis may remain prominent in the record after its clinical state changes. Reusing the old active code can misrepresent both disease burden and current care.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

7.How should specificity and unspecified codes be evaluated?

Assign the most specific code supported by the documentation and classification instructions. Laterality, site, acuity, complication, and other attributes may change code selection, but they cannot be invented to avoid an unspecified code. An unspecified code can be correct when the available clinical information does not establish greater detail. A clarification opportunity is strongest when relevant specificity appears clinically supported but is missing, conflicting, or unclear in the provider’s documentation.

Apply it

A note describes a current left-sided condition, but the selected code is unspecified for laterality. Reconcile the code with the documented detail. In a second record with no established side, do not guess from an old encounter.

Common pitfall: Treating every unspecified code as an error encourages unnecessary queries and unsupported precision. Documentation must establish the attribute before the code can express it.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

8.Which nonprovider documentation can support code assignment?

Diagnosis assignment generally relies on documentation by the provider legally accountable for establishing the diagnosis. The Official Guidelines permit specified exceptions for particular elements, including BMI and certain ulcer details, documented by other clinicians. These exceptions do not give every chart author authority to establish every diagnosis. Apply each exception to its named element, ensure any required associated diagnosis is provider documented, and seek provider clarification when documentation conflicts rather than choosing the preferred author.

Apply it

A nurse records a BMI of 36, while the provider documents obesity and discusses weight management. The BMI can support its corresponding code under the exception. If obesity were absent, the BMI alone would not establish that diagnosis.

Common pitfall: Permission to use a measurement from another clinician does not imply permission to infer its associated disease. Exceptions are element specific and do not resolve conflicting documentation.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

9.When can a diagnostic interpretation establish an outpatient diagnosis?

Section IV.K addresses outpatient encounters for diagnostic services only. When a final physician interpretation is available at coding and establishes a definitive diagnosis, code that confirmed diagnosis. Do not additionally report related signs or symptoms explained by it. This rule does not permit converting raw measurements, uncertain interpretations, or findings requiring clinical correlation into confirmed diseases. Its diagnostic-services-only context also prevents automatically extending it to an ordinary treating encounter.

Apply it

For an imaging-only encounter prompted by wrist pain, an available final physician interpretation definitively identifies a wrist fracture. Report the confirmed fracture rather than the related pain. Contrast an office treatment visit where an imaging report suggests a possible fracture and the treating assessment documents wrist pain without adopting a fracture diagnosis: the diagnostic-services-only rule does not establish a confirmed fracture for that treatment encounter.

Common pitfall: Both encounter purpose and diagnostic certainty matter. A final report saying 'cannot exclude fracture' remains uncertain. Likewise, an unadopted test finding during a treating encounter is not automatically reportable as a disease under Section IV.K; clinically relevant ambiguity may warrant provider clarification.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

10.How do APC grouping and OPPS packaging affect payment?

Under the hospital Outpatient Prospective Payment System, services are classified into ambulatory payment classifications using the applicable payment rules. Some services receive separate payment, while others are packaged into payment for a related service or comprehensive encounter. Packaging concerns payment treatment; it does not mean the service was absent or that accurate reporting is unnecessary. Review the relevant payment year and service status rather than assuming every reported procedure generates an additional independent payment.

Apply it

A hospital outpatient claim includes a principal procedure and a related service designated as packaged under the applicable OPPS rules. The related service contributes to the payment arrangement but does not automatically create another separately payable amount.

Common pitfall: Counting claim lines as separately payable services overstates reimbursement. Conversely, omitting a service solely because payment is packaged can undermine accurate reporting and cost information.

MLN6922507: Medicare Payment Systems

11.How are professional office/outpatient E/M levels selected and distinguished from facility payment?

Professional office/outpatient E/M levels are generally selected using medical decision making (MDM) or the physician's or qualified health professional's qualifying total time on the encounter date. MDM considers problems addressed, data reviewed and analyzed, and management risk; two of these three elements must meet the selected level. Document the assessment, work performed, and management decisions. When selecting by time, document qualifying practitioner time and exclude clinical staff time and separately reported services. A medically appropriate history and examination remain relevant but do not determine the level. Diagnosis count alone does not measure MDM.

Apply it

At an established-patient office visit on October 15, 2026, the practitioner addresses two stable chronic illnesses and documents prescription drug management. Those facts support moderate MDM through the problems and risk elements, consistent with 99214. Alternatively, 35 documented minutes of qualifying practitioner work that day support 99214 by time. A long problem list without documented assessment or management does not establish either basis. In a hospital outpatient clinic, the professional service and facility service still require separate coding and payment analysis.

Common pitfall: Do not add staff minutes or separately billed procedure time to practitioner E/M time. The current office/outpatient selection framework began in 2021. ACDIS's historical FY 2019 ICD-10-CM examination reference is a diagnosis-coding reference, not authority to apply historical E/M selection rules to a 2026 claim.

MLN6922507: Medicare Payment Systems · The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · mln006764-evaluation-management-services.pdf · How to Apply for the CCDS-O

12.Why does an overnight stay not establish inpatient status?

A patient can receive hospital services overnight and remain an outpatient, including while receiving observation services. Inpatient status requires formal admission under the applicable admission process; a bed assignment or elapsed night alone does not establish it. Status affects coverage, cost sharing, and which coding rules apply. CDI review should verify the actual status and admission documentation before applying inpatient concepts, especially when emergency care progresses to observation or later to a formal inpatient admission.

Apply it

A patient receives emergency treatment, remains overnight under observation, and leaves the following afternoon without an inpatient admission order. The stay remains outpatient despite its duration, so outpatient diagnosis-certainty rules govern the observation encounter.

Common pitfall: Using the number of midnights as the sole status test confuses time with formal admission. Observation is an outpatient service even when delivered in a hospital bed.

Inpatient or outpatient hospital status affects your costs

II. Diseases and clinical chart reviewnot stated

13.What establishes the chronicity required for CKD?

KDIGO defines CKD through abnormalities of kidney structure or function present for at least three months and carrying implications for health. Persistent reduced GFR or markers of kidney damage can establish the clinical basis; a single abnormal creatinine or eGFR cannot establish chronicity by itself. Review prior results, albuminuria, imaging, and relevant history. CDI uses those findings to identify clarification opportunities, while the provider establishes the diagnosis and its relationship to the current encounter.

Apply it

A patient has an eGFR of 48 today and comparable values documented five months earlier. The longitudinal pattern supports reviewing for CKD documentation. A first low value during an acute illness would require a different chronicity assessment.

Common pitfall: Calling every reduced eGFR CKD overlooks transient dysfunction and missing duration. Conversely, normal or mildly reduced GFR does not exclude CKD when persistent kidney-damage markers exist.

KDIGO 2024 Clinical Practice Guideline for the Evaluation and Management of Chronic Kidney Disease

14.How do GFR and albuminuria describe different dimensions of CKD?

KDIGO classifies CKD by cause, GFR category, and albuminuria category, often abbreviated CGA. GFR describes filtration, while albuminuria provides a separate marker of kidney damage and prognostic information. G3a corresponds to eGFR 45–59 and G3b to 30–44 mL/min/1.73 m². Albuminuria categories use urine albumin measures, with A2 generally corresponding to an albumin-creatinine ratio of 30–300 mg/g. Similar GFR values can therefore represent different risk profiles when albuminuria differs.

Apply it

Two patients have documented CKD and eGFR values near 50. One has urine ACR 12 mg/g and the other 180 mg/g. Their GFR categories align, but their albuminuria categories differ and should not be treated as interchangeable.

Common pitfall: Reducing CKD assessment to a single filtration number loses cause and albuminuria information. Clinical classification also does not authorize independent coding of an undocumented provider diagnosis.

KDIGO 2024 Clinical Practice Guideline for the Evaluation and Management of Chronic Kidney Disease

15.When does an A1C result support a diabetes diagnosis?

An A1C of at least 6.5% meets a laboratory diagnostic threshold for diabetes when an appropriate standardized test is used. In an asymptomatic patient, confirmation with a repeat test or another diagnostic test is generally required. An A1C of 5.7%–6.4% falls in the prediabetes range. These thresholds guide clinical assessment; they do not authorize CDI staff to assign diabetes without provider documentation or to disregard factors that can make the A1C result unreliable.

Apply it

An asymptomatic patient has a first A1C of 6.6%, with no established diabetes diagnosis. Review the clinician’s plan for confirmation and interpretation. Do not convert the isolated threshold result directly into a coded chronic disease.

Common pitfall: Confusing a diagnostic threshold with a completed diagnosis skips confirmation and provider judgment. Prediabetes-range results also should not be relabeled as diabetes to increase diagnostic capture.

Diabetes & Prediabetes Tests

16.Why can A1C and current glucose findings disagree?

A1C reflects average glycemia over approximately three months, with more recent glucose exposure contributing more strongly than earlier exposure. It therefore differs from a single glucose measurement taken at one moment. Conditions affecting red-cell survival, recent blood loss or transfusion, and some hemoglobin variants can distort interpretation. When A1C and glucose findings disagree, review timing and these limitations rather than assuming one value proves nonadherence, establishes a complication, or invalidates the entire clinical record.

Apply it

A patient recently received a transfusion, and the A1C appears inconsistent with several glucose results. The transfusion is relevant to interpretation. Ask whether the clinician has reconciled the discrepancy before treating the A1C as a reliable summary.

Common pitfall: Treating A1C as an exact current glucose value ignores its averaging period. Treating it as universally reliable overlooks red-cell and assay-related limitations that can alter results.

The A1C Test & Diabetes

17.What can furosemide reveal during chart review?

Furosemide is a loop diuretic that promotes renal excretion of salt and water. It is used for edema associated with several conditions, including heart, liver, and kidney disease, and can also be used for hypertension. Its presence can prompt review of the indication, volume assessment, and treatment plan. Because several diseases share this medication, the prescription cannot independently establish heart failure, identify its subtype, or prove that an acute exacerbation is occurring.

Apply it

A medication list contains furosemide, but the current note gives no indication. Review prior assessments and the present treatment plan. A supported clarification may be useful, but adding heart failure solely from the prescription would be unjustified.

Common pitfall: Matching a drug to its most familiar indication overlooks alternative uses. Medication exposure is a clinical clue, not a substitute for a documented diagnosis or disease acuity.

Furosemide: MedlinePlus Drug Information

18.Which findings distinguish heart-failure ejection-fraction categories during clinical review?

For patients with symptomatic heart failure, the ACC/AHA/HFSA guideline describes four ejection-fraction categories. Heart failure with reduced ejection fraction (HFrEF) has left ventricular ejection fraction (LVEF) at or below 40%. Heart failure with improved ejection fraction (HFimpEF) requires previous LVEF at or below 40% and follow-up LVEF above 40%. Heart failure with mildly reduced ejection fraction (HFmrEF) has LVEF 41–49% with evidence of increased left ventricular filling pressures. Heart failure with preserved ejection fraction (HFpEF) has LVEF at least 50% with evidence of increased filling pressures. Ejection fraction describes the proportion of left ventricular blood expelled with contraction. Review previous measurements before interpreting the current value; reduced EF without symptoms can represent pre-heart failure rather than symptomatic disease.

Apply it

Documented symptomatic heart failure with LVEF 35% supports review of the reduced-EF category. LVEF 45% with increased filling pressures and no previously reduced EF supports review of the mildly reduced category. A patient with symptomatic heart failure, LVEF 60%, increased filling pressures, and no prior reduced EF has findings consistent with preserved-EF disease. Contrast a patient whose documented HFrEF had LVEF 30% and whose follow-up LVEF is 55%: that trajectory meets the EF criteria for HFimpEF. If the current assessment says only 'heart failure,' present the dated measurements and seek provider clarification rather than automatically reclassifying the condition as HFpEF from the latest value.

Common pitfall: A current EF above 40% does not erase a previous reduced-EF trajectory, and improved EF does not by itself establish disease resolution. Clinical categories guide review but do not authorize independent diagnosis or code assignment for subtype or acuity. New edema, increased diuretic dosing, or an EF threshold alone does not establish acute systolic or diastolic heart failure. Ask the provider to reconcile longitudinal findings, current symptoms, and treatment without predetermining the diagnosis.

Guidelines for Achieving a Compliant Query Practice, August 2026 · Furosemide: MedlinePlus Drug Information · ACC, AHA, HFSA Issue Heart Failure Guideline - American College of Cardiology

19.How is the diabetes–CKD relationship evaluated?

The ICD-10-CM convention for conditions linked by with can establish a presumed causal relationship when the classification specifically connects them, unless documentation clearly states they are unrelated or another guideline requires explicit linkage. Diabetes and CKD are an important application. The convention does not permit deriving either diagnosis from laboratory results alone. Review provider-established diabetes and CKD, any statement that they are unrelated, and the additional stage coding needed to represent the documented renal disease.

Apply it

The provider documents type 2 diabetes and CKD stage 3b, with both addressed and no statement that they are unrelated. Apply the classification’s diabetes-with-CKD convention and capture the documented stage rather than demanding unnecessary causal wording.

Common pitfall: Requiring explicit linkage in every situation ignores classification conventions. Extending a presumed relationship to conditions the classification does not link creates a different and unsupported inference.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

20.When does malignancy remain active rather than historical?

Cancer status depends on whether malignancy remains present and whether treatment is still directed to the involved site. After excision or eradication, no evidence of remaining malignancy, and no further treatment directed to that site, a personal history code is generally appropriate. Continued treatment can support active malignancy reporting even after removal of the original lesion. Review the oncology assessment and treatment purpose; surveillance alone does not establish persistent cancer, and metastatic disease must be considered separately.

Apply it

A patient has completed all treatment for an eradicated primary tumor and now attends surveillance, with no remaining disease documented. Review history reporting. Another patient receiving ongoing treatment directed to the malignancy requires a different active-disease assessment.

Common pitfall: Assuming surgery always ends active cancer coding overlooks continuing treatment or residual disease. Assuming surveillance always means active cancer mistakes follow-up purpose for current malignant disease.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

21.How does treatment phase determine injury encounter character?

For injury codes requiring encounter characters, initial encounter refers to active treatment rather than necessarily the first visit to a particular clinician. Subsequent encounter generally describes routine care during healing or recovery after active treatment is complete. Sequela addresses a residual effect after the acute injury phase has ended. Review what care is occurring now, including whether active treatment continues, rather than assigning the character from appointment order or how long the patient has belonged to the practice.

Apply it

A new clinician sees a patient for routine healing follow-up after active fracture treatment elsewhere. Being new to that clinician does not make the visit an initial encounter; the current treatment phase supports subsequent-encounter review.

Common pitfall: Using first visit as shorthand for initial encounter confuses chronology with treatment phase. A late visit can involve active treatment, while an early follow-up can involve routine recovery.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

22.How are adverse effects distinguished from poisoning?

An adverse effect occurs when a drug is correctly prescribed and properly administered but produces an unwanted reaction. Poisoning involves circumstances such as overdose, an incorrect substance, or an administration error. The distinction changes sequencing: the nature of the adverse effect is coded before the drug adverse-effect code, whereas poisoning generally places the poisoning code before its manifestations. Review the dose, route, administration circumstances, and provider’s diagnostic statement rather than classifying every harmful medication event alike.

Apply it

A patient develops a documented drug-related reaction while taking the correct prescribed dose. Review adverse-effect coding and sequence the reaction first. If the patient instead took an accidental excess dose, the poisoning framework would apply.

Common pitfall: The seriousness of the reaction does not distinguish poisoning from an adverse effect. Correct use versus incorrect use is the central discriminating circumstance for this coding decision.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

23.How does prospective review support the next encounter?

Prospective review examines existing information before an encounter to identify issues the treating provider may need to assess. Prior diagnoses, medications, abnormal results, and unresolved discrepancies can focus attention, but they do not preauthorize current diagnosis reporting. The reviewer should distinguish a previously established condition from a suspected new condition and from a condition that may have resolved. The encounter must supply the provider’s current assessment and the support required for any eventual coding or risk-adjustment submission.

Apply it

Before an annual visit, a reviewer notices CKD documented last year but absent from recent assessments. Flag the history and relevant results for current evaluation. Do not prepopulate a confirmed current diagnosis merely to preserve last year’s HCC.

Common pitfall: A previsit opportunity list can become misleading if it appears to be a completed diagnostic assessment. Historical evidence should guide evaluation rather than predetermine the provider’s conclusion.

About the CCDS-O Certification · Guidelines for Achieving a Compliant Query Practice, August 2026

24.What makes retrospective review clinically useful?

Retrospective review examines a completed encounter for accurate translation of documented care into coded information. It can identify omitted supported diagnoses, conflicting statements, unclear specificity, or diagnoses requiring clinical validation. The reviewer must preserve what was actually known and addressed during that encounter rather than importing later findings as though they were contemporaneous. A retrospective clarification remains subject to the same neutrality, clinical support, and provider judgment principles as a query issued during care.

Apply it

A completed visit documents assessment and continued treatment of a chronic disease, but the diagnosis was omitted from coding. Reconcile the omission. If the diagnosis itself is unclear, seek clarification rather than rewriting the encounter from later records.

Common pitfall: Retrospective review is not permission to add every later-discovered disease to an earlier visit. Supported correction and reconstruction of undocumented care are fundamentally different activities.

About the CCDS-O Certification · Guidelines for Achieving a Compliant Query Practice, August 2026

III. Risk adjustment and documentationnot stated

25.How does a prospective risk-adjustment model use diagnoses?

A prospective model uses information from an earlier data period to estimate expected costs in a later payment period. In CMS-HCC risk adjustment, eligible diagnosis information contributes alongside demographic and other applicable model factors. The score estimates relative expected resource use for a population-based payment methodology; it is not a bill for individual treatments. Foundational CMS explanations describe this timing principle, but current implementation details require the applicable payment-year model resources rather than historical coefficients.

Apply it

A team asks why diagnoses documented during one year can affect a later payment period. Explain the prospective relationship and identify the applicable data and payment periods before comparing results or estimating financial effects.

Common pitfall: Assuming each diagnosis immediately generates a fixed payment confuses prospective risk estimation with fee-for-service billing. Historical model explanations also do not supply current payment-year coefficients.

Medicare Managed Care Manual, Chapter 7: Risk Adjustment · 2026 Model Software/ICD-10 Mappings

26.Why does capitation make accurate risk adjustment important?

Capitated payment supplies a payment for covered care over a defined period rather than paying separately for every service. Risk adjustment helps account for differences in expected resource needs across enrolled populations. Accurate documentation supports a more faithful representation of illness burden, but the objective remains correct reporting rather than maximizing diagnoses. A risk-adjusted payment reflects a model and payment framework; it should not be described as a direct reimbursement amount attached to each newly documented chronic condition.

Apply it

Two plans care for populations with different documented disease burdens. Risk adjustment helps account for expected cost differences. A CDI team should improve record accuracy without promising a fixed payment increase for each individual diagnosis clarified.

Common pitfall: Treating risk adjustment as a bounty for diagnoses encourages unsupported capture. Capitation and fee-for-service reimbursement answer different payment questions and should not be combined indiscriminately.

Medicare Managed Care Manual, Chapter 7: Risk Adjustment · The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

27.Which nondiagnosis factors can change a risk score?

CMS-HCC scoring includes demographic and eligibility-related information in addition to diagnoses. Applicable factors and model segments can reflect characteristics such as age, sex, disability, Medicaid status, and community or institutional status. Their precise treatment depends on the model and payment year. Therefore, identical diagnosis lists do not guarantee identical risk scores. Before attributing a score difference to documentation, establish whether the beneficiaries were scored using comparable segments, demographic inputs, eligibility information, and model versions.

Apply it

Two beneficiaries have the same supported disease categories but different risk scores. Before looking for a missing diagnosis, compare the demographic and eligibility inputs and the model segment used for each beneficiary’s calculation.

Common pitfall: Assuming diagnoses explain every score difference overlooks model structure. CDI staff also should not alter demographic or eligibility facts merely to align a score with expectations.

Medicare Managed Care Manual, Chapter 7: Risk Adjustment · 2026 Model Software/ICD-10 Mappings

28.How does a disease hierarchy prevent related-category double counting?

A hierarchy retains the model-defined higher-ranking category when related categories coexist, preventing their separate contributions from being added indiscriminately. For this hypothetical teaching model, assume N18.4 maps to category K4, N18.32 maps to K3b, and a stage 3a diagnosis maps to K3a. Assume K4 suppresses K3b and K3a, while category K5 suppresses all three. These identifiers and mapping rules are supplied exercise assumptions, not official CMS-HCC entries. Actual suppression must be established from the matching model software and hierarchy specifications.

Apply it

A beneficiary has supported stage 3b CKD at a March encounter and supported stage 4 CKD at a November encounter within the exercise's eligible data period. N18.32 triggers hypothetical K3b and N18.4 triggers hypothetical K4. Retain K4 after applying the supplied hierarchy. Preserve each encounter's accurate diagnosis; data-period hierarchy processing does not rewrite the earlier clinical assessment.

Common pitfall: Adding K4 and K3b violates the exercise's hierarchy. Suppression also does not authorize reporting conflicting stages at one encounter without clarification or suppressing unrelated categories. A clinical severity sequence alone does not establish the exact suppression rules of a particular CMS release.

Evaluation of the CMS-HCC Risk Adjustment Model, Final Report, March 2011 · 2026 Model Software/ICD-10 Mappings · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

29.When does a disease interaction contribute to risk scoring?

An interaction term represents a model-defined combination whose expected cost effect is not fully represented by simply adding the individual condition factors. It contributes only when the applicable model’s criteria are met. Clinical coexistence alone does not create an interaction, and a familiar interaction from an older model may not apply unchanged to a newer one. Identify retained categories and the relevant segment before applying the current interaction logic and its associated coefficient.

Apply it

A teaching model explicitly assigns an interaction of 0.12 when retained categories A and B coexist. Both remain after hierarchy processing, so add the interaction once. Without that stated model rule, coexistence alone would not justify it.

Common pitfall: Inventing interactions from clinical intuition can inflate scores. Reusing an interaction across years or segments without checking current specifications can also produce a technically incorrect calculation.

Medicare Managed Care Manual, Chapter 7: Risk Adjustment · 2026 Model Software/ICD-10 Mappings

30.How is a simplified additive RAF calculated?

For a simplified teaching calculation, add the supplied demographic factor, retained disease coefficients, and any explicitly applicable interactions after applying hierarchy rules. State that all values are hypothetical and that normalization, coding-pattern adjustments, blending, or other payment calculations are excluded unless supplied. This sequence separates category selection from arithmetic. The resulting classroom score illustrates model logic; it is not an actual payment estimate or a substitute for the official software and specifications for the relevant year.

Apply it

Assume a demographic factor of 0.40, retained disease factors of 0.25 and 0.30, and an applicable interaction of 0.10. With no other adjustments, the teaching score is 0.40 + 0.25 + 0.30 + 0.10 = 1.05.

Common pitfall: Performing accurate addition on the wrong retained categories still gives the wrong score. A simplified RAF also cannot be converted into dollars without the applicable payment framework.

Medicare Managed Care Manual, Chapter 7: Risk Adjustment · 2026 Model Software/ICD-10 Mappings

31.Why does HCC count differ from risk-score magnitude?

A risk score depends on the weights and structure of the applicable model, not simply the number of diagnoses or mapped categories. Different categories can carry different coefficients, related categories may be suppressed, and demographic or interaction factors may contribute. Consequently, a beneficiary with fewer retained HCCs can have a higher score than another beneficiary with more HCCs. Interpret category counts as one descriptive measure rather than as an interchangeable substitute for calculated risk.

Apply it

In a hypothetical model, one patient has two retained categories totaling 0.90, while another has three totaling 0.60. With identical other factors, the patient with fewer categories has the higher score because the coefficients differ.

Common pitfall: Using category count as a score proxy hides differences in weights and hierarchies. Counting raw diagnoses adds another distortion because several diagnoses may map to one category.

Evaluation of the CMS-HCC Risk Adjustment Model, Final Report, March 2011 · 2026 Model Software/ICD-10 Mappings

32.How should a documented diagnosis be traced through a release-specific mapping?

Identify the payment year, model version, release, and applicable service dates before mapping a supported ICD-10-CM code. Use the actual diagnosis-mapping file together with the corresponding hierarchy, software, and segment coefficients. A CMS resource page identifies available releases; code-level conclusions require the relevant entries in those files. In the hypothetical teaching mapping used here, N18.4 maps to K4 and N18.32 maps to K3b. These supplied mappings illustrate the sequence and do not establish payment-year 2026 Version 28 entries. A category mapping also does not establish a universal coefficient or fixed dollar payment.

Apply it

For a provider-established CKD stage 4 diagnosis, confirm that N18.4 represents the assessment and that the encounter meets the applicable submission rules. Under the hypothetical mapping, assign K4, apply the supplied hierarchy, and select the supplied segment coefficient. For an operational calculation, record the exact mapping and hierarchy filenames, their release, applicable service dates, and the matching entries before assigning an official category.

Common pitfall: Version 28 alone does not identify every operational specification. An undated worksheet, a different payment year, or an initial release substituted for a later release can change the applicable analysis. Do not treat hypothetical K4 or K3b as official HCC identifiers.

2026 Model Software/ICD-10 Mappings · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

33.How can a reportable diagnosis differ from a payment-category diagnosis?

Diagnosis reporting and payment-model inclusion are separate decisions. For a hypothetical comparison, assume N18.4 maps to payment category K4 while I10 contributes no payment category. Either diagnosis can still be correctly reportable when documented and relevant to its encounter. These mapping assumptions do not establish exact entries in a CMS payment-year release. More generally, exclusion from a payment category does not mean a disease is unimportant, unreportable, or excluded from all quality measures and other risk models.

Apply it

In separate cases, one provider documents and manages essential hypertension without heart or kidney disease, supporting I10; another documents and manages CKD stage 4, supporting N18.4. Both diagnoses belong in their respective encounter data. Under the supplied hypothetical mapping, only N18.4 triggers a payment category, subject to the exercise's eligibility and hierarchy rules. If hypertension and CKD coexist, also apply the hypertension–CKD coding conventions rather than automatically using I10.

Common pitfall: Omitting a reportable diagnosis solely because it contributes no payment category loses valid clinical information. Assigning N18.4 because a model rewards it remains unsupported unless the provider’s diagnosis and encounter record justify the code. Official payment-category inclusion requires the applicable mapping entry.

2026 Model Software/ICD-10 Mappings · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · Fact Sheet: 2024 Medicare Advantage and Part D Rate Announcement | CMS

34.How should annual diagnosis recapture be approached?

Risk adjustment uses diagnoses from defined data periods, so a diagnosis reported previously does not automatically establish a current-period submission. Recapture means reassessing whether a previously identified condition remains present and appropriately documented within the current period. Persistent disease can warrant ongoing assessment, while resolved disease, unsupported historical entries, and mapping changes require different handling. The goal is an accurate current representation of health status, not mechanical preservation of the previous year’s categories or score.

Apply it

A prior-year HCC appears on a previsit report. The clinician evaluates whether the underlying disease persists and documents current management when appropriate. If the condition has resolved, the team should not restore it solely to avoid a dropped-category metric.

Common pitfall: Annual recapture is not annual copying. A missed current assessment, a resolved condition, and a changed mapping can all produce an apparent drop but require different responses.

Medicare Managed Care Manual, Chapter 7: Risk Adjustment · Medicare Advantage Risk Adjustment Data Validation Program

35.How is risk-adjustment submission eligibility established separately from diagnosis coding?

Use separate checks for diagnosis support, data period, encounter source, service eligibility, professional specialty, and record authentication. Establish provider documentation, clinical support, encounter relevance, and accurate ICD-10-CM coding first. Then match the enrollee and service date to the applicable period, the source and CPT/HCPCS service to the relevant program rules, and the rendering specialty to its applicable list. The CMS file acceptable-physician-specialty-types-py-2026.pdf explicitly covers payment year 2026 with 2025 dates of service and lists nephrology as specialty 39. That entry establishes the specialty check, not eligibility of every nephrology service. Confirm the record identifies the patient, service date, author and credentials, and required authentication before applying the matching mapping and hierarchy.

Apply it

A signed 2025 nephrologist office record documenting current CKD assessment can satisfy the listed specialty and date checks for payment year 2026. If the service is coded 99214, separately establish that code's eligibility from the applicable eligible-service file and encounter rules; its valid E/M description alone does not establish risk-adjustment eligibility. A laboratory or imaging claim can support diagnosis coding in its own context without automatically establishing an acceptable risk-adjustment source. Determine source eligibility independently rather than inferring it from a diagnosis on the claim.

Common pitfall: An NPI, accepted claim, specialty-list entry, diagnosis code, or HCC mapping does not establish all submission requirements. Record the applicable eligible-service filename, program scope, service dates, and relevant entry before making a release-specific eligibility conclusion. CMS labels the payment-year 2026 outpatient excluded-services list PACE-only; do not apply that scope universally to Medicare Advantage.

ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · Medicare Managed Care Manual, Chapter 7: Risk Adjustment · Medicare Risk Adjustment Eligible CPT/HCPCS Codes | CMS · acceptable-physician-specialty-types-py-2026.pdf · Outpatient CPT HCPCS Excluded Services Lists | CMS · Medicare Advantage Risk Adjustment Data Validation Program

36.How do CMS-HCC and HHS-HCC risk-adjustment methodologies differ?

CMS-HCC is the foundational prospective methodology used for Medicare Advantage: base-period diagnoses help predict spending in a subsequent period. HHS-HCC is a concurrent methodology for ACA individual and small-group market risk adjustment: diagnoses help predict spending during the same period. Both group diagnoses into condition categories, but they serve different populations and payment purposes. HHS-HCC was adapted to commercial populations, including children and infants, and predicts plan liability for medical and drug spending; the Medicare CMS-HCC model addresses Medicare medical spending. Their category definitions and coefficients therefore cannot be exchanged.

Apply it

In a simplified timing example, diagnoses documented during 2025 inform a prospective CMS-HCC prediction for 2026. Under a concurrent HHS-HCC example, diagnoses documented during 2026 inform the prediction of 2026 spending. Before comparing scores, identify the program, model version, population, and data period. A condition's category number or coefficient in the commercial model does not establish its Medicare Advantage treatment.

Common pitfall: Concurrent describes the relationship between diagnosis and expenditure periods, not the date an analyst finishes processing data. The 2014 CMS model-design paper establishes these foundational distinctions; its historical category counts and coefficients are not current specifications. This selective comparison supports one competency within the official ACDIS outline, which defines the full examination scope.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Medicare Managed Care Manual, Chapter 7: Risk Adjustment · mmrr2014_004_03_a03.pdf

IV. CDI metrics and provider educationnot stated

37.How should outpatient CDI productivity be measured?

Productivity measures work performed over a defined resource or time denominator, such as completed chart reviews per productive hour. Specify what counts as a review, whether repeat reviews are included, and which hours enter the denominator. Volume alone does not measure clinical accuracy or improvement. Compare similar review types and complexity, and interpret productivity alongside quality findings. The official outline identifies chart-review productivity as a CDI metric but does not prescribe one universal departmental formula.

Apply it

A reviewer completes 48 qualifying reviews during eight productive hours. Under the department’s stated definition, productivity is six reviews per productive hour. Compare that figure with similar review assignments rather than with a team handling a different case mix.

Common pitfall: Using paid hours for one reviewer and productive hours for another makes the comparison misleading. Faster review volume also does not prove better documentation or safer coding.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

38.What does a query rate actually measure?

A query rate describes query activity relative to a defined reviewed population. One department may count encounters receiving at least one query divided by reviewed encounters; another may count total queries divided by reviews. Those measures differ when an encounter receives multiple queries. State the numerator and denominator before calculating or comparing rates. A higher rate may reflect more documentation gaps, different review targeting, or different query thresholds rather than superior CDI performance.

Apply it

Among 100 reviewed encounters, 25 receive queries, with 30 total queries issued. The encounter query rate is 25%, while queries per review is 0.30. Label the measures distinctly instead of presenting them as the same statistic.

Common pitfall: Treating query volume as an achievement target can reward unnecessary queries. An apparent change may also result from switching between encounter counts and individual query counts.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

39.How is provider query response rate calculated?

Response rate measures answered queries divided by eligible issued queries under a stated definition and observation window. Define how pending, withdrawn, duplicate, and invalid queries are handled before interpreting the result. A response acknowledges or resolves the query; it does not necessarily agree with a proposed diagnosis or produce a coding change. Cohort consistency matters because comparing newly issued queries with mature queries gives providers unequal opportunities to respond and can create a misleading trend.

Apply it

A closed cohort contains 80 eligible queries, of which 60 receive responses by the defined deadline. The response rate is 75%. A response declining the suggested interpretation still counts as answered under this definition.

Common pitfall: Counting only favorable answers as responses confuses engagement with agreement. Comparing different follow-up windows can also make a stable response process appear to deteriorate or improve.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

40.How does agreement rate differ from response rate?

Agreement rate evaluates a defined type of agreement within a specified denominator, commonly answered queries. Response rate instead asks whether queries were answered. Because departmental definitions vary, identify whether agreement means accepting a proposed clarification, supplying a supported diagnosis, or another explicitly defined result. A disagreement can be clinically correct and educationally valuable. Neither high agreement nor high response establishes that the queries were necessary, nonleading, clinically supported, or translated accurately into final coding.

Apply it

Of 100 issued queries, 80 are answered and 60 meet the department’s agreement definition. Response is 80%; agreement among answered queries is 75%. Agreement among all issued queries would instead be 60% and needs a different label.

Common pitfall: Comparing agreement percentages without their denominators can reverse conclusions. Pressuring clinicians toward agreement also undermines the independent judgment a compliant clarification process must preserve.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Guidelines for Achieving a Compliant Query Practice, August 2026

41.How can diagnosis capture after CDI intervention be measured?

A capture measure tracks whether a defined, supported documentation opportunity becomes an accurately coded diagnosis after intervention. Specify whether the unit is a diagnosis, encounter, or patient, and distinguish provider clarification from final coded capture. A favorable response does not guarantee the final claim contains the correct code. Attribute improvement cautiously because coding reconciliation, provider education, and unrelated workflow changes can affect results. The metric should reward accurate representation, including appropriate removal of unsupported diagnoses.

Apply it

A project identifies 40 supported opportunities under its audit definition. Thirty result in accurate final coded diagnoses after review, giving 75% capture for that opportunity cohort. Reconcile the remaining cases rather than assuming every answered query reached coding.

Common pitfall: Counting query agreements as completed capture skips the final coding step. Counting unsupported additions as successes can improve a dashboard while worsening documentation integrity and audit exposure.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Medicare Advantage Risk Adjustment Data Validation Program

42.How should a recapture-rate denominator be defined?

A recapture rate compares current-period capture with a defined cohort of prior-period conditions or categories eligible for reassessment. Decide whether the metric follows patients, diagnoses, or HCCs, and account for enrollment, mapping, and clinical-status changes. The prior-year total is not automatically a fair denominator if people left the population or conditions resolved. Report exclusions transparently so improvement represents better current assessment rather than selective removal of difficult cases or mechanical restoration of old diagnoses.

Apply it

A prior-year cohort contains 120 categories, but 20 fall outside the project’s predefined eligible population. Seventy of the remaining 100 are appropriately captured this year. The defined eligible-cohort recapture rate is 70%, with exclusions separately disclosed.

Common pitfall: Changing eligibility rules after seeing results can inflate recapture. Treating resolved diseases as failures also turns a clinical accuracy measure into pressure to preserve outdated diagnoses.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Medicare Advantage Risk Adjustment Data Validation Program

43.What can a dropped HCC indicate?

A dropped HCC is a category present in a defined prior period but absent from the current comparison. It can reflect a missed assessment, disease resolution, changed enrollment, hierarchy suppression, coding correction, or a different mapping version. Therefore, the label identifies a review question rather than proving underdocumentation. Compare the underlying diagnoses and model rules before acting. A clinically appropriate drop can be evidence of more accurate reporting rather than a departmental performance failure.

Apply it

A dashboard flags a missing category after a model update. The underlying disease remains documented, but its mapping changed. Classify the change as a model-related difference rather than asking the clinician to add another diagnosis to restore the former category.

Common pitfall: Equating every drop with lost revenue obscures legitimate clinical and technical explanations. An HCC comparison should not drive unsupported diagnoses or replacement categories chosen solely for score preservation.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · 2026 Model Software/ICD-10 Mappings

44.How should newly added diagnoses be interpreted?

A newly added diagnosis in coded data may represent incident disease, previously unrecognized disease, improved documentation of longstanding disease, or a coding correction. These mechanisms have different implications for population health and program evaluation. Review baseline records and the encounter establishing the condition before calling it new disease or attributing it entirely to CDI. Distinguish new clinical onset from new coded capture, and verify that the addition is supported rather than measuring success solely by increased category counts.

Apply it

After education, a clinic begins accurately coding a longstanding condition that was previously documented but omitted. Classify the result as improved coded capture, not a sudden rise in disease incidence or proof that patients became sicker.

Common pitfall: Treating new-to-data as new-to-patient can distort clinical trends. Attributing every addition to CDI also overlooks diagnostic work, coding changes, and differences in the reviewed population.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Medicare Advantage Risk Adjustment Data Validation Program

45.How should RAF trends be compared over time?

RAF trends require comparable populations, data maturity, model versions, and scoring assumptions. An increase can arise from changing demographics, enrollment, disease burden, documentation completeness, or model structure. Compare like periods and, when appropriate, recalculate a fixed cohort under one model to separate documentation effects from technical changes. Report both absolute and relative change accurately. A rising score is not inherently proof of better care, greater disease severity, or a successful CDI intervention.

Apply it

A mean RAF rises from 1.00 to 1.10 while both enrollment and model version change. The absolute increase is 0.10 and relative increase is 10%, but attribution requires a comparable-cohort analysis before crediting documentation improvement.

Common pitfall: Comparing an incomplete current year with a fully mature prior year biases the trend. A model change can also alter scores without any change in patient health.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · 2026 Model Software/ICD-10 Mappings

46.What does an unspecified-code trend reveal?

An unspecified-code rate can identify areas for documentation or coding review, but the metric requires a defined code set and denominator. Some unspecified codes accurately reflect the information established at the encounter. Examine whether missing detail was clinically knowable, provider documented but uncoded, or genuinely unresolved. A targeted audit can distinguish documentation gaps from coding errors. Reducing the percentage without checking support may create false precision and should not be treated as an independent measure of quality.

Apply it

A clinic’s unspecified laterality rate increases. Audit sampled records: some contain documented sides omitted during coding, while others never establish laterality. Address the coding workflow for the first group and appropriate documentation opportunities for the second.

Common pitfall: A blanket demand for zero unspecified codes encourages guessing or unnecessary queries. A falling rate can therefore reflect unsupported specificity rather than a genuine improvement in documentation.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

47.How should medical-necessity denial rates guide improvement?

A denial rate relates a defined set of denied claims or services to an eligible submitted population. Distinguish initial denials from final upheld denials and count claims, lines, or dollars consistently. Medical-necessity denials can reflect documentation gaps, coding mismatches, coverage requirements, or service-selection issues. Review actual denial reasons and supporting records before choosing an intervention. Adding a more severe diagnosis is not a legitimate general remedy when the encounter does not support it.

Apply it

Twenty of 400 eligible claims receive initial medical-necessity denials, a 5% initial denial rate. Review the denial categories and subsequent appeal outcomes before concluding that all 20 represent provider documentation failures or permanent lost reimbursement.

Common pitfall: Combining initial and final denials obscures resolution. Responding with diagnosis inflation can create compliance risk while failing to address the actual service, coverage, or documentation problem.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · MLN6922507: Medicare Payment Systems

48.How can provider education target a demonstrated gap?

Effective education connects a verified pattern to a specific documentation behavior the audience can change. Use representative cases, explain the clinical and coding distinction, and show how accurate documentation improves communication as well as data quality. Adapt the message to the specialty and workflow. Measure follow-up performance using the same definitions and comparable samples. Query agreement or a higher RAF alone does not demonstrate learning; audit whether the targeted documentation becomes more accurate and clinically supported.

Apply it

An audit finds that clinicians document CKD but omit established stage information. Offer a brief case-based session on supported staging documentation, then re-audit comparable encounters for stage completeness and accuracy rather than tracking attendance alone.

Common pitfall: Generic presentations may miss the actual cause of errors. Education framed around securing higher scores can also encourage severity inflation instead of clinically precise, defensible documentation.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Guidelines for Achieving a Compliant Query Practice, August 2026

V. Quality, regulation, and compliancenot stated

49.What makes a documentation query nonleading?

A nonleading query presents relevant clinical indicators and the documentation issue without directing the provider toward a predetermined answer. It preserves independent clinical judgment and does not use reimbursement, quality rankings, or an expected score as reasons to choose a diagnosis. The opportunity may involve missing specificity, conflicting information, or clinical validation. Neutrality applies to the wording, selected indicators, and available responses; a polite tone alone cannot make a selectively framed or clinically unsupported question compliant.

Apply it

A record contains conflicting renal assessments. Present the dated statements and relevant findings, then ask the provider to clarify the current condition. Do not state that the organization needs the more severe diagnosis to protect its risk score.

Common pitfall: A query can lead through omission as well as wording. Listing only evidence favoring one diagnosis can bias the request even when the question sounds courteous.

Guidelines for Achieving a Compliant Query Practice, August 2026

50.How should open-ended and multiple-choice query formats be chosen?

An open-ended query lets the provider state the clarification in their own words. A multiple-choice query offers clinically reasonable responses grounded in the record and must permit an alternative explanation through an 'Other (please specify)' option or an equivalent free-text response. 'Unable to determine' may be included when appropriate, but it does not replace the opportunity to supply another explanation. These responses serve different purposes: one identifies an unlisted explanation; the other expresses diagnostic uncertainty. Either format must use relevant clinical indicators, neutral wording, and response design that preserves independent clinical judgment.

Apply it

When the cause of documented edema is unclear, an open-ended request might ask, 'Please clarify the cause of the documented edema, if known.' If using multiple choice, offer only clinically reasonable causes supported by the record and include 'Other explanation (please specify).' Include 'Unable to determine' when appropriate as a separate response. A provider who identifies an unlisted cause must have a way to document that cause rather than being directed to select uncertainty.

Common pitfall: Including 'Unable to determine' alone leaves no opportunity to supply an alternative explanation. Adding 'Other' also does not correct unsupported diagnostic choices or leading wording. Compliance depends on the entire query, including its clinical context and response options.

Guidelines for Achieving a Compliant Query Practice, August 2026

51.When is a yes/no query appropriate?

Yes/no queries have limited appropriate applications under compliant-query guidance, including certain clarification or clinical-validation situations involving diagnoses already documented. They should not be used simply to introduce a new diagnosis from suggestive indicators by asking the provider to confirm it. Determine whether the question clarifies existing documentation or creates a new diagnostic assertion. The supporting indicators and alternatives must preserve the provider’s ability to disagree, explain another conclusion, or state that the issue cannot be determined.

Apply it

The record already contains a diagnosis that conflicts with other documentation. A properly supported validation query may ask whether it remains clinically valid. Asking whether undocumented heart failure exists solely because furosemide appears would require a different, neutral approach.

Common pitfall: A yes/no structure can make a new diagnosis appear like simple confirmation. The distinction turns on what is already documented and the permitted purpose of the query.

Guidelines for Achieving a Compliant Query Practice, August 2026

52.How should verbal clarification preserve documentation integrity?

Verbal clarification is subject to the same clinical support and nonleading principles as written queries. A discussion can be useful when the issue is complex or a written request was misunderstood, but the relevant question and resulting clarification must be documented according to a consistent process. The provider’s authenticated documentation should support the diagnosis used for coding. An informal conversation or the reviewer’s recollection should not become the sole basis for an otherwise undocumented coded condition.

Apply it

A provider telephones to discuss a confusing query and explains the intended diagnosis. Follow the organization’s query-documentation process and ensure the provider’s clarification is properly recorded before final coding instead of relying on the reviewer’s memory.

Common pitfall: Treating conversation as exempt from query standards creates an undocumented route to diagnostic changes. Verbal convenience does not remove the need for neutrality, traceability, and supported provider documentation.

Guidelines for Achieving a Compliant Query Practice, August 2026

53.How does clinical validation differ from coding specificity?

Clinical validation asks whether a documented diagnosis is supported by the patient's clinical circumstances. Specificity clarification requests additional detail about an established diagnosis. A clinical-validation query should present relevant supporting and conflicting findings and seek clarification of the diagnosis's clinical basis. If the provider retains the questioned diagnosis, request documentation of the supporting clinical data or clinical reasoning; simple confirmation does not adequately address the support concern. The 2026 guidance recommends multiple choice as the optimal clinical-validation format, without making it the only permissible format. The objective is an accurate, clinically supported record, whether the diagnosis is retained, revised, or ruled out.

Apply it

A provider documents an acute condition, but the examination and test findings summarized in the record do not explain its clinical basis. Present those actual findings and ask, 'Please clarify the status of the documented diagnosis. If the diagnosis remains supported, please document the supporting clinical findings or clinical reasoning.' A multiple-choice version can offer retention with supporting explanation, diagnosis ruled out, and other clinically appropriate responses, while permitting 'Other explanation (please specify)' and including 'Unable to determine' when appropriate. By comparison, requesting the missing subtype of an otherwise established condition addresses specificity.

Common pitfall: A response that merely repeats the diagnosis can leave the original clinical-support concern unresolved. Ask for its supporting findings or reasoning when retained. Choosing a less specific code does not establish clinical validity, and the reviewer should not independently remove a diagnosis solely because they disagree with it.

Guidelines for Achieving a Compliant Query Practice, August 2026 · Guidelines for Achieving a Compliant Query Practice: What's New in the 2026 Update

54.Why does problem-list maintenance matter for compliance?

Problem lists support longitudinal care but can accumulate resolved, duplicated, uncertain, or incorrectly imported conditions. Their presence should prompt reconciliation rather than automatic claim submission. Review whether each condition remains current, whether its status is clear, and whether encounter documentation supports reporting. Accurate maintenance improves communication and reduces repeated propagation of unsupported diagnoses. A historical problem-list entry can be useful context for assessment, but it should not override a current provider statement that the condition has resolved or was entered incorrectly.

Apply it

A copied problem list labels a condition active, while the current assessment states it was ruled out previously. Reconcile the discrepancy through the appropriate documentation process rather than repeatedly submitting the active disease because the older list persists.

Common pitfall: Treating the problem list as an immutable diagnosis source allows old errors to recur. Removing entries without preserving clinically relevant history can create a different communication problem.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027

55.What does Medicare Advantage RADV verify?

Medicare Advantage Risk Adjustment Data Validation evaluates whether diagnoses submitted for risk-adjusted payment are supported by the medical record. Its purpose concerns payment accuracy and identification of unsupported diagnosis data, rather than rewarding the number of diagnoses captured. A compliant review process should retain traceable links between submitted codes and supporting encounters and address identified errors. A plausible disease, a valid ICD-10-CM code, or a favorable model mapping cannot independently substitute for the required medical-record support.

Apply it

An audit sample includes a submitted diagnosis that appears in a vendor file but not in the supporting encounter record. Investigate the discrepancy and follow correction procedures. The vendor’s assertion does not establish that the medical record supports submission.

Common pitfall: Preparing for RADV only after an audit overlooks preventable source-data errors. More submitted diagnoses can increase unsupported reporting when the documentation and coding foundations are weak.

Medicare Advantage Risk Adjustment Data Validation Program

56.How do ACOs connect coordinated care with shared savings?

Accountable Care Organizations bring providers together to coordinate care for a defined population. Under the Medicare Shared Savings Program, eligible organizations can share savings when they satisfy applicable program requirements, including quality performance and financial criteria. Spending below a benchmark alone does not establish the final payment. CDI supports accurate population information and communication, but it cannot replace care coordination or quality performance. Any teaching calculation must explicitly state the benchmark, expenditures, sharing assumptions, and satisfied eligibility conditions.

Apply it

An ACO’s spending is below its benchmark, but the team has not checked quality requirements or the applicable sharing rules. Calculate preliminary gross savings separately from any earned shared-savings payment and verify the remaining conditions.

Common pitfall: Calling all underspending distributable savings skips program requirements. Raising coded risk also does not by itself demonstrate improved coordination, better outcomes, or entitlement to shared-savings payments.

Shared Savings Program

57.How do MACRA, MIPS, and Advanced APM participation relate to documentation and quality reporting?

The Medicare Access and CHIP Reauthorization Act of 2015 (MACRA) ended the Sustainable Growth Rate formula and established the Quality Payment Program. Its two participation pathways are the Merit-based Incentive Payment System (MIPS) and Advanced Alternative Payment Models (Advanced APMs). Eligible clinicians in MIPS receive performance-based Medicare payment adjustments. The Advanced APM pathway depends on participation in a qualifying payment model and sufficient participation to meet applicable requirements. Merely joining an alternative payment arrangement does not establish qualifying participation. Documentation supplies information used in reporting and evaluation, but its effect depends on the pathway and specific measure.

Apply it

A physician group joins an ACO and assumes all clinicians have left MIPS. First determine whether the particular ACO arrangement qualifies as an Advanced APM and whether the clinicians meet the applicable qualifying-participation requirements. If they remain subject to MIPS, evaluate documentation against their MIPS reporting obligations. If they qualify through the Advanced APM pathway, evaluate the model's quality and payment requirements. ACO membership alone does not resolve this decision.

Common pitfall: A higher Medicare Advantage payment RAF does not automatically improve a MIPS score or an APM quality result. Determine whether a documentation change affects the actual measure's population, exclusions, coded variables, or risk adjustment before attributing a performance change to improved clinical outcomes.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Shared Savings Program · Quality Payment Program | CMS

58.How do MAC and CERT functions distinguish documentation-review priorities?

Medicare Administrative Contractors (MACs) process Medicare fee-for-service claims and publish local coverage materials, including Local Coverage Determinations and related billing guidance. The Comprehensive Error Rate Testing (CERT) program reviews a statistical sample of Medicare fee-for-service claims to estimate improper payments under coverage, coding, and billing requirements. CERT findings distinguish insufficient documentation, no documentation, medical necessity, incorrect coding, and other errors. CERT measures payment compliance; an improper payment does not by itself establish fraud. CERT communicates identified payment errors to MACs, which handle resulting repayment or recoupment actions.

Apply it

A clinic reviewing a MAC coverage-related denial should compare the documented indication with the applicable coverage requirements. In contrast, a CERT-sampled laboratory claim containing a complete blood count result but lacking the order or documented intent to order illustrates insufficient documentation: the submitted record cannot establish all payment requirements. The corrective action is to address the missing ordering support and submission process, rather than assume that the test result proves coverage or that the service was never performed.

Common pitfall: Missing evidence and affirmative evidence of noncoverage require different analysis. An absent required order supports an insufficient-documentation finding; documentation showing that a service failed applicable medical-necessity criteria supports a different error category. Identify the specific finding before choosing education, coding correction, or documentation follow-up.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O · Medicare Administrative Contractors | CMS · introduction-comprehensive-error-rate-testing-cert-program.pdf-0

59.How should confidentiality shape CDI education and reporting?

CDI work involves sensitive clinical information, so record access, case discussion, and performance reporting must preserve confidentiality. The official outline explicitly includes confidentiality and core HIPAA principles. For practical education, use appropriately de-identified examples when identifiable details are unnecessary, distribute material through authorized channels, and limit access according to organizational policy and job responsibilities. Provider performance information also deserves controlled handling. An educational purpose does not make unrestricted distribution of patient-level records appropriate.

Apply it

A presenter wants to show a documentation error during a large educational meeting. Replace unnecessary identifying details with a de-identified case and use the organization’s approved sharing process rather than circulating a full chart screenshot.

Common pitfall: Removing only the patient’s name may leave identifying details visible elsewhere in a record. Convenience or an educational label does not eliminate confidentiality responsibilities or access controls.

The Clinical Documentation Integrity Specialist’s Certification Exam Candidate Handbook: CCDS and CCDS-O

60.How should technology-assisted queries preserve independent judgment?

Technology can help identify documentation discrepancies or draft a query, but it does not change the requirement for clinical support, neutral wording, and independent provider judgment. Review the actual encounter evidence before sending an automated suggestion. Check for copied errors, omitted contradictory findings, and unsupported answer options. The August 2026 query guidance addresses technology within the same compliance framework: automation assists the process but does not make an otherwise leading or clinically unsupported query acceptable.

Apply it

A system suggests a severe diagnosis from an isolated result while omitting a conflicting assessment. The reviewer checks the complete record, revises or rejects the suggestion, and sends a query only if a supported neutral clarification opportunity remains.

Common pitfall: Assuming a system-generated recommendation has already been clinically validated transfers responsibility to an unverified suggestion. Standardized wording cannot compensate for incorrect indicators or a biased diagnostic premise.

Guidelines for Achieving a Compliant Query Practice, August 2026 · Guidelines for Achieving a Compliant Query Practice: What's New in the 2026 Update

What to focus on during revision

The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.

  • Separate encounter-level diagnosis reporting from HCC mapping and payment effects.
  • Practise outpatient certainty rules across physician visits, emergency care, and observation.
  • Use laboratory results, medications, and longitudinal findings as clarification evidence without independently creating diagnoses.
  • Apply the explicitly hypothetical N18.4-to-K4 and N18.32-to-K3b mappings, their supplied hierarchy, and the assumed absence of an I10 payment contribution.
  • Distinguish diagnosis support, data-period eligibility, eligible services, acceptable sources and specialties, and record authentication.
  • Calculate departmental metrics only after defining the cohort, unit, denominator, and observation window.
  • Distinguish specificity queries, clinical validation, problem-list reconciliation, and unsupported diagnosis removal.
  • Interpret ACO, quality, and risk-score results without equating documentation changes with improved clinical outcomes.

A practical preparation plan

1. Map your experience to the full outline

Read the five CCDS-O areas on handbook pages 14–17. Mark unfamiliar settings and disease families, including areas beyond this selective guide, and distinguish them from the inpatient CCDS outline.

2. Build an encounter decision sequence

For each case, identify patient status, reason for services, established diagnoses, reporting criteria, source-documentation rules, and supported specificity before considering reimbursement or risk adjustment.

3. Rehearse clinical clarification

Use contrasting CKD, diabetes, heart-failure trajectories, cancer, injury, and medication cases. State which findings support review, what remains uncertain, and how a neutral query would preserve the provider’s judgment.

4. Calculate with explicit assumptions

Trace documented CKD stages to their ICD-10-CM codes, then use the explicitly supplied hypothetical mappings and hierarchy before adding teaching coefficients. For operational scoring, establish the applicable mapping, hierarchy, service eligibility, and segment from matching official files. For departmental metrics, write the numerator, denominator, exclusions, and time window before calculating or interpreting a trend.

5. Study the reference-version boundary

Keep ACDIS’s listed examination references distinct from current coding and query guidance. Use Version 28 for the announced exam requirement and official year-specific CMS files for operational mapping exercises.

6. Review reasoning after the drills

Complete the 20 questions, then explain why every alternative is less appropriate. Revisit weak domains with the flashcards and the complete outline; a practice score does not establish examination readiness.

Use your sample score as a starting point

The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.

Start the free sample

Official sources and updates

Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.