CCDS-O Certified Clinical Documentation Specialist-Outpatient (CCDS-O) Questions and Answers

ICD-10-CM category N18 (Chronic kidney disease) is used to report CKD by stage , including stage-based descriptors and end stage renal disease (ESRD) . Within N18, codes identify CKD stage 1 through stage 5, ESRD (stage 5D) , and CKD unspecified. Outpatient CDI review focuses on ensuring providers document the stage (often supported by eGFR trends) because stage drives correct code selection and accurately reflects disease severity for risk, quality, and medical necessity. Options that include dialysis are not part of N18 itself; dialysis status and encounter codes are reported elsewhere (e.g., dialysis dependence/status codes), not as N18 category diagnoses. AKI (acute kidney injury) and ATN (acute tubular necrosis) are acute renal conditions and are coded outside N18. Likewise, polycystic kidney disease and “uremia” are separate diagnoses with their own code categories. Therefore, the set that correctly matches what N18 represents is CKD stage-based diagnoses such as CKD stage 3 , more advanced/severe CKD stages, and ESRD .

APCs and DRGs are both prospective payment classification systems designed to group services that consume similar resources, supporting standardized reimbursement. DRGs group inpatient stays largely around the principal diagnosis, key procedures, complications/comorbidities, and discharge status to estimate expected hospital resource use for the admission. APCs, used primarily for hospital outpatient services, group billable procedures and services that are clinically comparable and expected to require similar levels of resources (staff time, supplies, equipment, intensity). While APCs often allow multiple payment classifications within a single outpatient encounter (because multiple procedures may be performed), that feature is not the fundamental similarity to DRGs—it’s a key difference in operational payment mechanics. Likewise, APC assignment is generally driven by CPT/HCPCS and revenue codes rather than being primarily diagnosis-dependent. The shared concept emphasized in outpatient CDI education is that both systems aim to align payment with anticipated resource utilization, which is why complete, accurate documentation is essential to support correct coding of the services and conditions that justify the level of care provided.

In hospital outpatient settings paid under OPPS, Ambulatory Payment Classifications (APCs) are influenced by the coded services and, in many workflows, the clinical documentation that supports correct CPT/HCPCS selection, units, modifiers, and—when applicable—medical necessity linkages to diagnoses. Accurate documentation ensures that the record supports what was actually performed (e.g., complexity, laterality, supplies, drug administration details, observation criteria, or separately payable procedures) and that coding can correctly apply bundling/packaging rules without losing legitimately reportable services. While APCs are primarily procedure-driven, documentation remains decisive because incomplete or ambiguous notes lead to downcoding, missed charges, incorrect status indicators, or denials during medical review. From an outpatient CDI standpoint, the goal is to ensure the clinical story supports codeable services and their necessity: clear indications, findings, assessment/plan, and any required elements (time, start/stop, dose/route for medications, device details, etc.). This supports appropriate APC grouping and reimbursement integrity, reducing rework, denials, and compliance risk.

When the goal is to demonstrate documentation and coding patterns to a mixed audience of providers and administrators, the most effective tool is one that clearly displays comparisons and trends in an easily interpretable way. A bar graph is 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.

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.

A Stage 4 pressure ulcer (pressure injury) is characterized by full-thickness tissue loss with extensive destruction, tissue necrosis, or damage to muscle, bone, or supporting structures . The key phrase in the question—“necrosis of soft tissue through the underlying muscle”—signals a depth of injury that extends beyond the subcutaneous tissue and involves muscle, which is consistent with Stage 4. By comparison, Stage 2 involves partial-thickness skin loss with exposed dermis (no necrosis through deeper structures). Stage 3 involves full-thickness skin loss where adipose may be visible, but muscle, tendon, or bone are not exposed ; undermining and tunneling may occur, yet the defining line is that it does not extend to muscle/bone involvement. “Stage 5” is not part of standard pressure ulcer staging used in coding and documentation. Outpatient CDI practice emphasizes documenting the exact stage, anatomic location, laterality when applicable, and whether the ulcer is healing or complicated (infection/osteomyelitis) because stage drives specificity, severity capture, and appropriate care planning documentation.

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.

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 source even if access is later revoked or 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 (the location of the shared note within the EHR/external record set), who authored it (provider name), when it was created (date of shared note), and the specific clinical documentation being 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.

