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

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.

The Medicare Shared Savings Program (MSSP) is designed to move reimbursement away from pure volume-based payment and toward value by rewarding organizations that reduce the total cost of care for an assigned Medicare population while meeting defined quality performance requirements. In MSSP, eligible provider groups participate as Accountable Care Organizations (ACOs) and are compared against a financial benchmark. If the ACO’s actual spending comes in below the benchmark and quality standards are achieved, the ACO can earn a portion of the savings—hence “shared savings.” Outpatient CDI supports MSSP success by ensuring documentation accurately reflects patients’ true disease burden (supporting appropriate risk adjustment for benchmarking), and that conditions addressed during visits are clearly documented as evaluated/managed to support reliable coding and quality measurement. While improving transitions of care may be a strategy that helps achieve savings and quality goals, it is not the core purpose of the program itself. Likewise, MSSP is not intended to increase fee schedule payments or simply optimize risk scores; the primary aim is participating in value-based care and sharing in savings when performance supports it.

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.

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.

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.

Metoprolol is a beta-blocker commonly used in atrial fibrillation to achieve ventricularrate control, reduce symptoms (palpitations, dyspnea), and improve hemodynamic stability, especially when the rhythm is persistent or recurrent. From an outpatient CDI chart-review perspective, therapy-to-diagnosis consistency is a key clinical indicator that supports clarifying the condition being treated and ensuring it is documented as assessed/managed at the encounter. The other options are clinically mismatched: “Ensure” is a nutritional supplement typically used for inadequate intake or weight loss and would not be recommended for morbid obesity; rivaroxaban (Xarelto) is an anticoagulant and would be inappropriate in the setting of hematemesis (active GI bleeding) where anticoagulation generally increases risk and would typically be held or reassessed; tamoxifen is an endocrine therapy for hormone receptor–positive breast cancer risk/treatment and is not a standard therapy for chronic congestive heart failure. Therefore, metoprolol for atrial fibrillation is the most appropriate and likely recommendation among the choices.

In outpatient CDI and ICD-10-CM coding guidance emphasized in ACDIS education, “NEC” (Not Elsewhere Classified) aligns with the “other specified” options in the code set and is used when the provider’s documentation is clinically specific, but the classification system does not offer a unique code for that exact specificity. In other words, the record contains enough detail to describe a distinct type, cause, manifestation, or clinical variation of a condition, yet there is no more precise code available, so the “other specified” category appropriately captures that documented specificity. This is the opposite of “unspecified” (often associated with “NOS”), which is selected when the documentation is not detailed enough to choose a more specific code option. From a chart review perspective, NEC/other specified supports accurate reporting because it reflects that the clinician did document additional detail, and the coder is not defaulting to unspecified due to missing documentation—rather, the code set itself limits further granularity.

CDI staff do not alter the legal health record and should not “code it as is” when documentation is unclear, conflicting, or incomplete in a way that impacts accurate reporting. The compliant next step is to issue a provider query for clarification, ensuring the final record accurately reflects the provider’s clinical judgment. ACDIS-guided outpatient CDI emphasizes that queries are a quality and compliance tool: they reconcile discrepancies (e.g., conflicting diagnoses across notes, missing linkage between symptoms and conditions, unclear acuity such as “CHF” without type/status, or ambiguous infection documentation). The query should be supported by clinical indicators from the chart and should ask the provider to document the clarified diagnosis/status in the record (progress note, addendum, or appropriate attestation). Escalation to compliance is reserved for patterns of nonresponse, suspected integrity concerns, or systemic issues, not routine discrepancies. The objective is to achieve a complete, consistent clinical story that supports coding, risk adjustment, quality reporting, and medical necessity—through provider clarification, not CDI edits.

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 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 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.

