Moderate evidence
Published recordHealthGood Space
More
Development of a Multimodal Model Combining Imaging and Clinical Data to Predict Bone Cement Leakage During Vertebroplasty for Fresh Thoracolumbar Compression Fractures
- Truvace record
- TRV-2026-2954raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- cf890418579f…check it
Background: Bone cement leakage is a common complication of percutaneous vertebroplasty (PVP), but perioperative risk stratification remains challenging. Existing models based on single-source clinical or imaging features have limited performance. This study aimed to develop and validate multimodal artificial intelligence (AI) models integrating clinical, imaging, and radiomics features to predict bone cement leakage during PVP. Methods: This multicenter study included 486 treated vertebrae from 378 patients at…
The gain
In a study of 486 treated vertebrae from 378 patients, multimodal AI models predicted cement leakage during vertebroplasty with AUCs of 0.902-0.939 on internal testing and 0.834-0.925 in a prospective cohort, above single-source models.
What this doesn’t fix
CT scans came from different scanners and protocols, the models predict radiographic rather than symptomatic leakage, the external and prospective cohorts were small, and the authors say further evaluation in larger and more diverse populations is required.
Sources
1 on file- JOR SPINEdoi:10.1002/jsp2.70227
Cite this record
v1Truvace Impact Record TRV-2026-2954, v1: “Development of a Multimodal Model Combining Imaging and Clinical Data to Predict Bone Cement Leakage During Vertebroplasty for Fresh Thoracolumbar Compression Fractures.” Truvace, 2026-11-16. /record/TRV-2026-2954 (accessed on the day you copy it). sha256 cf890418579f9bfd…
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-2954 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