Emerging evidence
Published recordHealthGood Space
More
Clinical Utility of Tumor-Detect Artificial Intelligence Algorithm for Detection of Prostate Cancer on Transurethral Resection Specimen
- Truvace record
- TRV-2026-2909raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Benchmark or lab evaluation
- Sources
- 1 sourcePeer-reviewed
- sha256
- 4cd817e7865d…check it
Artificial intelligence (AI)-based tumor detection algorithms are increasingly being integrated into digital pathology workflows. This study evaluated the performance of the Tumor-Detect AI algorithm for identifying prostate cancer in transurethral resection of prostate (TURP) specimens, which are diagnostically challenging due to tissue fragmentation and small incidental tumor foci. Eighty-one whole-slide images from 11 TURP specimens, including six specimens diagnosed as benign prostatic hyperplasia and five s…
The gain
In a study of 81 slides from 11 prostate resection specimens, PathAI's Tumor-Detect algorithm identified all five cancer-positive specimens (100% specimen-level sensitivity), with slide-level sensitivity of 88% and specificity of 86% against a pathologist's ground truth.
What this doesn’t fix
The study analysed only 11 specimens (81 slides) from a single comparison against one pathologist's ground truth, and false positives arose from complex glandular architecture, clear cell change and high-grade prostatic intraepithelial neoplasia.
Sources
1 on file- International Journal of Surgical Pathologydoi:10.1177/10668969261493447
Cite this record
v1Truvace Impact Record TRV-2026-2909, v1: “Clinical Utility of Tumor-Detect Artificial Intelligence Algorithm for Detection of Prostate Cancer on Transurethral Resection Specimen.” Truvace, 2026-11-14. /record/TRV-2026-2909 (accessed on the day you copy it). sha256 4cd817e7865d17bf…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2909 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.
ace