CCDS Sample Questions Answers

When all four Hospital VBP domains are scored, each domain contributes 25% of the hospital's Total Performance Score.

For FY 2026, the four domains are Clinical Outcomes, Person and Community Engagement, Safety, and Efficiency and Cost Reduction. CMS's Provider Data Catalog confirms that each contributes one-quarter of the Total Performance Score under the standard four-domain configuration.

The Clinical Outcomes domain includes mortality and complication measures. Person and Community Engagement incorporates HCAHPS patient-experience dimensions. The Safety domain contains healthcare-associated infection and safety-related measures, while Efficiency and Cost Reduction incorporates Medicare spending measures.

If a hospital receives valid scores in only three domains, CMS proportionately reweights the scored domains rather than simply assigning zero to the missing domain.

For CCDS practice, understanding these domains helps explain why accurate documentation influences more than MS-DRG reimbursement. Clinical documentation can affect severity adjustment, complications analysis, mortality calculations, and the reliability of administrative data used in performance measurement.

CCDS Reference Topics: Hospital VBP; Total Performance Score; quality domains; risk adjustment; hospital performance.

=========

ICD-10-CM generally presumes a causal relationship between hypertension and qualifying heart disease, including heart failure, when both are documented and the provider has not stated that they are unrelated.

The appropriate hypertensive heart-disease code is assigned together with an additional I50.- code identifying the specific heart-failure type and acuity.

The presumption is not limited to systolic heart failure. Diastolic and combined heart-failure diagnoses are included when they meet the applicable classification rules.

Therefore, a query solely asking the physician to state that hypertension caused the heart failure is generally unnecessary when both conditions are documented and no contradictory statement exists.

CDI should nevertheless query if the heart-failure type or acuity is unclear, documentation conflicts, or the provider explicitly indicates another relationship that affects classification.

Understanding presumed relationships is important because unnecessary queries consume physician time and create avoidable administrative work. CDI specialists must distinguish clinical relationships that require explicit provider linkage from those supplied by ICD-10-CM conventions.

CCDS Reference Topics: Hypertensive heart disease; heart failure; presumed causal relationship; coding conventions; query reduction.

=========

Severe intellectual disability is recognized ICD-10-CM terminology and maps to F72, Severe intellectual disabilities. The other phrases are not equivalent standardized ICD-10-CM diagnostic terminology.

This distinction is highly relevant to CDI. Terms used conversationally in the clinical record do not necessarily provide sufficient specificity or map cleanly to reportable ICD-10-CM diagnoses. When a patient's cognitive or developmental condition affects treatment, monitoring, self-management, nursing requirements, or the complexity of care, the CDI specialist should seek clinically appropriate provider documentation using recognized diagnostic terminology.

For FY 2026 MS-DRG logic, CMS identifies F72 as a CC, meaning it can qualify as a complication/comorbidity when it meets secondary-diagnosis reporting requirements. That does not mean the CDI specialist should query merely for reimbursement impact. The query must be clinically justified by the record and should allow the provider to determine the correct diagnosis.

“Severe mental challenge,” “acute mental incapacity,” and “acute intellectual disability” do not represent the same codable disease classification.

CCDS Reference Topics: Medical terminology; mental/behavioral and neurodevelopmental disorders; CC recognition; clinically supported query opportunities.

=========

A condition can be assigned present-on-admission status even when the definitive diagnosis is not made until later in the hospitalization. POA refers to whether the condition was present at the time the order for inpatient admission occurred, not the calendar date on which diagnostic confirmation became available.

This distinction is particularly relevant for infections, malignancies, fractures, acute vascular events, and other conditions whose definitive identification may require cultures, pathology, imaging, or additional diagnostic testing.

Therefore, a blood culture finalized on hospital day 3 does not automatically make the infection hospital acquired. The clinical record and provider documentation must establish whether the disease process was present at admission.

POA assignment applies to applicable principal and secondary diagnoses, not only the principal diagnosis. CDI specialists should recognize unclear timing as a potential clarification opportunity because POA status can affect CMS Hospital-Acquired Condition payment logic and quality reporting.

The CCDS content outline expressly includes the basics of POA assignment and its impact on payment, as well as identification of CMS HACs.

CCDS Reference Topics: Present on admission; diagnosis timing; HACs; inpatient coding; quality reporting.

=========

The most meaningful indicator is an increased volume of appropriately supported cases grouping to respiratory infection DRGs. The stated purpose of the pilot is not merely to obtain more physician responses; it is specifically to improve documentation of the type or etiology of pneumonia.

When providers document clinically supported pneumonia specificity—for example, an identified bacterial etiology or another qualifying respiratory infection—the coded case may move from a less specific/simple pneumonia grouping into a respiratory infections and inflammations DRG family, depending on the final diagnoses and grouper logic. A trend toward the expected DRG distribution can therefore demonstrate that the form is accomplishing its documentation objective.

Provider response and agreement rates are valuable CDI process metrics, but neither proves that useful specificity was obtained. A physician could respond to every query without adding meaningful diagnostic detail. Likewise, an increase in simple pneumonia DRGs would suggest that the intended specificity is not being captured effectively.

A robust CDI analysis should also verify that any DRG shift reflects clinically valid documentation rather than query pressure or reimbursement-oriented behavior.

CCDS Reference Topics: CDI metrics; query effectiveness; pneumonia specificity; MS-DRG trend analysis.

=========

This scenario requires a clinical validation query. The diagnosis of respiratory failure is documented, but the remainder of the record lacks clinical evidence supporting it. CDI should not automatically accept the diagnosis solely because it appears in a progress note, nor should the specialist unilaterally remove or invalidate the provider's diagnosis.

