ACDIS CCDS-O Exam Questions

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 of 7.0% clearly meets the threshold and supports diabetes. By comparison, a 2-hour OGTT value of 90 mg/dL is normal and does not support diabetes (diabetes is typically supported when the 2-hour value is 200 mg/dL). Hypoglycemia is 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. A fasting glucose of 100 mg/dL is at most borderline/prediabetes range and does not meet diagnostic criteria for diabetes (diabetes is supported at 126 mg/dL).

When documentation states ''metastatic uterine cancer,'' the most important missing element for complete, accurate outpatient coding is where the cancer has metastasized (the secondary site[s]). In ambulatory CDI, identifying secondary sites best clarifies the full scope of disease being monitored and treated because metastatic disease coding relies on documenting both the primary malignancy and the specific metastatic location(s) (e.g., lung, liver, bone, peritoneum, lymph nodes). This supports correct severity representation, risk capture, treatment intent, and medical necessity for ongoing chemotherapy follow-up. While tumor morphology can be clinically relevant, it is usually established earlier in the diagnostic pathway and does not, by itself, define current metastatic burden. Likewise, reviewing labs or MRI results may provide supportive indicators, but they do not replace provider documentation of the confirmed metastatic sites being managed. A compliant query focused on secondary sites prompts the provider to document the current metastatic disease status (active, responding, progressing) and specific locations, which most directly identifies the conditions under treatment.

The definition in option B is the official Uniform Hospital Discharge Data Set (UHDDS) definition used for inpatient coding: the principal diagnosis is the condition determined---after evaluation---to be chiefly responsible for the admission. It is not simply the first condition written, nor necessarily the ''worst'' or most severe condition; it is the reason for admission once the workup clarifies the clinical picture. CDI practice reinforces this because principal diagnosis selection drives DRG assignment, quality metrics, and reporting, and errors often stem from confusing presenting symptoms with the final established diagnosis. Although outpatient settings use different concepts (e.g., first-listed diagnosis for the encounter), ACDIS education frequently contrasts inpatient ''principal diagnosis'' with outpatient ''first-listed'' to prevent documentation and coding misalignment. Clinicians should document the definitive condition when known (and link symptoms to that condition), and clearly describe diagnostic uncertainty when not yet established. This clarity supports compliant coding, accurate benchmarking, and defensible medical necessity across settings.

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.

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.