CLINICAL TECHNOLOGY REVIEWEDITION 01 / SEPTEMBER 2026
Explore results →

CLINICAL TECHNOLOGY, PUT TO THE TEST

AI scribes, under the microscope.

We test AI medical scribes on the same recorded consultations. Explore how they compare on transcription, clinical notes and speed—then look closer at the cases behind the numbers.

Every consultation has an inventory of every fact said that relates to the patient's conditions, symptoms or signs, the standard Weiner et al. (2020) used to audit doctors' notes. The inventories were drafted by AI from each reference transcript alone, before any note was graded, and every fact quotes the line it comes from.

6 scribes testedHanah GPT-6.1 Sol local preview · 11 October 2026How we test Heidi review video

Local preview — Hanah notes regenerated on 11 October 2026 with GPT-6.1 Sol, low reasoning: 50 notes across 10 consultations, five stored transcript variants each. Two consultations await new Hanah notes. WER and transcription evidence retain their original capture dates; other scribes retain their existing results. New notes were graded blind by Sonnet 5.5 medium, followed by an unblinded agent audit; provisional, without independent clinician validation. Hanah timings are estimates: prompted-note wait uses measured API generation duration + 2 seconds readiness allowance; time to a finalised note adds estimated review and correction time. Both exclude transcription finalisation and app overhead, pending a live rerun.

Benchmark · 22 September 2026

AI scribes against a doctor writing the note

6 scribes, 12 consultations, Hanah note preview on 10 cases; other results retain their original dates. The doctor column comes from published studies, not our grading.

Swipe or scroll the table to see every scribe →

Headline measures for a doctor-written note and each AI scribe.
MeasureDoctor-written note (published studies)*HanahHeidiCliniScriptsLyrebirdFreedPatientNotes
Missed, partial or invented facts about a condition, symptom or sign (Weiner et al.), before any review. Lower is better.
As a share of a doctor writing it (100%). Lower is better.
Work to fix the note, as a share of writing it by hand. Lower is better.
Notes with no missing, partial or invented facts. Higher is better.

Every measure · 22 September 2026

6 AI scribes, 12 consultations

Notes graded blind, with provisional agent audit for the new Hanah results. Each figure is the average across runs; select any cell to see every run.

Local preview — Hanah notes regenerated on 11 October 2026 with GPT-6.1 Sol, low reasoning: 50 notes across 10 consultations, five stored transcript variants each. Two consultations await new Hanah notes. WER and transcription evidence retain their original capture dates; other scribes retain their existing results. New notes were graded blind by Sonnet 5.5 medium, followed by an unblinded agent audit; provisional, without independent clinician validation. Hanah timings are estimates: prompted-note wait uses measured API generation duration + 2 seconds readiness allowance; time to a finalised note adds estimated review and correction time. Both exclude transcription finalisation and app overhead, pending a live rerun.

Swipe or scroll the table to see every scribe →

Average result per scribe across all runs. Lower is better except clinical coverage. Select a cell to open the run-by-run spread.
MeasureDoctor-written note (published studies)*Hanah1HeidiCliniScripts2Lyrebird3Freed4PatientNotes
Wait from pressing stop to the graded note, plus review time: how long until the note can be finalised if it is reviewed straight away.
8m 6s
Share of notes that captured every fact in the consultation's inventory in full with no hallucination flags, so nothing needed editing.
10%
0% means no editing required; 100% means writing the full note by hand. Fixes are weighted by the work they take: partial fact 1, missing fact 2, hallucination flag 3, and +2 when a fact is captured wrongly.
100%
Estimated clinician time to proofread and fix one note (190 wpm reading, 5 s to recall and 40 wpm to type each missing or partial fact, 12 s to verify and delete each hallucination flag, including a wrong fact before it is retyped).
—
The single slowest note to review and fix across every case and run.
—
Time to write the note yourself (8.1 min, the median in Apathy et al. 2023) minus review time.
—
How much quicker reviewing and fixing a note is than writing it yourself (8.1 min, the median in Apathy et al. 2023). Negative means slower.
—
Relevant facts the note missed or captured only partly, plus every hallucination flag (a wrong detail counts twice, as in Weiner et al.), against an inventory of every fact said that relates to the patient's conditions, symptoms or signs (Weiner et al. 2020). Total per run, across 12 cases. The flat count is in Hallucination flags.
60.0
Note errors (Weiner et al. standard) per 100 notes, times 70%: in Biro et al. (2025), GPs reviewing AI drafts left each planted error uncorrected 65–75% of the time. An estimate of what a typical review would let through, across 12 cases.
500
Compared with the 5.0 errors per note Weiner et al. (2020) found in physicians' notes checked against recordings of the visit. Our test counts more strictly than theirs, so this favours the doctors. 100% means no errors; below 0% means more errors than the doctors. Across 11 cases.
0%
Every clinical element the note documents that the consultation does not support, including wrong values, sides, doses and timings: Weiner et al.’s (2020) errors of commission. Paraphrase and clinical terms for what was said do not count. Average per note, across 12 cases.
1.72
Missing items, partial items and hallucination flags a clinician would need to fix, per note.
6.06
Share of each consultation's fact inventory captured by the note (partial counts as half).
—
Mis-heard words that change clinical meaning, rated blind, across 12 cases.
—
Pooled word error rate per run against the human reference. Every word counts equally, including fillers.
—
Median time from pressing stop to the note written to our instruction, per run.
—
Average network data per consultation, per run.
—
Physical memory footprint (macOS `footprint`, matching Activity Monitor's Memory column) sampled every minute during one continuous 50-minute stress-test consultation — separate from the 12-case suite above. Every scribe recorded this visit at the same time on one machine, so absolute values reflect shared contention between them, not isolated real-world usage. Compare scribes to each other here, not to a device's spec sheet.
—
CPU used per minute during the same continuous 50-minute stress-test consultation, measured as cumulative CPU-seconds consumed divided by wall-clock time (can exceed 100% when a scribe uses more than one core). Every scribe ran concurrently on one machine.
—

Download everything: one JSON file with every run’s scores, transcripts, notes and jury reasons, or every run’s scores as CSV.

GO ONE LEVEL DEEPER

Results by clinical case

View the aggregate →

Each consultation compares the scribes on the same audio across every graded run. Open one to read each run's transcript and note, with every error marked.

Language-specific consultations

Separate comparisons with capability exclusions and translation-aware interpretation.

Physician dictation

Scored against verbatim references built from the publisher’s answer keys. Spoken dictation commands are not scored.

Extended-session stress test

A 50-minute synthetic fixture with background distractors. Included in the overall results.