SMASH 2026 · Paper #8 · Result card

Implementing Ambient Artificial Intelligence (AI) Scribes in Hospital-based Specialty Care: A Mixed-Methods Evaluation on Administrative Burden and Clinical Workflows

Nishila Mehta, Emily Ha, Andrew Gordon, Rodica Balaci, Onil Bhattacharya, Geetha Mukerji · Women's College Hospital · University of Toronto · Read the paper

Generic scribe drafts needed 78% of words edited. At the paper's median usage of 0.94% of encounters, a promised 4,550 clinic hours a month becomes 6.6.
specialty mixedencounters 6 syntheticbaseline note 6 minedit speed 1.5 s/wordencounters/month 390patients declining 10%trainee-led 20%promise 5 min/note
Edit burden of scribe drafts
78% → 27%
words changed to sign the draft: generic → specialty-customized
Net minutes per note
+1.5 / +3.3
vs writing it yourself in 6 min (generic / customized)
Clinic hours saved / month
6.6 h
at the paper's adoption, vs 4,550 h promised
Drafts needing substantial edits
33%
judge's call on generic drafts (paper survey: 88%)

From the abstract

Among 17 mid-pilot survey respondents, while 52% reported the AI scribe was easy to use, 88% reported that AI generated notes required substantial editing … These interim findings suggest that the implementation of an AI scribe is feasible in hospital-based ambulatory care but may not independently reduce documentation burden …

Evidence

How much of the scribe's draft did the specialist have to change?
How much of the scribe's draft did the specialist have to change?
Word-level edits (insertions + deletions + substitutions) the simulated specialist made to sign each draft, divided by the longer of draft and final note. Synthetic transcripts; LLM scribe and LLM specialist.
What was wrong with the drafts?
What was wrong with the drafts?
Left: PDQI-9-style item scores (LLM judge). Right: errors per draft by type. Orange = generic SOAP, blue = specialty-customized.
Promise vs implementation reality
Promise vs implementation reality
Clinician-hours saved per month across the clinic. 'Pilot reality' combines the paper's adoption funnel and usage distribution with the minutes measured here; each rung removes one barrier.
Where the encounters went (paper's numbers)
Where the encounters went (paper's numbers)
Adoption funnel at the interim analysis. Even after the barriers you assumed, most eligible encounters were simply not recorded with the scribe.

Paper vs. your run

MetricPaperYour run
AI notes needing editing88% reported that generated notes required frequent editing (n=17 survey)33% generic / 17% customized drafts judged to need substantial editsdifferent construct: clinician perception vs LLM judge
Mismatch with specialty documentationmismatch between output and specialty-specific documentation requirements (n=4)format errors per draft 0.8 generic vs 0.3 customized
Inaccurate contentinaccurate content information (n=4)inaccuracy + hallucination errors per draft 0.0; planted-fact recall 100%synthetic transcripts
Time savings41% felt they experienced overall time savings; 29% reported reduced documentation time83% of generic / 100% of customized notes faster than 6 min from scratchmodelled minutes, your assumptions
Adoption43 enrolled; 21 (49%) used the AI scribeused as model inputcalibration
Utilization among usersmedian 0.94% of encounters (IQR 3.04%), range 0.05-18.4%lognormal σ = 1.87; mean 3.1% per active userfitted, capped at 18.4%
Documentation time (EHR)longer clinical notes, greater editing time, slightly more time spent documenting per encounterdrafts 205 words; finalizing a draft 4.5 min vs 6 min assumed baseline

Try next

Read this before sharing