60/100

Moderate evidence

GainPublished recordHealthGood Space

Predicting ISUP upgrading from biopsy to radical prostatectomy using an interpretable machine learning model with mpMRI-diagnosed prostatitis: a retrospective study

Truvace record
TRV-2026-3018raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
ac9b5109813e…check it

The International Society of Urological Pathology (ISUP) grade upgrading from biopsy to radical prostatectomy (RP) occurs in approximately 30%-40% of prostate cancer patients and may compromise treatment planning. Although multiparametric MRI (mpMRI) improves lesion characterization, prostatitis-like signal changes can mimic clinically significant cancer and confound radiological interpretation; however, no predictive model has incorporated mpMRI-diagnosed prostatitis as a variable for ISUP upgrading. This singl…

The gain

In a retrospective study of 503 men who had prostate biopsy then surgery, a random forest model predicted which cases would be upgraded in grade with an AUC of 0.823, and MRI-diagnosed prostatitis added predictive value beyond PI-RADS scoring.

What this doesn’t fix

The study was a single-center retrospective analysis of 503 patients, with the model tested only on a split of the same cohort rather than an external dataset.

Sources

1 on file
  1. Asian Journal of Andrologydoi:10.4103/aja202643
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3018, v1: “Predicting ISUP upgrading from biopsy to radical prostatectomy using an interpretable machine learning model with mpMRI-diagnosed prostatitis: a retrospective study.” Truvace, 2026-11-18. /record/TRV-2026-3018 (accessed on the day you copy it). sha256 ac9b5109813e5f1a…

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. Publishedv1ac9b5109813e…

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