Playbook 03 · 12 weeks
Ambient documentation: buying it is the easy part.
An ambient documentation tool listens to a visit and drafts the note. The clinician reads it, corrects it, and signs it. Whether it helps depends less on the product than on the rooms, the network, the patients, and whether clinicians are still using it in month three.
01 · Before you start
What it takes, and what you get.
This is a clinical change with some technology in it. Run it that way. If your governance group isn’t set up yet, start with Your first 90 days.
- Who leads
- A clinical champion who sees patients, paired with a clinic manager or nurse leader who owns the workflow. IT supports. Neither IT nor the vendor leads.
- Time
- About 12 weeks from the first vendor call to a steady routine. The weekly count of use continues for as long as you pay for the tool.
- What you need
- Approval from your governance group. A business associate agreement. Reliable network coverage in the rooms where it will be used. A small first group of clinicians who volunteered.
- What you’ll have at the end
- A notice patients understand. A review step every clinician follows. A weekly count of who is using the tool. A decision on whether to expand.
02 · Three rules
Three rules that don’t bend.
Everything else on this page can be adjusted to fit your hospital. These three can’t.
- 1
The patient knows
Patients are told in plain words, before the visit starts, that a tool is listening to help write the note. They can say no, and it doesn’t change their care.
- 2
The clinician reads every note
The tool drafts. The clinician reads, corrects, and signs. The clinician is the author of the note and answers for what it says.
- 3
Use is counted every week
Per clinician, for as long as you pay for it. A license tells you what you bought. The weekly count tells you what you’re getting.
03 · The route
Six mile markers, from first call to steady use.
The first half happens before any patient visit is recorded. Hospitals that skip it tend to find out why in the first week of go-live.
-
Mile1Weeks 1–2
Decide what problem you’re solving
Be specific. Notes finished after hours? Clinicians typing through visits? Charts left open for days? Each one points to a different measure. Then pick the first group: a few clinicians who want it, in one setting.
- The problem is written in one sentence
- A baseline exists for it, such as how many notes are signed the same day
- A first group of volunteers, including at least one clinician who isn’t sure
- One setting to start: clinic or emergency department, not both
- The governance group has approved the plan
-
Mile2Weeks 2–4
Ask the vendor, in writing
Every vendor’s demo works. Ask about your EHR, your network, and your patients, and keep the written answers with the contract.
- Will you sign a business associate agreement?
- Is the audio kept after the note is written? For how long, where, and who can hear it?
- Is our audio or text used to train your models? Can we say no?
- How does the note get into our EHR, in our version? Show us in our system, not in a demo
- What happens when the connection drops in the middle of a visit?
- How does it handle an interpreter, a family member in the room, or background noise?
- Which hospitals of our size use it today, and may we call one?
- What does it cost to leave, and what happens to our data when we do?
Rules on recording, patient notice, and AI in clinical documentation differ by state and are still changing. Check the regulatory map, and your attorney, before you sign.
-
Mile3Weeks 4–6
Get the rooms and the patients ready
Test in the real rooms. Walk every exam room with the device clinicians will use, close the door, and check the signal. Decide where the microphone sits. Then decide how patients will be told, and how they say no.
- Wi-Fi or cellular coverage tested in every room, with the door closed
- A device and microphone plan for each room: phone, tablet, or workstation
- A plain-language notice for patients, on a sign and said out loud
- A simple way for a patient to decline, with no effect on their care
- Front desk and nursing staff know what to say when patients ask
- A rule for visits where recording isn’t appropriate, and who makes that call
Where small hospitals get stuckThe building. Older exam rooms, thick walls, and one access point at the end of the hall. If the tool drops out twice in a morning, clinicians stop using it by the afternoon. Fix coverage before go-live, not after.
-
Mile4Weeks 6–8
Train, then start with a few visits a day
Training is short. The habit takes longer. Start each clinician with a few visits a day and build from there. One step is never skipped: the clinician reads the whole note before signing it.
- Each clinician has had hands-on practice before a real visit
- Every note is read and corrected by the clinician before it is signed
- Clinicians know the errors to look for: the wrong speaker, a missed “no,” and things that were never said
- A way to report a wrong note that takes less than a minute
- Someone on site to ask in the first two weeks, not only a vendor help line
- Note templates are adjusted to how each clinician writes
-
Mile5Weeks 8–12
Count use every week
Each week, count who used the tool and for what share of their visits. Put the numbers where the group can see them. Use drops quietly. A weekly count is how you hear it.
- A weekly count per clinician: visits with the tool, out of visits seen
- The baseline measure from mile 1, checked again
- A short weekly check-in with the first group: what worked, and what didn’t
- A sample of notes reviewed for accuracy by a clinical leader
- Patient declines counted, and any complaints logged
- The results go to the clinicians themselves, not only to leadership
Where small hospitals get stuckCounting licenses instead of use. The invoice says every clinician has the tool. The weekly count may say only a few of them use it. Watch the second number, and bring it to the contract renewal.
-
Mile6Week 12 and after
When adoption stalls, find out why
Expect some clinicians to start strong and then stop. Don’t send a reminder email. Sit in on a visit or two and watch. The reason is usually specific and fixable: the note style is wrong, the device is awkward, the edits take longer than typing, or the connection fails in one room.
- Anyone whose use dropped has had a conversation, not a reminder
- The cause is named: workflow, note quality, device, network, or a poor fit for their visits
- Fixes are made one at a time, and use is checked again two weeks later
- Clinicians the tool doesn’t suit can stop, without a mark against them
- A decision on expanding, made with the weekly numbers on the table
- A date for the next review of accuracy, use, and the contract
Where small hospitals get stuckTreating a stall as a motivation problem. A clinician who went back to typing has usually found that the tool costs them time somewhere. Find where. If it can’t be fixed, that is a finding, not a failure on their part.
04 · After week 12
Steady use, and numbers to prove it.
By now the tool is either part of how the first group works, or you know exactly why it isn’t. Either answer is useful when the next group asks to join, and when the contract comes up.
The six-week pilot has more on baselines and stop rules. The board briefing covers how to report the results to trustees.
What done looks likeSix things that are true every week
- Patients are told every time, and declining is easy.
- Every note is read and corrected by its clinician before signing.
- Use is counted weekly, per clinician, and the clinicians see the numbers.
- The baseline has been checked again, and you can say whether it moved.
- Clinicians whose use dropped have been heard, and fixes were tried.
- The decision to expand, hold, or stop was made with the numbers on the table.
Stuck at a mile marker?
Tell us which step and what’s in the way. If other hospitals are stuck in the same place, the answer becomes part of this playbook.