68/100

Moderate evidence

GainPublished recordHealthGood Space

Multicenter external validation of CT-based deep learning for proximal femoral fracture classification and quantitative fracture-line assessment

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

To develop and externally validate a CT-based deep learning CAD system for proximal femoral fracture classification and fracture-line angle quantification and to preliminarily evaluate its clinical utility in a reader study. In this multicenter retrospective study, coronal CT images from four institutions were used for training (259 patients, 19,844 annotated images) and internal validation (91 patients, 92 hips). External validation included 200 patients from independent institutions scanned with CT systems fro…

The gain

In a multicenter study with 200 externally validated patients, a CT deep learning system classified proximal femoral fractures with 91.5% accuracy, and residents' sensitivity for non-displaced femoral neck fractures rose from 0.47 to 0.78 with its help.

What this doesn’t fix

Performance was lower on external data than internal data, and the six-reader study was exploratory and preliminary, so the clinical benefit is not yet established.

Sources

1 on file
  1. Skeletal Radiologydoi:10.1007/s00256-026-05447-1
    Peer-reviewed2026-11-20

Cite this record

v1

Truvace Impact Record TRV-2026-3085, v1: “Multicenter external validation of CT-based deep learning for proximal femoral fracture classification and quantitative fracture-line assessment.” Truvace, 2026-11-21. /record/TRV-2026-3085 (accessed on the day you copy it). sha256 4df87eab04fac5be…

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

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