How to Roll Out an AI Scribe Without Losing Patient Trust

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Roll Out an AI Scribe Without Losing Patient Trust.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Roll Out an AI Scribe Without Losing Patient Trust.

Tell patients before they arrive, ask in the room every time, make saying no easy and free of consequences, start with a small pilot of willing clinicians, check every note before it's signed, and explain plainly what happens to the audio. Then track opt-outs, note corrections and complaints for 90 days before extending the scribe to everyone.

Trust is lost through surprise far more than through the technology itself. A patient who is asked and says yes rarely thinks about it again; a patient who finds out afterwards, from a line in their notes or a friend, feels something was done to them. The second way trust goes is quieter: a note that records "denies chest pain" when the patient mentioned chest pain. Both are preventable, and both are easier to prevent in a small pilot than across a whole clinic.

Follow me on Instagram@sagnikteaches

Pin down the facts you'll be promising patients

Before any patient hears a word about the scribe, you need true answers to the questions they'll ask. Vendors differ a lot. Heidi says it doesn't store consultation audio and lets you set how long transcripts are kept. Nabla says it discards audio as it processes it and keeps transcripts and notes for 14 days by default, a period organisations can change. Your vendor may do something else entirely, and settings you choose can change the answer.

Connect on LinkedInSagnik Bhattacharya

Write a one-page fact sheet from the vendor's documentation and your own settings, and keep it with the date you checked. An illustrative version:

Subscribe on YouTube@codingliquids
SCRIBE FACT SHEET (checked [date], by [name])
Audio: processed during the consultation, not stored.
Transcript: kept 7 days for clinician review, then deleted.
Draft note: copied into our records system by the clinician
  after review; deleted from the scribe after 7 days.
Model training: vendor contract says our data is not used.
Who can see it: the treating clinician; vendor support only
  with our written permission.
Where processed: [region stated in the vendor contract]
If we stop using the vendor: data deleted within [period].
Settings owner: practice manager. Re-check every 6 months.

Every patient-facing sentence you write later must match this sheet. If the vendor changes a default, the sheet changes first, then the wording. The commonest mismatch comes from material you didn't write. In an illustrative clinic, the leaflet supplied in the vendor's welcome pack said "recordings are securely stored", while the clinic's own settings discarded audio. A patient who read it asked reception for a copy of her recording, was told it was "stored securely", and then had to be told the next day that it didn't exist. Nothing had gone wrong with her data, but the clinic now looked as though it didn't know what its own tool did. Read every piece of vendor material against the sheet before it goes on a wall or a website. What an AI scribe is and how it works in a consultation explains the mechanics if your team needs a primer.

Start with two clinicians and the right appointments

Choose clinicians who want to try it and who are comfortable explaining it. A reluctant clinician explains a scribe reluctantly, and patients hear the doubt. Run the pilot for about four weeks, in the style of a shadow-mode pilot: the clinician still owns and reviews every note, and nothing about the patient's care depends on the scribe.

Leave these out of the pilot, and decide later case by case whether they come in:

  • Intimate or sensitive examinations.
  • Consultations where safeguarding concerns are likely to come up.
  • Patients who may lack capacity to agree, until you have a process for them.
  • Children, until the rule on who agrees is written down.
  • Consultations through an interpreter, until you've tested how the scribe handles two languages.
  • Anyone in acute distress.

When you're ready to test interpreted consultations, rehearse one first rather than learning on a patient. Two staff members play clinician and patient, the patient speaking another language, with a colleague interpreting. Then read the draft for three things: whether the interpreter's words are recorded as the patient's own (a draft full of "patient reports" may mean it can't tell the voices apart), whether anything said only in the second language has simply vanished, and whether the clinician's questions have turned into the patient's answers. If any of the three shows up in a rehearsal, keep interpreted consultations out until the vendor can show you a better result.

Tell patients before they walk in

Patients should meet the idea before the consultation, so the question in the room isn't a surprise. Three light touches work together: one line in the booking confirmation, a short page on your website linked from it, and a notice in the waiting area. The line can be as simple as: "Some of our clinicians use an AI tool to help write notes. They'll ask you first, and you can say no."

Resist the pull towards policy wording. The first draft of that line in an illustrative clinic read: "We may use artificial intelligence technologies to support clinical documentation in accordance with our privacy notice." It's accurate, and it tells a patient nothing they need: not who uses it, not when, and not that they can refuse. A quick test for any notice: hand it to a receptionist, take it away after one reading, and ask them to say what it means. If they can't, a patient skimming a booking email won't either.