The CMS-HCC risk adjustment methodology is designed to estimate an individual beneficiary’s expected healthcare resource use and cost relative to an average Medicare beneficiary. It does this by converting demographic factors (such as age/sex and certain eligibility variables) plus documented, coded chronic conditions into a Risk Adjustment Factor (RAF). That RAF is then used to forecast the likely cost of caring for that specific patient in the payment year and to adjust benchmarks/payments so plans and providers managing sicker patients are compared more fairly to those managing healthier patients. This is why outpatient CDI emphasizes accurate, specific documentation and annual recapture of active conditions that are monitored, evaluated, assessed/addressed, or treated—because those coded conditions drive the predicted cost profile. CMS-HCC is not a mortality prediction tool (eliminating B), nor is it intended to measure “group costs” as the primary target (C), even though aggregated risk scores can be used for population analytics. It also does not measure an individual physician’s cost of care provision (D); it measures patient-level expected cost burden.

In outpatient CDI, “pre-visit” or prospective preparation focuses on chronic, clinically significant conditions that are likely to remain active and that should be reassessed and documented with clear MEAT support (monitor, evaluate, assess/address, treat) during the upcoming encounter. Epilepsy, chronic heart failure, and Crohn’s disease are all long-term conditions that commonly require ongoing medication management, monitoring, and periodic reassessment, making them strong candidates for reminder/education to ensure the provider documents current status (controlled vs uncontrolled, exacerbation, complications, and treatment plan). This also supports accurate risk adjustment because chronic conditions with ongoing impact are the ones expected to be recaptured when addressed. In contrast, option C includes “family history,” which is not a current active condition for risk adjustment, and options D includes acute/self-limited problems (syncope episode, pharyngitis) that are less appropriate as pre-visit chronic-condition prompts. Option B mixes chronic disease with items that may be historical or encounter-specific (compression fracture timing/status), making it less consistently targetable than option A.

Under CMS-HCC risk adjustment (commonly applied to Medicare Advantage), qualifying diagnoses must come from acceptable encounter/claim sources and eligible provider types. Hospital-based outpatient services (including a hospital ambulatory clinic) are among the standard, acceptable settings where diagnoses documented, coded, and submitted on qualifying encounters may be used for risk adjustment—assuming they are supported, assessed/managed, and submitted per program requirements. In contrast, certain facility claim types do not typically contribute to CMS-HCC capture in the same way. Hospice care is generally treated as a carve-out/unique payment environment and is not relied upon as a routine source of risk-adjusting diagnosis capture for the member’s ongoing RAF. Renal dialysis centers (ESRD facilities) likewise operate under specialized payment constructs and are not the typical outpatient setting used to drive CMS-HCC diagnosis capture for risk adjustment in standard CDI workflows. Freestanding ambulatory surgical centers also frequently fall outside the usual risk-adjustment-eligible encounter sources emphasized in outpatient CDI programs. Therefore, the hospital ambulatory clinic is the correct setting among these choices.

In ICD-10-CM diabetes coding (as reinforced in outpatient CDI education), some diabetes manifestations are fully captured by a single diabetes “combination” code, while others require a diabetes complication codeplus an additional codeto identify the specific manifestation. Diabeticnephropathyand many forms of diabeticretinopathyare commonly represented by diabetes combination codes that already describe the manifestation with built-in specificity options (e.g., diabetes with nephropathy; diabetes with retinopathy with/without macular edema and severity).Osteomyelitis, however, is typically captured using a diabetes code such as “diabetes with other specified complication” (e.g., E11.69) to establish the linkage to diabetesandan additional code from the osteomyelitis category (e.g., M86.-) to specify the site, acuity, and type of osteomyelitis. From a chart review standpoint, CDI often queries to confirm the causal relationship (“due to diabetes”) and to ensure the osteomyelitis details (site, acute vs chronic) are documented so both codes can be assigned accurately and compliantly.

