The Sepsis Query That Arrived Too Late
A 71-year-old is admitted with pneumonia. On day 1 the emergency physician documents "pneumonia, hypoxia, IV antibiotics started" and a lactate of 3.4 mmol/L. On day 3 the patient's blood pressure drops to 84/50 and the intensivist writes "septic shock, transfer to ICU, norepinephrine started." The record contains no explicit statement of sepsis on day 1. A CDI specialist reviews the chart on day 6, after the physician has been discharged from the service and the patient is stable on the floor. She sends a multiple-choice query: "Sepsis vs. SIRS vs. bacteremia - please clarify." The physician selects "SIRS" without comment. The coder later assigns pneumonia with SIRS, and the case is submitted. Two months later the payer requests records and denies the ICU-level claim, citing lack of documented sepsis.
1. Was the CDI query appropriately designed and timed? Identify the specific failures and explain the compliance risk.
Read the worked answer
The query fails on several fronts.
Timing. It was issued on day 6, when the clinical picture had already resolved and the physician was off-service. A query should be raised when the clinical indicators are present and the provider is actively treating the patient, so the answer reflects contemporaneous judgment rather than retrospective reconstruction.
Leading format. A multiple-choice list that includes "sepsis" alongside "SIRS" telegraphs the desired answer and risks being read as a leading query. A compliant query states the clinical indicators (lactate 3.4, hypoxia, antibiotics, later hypotension requiring pressors) and asks an open question: "Please clarify the clinical significance of these findings and document the diagnosis you are treating."
Missing clinical context. The query did not attach the day-3 hypotension and vasopressor data, so the physician answered without the information that would have supported sepsis.
Compliance risk. A vague or leading query that produces a diagnosis unsupported by the record can constitute upcoding and creates False Claims Act exposure. The defensible path was an open, indicator-based query on day 1 or 2, with the answer documented in the progress note.
2. The claim has already been submitted and denied. What should the reviewer do now, and what should NOT be done?
Read the worked answer
What to do. First, do not simply resubmit with a "corrected" diagnosis. Re-review the original record and determine whether the documentation actually supports sepsis as the treating physician understood it. If it does, the appropriate step is a post-bill physician query limited to clarifying existing documentation - not adding new clinical facts. The physician may add a late entry that is clearly dated as a late entry, states the reason for the delay, and does not alter the clinical facts. If the physician confirms sepsis was the working diagnosis on day 1, an amended claim with supporting documentation can be filed. If the physician cannot confirm it, the original coding stands and the denial should be accepted.
What not to do. Do not coach the physician toward a specific answer, do not backdate an entry, and do not submit a query that lists only the payable diagnosis as an option. Do not alter the original note. Document the review, the query, and the physician's independent response in the compliance file. Consider a root-cause review of why the query was late - a CDI workflow gap, not a coder error.