Exact wording for each of these, plus scripts for the room and for patients who decline, is in telling patients you use AI note-taking. The point here is the order: notice first, question second, never the question alone.

What happens in the room

How the clinician behaves shapes trust more than any leaflet. Four habits help:

  1. Ask before starting, not after the patient has begun talking. Start the scribe only once they've agreed.
  2. Keep the device visible. A phone face-up on the desk is less unsettling than an unseen microphone.
  3. Pause it for anything the patient wants kept out, and say you've paused it.
  4. Say when it's off at the end: "That's the recording stopped."

Patients ask questions, and the answers should come from the fact sheet. An illustrative exchange:

Patient:   Is it listening now?
Clinician: Yes, since you said that was fine. I can pause it
           any time. Just tell me.
Patient:   Who hears it?
Clinician: Nobody hears it. The tool turns our conversation
           into a draft note, and I read and correct that draft
           before it goes into your record. The audio isn't
           kept.
Patient:   Can you stop it for a minute? This bit's personal.
Clinician: Of course. [pauses] It's paused now.

Making "no" easy, and "stop" easier

A patient who declines must notice no difference in their care. No sigh, no "it'd really help me if…", no longer wait. The clinician types notes the usual way and moves on. Record the decision in the notes so the next clinician doesn't ask again the same day, but don't ask the patient why.

Plan for the patient who changes their mind halfway through. The clinician stops the scribe, deletes that session using the vendor's process, finishes the consultation without it, and records that the patient withdrew. Test the deletion during the pilot so you know it works and how long it takes. In an illustrative pilot, the first test took 11 minutes, because the delete option was visible only to the account administrator and the practice manager was with a patient. The clinic changed the permissions so each clinician could delete their own sessions, and the second test took under a minute. Far better to find that on a test session than with a patient waiting. If the patient asks later for any trace to be removed, the practice manager handles it using the fact sheet.

Notes patients can trust

More patients now read their own records, so a wrong note is visible. Scribes make a few characteristic kinds of error, and reviewing clinicians should look for them specifically:

Error typeIllustrative exampleHow to catch it
Negation flippedPatient said "a bit of chest tightness"; note says "denies chest pain"Read every "denies" and "no" line against memory of the consult
Examination that didn't happen"Abdomen soft, non-tender" in a phone consultationCheck every examination finding was actually performed
Left and right swapped"Right knee" when it was the leftCheck laterality on every musculoskeletal note
Wrong attributionA carer's worries recorded as the patient's symptomsCheck who said what when others were present
Dose or frequency misheard"15 mg" recorded as "50 mg"Check every number against the prescription

Several of these can turn up in a single short note. An illustrative draft from a telephone consultation with an older patient whose daughter joined the call:

DRAFT (as generated)
Three days of productive cough. Denies fever. Chest clear on
auscultation. Reports confusion at night. Advised fluids and
paracetamol; review if worse.

AS SIGNED
Three days of productive cough. Felt "hot and cold" last night,
no thermometer reading. Telephone consultation: no examination.
Daughter reports patient more confused at night over 2 days;
patient does not report this herself. Advised fluids and
paracetamol. Face-to-face review tomorrow given new confusion.

Three corrections, and each matters. "Denies fever" flipped what the patient said. "Chest clear on auscultation" described an examination that can't happen on a phone call. And "reports confusion" put the daughter's observation in the patient's mouth. The third correction also changed the plan: new confusion reported by a relative is a reason to see someone sooner, which the draft's tidy summary had hidden.

During the pilot, each clinician logs the number of corrections per note. If corrections aren't falling after the first two weeks, the templates or the microphone position usually need changing. The log shows which. One illustrative clinician's first week recorded 18 corrections across 14 notes; 7 of them were left-right swaps and all 7 came from knee and shoulder consultations, where she described the joint while facing the patient. Saying "the patient's left" out loud during the examination cut the swaps to one in week two. Another clinician's corrections were spread across every type, which pointed to the audio rather than the words: his phone sat on the far side of the desk next to a humming printer, and moving it to the middle of the desk fixed most of them. Setting up human review for AI work covers how to keep review quick without letting it become a rubber stamp.

What front-desk staff say when patients ask

Patients often ask reception rather than the clinician. Give the front desk short answers drawn from the fact sheet, so the story is the same whoever answers. "Is my appointment being recorded?" Only if you agree when the clinician asks you. "Where does it go?" The tool writes a draft note and the audio isn't kept; your clinician checks the note. "I don't want it." That's fine; tell your clinician, or we'll add a note so they know. "Is it the same as the ones on the news?" A good cue to hand over the website page rather than debate it at the desk.

