ACDIS CCDS-O Certified Clinical Documentation Specialist-Outpatient (CCDS-O) Exam Practice Test

In the outpatient setting, when the provider does not document a definitive diagnosis for the acute complaint (e.g., influenza, sinusitis, URI), ICD-10-CM guidance directs coders to report thesigns and symptomsthat are documented and addressed. Here, the clinician documentscongestion, fever, and malaiseand provides treatment instructions for those symptoms (OTC meds, rest, follow-up). That makes the symptom codes the most appropriate representation of the reason for the encounter. Outpatient CDI principles further emphasize that chronic conditions likeDM, GERD, and HTNshould only be coded when the documentation shows they wereevaluated, monitored, assessed/managed, or treatedduring the visit (e.g., status, control, medication adjustment, related testing, counseling). In this note, the plan targets only the acute symptoms and does not demonstrate active management of the chronic conditions beyond listing history/medications. Therefore, the guideline most directly applicable to correct coding of the encounter iscodes that describe symptoms and signs.

In MSSP-style ACO financial reconciliation, performance is evaluated against a benchmark (expected costs). Here, the ACO’s actual spending ($52M) exceeds the expected benchmark ($50M) by $2M, meaning the ACO generatedshared lossesrather than savings. In risk-bearing ACO arrangements, when costs exceed the benchmark and the ACO is in a track that includes downside risk, the organization may owe CMS a portion of those losses. The shared savings/loss rate (50% in this scenario) represents the percentage of the difference from the benchmark that the ACO shares with CMS, assuming applicable thresholds are met. Thus, instead of receiving a shared savings payment, the ACO would be accountable topay backa share of the excess spending (conceptually 50% of the $2M overage, if all model requirements are satisfied). Option D is not correct because reconciliation is typically performed on a performance-year basis rather than only at the end of the full agreement period, and option C is not how MSSP eligibility works.

Chronic kidney disease (CKD) is defined by evidence of kidney damage or reduced kidney function that persists for at least three months. An estimated glomerular filtration rate (eGFR/GFR)below 60 mL/minsustained over that timeframe is an objective indicator of chronically decreased renal function and supports CKD identification and staging in the outpatient record. This is why outpatient CDI programs frequently use trended eGFR as a clinical indicator to prompt documentation of CKD stage (e.g., stage 3a/3b, stage 4, etc.) when appropriate. BNP >1000 is more aligned with heart failure severity/volume status rather than kidney damage. BUN <12 is within/near normal and does not indicate renal impairment (elevated BUN may be seen with renal dysfunction but is less specific and affected by hydration, diet, GI bleed). Glucose >100 is a screening indicator for impaired fasting glucose/prediabetes but does not, by itself, establish chronic kidney damage. Therefore, sustained GFR <60 is the best objective lab-based measure of chronic kidney damage over time.

Outpatient CDI queries are most commonly triggered when there is a disconnect between the documented diagnosis and the documented treatment plan, suggesting that the clinician may be managing an additional condition that is not clearly stated, or that the diagnosis is inaccurately documented. Options A and B reflect typical, clinically aligned management: luteinizing hormone-releasing hormone therapy is a standard treatment pathway for prostate carcinoma, and amiodarone is a recognized antiarrhythmic used in atrial fibrillation management in appropriate circumstances. Option C can also be clinically consistent because parenteral nutrition is often used when malnutrition is present and the patient cannot meet nutritional needs enterally. Option D is the outlier: “immunotherapy” is not a standard treatment for severe major depressive disorder and more commonly aligns with oncology or certain immune-mediated diseases. This mismatch would appropriately prompt a query to clarify the actual condition being treated (e.g., an active malignancy) or to confirm whether “immunotherapy” refers to something else (such as allergy immunotherapy) and whether depression is the correct, visit-relevant diagnosis being addressed.

Under the CMS-HCC model, a beneficiary’s risk score (RAF) is intended to represent the expected cost of caring for that individual relative to an average beneficiary. The score is calculated using two primary inputs: (1) the beneficiary’s demographic factors (such as age, sex, Medicaid status/dual eligibility, disability status, and original reason for Medicare entitlement, depending on the model segment), and (2) the beneficiary’s documented disease burden captured through ICD-10-CM codes that map to Hierarchical Condition Categories (HCCs). Those HCCs reflect the person’s health status and severity, with hierarchy rules preventing “stacking” of related conditions and with certain interaction terms in some model versions. Social determinants are not generally described as the defining basis of the traditional CMS-HCC RAF in CDI education, and “family demographics” are not used. The model is not a mortality predictor; it is a cost/risk prediction tool for payment adjustment. Therefore, the best definition is the beneficiary’s individual demographic and health status.

