Skip to content
#software testing Open access

The Translational Gap in Neonatal Sepsis Prediction: A Scoping Review of Prospective Artificial Intelligence Validations in the NICU

Oct 2026 · Open Science Framework

Abstract

Background and Clinical Context Neonatal sepsis remains one of the leading causes of morbidity and mortality among premature infants in the Neonatal Intensive Care Unit (NICU). Because the clinical signs of sepsis in premature infants are often subtle and non-specific, diagnosis is frequently delayed, leading to rapid deterioration. In recent years, Artificial Intelligence (AI) and Machine Learning (ML) have emerged as highly promising tools to predict sepsis hours or even days before clinical onset by analyzing continuous physiological data (such as heart rate variability) and electronic health records. However, a critical "translational gap" exists. The current scientific literature is overwhelmed with retrospective, in silico models trained on historical databases (like MIMIC-III) that have never been tested on real patients. Despite the technological hype, very few algorithms have successfully transitioned from the computer science laboratory to bedside implementation in the NICU. Purpose and Objectives The primary purpose of this scoping review is to critically map the current landscape of AI and ML models that have achieved prospective, real-time clinical validation for predicting neonatal sepsis in the NICU. Rather than evaluating the mathematical accuracy of theoretical models, this research aims to investigate the practical realities of bedside AI deployment. The core objectives are to: Isolate the pioneering studies that have successfully connected predictive algorithms to patient monitors and clinical workflows in real-time. Identify and categorize the translational barriers preventing widespread clinical adoption of these technologies. Evaluate the clinical utility of the predictive alerts (lead time) generated by these models prior to the standard clinical suspicion of sepsis. Methodology The project follows a rigorous scoping review methodology, guided by the PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses Extension for Scoping Reviews) framework. A highly specific search strategy is applied across medical and biomedical engineering databases, including PubMed (MEDLINE), Embase, and IEEE Xplore. The study utilizes a strict "bedside filter" for eligibility: all retrospective models are systematically excluded. Data extraction focuses on algorithm specifications, continuous vital sign inputs, predictive lead time, and operational implementation challenges reported by the clinical teams. Expected Outcomes and Clinical Impact This research is expected to expose the profound disparity between AI development and real-world clinical application in neonatology. By synthesizing data from prospective validations, the expected outcomes include: Identification of Key Implementation Barriers: A structured analysis of the practical challenges of AI in the NICU, including hardware/software interoperability issues, high rates of false positives leading to "alarm fatigue" among nursing staff, and the "black box" phenomenon that hinders physician trust. A Paradigm Shift in Research Focus: The findings will provide a strong evidence base to argue that future research funding and efforts must shift away from redundant retrospective data mining and toward prospective clinical trials. Blueprint for Future AI Deployment: By understanding what went wrong—or right—in the few models that reached the bedside, this project will offer actionable insights for healthcare policymakers, biomedical engineers, and neonatologists to design better, workflow-integrated digital health solutions. Ultimately, this project aims to advance the conversation around precision medicine and digital care, ensuring that AI serves as a functional, life-saving tool for vulnerable premature infants rather than just a theoretical engineering concept.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.