Moderate evidence
Published recordHealthGood Space
More
OPXrayNet: a high-precision, explainable AI framework for transformative opportunistic osteoporosis screening utilizing multi-site X-ray imaging
- Truvace record
- TRV-2026-2913raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 70af8c6b9dcf…check it
Objective: This study aimed to develop and validate OPXrayNet, an automated deep-learning framework for opportunistic osteoporosis (OP) screening using multi-site skeletal X-ray images, to address the limitations of single-site analysis and poor interpretability in existing methods. Materials and methods: This retrospective, multicenter diagnostic study utilized 16,347 annotated X-ray images from 2186 patients. The reference standard was OP diagnosis based on DXA T-score (≤ -2.5). OPXrayNet integrated YOLOv8 for…
The gain
In a retrospective multicenter study of 2,186 patients, the OPXrayNet model detected osteoporosis on routine X-rays with 80.1% accuracy on an internal test set and an AUC of 0.844 on external validation, using DXA T-scores as the reference.
What this doesn’t fix
The study was retrospective, and the observed advantage over other models was described only as a numerical difference of 3.9% on external validation.
Sources
1 on file- European Radiologydoi:10.1007/s00330-026-13023-3
Cite this record
v1Truvace Impact Record TRV-2026-2913, v1: “OPXrayNet: a high-precision, explainable AI framework for transformative opportunistic osteoporosis screening utilizing multi-site X-ray imaging.” Truvace, 2026-11-14. /record/TRV-2026-2913 (accessed on the day you copy it). sha256 70af8c6b9dcf203a…
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-2913 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