Key points
- Treat ambient scribing as clinical documentation support, not autonomous decision-making.
- Assume the clinician remains accountable for the record; review and edit is non-negotiable.
- In the NHS, compliance expectations typically touch DTAC, clinical safety (DCB0129/0160), and (if relevant) MHRA medical device status.
The safest operating principle
Step 1 — Define the use case tightly
Step 2 — Map your data flow
Step 3 — Decide what must never be captured
Step 4 — Make review explicit in the workflow
Step 5 — Pilot with measurement
Official Sources
Save your place and choose what comes next
Work through this guide (5 steps)
Use the actions from this article to track what you have worked through.
Sign in using the reading controls above to save your steps.
Decide what you want produced: consultation note, referral letter, patient summary, admin task list. Narrow scope reduces risk and makes evaluation possible.
Return to this sectionWrite down what audio/text leaves your environment, where it is processed, what is stored, and for how long. If you can’t describe the flow, you can’t govern it.
Return to this sectionAgree ‘red lines’ locally (e.g., sensitive third-party information, certain categories of patient data, safeguarding details). Train staff to pause/disable capture when needed.
Return to this sectionBuild time for verification (even 30–60 seconds) and define what “good” looks like: completeness, correct negatives, correct meds, correct safety-netting language.
Return to this sectionMeasure time saved AND error rates (near misses, corrections per note, missing key items). If quality drops, the ‘time saved’ is debt.
Return to this section
United Kingdom · Starting work · Article 7 of 28