TRV-2026-1631Certified recordPeer-reviewed

Does it Fit? Testing a Novel Pediatric Surgical Risk Calculator in Africa

Background Low- and middle-income countries (LMICs), particularly Sub-Saharan Africa, experience a high burden of surgical disease and a disproportionately high postoperative morbidity and mortality. Although machine learning based pediatric surgical risk calculators (SRCs) have been developed to support clinical decision making, most are derived from high-income settings and may not generalize well to LMIC populations. We previously developed a pediatric surgical risk calculator using multinational LMIC data; h…

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

Current reading — gain

In a 1,670-child validation cohort, the machine learning calculator predicted in-hospital mortality better than ASA class alone and separated low-risk from high-risk children.

Current reading — problem

The calculator performed poorly in neonates and left most patients in an intermediate risk group that gives no useful guidance for decisions.

What this doesn’t fix

Performance was low in neonates, the model was systematically miscalibrated until recalibrated, and about two thirds of patients fell in an intermediate risk group that did not help decision making.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1631, v1: “Does it Fit? Testing a Novel Pediatric Surgical Risk Calculator in Africa.” Truvace, 2026-10-16. /record/TRV-2026-1631 (accessed at citation time). sha256 0d8845843ab374cf…

Calibration history

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

  1. Certifiedv10d8845843ab3…

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