Handling Verbal Queries
By Robin Sewell, CDIP, CCS, CIC, CPC, CCDS
We rely on instant messaging for its convenience. Text, Teams, WhatsApp-you name it. Hospitals are no different. EHR messaging systems and other applications have made communication between CDI, Coding, and providers easier than ever. Could we be sacrificing compliance for convenience?
Example instant message:
“Doctor, do you agree that Mr. Smith had acute respiratory failure?”
Or perhaps:
“Doctor, do you agree that sepsis should be removed, documentation seems weak?”
The physician responds, “Yes.”
While verbal queries are perfectly acceptable, there needs to be a “paper trail.” Unfortunately, this practice is not always followed. When does this become a problem?
Scenario 1: Codes Eliminated from the Coding Summary
During a recent DRG audit, we found solid documentation of sepsis and metabolic encephalopathy in the patient’s chart, but these diagnoses never made it to the coding summary or final billing.
Our first thought was that the CDI or coding professional must have sent a clinical validation query, and the physician subsequently ruled out these conditions.
However, no clinical validation query was found in the chart or the CDI application. Instead, the clarification apparently occurred through a private conversation that went undocumented.
Particularly concerning was the removal of physician-documented significant, clinically valid, and reportable diagnoses. From an audit perspective, it appeared that the CDI specialist or coder had independently determined that these diagnoses were unsupported and removed them from the coded record. In fact, this topic is addressed in Coding Clinic for ICD-10-CM/PCS, Fourth Quarter 2017: Page 110 “Omitting ICD-10-CM Codes” where the instruction is that it is “not appropriate to develop internal policies to omit codes automatically when the documentation does not meet a particular clinical definition or diagnostic criteria.”
Imagine the potential consequences…
A patient is admitted for a complicated urinary tract infection (UTI), discharged after a couple of days, but subsequently readmitted in septic shock and expires.
What if sepsis and metabolic encephalopathy were clinically valid during the previous admission but never made it into the coded data?
The hospital’s reported severity of illness and risk-adjusted outcomes may no longer accurately reflect the patient’s clinical condition. Suddenly, we’re not just talking about a missed DRG opportunity. We’re talking about the integrity of the hospital’s quality data.
Scenario 2: Generic Templates Added to the CDI Application
In other cases, we may find a “query” that apparently follows an instant message conversation that was never adequately documented.
These appear to be placeholders intended to create a “paper trail.” However, they contain little to no clinical indicators, no source documentation, no record of the conversation, and no indication of what was truly presented to the physician.
Instead, the provider simply selects “agree” or “disagree” from a dropdown menu.
Agree or disagree with what, exactly?
This creates a significant vulnerability: third-party reviewers, including payers, could exploit because they cannot determine what the provider was asked or why a diagnosis was added or removed.
And yes, that opens the door to denials and compliance concerns.
What Does the Query Practice Brief Actually Say About Verbal Queries?
The 2026 AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice specifically recognizes verbal queries, including communications conducted through chat and messaging.
The Brief defines a verbal query as:
A verbal query is conducted through spoken communication or dialogue (e.g., chat, messaging, etc.) that is documented in accordance with organizational policy.
Importantly, the Brief further specifies that verbal queries must include the clinical indicators and response options discussed, be recorded and tracked consistently with written queries, and have the provider’s response documented in the health record to support code assignment.
So, the issue isn’t whether you can send an instant message. You can. But communication must meet the same compliance requirements as a written query. More importantly, other reviewers or auditors need to be able to verify documentation trail.
Section V, III, Verbal Queries, identifies the information that must be captured:
- Date, time, and individuals involved
- Clinical indicators discussed and their sources
- A nonleading query statement explaining the need for clarification
- Answer options presented, when applicable
- The provider’s verbal response
The Brief also explains that clinical validation queries are intended to clarify whether a documented diagnosis is clinically supported. The purpose is not simply to confirm or negate a diagnosis, but also to obtain additional clinical evidence or the provider’s clinical reasoning when appropriate.
This is an important distinction.
The objective of CDI and coding is not to independently determine which physician diagnoses should survive DRG review. It is to identify documentation opportunities and obtain appropriate clarification from the provider.
When a documented diagnosis is removed without a compliant clarification process, it becomes difficult to distinguish the physician’s clinical judgment from the CDI or Coding professional’s interpretation.
Query IQ Tip
Document the Question, Not Just the Answer
One of the biggest misconceptions about verbal queries is that documenting the physician’s response is sufficient.
It isn’t.
If the only record of the interaction is “physician agreed,” we’ve lost the most important part of the query process: What information was presented, what clarification was requested, and how was the provider given the opportunity to exercise independent clinical judgment?
And entering an incomplete query template after the conversation doesn’t correct the original problem.
Remember, a compliant verbal query doesn’t necessarily require a separate written template. It does, however, require documentation and tracking of the query interaction and a provider response in the permanent health record.
Is Your Query Process Audit Ready?
Brundage Group experts can review your verbal and written query practices and help you close documentation gaps before your auditors find them.