CMS-HCC risk adjustment assigns a baseline coefficient (weight) to each qualifying HCC condition, but certaincombinations of conditionscan increase predicted cost beyond what would be expected by simply adding the two individual weights. These added increments are captured throughdisease interaction factors, which apply when specific conditions coexist (for example, diabetes with certain severe complications, or other paired conditions defined by the model). In outpatient CDI, this is why documentation must clearly support both diagnoses—each must be clinically evaluated/managed and meet reporting rules—because accurately capturing the interacting conditions can legitimately increase the beneficiary’s risk score. By contrast,hierarchiesare designed to prevent double-counting within related condition families (the more severe manifestation typically supersedes a less severe one), which often limits—not adds—separate weights.Resource-based relative valuesandconversion factorsbelong to physician fee schedule payment methodology for services/procedures (RVUs and payment conversion), not HCC risk score calculation. Therefore, disease interactions are the correct concept that adds risk score weight beyond individual HCC coefficients.

In outpatient coding, selection and sequencing must follow ICD-10-CM Official Guidelines, including obstetric chapter rules. When HIV is documented in a pregnant patient, the pregnancy complication code is sequenced first because the pregnancy status frames the encounter and drives the obstetric complication coding structure. The phrase “HIV positive” (without documentation of HIV-related illness or “HIV disease”) is treated asasymptomatic HIV infection status, which aligns with the status concept rather than active HIV disease. Therefore, the correct approach is to codepregnancy complicated by asymptomatic HIVfirst (obstetric complication category), followed by the HIV status code to fully describe the condition affecting the pregnancy. Options that place “pregnancy” second do not follow obstetric sequencing conventions, and options that assume “HIV disease” overstep the documentation because “HIV positive” alone does not confirm symptomatic HIV disease. Outpatient CDI best practice would be to query if the provider intends HIV disease versus asymptomatic status, but based strictly on the given statement, pregnancy with asymptomatic HIV is most appropriate.

RADV (Risk Adjustment Data Validation) is a CMS audit program used in Medicare Advantage to confirm that diagnoses submitted for risk adjustment are supported by medical record documentation and meet reporting requirements. Its central aim ispayment integrity—ensuring that risk-adjusted capitation payments to Medicare Advantage organizations are accurate based on valid, documented conditions. In outpatient CDI practice, RADV risk underscores why documentation must clearly support each reported diagnosis (e.g., condition evaluated/assessed/treated, clinically relevant, and properly documented by an eligible provider), because unsupported diagnoses can lead to payment recoupment and compliance exposure. RADV is not designed to assess medical necessity of the services provided (that is typically addressed through utilization review and other payer audits), nor is it focused on identifying overpayments to individual physicians (it targets plan-level risk adjustment payments). It also is separate from E/M leveling accuracy, which is governed by CPT/E/M guidelines and distinct audit processes. Therefore, the best definition of RADV’s primary purpose is ensuring the integrity and accuracy of risk-adjusted payments.

The HHS-HCC risk adjustment model (used for ACA Marketplace plans) calculates a member’s risk score using a combination ofdemographic factorsanddiagnosis codesthat map to HHS-HCCs. Among the listed health record elements,genderis a core demographic variable used in the model’s coefficients because expected healthcare utilization and cost patterns differ by age/sex groupings. In outpatient CDI terms, this is why accurate demographic data capture (including sex) matters alongside complete and specific condition reporting. CPT codes do not drive HHS-HCC risk scores; the model relies on diagnosis reporting (ICD-10-CM) rather than procedure codes for risk category assignment. Discharge status is an encounter/billing element relevant to certain facility payment and quality measures, but it is not a standard HHS-HCC risk score input. Ethnicity is not used as a direct risk adjustment variable in the HHS-HCC model for score calculation. Therefore, gender is the correct element that impacts HHS-HCC risk scores.

In outpatient and physician-office reporting, the diagnosis that best describes the main reason for the visit is reported as thefirst-listed diagnosis. Outpatient coding guidance emphasizes that the “principal diagnosis” concept is primarily an inpatient construct (the condition established after study to be chiefly responsible for admission). In ambulatory encounters, patients are often seen for evaluation, management, follow-up, or symptom assessment, so the coding framework usesfirst-listedto identify the condition, problem, or symptom chiefly responsible for the services provided during that encounter. Co-existing conditions may also be reported when they are addressed or affect care (e.g., monitored, evaluated, assessed/managed, or treated), but they do not replace the requirement to sequence the primary reason for the visit first. Differential diagnoses are not used as the “reason chiefly responsible” in outpatient coding unless a confirmed diagnosis is established; if uncertainty remains, symptoms may be reported instead. Therefore, “first-listed diagnosis” is the correct term for the outpatient setting.

