TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0738Certified recordPeer-reviewed

Prediction of Clinically Meaningful Improvement After Internet-Delivered Cognitive Behavioral Therapy for Depression and Anxiety Disorders: Machine Learning-Based Predictive Model Development and Temporal Validation Study

Background Up to 50% of patients treated with internet-delivered cognitive behavioral therapy (ICBT) for depression and anxiety disorders do not experience clinically significant symptom reduction. Identifying these patients prior to the initiation of ICBT can support treatment planning. Objective The aim of this study was to enhance baseline prediction of clinically meaningful improvement in patients treated with ICBT for common psychiatric disorders in routine care, which could ultimately inform treatment plan…

Health · P Space — documented harm · certified 2026-08-12 · v1 · article view · machine-readable

Current reading — problem

Up to half of patients receiving internet-delivered CBT for depression and anxiety disorders fail to achieve clinically significant symptom reduction, complicating treatment planning at intake.

What this doesn’t fix

Polygenic scores did not improve prediction in this cohort and modeling setup, and validation was limited to temporal holdout rather than prospective external implementation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0738, v1: “Prediction of Clinically Meaningful Improvement After Internet-Delivered Cognitive Behavioral Therapy for Depression and Anxiety Disorders: Machine Learning-Based Predictive Model Development and Temporal Validation Study.” Truvace, 2026-08-12. /record/TRV-2026-0738 (accessed at citation time). sha256 a8d8c74ff662809b

Calibration history

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

  1. Certifiedv1a8d8c74ff662

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