63/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Dichotomisation and limited antenatal signal constrain prediction of early postpartum depressive symptoms: A secondary analysis of 1634 women

Truvace record
TRV-2026-2951raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
8de866170582…check it

Antenatal screening with the Edinburgh Postnatal Depression Scale (EPDS) guides postnatal follow-up. We quantified its performance against early postpartum depressive symptoms and asked whether psychological measures or machine learning recover information discarded at the cutoff. Secondary analysis of 1634 women assessed with the EPDS and attachment and coping measures in the third trimester, and with the EPDS again within one week of delivery. Antenatal screening (≥ 12) was evaluated against early postpartum s…

The problem

In a secondary analysis of 1,634 women, an 18-variable machine learning model (AUC 0.708) did no better than the raw antenatal Edinburgh score (0.708) at predicting early postpartum depressive symptoms in any of 20 repeats.

What this doesn’t fix

The outcome, assessed about one week after delivery, overlaps with postpartum blues, only two timepoints were available, and this secondary analysis of one cohort was not preregistered.

Sources

1 on file
  1. Journal of Affective Disordersdoi:10.1016/j.jad.2026.122731
    Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2951, v1: “Dichotomisation and limited antenatal signal constrain prediction of early postpartum depressive symptoms: A secondary analysis of 1634 women.” Truvace, 2026-11-16. /record/TRV-2026-2951 (accessed on the day you copy it). sha256 8de8661705824a90…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv18de866170582…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2951 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.