TRV-2026-1916Certified recordPeer-reviewed

Readability and Content Integrity of Discharge Documents for Common Pediatric Orthopaedic Procedures Before and After Artificial Intelligence Simplification

Background: Caregivers of pediatric orthopaedic surgical patients routinely receive discharge documents written at reading levels exceeding established health literacy recommendations. This disparity creates a significant barrier to comprehension and adherence to postoperative instructions. While artificial intelligence (AI) language models offer a scalable solution for simplification of medical text, a systematic evaluation of the ability to preserve critical content in surgical discharge materials remains lack…

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

Current reading — gain

Simplifying caregiver discharge documents with ChatGPT lowered mean reading level by about four grade levels, bringing 11 of 15 documents to a sixth-grade level or below.

Current reading — problem

The same simplified documents contained 35 content flags, including 12 safety-critical errors, and three needed clinician revision because of omissions before they could be used clinically.

What this doesn’t fix

The study used only 15 documents covering three pediatric orthopaedic conditions and one model with a single standardized prompt, so results may not generalize; the source also classifies it as Level III evidence.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1916, v1: “Readability and Content Integrity of Discharge Documents for Common Pediatric Orthopaedic Procedures Before and After Artificial Intelligence Simplification.” Truvace, 2026-10-19. /record/TRV-2026-1916 (accessed at citation time). sha256 3e4fae32fdbff97d…

Calibration history

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

  1. Certifiedv13e4fae32fdbf…

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