68/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Diagnostic performance of S-detect artificial intelligence compared with conventional breast ultrasound for lesion characterization: a prospective lesion-based study

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

Abstract Purpose The aim of this prospective study was to compare the diagnostic performance of conventional breast ultrasound (US) assessment with S-Detect artificial intelligence (AI) for differentiating benign from malignant breast lesions. The study was not designed to assess reduction in biopsy rates. Materials and Methods A total of 130 women with 130 target breast lesions were prospectively evaluated from January 2024 to December 2025. One target lesion was analyzed per patient. Each lesion underwent conv…

The problem

In a prospective study of 130 women with breast lesions, the S-Detect AI tool had 63.3% specificity and 67.7% accuracy versus 87.2% and 87.7% for conventional ultrasound, with 40 false positives against 14.

What this doesn’t fix

The study was not designed to assess reduction in biopsy rates, and only 21 of the 130 lesions were malignant; the authors say larger prospective reader studies with predefined management rules are needed.

Sources

1 on file
  1. Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2952, v1: “Diagnostic performance of S-detect artificial intelligence compared with conventional breast ultrasound for lesion characterization: a prospective lesion-based study.” Truvace, 2026-11-16. /record/TRV-2026-2952 (accessed on the day you copy it). sha256 797661fc7d36f147…

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

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