68/100

Moderate evidence

GainPublished recordHealthGood Space

Enhancing diagnostic precision for BI-RADS 4a breast nodules: A multimodal AI model integrating ultrasound radiomics, hemodynamic signatures, and clinical profiles

Truvace record
TRV-2026-1239raw data (JSON)
Version
v2Revised
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
a488ad0efd7f…check it

Background Breast Imaging Reporting and Data System (BI-RADS) 4a nodules represent a diagnostic dilemma, with a malignancy rate ranging from 2% to 10%. The majority of these nodules prove benign after biopsy, leading to unnecessary invasive procedures, patient anxiety, and healthcare costs. Current clinical practice lacks a reliable, noninvasive tool to accurately distinguish benign from malignant BI-RADS 4a lesions. Emerging evidence suggests that integrating multiparametric ultrasound data with clinical factor…

The gain

On 90 held-out breast nodules, a model combining ultrasound, blood-flow and clinical data caught all malignant ones (100% sensitivity) with 86.1% specificity and an AUC of 0.95.

Sources

1 on file
  1. Peer-reviewed2026-10-01

Cite this record

v2

Truvace Impact Record TRV-2026-1239, v2: “Enhancing diagnostic precision for BI-RADS 4a breast nodules: A multimodal AI model integrating ultrasound radiomics, hemodynamic signatures, and clinical profiles.” Truvace, 2026-11-04. /record/TRV-2026-1239 (accessed on the day you copy it). sha256 a488ad0efd7fdbeb…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2a488ad0efd7f…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Publishedv11ef02cc104a7…

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