Medicaid risk adjustment models generally calculate risk using two major categories of inputs:demographicsanddiagnosis data. Demographic factors commonly includegenderand indicators tied toMedicaid status/eligibility(for example, eligibility category, dual status, disability-related eligibility, or other program qualifiers depending on the state/model). These demographic elements adjust expected cost and are foundational to the risk score even before considering diagnoses. By contrast,race is not a standard inputfor calculating Medicaid risk scores in typical risk adjustment methodologies, so options that include race are not supported. Likewise, “patient noncompliance” is primarily a clinical and quality-of-care issue and may affect treatment outcomes, but it isnot itself a standard risk-score driverunless it is documented as a reportable, supported diagnosis that the specific model recognizes (and most models don’t directly risk-adjust for nonadherence codes). Therefore, among the options given,Medicaid status and genderare the most clearly valid factors that impact the beneficiary’s risk score.

In outpatient CDI, a prime query opportunity is any diagnosis with unclear “status” that materially affects coding, risk adjustment, surveillance, and care planning. “History of colon cancer” paired with “18 months s/p bowel resection” creates ambiguity: the provider must clarify whether the malignancy is still active (current disease, recurrence, metastasis, ongoing treatment) versus no longer present (history of malignancy, in remission, disease-free status, post-treatment surveillance only). This distinction changes code selection substantially and prevents inappropriate reporting of an active cancer when the encounter is actually follow-up after curative treatment. By contrast, ostomy status is not documented as present, and OSA/COPD “status” may be clinically useful but is not inherently ambiguous from the prompt in the same way (they are listed as chronic problems without a conflicting timeline event). ACDIS outpatient CDI practice prioritizes clarifying cancer status because it impacts longitudinal documentation integrity, accurate problem list management, and compliant diagnosis reporting at each visit.

This question applies the outpatient risk adjustment “reserve” concept: predicted cost is estimated by multiplying the member’s risk factor contribution by a baseline per-member-per-month (PMPM) amount, then annualizing. The morbid obesity HCC factor is 0.186, and PMPM is $800. First compute the monthly cost impact: $800 × 0.186 = $148.80 per month per patient. Convert to yearly: $148.80 × 12 = $1,785.60 per patient per year. The year-over-year increase in patients with morbid obesity documentation is 11,000 − 10,000 = 1,000 additional patients. Multiply the annual per-patient impact by the additional patient count: $1,785.60 × 1,000 = $1,785,600. Outpatient CDI programs emphasize that improving documentation specificity (when clinically supported) can change whether an HCC is captured, which can affect RAF-based projections and resource planning. However, documentation must still be accurate, supported, and reflect conditions assessed/managed during the encounter.

Across both inpatient and outpatient CDI, the single expectation that must remain consistent isquery compliance. While productivity targets, the types of query opportunities, and the way “impact” is measured can differ significantly by setting (e.g., DRG/CC-MCC focus in inpatient vs. HCC capture, specificity, and MEAT support in outpatient), the compliance framework for querying does not change. A compliant query must be clinically supported, non-leading, clearly written, and must allow the provider to independently determine the most accurate documentation based on the record. It should include relevant clinical indicators, present reasonable options (including “other”/“unable to determine” when appropriate), and avoid language that appears to request diagnoses for payment purposes. These principles protect documentation integrity, support defensible coding, and reduce audit risk regardless of whether the encounter is hospital-based or ambulatory. By contrast, “review productivity” and “revenue impact” vary widely by program design and setting, and “query opportunities” differ because inpatient vs. outpatient have different reportability rules and documentation drivers. Therefore, query compliance is the metric held to the same standard in both environments.

Year 2 shows a higher total volume of MDD diagnoses (185,090 vs. 155,501), but the key CDI signal is the shift in coding specificity: “MDD, specified” increases substantially (118,516 vs. 76,318), while “MDD, unspecified” decreases (66,574 vs. 79,193). In outpatient CDI terms, this pattern is consistent with improved documentation quality and code capture—providers are describing the condition with greater clinical detail (episode type, severity, remission status, recurrence, etc.), allowing assignment of more specific ICD codes. When an HCC value (0.299) is associated with MDD, improved capture of qualifying, specific MDD codes supports more accurate risk adjustment. That increases the accuracy of projected resource need and affects future cost benchmarking (and potentially quality/utilization comparisons) because the population’s documented burden of illness is better represented. Therefore, the appropriate inference is increased patients plus increased “specified” use and decreased “unspecified,” with an impact on future benchmarking.

A compliant query is designed to clarify the record without steering the provider to a predetermined answer. ACDIS-aligned standards stress two essentials: neutrality (non-leading phrasing) and clinical support (relevant indicators). Clinical indicators might include vitals, labs, imaging, medications, documented symptoms, problem list history, or assessment findings that create the need for clarification. The query should present the inconsistency or ambiguity, reference the supporting facts, and offer clinically reasonable answer choices including “other” and “unable to determine” when appropriate. This structure protects documentation integrity and reduces regulatory risk, because leading queries can be interpreted as directing documentation for payment rather than accuracy. Verbal-only queries are not sufficient when they affect coding; CDI programs typically require a documented query trail per policy. Purely open-ended questions without context are also problematic because they do not show why clarification is needed and may not be actionable. Proper non-leading, indicator-supported queries improve accuracy of diagnosis specificity, severity capture, and defensibility in audits while preserving provider autonomy.