The appropriate process is to present relevant patient-specific clinical information objectively and ask the responsible provider to clarify whether respiratory failure remains clinically appropriate. A compliant validation query should permit the provider to confirm the diagnosis, document another condition, indicate that it was ruled out, or provide another clinically appropriate response.

Looking only for CPAP documentation is inadequate because CPAP can be used for multiple conditions and its presence or absence does not independently determine whether respiratory failure exists. Similarly, simply refusing to code the diagnosis without seeking clarification bypasses the provider's clinical judgment and the organization's validation process.

The 2026 ACDIS/AHIMA query guidance is now the current foundational standard and supersedes earlier versions of the practice brief.

CCDS Reference Topics: Clinical validation; compliant querying; unsupported diagnoses; documentation integrity.

=========

The documentation does not clearly establish the definitive condition chiefly responsible for the inpatient admission. The patient has chest pain, borderline troponin elevation, and a history of GERD, while the physician describes the symptoms only as “likely GI in origin.” The appropriate CDI action is therefore to clarify the condition responsible for the admission rather than independently select GERD or myocardial infarction.

A history of GERD does not establish that GERD caused the present chest pain. Likewise, borderline troponin elevation alone does not establish an AMI, so a query that directs the provider toward AMI would be inappropriate without stronger clinical support.

For inpatient coding, uncertain diagnoses documented at discharge using terms such as “probable,” “suspected,” or “likely” may be coded as though established. However, the phrase “GI in origin” still fails to identify a specific gastrointestinal disease responsible for the admission. The CDI specialist's purpose is to obtain clinically meaningful diagnostic clarification rather than infer a diagnosis from treatment such as omeprazole.

A compliant query should include the relevant symptoms, diagnostic findings, treatment, and supported alternatives without indicating financial consequences.

CCDS Reference Topics: Principal diagnosis clarification; ambiguous documentation; compliant querying; clinical indicators.

=========

The fundamental objective of clinical documentation integrity is to ensure that the health record accurately represents the patient's clinical condition, including severity of illness, complexity, acuity, diagnoses, treatments, and outcomes. Reimbursement is an important downstream consequence of documentation and coding, but maximizing reimbursement is not the primary professional objective of CDI.

The ACDIS CCDS framework describes the CDI specialist as applying clinical knowledge to determine how documentation translates into coded data and educating providers so the record appropriately reflects severity, complexity, and acuity. This distinction is critical from an ethics and compliance perspective. A CDI program must pursue documentation accuracy whether clarification raises, lowers, or leaves reimbursement unchanged.

Reducing HACs is principally a clinical-quality and patient-safety function. CDI can improve the accuracy with which HACs are identified and reported, but it does not directly prevent those conditions. Similarly, improved provider communication is an important mechanism used by CDI professionals, but it is a means toward accurate documentation rather than the primary endpoint.

Therefore, A most accurately captures the broad clinical, coding, quality, and compliance purpose of CDI.

CCDS Reference Topics: Professionalism, ethics, and compliance; Medical record documentation; goals of CDI beyond reimbursement.

=========

The strongest educational approach is targeted specialty-specific education using the surgeons' own documentation trends and realistic clinical examples. This addresses the recurring documentation problem while remaining clinically relevant to the audience.

Orthopedic surgeons do not need to become coding specialists. Education should instead explain which clinical distinctions matter—for example, whether anemia represents expected postoperative change, acute blood loss anemia, chronic anemia, or another diagnosis—and why accurate terminology improves the medical record.

Providing a long code list is unlikely to improve physician documentation behavior. Instructing surgeons to document acute blood loss anemia whenever hemoglobin decreases would be clinically inappropriate and could produce unsupported diagnoses. A postoperative hemoglobin decline may reflect hemodilution, expected surgical blood loss, chronic anemia, or other factors.

Stopping queries would leave meaningful ambiguities unresolved.

ACDIS/AHIMA query guidance emphasizes documentation accuracy and provider independence rather than reimbursement-focused diagnosis selection.

Successful physician education should be concise, clinically oriented, supported by service-line data, and reinforced when subsequent query trends demonstrate persistent problems.

CCDS Reference Topics: Physician education; communication; postoperative anemia; query trends; provider engagement.

=========

The significant hemoglobin decline, documented surgical blood loss, and transfusion requirement create a strong clinical basis to clarify whether the patient has acute blood loss anemia or another form of postoperative anemia.

However, neither the hemoglobin value nor transfusion independently establishes the diagnosis. The provider must determine the clinical significance and etiology. A postoperative hemoglobin decline can reflect actual hemorrhage, hemodilution, preexisting anemia, expected procedural blood loss, or multiple factors.

A compliant query could present baseline and postoperative hemoglobin levels, estimated blood loss, transfusion, hemodynamic findings, and relevant treatment, then ask the provider to characterize the anemia.

The CDI specialist should also distinguish anemia from a postprocedural complication. Even if acute blood loss anemia is documented, that does not automatically mean a surgical complication occurred. Complication status may require separate provider clarification depending on the record.

Hemolytic anemia has a different pathophysiology involving red-cell destruction, while chronic iron deficiency cannot be inferred from the acute postoperative course.

CCDS Reference Topics: Acute blood loss anemia; postoperative documentation; transfusion; clinical indicators; complications of care.

=========

When severe sepsis is documented, coding requires the underlying systemic infection first, followed by the appropriate severe-sepsis code and additional code(s) for the acute organ dysfunction. Therefore, the sepsis code is sequenced first, followed by the severe-sepsis code and acute kidney injury.

The FY 2026 ICD-10-CM Official Guidelines state that severe sepsis requires at least two codes: one for the underlying systemic infection and another from subcategory R65.2-. Additional codes identify associated acute organ dysfunction. A code from R65.2- cannot serve as the principal diagnosis.

