68/100

Moderate evidence

GainPublished recordHealthGood Space

Machine learning explainability of acute toxicity in salvage prostate cancer radiotherapy: A multicentric investigation

Truvace record
TRV-2026-3086raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
3db26f675d56…check it

To develop and validate an explainable machine learning (ML) model for early prediction of grade ≥ 2 acute gastrointestinal (GI) and genitourinary (GU) toxicities in prostate cancer patients treated with salvage radiotherapy (SRT) post-prostatectomy. Patient-, surgical- and treatment-related data from 454 patients treated with SRT in three Italian centers were collected and analyzed. 271 patients from two centers served as the training and internal validation set, while 183 patients from the third institution we…

The gain

In a study of 454 post-prostatectomy patients at three Italian centres, a machine learning model predicted grade 2 or higher genitourinary toxicity from salvage radiotherapy with an AUC of 0.855 on an external test set of 183 patients.

What this doesn’t fix

Performance was lower on the external test set from the third centre than in internal validation, especially for gastrointestinal toxicity (AUC 0.706 versus 0.784).

Sources

1 on file
  1. Physica Medicadoi:10.1016/j.ejmp.2026.107215
    Peer-reviewed2026-11-19

Cite this record

v1

Truvace Impact Record TRV-2026-3086, v1: “Machine learning explainability of acute toxicity in salvage prostate cancer radiotherapy: A multicentric investigation.” Truvace, 2026-11-21. /record/TRV-2026-3086 (accessed on the day you copy it). sha256 3db26f675d56cfd6…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv13db26f675d56…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3086 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.