60/100

Moderate evidence

GainPublished recordHealthGood Space

Temporal stability of an electronic health record-driven machine learning model predicting type 2 diabetes among patients with mental illness

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

We previously trained and tested a machine learning model to predict incident type 2 diabetes (T2D) in patients with mental illness using electronic health record (EHR) data from routine clinical practice. This hyperparameter-tuned XGBoost model - based on information on sex, age and mean HbA1c within the past two years - predicts whether a patient will meet criteria for T2D in the two years following each contact to psychiatric services. The performance of such a model may drift over time due to changes in stan…

The gain

In a temporal validation study, an XGBoost model trained on 2013-2017 health records predicted type 2 diabetes two years ahead in psychiatric patients with AUROC of 0.80 to 0.87 across contacts in 2018 to 2023, declining only 0.004 per year.

What this doesn’t fix

The estimated yearly change in AUROC has a wide confidence interval (-0.024 to 0.016), and the authors stress that continued evaluation is needed.

Sources

1 on file
  1. Acta Neuropsychiatricadoi:10.1017/neu.2026.10105
    Peer-reviewed2026-11-13

Cite this record

v1

Truvace Impact Record TRV-2026-2891, v1: “Temporal stability of an electronic health record-driven machine learning model predicting type 2 diabetes among patients with mental illness.” Truvace, 2026-11-13. /record/TRV-2026-2891 (accessed on the day you copy it). sha256 f65415505cd244c2…

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. Publishedv1f65415505cd2…

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