A concurrent query for acute respiratory failure is outstanding with no authenticated provider response. What should the coder do regarding that diagnosis?
Select an answer to reveal the explanation.
Short Explanation
A query in flight is a question, not an answer. Until the provider writes back and authenticates, that diagnosis is not chart fact. Park the code until the response lands.
Full Explanation
A concurrent query creates a clarification opportunity; it does not create an established diagnosis. When a query for acute respiratory failure remains outstanding with no authenticated provider response, the coder must not report that diagnosis as established fact until an authenticated response is present in the record. Coding the diagnosis merely because a query was sent treats an unanswered question as a confirmed condition and is noncompliant for hospital inpatient abstracts. Using the query text itself as a "rule out" diagnosis misuses the query instrument as clinical documentation. Entering the diagnosis with POA "U" solely because the query is open confuses query workflow status with present-on-admission uncertainty rules and can distort quality and payment analytics. Exam caveat: inpatient uncertain-diagnosis guidelines at discharge differ from unanswered-query situations—know which pathway applies and never equate a blank query with provider agreement. Operational check for county CDI and coding teams: track query aging, withhold the queried diagnosis from the final code set until an authenticated response exists, then code consistent with that response and the remainder of the record.