9.1 Chain of Command & Protocols for Unanswered Queries

Resolving Unanswered Queries Through a Defined Escalation Process

An unanswered query leaves a clarification request unresolved. It does not establish the proposed diagnosis, prove provider misconduct, or automatically prevent every aspect of coding from proceeding. The CDI team first determines whether the request remains necessary, whether it reached the appropriate provider, and what the organization’s approved process requires. Escalation brings an unresolved issue to someone who can help resolve it; it must preserve independent clinical judgment.

The August 2026 ACDIS–AHIMA query practice brief assigns specific response windows to organizational policy. It describes concurrent response before or at discharge as best practice and recommends a defined window for retrospective queries. It also addresses closure when escalation has been exhausted: close the query under policy and assign codes from the existing health record. A national five-tier ladder with fixed hourly deadlines would replace that framework with requirements the brief does not establish.

Distinguish the Problem Before Sending a Reminder

Silence has several possible causes. The message may have reached an inactive inbox, the requested clinician may not have participated in the relevant care, the question may be unclear, or the clinical workup may still be evolving. A provider may also have answered in an authenticated record entry that the tracker has not captured. Check these possibilities before classifying the event as nonresponse.

Review the original request as carefully as the delivery route. Confirm that a real documentation need remains, the indicators are sourced accurately, and the question does not suggest a preferred diagnosis. A supervisor can identify a flawed template or duplicate query and arrange correction or withdrawal. Escalating a defective question through more senior people does not make it appropriate.

Separate administrative nonresponse from a clinical answer the reviewer dislikes. A provider’s reasoned rejection of the suggested condition, or a genuine inability to determine it, may resolve the question. An agreement rate is not a standard against which every individual answer must be forced.

Build the Local Path Around Responsibilities

An effective policy identifies an owner at each necessary stage, the response window, the permitted communication channels, and what happens at closure. It should accommodate actual coverage and practice arrangements. A small program might use a CDI lead and a designated physician advisor; a larger organization may involve service leadership. The number and titles of the steps are local design decisions.

This table is a workflow example, not a national sequence or sanction schedule. Clinical concerns requiring immediate patient care use the appropriate clinical safety route; an administrative query clock must not delay care.

Governance and Authority

Use the organization’s actual approval structure. Medical staff leadership may need to participate when policy affects provider responsibilities, coverage, or conduct. Under 42 CFR 482.22, hospital medical staff governance and bylaws have specified responsibilities, including governing-body approval of bylaws. That does not mean every CDI procedure must receive separate Medical Executive Committee ratification or automatically become a condition of privileges.

Medical record completion requirements also have their own scope. For example, 42 CFR 482.24 addresses the hospital record, authentication, final diagnosis, and completion within 30 days following discharge. That provision is not a national 30-day query response deadline, nor does it create a 72-hour disciplinary rule. Verify applicable law, bylaws, and local authority before describing an administrative consequence. CDI personnel should refer conduct issues to the responsible leadership rather than invent sanctions in a query message.

Communicate Without Changing the Clinical Question

A reminder can identify the encounter, the pending clarification, the applicable local response expectation, and where help is available. It should avoid blame and unnecessary disclosure. Use approved access and communication arrangements suitable for patient information.

If a peer conversation asks for patient-specific diagnostic clarification, it remains a query regardless of the speaker’s title. Preserve the actual discussion and obtain the provider’s response in the permanent health record when it is to support coding. A tracker entry saying “advisor agrees” does not substitute for the responsible provider’s documentation. General discussion of documentation principles can be education; the distinction depends on the interaction’s function.

After an answer, evaluate what is actually unresolved. A subsequent query may address new or evolving information or obtain necessary specificity from a prior response. Repeating substantially the same question to obtain a preferred answer is inappropriate. Neither a second query nor an unhappy reviewer, by itself, establishes the proper next action.

Manage Closure and Billing Together

HIM, CDI, and revenue-cycle staff should know who can place or release a billing hold, how open issues are reviewed, and who handles a dispute. Some unresolved questions may affect a claim materially; others may not change the available supported code assignment. Avoid an assumption that every open query demands an indefinite hold or an automatic unspecified diagnosis.

When the defined escalation process is exhausted, close under policy and code the existing record using applicable conventions and guidelines. Communicate any genuine unresolved coding question through the appropriate coding or compliance process. Do not infer a diagnosis from nonresponse or convert “unable to determine” into a probable diagnosis. Document the reason for closure rather than recording an invented agreement.

If a provider later supplies an answer, use the applicable amendment and claim-correction procedures. A closed tracking status neither erases the prior communication nor determines whether a later record correction is permissible.

Worked Workflow Review

A program reviews 32 unanswered requests. Four reached an obsolete inbox, six were already answered in authenticated record entries, and two repeat questions no longer serve a documentation need. The team corrects the route, reconciles the six responses, and reviews the two duplicates for withdrawal. Twenty requests still require the approved follow-up process. Calling all 32 cases provider delinquency would conceal the causes and direct the intervention at the wrong people.

For a simple administrative measure, the initial routing defects were 4 / 32 = 12.5% of this reviewed group. This is a local sample result, not a national benchmark or a rate among all queries. Keep the denominator and observation period visible. A program can also track response time, closure reasons, and unresolved age, using explicit rules for when the clock starts and which completed responses enter the calculation.

Review unusually long delays and repeated escalation for their causes. They may signal access problems, unnecessary questions, unclear coverage, education needs, or conduct concerns. No single percentage establishes the explanation. A useful escalation process improves clarity and reliable follow-through while allowing the provider to reach any clinically supported conclusion.

Source anchors: ACDIS–AHIMA 2026 query practice brief, sections V, VII, IX, and XIII; 42 CFR 482.22; 42 CFR 482.24.