Query IQ: “But the Provider Already Labeled it”

Querying Sepsis Without Leading

By Robin Sewell, CDIP, CCS, CIC, CPC, CCDS

A chart came across our team recently, causing one of our auditors to halt briefly. The patient was diagnosed with pneumonia, urinary tract infection (UTI), acute kidney injury (Creatinine 2.52), and hypotension (MAP 65). There was an obvious Sepsis 3 query opportunity, except the provider had already labeled AKI and hypotension as due to dehydration. 

The auditor’s instinct was to leave it alone. “If I query for sepsis now, could that be leading? The provider already gave the etiology.” 

That hesitation is one of the most common- and costly- reflexes in clinical documentation integrity (CDI). And it’s worth myth-busting, because two different issues are shrouded within. First, a misunderstanding of the current Query Practice Brief and, second, a payer conditioning.

Myth #1: “The provider already answered, so a query would be leading.” 

Documentation includes the diagnosis of respiratory insufficiency on the pulmonary consult date xx/xx/25. 

Clinical Indicators: 

This is a Query myth that gave our auditor pause. 

The facts: A query is not leading because it revisits a documented conclusion. Maybe that was the best conclusion based on clinical facts at that time. Medicine is both science and art.

So, the provider having attributed hypotension and AKI to dehydration doesn’t close the door. If anything, it’s why you knock. You’re not overturning their answer; you’re asking them to reconcile two things in the record that don’t yet line up: an active infection with SOFA-scoreable organ dysfunction, and a note attributing that dysfunction to volume depletion. Could the volume depletion also be attributable to their infectious process? The two are not necessarily mutually exclusive. Fluid resuscitation is often a first-line treatment for sepsis.

What would make the query leading is the execution: 

• Asserting that the AKI and hypotension “are organ dysfunction due to sepsis” (Playing Doctor) 
• Dropping dehydration as an option, or presenting only indicators that favor sepsis while omitting the ones supporting volume depletion- (Performing “un-natural” Selection) 
• Asking the provider to confirm sepsis rather than clarify the etiology. (Name Dropping) 

Keep dehydration on the table, lay out all the indicators, and ask them to clarify what’s driving the findings. This is not clarifying steering. The provider’s prior note isn’t an obstacle to a complaint query. It’s one of the answer choices.

Myth #2: “Maybe dehydration really does explain it.” 

This is a subtle myth, and it’s payer-driven. The premise is that fluid-responsive hypotension (or AKI) can’t really be sepsis. Querying would be chasing a diagnosis that will ultimately be denied by the payer. This is where payer conditioning has quietly infiltrated how CDIs and coders think. It’s worth scrutinizing the actual Sepsis-3 definition to address this myth. 

Sepsis-3 (Singer et al., JAMA 2016) defines sepsis as life-threatening organ dysfunction caused by a dysregulated host response to infection, with organ dysfunction operationalized as an acute increase in the SOFA score of 2 or more points resulting from the infection. Hypotension drives the cardiovascular component (a MAP below 70 is a point on its own), and creatinine drives the renal component (2.0–3.4 mg/dL is 2 points). A patient with an infection, a MAP under 70, and a creatinine of 2.52 already has a SOFA score of 3. AKI and hypotension aren’t a weak indicators of organ dysfunction — they are organ dysfunction under the definition. 

And nothing in the sepsis definition requires that dysfunction persists after a fluid bolus to confirm the diagnosis. “Despite fluids / in the absence of hypovolemia” language belongs to the definition of septic shock — the sickest subset of patients — not to sepsis- itself. The real question Sepsis-3 asks is attribution: was organ dysfunction a consequence of the infection, or of something else? Fluid-responsiveness is a clue about that, not a disqualifier. 

In this record, there absolutely was a basis to query. Pneumonia as a source, SOFA-scoreable dysfunction, and a competing dehydration explanation add up to genuine etiologic ambiguity — which is precisely the condition a query is meant to resolve. Uncertainty wasn’t a reason to hold back. It was the reason to ask for clarification. 

The Recommended Query

Now that we’ve established that it is appropriate to query in the situation, a compliant query writes itself:

Clinical indicators in the record: 

• ED Vitals: Heart Rate: 91 (Monitored) RR: 23 Blood Pressure: 80/50 SpO₂: 94% 
• H&P: Pneumonia documented on imaging; UTI + Streptococcus agalactiae 
• Labs: Creatinine 2.52 normal baseline; WBC 14 
• Treatment: IV Fluids administered 1.75 liters; Vancomycin/ Zosyn IV ABX 
• Progress Note: Pneumonia, UTI, AKI and hypotension secondary to dehydration 

The record reflects both active infections (PNA and UTI), as well as concurrent AKI, and hypotension currently attributed to dehydration.

Please confirm the etiology of the AKI and hypotension:

• Due to hypovolemia/dehydration 
• Due to sepsis secondary to pneumonia 
• Due to dehydration and sepsis 
• Clinically undetermined 
• Other (please specify) 

Notice what the query does:   

Any Query Response is a Win!

Whichever way it resolves, you’ve replaced ambiguity with clarity, and clarity is what survives an audit. If the etiology is sepsis, you’ve captured it with a neutral query. If the provider confirms dehydration as the etiology, it is still a win. Clarifying ambiguous documentation beats an unasked question every time.