Sertraline is a selective serotonin reuptake inhibitor (SSRI) most commonly used to treat depressive disorders and several anxiety-related conditions. In outpatient chart review, recognizing medication–condition relationships supports accurate problem list maintenance and compliant diagnosis reporting, but the diagnosis must still be clearly documented as assessed/managed at the encounter. Depression is the best match because SSRIs like sertraline are first-line pharmacologic therapy for major depressive disorder and are frequently continued long-term with monitoring for symptom control, side effects, and functional status. Schizophrenia is primarily treated with antipsychotic medications; sertraline may be used only as an adjunct if a comorbid depressive or anxiety disorder is present, so it is not the common primary treatment. Asthma management centers on bronchodilators and inhaled corticosteroids, not SSRIs. Heart failure therapy involves guideline-directed cardiac medications (e.g., beta-blockers, ACE inhibitors/ARNI, diuretics), and sertraline is not a standard heart failure treatment. Outpatient CDI education emphasizes documenting the specific mental health diagnosis, current status (stable/worsening), and treatment plan to support coding.

The CDI specialist should review CKD staging criteria with the provider because assigning CKD based on a single eGFR value can be clinically unreliable and may lead to inaccurate documentation and coding. Outpatient CDI guidance emphasizes that documentation must reflect a condition that is clinically valid, supported by the record, and accurately described , especially for chronic diseases. CKD is generally established by evidence of decreased kidney function or kidney damage that is persistent , not a one-time lab that could be affected by hydration status, acute illness, medications, or transient physiologic changes. While an eGFR of 52 falls within the numeric range commonly associated with stage 3a , the key CDI issue is the foundation for diagnosing chronic disease , not simply whether the number is “reportable.” Option A inappropriately directs CDI to add diagnoses to claims; CDI supports providers and coding, but does not independently “add” conditions. Option C is incorrect because chronic conditions may be coded when addressed/impact care, not only when actively treated. Option D is unsupported because eGFR 52 does not suggest stage 4.

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.

For RAF impact in the CMS-HCC model, the most valuable provider education targets are conditions that (1) map to HCCs or interact with HCC hierarchies, and (2) are clearly within the specialist’s scope to assess and manage during visits. In this scenario, the endocrinologist is actively treating diabetes and its complications. Diabetes with peripheral neuropathy/vascular disease plus an active non-healing foot ulcer reflects significant diabetic disease burden and often supports additional required coding (e.g., diabetes complication code plus a separate site/severity ulcer code). The history of toe amputations is also important because amputation status can represent ongoing complexity, affects care planning (risk of recurrent ulcer/infection), and may contribute to risk capture depending on the model and associated complications. By contrast, CAD/COPD/HF may not be evaluated by the endocrinologist at the visit, “A1C” is a lab value (not a diagnosis), and “history of prostate cancer” generally does not risk-adjust like active malignancy. Therefore, educating on documenting diabetes, amputation status, and ulcer details best supports RAF accuracy.

CMS-HCC risk adjustment assigns a baseline coefficient (weight) to each qualifying HCC condition, but certain combinations of conditions can increase predicted cost beyond what would be expected by simply adding the two individual weights. These added increments are captured through disease 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, hierarchies are 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 values and conversion factors belong 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.

