TRV-2026-1687Certified recordPeer-reviewed

A Controlled Single-Speaker Evaluation of Ambient Voice Technologies' Speech-to-Text Function Using Narrated Surgical Case-Reports

Ambient voice technologies (AVT) utilise automatic speech recognition (ASR) and generative artificial intelligence for speech-to-text conversion, and are advocated as efficient, accurate tools for clinical documentation. We investigated (n = 8) AVT systems using surgical case-reports as narratives in a controlled single-speaker evaluation prioritising safety outcomes: specifically 3 commercial transcription-systems (Dragon-Medical-One, Heidi-Health, Tortus); 4 ASR speech-to-text Application Programming Interface…

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

Current reading — gain

Adding GPT-5 generative error correction to a GPT4oTranscribe pipeline reduced the share of transcripts with clinically significant Class 3 errors from 53% to 30%, resolving 51 of 89 such errors.

Current reading — problem

Every tested ambient voice system produced clinically significant Class 3 errors in 30-68% of transcripts, including 53 errors with potential for severe harm or death, mostly in medication and laboratory result details.

What this doesn’t fix

The evaluation used a single speaker and narratives derived from surgical case reports in a controlled setting, and the authors state that safety and effectiveness in clinical practice require further evaluation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1687, v1: “A Controlled Single-Speaker Evaluation of Ambient Voice Technologies' Speech-to-Text Function Using Narrated Surgical Case-Reports.” Truvace, 2026-10-17. /record/TRV-2026-1687 (accessed at citation time). sha256 57106dd0b8eff6fd…

Calibration history

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

  1. Certifiedv157106dd0b8ef…

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