TRV-2026-1789Version 1 · Certified

Written 2026-10-18 06:54:15 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1789
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-18T06:54:15.086635Z
status: published
lens: g_space
sector: health
headline: Conventional statistical and machine learning-based prediction of neonatal outcomes in late-onset fetal growth restriction
dek: Objectives To evaluate associations between antenatal fetal biometric and Doppler parameters and neonatal outcomes in late-onset fetal growth restriction (FGR), and to evaluate machine learning models for neonatal outcome prediction. Methods This retrospective cohort included 137 singleton pregnancies. Continuous missing values were completed using a single iterative chained-equations procedure. Maternal characteristics, fetal biometric measurements, and Doppler parameters, including umbilical artery pulsatility…
gain_title: Machine learning models built on fetal biometry, Doppler and maternal data predicted birth weight and neonatal sepsis with moderate accuracy, supporting conventional statistical findings in late-onset FGR.
problem_title: (none)
trace_subject: (none)
gain_reading: Machine learning models built on fetal biometry, Doppler and maternal data predicted birth weight and neonatal sepsis with moderate accuracy, supporting conventional statistical findings in late-onset FGR.
gain_evidence: neonatal sepsis had the highest classification AUC (0.850) | Machine learning models showed moderate predictive performance and confirmed findings from conventional statistical analyses
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers analyzed 137 singleton pregnancies complicated by late-onset fetal growth restriction. They compared conventional statistics and regression with machine learning models, using prenatal ultrasound measurements, Doppler indices and maternal characteristics to predict outcomes such as NICU admission, transient tachypnea and sepsis.

The work suggests that routinely collected prenatal data can flag newborns at higher risk, and that machine learning largely agrees with traditional methods rather than clearly outperforming them. The sample is small and retrospective, and the models have not been tested on outside populations, so clinical usefulness is still unproven.
limitation: The authors state the findings should be interpreted in light of the retrospective design and the lack of external validation of the models.
tag: Evidence-backed gain
key_points: The retrospective cohort included 137 singleton pregnancies with late-onset fetal growth restriction. | In final logistic models, maternal age, previous abortions and estimated fetal weight predicted NICU admission. | Previous cesarean delivery predicted transient tachypnea of the newborn, while maternal age and estimated fetal weight predicted neonatal sepsis. | Machine learning reached a cross-validated R2 of 0.592 for birth weight and an AUC of 0.850 for neonatal sepsis.
rundown: The study assessed associations between antenatal fetal biometric and Doppler parameters, including umbilical artery and middle cerebral artery pulsatility indices and the cerebroplacental ratio, and neonatal outcomes. Missing continuous values were filled using a single iterative chained-equations procedure.

NICU admission was linked to higher maternal age and to lower gestational age, fetal biometric measurements, estimated fetal weight, birth weight, Apgar scores and umbilical cord pH after false discovery rate correction.

The birth-weight linear model had the highest explanatory power, with an adjusted R2 of 0.662. Machine learning models were evaluated with repeated 5-fold cross-validation and showed moderate predictive performance.
sources:
- peer_reviewed | Journal of Perinatal Medicine | https://doi.org/10.1515/jpm-2026-0344 | 2026-10-07
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
d5b44350f2b7043b142780022717f6f430fb74764ad34171924d97b69f7d27c9
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1789 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.