Emerging evidence
Published recordHealthProblem Space
More
Artificial intelligence and digital technologies transforming neonatal respiratory assessment: a scoping review
- Truvace record
- TRV-2026-1275raw data (JSON)
- Version
- v3Revised
- First published
- Evidence type
- Commentary, opinion, or narrative review
- Sources
- 1 sourcePeer-reviewed
- sha256
- 7a804cccc415…check it
Digital technologies and artificial intelligence (AI) have been increasingly incorporated into neonatal care, particularly in respiratory assessment. However, structured evidence regarding their clinical applications, performance, and limitations remains limited. This scoping review analyzed 35 studies published between 2019 and 2026 to map the use of digital technologies and AI in neonatal respiratory assessment. The findings showed that these approaches are mainly applied to predictive models, medical image an…
The problem
A review of 35 studies found AI and digital tools for newborn breathing assessment lack robust external validation, use small samples and have no standardized protocols, so they are not ready for routine clinical use.
What this doesn’t fix
Evidence limited by methodological heterogeneity, lack of strong external validation, small sample sizes, and absence of protocol standardization, with no demonstrated clinical impact yet.
Sources
1 on file- Journal of Perinatologydoi:10.1038/s41372-026-02894-5
Cite this record
v3Truvace Impact Record TRV-2026-1275, v3: “Artificial intelligence and digital technologies transforming neonatal respiratory assessment: a scoping review.” Truvace, 2026-11-05. /record/TRV-2026-1275 (accessed on the day you copy it). sha256 7a804cccc415e265…
Change history
3 versionsEvery change made to this record since it was first published, and why.
Voice pass: plainer wording and study attribution; no facts or figures changed.
Editorial pass: sharper headline; gain/problem restated as concrete outcomes; refiled trace to p_space (gain unsupported, problem outcome).
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-1275 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