The first 90 days: signals to watch

SignalHow to measureWhen to pause and review
Decline ratePatients who say no ÷ patients askedA sudden rise, or one clinician far above the others
Mid-consult withdrawalsCount per monthAny cluster; ask the clinician what prompted them
Corrections per noteClinician's own logNot falling after two weeks
Complaints or concerns about the scribeComplaints log, feedback formsAny complaint about not being asked
Patient questions at receptionTally sheet at the deskThe same question repeatedly: the notice isn't answering it

Take an illustrative five-clinician clinic whose two pilot clinicians see 310 patients in four weeks. Fourteen decline (4.5%), two withdraw mid-consultation, corrections fall from about 1.3 per note in week one to 0.4 by week four, and one patient raises a concern: she'd missed the booking confirmation line and was surprised by the question. The clinic moves the notice to the top of the confirmation text, adds a line to the check-in screen, and extends the scribe to two more clinicians. Whether the scribe is worth this effort for your clinic is a separate question; is an AI scribe worth it for a small private clinic works through the numbers.

Deciding whether to extend beyond the pilot

Agree the go/no-go test before the pilot starts, so enthusiasm doesn't make the decision for you. A reasonable set of conditions for extending the scribe to more clinicians:

  • No complaint about a patient not being asked, or a clear fix for any that arose.
  • Corrections per note falling, and no correction of a kind that could have harmed a patient left unexplained.
  • Deletion tested at least once, start to finish, including a mid-consultation withdrawal.
  • The fact sheet re-checked against the vendor's current documentation and your live settings.
  • Front-desk staff able to answer the common questions without looking them up.
  • The pilot clinicians willing to keep using it, and able to say why.

If one condition fails, extend the pilot by a fortnight and fix that one thing rather than abandoning the scribe or pressing on regardless.

The step most clinics forget is everyone who wasn't in the pilot. Locums, bank staff and new starters inherit the scribe without the conversations that shaped how it's used. Give each of them the fact sheet, the exclusion list and the in-room habits on their first day, and make "ask before you start the scribe" part of the induction checklist they sign. A locum who treats the scribe as always-on can undo months of careful rollout in a single afternoon, because the patient who wasn't asked doesn't know it was one person's mistake.

If trust takes a knock anyway

Sooner or later a patient will read a note that describes something that didn't happen, or discover they weren't asked because a locum skipped the step. Handle it the way you'd handle any record error: apologise plainly, correct the note with a dated addendum, explain what the scribe does and doesn't keep, and tell the patient what you've changed so it doesn't happen again. The correction itself should say plainly what happened, without blaming the patient or hiding behind the software. An addendum along these lines works:

Addendum, [date], [clinician]: The note of [date] recorded
examination findings in error. This was a telephone consultation
and no examination took place. The findings were generated by the
note-writing tool and were not removed at review. Corrected entry
below. Patient informed on [date].

The sentence "were not removed at review" is the honest part. The tool produced the error, but the clinician signed it, and patients notice when a practice owns that rather than pointing at the software. Then check whether it was a one-off or a process gap, such as locums not being briefed. Log it; the patient data confidentiality checklist includes what to do if data may have gone somewhere it shouldn't. Patients tend to forgive a mistake handled openly; they rarely forgive one they feel was hidden.

Questions clinics ask during a scribe rollout

Is verbal consent enough, or do we need a signed form?

It depends on the law where you practise, your professional body's guidance and your indemnity provider's view. Many clinics ask verbally at the start of each consultation and record the answer in the notes themselves. Some add written consent for particular groups. Ask your indemnity provider or a healthcare lawyer which approach they expect before you finalise the process.

Should we use the scribe in children's appointments?

Leave them out of the pilot. Once the process is settled, decide who gives agreement (usually the parent, with the child's own view taken into account as they get older) and whether some appointment types, such as safeguarding concerns or teenagers seen alone, should stay excluded. Write the rule down so every clinician applies it the same way.

Can a patient ask for the recording or transcript?

Patients can generally ask for the information you hold about them. If your scribe deletes audio once the note is generated, there's no recording to provide. Transcripts kept for a review period may be covered by an access request while they exist. Know your vendor's retention settings so front-desk staff can answer accurately.

Further reads

Sources: Heidi Health data and security help pages; Nabla privacy and security documentation (checked September 2026).

Planning an AI scribe pilot at your clinic?

On a 1:1 call we'll work out your vendor fact sheet, choose which clinicians and appointment types go first, and set the checks and trust signals you'll review before extending it.

Book a 1:1 call with me