8.3 When a Physician Query Is Warranted

8.3 When a Physician Query Is Warranted

Quick Answer: Under the August 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice, query when current-encounter clinical indicators support a clarification the record does not yet make. Typical inpatient triggers are a supported but undocumented condition, unclear / incomplete / inconsistent documentation, clinical validation of an unsupported diagnosis, present-on-admission (POA) status, acuity or specificity, history-of versus active disease, procedure intent, and a differential that was never ruled in or out. Never query to raise a DRG.

This independent OpenExamPrep section paraphrases the 2026 brief's "when to query" principles for inpatient CCDS study. It is not a substitute for the brief, not an ACDIS product, and not a claim of partnership or official approval. Chapter 9 covers formats and verbal-query mechanics; Chapter 10 covers leading versus compliant wording. Here the skill is recognizing a legitimate trigger.

The test before the list

A query is a communication tool used to clarify documentation so the record reflects the patient's clinical status and so diagnosis or procedure codes can be assigned accurately. It is not a suggestion box for a better-paying MS-DRG, a workaround for a thin quality abstract, or a way to import last year's problem list. Before you match a scenario to a bullet, confirm three things:

1. Current-encounter support exists. Indicators may come from the H&P, progress notes, consults, ED notes, labs, imaging, ancillary assessments, orders, and—when clinically relevant—a cited prior record. Prior documentation cannot be the sole basis for the query.
2. The clarification would be reportable. Inpatient options must be able to meet ICD-10-CM Section III / UHDDS additional-diagnosis rules (or to identify the principal diagnosis or the procedure actually performed). Querying a finding nobody evaluated, treated, or monitored is not a 8.3 skill; it is a 8.4 refusal.
3. The provider keeps independent judgment. The query is nonleading, indicators are sourced without the reviewer's diagnosis labels, and the text never mentions reimbursement, case mix, audit risk, or quality scores.

If those three fail, stop. If they hold, the 2026 list tells you the usual reasons to proceed.

Supported but undocumented conditions

The brief's first inpatient trigger is a condition supported by clinical indicators that meets reporting requirements but has not been explicitly documented by the provider. Example pattern: creatinine doubles from baseline, nephrology is consulted, IV fluids and holding of nephrotoxins are ordered, and no note says acute kidney injury. The indicators are real. The diagnosis is missing. A query is warranted.

The same pattern appears with acute blood-loss anemia after a gastrointestinal bleed (hemoglobin drop, transfusion, endoscopy) and with acute hypoxic respiratory failure (tachypnea, accessory-muscle use, new oxygen requirement, arterial blood gas) when the notes only say "pneumonia." Do not insert the missing diagnosis into the query as if it were already proven. Source the facts. Ask what condition is being evaluated or treated.

Unclear, incomplete, inconsistent, or intent-missing documentation

Query when documentation is unclear or incomplete, does not reflect the provider's intent, or contains inconsistencies among providers that block accurate coding. Incomplete often means a word is present but not usable: "heart failure" with no acuity or type despite an echocardiogram and IV diuretics; "pneumonia" with no stated organism or aspiration concern despite tube feeding and a right-lower-lobe infiltrate; a procedure note that never states whether debridement was excisional.

Inconsistent means two treating-provider statements cannot both be true. The attending resolves those conflicts, as Section 8.2 described. Incomplete also covers relationships: two documented conditions sit side by side (pancytopenia and chemotherapy; heart failure and valvular disease; ulcer and diabetes) and the record never says whether they are linked, even though coding needs the relationship and the "with" convention does not already supply it.

Clinical validation of unsupported diagnoses

A documented diagnosis that does not appear to be supported by available indicators is a query trigger, not an automatic deletion. Clinical validation asks the provider to confirm the diagnosis with additional evidence, to state that it was ruled out or is no longer valid, or to offer an alternative. The 2026 brief calls multiple-choice the optimal format and requires an open-ended "other" path. Typical option families include ruled out, no longer valid after study, confirmed with supporting evidence, and an alternative diagnosis.

A daily copy-forward of "acute respiratory failure" in a patient on room air with a normal blood gas and no distress is the classic inpatient example of this trigger. The specialist does not silently drop the code to protect an auditor, and does not silently keep it to protect the DRG. The specialist queries.

POA, acuity, history-of, procedures, and differentials

Several 2026 bullets are easy to under-study because they look like coding mechanics rather than query mechanics:

• POA (inpatient only). Query when it is unclear whether the condition was present at the time of the inpatient order. Conditions that began in the emergency department, in observation, or during outpatient surgery before that order are POA = Y once the diagnosis is established. A yes/no POA query must include unable to determine in addition to yes and no. U (insufficient documentation) is not a substitute for failing to query when the record could still be clarified.
• Acuity and specificity. Query when indicators support a more precise, still-reportable statement: acute versus chronic respiratory failure, systolic versus diastolic heart failure, stage of chronic kidney disease, type of myocardial infarction, organism of pneumonia. Do not offer clinically irrelevant choices (a low sodium does not support a hypernatremia option).
• History-of versus active. Query when a problem list or H&P says "history of" a condition that is being treated now, or says a condition is active when it appears resolved. Malignancy, venous thromboembolism, and hepatitis are frequent inpatient examples.
• Procedure objective, intent, or extent. Query when the operative note does not support a root operation, approach, body part, or depth. Intent is a PCS problem, not a guess from the instrument tray.
• Complications of procedures or care. Query when it is unclear whether an event is a reportable complication, an expected occurrence, or unrelated.
• Differentials ruled in or out. Query when the record lists competing diagnoses (NSTEMI versus demand ischemia; seizure versus syncope; infection versus colonization) and never closes the list. Inpatient uncertain-diagnosis rules can apply at discharge, but an open differential that was never addressed is still a clarification need.
• Assessments by someone who is not a qualified diagnostic provider. Query the treating provider when an RD, wound nurse, or other ancillary clinician wrote a diagnostic label. That bullet is the Section 8.2 multiple-choice rule in "when to query" clothing.

Never query to raise a DRG

The 2026 brief forbids query titles and bodies that mention reimbursement, quality measures, denial mitigation, or other reporting initiatives. "Please document acute hypoxic respiratory failure so the case groups to DRG 189" is not a query; it is a compliance failure. The same failure occurs if the only reason you opened the chart was to move a without-CC/MCC stay into a with-MCC stay, even if you were clever enough to leave the dollar words out.

A clinically warranted query may incidentally change the MS-DRG, the Hospital-Acquired Condition (HAC) POA flag, or a quality abstract. That incidental effect does not make the query improper. Motive, indicators, and wording do. If the indicators would not have prompted a query in a cash-pay patient with the same physiology, you do not have a 2026 trigger.

Worked inpatient pattern

Night-shift sodium is 118, the patient is newly confused, and 3% saline is infusing. Progress notes list only pneumonia. This is a supported but undocumented condition plus a possible specificity need (acute symptomatic hyponatremia versus a chronic baseline). Source the sodium with date and location, the infusion, and the mental-status change. Do not write "hyponatremia" as an indicator. Do not mention MCC capture. Ask what condition is being treated. If instead every note already says "acute hyponatremia, treating with 3% saline," you already have a codeable statement and no query is warranted.