TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0791Certified recordPeer-reviewed

Real-time artificial intelligence-based anatomy recognition in single-port transvesical enucleation of the prostate

To evaluate the feasibility and accuracy of an artificial intelligence (AI) model to assist surgeons through automated real-time detection and segmentation of key anatomical structures during robot-assisted single-port transvesical enucleation of the prostate (STEP). This retrospective single-centre study utilised surgical videos from patients undergoing single-port robot-assisted transvesical prostate enucleation performed by a single expert surgeon. Selected frames extracted from these surgical videos were man…

Health · G Space — documented gain · certified 2026-08-16 · v1 · article view · machine-readable

Current reading — gain

An AI model trained on surgical video frames achieved automated real-time detection and segmentation of bladder neck, adenoma and peripheral zone during robot-assisted prostate enucleation with high Dice scores and >60 fps inference.

What this doesn’t fix

Pilot feasibility study was retrospective, single-centre, and based on videos from a single expert surgeon with only 611 annotated frames, limiting generalizability.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0791, v1: “Real-time artificial intelligence-based anatomy recognition in single-port transvesical enucleation of the prostate.” Truvace, 2026-08-16. /record/TRV-2026-0791 (accessed at citation time). sha256 223c0ff270653891

Calibration history

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

  1. Certifiedv1223c0ff27065

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