The UTI identifies the localized source but does not replace the systemic infection as principal diagnosis when sepsis is the condition chiefly responsible for admission. Likewise, the AKI is a manifestation of the severe systemic process and is not sequenced before the sepsis in this scenario.

For CDI specialists, the essential documentation element is the relationship between sepsis and the acute organ dysfunction. Organ dysfunction alone does not automatically permit severe-sepsis coding; provider documentation must establish the association when it is not inherent.

CCDS Reference Topics: Sepsis; severe sepsis; organ dysfunction; sequencing; principal diagnosis.

=========

CMS PSI 90, the Patient Safety and Adverse Events Composite, is one of the six measures used in the FY 2026 HAC Reduction Program.

CMS states that the program uses one claims-based patient-safety composite—PSI 90—plus five healthcare-associated infection measures: CLABSI, CAUTI, colon and abdominal hysterectomy surgical-site infection, MRSA bacteremia, and C. difficile infection.

Case mix index is an MS-DRG resource-intensity statistic and is not a HACRP quality measure. Query-response rate is an internal CDI performance metric. Patient-experience measures belong to other CMS quality frameworks, including Hospital VBP, rather than constituting a HACRP measure.

For FY 2026, hospitals with Total HAC Scores above the 75th percentile—effectively the worst-performing quartile—are subject to a 1% payment reduction under the program.

A CDI specialist should also distinguish HACRP from the separate HAC/POA payment provision. CMS explicitly identifies them as distinct programs, even though both involve hospital-acquired conditions.

CCDS Reference Topics: HACRP; PSI 90; healthcare-associated infections; patient safety; quality reimbursement.

=========

The CDI specialist should query the provider regarding the cause-and-effect relationship between the urinary catheter and the infection. The simultaneous presence of a catheter and UTI does not, by itself, establish a device-related complication for coding.

A positive culture, pyuria, and fever may support infection, but attribution to an indwelling catheter requires appropriate provider documentation when the classification does not independently establish the relationship.

The query should present relevant facts neutrally: catheter placement and duration, fever, urinary symptoms when present, urinalysis, culture findings, antibiotic treatment, and existing UTI documentation. Possible responses should allow the physician to identify catheter-associated UTI, UTI unrelated to the catheter, another diagnosis, or inability to determine.

Option A improperly infers causation. Option C goes too far in the opposite direction; although asymptomatic bacteriuria is common in catheterized patients, the provider has documented UTI and the patient has clinical findings that may support infection. Option D similarly equates a test result with a complication diagnosis.

This is a classic CCDS cause-and-effect clarification issue and demonstrates why device-related complications require careful documentation.

CCDS Reference Topics: CAUTI; device-related complications; cause-and-effect queries; clinical indicators; quality reporting.

=========

Direct verbal communication can be an effective and appropriate CDI technique, particularly when the responsible physician is available and the issue can be clarified efficiently. The interaction must remain professional, clinically focused, and compliant with the organization's process for documenting or retaining verbal queries.

ACDIS specifically identifies collaboration with providers, verbal discussion, written queries, and resolution of missing, unclear, or conflicting documentation as core inpatient CDI responsibilities. The CCDS blueprint also tests situations in which personal or verbal communication may be preferable to written communication.

Option C is inappropriate because the CDI specialist should not direct the physician toward a diagnosis based on MS-DRG impact. The discussion should present the clinical issue neutrally and allow the physician to exercise independent clinical judgment.

There is also no rule requiring all queries to be electronic. Query format and retention should follow compliant organizational policies and current ACDIS/AHIMA standards. Waiting until final billing can unnecessarily delay resolution and undermine the advantages of concurrent CDI review.

Effective CDI communication balances clinical precision, efficiency, collegiality, and auditability.

CCDS Reference Topics: Verbal queries; physician communication; concurrent CDI; nonleading clarification; query documentation.

=========

The fracture occurred after inpatient admission as the result of a hospital fall, placing it within CMS's Hospital-Acquired Condition category for Falls and Trauma when the applicable fracture code is included in the HAC code list. CMS's FY 2026 MS-DRG Definitions Manual continues to identify qualifying fracture codes within HAC 05.

The fracture must still be coded; therefore, option D is incorrect. Because it clearly developed after admission, it would not appropriately receive POA indicator “U,” which indicates insufficient documentation to determine whether the condition was present on admission.

For qualifying HAC diagnoses that are not POA, CMS payment logic prevents the hospital from receiving the higher MS-DRG payment that would otherwise result solely from the condition's CC/MCC status. Thus, option B expresses the intended payment effect.

This distinction is central to CDI practice: a hospital-acquired diagnosis does not disappear from the record or coding. It remains reportable for clinical and quality purposes, but certain qualifying HACs are treated differently in MS-DRG payment calculations.

CCDS Reference Topics: HACs; POA indicators; Falls and Trauma; MS-DRG payment adjustment.

=========

An observed-to-expected mortality ratio is calculated by dividing observed deaths by expected deaths. Here, 125 divided by 100 equals 1.25. Therefore, observed deaths are 25% higher than the number predicted by the risk-adjustment model.

A ratio of 1.0 indicates observed mortality equals expected mortality. A value below 1.0 indicates fewer observed deaths than predicted, while a value above 1.0 indicates more observed deaths than predicted.

The CDI implication is important. Expected mortality is influenced by the patient's documented disease burden and other variables used by the applicable risk-adjustment methodology. If clinically significant conditions are underdocumented, the coded record may fail to represent the patient's actual severity, potentially reducing calculated expected mortality.

However, CDI should never seek diagnoses solely to improve a mortality ratio. Each diagnosis must be clinically supported and accurately documented. A high ratio can reflect multiple factors—including clinical outcomes, case mix, documentation, coding, data quality, or model characteristics—and should trigger multidisciplinary analysis rather than automatic querying.

ACDIS includes mortality and severity/risk adjustment within CCDS competency expectations.