When a CDI query references information from an externally shared note, best practice is to include enough identifying detail so the provider can locate and validate the sourceeven if access is later revokedor if the shared record becomes unavailable. From an outpatient CDI and HIPAA-aligned workflow perspective, the query should clearly cite: where the information came from (thelocationof the shared note within the EHR/external record set),whoauthored it (provider name),whenit was created (date of shared note), and thespecific clinical documentationbeing referenced (the relevant statement/findings). This supports transparency, auditability, and minimizes the risk of misattribution or relying on inaccessible information. Options B–D are missing one or more critical elements—most notably the date and/or location of the shared note—making it harder to verify the source. Including “follow-up procedure” is not the priority for HIPAA-compliant source identification; the key need is traceability of the external documentation used to support the clarification request.

Effective outpatient CDI depends on provider engagement, efficient workflows, and respectful communication. When a provider is frustrated about time pressures, the most productive approach is to partner with them to reduce friction while preserving compliant documentation improvement. ACDIS outpatient CDI concepts emphasize collaboration and provider education—meeting the provider where they are, understanding their workflow constraints, and jointly designing a query process that is minimally disruptive (e.g., batching queries, aligning with clinic schedules, using prospective queries, leveraging templates, or routing through agreed channels). Option C directly addresses the root issue (workflow burden) and builds trust by seeking the provider’s input and scheduling the discussion at their convenience. Option A is confrontational and frames CDI as a compliance demand rather than a clinical accuracy initiative. Option B is inappropriate because CDI cannot stop querying when clarification is needed for accurate documentation, coding, quality reporting, and risk adjustment. Option D escalates prematurely and damages relationships; escalation is typically reserved for persistent, unresolved non-responsiveness after collaborative efforts and leadership-supported education.

Stage 3 pressure ulcers are defined byfull-thickness skin losswhere the injury extends through the dermis and involvesdamage or necrosis of subcutaneous tissue. Clinically, the ulcer may present as a deep crater and can include undermining or tunneling, but the key boundary is thatbone, tendon, and muscle are not exposed. That deeper involvement (exposed muscle/tendon/bone) is characteristic of Stage 4, making option C incorrect. Option D describes partial-thickness loss, which aligns with Stage 2 (epidermis/dermis involvement such as abrasion or blister). Option A reflects early skin changes that correspond more closely to Stage 1 (intact skin with non-blanchable erythema and possible localized edema/induration). In outpatient CDI chart review, accurately distinguishing Stage 3 from Stage 2 and Stage 4 is essential because staging drives severity capture, care planning (wound care interventions, debridement considerations), and quality reporting. Documentation should clearly support “full thickness,” the tissue layers involved, and the absence of exposed bone/tendon/muscle.

RADV (Risk Adjustment Data Validation) is an audit process used to validate that risk-adjusting diagnoses submitted for payment are supported by compliant medical record documentation. A foundational requirement is that the record is properly authenticated by an acceptable provider—meaning the documentation must be attributable to the treating clinician through a valid signature. In compliant documentation standards emphasized in outpatient CDI education, acceptable authentication may be a traditional hand-written signature or an electronic signature/attestation that meets organizational and regulatory policy. Option B is not correct because diagnoses do not have to appear only on a facesheet or “final diagnosis” list; they may be supported within the body of the note (assessment/plan, problem-based charting, or other authenticated sections) as long as they are clearly documented and clinically supported. Options A and D are not reliably true statements in a general RADV context because RADV focuses on diagnoses supported by appropriate provider documentation and acceptable encounter record criteria; “technician-assigned” diagnoses are not acceptable, and radiology documentation alone may not meet all validation expectations depending on the program’s rules and encounter context.

This documentation presents a key outpatient CDI problem:hemiparesis is present, but two potential causal conditions are referenced—history of CVAandintracranial trauma—without clear linkage. In ICD-10-CM, correct reporting of hemiparesis often depends on identifying whether it is alate effect (sequela)of a prior stroke, a residual from traumatic brain injury, or due to another neurologic condition. Coding hemiparesis automatically as a CVA sequela (option A) would be assumptive and potentially inaccurate, because the clinician has not documented the relationship. Likewise, simply coding hemiparesis alone (option D) may miss important etiologic specificity, and coding both histories without clarifying the cause (option B) still leaves the main clinical ambiguity unresolved. Outpatient CDI best practice is to issue anon-leading queryrequesting provider clarification of theetiology/sourceof the hemiparesis (e.g., due to prior CVA, due to prior intracranial trauma, both, or other/undetermined). This supports accurate diagnosis reporting, appropriate sequencing, and defensible risk/quality representation.

