TRV-2026-1687Version 1 · Certified

Written 2026-10-17 10:42:17 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1687
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-17T10:42:17.598145Z
status: published
lens: trace
sector: health
headline: A Controlled Single-Speaker Evaluation of Ambient Voice Technologies' Speech-to-Text Function Using Narrated Surgical Case-Reports
dek: 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…
gain_title: 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.
problem_title: 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.
trace_subject: Safety of AI speech-to-text transcription of surgical case narratives, with and without LLM error correction
gain_reading: 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.
gain_evidence: LLM-processing reduced the proportion of transcript-outputs affected (53% to 30%)
problem_reading: 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.
problem_evidence: 30-68% (GPT4oTranscribe-Corrected-5; Amazon-Medical-Transcribe and Dragon-Medical-One, respectively) contained at least one clinically significant Class 3 error | Errors with potential to cause severe harm or death (NHS England Level 3-4) totalled (n = 53) across systems
quick_read: Researchers tested eight ambient voice and speech-to-text systems, including commercial clinical products, cloud transcription APIs and an experimental pipeline pairing GPT4oTranscribe with GPT-5 error correction. A single speaker recorded 100 reference transcripts derived from surgical case reports, yielding 800 transcript outputs that were graded for potential patient harm.

The findings matter because these tools are promoted as efficient and accurate for clinical documentation, yet error rates in clinically significant content were high for every system. Language-model correction helped substantially but also created new errors, and the source states that safety and effectiveness in real clinical practice still need evaluation.
limitation: 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.
tag: Dual reading
key_points: Across 800 outputs, the share containing at least one clinically significant Class 3 error ranged from 30% to 68% depending on the system. | The correction pipeline resolved 51 of 89 significant errors, left 38 in place and introduced 4 new ones. | Of 53 errors with potential for severe harm or death, 39.6% involved medication type or dose and 30.2% involved investigations or laboratory results. | Longer reference transcripts raised the odds of Class 3 errors for four systems, with odds ratios of 2.65-3.34 per additional 100 words. | On medical terminology, GPT4oTranscribe-Corrected-5 (DWER 3.60%) and Heidi-Health (5.67%) did best, while Amazon-Medical-Transcribe was worst at 24.03%.
rundown: The study compared three commercial transcription systems (Dragon-Medical-One, Heidi-Health, Tortus), four speech-to-text APIs (Speechmatics-Enhanced, Amazon-Medical-Transcribe, Whisper, GPT4oTranscribe) and one experimental two-stage pipeline. The reference transcripts totalled 32,897 words, averaging 329 words each.

The primary outcome was the proportion of outputs with at least one Class 3 error graded for potential harm. Secondary outcomes were domain word error rate against SNOMED-CT, lexical accuracy via ROUGE, and semantic similarity via BERT and BART scores. Performance differed significantly across systems on these transcription metrics (P < 0.001).

The pipeline comparison classified errors in the raw ASR output as resolved, remaining or newly introduced. Newly introduced errors affected 3% of transcript outputs, so the correction layer reduced but did not remove clinically significant risk.
sources:
- peer_reviewed | Journal of Medical Systems | https://doi.org/10.1007/s10916-026-02471-5 | 2026-10-09
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
57106dd0b8eff6fd95e5ab77a07bb76ee13f5ba741ebcb63f5062be363c76ba0
previous
0000000000000000000000000000000000000000000000000000000000000000
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.