Moderate evidence
Published recordHealthGood Space
More
Computed tomography derived cardiometabolic biomarkers in high-risk breast cancer using fully automated deep learning algorithms
- Truvace record
- TRV-2026-2964raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 627f7a71c9ca…check it
Purpose Cardiometabolic disease and obesity are important factors when considering breast cancer risk and survivorship. We aimed to utilize a fully automated deep learning algorithm to evaluate CT-derived cardiometabolic biomarkers in patients with breast cancer. Methods We applied fully automated deep learning algorithms to derive cardiometabolic markers from baseline computed tomography (CT) abdomen scans of females with breast cancer diagnosed between 2016 - 2018 at Johns Hopkins. Results Among 127 females (6…
The gain
In a study of 127 women with breast cancer at Johns Hopkins, automated deep learning on CT scans measured body composition, liver fat and aortic plaque, and found myosteatosis and menopausal status tracked adiposity and aortic calcification where BMI did not.
What this doesn’t fix
The analysis covered only 127 women treated at a single institution, Johns Hopkins, which limits how far the findings generalize.
Sources
1 on file- Breast Cancer Research and Treatmentdoi:10.1007/s10549-026-08122-0
Cite this record
v1Truvace Impact Record TRV-2026-2964, v1: “Computed tomography derived cardiometabolic biomarkers in high-risk breast cancer using fully automated deep learning algorithms.” Truvace, 2026-11-16. /record/TRV-2026-2964 (accessed on the day you copy it). sha256 627f7a71c9ca619a…
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-2964 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