A leading query is one that steers the provider toward a particular diagnosis or limits clinically appropriate choices in a way that can be perceived as prompting. Option D is leading because it presents a single, high-impact diagnosis (“alcohol dependence”) and forces a binary yes/no response without offering reasonable alternative interpretations (e.g., alcohol use, alcohol abuse/harmful use, dependence in remission, or clinically undetermined) or an “other” option. In addition, it attempts to obtain a potentially new diagnosis based on one data point (quantity consumed) without a balanced set of diagnostic possibilities and supporting clinical indicators (tolerance, withdrawal, impairment, failed attempts to cut down, etc.). By contrast, A is open-ended and requests clarification of the treated condition; B provides two plausible classification choices (active vs history); and C offers multiple reasonable BMI-related diagnostic options plus “other” and “clinically undetermined,” which supports compliant, non-leading clarification. Therefore, D best fits the definition of a leading query.

In the CMS-HCC risk adjustment methodology, each qualifying condition maps to an HCC with an associated coefficient (weight). However, CMS also recognizes that certain combinations of conditions can drive costs and complexity more than the simple sum of individual HCC weights. To account for this, the model includes disease interaction terms —additional coefficients applied when specific conditions coexist in the same beneficiary (for example, selected interactions involving diabetes and particular complications, or other defined pairings). This is why outpatient CDI focuses not only on capturing each chronic condition accurately, but also ensuring both conditions are clearly documented as assessed/managed and meet reporting requirements, because capturing both can legitimately trigger interaction weights. By contrast, hierarchies primarily prevent double-counting within related disease groups by allowing the most severe manifestation to “trump” a less severe one; this generally controls/limits weight rather than adding extra. Resource-based relative values and conversion factors are physician fee schedule payment components (RVUs and payment calculation), not HCC risk scoring elements. Therefore, disease interactions are the correct answer.

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.

In the outpatient setting, diagnoses documented as uncertain (e.g., “possible,” “probable,” “suspected,” “rule out”) are generally not coded as confirmed conditions; instead, coding is based on confirmed diagnoses or, when not confirmed, the presenting signs/symptoms. Here, the provider documented only “possible Zika,” which is not a confirmed diagnosis for outpatient reporting. Even though the CDI specialist sees a positive serology result, lab data alone does not replace provider diagnostic confirmation in the assessment/plan. The appropriate next step is to query the provider to confirm whether Zika is the established diagnosis based on the positive test (and whether it is clinically addressed during the encounter). If confirmed, Zika can be coded appropriately and sequenced based on the reason for the visit; if not confirmed or still under evaluation, the symptom (fever) remains first-listed. Option B is incorrect because coders do not “code the result” of a serology test as a diagnosis; they code the condition the test supports once clinically confirmed.

In the CMS-HCC model, certain disease groupings are arranged in hierarchies so that when multiple related conditions are reported for the same patient, only the most severe (highest-ranked) HCC in that hierarchy is counted for risk adjustment. This prevents “double counting” of clinically related conditions that represent the same underlying burden of illness. The cancer-related HCCs in the 35–38 range are an example of this hierarchical design: if a patient has diagnoses that map to more than one of these HCCs, the model retains the highest-ranked category and suppresses the lower ones. Therefore, the correct hierarchy order is from the most severe category (HCC 35) down sequentially through HCC 36, HCC 37, and HCC 38. From an outpatient CDI perspective, this reinforces why accuracy and specificity matter: documentation should clearly establish the most clinically severe, active, and treated condition so the correct (highest) HCC is captured, rather than relying on nonspecific or less severe descriptors that could under-represent patient complexity.

Within the CMS-HCC model, only certain diagnoses map to HCC categories that contribute to the RAF score. Among the listed options, cachexia is the diagnosis most likely to map to an HCC because it represents a serious systemic wasting condition associated with significant morbidity, higher expected resource use, and frequently coexists with advanced chronic disease. In contrast, Barrett’s esophagus generally does not map to an HCC in CMS risk adjustment, and symptom-based diagnoses such as significant weight loss typically do not trigger HCC capture. Anorexia in general clinical usage often represents a symptom (loss of appetite) and, unless it is clearly documented as a qualifying malnutrition-related condition with appropriate specificity, it usually does not map to an HCC. The plan for tube feeding and dietitian involvement strengthens clinical relevance, but for risk adjustment the diagnosis must be one that maps to an HCC category—here, cachexia is the one that meets that criterion and would be the HCC-triggering diagnosis.

