TruaceTracing the truth around AIWednesday, July 22, 2026
TRV-2026-0508Certified recordPeer-reviewed

Multiturn Large Language Model-Based Conversational Agents for Patients With Cancer and Caregivers: Scoping Review

Large language model (LLM)-based conversational agents are increasingly used in health care, yet their capacity to support genuine multiturn dialogue remains underexplored. In oncology, where patients and caregivers experience complex informational and emotional needs throughout the disease trajectory, conversational agents may support information provision, symptom consultation, and emotional assistance. However, research specifically examining multiturn conversational agents designed for patients with cancer a…

Health · P Space — documented harm · certified 2026-07-22 · v1 · article view · machine-readable

Current reading — problem

LLM-based multiturn chatbots for cancer patients and caregivers lack consistent reporting on safety risks and mitigation, and lack evaluation of conversational continuity and memory.

What this doesn’t fix

Evidence base is very small and early-stage, with only eight included studies focused on prototype development and heterogeneous evaluation, limiting generalizability about effectiveness or safety.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0508, v1: “Multiturn Large Language Model-Based Conversational Agents for Patients With Cancer and Caregivers: Scoping Review.” Truvace, 2026-07-22. /record/TRV-2026-0508 (accessed at citation time). sha256 35ed37609b751152

Calibration history

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

  1. Certifiedv135ed37609b75

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