17.4 Managing Post-Discharge Query Workflows

Managing Post-Discharge Query Workflows

A useful retrospective workflow tells staff who owns the unresolved issue, where the query and response are recorded, when to escalate, and how to close the account. Clinical accuracy and timely billing both benefit from explicit responsibilities. Neither a fixed national query clock nor an automatic billing hold follows from the fact that a query is retrospective.

The 2026 AHIMA/ACDIS brief, Sections IX and XIII, assigns response windows, escalation and closure to organizational policy. It recommends responding to concurrent queries before or at discharge and giving retrospective queries a defined window. It does not prescribe a universal 3–5-business-day response deadline, day-3 reminder, day-5 physician intervention or day-10 claim release.

Trace the account and the question separately

An open query is a clinical-documentation work item. A claim hold is an operational status applied under the organization's rules. Some queries occur before billing, some after billing, and not every question prevents final billing. Before placing a hold, determine the issue's effect on coding or reporting, the responsible owner and the appropriate action under policy. Do not make a hold's dollar value an instruction to the provider to confirm a diagnosis.

The HFMA MAP Keys distinguish several revenue-cycle measures:

Hypothetical calculation: At month-end, gross DNFB is $1.2 million. The month's gross patient-service revenue is $12 million over 30 days. Average daily gross revenue is $400,000, so DNFB days are $1,200,000 ÷ $400,000 = 3 days. This does not mean every account has been held for exactly three days. Do not substitute net revenue or a three-month denominator into that PB-1 calculation.

Track query-related accounts with a defined reason code and attribution method. Separately track account age, query-response time and total financial measures. A reduction in open queries does not prove a matching reduction in net A/R days: other billing work, receivable balances, revenue and collections also change.

Define a local workflow with explicit handoffs

For training, a facility might choose a response window and reminder schedule suited to its coverage and billing processes. Such numbers must be identified as local examples, not attributed to AHIMA, CMS or a national performance benchmark. The hospital medical-record completion requirement in 42 CFR 482.24 is not itself a universal CDI query-response deadline.

A physician champion can explain the clinical question and help resolve routing or workflow barriers. An administrative advisor who did not participate in the encounter's clinical care cannot supply its diagnosis merely to clear the queue. Repeating a substantially similar question to obtain a preferred answer is improper pressure. Further clarification may be appropriate for new/evolving information or needed specificity; the number of queries alone does not decide compliance.

Verbal retrospective queries are possible

A phone conversation can be an appropriate retrospective query when conducted and recorded under the same substantive standards as a written query. Record the patient-specific question, relevant sourced indicators, options discussed, participants, date/time and actual response under policy. Keep confidential patient discussion in an appropriate setting.

For coding, the clinical answer must reach the permanent health record through an approved, appropriately authenticated mechanism. A private CDI note saying “the physician agreed” is insufficient. However, a permanent authenticated query-response document can supply the answer without requiring the same diagnosis to be repeated in a separate discharge-summary addendum. The actual query may be retained in the health record or a retrievable business record under the organization's retention policy.

Suppose a provider clarifies metabolic encephalopathy by phone but the only documentation is an internal tracking entry. The team should obtain the required permanent clinical response before using that clarification as the basis for code assignment. The problem is the missing clinical response record, not an absolute ban on spoken communication. A signature alone also does not settle whether a response is clinically consistent or whether its code is reportable.

The hospital record rules require appropriate completeness, dating, timing and authentication; they do not dictate a single vendor, physical EHR interface or exclusive addendum workflow for every query. Use HIM's approved correction and authentication process. Preserve a retrievable query history so the original question and actual answer can be evaluated.

Improve the causes of avoidable delay

Review recurring issues before adding more reminders. Examples include misrouted questions, unclear requests, uncovered provider absences, late results with no assigned reviewer, genuine diagnostic conflicts and missing authentication. Concurrent review and discharge planning can address issues already apparent during the stay, while some final results will still become available later.

Use a balanced dashboard: query counts by timing and reason, responses within the defined window, median response time, age of unresolved work, closure without response, sampled query quality and attributable account holds. A program should not be judged by an invented universal target of fewer than 5–10% retrospective queries. Evaluate its clinical setting, staffing, result timing and review design.

Close unanswered queries under policy after the escalation pathway is exhausted and code from the existing health record. Do not treat silence as confirmation or automatically bill a requested diagnosis. A subsequent billing decision must also satisfy the relevant claim rules; query closure is a workflow disposition, not a waiver of factual accuracy or reporting requirements.