65/100

Moderate evidence

GainPublished recordHealthGood Space

Electronic Children's Hospital Early Warning Score: Development and Validation of a Novel Machine Learning Algorithm Predicting Critical Deterioration Events in a Retrospective, Single-Center Cohort

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

Objective To develop and validate a novel, machine learning prediction model for critical deterioration events. Design Retrospective cohort study. Setting Single quaternary care freestanding pediatric hospital. Patients All patients up to 21 years old admitted to acute care wards (excluding cardiac and psychiatry units) between January 2012 and June 2023. Interventions None. Measurements and main results The primary outcome was a critical deterioration, defined as utilization of advanced respiratory support or c…

The gain

In a retrospective study of 179,074 pediatric hospitalizations at one hospital, the eCHEWS machine learning score had a positive predictive value of 11.4% versus 1.8% for the legacy CHEWS at about 44% sensitivity, cutting the number needed to alert from 55 to 9.

Sources

1 on file
  1. Pediatric Critical Care Medicinedoi:10.1097/pcc.0000000000004112
    Peer-reviewed2026-11-13

Cite this record

v1

Truvace Impact Record TRV-2026-2906, v1: “Electronic Children's Hospital Early Warning Score: Development and Validation of a Novel Machine Learning Algorithm Predicting Critical Deterioration Events in a Retrospective, Single-Center Cohort.” Truvace, 2026-11-14. /record/TRV-2026-2906 (accessed on the day you copy it). sha256 c675d179d802f37f…

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. Publishedv1c675d179d802…

    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-2906 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.