The Sepsis Query and the Missing Progress Note
A 64-year-old admitted with pneumonia has an admission note documenting 'sepsis, lactate 3.1, started on broad-spectrum antibiotics within 1 hour.' Day 2 progress notes document 'improving, afebrile, tolerating PO.' The physician documented 'pneumonia, resolved sepsis' on the discharge summary. The CDI specialist wants to query for 'severe sepsis' because the lactate was 3.1 and the patient received IV antibiotics. The coder notes the physician never documented 'sepsis' in the discharge summary, only 'resolved sepsis.' The facility uses a compliant query process requiring clinical indicators to support the query. The DRG with sepsis as principal diagnosis pays $18,400; without it, $9,200.
1. Should the CDI specialist issue a query for severe sepsis? Analyze the clinical indicators and query compliance requirements.
Read the worked answer
No - not for severe sepsis, and not as framed.
- Clinical indicators: Lactate 3.1 and IV antibiotics support possible sepsis, but 'resolved sepsis' in the discharge summary is a physician statement that sepsis occurred. The question is whether severe sepsis (sepsis with organ dysfunction) is supported. A single lactate of 3.1 is a screening/monitoring value, not by itself organ dysfunction documentation. There's no documented hypotension, altered mentation, or other organ dysfunction.
- Query compliance: A query must be supported by clinical indicators and must not lead the physician to a predetermined answer. Asking 'Query severe sepsis?' with no organ dysfunction indicator is a leading, non-compliant query.
- What IS appropriate: A non-leading clarification query asking the physician to clarify the diagnosis - e.g., 'Please clarify the diagnosis: sepsis (specify type), sepsis with organ dysfunction, or pneumonia with bacteremia?' with the supporting indicators listed neutrally.
- Financial pressure is not a justification. The $9,200 DRG difference is irrelevant to whether a query is clinically warranted. Queries driven by reimbursement violate compliance standards.
- Documentation gap: The discharge summary should reconcile the admission diagnosis. A query to clarify whether sepsis was present on admission and resolved is legitimate if indicators support it.
2. If the physician responds 'sepsis, resolved,' how should the coder assign the principal diagnosis, and what documentation standard applies?
Read the worked answer
- Principal diagnosis selection: The principal diagnosis is the condition established after study to be chiefly responsible for the admission. If the physician documents sepsis as present on admission and treated, sepsis may be principal even if resolved by discharge - 'resolved' status does not negate that it was the reason for admission.
- But documentation must be clear. 'Resolved sepsis' in the discharge summary alone, without admission documentation of sepsis, is ambiguous. The coder should review the entire record; if the admission note supports sepsis as the reason for admission, sepsis can be principal.
- POA status: Sepsis present on admission must be documented. If the physician's documentation supports it was present on admission, assign POA = Y.
- Coding standard: Code only what the physician documents; do not infer sepsis from lactate or antibiotics alone. If documentation is contradictory, query rather than assume.
- Takeaway: The coder cannot upgrade to severe sepsis without organ dysfunction documentation, and cannot assign sepsis solely on lab/medication inference.