68/100

Moderate evidence

GainPublished recordHealthGood Space

Prostate-Specific Membrane Antigen PET/CT Segmentation Guided by Vision Language Models Embedding Clinical Report Semantics

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

Whole-body prostate-specific membrane antigen (PSMA) PET/CT segmentation remains challenging: manual contouring is unsustainable, and image-only artificial intelligence models often misclassify physiologic uptake as malignant, causing high false-positive rates. These limitations underscore the need for segmentation strategies that incorporate the nuclear medicine expertise encoded in PET/CT reports but not used by current models. We investigated whether routine PET/CT reports improve automated lesion segmentatio…

The gain

In a study of 284 prostate cancer patients, an AI model that read PET/CT report text alongside the scans cut false-positive lesions by nearly 4 per patient with BiomedVLP versus an image-only model.

What this doesn’t fix

The test set held only 41 cases from one dataset, and the authors call for external validation, true-positive-only analysis in independent cohorts, and PSMA-specific language pretraining.

Sources

1 on file
  1. Journal of Nuclear Medicinedoi:10.2967/jnumed.126.272702
    Peer-reviewed2026-11-12

Cite this record

v1

Truvace Impact Record TRV-2026-2901, v1: “Prostate-Specific Membrane Antigen PET/CT Segmentation Guided by Vision Language Models Embedding Clinical Report Semantics.” Truvace, 2026-11-14. /record/TRV-2026-2901 (accessed on the day you copy it). sha256 0f1e0e3b7286d37f…

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

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