TruaceTracing the truth around AITuesday, July 21, 2026
TRV-2026-0458Certified recordPeer-reviewed

Artificial intelligence in undergraduate medical education: an updated scoping review

BACKGROUND: The irrevocable alteration of medical education due to widespread access to large language models (LLMs) in 2022, and the concomitant surge in AI-related literature, has prompted us to update the evolving impact of AI on undergraduate medical education (UGME). METHODS: The scoping review adhered to the framework of Arksey and O'Malley. A literature search was conducted in April 2024 on PubMed, Scopus, Web of Science Core Collection, ERIC, and Google Scholar using the terms "UGME", "medical students",…

Health · The Trace — both readings · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — gain

Some institutions have begun integrating AI into undergraduate medical curricula as AI use rapidly increases across basic and clinical courses.

Current reading — problem

There is no standardized approach or consensus on AI competencies and ethical frameworks for undergraduate medical education, and no studies assessed impact on critical thinking or clinical reasoning.

What this doesn’t fix

No included studies measured AI's effect on critical thinking or clinical reasoning, and best evidence for implementation remains unclear.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0458, v1: “Artificial intelligence in undergraduate medical education: an updated scoping review.” Truvace, 2026-07-20. /record/TRV-2026-0458 (accessed at citation time). sha256 dce3f4348ad553a0

Calibration history

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

  1. Certifiedv1dce3f4348ad5

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