When the goal is todemonstrate documentation and coding patternsto a mixed audience of providers and administrators, the most effective tool is one that clearly displayscomparisons and trendsin an easily interpretable way. Abar graphis ideal because it can quickly show differences in rates or volumes—such as unspecified diagnosis utilization, HCC capture rates, query response/agree rates, denial categories, or condition specificity—across providers, clinics, or time periods. This supports outpatient CDI education by making variation visible and actionable while keeping the discussion focused on documentation behaviors and opportunities for improvement. A spaghetti diagram is used for mapping physical workflow movement and inefficiencies, not coding patterns. The PDSA cycle is a structured improvement method for testing changes, but it is not primarily a visualization tool for presenting pattern data. The Donabedian model (structure–process–outcome) is a quality framework that helps organize improvement thinking, but it doesn’t display coding/documentation pattern performance as directly as a bar graph.

In outpatient risk adjustment (commonly Medicare Advantage), the patient’s predicted cost is derived from the Risk Adjustment Factor (RAF), which is the sum of component risk contributions. Here, the RAF is calculated by adding the HCC diagnoses score (0.166), disease interactions (0.112), and demographic score (0.330). That total equals 0.608. The PMPM (per-member-per-month) baseline cost is $800. To estimate the patient’s expected monthly cost, multiply PMPM by RAF: $800 × 0.608 = $486.40 per month. The question asks for the expected yearly cost, so convert PMPM to annual: $486.40 × 12 = $5,836.80. ACDIS outpatient CDI teaching emphasizes that accurate documentation and compliant coding directly affect RAF through captured HCCs and interactions (when supported), which in turn drives expected resource needs and plan payment. Missing or unsupported diagnoses can understate RAF; vague documentation can prevent valid HCC capture.

In outpatient clinical documentation and chart review, diabetes can be supported by recognized diagnostic thresholds. An HbA1c value reflects average blood glucose over approximately the prior 2–3 months and is commonly used to diagnose and monitor diabetes. An HbA1c≥ 6.5%(when confirmed per clinical practice standards and interpreted in the appropriate clinical context) supports a diagnosis of diabetes; therefore an HbA1c of7.0%clearly meets the threshold and supports diabetes. By comparison, a2-hour OGTT value of 90 mg/dLis normal and does not support diabetes (diabetes is typically supported when the 2-hour value is≥ 200 mg/dL).Hypoglycemiais low blood glucose and is not diagnostic of diabetes; it may occur in diabetics due to treatment but can also occur in non-diabetics for many reasons. Afasting glucose of 100 mg/dLis at most borderline/prediabetes range and does not meet diagnostic criteria for diabetes (diabetes is supported at≥ 126 mg/dL).

In outpatient CDI chart review, a key skill is recognizing when medications and treatment plans suggest a specific diabetic complication that is not explicitly documented. Gabapentin is commonly prescribed for neuropathic pain, and in a diabetic patient it is frequently used to treatdiabetic peripheral neuropathysymptoms (burning, tingling, numbness, shooting pain). ACDIS outpatient CDI guidance supports querying when there are strong clinical indicators that a more specific, clinically relevant diagnosis may be present and is being treated at the encounter, because diabetes codes require complication specificity when supported (e.g., “diabetes with neuropathy” rather than unspecified diabetes). The elevated glucose and A1C confirm ongoing diabetes management but do not, by themselves, indicate CKD, macular degeneration, or ketoacidosis. Ketoacidosis would require documentation of acute metabolic decompensation and supporting clinical/lab findings, which are not provided here. Therefore, the most appropriate clarification is whether the patient has diabetic peripheral neuropathy (and whether it is painful neuropathy) being managed with gabapentin, so the provider can document the condition clearly and accurately.

Outpatient CDI performance is best measured by metrics that reflect ambulatory documentation quality, risk-adjustment accuracy, and provider engagement.HCC capture rateis central because outpatient CDI frequently supports risk adjustment (e.g., CMS-HCC/HHS-HCC) and aims to ensure chronic conditions are accurately documented, linked, and reported when they are actively managed.Unspecified code utilization rateis a practical quality metric for provider education because high unspecified use often signals missed clinical specificity (severity, laterality, acuity, manifestations, staging) that can reduce coding accuracy, obscure patient complexity, and weaken data used for benchmarking and quality reporting.Query response rateis also a core operational KPI: it reflects provider participation, workflow effectiveness, and the CDI team’s ability to obtain timely clarifications that support compliant coding and complete clinical representation. In contrast,Medicare CMIandseverity of illnessare predominantly inpatient-focused constructs and are not the primary yardsticks for outpatient CDI program success. While aggregate RAF and quality indicators matter, the best “program performance” set is the one directly tied to outpatient CDI levers: HCC capture, specificity/unspecified reduction, and query responsiveness.

