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

Enhancing diagnostic safety: addressing knowledge gaps for using human factors tools in the safe and effective use of AI - a proposed research agenda

Introduction Identify knowledge gaps in applying artificial intelligence in clinical settings, using medical imaging as a primary use case to enhance diagnostic efficacy, efficiency, and patient and provider safety. Methods We convened a two-day workshop with 18 interdisciplinary experts from three countries. Experts represented quality and patient safety, human factors and systems engineering, radiology and other medical specialties, nursing, medical informatics, cognitive and perceptual psychology, psychometri…

Health · P Space — documented harm · certified 2026-08-14 · v1 · article view · machine-readable

Current reading — problem

Clinical AI deployment without human-factors tools risks automation bias, overreliance, fragmentation of care, and other unintended consequences that threaten diagnostic safety.

What this doesn’t fix

Findings derive from a two-day expert consensus workshop with 18 participants rather than empirical evaluation of deployed AI systems, limiting generalizability to specific clinical workflows.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0750, v1: “Enhancing diagnostic safety: addressing knowledge gaps for using human factors tools in the safe and effective use of AI - a proposed research agenda.” Truvace, 2026-08-14. /record/TRV-2026-0750 (accessed at citation time). sha256 440ad8884f439a92

Calibration history

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

  1. Certifiedv1440ad8884f43

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