TRV-2026-1805Certified recordPeer-reviewed

A Hybrid Human-AI Workflow for Ultrasound Report Quality Control: A Multicenter Performance and Efficiency Evaluation

Rationale and objectives: This study evaluated a hybrid human-AI workflow for ultrasound report quality assurance using multicenter retrospective data. Materials and methods: 786 anonymized ultrasound reports covering 22 examination categories were collected from four hospitals. Reports containing naturally occurring or implanted errors were matched across arms. GPT-4o and DeepSeek-v3 performed initial screening before review by six human reviewers (HRs). HR with blinded expert over-reading (HR-ex) served as con…

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

Current reading — gain

Pairing GPT-4o or DeepSeek-v3 screening with human review matched single-reviewer accuracy on ultrasound reports while cutting median audit time from 51.0 s to about 11 to 12 s.

What this doesn’t fix

The study was retrospective and the authors state that prospective real-world validation is required before routine clinical implementation; the hybrid also trailed expert over-reading on accuracy and false negatives.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1805, v1: “A Hybrid Human-AI Workflow for Ultrasound Report Quality Control: A Multicenter Performance and Efficiency Evaluation.” Truvace, 2026-10-18. /record/TRV-2026-1805 (accessed at citation time). sha256 01300edaa7cea936…

Calibration history

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

  1. Certifiedv101300edaa7ce…

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