Outpatient diagnosis reporting requires coding conditions that are evaluated, assessed, treated, or that influence care/management at the encounter. The chief reason for the visit is the persistent cough, which is assessed and attributed to an adverse effect of an ACE inhibitor (enalapril). For outpatient coding of medication adverse effects, the documentation supports reporting both the manifestation (cough) and the adverse effect of the drug (ACE inhibitor adverse effect), because the provider identified the causal relationship and changed therapy by discontinuing enalapril. In addition, the provider addresses chronic conditions that are clinically relevant to the visit: COPD is assessed as “stable” and the patient is instructed to continue COPD/asthma medications, demonstrating ongoing management. Hypertension also remains relevant because medication therapy is adjusted due to the adverse effect; the patient still has HTN even though one agent is discontinued. Therefore, all five items—cough, ACE inhibitor adverse effect, COPD, asthma, and hypertension—are supported and should be reported, making option D the most appropriate.

Symbicort is an inhaled combination medication containing an inhaled corticosteroid (ICS) and a long-acting beta-agonist (LABA). In outpatient chart review, this medication class is most strongly associated with chronic airway inflammatory diseases requiring controller therapy—especiallypersistent asthma(and also maintenance therapy for COPD, though COPD is not an option here). For CDI purposes, medication-to-diagnosis linkage can act as a clinical indicator supporting clarification when the visit note lists respiratory symptoms but does not clearly document the chronic condition being treated or its acuity/status. Symbicort is not used to treat musculoskeletal degenerative disease (osteoarthritis), peripheral nerve pain from diabetes (diabetic neuropathy), or cardiac pump failure (congestive heart failure). When Symbicort appears on the active med list, outpatient CDI commonly checks that the provider’s documentation appropriately reflects asthma classification (intermittent vs persistent), current control, exacerbation status if applicable, and that the condition is being monitored/assessed/treated during the encounter to support reportability and accurate coding.

Atrial fibrillation (AF) type is determined largely by episode duration and whether the rhythm self-terminates. In outpatient CDI education,paroxysmal AFis intermittent and typically terminates spontaneously, commonly within7 days(often within 48 hours).Persistent AFis sustained and lastsmore than 7 days, or requires active intervention (e.g., cardioversion) to restore sinus rhythm. This scenario documents AF “for10 days,” which exceeds the 7-day threshold and therefore best fitspersistentAF. The management also aligns with a sustained arrhythmia strategy: rate control (atenolol), rhythm control/antiarrhythmic therapy (sotalol), stroke prevention anticoagulation (rivaroxaban), and discussion of catheter ablation, which is often considered for symptomatic or recurrent/persistent AF. “Chronic” is a nonspecific descriptor and not the preferred current classification term, andpermanent AFimplies a decision has been made not to pursue rhythm control (accepting AF long-term), which is not supported here because rhythm-control options are being considered.

Outpatient CDI programs should share provider-facing metrics that are clinically meaningful, aligned with ambulatory documentation goals, and unlikely to be perceived as payment-driven prompting.RAF scoresare an appropriate metric because they reflect how well the documented and coded condition burden represents the patient panel’s complexity in risk adjustment models. Discussing RAF supports education around accurate diagnosis capture, specificity, and annual recapture of active chronic conditions that are monitored, evaluated, assessed/addressed, or treated. In contrast,APC payment ratesare facility OPPS payment constructs and typically are not actionable for individual ambulatory provider documentation improvement.HCC per member per month paymentsis explicitly financial and can create compliance risk by tying documentation discussions directly to payment, which outpatient CDI guidance warns against in provider messaging.MCC ratesare primarily an inpatient DRG severity concept and are not the most relevant outpatient performance measure. Therefore, RAF scores best balance provider relevance, program goals, and compliant education focus.

Under Medicare billing rules applied in outpatient CDI education,observation services are outpatient(typically paid under Part B), even though the patient may stay in a hospital bed and receive ongoing monitoring and treatment. Therefore, anED visit that converts to observationremains an outpatient encounter from a billing and documentation perspective, and the services are reported/paid as outpatient. By contrast, when an ED visit results in aninpatient admission, the encounter transitions to inpatient status, and many hospital ED services immediately preceding admission are commonly bundled/packaged with the inpatient stay rather than billed as a separate outpatient encounter. A scheduledsigmoid resectionis generally a major procedure that is not typically performed as ambulatory/outpatient surgery in routine circumstances, so it is not the best outpatient choice here. Finally, “admission for COPD exacerbation with LOS less than two midnights” is ambiguous because “admission” implies inpatient, even though short stays may sometimes be observation/outpatient depending on medical necessity and the 2-midnight guidance. The clearest outpatient encounter is ED leading to observation.

