8.5 Query Retention, Audit Trail, and Provider Response Handling
Key Takeaways
- A query process must preserve who asked, what was asked, which indicators were used, how the provider responded, and how the response affected coding.
- Provider responses must be authenticated and interpreted with the rest of the record, not treated as a standalone shortcut.
- If a response conflicts with existing documentation, is incomplete, or does not answer the question, additional compliant clarification or escalation may be needed.
- Retention rules are facility-specific, but the audit trail should support consistency, compliance review, denial defense, and coder accountability.
The Audit Trail Is Part of the Query
A provider query is not just a question. It is a documented compliance event that should show why clarification was needed, what clinical indicators were presented, who sent the query, who responded, when the response occurred, and how the final coding decision was supported. Facilities may retain queries as part of the legal health record, as a business record, or through another approved system depending on policy. For CCS purposes, the key concept is that the query and response must be retrievable and defensible.
The audit trail protects more than reimbursement. It supports data integrity, quality reporting, denial response, provider education, internal audits, and external review. If a payer later challenges acute kidney injury, sepsis, encephalopathy, malnutrition, a complication code, or POA status, the organization should be able to show the original documentation, the query indicators, the provider's authenticated response, and the final code assignment rationale. A query that exists only as an undocumented conversation cannot perform that function.
Query Record Components
| Component | Why it matters |
|---|---|
| Date and author of query | Shows accountability and timing |
| Patient encounter identifier | Connects the query to the correct record |
| Clinical indicators | Supports why clarification was clinically reasonable |
| Query question and options | Allows compliance review of non-leading language |
| Provider response | Establishes the clarified documentation for coding |
| Authentication | Confirms the response is attributable to the provider |
| Coding impact or disposition | Shows whether the response was used, not used, or required follow-up |
| Escalation notes when applicable | Explains unresolved conflict or nonresponse handling |
Provider responses must be read carefully. If the provider selects acute blood loss anemia but the rest of the response says the hemoglobin drop was expected and clinically insignificant, the coder should not blindly code the most severe phrase. If the provider writes unable to determine, the coder should not code the condition that the query suggested. If the provider answers with a diagnosis that is not one of the listed choices but is clinically supported and authenticated, the coder may use it if coding guidelines and facility policy allow.
The query response becomes part of the documentation picture, not a substitute for coder judgment.
A response may be incomplete. For example, a query asks for heart failure acuity and type. The provider answers systolic but does not clarify acute, chronic, or acute on chronic. The coder may code the type if supported but still lack acuity. Depending on the record and facility policy, a follow-up query may be needed. The follow-up should not pressure the provider by saying, you forgot to choose acute. It should state the remaining unresolved issue and include the relevant indicators.
A response may also create a conflict. Suppose a query asks whether a pressure injury was present on admission. The wound care nurse documented a stage 3 sacral pressure injury on hospital day one, but the provider responds that it developed after admission. If other provider documentation conflicts, the coder may need escalation or additional clarification. The coder should not override the provider response with nursing documentation alone for diagnosis coding, but nursing documentation may be relevant clinical evidence and may support a query.
Response Handling Workflow
- Confirm the response is from an authorized provider and is authenticated according to facility policy.
- Read the response with the original query and the full record.
- Determine whether the response fully answers the documentation barrier.
- Assign codes only for diagnoses, procedures, POA status, and relationships that are now supported.
- If the answer is unable to determine, no additional diagnosis, or not clinically supported, do not code the queried condition.
- If the response is incomplete, contradictory, or unclear, follow facility policy for follow-up query or escalation.
- Retain the query, response, and coding disposition in the approved system.
Nonresponse handling must also follow policy. Some facilities allow concurrent query reminders, escalation to CDI leadership, or referral to a physician advisor. Coders should not keep resending the same leading query or hold a claim indefinitely without a defined process. If the provider does not respond and the record remains insufficient, the coder must code based on existing documentation and guidelines. The absence of a response does not permit assumptions.
Query retention also supports education and metrics, but metrics can create risk if used improperly. Tracking query response rates, agreement rates, and common documentation gaps is useful for process improvement. However, pressuring coders or providers to achieve a target agreement rate can compromise compliance. A low agreement rate may mean queries are weak or unsupported; a very high rate may mean queries are leading or sent only when the answer is obvious. The ethical focus is accuracy.
In exam questions, watch for answers that say to code from an unsigned email, use a verbal answer without documentation, ignore an unable-to-determine response, or change a code because a query was sent even though no response was received. Those answers are weak. The best answer preserves the audit trail and codes from authenticated, clear provider documentation.
A provider responds to a query with unable to determine. What should the coder generally do?
Which item is most important for query audit defensibility?
A provider answers only part of a query, leaving a coding fact unresolved. What is the best next step if clarification is still required?