TRV-2026-1845Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1845 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-18T18:13:55.644387Z status: published lens: p_space sector: health headline: The Role of Interpreters in Supporting Resilience and Implications for Artificial Intelligence dek: Background Interpreters help millions of patients with a non-English language preference (NELP) navigate the healthcare system. Artificial intelligence (AI) tools are rapidly improving and undergoing testing and implementation for interpretation purposes. However, little is understood about interpreters' roles beyond direct interpretation, such as how they may promote resilience, which supports patient safety. Understanding these additional roles is critical as AI tools expand in interpretation. Objective To und… gain_title: (none) problem_title: AI interpretation tools do not yet support the resilience-enhancing behaviors interpreters perform, so adopting them without care could open patient safety gaps for patients with a non-English language preference. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: AI interpretation tools do not yet support the resilience-enhancing behaviors interpreters perform, so adopting them without care could open patient safety gaps for patients with a non-English language preference. problem_evidence: these behaviors are not yet supported by AI interpretation tools | to avoid safety gaps quick_read: Researchers held three focus groups with 17 medical interpreters about their work with patients who have a non-English language preference during ambulatory visits for new or worsening symptoms. Using Hollnagel's resilience framework, they identified eleven interpreter behaviors that go beyond strict interpretation and support patient safety. This matters because AI tools for interpretation are being tested and implemented quickly, and the study suggests they could miss functions that protect patients during diagnosis. The findings come from interpreter experiences rather than from a test of AI tools, so the size of any actual safety gap is not measured. limitation: The evidence comes from a small sample of 17 interpreters in focus groups examining their experiences, not from direct evaluation of AI interpretation tools, so safety gaps are inferred rather than measured. tag: Evidence-backed problem key_points: Seventeen medical interpreters took part in three focus groups plus result-checking. | Eleven resilience-supporting behaviors were identified across four potentials: respond, monitor, learn and anticipate. | Behaviors under responding include managing communication flow, strengthening the patient's voice and holding pre-briefings. | Interpreters also monitor patient emotion, team dynamics and the impact of technology, and they anticipate future threats to patient safety. rundown: The study focused on ambulatory care because of the high risk of misdiagnosis as patients move across language barriers and multiple encounters in the health system. Interpreters described their experiences assisting patients during diagnostic processes. The analysis was deductive and organized around four resilience potentials. Responding included viewing the interpretation role broadly, while monitoring included tracking patient understanding. Learning drew on interpreters' cultural backgrounds and work experiences, and anticipating included identifying system improvements. The authors conclude that implementing AI tools and their workflows will require careful consideration of these behaviors to avoid safety gaps. sources: - peer_reviewed | Journal of General Internal Medicine | https://doi.org/10.1007/s11606-026-10850-4 | 2026-10-05 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- c0bda12f439912d31d5a2fdccb28215a1aaf014064e73c83c600550a7fbbbb8d
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1845 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.
ace