TRV-2026-2157Certified recordPeer-reviewed

Associations of patient safety-related perceptions and lifelong learning-related attitudes with critical trust in AI/digital clinical tools among medical students: a cross-sectional study

Patient safety, lifelong learning, and the safe use of artificial intelligence (AI) are increasingly relevant to undergraduate medical education, but their interrelationships remain poorly understood. This study examined medical students’ patient safety-related perceptions, lifelong learning-related attitudes, and critical trust in AI/digital clinical tools. This single-center cross-sectional survey was conducted at Gaziantep University Faculty of Medicine, Türkiye, between April and May 2026. Of 366 submitted r…

Health · Problem Space — documented harm · certified 2026-10-22 · v1 · article view · machine-readable

Current reading — problem

Few medical students had recent patient safety or AI/digital clinical tool training, and reported AI training was inversely associated with critical trust, leaving preparation for safe AI use thin.

What this doesn’t fix

The study is a single-center, exploratory cross-sectional survey using study-developed items, so it cannot establish causal or curricular effects, and the estimated association size varied with how scores were constructed.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2157, v1: “Associations of patient safety-related perceptions and lifelong learning-related attitudes with critical trust in AI/digital clinical tools among medical students: a cross-sectional study.” Truvace, 2026-10-22. /record/TRV-2026-2157 (accessed at citation time). sha256 3d5081d9e02aad8b…

Calibration history

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

  1. Certifiedv13d5081d9e02a…

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