TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0729Certified recordPeer-reviewed

Mortality prediction of road traffic crash with artificial intelligence: a systematic review

Background Road traffic crashes cause substantial global mortality and disability. Conventional injury severity scores may not fully capture the complex interactions among demographic, clinical, crash and environmental factors. Artificial intelligence and machine learning may improve mortality prediction by modelling non-linear patterns in traffic crash data. Methods This systematic review followed Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) 2020 guidance. PubMed/MEDLINE, Web of S…

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

Current reading — gain

Systematic review found AI and machine learning may improve mortality prediction after road traffic crashes by modelling non-linear patterns among demographic, clinical and crash factors.

Current reading — problem

Clinical translation of AI mortality prediction after road traffic crashes remains limited by insufficient external validation, inconsistent handling of class imbalance, and incomplete reporting of tuning and missing data strategies.

What this doesn’t fix

Findings were synthesised narratively due to heterogeneity, and only two studies reported external validation, limiting generalizability.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0729, v1: “Mortality prediction of road traffic crash with artificial intelligence: a systematic review.” Truvace, 2026-08-10. /record/TRV-2026-0729 (accessed at citation time). sha256 b61e2f507dfc6340

Calibration history

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

  1. Certifiedv1b61e2f507dfc

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