56/100

Moderate evidence

GainPublished recordHealthGood Space

A pulse oximetry warning system predicts severity of late-onset sepsis in very low birth weight neonates

Truvace record
TRV-2026-2944raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
f343ab4a3f9b…check it

Late-onset sepsis (LOS) causes morbidity and mortality in very-low birthweight (VLBW) neonates. We previously developed a machine learning model, the Pulse Oximetry Warning System (POWS), to predict LOS in the next 24 h. The neonatal Sequential Organ Failure Assessment (nSOFA) score predicts sepsis mortality. We hypothesized that POWS scores would differentiate severe LOS events, defined by nSOFA >4, from milder events. We conducted a multicenter, retrospective cohort study including VLBW infants diagnosed with…

The gain

In a multicenter retrospective study of 89 late-onset sepsis episodes in 84 very low birth weight infants, the Pulse Oximetry Warning System score rose more steeply in the 24 hours before severe episodes (30% of cases) than before milder ones.

What this doesn’t fix

The study was a retrospective cohort analysis of 89 episodes in 84 infants, so it shows an association with severity but not that acting on the score improves outcomes.

Sources

1 on file
  1. Pediatric Researchdoi:10.1038/s41390-026-05665-2
    Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2944, v1: “A pulse oximetry warning system predicts severity of late-onset sepsis in very low birth weight neonates.” Truvace, 2026-11-15. /record/TRV-2026-2944 (accessed on the day you copy it). sha256 f343ab4a3f9bf552…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1f343ab4a3f9b…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2944 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.