To support a query for alcohol dependence in remission , outpatient CDI practice looks for indicators that reflect a documented history of dependence plus evidence the patient is actively maintaining sobriety or being followed for recovery status. Attendance at AA meetings together with a documented history of excessive alcohol use is a strong, direct indicator of recovery efforts and ongoing monitoring of a prior substance use disorder. This combination supports clarifying whether the provider intends to diagnose alcohol dependence in remission (versus current dependence, use without dependence, or no current disorder). By contrast, cirrhosis and elevated liver enzymes (option A) can be caused by many etiologies and do not, by themselves, establish dependence or remission status. Nausea, vomiting, and abdominal distention (option D) are nonspecific and may suggest acute illness or liver disease but are not specific to remission. Occasional social drinking with recreational drug use (option C) suggests current substance use and would not support “in remission” without additional documentation. Therefore, option B best supports a remission-related query.

In ambulatory CDI, “risk adjustment impact” means the clarification can change whether an HCC-relevant condition is captured accurately (or captured at all) based on ICD-10-CM reporting rules. Here, “DM2 with peripheral neuropathy with diabetic ulcer” already establishes diabetes with complications , so querying option B adds little—complications are already documented. “Nicotine dependence” is not supported because the patient stopped smoking two years ago; at most, this supports a history of nicotine dependence, which generally does not drive HCC risk scoring. “Morbid obesity” may be clinically relevant (BMI 43 supports it), but obesity typically does not produce meaningful CMS-HCC risk adjustment impact compared with other chronic categories. The diabetic ulcer does matter: correct reporting requires an additional L97.- code that depends on ulcer severity/depth (skin breakdown, fat layer exposed, necrosis of muscle/bone). Clarifying depth supports accurate ulcer severity coding and can affect HCC capture/validation for chronic ulcer burden.

The documentation shows a patient with advanced COPD (GOLD stage 3) who now requires an increase in home oxygen to 3 liters, along with escalation of respiratory therapies (home nebulizers and systemic steroids). In outpatient CDI, an increased or ongoing home oxygen requirement is a strong clinical indicator that the provider may be managing chronic respiratory failure (or chronic hypoxemic respiratory failure), which is more clinically meaningful than simply documenting oxygen use as a status. “Oxygen dependence” is a status code and does not fully describe the underlying physiologic impairment driving the need for oxygen; chronic respiratory failure captures the severity and ongoing nature of the condition and better reflects risk, complexity, and medical necessity for durable oxygen therapy. Querying for pneumonia organism specificity is not as relevant in a follow-up visit unless pneumonia is still being actively treated and the organism is known. Querying COPD acuity (e.g., exacerbation) may be appropriate, but the most significant clarification prompted by increased home O2 is whether chronic respiratory failure is present and being managed.

Under the Medicare Outpatient Prospective Payment System (OPPS), hospital outpatient services are paid based on Ambulatory Payment Classifications (APCs). APCs are the mechanism that groups clinically similar services and procedures—typically identified through CPT/HCPCS reporting—into payment categories with established relative resource costs. CPT codes identify what service was performed, but CPT itself is not the OPPS payment grouping methodology; OPPS takes the coded line items and maps many of them into APC groupings (with packaging rules, status indicators, and modifier impacts) to determine the payment rate. DRGs are used for inpatient prospective payment and do not apply to OPPS outpatient claims in the same way. The Physician Fee Schedule applies to professional services (physician/clinician billing) rather than the hospital facility component paid under OPPS. From an outpatient CDI lens, accurate, specific documentation supports correct CPT/HCPCS selection, modifier use, units, and medical necessity linkages—ensuring services map to the correct APC and are not inappropriately bundled, denied, or downcoded during review. This protects payment accuracy and compliance by aligning the clinical story with the reported outpatient services.