CCDS Reference Topics: O/E mortality; risk adjustment; severity documentation; quality outcomes.

=========

ICD-10-CM permits the NIH Stroke Scale score to be reported from documentation by an appropriate clinician other than the provider responsible for establishing the diagnosis. The underlying stroke diagnosis itself must be appropriately documented by the provider.

This is similar to other specified exceptions such as BMI, pressure-ulcer stage, coma scale values, and certain additional clinical elements for which qualified non-provider documentation may support code assignment.

The exception does not mean that a stroke nurse can independently establish cerebral infarction for coding. Rather, once the provider has documented the stroke, the nurse's formal NIHSS assessment can supply the standardized severity measurement.

This approach recognizes that specially trained clinical professionals routinely collect and document these structured measurements as part of patient care.

If multiple NIHSS values are documented, the applicable coding instructions and timing requirements should be followed rather than simply selecting the highest score because it produces a different code.

For CDI professionals, awareness of these non-provider documentation exceptions prevents unnecessary physician queries while ensuring that important severity information is not lost.

CCDS Reference Topics: NIH Stroke Scale; cerebral infarction; non-provider documentation; coding exceptions; stroke severity.

=========

When a patient is admitted with a localized infection and sepsis develops after admission, the localized infection is generally sequenced as the principal diagnosis, followed by the appropriate sepsis code.

The FY 2026 ICD-10-CM Official Guidelines explicitly distinguish this circumstance from cases in which both the localized infection and sepsis are present on admission. When sepsis develops only after admission, the localized infection responsible for the original hospitalization remains principal.

Therefore, pneumonia is sequenced first in this scenario.

If the patient subsequently develops acute organ dysfunction related to sepsis and the provider documents severe sepsis, additional severe-sepsis and organ-dysfunction codes are assigned as appropriate. The severe-sepsis code cannot itself serve as principal diagnosis.

This question demonstrates why CDI specialists must clarify timing. Simply seeing both “pneumonia” and “sepsis” in a discharge summary is insufficient to determine correct sequencing when the onset relationship is unclear.

The POA status of sepsis also becomes relevant because documentation indicates that it developed after inpatient admission.

CCDS Reference Topics: Sepsis; pneumonia; sequencing; timing; POA; principal diagnosis.

=========

The underlying systemic infection/sepsis code is sequenced as the principal diagnosis when sepsis or severe sepsis is present on admission and is the condition chiefly responsible for admission. Therefore, sepsis is the correct selection from the available choices.

The presence of organ failure means the patient may also meet the documentation requirements for severe sepsis when the acute organ dysfunction is explicitly associated with the sepsis. However, the severe-sepsis code from subcategory R65.2- cannot be assigned as the principal diagnosis. The FY 2026 ICD-10-CM Official Guidelines require the underlying systemic infection first, followed by R65.2- and codes for the associated acute organ dysfunction.

Osteomyelitis represents the localized infection source, but when the reason for admission is sepsis associated with that localized infection, the systemic infection is sequenced first under the sepsis guidelines. “Septicemia” should not be substituted for provider-documented sepsis.

The CDI specialist should also verify that the provider has clearly linked the organ failure to sepsis before severe-sepsis coding is applied.

CCDS Reference Topics: Sepsis sequencing; severe sepsis; principal diagnosis; localized infection.

=========

This is an appropriate clinical validation query because the provider has documented a diagnosis while the available clinical information appears inconsistent with that diagnosis.

The CDI specialist should not automatically accept every documented diagnosis when substantial contradictory clinical evidence exists. Conversely, CDI cannot independently delete the physician's diagnosis or replace the physician's clinical judgment.

The query should objectively identify the documented severe malnutrition and relevant contradictory findings—for example, stable weight, adequate nutritional intake, and absence of documented muscle or fat loss—and ask the provider to clarify whether severe malnutrition remains clinically appropriate, whether another nutritional condition better describes the patient, whether the diagnosis has been ruled out, or whether additional clinical reasoning supports it.

The query must remain neutral and should not mention the MCC status or potential reimbursement effect of severe malnutrition.

The August 2026 ACDIS/AHIMA compliant-query guidance supersedes previous editions and is the current foundational standard for compliant documentation clarification.

CCDS Reference Topics: Clinical validation; malnutrition; conflicting clinical indicators; compliant queries; documentation integrity.

=========

The CDI specialist should seek greater specificity regarding the pneumonia. The abbreviation HCAP historically referred to “healthcare-associated pneumonia,” but that terminology does not identify a causative organism or a sufficiently specific ICD-10-CM pneumonia diagnosis.

From a CDI perspective, the clinically relevant clarification may involve whether the pneumonia is bacterial, viral, aspiration-related, gram-negative, due to a specific organism, or otherwise characterized by the provider based on the available evidence. Culture results, aspiration risk, recent healthcare exposure, antibiotic selection, radiology, respiratory cultures, and infectious-disease documentation may provide appropriate clinical indicators for a neutral query.

Simply assigning a generic pneumonia working code fails to resolve the documentation deficiency. Asking only whether HCAP means “healthcare-acquired pneumonia” merely expands the abbreviation without producing useful etiologic specificity. “Complex pneumonia” is not an appropriate substitute diagnostic classification.

The CDI specialist must also avoid assuming that recent healthcare exposure establishes resistant-organism pneumonia. Contemporary clinical practice has moved away from treating HCAP as a standalone etiologic category because exposure alone does not reliably establish a particular pathogen.

CCDS Reference Topics: Pneumonia specificity; abbreviations; diagnostic clarification; compliant provider queries.

=========

Sepsis resulting from a postprocedural infection follows specialized sequencing rules. The code identifying the postprocedural infection or surgical-site infection is sequenced first when applicable, followed by the code for sepsis following a procedure and any additional codes required for the infectious organism or severe sepsis.

