TRV-2026-1632Certified recordPeer-reviewed

Human or AI-generated voiceover for chemotherapy education video? Evidence from knowledge and practice tests improvement among cancer patients by pharmacists

BackgroundEducational videos play a crucial role in enhancing healthcare delivery. Developing an educational video designed to improve patient understanding of catastrophic treatment. During the video's creation, two voiceover methods were employed: human voices and artificial intelligence (AI)-generated voices. To date, the impact of voice-over origin-whether human or AI-on patient knowledge acquisition remains unexplored and warrants further investigation. This study aimed to assess the differences in knowledg…

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

Current reading — gain

Chemotherapy education videos narrated with AI-generated voices improved cancer patients' knowledge and attitudes across key topics, with no difference found between AI and human voice education.

What this doesn’t fix

The authors report a sustained trend favoring human-voice videos even though no difference was found between human and AI voice education, so equivalence of AI narration is not firmly established.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1632, v1: “Human or AI-generated voiceover for chemotherapy education video? Evidence from knowledge and practice tests improvement among cancer patients by pharmacists.” Truvace, 2026-10-17. /record/TRV-2026-1632 (accessed at citation time). sha256 8323aeeb35459179…

Calibration history

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

  1. Certifiedv18323aeeb3545…

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