Sepsis in the ICU — And How ML Could Help Stop It
Imagine you’re a nurse managing six patients in an intensive care unit. It’s hour nine of a twelve-hour shift. You’re charting vitals, managing medications, responding to alarms. One of your patients, a 72-year-old man recovering from abdominal surgery, looks stable. His numbers aren’t alarming. Nothing is flagging. Over the next six hours, his heart rate creeps up. His blood pressure dips slightly. His breathing becomes a little faster. Each change, on its own, looks unremarkable. Together, they tell a story that won’t become obvious until it’s almost too late: he is developing sepsis.
What Is Sepsis?
Sepsis is not a disease you catch. It’s what happens when your body’s response to an infection spirals out of control. Instead of fighting the infection, the immune system begins attacking the body’s own tissues and organs. Blood pressure drops. Organs start to fail and time becomes the enemy. Every hour of delayed treatment increases the risk of death by roughly 7% and yet, because the early signs are subtle and easy to miss — especially in an ICU where every patient has abnormal vitals — sepsis is often caught too late.
In the United States alone, an estimated 350,000 people die from sepsis every year 1, more than those who die from stroke, prostate cancer, breast cancer, and opioid overdoses combined. It is the leading cause of death in hospitals and the most expensive condition to treat, costing the healthcare system over $62 billion annually.2
Why Is It So Hard to Catch Early?
The challenge with sepsis is that it doesn’t announce itself. It develops gradually, through patterns that are hard for humans to track in real time, especially when one nurse is responsible for multiple critically ill patients simultaneously.
Current clinical tools like qSOFA and SIRS criteria give nurses simple checklists to assess sepsis risk. Check three boxes, add up the score. These tools are better than nothing, but they have real limitations. They look at a single snapshot in time. They don’t account for trends. And they rely on a nurse remembering to run the check in the first place.
Some hospitals, including those using Epic’s electronic health record system, do have automated sepsis alerts built in. But these come with a problem: alert fatigue. A study of one hospital’s sepsis alert system found that nearly 88% of alerts were cancelled or timed out without action.3 A University of Michigan study of Epic’s own Sepsis Model found it missed 67% of actual sepsis patients while still firing alerts on 18% of all hospitalized patients.4 An alert that gets ignored — or fires so often it loses meaning — isn’t saving anyone.
The deeper issue is explainability. Current automated alerts tell a nurse that something might be wrong, but not why. Without knowing which specific vitals are driving the concern, the nurse has no clear action to take. The signal is there. It’s just buried in noise, spread across hours of data, and too often delivered without context.
What If a Machine Was Watching?
For my data science senior project, I’m building a Sepsis Early Warning System using real ICU data from the PhysioNet Computing in Cardiology Challenge 2019, a dataset containing over 20,000 de-identified patient records from actual intensive care units.
Each patient record contains hourly readings of vital signs and lab values: heart rate, temperature, blood pressure, oxygen saturation, respiration rate, white blood cell count, lactate levels, and others. Each row is labeled — sepsis eventually developed, or it didn’t.
The goal is to train a machine learning model to recognize the pattern that precedes sepsis onset, up to 12 hours before a clinician would traditionally identify it. Not by looking at one number but by looking at how all the numbers move together over time.
My motivation for building this system goes beyond the technical challenge. ICU nurses already carry one of the most demanding workloads in healthcare, managing multiple critically ill patients, documenting vitals, responding to alarms, all within a 12-hour shift that leaves little room for error. A tool that flags risk early doesn’t just help patients. It gives nurses better information at the right moment, reducing the cognitive burden of having to catch what the data is quietly trying to say. Better tools mean better care, and a less impossible job.
Why 12 Hours Matters
Twelve hours of advance warning in the ICU is huge. It’s the difference between a nurse proactively administering antibiotics and fluids before a crisis, versus scrambling to stabilize a patient who is already in septic shock.
Early intervention means shorter ICU stays. Fewer organ failures. Less cost. Lower Deaths.
What Comes Next
This is the first of three posts documenting my journey building this system from scratch.
In the next post, I’ll get into the technical details: how I cleaned and processed 20,000 messy ICU patient files, what features the model actually learns from, and how XGBoost compares to simpler baseline approaches.
In the final post, I’ll walk through deploying the model as a live web application and reflect on what building this project taught me about the gap between research and real world clinical deployment.
References
1 Sepsis Alliance. (2022). Sepsis Alliance Updates Key Number of Annual Sepsis Casualties. https://www.sepsis.org/news/sepsis-alliance-updates-key-number-of-annual-sepsis-casualties/
2 End Sepsis. Sepsis Fact Sheet. https://www.endsepsis.org/what-is-sepsis/sepsis-fact-sheet-2/
3 Parajon et al. (2020). Study of Alert Fatigue, Effectiveness, and Accuracy in the Development of a New Sepsis Best Practice Alert. Society of Hospital Medicine. https://shmabstracts.org/abstract/study-of-alert-fatigue-effectiveness-and-accuracy-in-the-development-of-a-new-sepsis-best-practice-alert/
4 Infectious Disease Advisor. (2021). Epic Sepsis Model Poorly Predictive Due to Low Sensitivity, Inadequate Calibration. https://www.infectiousdiseaseadvisor.com/news/epic-sepsis-model-is-poor-predictor-and-has-tendency-to-cause-alert-fatigue/
This project was developed using the PhysioNet CinC Challenge 2019 dataset.