The FY 2026 Official Guidelines specifically state that for sepsis following a postprocedural wound or surgical-site infection, the appropriate postprocedural infection code is sequenced first. An additional code for sepsis following a procedure is then assigned. If severe sepsis exists, the appropriate R65.2- code and codes for acute organ dysfunction are additionally reported.

This differs from ordinary sepsis due to a localized infection, where the systemic infection is typically sequenced before the localized infection when sepsis is the reason for admission.

The cause-and-effect relationship is also essential. A wound infection merely occurring after surgery does not automatically establish a postprocedural complication. Here, the surgeon has explicitly documented that relationship, so the necessary clinical linkage is present.

CCDS Reference Topics: Postprocedural infection; sepsis; surgical-site infection; complication coding; sequencing.

=========

The remote peptic ulcer disease generally does not meet the definition of a reportable secondary diagnosis for this hospitalization because it does not affect current patient care.

For inpatient reporting, additional diagnoses include clinically significant conditions that coexist at admission or develop subsequently and affect care through factors such as clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care and monitoring.

Merely appearing in a past medical history or problem list does not make a condition reportable. The condition must satisfy applicable secondary-diagnosis criteria or another specific coding instruction.

This principle prevents the coded record from becoming populated with historical conditions having no relevance to the current hospitalization. It also underscores why CDI review should focus on diagnoses that meaningfully characterize the current episode of care.

Whether a diagnosis is classified as a CC or MCC is a separate MS-DRG concept. A diagnosis must first be appropriately reportable before its severity classification becomes relevant.

The CCDS outline specifically requires application of both principal- and secondary-diagnosis reporting principles.

CCDS Reference Topics: Additional diagnoses; clinically significant secondary conditions; historical diagnoses; resource utilization.

=========

CMS's Hospital-Acquired Condition payment framework specifically identifies Stage III and Stage IV pressure ulcers among the defined HAC categories when applicable conditions are not present on admission.

The distinction is important because not every pressure injury automatically triggers HAC payment treatment. Stage and POA status therefore require accurate documentation.

A hospital-acquired pressure ulcer remains reportable even when HAC payment provisions apply. CMS does not instruct hospitals to suppress or omit such conditions. Instead, defined HAC diagnoses that are not POA may lose the CC/MCC payment effect they otherwise would contribute to the MS-DRG, subject to applicable grouper rules.

The CDI specialist should ensure that wound location, laterality when relevant, stage, progression, and timing are accurately documented. Qualified wound-care nurse documentation may be used for pressure-ulcer staging under the ICD-10-CM non-provider documentation exception, while the diagnosis itself remains subject to provider-documentation requirements.

CDI professionals must also distinguish the HAC/POA MS-DRG payment provision from the separate HAC Reduction Program, which reduces applicable hospital payments by 1% for hospitals in the worst-performing quartile.

CCDS Reference Topics: HACs; pressure ulcers; POA; MS-DRG adjustment; wound documentation.

=========

The clinical picture presents an appropriate opportunity to clarify whether the patient has NSTEMI, unstable angina, or another acute coronary diagnosis.

A significant rise and/or fall in cardiac troponin consistent with acute myocardial injury, together with ischemic symptoms and ECG abnormalities, strongly raises concern for acute myocardial infarction. In contrast, unstable angina generally refers to ischemia without the biomarker evidence required for myocardial infarction.

Nevertheless, CDI should not make the diagnosis independently. Troponin elevations can occur in multiple conditions, including myocarditis, pulmonary embolism, sepsis, tachyarrhythmia, renal disease, and other forms of myocardial injury.

Therefore, the cardiologist should be asked to clarify the final diagnosis based on the complete clinical evaluation.

GERD, chronic stable angina, and old MI do not adequately reflect the acute findings described.

For CCDS preparation, cardiovascular questions frequently require distinguishing symptoms from established diagnoses and understanding the clinical indicators associated with NSTEMI, STEMI, type 2 MI, and other myocardial injury categories.

The ACDIS candidate handbook identifies anatomy, physiology, pharmacology, pathophysiology, and clinical record analysis as essential examination competencies.

CCDS Reference Topics: NSTEMI; acute coronary syndrome; troponin; myocardial ischemia; diagnostic clarification.

=========

BMI is one of the recognized ICD-10-CM non-provider documentation exceptions. A qualified clinician such as a registered dietitian may document the BMI value, while the associated diagnosis—such as overweight or obesity—must be appropriately documented by the responsible provider.

Therefore, the coder may use the documented BMI of 38.4 in conjunction with the provider's obesity diagnosis when reporting requirements are otherwise satisfied.

The BMI itself does not permit the coder or CDI specialist to independently diagnose obesity or determine obesity type. Clinical diagnosis remains the provider's responsibility.

This distinction prevents unnecessary physician queries merely to reproduce objective measurements that have already been reliably documented by another qualified clinician.

Comparable non-provider documentation exceptions include pressure-ulcer stage and certain standardized scales or clinical details under applicable ICD-10-CM guidance.

CDI specialists should know these exceptions because unnecessary queries increase provider burden and can delay coding without improving data quality. Conversely, they should not extend the exception beyond what ICD-10-CM permits.

CCDS Reference Topics: BMI; obesity; non-provider documentation; dietitian documentation; coding exceptions.

=========

The provider query response rate is calculated by dividing answered queries by total queries issued:

720 ÷ 800 × 100 = 90%.

Therefore, the correct answer is 90%.

The 540 responses agreeing with the clarification are relevant to a different measure: provider agreement rate. If agreement were calculated against answered queries, it would be 540 ÷ 720 = 75%.

These metrics should not be confused. Response rate measures whether providers participate in the clarification process, whereas agreement rate measures the proportion of responses that substantively agree with the diagnosis or clarification being evaluated.

