TruaceTracing the truth around AISaturday, September 12, 2026
TRV-2026-0996Certified recordPeer-reviewed

"Reports in Medical Illustration (REMIL) in Musculoskeletal Radiology: An Evaluation of Evolving AI Models"

Objective Radiology reports remain predominantly text-based, requiring clinicians and patients to mentally reconstruct imaging findings. Reports in Medical Illustration (REMIL) represent an emerging approach in which artificial intelligence (AI) generates simplified visual summaries directly from report text. This study aimed to evaluate the feasibility, anatomical accuracy, and clinical utility of AI-generated REMIL in musculoskeletal (MSK) radiology. Methods Twenty-five MSK imaging cases were selected. Identic…

Health · The Trace — both readings · certified 2026-09-06 · v1 · article view · machine-readable

Current reading — gain

AI systems can generate rapid visual summaries directly from musculoskeletal radiology report text, with the best model producing clinically useful images in a majority of tested cases.

Current reading — problem

Current AI models frequently produce visually plausible but anatomically inaccurate illustrations, with major errors across all models, making them unreliable for unsupervised clinical use.

What this doesn’t fix

Evaluation was limited to 25 selected MSK cases assessed by two radiologists, with performance dropping in complex cases involving multiple structures or planes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0996, v1: “"Reports in Medical Illustration (REMIL) in Musculoskeletal Radiology: An Evaluation of Evolving AI Models".” Truvace, 2026-09-06. /record/TRV-2026-0996 (accessed at citation time). sha256 ce033e6381c09b31

Calibration history

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

  1. Certifiedv1ce033e6381c0

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