Abstract

A nurse-triggered sepsis alert called "Code Sepsis" was implemented for early recognition and management of sepsis. The researchers analyzed its impact on antimicrobial use and identified factors associated with infection as source of Code Sepsis. The medical records of hospitalized patients with Code Sepsis between January 1 and June 30, 2018, were reviewed. Patients were classified as "Infection" when probable or definitive infection was identified or "No Infection" when a probable or definitive noninfectious source was identified. Patients were categorized as "Escalation" with addition or change to broader-spectrum antimicrobials or "No Escalation" with no change or change to narrower-spectrum antimicrobials. Escalation was classified as "Indicated" with appropriate escalation or "Not Indicated" with inappropriate escalation. Logistic regression model was used to identify factors associated with Infection as Code Sepsis trigger. Code Sepsis was activated in 529 patients, with Escalation in 246 (46.5%) and No Escalation in 283 (53.5%) patients. Escalation was Indicated in 157 (63.8%) and Not Indicated in 89 (36.2%) patients. Infection was identified in 356 (67.3%) and No Infection in 173 (32.7%) patients. History of HIV (odds ratio [OR] = 2.75, p = 0.03), temperature > 38.3°C or < 36°C (OR = 2.63, p < 0.01), and respiratory rate > 20/minute (OR = 1.56, p = 0.02) were associated with Infection, while surgery within 3 days (OR = 0.30, p < 0.01) was associated with No Infection. One hospital system's Code Sepsis inadvertently identified patients without infections and led to antimicrobial overuse. By refocusing Code Sepsis on early recognition of severe sepsis and septic shock only, the organization hopes to optimize resource utilization and improve patient outcomes.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call