A lower agreement rate is not necessarily evidence of poor CDI performance. Providers should remain free to disagree, document another supported diagnosis, rule out a condition, or indicate that the issue cannot be determined.

A CDI manager should trend response rate, agreement rate, response time, unanswered-query aging, retrospective-query percentage, and query type together rather than judging program success from a single number.

The 2026 ACDIS/AHIMA guidance reinforces provider independence as a fundamental aspect of a compliant query process.

CCDS Reference Topics: Query response rate; agreement rate; CDI metrics; provider engagement; program analysis.

A neutral multiple-choice query is appropriate when significant clinical indicators exist but no corresponding diagnosis has been documented. The query should present the relevant patient-specific facts and allow the provider to exercise independent clinical judgment among reasonable alternatives.

For example, depending on the complete record, options could include sepsis, localized infection without sepsis, bacteremia, another condition, or unable to determine. Each offered diagnosis must be clinically supported.

A yes/no query is generally inappropriate when it introduces a completely new diagnosis that has never appeared in the health record. Option B is overtly leading because it directs the provider to document sepsis rather than requesting clarification.

The 2026 ACDIS/AHIMA compliant-query guidance, published August 20, 2026, supersedes all previous versions and serves as the current foundational standard for CDI and coding query practice. It applies across inpatient, outpatient, ambulatory, and professional-fee settings.

The purpose of the query is documentation integrity—not obtaining an MCC, changing the MS-DRG, or achieving a particular quality result.

CCDS Reference Topics: Multiple-choice queries; missing diagnosis; nonleading queries; clinical indicators; compliance.

=========

Observed-to-expected mortality is calculated as:

Observed deaths ÷ Expected deaths

Therefore:

72 ÷ 90 = 0.80.

An O/E ratio of 0.80 means that observed mortality was lower than predicted by the applicable risk-adjustment model. Specifically, observed deaths were 20% below the expected number.

A ratio of 1.0 indicates observed mortality equals expected mortality. Values above 1.0 indicate more deaths than predicted, while values below 1.0 indicate fewer deaths than predicted.

CDI influences the integrity of mortality analysis because the documented disease burden contributes to clinical data used by many risk-adjustment methodologies. If significant comorbidities are incompletely documented, expected mortality may not fully reflect the patient's clinical risk.

However, mortality review must never become a mechanism for adding unsupported diagnoses. The objective is accurate clinical representation.

The CCDS candidate handbook explicitly identifies data analysis, reporting functions, medical-record review, and the impact of documentation on clinical and administrative outcomes as important CDI competencies.

CCDS Reference Topics: Mortality index; O/E ratio; risk adjustment; quality reporting; CDI analytics.

=========

The principal diagnosis is the condition established after study to be chiefly responsible for occasioning the patient's admission to the hospital for care. This is the UHDDS definition used in the ICD-10-CM Official Guidelines for inpatient principal-diagnosis selection.

“After study” is critical. The diagnosis initially suspected in the emergency department may change after diagnostic testing, consultation, treatment response, surgery, pathology, or other evaluation. The final principal diagnosis therefore may differ from the first diagnosis documented.

Relative weight does not determine principal diagnosis. A hospital cannot select a higher-paying condition merely because it produces a more favorable MS-DRG. Similarly, medication volume is not a principal-diagnosis criterion.

For CDI specialists, principal-diagnosis review requires understanding the circumstances surrounding admission, the diagnostic workup, final provider documentation, sequencing conventions, and any chapter-specific guidelines. When two conditions are documented and it is unclear which chiefly occasioned the admission, a provider query may be warranted.

The CCDS content outline specifically tests the principles and application of principal-diagnosis assignment.

CCDS Reference Topics: Principal diagnosis; UHDDS; inpatient sequencing; working MS-DRG.

=========

CMS publishes the complete MCC and CC lists as part of the FY 2026 IPPS Final Rule supporting tables. Specifically, the FY 2026 final-rule page identifies Table 6I as the Complete MCC List and Table 6J as the Complete CC List, along with additions, deletions, and the CC exclusion list.

These files are critical reference resources when assessing MS-DRG severity logic. Nevertheless, classification as an MCC or CC does not automatically mean that the diagnosis changes a particular case's MS-DRG. Principal-diagnosis exclusions, procedure logic, DRG structure, and the presence of another MCC can affect whether a diagnosis alters final assignment.

The Hospital Consumer Assessment survey relates to patient experience rather than diagnosis severity classification. The Physician Fee Schedule governs professional reimbursement and does not contain the inpatient MS-DRG MCC/CC classification system. National Coverage Determinations address Medicare coverage for particular services rather than MS-DRG severity categories.

CDI specialists should use the current CMS version applicable to the discharge date. CMS identifies MS-DRG Version 43.1 as effective April 1 through September 30, 2026.

CCDS Reference Topics: MCC; CC; CMS Definitions Manual; IPPS; MS-DRG severity.

=========

PACT stands for Post-Acute Care Transfer. The PACT policy is part of Medicare's IPPS transfer-payment framework and can modify the normal full MS-DRG payment when a qualifying inpatient stay ends with an early transfer or discharge to specified post-acute settings.

CMS applies transfer-payment methodology when applicable conditions are met, including circumstances involving selected discharges to skilled nursing facilities, inpatient rehabilitation facilities, long-term care hospitals, psychiatric facilities, and certain home-health arrangements. For home health, the timing and relationship of post-discharge care can be relevant.

The policy exists because a short acute-care hospitalization followed by transfer to another care setting may not involve the same hospital resource utilization as a conventional discharge completing the expected course of inpatient treatment. Accordingly, the transferring hospital may receive a calculated transfer payment rather than the unrestricted full MS-DRG amount.

