Conference Coverage

VIDEO: Software predicts septic shock in hospitalized patients

View on the News

Daniel Ouellette, MD, FCCP, comments

Dr. Daniel Ouellette

Early identification and treatment of sepsis should lead to improved outcomes from this serious and life-threatening condition. A new computer-based system that will allow physicians to identify these patients more expeditiously and with greater certainty is likely to improve medical care. However, identification of septic patients is only the first step. Appropriate, evidence-based interventions must be rapidly initiated in septic patients if one is to save the lives of these critically ill individuals. A system that rapidly allows for patient identification, facilitates sepsis treatment bundles, and can rapidly incorporate physician decision-making will represent an ideal future goal.


 

AT ATS 2017

– Researchers have devised a program that can predict severe sepsis or septic shock about 12-30 hours in advance of its onset in hospitalized patients, a feat they hope will allow them to apply early interventions to stave off impending sepsis.

“We’d love to see a change in sepsis mortality. Will earlier recognition and implementation of the sepsis bundle – fluids, antibiotics, etc. – improve outcomes?” wondered Heather M. Giannini, MD, in a video interview at an international conference of the American Thoracic Society.

The computer program works by monitoring all the data that enter a patient’s electronic health record during hospitalization. Researchers developed it and designed it specifically for inpatients who are not in the intensive care unit or emergency department.

Results from initial testing during October-December 2015 in 10,448 patients hospitalized at one of three participating Philadelphia hospitals showed the program predicted subsequent severe sepsis or septic shock with a sensitivity of 26% and a specificity of 98%, reported Dr. Giannini, a researcher in the Center for Evidence-Based Practice at the University of Pennsylvania in Philadelphia. Analysis also showed a positive likelihood ratio of 13 for severe sepsis or septic shock actually occurring following an alert generated by the computer program, a level indicating a “very strong” ability to predict sepsis, she said.

Dr. Giannini and her associates developed the prediction program using a technique called “computational machine learning,” an alternative to standard logistic regression modeling that is better suited to analyzing large data sets and can better integrate outlier data points. They took EHR data for all non-ICU, non-ED inpatients at three Philadelphia hospitals during a 3-year period during 2011-2014 and had the program focus particularly on EHR data gleaned from the nearly 1,000 patients who developed severe sepsis or septic shock during the 12 hours preceding the start of these sepsis events. The analysis identified patients as having developed severe sepsis or shock if they had a blood draw positive for infection at the same time as having a blood lactate level above 2.2 mmol/L or a systolic blood pressure below 90 mm Hg.

To create the algorithm the machine-learning device compared the EHR entries for patients who developed severe sepsis or septic shock with EHR data from patients who did not, a process that involved hundred of thousands of data points, Dr. Giannini said. This identified 587 individual types of relevant EHR data entries and ranked them from most important to least important. Important, novel determinants of impending severe sepsis identified this way included anion gap, blood urea nitrogen, and platelet count. The development process also confirmed an important role for many classic markers of septic shock, such as respiration rate, heart rate, and temperature.

The researchers designed the algorithm to have a moderate level of sensitivity to avoid “alert fatigue” from generating too many alarms for impending severe sepsis. Their goal was for clinicians to receive no more than about 10 alerts per day for each hospital.

“We are satisfied with the sensitivity. We felt it was better to have too few alerts rather than overwhelm clinicians. About 10 alerts a day is reasonable,” Dr. Giannini explained. During initial 2015 testing, the system generated a daily average of 11 alerts.

Pages

Next Article: