TRV-2026-1810Certified recordPeer-reviewed

Development and Preliminary Evaluation of a Conversational Agent Delivering Problem-Solving Therapy for Family Caregivers of Children With a Chronic Health Condition: Multiphase Mixed Methods Study

Background Family caregivers of children with chronic health conditions experience substantial physical and mental health burdens, including burnout, anxiety, depression, fatigue, and sleep disturbances. Despite this need, validated digital mental health tools tailored to family caregivers remain limited. AI-powered conversational agents offer a promising approach for delivering on-demand, personalized mental health support, yet development and evaluation frameworks for this population are lacking. Objective Thi…

Health · Good Space — documented gain · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

In a single-session test with 38 caregivers, a Wizard-of-Oz version of COCO was rated acceptably usable and was followed by lower negative affect, sadness, guilt, and fatigue.

What this doesn’t fix

The user-facing results come from a single therapy session with a Wizard-of-Oz prototype, and the LLM version was evaluated only by research team members using personas, so real-world performance of the final AI agent is untested.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1810, v1: “Development and Preliminary Evaluation of a Conversational Agent Delivering Problem-Solving Therapy for Family Caregivers of Children With a Chronic Health Condition: Multiphase Mixed Methods Study.” Truvace, 2026-10-18. /record/TRV-2026-1810 (accessed at citation time). sha256 838e2e671128f5ce…

Calibration history

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

  1. Certifiedv1838e2e671128…

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