Enterprise-Scale Deployment of AI Ambient Scribes Across Multiple Healthcare Systems

memorial_sloan_kettering_/mcleod_health/_ucla · Healthcare · 2025 · source Agentic: no · promotional bias: low · source-backed · extracted with prompt 0.5.6 (schema v2)

Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.

Problem

Domain: Healthcare ambient clinical documentation

McLeod Health, UCLA Health, and Memorial Sloan Kettering needed to select, evaluate, roll out, and justify AI ambient scribe systems that reduce documentation burden and burnout without compromising clinical workflow, note quality, privacy, ROI, or patient trust.

Constraints:

Architecture

The systems used structured vendor selection and rollout processes rather than a single technical stack. McLeod filtered vendors, used 15 scripted patient encounters with actors, collected unedited notes, had physicians/RevCycle/patients score notes, then tested Epic usability before selecting Suki. UCLA ran a randomized controlled trial with two intervention groups and one control group before scaling Nabla in monthly waves with mandatory training and support. MSK piloted vendors head-to-head, focused on oncology complexity and EHR workflow, and evaluated Abridge with broader metrics and workflow lessons.

Diagram confidence: reconstructed (reconstructed from prose).

flowchart LR
  clinical-encounter-audio["Clinical encounter audio"] --> ai-scribe-vendor-system["AI scribe vendor system"]
  ai-scribe-vendor-system --> ehr-workflow["EHR workflow"]
  ai-scribe-vendor-system --> clinician-review["Clinician review"]
  ehr-workflow --> clinician-review["Clinician review"]
  clinician-review --> evaluation-program["Evaluation program"]
  evaluation-program --> training-and-support["Training and support"]
  training-and-support --> clinician-adoption["Clinician adoption"]
Drag to pan · scroll or use +/− to zoom · reconstructed from the source's described component topology

Components

Component Role Interacts with
Clinical encounter audio Patient-provider conversations captured by ambient scribe vendors. AI scribe vendor system
AI scribe vendor system Generates draft clinical notes, summaries, and potential coding support. EHR workflow, Clinician review
EHR workflow Epic/Haiku/Abridge/Nabla/Suki integration context where clinicians document care. Clinician review
Clinician review Human oversight of note quality, edits, and suitability for patient care. Evaluation program
Evaluation program Vendor comparison, RCTs, pilots, surveys, note scoring, ROI, burnout, and patient-satisfaction tracking. Training and support
Training and support Mandatory onboarding, super users, elbow-to-elbow support, and rollout waves. Clinician adoption
Clinician adoption Usage across clinicians, visits, specialties, and encounter types. —

Data flow

Clinical encounters are captured by ambient scribe tools, converted into draft notes or visit summaries, reviewed in clinical workflow/EHR context, and evaluated through note scoring, surveys, adoption/usage metrics, burnout instruments, financial measures, patient satisfaction, and technical monitoring for errors such as hallucinations.

“The vendors had to record these interactions, all 15 of them, in real time, and they had to send them the notes to me, unedited.”transcript, stated
“we make sure we validate everything before we use it”transcript, stated

Why this architecture

The organizations used rigorous evaluation and staged rollout because ambient scribes are expensive, clinically sensitive, workflow-dependent, and not universally appropriate; vendor choice and adoption depend as much on clinical fit as model capability.

“we didn't want to just pick a vendor based on groupthink or what other people were doing.”transcript, stated
“It's not a silver bullet. It is not the perfect solution for every clinician.”transcript, stated

Models used: Suki · Nabla · Abridge · AI scribes · LLMs · Epic · Haiku

Scale

Alternatives considered (roads not taken)

Pick the expected or popular AI scribe vendor.

Rejected because: McLeod's structured testing overturned the presenter's initial bias.

“Pretty sure of who I was gonna pick as an AI scribe vendor. And I was wrong.”transcript, stated

Evaluate vendors without randomized controls.

Rejected because: UCLA chose a randomized controlled trial to get actionable decision data.

“Run this as a gold standard, a randomized controlled trial”transcript, stated

Use monthly per-provider pricing.

Rejected because: Encounter-based pricing aligned vendor incentives and enabled lower-use clinicians to participate.

“We're not going to charge you. This fee per month, we're going to do encounter-based pricing”transcript, stated

Deploy without workflow mapping.

Rejected because: MSK wished it had mapped workflows earlier to tailor rollout by specialty and visit type.

