TruaceTracing the truth around AITuesday, September 15, 2026
TRV-2026-1096Certified recordPeer-reviewed

Predicting early psychiatric readmission among people with major depressive disorder: A machine learning analysis from the prospective multicentre DEEP READ study

Background Major depressive disorder (MDD) is associated with high relapse rates, with around 20% of inpatients experiencing readmission within 90 days after discharge. Routinely collected clinical information may help identify individuals at higher risk of readmission. Machine learning (ML) models could complement more traditional statistical approaches by exploring complex relationships among multiple vulnerability factors. Methods The DEEP READ study is a prospective, multicentre cohort study conducted across…

Health · The Trace — both readings · certified 2026-09-15 · v1 · article view · machine-readable

Current reading — gain

A Random Forest trained on 22 routine clinical variables predicted unplanned 90-day psychiatric readmission in adults with MDD with moderate discrimination.

Current reading — problem

The model showed variable cross-validation performance down to 0.59 AUC and is not validated for clinical implementation without further calibration and utility assessment.

What this doesn’t fix

Model was only internally evaluated with stratified 5-fold cross-validation and lacks external validation, calibration assessment, and demonstrated clinical utility.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1096, v1: “Predicting early psychiatric readmission among people with major depressive disorder: A machine learning analysis from the prospective multicentre DEEP READ study.” Truvace, 2026-09-15. /record/TRV-2026-1096 (accessed at citation time). sha256 cc8d484b8b1f7225

Calibration history

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

  1. Certifiedv1cc8d484b8b1f

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