TRV-2026-1411Certified recordPeer-reviewed

Performance Evaluation of an Artificial Intelligence-Assisted Digital Morphology System for Bone Marrow Aspirate Examination

Introduction: Morphological examination of bone marrow aspirates (BMA) remains essential for the diagnosis of hematologic diseases, but conventional microscopy is labor-intensive and subject to interobserver variability. Methods: A total of 158 samples from patients were analyzed. Differential counts obtained by optical microscopy were compared with those of the CellaVision BMA Application used according to its intended workflow of automated preclassification followed by expert review. The two methods were compa…

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

Current reading — gain

In 158 patient samples, automated preclassification plus expert review gave differential counts comparable with conventional microscopy for most nucleated cells, with 96.8% to 99.4% agreement at key decision thresholds.

Current reading — problem

Agreement was weaker for basophils and plasma cells, and sensitivity at the 20% blast threshold was only 77.3%, so expert review remains necessary.

What this doesn’t fix

The findings come from a single-center series and the system was assessed only within an expert-reviewed workflow, so expert review and further validation remain necessary.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1411, v1: “Performance Evaluation of an Artificial Intelligence-Assisted Digital Morphology System for Bone Marrow Aspirate Examination.” Truvace, 2026-10-15. /record/TRV-2026-1411 (accessed at citation time). sha256 9822a5e93ce803c1…

Calibration history

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

  1. Certifiedv19822a5e93ce8…

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