For CDI professionals, PACT illustrates why accurate discharge disposition and documentation can affect reimbursement even when the principal diagnosis, procedures, CCs, and MCCs are correctly captured.

CCDS Reference Topics: IPPS; MS-DRG reimbursement; discharge disposition; transfer payment policy.

=========

When a patient is admitted specifically for treatment of a documented postoperative complication, the complication is generally sequenced as the principal diagnosis when it is established after study to be chiefly responsible for the admission.

In this scenario, the surgeon has explicitly documented the wound infection as a complication of the prior procedure, and treatment of that complication is the reason for the current hospitalization. The original surgical disease therefore does not automatically remain the principal diagnosis simply because it led to the earlier operation.

Fever and abdominal pain are clinical manifestations or symptoms and ordinarily are not sequenced ahead of the definitive postoperative infection once that condition has been established.

A critical CDI principle is that a temporal relationship alone is insufficient to classify a postoperative condition as a complication. The provider must establish the appropriate relationship when required by ICD-10-CM. Here, that documentation is already present, so a query simply asking whether the infection is postoperative would be unnecessary.

The principal-diagnosis decision should still account for all applicable complication-code sequencing instructions and circumstances of admission. The FY 2026 Official Guidelines emphasize both principal-diagnosis rules and requirements surrounding complications of care.

CCDS Reference Topics: Principal diagnosis; postoperative complications; complications of care; sequencing.

=========

Pulmonary vascular congestion accompanied by pleural effusions is classically associated with congestive heart failure, particularly left-sided or biventricular decompensation. Increased left-sided cardiac filling pressure raises pulmonary venous and capillary hydrostatic pressure, promoting interstitial and alveolar fluid accumulation. Fluid may also migrate into the pleural space, producing unilateral or bilateral pleural effusions.

Additional radiographic indicators of heart failure may include cardiomegaly, cephalization of pulmonary vessels, interstitial edema, Kerley B lines, perihilar alveolar opacities, and bilateral effusions. These findings should always be interpreted alongside symptoms and other clinical evidence such as dyspnea, orthopnea, edema, BNP/NT-proBNP, echocardiography, and response to diuretics.

COPD more commonly demonstrates hyperinflation, flattened diaphragms, and increased lucency rather than pulmonary vascular congestion. Cor pulmonale refers to right-sided cardiac dysfunction resulting from pulmonary disease and does not typically produce the classic pulmonary venous congestion pattern. Pulmonary embolism may have a normal chest radiograph or nonspecific abnormalities, but pulmonary vascular congestion with effusions is not its characteristic pattern.

For CDI purposes, imaging provides a clinical indicator but does not independently establish the diagnosis or acuity of heart failure.

CCDS Reference Topics: Heart failure pathophysiology; chest radiography; clinical indicators; cardiopulmonary terminology.

=========

For FY 2026, CMS Hospital Value-Based Purchasing performance is organized into four domains: Clinical Outcomes; Person and Community Engagement; Safety; and Efficiency and Cost Reduction. CMS reports that each domain contributes to the hospital's Total Performance Score, with the FY 2026 dataset showing weighted scores for all four domains.

The Hospital VBP Program is funded by reducing participating hospitals' base operating DRG payments by 2% and redistributing the amount through value-based incentive payments according to program performance.

CDI professionals are particularly relevant to quality reporting because complete and accurate documentation can influence coded clinical information used in mortality, complications, risk adjustment, patient-safety analysis, and other quality processes. Documentation integrity should not be manipulated to improve scores; rather, the health record must accurately reflect the patient's actual severity and clinical course.

ACDIS explicitly includes Hospital VBP measures, SOI/ROM, Patient Safety Indicators, and publicly reported quality data within CCDS program-analysis competencies.

CCDS Reference Topics: Hospital VBP; quality reporting; Safety domain; Clinical Outcomes; CDI impact on publicly reported data.

=========

The documented acute mental-status change associated with systemic infection creates a reasonable clarification opportunity for acute metabolic encephalopathy, assuming the complete clinical record supports that diagnosis.

Encephalopathy represents diffuse cerebral dysfunction arising from systemic, metabolic, toxic, hypoxic, infectious, or other causes. Acute confusion, impaired attention, fluctuating cognition, and absence of a focal lesion can support an encephalopathic process.

However, the CDI specialist cannot convert “altered mental status” into encephalopathy independently. The provider must determine whether the patient's presentation represents metabolic encephalopathy, delirium, medication effect, dementia, another neurologic condition, or simply a nonspecific symptom.

Chronic dementia does not fit the acute fluctuating pattern unless underlying dementia is separately documented. Cerebral infarction would generally require compatible focal neurologic findings and clinical or imaging evidence. Transient global amnesia typically presents with prominent acute memory disturbance rather than generalized encephalopathy.

A compliant query should include the mental-status findings, infectious process, relevant laboratory data, neurologic evaluation, treatment, and clinical course.

CCDS Reference Topics: Encephalopathy; altered mental status; infection; neurologic clinical indicators; diagnostic clarification.

=========

The wound care nurse's documentation may be used to establish the stage of a pressure ulcer, making option D correct. ICD-10-CM provides specific exceptions to the general rule that diagnosis code assignment is based on documentation by a provider legally accountable for establishing diagnoses. Pressure-ulcer staging is one of the clinical details that may be derived from documentation by qualified non-provider clinicians involved in the patient's care.

Wound care nurses possess specialized expertise in pressure-injury assessment and commonly document staging based on tissue involvement. Current ICD-10-CM guidance directs assignment of the pressure-ulcer stage according to clinical documentation and provides specific rules for unstageable ulcers, healing ulcers, and ulcers that progress during hospitalization.

This exception does not mean that a wound-care nurse independently establishes every element of the medical diagnosis for coding purposes. The provider documentation remains central to identifying the pressure-ulcer diagnosis and relevant clinical condition, while the stage may come from qualified clinician documentation.

