TRV-2026-1829Certified recordPeer-reviewed

Automated Calculation of the Pediatric Emergency Care Applied Research Network (PECARN) Intra-Abdominal Injury Rule from Unstructured Emergency Department Notes Using a Large Language Model

Objective: The Pediatric Emergency Care Applied Research Network (PECARN) intra-abdominal injury clinical prediction rule identifies children at very low risk for clinically significant intra-abdominal injury after blunt abdominal trauma. However, retrospective evaluation of the rule's use in practice requires resource-intensive chart review. We investigated whether large language models (LLMs) can automatically calculate PECARN intra-abdominal injury risk scores from real-world unstructured emergency department…

Health · Good Space — documented gain · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

An LLM read unstructured emergency notes and produced PECARN intra-abdominal injury risk scores closely matching clinician-derived scores, which could reduce the chart review needed to evaluate how the rule is used.

What this doesn’t fix

The analysis was retrospective, drew on only two urban pediatric emergency departments, and included just 196 children with complete notes, so it does not show how the model performs prospectively or elsewhere.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1829, v1: “Automated Calculation of the Pediatric Emergency Care Applied Research Network (PECARN) Intra-Abdominal Injury Rule from Unstructured Emergency Department Notes Using a Large Language Model.” Truvace, 2026-10-18. /record/TRV-2026-1829 (accessed at citation time). sha256 66431d0f2c232421…

Calibration history

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

  1. Certifiedv166431d0f2c23…

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