TRV-2026-2114Certified recordPeer-reviewed

Non-contrast CT radiomics for identifying nonfunctioning kidneys: a multicenter development and external validation study

In urological practice, the decision to resect or preserve a kidney with obstruction, tumor or atrophy is based on split renal function, although SPECT renal dynamic scintigraphy as the reference standard is resource-intensive. We developed and externally validated a non-contrast CT radiomics model to identify nonfunctioning kidneys and support urological decision-making in this setting. In this three-center retrospective study (TRIPOD+AI), adults underwent non-contrast CT and SPECT renal dynamic scintigraphy wi…

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

Current reading — gain

A radiomics machine learning model using routine non-contrast CT identified nonfunctioning kidneys with high negative predictive value, potentially reducing unnecessary SPECT scintigraphy and informing nephrectomy versus kidney-sparing decisions.

What this doesn’t fix

The study is retrospective, and the advantage over the combined baseline was not statistically significant in one external cohort. External sensitivity of the random forest at fixed thresholds was lower than internally.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2114, v1: “Non-contrast CT radiomics for identifying nonfunctioning kidneys: a multicenter development and external validation study.” Truvace, 2026-10-21. /record/TRV-2026-2114 (accessed at citation time). sha256 a77580e7d051083b…

Calibration history

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

  1. Certifiedv1a77580e7d051…

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