Moderate evidence
Published recordHealthProblem Space
More
Machine-Learning Derived Individual Risk Prediction in Congenital Heart Surgery: Development and internal validation of risk prediction models for in-hospital mortality after congenital heart surgery using data from the Pediatric Cardiac Critical Care Consortium (PC4) registry
- Truvace record
- TRV-2026-2956raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 46b4fdbd669f…check it
Background Machine learning (ML) methods may improve prediction of individual risk of mortality risk after congenital heart surgery (CHD) by identifying nonlinear relationships/novel combinations of variables. Improved risk discrimination may improve outcomes by optimizing resource allocation and patient surveillance. Methods Children and adolescents (age≤18 years) undergoing CHD surgery at Pediatric Cardiac Critical Care Consortium hospitals 9/1/2014-12/30/2019 were studied. Non-collinear potential predictors w…
The problem
In a registry study of 51,475 congenital heart operations at 52 US-linked hospitals, random forest and gradient boosting models predicted in-hospital death no better than logistic regression, with reclassification gains that were at best modest and not significant.
What this doesn’t fix
The models were developed and internally validated on registry data from one consortium, and the authors say further research is needed on whether more comprehensive data or advanced computational techniques add value.
Sources
1 on file- American Heart Journaldoi:10.1016/j.ahj.2026.107655
Cite this record
v1Truvace Impact Record TRV-2026-2956, v1: “Machine-Learning Derived Individual Risk Prediction in Congenital Heart Surgery: Development and internal validation of risk prediction models for in-hospital mortality after congenital heart surgery using data from the Pediatric Cardiac Critical Care Consortium (PC4) registry.” Truvace, 2026-11-16. /record/TRV-2026-2956 (accessed on the day you copy it). sha256 46b4fdbd669fdb0d…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2956 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.
ace