In outpatient CDI and coding, the Official ICD-10-CM Guidelines that apply are the universal rules plus the outpatient-specific rules. Section I contains conventions, general coding guidelines, and chapter-specific guidance that govern code assignment in every setting (e.g., code structure, “use additional code,” laterality, sequencing instructions, and condition-specific rules). Section IV is specifically written for outpatient services and drives core outpatient behaviors such as selecting the “first-listed” diagnosis based on the main reason for the encounter, reporting additional diagnoses that are evaluated/assessed/treated or impact care, and applying outpatient-only restrictions (for example, diagnoses documented as “rule out,” “probable,” or “suspected” generally are not coded in outpatient the way they may be for inpatient reporting). ACDIS outpatient CDI education emphasizes teaching providers to document clearly the reason for visit, the assessment/clinical relevance of each condition addressed, and the linkage between conditions and services rendered so Section I and Section IV rules can be applied accurately for compliant reimbursement and reporting.

Risk adjustment is used to make cost and efficiency comparisons fair by accounting for differences in patient severity and expected resource needs. In outpatient CDI, accurate documentation and coding of chronic and acute conditions (especially risk-adjusting diagnoses such as HCC-relevant conditions) directly influence the risk profile assigned to a patient population. That risk profile is then applied when evaluating utilization and cost measures—such as total cost of care, inpatient admissions, ED use, and other resource consumption—so that providers or groups caring for more complex patients are not inappropriately labeled as inefficient simply because their patients require more services. This aligns with option B: risk adjustment is applied to resource utilization measures. Option A is incorrect because E&M levels are a professional billing construct and are not the basis for risk score calculation. Option C is incorrect because physician time may affect E&M selection under certain rules, but it is not the mechanism for risk adjustment in cost efficiency analytics. Option D is incorrect because procedures/interventions describe services rendered, not the adjustment methodology itself.

A core outpatient guideline difference is how to handle uncertainty in diagnoses. In the inpatient setting, facilities may code diagnoses documented as “probable,” “suspected,” “likely,” or “rule out” at discharge if they meet inpatient reporting rules. In outpatient/office settings, however, uncertain conditions generally are not coded as established diagnoses because the encounter is often focused on evaluation rather than confirmed final diagnoses. Instead, outpatient coding relies on confirmed conditions and/or signs and symptoms when a definitive diagnosis has not been made. This is why outpatient CDI education emphasizes precise provider language: if the clinician is still evaluating, they should document the symptom/abnormal finding and the assessment plan; if the condition is confirmed, they should state it clearly and link it to evaluation/management performed. Options A, B, and D are incorrect because chronic conditions may need to be reported whenever they are assessed/managed, “first-listed” is an outpatient concept distinct from inpatient “principal,” and documentation should support all clinically relevant conditions addressed, not only the chief complaint.

This query is non-compliant because it isleading: it asks the provider to “confirm a diagnosis of hemiplegia,” presenting only one targeted outcome rather than requesting clarification in a neutral, clinically appropriate way. ACDIS-aligned outpatient query practice requires queries to be compliant, non-leading, and supported by clinical indicators, typically offering multiple reasonable options (or an open-ended format) and allowing the provider to document the most accurate clinical impression. In this scenario, “history of CVA,” “left-sided weakness,” and “physical therapy ordered” could reflect several possibilities—such as hemiparesis, residual weakness, post-stroke deficits, deconditioning, or other neurologic impairment—so the query should ask the provider to clarify thenature and diagnosisof the deficit (and laterality), not to confirm a single diagnosis. Option A is incorrect because coding cannot assume hemiplegia without provider documentation. Option C is not the best feedback because indicators can justify clarification. Option D is unnecessary; MRI results are not required for a compliant outpatient query.

In the outpatient/ambulatory setting, ICD-10-CM reporting rules applied in CDI education distinguish clearly between confirmed diagnoses and “uncertain” or “rule out” conditions. Terms such as “rule out,” “suspected,” or “probable” generally are not coded as established diagnoses in the outpatient record because the encounter is often for evaluation and testing rather than definitive confirmation. Instead, coders report the patient’s presenting signs and symptoms when a definitive condition has not been documented as confirmed by the provider. Here, the clinician ordered diagnostic testing (ECG and chest x-ray) specifically to rule out myocardial infarction (MI), but no final diagnosis of MI or angina is documented in the scenario. Therefore, “rule out MI” is not reportable, and neither is acute MI or angina unless explicitly diagnosed. The reportable conditions are the symptoms that drove the visit and required evaluation: chest pain (captured as “other chest pain” in the options), shortness of breath, and nausea.

This scenario describes a query placedbefore the patient is seen, with the intent that the issue be addressedduring the upcoming visit. In outpatient CDI practice, that is the defining feature of aprospectivequery: it is initiated ahead of the encounter so the provider and/or clinic team can capture needed specificity in real time (here, clarifying BMI-related documentation to support an obesity diagnosis when clinically appropriate). By contrast, aconcurrentquery is typically issued while the encounter is actively occurring or immediately as documentation is being created and reviewed in near–real time. Aretrospectivequery occurs after the visit is completed, usually during post-encounter review, when opportunities are identified after documentation is finalized. “Prebill” refers to a workflow timing concept tied to billing hold/review before claim submission, not the clinical timing of when the patient will be seen. Because the query is placed in advance specifically to be addressed during the scheduled visit,prospectiveis the best classification.