“We actually didn't do that for our pilot, and looking back on it, I wish we did.”transcript, stated

Patterns

eval-driven-development (evaluation)

Healthcare systems used scripted scenarios, RCTs, head-to-head pilots, surveys, and ROI metrics before scaling.

“we also have an excellent research team at UCLA Health that's called our Values and Analytics Solution Group”transcript, stated

human-in-the-loop-gate (governance)

Clinicians review and use AI-generated notes as a support tool rather than an autonomous clinical authority.

“It's a support tool for our clinicians and documentation.”transcript, stated

safety-policy-enforcement (safety)

Training explicitly covers LLM imperfections such as omissions and inaccuracies.

“we can see errors with it, like omissions. Inaccuracies and whatnot”transcript, stated

observability-tracing (operations)

Rollouts track adoption, utilization, qualitative/quantitative outcomes, ROI, burnout, EHR time, and hallucination feedback.

“collecting both qualitative and quantitative data.”transcript, stated

Tradeoffs

Run rigorous vendor evaluation before selection.

Chose Scripted encounters, head-to-head pilots, RCTs, and stakeholder review. over Selecting based on market reputation or initial assumptions..

Rationale: Clinical note quality, workflow fit, and vendor support varied in non-obvious ways.

“three groups of people rate the notes”transcript, stated

Scale through waves with training and support.

Chose Monthly expansion, mandatory training, super users, and elbow-to-elbow support. over A single broad rollout after pilot completion..

Rationale: The organizations needed adoption without ignoring LLM limitations or clinician workflow differences.

“expansion phase, which we're doing in monthly waves”transcript, stated

Prioritize tech stack and future workflow integration.

Chose A vendor whose stack could move beyond commodity notes toward clinical decision support and conversational AI. over Choosing only on current note output..

Rationale: Switching costs are significant, and scribe notes may become commoditized.

“The tech stack was the most important for us, because we felt like switching costs were going to be fairly significant.”transcript, stated

Gotchas (what bit them)

Vendor preference bias can mislead selection.

Root cause: Leaders may assume a favored vendor is best before structured testing.

Resolution: Use scripted encounters, unedited notes, and multi-stakeholder scoring.

“We wanted to remove as much cognitive bias from the decision-making.”transcript, stated

Ambient scribes do not fit every clinician or specialty.

Root cause: Some clinicians prefer paper/Dragon or have workflows where the tool is not useful.

Resolution: Treat non-adoption as acceptable and learn fit by patient, visit, clinician, and specialty type.

“some people who just say, I don't want to use it”transcript, stated

Simple-looking scribe tools require deep training.

Root cause: The note appears magically, but clinicians must learn how to speak/use it and handle LLM error modes.

Resolution: Make training mandatory and add super-user and elbow-to-elbow support.

“I don't think there's a way for you to be able to use this tool without receiving that training.”transcript, stated

Pricing can block scaling to clinicians who use the tool intermittently.

Root cause: Per-provider monthly licenses make low-frequency but valuable use cases unattractive.

Resolution: Use encounter-based pricing with a cap to align vendor and hospital incentives.

“it causes the vendor to be on the hook, and they're aligned, their interests are aligned with our organization”transcript, stated

Evaluation

The panel describes evaluation through scripted encounters, unedited vendor notes, physician/RevCycle/patient review, RCTs, pilots, Mini Z, NASA TLX, burnout prevalence, work RVUs, documentation time, level of service, EHR time, hallucination feedback, adoption/utilization, patient satisfaction, and financial ROI.

Metrics: 15 scripted encounters · Top four vendors · 35 to 150 McLeod doctors · About 200 UCLA pilot physicians · 20% burnout reduction · 30-40% encounter usage · 6.3% patient-satisfaction increase · $1,000 per provider per month net after subscription

“We'll be looking at, like, work RVUs, time to document, um, average level of service, uh, working very closely with our financial colleagues around those metrics.”transcript, stated
“We're using the Mini Z and the NASA TLX to assess both of those metrics, which I think are very important.”transcript, stated

Outcomes

The case spans McLeod's seven-hospital system, UCLA's roughly 5,000 ambulatory physicians, and MSK's oncology-focused deployment/evaluation work.

“I think I feel comfortable in saying that we're currently using NAVLA at UCLA Health.”transcript, stated
“Results included significant reductions in burnout (20% at UCLA), improved patient satisfaction scores (5-6% increases at McLeod), time savings of 1.5-2 hours per day”summary, stated