The strongest CDI query opportunity is clarifying whether the UTI iscatheter-associated. The patient has anindwelling Foley catheter, significant leukocytosis (WBC 20), apositive urine culture for E. coli, and is being treated with antibiotics for UTI—these indicators raise a clear question about theetiology of infectionand whether it is related to the urinary catheter. In outpatient CDI practice, linking the infection to a device (when clinically supported) improves documentation accuracy, supports correct code assignment, and has important quality and compliance implications because catheter-associated UTIs are captured differently than uncomplicated UTIs. By comparison, querying the “etiology of BPH” is not supported as an immediate gap (BPH is already stated), and the “etiology of low back pain” is less directly tied to the documented treatment focus (UTI management). “Leukocytosis” is a lab finding that is already objectively supported and often represents a symptom/abnormal result rather than the principal clarification needed. Therefore, confirming whether the UTI is related to the Foley catheter is the best, most clinically anchored query.

Nightly reliance on CPAP in a morbidly obese patient most strongly points to sleep-disordered breathing, and in the context of severe obesity (BMI 45), it raises concern forobesity hypoventilation syndrome (OHS), which is characterized byalveolar hypoventilation(chronic hypoventilation with hypercapnia) that is not fully explained by other pulmonary or neuromuscular causes. While CPAP is commonly prescribed for obstructive sleep apnea, severe obesity increases the likelihood of associated hypoventilation physiology; in outpatient CDI review, this becomes a documentation opportunity to ensure the provider specifies whether the patient has OSA alone versus OSA with OHS/alveolar hypoventilation, because the latter reflects higher clinical complexity and requires clear monitoring/management (e.g., ABGs or bicarbonate trends, symptoms of hypoventilation, adherence, need for BiPAP). Heart failure and pulmonary edema are not implied by CPAP use, and essential hypertension is common in obesity but not the condition most specifically linked to CPAP dependence. Therefore, alveolar hypoventilation is the best supported answer.

In outpatient CDI, the foundational aim is documentation integrity—making sure the medical record clearly and consistently tells the clinical story: why the patient is being seen, what conditions are evaluated/managed, the current severity and associated risks, what was done (assessment and treatment), and how this supports medical necessity and accurate code assignment. While reimbursement can be affected, it is an outcome—not the purpose. ACDIS-aligned CDI education emphasizes completeness and specificity so the record reflects true acuity and complexity (e.g., chronic conditions with current status, complicating comorbidities, medication management, and risk/decision-making). This improves downstream quality reporting, risk adjustment accuracy, continuity of care, and compliance because coders must code what is documented, not what is presumed. Strong CDI reduces denials and audit exposure by ensuring diagnoses are clinically supported (MEAT—monitor, evaluate, assess/address, treat) and linked to the encounter’s work. In short, CDI exists to ensure the record accurately represents the patient’s condition and the care delivered, enabling correct coding, quality measurement, and appropriate payment.

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.

A compliant prospective query is initiated before the next encounter so the provider can clarify documentation during the upcoming visit, using clinically relevant indicators without directing a specific diagnosis. Option A does this appropriately: it references an existing CHF history and a supportive medication (Lasix), then asks the provider to confirm whether CHF is pertinent at the next visit and, if so, to specify type and acuity. This supports accurate outpatient reporting because heart failure coding requires specificity (systolic/diastolic/combined; acute/chronic/acute on chronic) and should reflect what is actually evaluated/managed at the encounter. Option B is retrospective and attempts to justify a prior test. Option C is leading because it asks the provider to “add” a diagnosis to a past note rather than clarify current clinical status. Option D is also retrospective and uses “please add CHF,” which is leading and can be perceived as prompting. Therefore, A best demonstrates a compliant prospective query.

Within the CMS-HCC model, only certain diagnoses map to HCC categories that contribute to the RAF score. Among the listed options,cachexiais 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 esophagusgenerally does not map to an HCC in CMS risk adjustment, and symptom-based diagnoses such assignificant weight losstypically do not trigger HCC capture.Anorexiain 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.

