Provider Queries
Purpose and constraints
A query exists to clarify documentation so the record accurately reflects the patient's clinical picture and severity of illness. A query is not a tool to increase reimbursement, to dictate a diagnosis, or to compensate for a provider who declined to document. Any query that points toward a specific answer, or that exists only because a code pays more, is noncompliant.
Elements of a compliant query
A written query should include the patient identifier and encounter, the date, the name of the individual issuing the query, the specific question, the clinical indicators supporting the question (vital signs, labs, imaging, treatment, provider statements), clinically supported multiple-choice options plus a mechanism to indicate "other" or "unable to determine," a response line, and the provider's signature or electronic authentication. Verbal queries are acceptable where policy allows but must be documented in the record and authenticated.
Types and timing
Queries can be concurrent (during the stay, most effective for DRG accuracy) or retrospective (after discharge, before final coding). They may be written, verbal, or electronic. Escalate to a physician advisor or CDI lead when a query goes unanswered or the response contradicts the clinical picture.
Common traps
Yes/no queries with no supporting indicators; offering only one option; telling the provider what the answer "should be"; summarizing reimbursement impact; accepting a response that conflicts with the record rather than re-querying; failing to retain the query with the record.
Worked example
Creatinine 3.2 and rising BUN are documented, but the note says only "renal insufficiency." A compliant query lists the indicators and asks the provider to specify: acute kidney failure, chronic kidney disease, acute on chronic, or unable to determine - without suggesting which is correct.