TRV-2026-2002Certified recordPeer-reviewed

Artificial intelligence in personalized internal dosimetry for radiopharmaceutical therapy: a narrative mini-review

Personalized internal radiation dosimetry supports individualized radiopharmaceutical therapy but remains difficult to implement because workflows require repeated quantitative imaging, segmentation, registration, kinetic modeling, and absorbed-dose calculation. This mini-review summarizes current evidence on artificial intelligence across the personalized dosimetry workflow and considers clinical readiness. A narrative PubMed search was completed in early 2026 and covered peer-reviewed studies published from 20…

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

Current reading — gain

Deep learning cut Y-90 SPECT reconstruction error and sped up image registration, easing workflow burdens that make individualized radiopharmaceutical dosimetry hard to implement.

Current reading — problem

AI-based clinical decision support for dosimetry rests mainly on retrospective, single-center evidence and still needs prospective, multicenter validation before routine clinical use.

What this doesn’t fix

The evidence for AI-based clinical decision support is mainly retrospective and single-center, and decision-support tools still need prospective, multicenter validation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2002, v1: “Artificial intelligence in personalized internal dosimetry for radiopharmaceutical therapy: a narrative mini-review.” Truvace, 2026-10-20. /record/TRV-2026-2002 (accessed at citation time). sha256 ff104b4ee9303c95…

Calibration history

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

  1. Certifiedv1ff104b4ee930…

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