The CDI specialist shouldreview CKD staging criteria with the providerbecause assigning CKD based on asingle eGFR valuecan be clinically unreliable and may lead to inaccurate documentation and coding. Outpatient CDI guidance emphasizes that documentation must reflect a condition that isclinically 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 ispersistent, not a one-time lab that could be affected by hydration status, acute illness, medications, or transient physiologic changes. While an eGFR of52falls within the numeric range commonly associated withstage 3a, the key CDI issue is thefoundation 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.

Outpatient/provider coding relies on two major code sets: ICD-10-CM for diagnoses and CPT/HCPCS for professional services, procedures, and supplies. Because of that, outpatient coding authority is anchored not only in the ICD-10-CM Official Guidelines and AHA Coding Clinic guidance for diagnosis reporting, but also in the authoritative guidance that clarifies CPT/HCPCS reporting. ACDIS outpatient CDI education stresses that CDI specialists must understand both sides: the diagnosis coding rules (ICD-10-CM) and the procedural/service reporting rules (CPT/HCPCS) that drive much of outpatient reimbursement. AMA’s CPT Assistant is a key interpretive authority for CPT coding guidance, while AHA’s Coding Clinic for HCPCS provides clarification on HCPCS Level II reporting. The other options focus on ICD-10-PCS guidelines and DRG tools, which are primarily inpatient facility concepts (PCS is inpatient procedure coding; DRGs are inpatient payment groupers). Therefore, the correct supplemental outpatient authority pair is AHA’s Coding Clinic for HCPCS and AMA’s CPT Assistant.

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.

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.

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.

Medicare Advantage (MA) payments are risk adjusted so CMS can predict expected healthcare costs for each enrollee in the upcoming payment year. The model used for this forecasting is the CMS-HCC (Hierarchical Condition Category) risk adjustment methodology. It converts demographic factors (such as age/sex and eligibility status) plus documented, coded diagnoses (ICD-10-CM codes that map to HCCs) into a Risk Adjustment Factor (RAF). CMS then uses the RAF to adjust capitation payments to MA plans to reflect the member’s anticipated resource needs. This is why outpatient CDI places heavy emphasis on accurate, specific capture and annual “recapture” of active chronic conditions that are monitored, evaluated, assessed/addressed, or treated during the encounter—because the prior year’s valid HCCs drive the next year’s predicted cost and payment. By contrast, APCs relate to OPPS facility outpatient payment, RVUs/RBRVS relate to physician fee schedule valuation, and GPCIs adjust payment geographically; none of those are the MA risk forecasting model.

The record contains conflicting documentation: the problem list includes both “type 2 diabetes without complications” and diabetes with complications (erectile dysfunction association), while the most recent clinic note indicates the provider addressed “DM2 with autonomic neuropathy,” which is clearly a diabetic complication. In outpatient CDI, the first priority is to resolve internal inconsistency so coding accurately reflects the patient’s current clinical status and what was evaluated/managed at the encounter. A query should therefore focus on whether the patient’s diabetes iswith complications(and which complications are active/being addressed) versus trulywithout complications, because “without complications” is generally not appropriate when neuropathy/other manifestations are present and being managed. CDI staff also should not unilaterally remove items from the provider-maintained problem list, and asking the patient is not a reliable documentation/coding source for establishing diagnoses. Once the provider clarifies diabetes complication status, a follow-up clarification can address specific linkages (e.g., erectile dysfunction due to diabetes) if needed for correct code assignment

The documented indicators strongly support two clarification needs that affect accurate outpatient reporting. First,morbid obesityis supported by an objectiveBMI of 46, and outpatient CDI practice emphasizes ensuring obesity class is clearly documented as a diagnosis (not only implied by BMI) and that it is clinically relevant to care planning and risk (e.g., contributes to thrombotic risk, impacts treatment options). Second, the Doppler “indicates DVT,” but the record also notes ahistory of DVT, creating ambiguity aboutstatus—is this anacute new/recurrent DVT, achronic/residual thrombosis, or a prior condition now re-identified? Clarifying acuity/status is essential because it changes code selection and clinical severity representation and supports medical necessity for management decisions, especially given “contraindications to anticoagulation.” Hypertensive urgency is not supported (BP 142/88 without crisis features), and “hypercoagulability” is not established by the provided indicators. Therefore, querying for morbid obesity and DVT status is most appropriate.

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.

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.

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.

