TRV-2026-1784Certified recordPeer-reviewed

Convolutional neural network for red blood cell transfusion prediction: A machine learning based study

Background Subjective, inconsistent clinician judgement on red blood cell (RBC) transfusion demand causes unnecessary blood wastage, increased perioperative safety risks, and poorly balanced hospital blood inventory. To tackle these persistent clinical limitations, we developed a workflow-adapted clinical decision support tool: a one-dimensional convolutional neural network (1D CNN) trained on routinely acquired haematological and clinical variables to stratify inpatient RBC transfusion volume categories. Method…

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

Current reading — gain

In a retrospective single-hospital cohort, the model forecast routine transfusion volume categories from 19 pre-transfusion variables, correctly identifying the dominant 2-unit class.

Current reading — problem

The model under-detected high-volume transfusion events, with weak performance in the minority classes of 3 units and 5 or more units, which limits clinical reliability for these cases.

What this doesn’t fix

The model was developed and tested in a single-centre retrospective cohort and under-detected high-volume transfusions, so generalisability and usefulness for rare, large transfusions remain unproven.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1784, v1: “Convolutional neural network for red blood cell transfusion prediction: A machine learning based study.” Truvace, 2026-10-18. /record/TRV-2026-1784 (accessed at citation time). sha256 0c815903b3a2e3ab…

Calibration history

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

  1. Certifiedv10c815903b3a2…

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