A prospective query is initiated early enough (before or during the visit workflow) so the provider can evaluate, assess, and document the condition in real time while the patient is present. This is a major provider benefit because it supports better clinical accuracy and completeness: the clinician can ask targeted questions, perform relevant exam elements, review results, and determine whether the condition is present, active, being monitored, or ruled out—then document the final clinical impression and plan. From an ACDIS outpatient CDI perspective, prospective querying improves efficiency and reduces retrospective “chart-chasing,” late addenda, and documentation gaps that occur when clarification is requested after the encounter is closed. Importantly, prospective queries must remain non-leading and cannot direct the provider to a particular diagnosis (eliminating option A). They also cannot “guarantee” risk-adjusted capture because the diagnosis must be clinically supported and addressed (eliminating option B). Defining the purpose of the encounter is driven by the clinical reason for visit, not by CDI (eliminating option D).

Copy-and-paste of an inpatient problem list into an outpatient note creates significant documentation integrity risks: outdated diagnoses may be carried forward, resolved conditions may appear active, and the note may not clearly show which problems were actually evaluated or managed during the current encounter. Outpatient CDI best practice is not to assume relevance (eliminating D) and not to reflexively query every listed diagnosis (B), which can be burdensome, non-targeted, and may lead to “query fatigue.” Likewise, blanket instruction to “not code” anything pasted (A) is not appropriate because some conditions may still be active and reportable if the provider documents assessment/management (e.g., monitoring, evaluation, addressing, or treatment). The most effective and sustainable action is provider education: explain why indiscriminate copy-forward threatens accuracy, compliance, medical necessity support, quality reporting, and risk adjustment validity; reinforce documenting current status and care provided for each active condition; and encourage updating the problem list and assessment to reflect what is truly addressed at the visit. Targeted queries can still be used when specific contradictions or high-impact ambiguities are identified.

Under CMS-HCC methodology, risk adjustment is driven by ICD-10-CM diagnoses that map to HCC categories and are supported as active conditions addressed at the encounter. CKD stage 3 is a classic HCC-qualifying chronic condition because it represents ongoing kidney disease severity and expected resource use, and in this note it is actively assessed with labs reviewed and a nephrology referral. A chronic non-pressure foot ulcer is also typically HCC-qualifying when documented as ongoing and requiring management, which is supported here by home care/wound assessment planning. In contrast, “depression” (without specification such as major depressive disorder severity/status) commonly does not qualify for HCC in the way major depressive/bipolar categories do, making it less reliable as a risk-adjusting diagnosis. Likewise, “renal failure” is nonspecific and potentially conflicting with CKD stage 3; CDI best practice would be to clarify acuity/severity (acute kidney injury vs CKD stage vs ESRD) rather than assume “renal failure” as an HCC driver. Therefore, the validated HCC-qualifying pair is CKD 3 and chronic non-pressure ulcer.

In outpatient CDI and coding guidance, an “uncertain diagnosis” is identified by wording that indicates the provider has not confirmed the condition (e.g., possible, probable, suspected, rule out, question of, concern for). These terms reflect diagnostic consideration rather than an established diagnosis. Option A uses the phrase “concern for,” which is a classic uncertainty qualifier and signals the provider is considering streptococcal pneumonia but has not definitively diagnosed it. In contrast, options B and D describe active treatment “for streptococcal pneumonia,” which implies the provider is managing the condition as a working diagnosis; however, in outpatient coding, treatment alone does not automatically make a diagnosis confirmed if the documentation still reflects uncertainty—CDI would look for explicit provider confirmation. Option C (“evidence of”) generally suggests supportive findings and is commonly interpreted as stronger than “concern for,” though CDI would still assess whether the provider has clearly stated a confirmed diagnosis in the assessment/plan. Therefore, the clearest uncertain descriptor is “concern for.”

