CLINICAL TECHNOLOGY REVIEWEDITION 01 / SEPTEMBER 2026
Explore results →

SCRIBE RESULTS / 22 SEPTEMBER 2026

CliniScripts

Averages across 5 graded runs of 12 consultations, the same audio and instruction for every scribe. Notes graded on default template.

4m 3sTime to a finalised note · ranked 3 of 6
2%Notes ready to finalise as written · ranked 3 of 6
116.2Note errors (Weiner et al. standard) · ranked 4 of 6
1.40Hallucination flags per note (Weiner et al. standard) · ranked 3 of 6
13.0%Word error rate · ranked 2 of 6

Summary

CliniScripts had a word error rate of 13.0%, ranked 2 of 6, and averaged 1.40 hallucination flags per note, ranked 3 of 6. Time to a finalised note was 4m 3s, ranked 3 of 6.

It averaged 9.68 errors per note under the Weiner et al. standard, ranked 4 of 6, against the 5.0 Weiner et al. (2020) found in doctor-written notes, on a stricter test than theirs. Clinical coverage was 80%, ranked 5 of 6.

Every measure

MeasureAverageRun rangeRank
Time to a finalised noteWait from pressing stop to the graded note, plus review time: how long until the note can be finalised if it is reviewed straight away.4m 3s3m 39s–4m 21s3 of 6
Notes ready to finalise as writtenShare of notes that captured every fact in the consultation's inventory in full with no hallucination flags, so nothing needed editing.2%0%–8%3 of 6
Editing effort0% 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.25%23%–27%3 of 6
Review time per noteEstimated 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).3m 50s3m 27s–4m 3s4 of 6
Worst note, any runThe single slowest note to review and fix across every case and run.10m 47s—6 of 6
Time saved per noteTime to write the note yourself (8.1 min, the median in Apathy et al. 2023) minus review time.4m 16s4m 3s–4m 39s4 of 6
Faster than writing it yourselfHow 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.53%50%–57%4 of 6
Errors per note (Weiner et al. standard)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). Average per note, across 12 cases.9.688.33–10.084 of 6
Note errors (Weiner et al. standard)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.116.2100.0–121.04 of 6
Errors reaching the record, per 100 notes (estimate)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.678583–7064 of 6
Fewer errors than doctor-written notesCompared 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.-94%-102%–-67%4 of 6
Hallucination flags per note (Weiner et al. standard)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.400.92–1.833 of 6
Edit actions per noteMissing items, partial items and hallucination flags a clinician would need to fix, per note.9.688.33–10.084 of 6
Clinical coverageShare of each consultation's fact inventory captured by the note (partial counts as half).80%77%–83%5 of 6
Significant transcript errors per runMis-heard words that change clinical meaning, rated blind, across 12 cases.9.08.0–10.02 of 6
Word error ratePooled word error rate per run against the human reference. Every word counts equally, including fillers.13.0%12.9%–13.3%2 of 6
Stop to prompted noteMedian time from pressing stop to the note written to our instruction, per run.25s24s–30s3 of 6
Data per consultAverage network data per consultation, per run.31.5 MB31.5 MB–31.5 MB5 of 6
Avg RAM (stress test)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.972 MB888 MB–1042 MB1 of 6
Avg CPU (stress test)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.28.8%26.3%–30.1%2 of 6

Definitions and weights are in the methodology. Compare CliniScripts head to head ↗

Consultations

Reviews

Write a review

Overall
Accuracy
Note quality
Workflow
Reliability
Value for money