Physician Queries and CDI Boundaries
Key Takeaways
- A query is appropriate when documentation is incomplete, conflicting, ambiguous, or clinically unclear in a way that affects code assignment.
- Compliant queries are nonleading, supported by clinical indicators in the record, and part of the documented query process defined by policy.
- Clinical documentation improvement (CDI) clarifies documentation; it cannot tell a provider what diagnosis to document for payment.
- If the provider does not respond or clarify, the coder reports only what the record supports under the applicable setting rules.
When to Query
A physician query clarifies documentation so codes can be assigned accurately. Query when the record contains ambiguity, missing specificity, conflicting statements, unclear cause-and-effect (for example, "is the ulcer due to the diabetes?"), inconsistent procedure detail, or clinical indicators that need provider interpretation. The AHIMA/ACDIS practice brief Guidelines for Achieving a Compliant Query Practice is the recognized standard the exam mindset reflects.
Do not query merely because a diagnosis would raise reimbursement, fill a CC/MCC (complication-comorbidity / major CC) gap, or improve a metric. The trigger is documentation facts plus clinical indicators, not the dollar value of the answer.
Compliant Query Features
A compliant query is clear, concise, nonleading, and grounded in the record. It may be open-ended or multiple choice when policy allows; when multiple choice is used, the options must be clinically reasonable and include neutral choices such as other, clinically undetermined, or unable to determine. A query must never include only the answer that pays more, and it must never reference DRG, payment, or quality scores.
A leading query points the provider to one answer, highlights payment impact, or asks for confirmation without adequate clinical support. "Please document acute respiratory failure to support the DRG" is non-compliant on two counts: it supplies the diagnosis and it cites reimbursement. A compliant version cites the indicators (oxygen saturation, work of breathing, oxygen therapy) and asks the provider to clarify the respiratory condition.
Verbal vs Written Queries
| Element | Compliant practice |
|---|---|
| Format | Written (paper/electronic) or verbal; verbal queries are documented per policy |
| Indicators | Cite the specific clinical findings already in the record |
| Options | Clinically reasonable; include a neutral / undetermined choice |
| Forbidden | Leading language, only-one-payable option, DRG/payment references |
| Retention | Query becomes part of the record or a defined query repository |
The CDI Boundary
Clinical documentation improvement (CDI) focuses on clear, complete, accurate documentation. CDI staff may educate providers about documentation requirements and collaborate with coders to resolve gaps, but CDI does not replace coding judgment, and neither coders nor CDI staff diagnose patients. Lab values, imaging, medications, and nursing notes can support a query, yet the provider must document the diagnosis. If the provider declines to clarify, the coder assigns only what the documentation supports under the applicable setting rules — not the coder's preferred or higher-weighted code.
Leading vs Nonleading: Side-by-Side
The single most tested distinction in this section is whether a query leads. A query leads if it introduces a diagnosis the record does not support, offers only the higher-paying option, or attaches the answer to reimbursement or quality impact.
| Leading (non-compliant) | Nonleading (compliant) |
|---|---|
| "Document sepsis to capture the MCC." | "WBC 18k, temp 39C, lactate elevated, on IV antibiotics — please clarify whether sepsis is present." |
| "Patient meets criteria for AKI, agree?" | "Creatinine rose from 0.9 to 2.1 with oliguria — is acute kidney injury present? Options: AKI / CKD exacerbation / other / undetermined." |
| "Add CHF to justify the admission." | "BNP elevated, bilateral crackles, IV diuretics given — please clarify the cardiac diagnosis." |
Query Format and Retention
A query may be open-ended ("Please clarify the type of pneumonia") or multiple choice. Multiple-choice options must be clinically reasonable and must include a neutral choice such as clinically undetermined or unable to determine; offering only diagnoses that increase severity is itself leading. Verbal queries are permitted but must be documented per facility policy, including who was queried, when, the clinical indicators cited, and the response. The query and its response are retained as part of the legal health record or a defined query repository — they are not discarded once the code is assigned.
When the Provider Does Not Respond
The exam tests what happens at the boundary. If a provider does not answer a query or declines to clarify, the coder does not assign the unconfirmed diagnosis and does not keep re-querying to pressure an answer. The coder reports only the conditions and procedures the documentation supports under the applicable setting rules and escalates a non-responsive query through policy (for example, to a physician advisor or compliance) when an unresolved gap materially affects code assignment.
The boundary line is constant: clinical evidence can support a query, but only the provider's documentation can establish the diagnosis that gets coded.
Common Query Triggers to Recognize
The exam rewards quick recognition of when a query is warranted versus when the record already answers the question. The most frequent triggers are clinical indicators without a stated diagnosis (abnormal labs, imaging, or vital signs the provider has not interpreted), a diagnosis stated without the specificity a code requires (pneumonia without organism; diabetes without type or control status), conflicting statements across notes that change the code, an unclear cause-and-effect link the classification needs ("is the acidosis due to the diabetes?"), and documentation of treatment for a condition that is never actually named.
By contrast, do not query to confirm something already clearly documented, to obtain a more lucrative diagnosis, or to resolve a question the coding guidelines already answer through a default code or convention. A query consumes provider time and creates a permanent record entry, so it is reserved for genuine ambiguity that affects code assignment — issuing unnecessary or repetitive queries is itself a quality problem, and a leading query is a compliance problem. Mastering that distinction is what separates a passing CDI/query answer from a failing one on the CCA.
The record shows low oxygen saturation, increased work of breathing, and oxygen therapy, but the provider documents only shortness of breath. Which query is most compliant?
A discharge summary states pneumonia, but progress notes alternately state viral and bacterial pneumonia, and the distinction affects code assignment. What should the coder do?
Which statement best describes the CDI role in a compliant coding environment?