15.2 Principles of a Compliant, Nonleading Query

Principles of a Compliant, Nonleading Query

A query asks the responsible provider to clarify the health record. Its purpose may be a missing diagnosis, greater specificity, a relationship between conditions, conflicting documentation, or clinical validation of an existing diagnosis. The desired outcome is an accurate record, including an answer that leaves severity unchanged, removes an unsupported condition, or acknowledges uncertainty.

The governing professional reference for this lesson is the August 2026 AHIMA/ACDIS query brief, particularly Sections V–VII and X. It supplies professional guidance rather than creating a separate federal offense for each defective query. Apply it together with current coding guidance and organizational policy.

Start with the issue requiring clarification

Before drafting, identify what the existing record actually says. Distinguish an absent diagnosis from a condition already established but lacking a detail. Read later notes before querying an earlier omission: the provider may already have supplied the answer. Determine whether an apparently conflicting statement concerns the same condition, time, and encounter.

The purpose affects both the recipient and the question. A diagnosis query belongs with an appropriately involved provider who can establish the diagnosis. A request for a missing administration time may belong with the clinician who performed or documented the service. An administrative reviewer should not answer a medical diagnosis query solely because the reviewer has access to the chart. Use the recipient rules in Section VII and the organization's escalation process.

Clinical validation asks the provider to review an existing diagnosis whose support appears inconsistent or unclear. It does not allow CDI to erase a diagnosis by applying its own threshold. FY2027 coding guideline I.A.19 bases code assignment on the provider's diagnostic statement rather than the coder's independent clinical criteria; clarification remains appropriate when the record raises a concern. These principles address different decisions and must be used together.

Present a faithful, balanced record

Include relevant patient-specific indicators and identify their locations. Useful evidence may include provider observations, laboratory or imaging reports, treatment, nursing assessments, or other ancillary documentation. There is no universal minimum number of indicators. Include information important to the question, including contrary findings that materially affect the interpretation.

Preserve what the source says. If the record contains a heart rate of 120, cite that measurement and its source rather than inserting a new diagnosis of tachycardia into the evidence. A hemoglobin value is not permission to label the patient anemic in the query's clinical summary. Distinguish a diagnosis already documented by a provider from a diagnosis offered for the provider's consideration as an answer option.

Prior-encounter evidence can be relevant. Section X permits its use when connected to the present clinical scenario and an appropriate current trigger. For example, a prior renal diagnosis may help clarify current renal dosing. Cite the prior record and the current reason for clarification; do not import an old diagnosis into the current claim or search unrelated history solely to collect codes.

Neutrality extends beyond the question sentence

Review the visible title, clinical summary, answer choices, formatting, and any accompanying conversation. A neutral sentence does not cure a title that announces a preferred diagnosis. The brief bars references to reimbursement, quality measures, denial mitigation, or reporting consequences in relation to the requested clarification or particular answers. Avoid asking the provider to “help the hospital” achieve a score or payment outcome.

Do not direct the provider to document a particular diagnosis or hide reasonable disagreement. Clinical definitions or recognized criteria may be supplied, with a citation, at the end of a template under Section V.I.F. Their presence should inform the provider without emphasizing a preferred result. Criteria should not be converted into a statement that CDI has already made the diagnosis.

Wording such as “agree” or “confirm” is evaluated in context. A yes/no question can appropriately substantiate a diagnosis already present in provider documentation, with the required response structure. The same wording cannot be used to introduce a new diagnosis from raw observations. Format-specific rules matter more than a blanket ban on a few verbs.

Work through a clinical validation example

Consider this hypothetical record:

• Operative report, October 21: estimated blood loss 20 mL.
• Laboratory report: hemoglobin 10.2 g/dL before the procedure and 10.1 g/dL the following morning.
• Progress note, October 22: “acute blood loss anemia.”
• No explanation of the apparent discrepancy is found in the reviewed record.

A neutral open-ended request could identify these sources and ask the provider to clarify the diagnosis associated with the laboratory findings and the existing anemia statement, including whether the statement remains applicable. It should allow a free-text explanation. The provider might identify additional information or explain a different condition; the question should not announce that blood-loss anemia is impossible or require its removal.

Compare that approach with “The blood loss was only 20 mL, so please remove acute blood loss anemia to avoid an audit.” That version supplies CDI's conclusion and a denial-related incentive. Both can influence the answer. Conversely, a query asking the provider to retain the condition because it affects reimbursement is equally unacceptable.

Match response choices to the format

There is no universal four-element formula requiring diagnostic alternatives in every query. An open-ended query provides a neutral prompt and relevant indicators without preselected answers. A multiple-choice query needs at least one clinically valid supported option and a way to supply an alternative explanation, such as an “Other” field. It does not require three diagnostic differentials or a fixed combination of “Other,” “Unable to determine,” and “Ruled out.”

A general yes/no query requires the appropriate existing-documentation basis, relevant indicators, no preferred answer, and a third route for inability to determine or further free-text information. A POA yes/no query specifically requires Yes, No, and Unable to determine. Section 15.3 applies these distinctions to complete examples.

Do not manufacture unsupported chronic disease, shock, dementia, or other alternatives merely to make a list longer. An irrelevant low-severity choice does not make an unsupported high-severity choice acceptable. Similarly, “Unable to determine” is not an uncertain diagnosis such as “probable” or “unable to rule out”; the coding consequences must follow the actual response.

Preserve the answer and review the process

An appropriately authenticated response in the permanent health record may support coding without repetition elsewhere, provided subsequent information does not create a conflict. Retain actual queries in the health record or in a retrievable business record as organizational policy directs. The query log alone does not substitute for the provider's usable clinical response.

Review a sample of completed queries for faithful sourcing, supported choices, suitable format, correct recipient, and appropriate response documentation. A high response rate or a high rate of favorable DRG changes cannot establish compliance. Investigate repeated unsupported options or pressure after a provider has answered; correct the template, education, or workflow responsible for the problem.

The False Claims Act addresses specified conduct involving false claims, including knowing submission and material false records. Its knowledge definition includes actual knowledge, deliberate ignorance, and reckless disregard. A query defect alone does not prove all elements of liability. Escalate suspected misconduct for appropriate compliance and legal assessment; do not teach a checklist error as an automatic fraud finding or attach an undated penalty range to it.