TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0674Certified recordPeer-reviewed

Machine learning-enabled prediction of ART pregnancy outcomes: a systematic review and meta-analysis

Objective To systematically evaluate the diagnostic accuracy and methodological quality of machine learning (ML) prediction models for pregnancy outcomes after assisted reproductive technology (ART). Methods PubMed, Embase, the Cochrane Library, IEEE Xplore, MEDLINE, ClinicalTrials.gov, CNKI, Wanfang, and VIP were searched from inception to July 2026. Eligible studies developed or validated ML models to predict clinical pregnancy or live birth after ART. For studies reporting complete 2 × 2 contingency data, poo…

Health · The Trace — both readings · certified 2026-08-07 · v1 · article view · machine-readable

Current reading — gain

Machine learning models achieved moderate diagnostic accuracy for predicting clinical pregnancy or live birth after assisted reproductive technology, with pooled sensitivity 0.737 and specificity 0.789.

Current reading — problem

The evidence base for ML prediction of ART outcomes is limited by substantial heterogeneity and frequent high or unclear risk of bias, requiring prospective multi-center external validation before clinical use.

What this doesn’t fix

Evidence base limited by substantial heterogeneity (I2 97.7% and 99.0%) and frequent high or unclear risk of bias, with subgroup findings driven by a single prospective study.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0674, v1: “Machine learning-enabled prediction of ART pregnancy outcomes: a systematic review and meta-analysis.” Truvace, 2026-08-07. /record/TRV-2026-0674 (accessed at citation time). sha256 b9126d239081962f

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1b9126d239081

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0674 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.