TRV-2026-1341Certified recordPeer-reviewed

Mapping AI Ethics Integration in Postgraduate Health Professions Education: A Scoping Review Through the Lenses of Principlism and Transformative Learning

Background: Artificial intelligence (AI) is disrupting healthcare and health professions education (HPE), creating complex ethical challenges. Despite existing governance frameworks, postgraduate and continuing professional development (CPD) learners require stronger micro-level ethical competence. However, AI-ethics remains insufficiently integrated into postgraduate/CPD curricula with few real-world reflective and interprofessional strategies, raising concerns regarding ethical preparedness. The aim of this st…

Education · Problem Space — documented harm · certified 2026-10-14 · v1 · article view · machine-readable

Current reading — problem

AI ethics teaching for postgraduate and continuing-development health learners is limited, superficial and weakly evaluated. That leaves doubts about whether clinicians are ethically prepared for AI in healthcare.

What this doesn’t fix

The evidence base is small, at sixteen sources, and mostly non-empirical. It reflects a strong Western worldview, and most studies predate generative AI, which limits how far the findings apply to current tools and settings.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1341, v1: “Mapping AI Ethics Integration in Postgraduate Health Professions Education: A Scoping Review Through the Lenses of Principlism and Transformative Learning.” Truvace, 2026-10-14. /record/TRV-2026-1341 (accessed at citation time). sha256 6b790cb5cb1a314f…

Calibration history

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

  1. Certifiedv16b790cb5cb1a…

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