In outpatient CDI, diagnoses reported for an encounter must be supported as current and clinically relevant to that visit (evaluated, monitored, assessed, treated, or otherwise affecting care). The note documents ahistoryof sick sinus syndrome with pacemaker placement in 2016 and indicates the current rhythm ispaced. The most clearly reportable, present condition is thepresence of a cardiac pacemaker, which is a status that can affect clinical decision-making (e.g., interpretation of rhythm findings, medication choices, procedures, and future cardiac evaluation) and is appropriate to code when documented. However, the documentation does not show that sick sinus syndrome itself was actively assessed or managed during this visit; it is referenced as a past condition leading to the device. Because outpatient coding does not assume an active diagnosis solely from historical mention, the best action is to capture thepacemaker statuscode only. Retrospective amendment requests or rebilling steps are not the first-line CDI action when the documentation does not support active management of the underlying arrhythmia.

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.

In outpatient CDI,MEATis a commonly taught framework used to determine whether a condition is sufficiently supported asreportablefor a specific encounter. MEAT stands forMonitor, Evaluate, Assess/Address, and Treat. The concept is that diagnoses should not simply be copied forward on a problem list; they should be tied to provider work and clinical relevance during the visit. “Monitor” includes reviewing status, trends, or test results related to the condition. “Evaluate” includes ordering or interpreting studies, considering disease progression, or documenting response to therapy. “Assess/Address” includes documenting stability, exacerbation, or risk and making a plan (education, counseling, referrals). “Treat” includes medications, procedures, or other therapeutic interventions. Using MEAT helps CDI staff educate providers to document thecurrent statusand management of chronic diseases, supports accurate coding and risk adjustment, and reduces denials by showing medical necessity. OPPS, MACRA, and RADV are important regulatory/payment terms, but they are not the standard acronym used to assess encounter-level reportability.

In CMS-HCC risk adjustment, RAF impact comes from reporting qualifying chronic diseases (HCCs), not from nonspecific symptom-only documentation. “Angina pectoris, unspecified” is frequently a symptom-level statement and, by itself, often does not carry the same risk-adjustment weight as documenting and coding the underlying ischemic heart disease responsible for the angina (for example, coronary artery disease/atherosclerotic heart disease with angina). Ambulatory CDI practice emphasizes that when providers document only “angina,” coders may be limited to a symptom code, which can under-represent the patient’s true disease burden in the HCC model. This makes angina an excellent target for provider education: clarify whether the angina is due to CAD, whether CAD is present and being managed, and whether there are related manifestations (e.g., unstable angina, prior MI history, status post CABG/stent) that support more complete, clinically accurate reporting. By improving documentation linkage from symptom (angina) to the definitive chronic condition (CAD with angina), the provider can more reliably capture an HCC-relevant diagnosis and positively influence RAF accuracy.

Outpatient CDI follow-up must balance responsiveness with confidentiality and professional standards. The most compliant approach is to communicate query-related information in a setting that protects protected health information and minimizes the risk of incidental disclosure. Discussing the query in a private room with the door closed supports timely clarification while maintaining privacy, avoiding conversations that could be overheard by patients, visitors, or staff who are not involved in the patient’s care. Catching the provider in the hallway is faster but increases privacy risk because clinical details can be overheard, and it may also distract the provider in a high-traffic environment. Leaving a sticky note on the next patient’s chart is inappropriate because it can be seen by others, may be misplaced, and can create compliance and medico-legal concerns (including mixing patients or leaving PHI unsecured). Waiting for the next scheduled meeting may be compliant but does not support a quick response, potentially delaying coding completion and data integrity. Therefore, a private discussion is both the quickest and most compliant option.

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).

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.