Moderate evidence
Published recordHealthGood Space
More
The Session-specific Risk Index (SRI) in psychotherapy: Developing longitudinal session-by-session machine learning algorithms to predict the likelihood of non-response to treatment
- Truvace record
- TRV-2026-3066raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 1e29f2d30c65…check it
Introduction This study aimed to develop and introduce an implementation-oriented, session-specific metric called the Session-specific Risk Index (SRI), which defines the likelihood of treatment non-response in psychotherapy. The SRI integrates baseline information with real-time clinical data from each session, providing a continuously updated probability of non-response to treatment. Methods We used observational data from an outpatient clinic, including 1,010 psychotherapy patients. We compared the performanc…
The gain
In an observational study of 1,010 outpatient psychotherapy patients, an elastic net model predicted non-response by session 20 with accuracy of .65-.70 and AUC of .70-.77 across the first ten sessions.
What this doesn’t fix
The index was built from observational data at one outpatient clinic and has not been tested in routine practice; the authors say benefits apply only if it is implemented in clinical practice.
Sources
1 on file- Psychotherapy and Psychosomaticsdoi:10.1159/pps/aemag026
Cite this record
v1Truvace Impact Record TRV-2026-3066, v1: “The Session-specific Risk Index (SRI) in psychotherapy: Developing longitudinal session-by-session machine learning algorithms to predict the likelihood of non-response to treatment.” Truvace, 2026-11-20. /record/TRV-2026-3066 (accessed on the day you copy it). sha256 1e29f2d30c65399d…
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-3066 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