POA assignment follows separate reporting rules and is based on whether the condition was present at the time inpatient admission occurred.

CCDS Reference Topics: Pressure ulcers; non-provider documentation; staging; coding conventions.

=========

Among the choices presented, sepsis associated with a urinary tract infection represents the strongest overall mortality-risk condition. Sepsis is a systemic, potentially life-threatening response to infection and is associated with substantially greater mortality risk than an uncomplicated localized infection, particularly in an elderly patient.

Risk of mortality in CDI is not determined merely by whether a diagnosis is a CC or MCC. Risk-adjustment systems evaluate the complete clinical profile, including principal diagnosis, secondary diagnoses, age, organ dysfunction, severity interactions, and other patient characteristics. Thus, reimbursement severity and predicted mortality are related concepts but are not interchangeable.

The history of mastectomy ten years earlier does not itself materially increase the current acute severity unless active malignancy or another relevant condition is present. The principal acute concern in option D is sepsis. COPD with respiratory failure and NSTEMI with acute systolic heart failure are also high-risk presentations and require complete documentation; however, the question's intended risk-adjustment comparison identifies the septic presentation as carrying the greatest mortality concern.

If acute organ dysfunction were linked to sepsis, documentation of severe sepsis would further increase the represented clinical severity.

CCDS Reference Topics: Risk of mortality; severity adjustment; sepsis; quality reporting; distinction between MS-DRG severity and ROM.

=========

For an inpatient discharge, a diagnosis documented as “probable” may be coded as though the condition existed or was established when it remains documented as such at discharge.

The FY 2026 ICD-10-CM Official Guidelines provide a specific inpatient rule for uncertain diagnoses documented at the time of discharge. Terms such as probable, suspected, likely, questionable, possible, still to be ruled out, compatible with, and consistent with are coded as if the condition existed, because the diagnostic workup and treatment generally correspond to the suspected condition.

Therefore, aspiration pneumonia—not merely the respiratory symptoms—is the appropriate condition to code in this scenario.

This rule is specific to inpatient hospital coding and should not be generalized to outpatient encounters, where uncertain diagnoses are handled differently and symptoms or confirmed conditions are generally reported instead.

A query would still be appropriate if the documentation were contradictory, clinically ambiguous, or if multiple competing diagnoses remained without sufficient clarification. But the word “probable” itself does not create a mandatory inpatient query.

CCDS Reference Topics: Inpatient uncertain diagnoses; aspiration pneumonia; discharge documentation; Official Guidelines.

=========

POA status is determined in relation to the time of inpatient admission, not the patient's physical arrival at the hospital. Therefore, a condition that develops during outpatient surgery, emergency-department care, or observation and remains present when the inpatient admission order occurs is generally considered present on admission for inpatient POA reporting.

This concept can be counterintuitive because the condition technically developed after the patient entered the hospital building. However, CMS's POA framework distinguishes outpatient care from the subsequent inpatient admission.

The fact that the condition is a complication does not automatically make it POA = N. POA status and classification as a complication are separate concepts.

A “U” indicator signifies insufficient documentation to determine whether the condition was present at admission; it should not be selected merely because a condition arose during outpatient care before admission.

CDI specialists frequently need to establish precise clinical timelines involving emergency services, observation, procedures, admission orders, and onset of complications. Clear timing supports accurate POA assignment and is especially important when diagnoses intersect with CMS HAC payment logic.

The CCDS framework specifically expects knowledge of POA and inpatient reimbursement regulations.

CCDS Reference Topics: POA; outpatient-to-inpatient transition; admission timing; HAC policy.

=========

The query should be rewritten as a neutral, clinically supported clarification request. The original wording is noncompliant because it directs the physician toward a particular diagnosis and explicitly identifies its reimbursement consequence.

The current ACDIS/AHIMA 2026 Guidelines for Achieving a Compliant Query Practice, released in August 2026, supersede prior versions and emphasize that the query process exists to ensure the health record accurately reflects the patient's clinical status.

A compliant query could present relevant findings such as oxygen saturation, respiratory rate, blood-gas values, oxygen requirements, work of breathing, escalation to noninvasive or invasive ventilation, and treatment. It should then request clarification using clinically reasonable choices or another compliant format without highlighting which answer produces an MCC.

An oxygen saturation of 84% may be an important indicator, but a CDI specialist may not convert that finding independently into respiratory failure. The provider must evaluate the complete clinical picture.

Approval from a coding manager does not cure biased wording. Substituting “CC” for “MCC” likewise leaves the fundamental compliance problem intact.

CCDS Reference Topics: Query compliance; leading queries; respiratory failure; ethical CDI practice.

=========

This is a classic clinical validation query scenario. A diagnosis has been documented, but the available clinical evidence appears inconsistent with or insufficient to support that diagnosis.

The CDI specialist should not independently delete acute respiratory failure, substitute another diagnosis, or direct coding personnel to disregard provider documentation without an appropriate clarification process. Instead, the query should objectively present the relevant clinical findings—normal respiratory effort, room-air oxygenation, absence of escalating oxygen requirements, and absence of ventilatory support—and ask the provider to clarify the diagnosis.

The provider may confirm respiratory failure and document additional clinical reasoning, revise the diagnosis, identify another condition, or state that the diagnosis was ruled out. The CDI specialist's responsibility is to support record integrity, not to replace provider clinical judgment.

The official CCDS content outline specifically requires candidates to understand mechanisms for addressing diagnoses lacking clinical support and to distinguish compliant from noncompliant queries. The current 2026 ACDIS/AHIMA guidance is the foundational query-practice standard.

CCDS Reference Topics: Clinical validation; respiratory failure; unsupported diagnoses; compliant query practice; documentation integrity.

=========