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

Evaluating Artificial Intelligence Translation Tools for Language Equivalence of Oncology-Informed Consent Forms From English to Spanish

Approximately 8% of the US population speaks primary languages other than English. Limited English proficiency (LEP) contributes to under-representation of Hispanic patients in oncology clinical trials. Although certified translation services exist, they are time-consuming and costly. Artificial intelligence (AI)-generated translations of informed consent forms (ICFs) could provide low-cost alternatives, but data on accuracy and safety remain limited. We evaluated language equivalence of English-to-Spanish trans…

Health · The Trace — both readings · certified 2026-08-06 · v1 · article view · machine-readable

Current reading — gain

General-purpose AI tool ChatGPT-4o achieved near-certified translation equivalence for English-to-Spanish oncology informed consent forms.

Current reading — problem

Low-cost AI translations of oncology informed consent forms showed variable language equivalence and remain unsuitable for clinical use without human review.

What this doesn’t fix

Exploratory evaluation limited to three oncology ICFs and two physician raters, with variable equivalence across tools and domains.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0663, v1: “Evaluating Artificial Intelligence Translation Tools for Language Equivalence of Oncology-Informed Consent Forms From English to Spanish.” Truvace, 2026-08-06. /record/TRV-2026-0663 (accessed at citation time). sha256 791353815237e3ab

Calibration history

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

  1. Certifiedv1791353815237

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