TruaceTracing the truth around AIThursday, August 27, 2026
TRV-2026-0908Certified recordPeer-reviewed

International Application of Artificial Intelligence for Lesion Detection on Digital Breast Tomosynthesis: Comparing Western and Eastern Databases

Rationale and objectives The international application of artificial intelligence (AI) for lesion detection based on digital breast tomosynthesis (DBT) is limited due to disease variations among populations. We hypothesized that lesion detection models trained on either the Western or Eastern DBT dataset would exhibit reduced performance on another dataset. We proposed transfer learning to enhance lesion detection across DBT databases. Materials and methods The Western database (94 patients) was obtained from th…

Health · The Trace — both readings · certified 2026-08-27 · v1 · article view · machine-readable

Current reading — gain

Transfer learning enhanced AI lesion detection performance when models were adapted from one regional DBT database to another.

Current reading — problem

AI lesion detection models trained on Western or Eastern DBT data showed reduced performance when applied to the other population due to differences in lesion types.

What this doesn’t fix

Findings are based on small samples of 94 and 157 patients with Eastern data from a single anonymous center, limiting broad international generalizability.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0908, v1: “International Application of Artificial Intelligence for Lesion Detection on Digital Breast Tomosynthesis: Comparing Western and Eastern Databases.” Truvace, 2026-08-27. /record/TRV-2026-0908 (accessed at citation time). sha256 c2824ae1af4d160d

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1c2824ae1af4d

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0908 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.