In outpatient risk adjustment, “disease interactions” refer to model coefficients that are triggered when certain clinically related conditions co-exist, reflecting higher expected resource use than either condition alone. In this case, the record already supports active malignancy care (colon cancer on chemotherapy) with newly documented metastasis, and the lab pattern (anemia, leukopenia, and severe thrombocytopenia) strongly suggests pancytopenia. The highest-yield query opportunity is to clarify whether the cytopenias represent chemotherapy-induced pancytopenia (or another specified etiology) because a confirmed, well-specified hematologic complication in the context of active cancer treatment is the type of combination that commonly drives interaction effects in risk models (cancer plus significant systemic complication/manifestation). Options A and B describe clinical context but do not, by themselves, establish an interaction-ready, separately reportable complication. Option C is unrelated to the presented lab-driven severity signal. Querying and documenting chemotherapy-induced pancytopenia supports accurate capture of severity and the interaction impact.

Medicaid risk adjustment models generally calculate risk using two major categories of inputs: demographics and diagnosis data . Demographic factors commonly include gender and indicators tied to Medicaid 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 input for 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 is not itself a standard risk-score driver unless 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 gender are the most clearly valid factors that impact the beneficiary’s risk score.

The documentation explicitly links the conditions by stating “Type 2 Diabetes with bilateral peripheral arteriosclerotic disease of LE,” which supports a diabetic circulatory manifestation rather than “diabetes without complications.” In outpatient CDI chart review, the word “with” and clear provider linkage allow coding of diabetes “with peripheral angiopathy” (a diabetes complication category) when peripheral arterial/arteriosclerotic disease is documented as associated. In addition, best practice is to code both the diabetes complication category and the specific manifestation when supported, because the manifestation (atherosclerosis of the lower extremities, bilateral) further describes the clinical condition being evaluated. Hypertension is also evaluated and managed (“well controlled on Lopressor”), meeting outpatient reporting expectations for an active condition addressed during the encounter. Option D is incorrect because it double-counts the same concept—peripheral angiopathy already represents a circulatory complication, so adding a separate “diabetes with circulatory complication” statement is redundant rather than additive. Therefore, the correct coding set includes diabetes with peripheral angiopathy, the bilateral lower-extremity atherosclerosis manifestation, and hypertension.

In the outpatient setting, uncertain diagnoses described with terms such as “likely,” “probable,” “suspected,” or “rule out” generally are not reported as established conditions for coding purposes. Instead, the encounter is coded to the confirmed signs and symptoms documented and evaluated at that visit. Here, the provider’s assessment is “likely UTI,” with urine culture results still pending, so a definitive UTI diagnosis is not yet confirmed within the scenario. Likewise, the organism (E. coli) cannot be coded because it is only suspected and not confirmed until culture results are finalized. Outpatient CDI emphasizes aligning reportable diagnoses to what is clearly supported as present and addressed during the visit. The note explicitly identifies pain, urinary frequency, and fever—symptoms that drove evaluation and treatment (antipyretics and antibiotic initiation). Between the answer choices, “abdominal pain, fever, and urinary frequency” best represents the reportable conditions based on documented, evaluated symptoms without coding an uncertain infection diagnosis or an unconfirmed causative organism.

In obstetric and postpartum coding, the most important clarification is the type/timing of hypertension because ICD-10-CM has distinct categories for chronic (pre-existing) hypertension, gestational hypertension, and hypertensive disorders that persist into or present during the postpartum period. At 6 weeks postpartum with elevated readings (including a systolic of 160) and headache, the documentation “hypertension” is not specific enough to determine whether this represents chronic hypertension that predates pregnancy, gestational hypertension that has not resolved, or another pregnancy-related hypertensive disorder requiring different obstetric coding and follow-up. ACDIS outpatient CDI guidance prioritizes queries that resolve coding-impactful ambiguity using clinically supported options without leading the provider. While postpartum preeclampsia could be a clinical consideration, the note does not provide key supporting elements (e.g., proteinuria or other definitive severe-feature criteria), so jumping directly to preeclampsia/eclampsia is less appropriate than clarifying onset and relationship to pregnancy. Linking hypertension to smoking is not a standard required linkage for diagnosis coding, and “hypertensive crisis” is not supported by the documentation provided.

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 low agree rate indicates 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 reflects query 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.

