TRV-2026-1858Certified recordPeer-reviewed

The medical physicist's role in the artificial intelligence era: an updated EFOMP curricular and professional framework

Purpose Five years after the European Federation of Organizations for Medical Physics (EFOMP) published its first curricular framework for artificial intelligence (AI) in medical physics, the updated core curricula for radiology, radiotherapy and nuclear medicine have incorporated AI as a core competency rather than an addendum, a change consistent with the framework's principal recommendation. This paper examines the resulting educational landscape and defines the next stage of AI competency for the profession.…

Health · The Trace — both readings · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

The updated EFOMP radiology, radiotherapy and nuclear medicine curricula now treat AI as a core competency, which supports safer clinical integration of AI.

Current reading — problem

Six competency gaps common to all three medical physics subspecialties remain beyond the entry-level curricula, and the curricula diverge in ECTS allocation, coverage of recent AI architectures and treatment of the EU AI Act.

What this doesn’t fix

The study is a expert-deliberation and curriculum-comparison exercise, so it offers a proposed framework and recommendations rather than evidence of outcomes for patients or practice.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1858, v1: “The medical physicist's role in the artificial intelligence era: an updated EFOMP curricular and professional framework.” Truvace, 2026-10-18. /record/TRV-2026-1858 (accessed at citation time). sha256 4f80ffbdc9f71849…

Calibration history

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

  1. Certifiedv14f80ffbdc9f7…

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