24.2 Query Timeframes, Aging and Measurement

Define what each query clock measures

Query timeframes are meaningful only when their start, end, calendar, and population are explicit. A request can be delivered, opened, answered, authenticated, reviewed, and administratively closed at different times. Calling all of these events “turnaround” makes it difficult to identify the actual delay or evaluate a local policy fairly.

Section IX of the 2026 AHIMA/ACDIS query brief leaves specific response timeframes to organizational policy. It recommends concurrent responses before or at discharge as best practice, a defined retrospective window, and escalation and closure for unanswered requests. It does not establish one national hourly response target or pre-bill holding period. This lesson applies that framework to clocks and aging; Section 9.1 addresses the escalation process itself.

Specify the events before calculating elapsed time

Build a local definition that someone outside the department can reproduce:

Document the approved interpretation before judging performance. Do not silently restart a clock when a reminder is sent or mark an unanswered question resolved because a notification was opened. If a request was defective or misrouted, preserve that fact and its correction; decide its treatment under the metric's stated rules rather than conceal the delay.

Work a calendar-versus-business-day example

Illustrative local policy: Business days are Monday through Friday, with no holidays in this example. All timestamps use one time zone with an unchanged UTC offset. The dispatch day does not count. A response is due at 17:00 on the second business day after dispatch. This is an invented local policy for calculation, not an AHIMA/ACDIS requirement.

A query is dispatched on Friday, October 23, 2026 at 15:00. Monday, October 26 is the first following business day; Tuesday, October 27 is the second. The local deadline is therefore Tuesday at 17:00. The elapsed calendar interval from dispatch to that deadline is 98 hours.

Under a different hypothetical rule requiring a response within 48 calendar hours, the deadline would be Sunday, October 25 at 15:00. These policies do not mean the same thing. Neither should be described simply as a national “two-day” standard. A hospital choosing either method would still need to consider its actual clinical setting, coverage, and applicable requirements.

The calculation also depends on the start rule. A policy counting the dispatch day would produce a different business-day result. Do not change that rule after observing whether a case met the target. Publish the definition and apply it consistently to the stated cohort.

Separate response, authentication, and staff processing

Use the same hypothetical Friday dispatch with the following recorded events:

If the defined metric ends at an authenticated usable response, its result is 92 hours, not 66 or 67. The interval from that response to completed CDI review is three hours. These figures answer different operational questions. The preliminary reply's content and documentation must still be evaluated through the approved response process; the timestamp alone does not establish coding sufficiency.

Under the stated local business-day policy, the usable answer arrives before Tuesday's 17:00 deadline. That does not establish a national compliance conclusion, prove clinical accuracy, or determine the correct code. The example measures a defined process, while Section 16.3 addresses response content and authentication.

Include unresolved work in the aging picture

A report containing only answered queries can hide the longest delays. Define an observation cutoff, retain the pending population, and distinguish requests whose deadlines have passed from those not yet due. Also identify withdrawn or corrected requests under the published measure definition.

Worked cohort: At a stated cutoff, ten dispatched queries remain in the reporting cohort. Eight have reached their deadlines: six received usable responses on time and two remain unanswered and overdue. The other two queries remain pending and are not yet due. There are no withdrawals or other exclusions in this example.

• Overall usable-response proportion at the cutoff is 6 ÷ 10 = 60%.
• Eight requests have reached their deadlines: six answered on time and two overdue. The on-time response proportion among requests due by the cutoff is 6 ÷ 8 = 75%.
• The two not-yet-due requests remain visible as pending; they are not overdue failures under this local definition.

Reporting only the six completed requests would produce an apparently perfect completed-case result while omitting the two overdue cases. Reporting every unanswered request as overdue would incorrectly classify the two whose deadlines have not arrived. State the numerator, denominator, cutoff, and definition with the result. These are illustrative operational measures, not required national thresholds.

Examine age bands and causes rather than use one percentage as proof of provider behavior. A long interval may involve routing, coverage, unclear content, incomplete documentation, or departmental processing. Investigate the actual record and workflow before assigning responsibility.

Keep query targets separate from record and billing requirements

For covered hospitals, 42 CFR 482.24(c)(4)(viii) includes final diagnosis and completion of medical records within 30 days after discharge. That is a hospital record-completion requirement, not a universal 30-day response window for every query. A local two-business-day query target does not replace that requirement; the record rule also does not supply a five-day billing hold or authorize delaying an urgent clinical concern.

Discharge, record completion, query closure, and claim readiness need separate owners and status information. Apply actual billing and amendment procedures to an unresolved or late answer. Do not infer a diagnosis from silence to release a claim. After exhausted escalation, the brief directs closure under policy and code assignment from the existing health record, using applicable coding guidance. Existing supported diagnoses are not automatically erased merely because requested additional specificity remains unanswered.

Preserve a reproducible time history

Keep the issued version, delivery and response events, responsible roles, due-date basis, and actual disposition linked through the approved systems. If a legitimate late response requires reopening, preserve the earlier closure and evaluate the new information through the applicable process. Do not overwrite an earlier event to make the case appear timely.

When policy changes, identify the effective version and which requests it governs. Explain whether an absence or system outage changes a deadline and who authorizes the decision. A retrospective dashboard should not apply whichever policy version gives the most favorable result. The record-management and preservation rules themselves are addressed in Section 24.3; maintaining a useful aging history does not create a new nationwide retention period.