Provider engagement in an outpatient CDI program is best reflected by measures that show the provider is actively interacting with CDI processes and improving documentation behaviors in real time.Query response ratesdirectly indicate whether the provider is reading and responding to CDI clarifications promptly and consistently, which is a fundamental engagement behavior and a key operational driver of documentation accuracy.Problem list updatesfurther demonstrate sustained engagement because they reflect the provider’s willingness to maintain an accurate, current list of active conditions (adding validated diagnoses, removing resolved problems, and updating specificity such as stage, severity, or laterality). Together, these two metrics show both immediate participation (responding to queries) and longer-term adoption of documentation best practices (maintaining the problem list). In contrast,RAF scoresandRAF capture ratesare influenced by patient complexity, payer mix, and coding capture processes, and may improve even without meaningful provider participation.MIPS scoresreflect broader quality program performance and are not specific to CDI-provider interaction. Therefore, query responsiveness plus problem list maintenance most directly measures engagement with outpatient CDI.

When internal CDI metrics show increased HCC-related querying and coding accuracy is confirmed, you would typically expect payer RAF outputs to stabilize or improve—assuming the payer receives and processes the same diagnosis data. A payer-reported RAF decrease despite accurate internal capture most strongly suggests a break in the data flow between the organization and the payer. In outpatient risk adjustment, RAF depends on documented, supported diagnoses being correctly coded and then successfully transmitted on the encounter/claim to the payer’s risk-adjustment ingestion process. If certain diagnoses are dropped (claim edits, interface mapping issues, encounter rejection, late submissions, or incomplete encounter files), the payer’s dataset will under-represent HCCs and RAF will fall even though internal coding looks correct. CPT visibility (B) generally affects utilization/fee-for-service payment and analytics, not HCC-based RAF. Compliant queries (C) describe process quality but don’t explain a payer-side RAF decline. A local “model not updated” (D) wouldn’t reduce payer-calculated RAF if the payer is applying its own current model to received diagnoses.

HCC category assignment is most similar to DRG diagnostic category logic because both methods take detailed diagnosis coding andmap it into clinically meaningful groupingsused for payment or performance methodologies. In CMS-HCC risk adjustment, ICD-10-CM diagnosis codes map to Condition Categories (HCCs) that represent disease groups with expected cost and complexity, and the model applies rules such ashierarchies(to avoid double-counting related conditions) and, in some cases,interactions(to recognize added impact when certain conditions coexist). DRGs similarly group diagnoses (and procedures in the inpatient setting) into a limited number of categories intended to reflect resource consumption and clinical similarity, rather than paying strictly on every individual code. By contrast, 835 is a remittance advice transaction standard (payment explanation) and has nothing to do with clinical grouping methodology. ICD-10-PCS and CPT are procedure/service coding systems; they describe interventions performed, not the risk-category grouping of diagnoses. Therefore, DRG diagnostic categories are the closest conceptual match to HCC assignment methodology.

A well-maintained problem list supports continuity of care by giving the care team an accurate, up-to-date clinical “snapshot” of active and relevant historical conditions that affect ongoing management, decision-making, and risk assessment. Outpatient CDI education emphasizes that the problem list should be curated—conditions should be current, clinically meaningful, and appropriately resolved or clarified (e.g., active vs history, controlled vs uncontrolled). Option A is incorrect because diagnoses are not removed based on an arbitrary time threshold; they are updated based on clinical status (resolved, inactive, erroneous, or no longer relevant). Option C is inaccurate because simply adding more diagnoses can introduce noise and increase the risk of outdated or incorrect conditions being propagated (“problem list bloat”), which can harm patient safety and lead to inaccurate coding. Option D is inaccurate because CDI professionals typicallydo notindependently update the problem list; rather, they support providers through compliant queries, education, and process improvements so the treating provider validates and maintains the record. Therefore, B best reflects outpatient documentation best practice.

A high query rate with a strong physician response rate shows the CDI specialist is generating many queries and providers are opening/responding to them. However, a consistently lowagree rateindicates providers frequently select “disagree,” “clinically undetermined,” or otherwise do not validate the query’s suggested clarification. In outpatient CDI program management, that pattern most often reflectsquery quality problems—for example, queries that are not well-supported by encounter-specific clinical indicators, queries that are vague or overly speculative, or queries that do not align with outpatient reportability standards (e.g., prompting for diagnoses not clearly monitored/evaluated/assessed/treated). While leading queries are a compliance concern, the more direct operational inference from “high volume + answered + not agreed with” is that the queries are not clinically compelling or are poorly constructed, resulting in frequent provider non-concurrence. Case complexity alone would not reliably drive low agree rates if the queries were appropriately targeted and evidence-based. Therefore, the most likely interpretation is poor-quality queries requiring coaching on clinical support, clarity, and compliant construction.