TRV-2026-2154Certified recordPeer-reviewed

AI-Powered CURA Application for Identifying At-Risk Pregnancies in Obstetrics Management (CURAte): protocol for a randomised controlled trial

Background: Early identification of high-risk pregnancies is a cornerstone of obstetric care, yet antenatal risk assessment in routine practice remains imprecise and highly variable. Evidence from contemporary cohort studies suggests that only a minority of pregnancies that subsequently experience adverse maternal or fetal/neonatal outcomes are identified as high risk in the first trimester, with reported detection rates in the range of 20%–30%. Despite rapid advances in machine-learning (ML) methods for clinica…

Health · Problem Space — documented harm · certified 2026-10-22 · v1 · article view · machine-readable

Current reading — problem

Routine antenatal risk assessment is imprecise: only about 20%–30% of pregnancies with later adverse outcomes are flagged as high risk in the first trimester, and no ML approach has been tested against standard care in an RCT.

What this doesn’t fix

This is a protocol only, so no outcome data exist; the hypothesised gains in accuracy and reduced adverse outcomes are untested, and the tool is intended only as decision support.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2154, v1: “AI-Powered CURA Application for Identifying At-Risk Pregnancies in Obstetrics Management (CURAte): protocol for a randomised controlled trial.” Truvace, 2026-10-22. /record/TRV-2026-2154 (accessed at citation time). sha256 89152b0eda93c2c7…

Calibration history

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

  1. Certifiedv189152b0eda93…

    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-2154 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.