TRV-2026-1681Certified recordPeer-reviewed

Human-in-the-Loop Suicide Risk Detection and Clinical Escalation in a Generative AI Mental Health Chatbot: Prospective Implementation Study

Background Mental illness is the leading cause of disability worldwide, affecting more than one billion individuals, and suicide accounts for 720,000 to 800,000 deaths annually. While AI-native mental health chatbots have the potential to fill a sizable gap between treatment need and workforce capacity, their rapid proliferation has outpaced the development of scalable procedures to identify, detect, and respond to suicidal ideation. Despite AI best practice recommendations to incorporate human oversight for saf…

Health · The Trace — both readings · certified 2026-10-17 · v1 · article view · machine-readable

Current reading — gain

A human-in-the-loop protocol combining universal screening and conversational detection was operationally feasible, starting clinician outreach about 11 minutes after risk alerts in a chatbot trial.

Current reading — problem

Clinicians successfully contacted only 30.9% of alerted participants in Phase 1 and 42.4% in Phase 2, leaving many flagged users without completed human assessment.

What this doesn’t fix

Contact and clinical assessment were not completed for a sizable share of alerted participants, and the effect of these procedures on clinical outcomes was not characterized.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1681, v1: “Human-in-the-Loop Suicide Risk Detection and Clinical Escalation in a Generative AI Mental Health Chatbot: Prospective Implementation Study.” Truvace, 2026-10-17. /record/TRV-2026-1681 (accessed at citation time). sha256 38a7154c24047d38…

Calibration history

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

  1. Certifiedv138a7154c2404…

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