Post-Discharge Sepsis Query Before Claim Drop

Yes, a query is appropriate because the record contains conflicting clinical indicators: the discharge summary says "sepsis, resolved," while the H&P describes hypotension and an elevated lactate that responded to fluids. The coder cannot resolve that conflict by choosing the more favorable diagnosis.

The query must be written, non-leading, and clinically focused:

• State the clinical indicators without interpreting them for the physician: hypotension responsive to 1 liter of normal saline, lactate 2.8, pneumonia, AKI, and the discharge summary language.
• Ask a clear question about whether sepsis was present on admission and whether it resolved, and whether the UTI was the source.
• Provide reasonable options, including "sepsis present on admission," "sepsis not present on admission," "UTI without sepsis," and "other (specify)." Do not offer only the option that increases reimbursement.
• Do not mention the DRG or dollar impact in the query. That is a compliance red flag.
• Address the physician by name and role, with a response deadline consistent with policy.

The CDI specialist should not use a verbal query because the patient is discharged and the policy prohibits it. The query should be sent to the covering attending or the physician who can attest, with a copy to the attending of record.

The main compliance risks are leading the physician, changing documentation without physician attestation, and delaying the claim beyond timely filing to capture a higher payment. The CDI specialist may not alter the record or select the sepsis diagnosis because it pays more. The physician must make the clinical determination.

If no response arrives before the 48-hour drop:

• Do not hold the claim indefinitely. Check the payer's timely filing limit and the hospital's policy on query-related holds. A short hold may be defensible if the response window is active, but the claim cannot be delayed solely for revenue optimization.
• Bill from the existing documentation if the hold expires. If the discharge summary is the final attestation and supports "sepsis, resolved," code from that documentation using standard coding rules and the present-on-admission status supported by the record. Do not code sepsis if the record does not support it.
• Continue the query after billing. If the physician later responds with a clarification, follow the organization's corrected-claim process if appropriate and compliant.
• Escalate through the physician advisor or medical staff process if non-response is chronic.

The CDI specialist should document the query, the response attempts, and the rationale for the billing decision.

The DRG impact should be known to the CDI specialist for prioritization but must not appear in the query or drive the clinical options. The query should stand on the clinical indicators: hypotension, lactate, fluid response, and conflicting documentation. If the indicators did not support sepsis, the specialist should not query for it merely because the DRG pays more.

Prevention measures include:

• Query templates reviewed by compliance to remove leading language and financial references.
• CDI education on the difference between a documentation clarification and a coding optimization query.
• Physician advisor review for recurrent conflicts between the discharge summary and admission documentation.
• Auditing a sample of sepsis queries for leading language, response quality, and documentation support.
• Tracking query outcomes by diagnosis, not only by reimbursement impact, to detect patterns of upcoding pressure.

The team should treat the $4,200 difference as a reason to resolve the documentation conflict, not as a reason to prefer one answer. If the physician responds that sepsis was present and resolved, the code should reflect that with the appropriate present-on-admission status. If the physician says the illness was a UTI without sepsis, that answer must be accepted even though it reduces payment.