Moderate evidence
Published recordHealthGood Space
More
Demoralization syndrome in hemodialysis patients: Development and validation of an interpretable machine learning prediction model
- Truvace record
- TRV-2026-3083raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- e84ca4b59242…check it
Demoralization syndrome (DS)-an existential distress state marked by hopelessness, helplessness, and loss of meaning-is a prevalent yet underrecognized affective comorbidity among maintenance hemodialysis (MHD) patients. Unlike depression, it stems from impaired coping capacity and carries distinct suicidal ideation risk, yet no practical prediction tool exists for early identification in routine care. To develop and externally validate a parsimonious, interpretable machine learning model for predicting early DS…
The gain
In a multicenter cohort study of 592 hemodialysis patients, a 12-variable machine learning model predicted demoralization syndrome at 5 months with an AUC of 0.922 in external validation of 245 patients, matching a 28-variable model.
What this doesn’t fix
Recall was 0.652, so the model missed about a third of patients who developed demoralization, and it was assessed only for prediction, not for effects on patient care.
Sources
1 on file- Journal of Affective Disordersdoi:10.1016/j.jad.2026.122759
Cite this record
v1Truvace Impact Record TRV-2026-3083, v1: “Demoralization syndrome in hemodialysis patients: Development and validation of an interpretable machine learning prediction model.” Truvace, 2026-11-21. /record/TRV-2026-3083 (accessed on the day you copy it). sha256 e84ca4b59242fefc…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3083 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.
ace