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

Application of Artificial Intelligence (AI) in cancer symptom management for adult cancer survivors: a scoping review

Artificial Intelligence (AI) has been increasingly used in cancer survivorship to support symptom management. This scoping review aimed to map existing evidence on AI applications in cancer symptom management for adult cancer survivors, including AI model development, AI-enabled intervention delivery and adoption, symptom targets, key features of the AI approaches used, reported outcomes, influencing factors, and research gaps to inform future priorities. This scoping review was conducted in accordance with the…

Health · G Space — documented gain · certified 2026-08-17 · v1 · article view · machine-readable

Current reading — gain

AI-enabled intervention delivery for adult cancer survivors was associated with reported improvements in clinical and psychosocial outcomes, with model performance generally moderate to high across symptom tasks.

What this doesn’t fix

Evidence base is heterogeneous, early-stage, and context-dependent with variability in functionality, reporting, populations, settings, and designs, limiting generalisability and real-world usefulness beyond predictive accuracy.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0805, v1: “Application of Artificial Intelligence (AI) in cancer symptom management for adult cancer survivors: a scoping review.” Truvace, 2026-08-17. /record/TRV-2026-0805 (accessed at citation time). sha256 cfa394e67d0c28f3

Calibration history

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

  1. Certifiedv1cfa394e67d0c

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