The clinical indicators strongly support alcohol dependence , not merely alcohol “use” or “abuse.” The patient reports heavy, compulsive intake (early-morning drinking and at least a pint daily), and the provider explicitly documents that she “continues to be dependent on alcohol” and discusses treatment options—this aligns with a dependence-level disorder being addressed. Hypertension is also supported because the BP is elevated (165/89) and the provider documents management activity (medications and diet counseling), meeting encounter relevance/reportability expectations. Diabetes is listed among chronic conditions, but the scenario provides no indicators of complications (no neuropathy, CKD, ulcers, retinopathy, etc.), so the supported choice is DM type 2 without complications rather than “with complications.” Although COPD is listed in the “including” statement, no COPD-specific assessment/monitoring/treatment is described in the indicators provided, so the best-supported grouped option focuses on the conditions with clear supporting indicators and management in the note: DM2 without complications, HTN, and alcohol dependence.

Beta-blockers are commonly used in the management of coronary artery disease (CAD) because they lower heart rate, decrease myocardial contractility, and reduce oxygen demand—key goals in treating stable angina and in secondary prevention after myocardial infarction. In outpatient chart review, ACDIS-focused clinical documentation education emphasizes linking the medication to the condition being managed (e.g., “CAD with angina—on metoprolol for symptom control” or “history of MI—on beta-blocker for secondary prevention”) to support accurate diagnosis reporting and demonstrate ongoing assessment and treatment. By contrast, third-degree (complete) heart block and sinus bradycardia are conditions where beta-blockers are typically avoided or used only with extreme caution because they can worsen conduction delay and slow the heart rate further. Cardiomyopathy can sometimes be treated with certain evidence-based beta-blockers when the clinical context is systolic heart failure, but the option most broadly and reliably associated with beta-blocker treatment in standard outpatient practice and documentation is CAD.

RAF (Risk Adjustment Factor) is best explained to providers as a population-health and resource-planning tool, not a visit-level payment lever. In outpatient risk adjustment models, diagnoses and demographics are used to estimate the patient’s overall disease burden and the expected cost/resources required to meet that patient’s healthcare needs. When documentation accurately reflects active conditions and their specificity, the patient’s risk profile is represented more realistically. That improves care in practical ways: it supports appropriate allocation of care management services (e.g., nurse navigators, chronic care programs), helps organizations anticipate medication, testing, specialist, and follow-up needs, and improves fairness of performance benchmarking by comparing outcomes and costs against similarly complex patients. Option A is overly simplistic because RAF does not directly determine an individual provider’s reimbursement for a given encounter; it influences broader payment and benchmarking methodologies tied to attributed populations. Option C is not what RAF measures, and option D confuses RAF with medical necessity, which is based on clinical documentation and coverage rules, not a risk score.

In outpatient and physician-office reporting, the diagnosis that best describes the main reason for the visit is reported as the first-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 uses first-listed to 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.

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—especially persistent 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.

A yes/no query format is considered compliant when it is used to resolve a clear documentation conflict and the provider is being asked to confirm which statement accurately reflects the patient’s condition for that encounter. In these situations, the intent is not to introduce a new diagnosis or steer the provider toward a particular coded outcome, but to reconcile inconsistent information already present in the record (e.g., one clinician documents a condition and another documents the opposite, or different notes describe different statuses). A focused yes/no confirmation can be appropriate because the clinical question is essentially binary: which interpretation is correct. By contrast, obtaining a new diagnosis generally requires an open-ended or multiple-choice format with balanced options (including “unable to determine”) and strong encounter-specific indicators to avoid leading. Likewise, organism specification and acuity clarification often involve more than two clinically valid possibilities (different organisms, acute vs chronic vs acute-on-chronic, etc.), making yes/no overly restrictive and potentially leading. Therefore, resolving conflicting documentation is the best fit for a compliant yes/no query.