TRV-2026-1725Certified recordPeer-reviewed

UroVision: a new artificial intelligence software for functional magnetic resonance urography evaluation in children with congenital anomalies of the kidney and urinary tract

Objectives This study compared UroVision, a novel AI-based tool for automated three-dimensional (3D) segmentation and magnetic resonance urography (MRU) functional analysis, with the validated ImageJ MRU software, focusing on split renal function (SRF) and drainage curve classification in children with congenital anomalies of the kidney and urinary tract (CAKUT). Materials and methods MRU examinations in children with CAKUT were retrospectively analysed using UroVision and ImageJ MRU. UroVision functional assess…

Health · Good Space — documented gain · certified 2026-10-17 · v1 · article view · machine-readable

Current reading — gain

In a retrospective set of 100 kidneys, an AI tool for automated MRU analysis produced results comparable to the validated ImageJ MRU software, with excellent reproducibility between and within readers.

What this doesn’t fix

The study was retrospective and small (50 patients), and the functional parameters showed only moderate correlation with the reference software, so agreement was not uniformly strong.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1725, v1: “UroVision: a new artificial intelligence software for functional magnetic resonance urography evaluation in children with congenital anomalies of the kidney and urinary tract.” Truvace, 2026-10-17. /record/TRV-2026-1725 (accessed at citation time). sha256 1593c5e360d938ac…

Calibration history

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

  1. Certifiedv11593c5e360d9…

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