TRV-2026-1959Certified recordPeer-reviewed

ThaCoder: an explainable deep learning framework for thalassemia screening using routine complete blood count: a multi-center validation study

Thalassemia remains a global public health challenge, yet definitive diagnosis via genetic testing is often restricted by high costs and infrastructure requirements. We aimed to develop and externally evaluate an interpretable deep-learning framework using routine complete blood count (CBC) parameters for thalassemia screening. Using 2317 CBC records from the internal derivation cohort, we implemented a two-stage analytical architecture. First, exploratory factor analysis (EFA) with Varimax rotation reduced nine…

Health · The Trace — both readings · certified 2026-10-20 · v1 · article view · machine-readable

Current reading — gain

A deep neural network using routine blood count values separated likely thalassemia cases from others in four external centers, and a simulation suggests it could cut genetic-testing referrals by about 76%.

Current reading — problem

The same model detected only about half of silent α-thalassemia carriers, so milder carriers are missed at the chosen threshold.

What this doesn’t fix

Sensitivity for silent α-thalassemia carriers was only 0.5270, the cost estimate comes from a preliminary simulation, and absolute risk estimates need site-specific recalibration.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1959, v1: “ThaCoder: an explainable deep learning framework for thalassemia screening using routine complete blood count: a multi-center validation study.” Truvace, 2026-10-20. /record/TRV-2026-1959 (accessed at citation time). sha256 b2a1a59c1ba812e6…

Calibration history

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

  1. Certifiedv1b2a1a59c1ba8…

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