An AI scribe can have an appropriate basis for processing information without the patient understanding what is happening or feeling able to object. Good implementation therefore needs more than a lawful-basis entry in a governance document. It needs an honest explanation, a workable alternative and a clinical record that reflects what actually occurred.
This guide updates iatroX's original consent and transparency article of 8 February 2026. The legal and regulatory discussion was checked on 10 October 2026 and focuses on NHS England's guidance for individual-care ambient scribing. It is practical service guidance, not individual legal advice. Final arrangements should pass through the organisation's information-governance lead, data protection officer, chief clinical information officer or clinical safety officer, as appropriate.
The mindset: consent is not always the point, transparency is
NHS England's information-governance guidance, checked on 10 October 2026, says explicit consent is not required for the individual-care processing it describes. It nevertheless requires transparency and respect for dissent. These are separate obligations, not contradictory instructions.
Do not collapse data-protection law, the common law duty of confidentiality and consent to treatment into one checkbox. A patient-facing question about whether the person is comfortable with a scribe does not automatically make consent the organisation's UK GDPR lawful basis. Conversely, an organisation's selected lawful basis does not make it acceptable to continue using the tool after a patient has dissented under the described direct-care arrangement.
The operational aim remains straightforward: explain the tool before it starts, make refusal easy and document the explanation and review that actually happened. A privacy notice supports that conversation. It does not replace it.
What patients should be told: the four truths
Patients need to understand the capture, the output, the processing arrangements and their choice. These four topics should remain consistent across reception information, the consulting room and the service website.
First, say that the system listens to the consultation to help produce documentation. Second, distinguish its draft from the clinician-approved record. Third, explain who processes the information and where the resulting material goes. Fourth, make clear that the patient can decline and receive ordinary note-taking instead.
The processing explanation needs particular care. Saying that only the clinical team uses a draft may be misleading where a supplier or its subprocessors handle audio or text. Staff should use an explanation approved for the actual service, including relevant external processing, rather than borrow a reassuring sentence from another practice's poster.
Likewise, the final note entering the normal patient record does not establish what happens to intermediate audio, transcripts or technical logs. The patient should be able to obtain those details without having to understand the technical architecture first.
The 30-second patient script: clinic-ready wording
A suggested spoken introduction is:
We use an AI scribe to help draft our consultation notes. It listens while we talk and produces a draft, which I check and correct before adding it to your record. I remain responsible for my clinical decisions. You can ask me not to use it, or to stop it, without affecting your care. Are you comfortable with us using it today?
This is proposed wording, not a mandatory legal formula. Adapt it to the actual system and the person's communication needs. Do not deliver it while capture is already running, then treat the absence of an interruption as meaningful choice.
When the patient asks whether they are being recorded, answer the question directly. Explain whether audio is captured, whether it is retained and whether a transcript remains. Follow that with the review process and the option to stop. A statement about clinician responsibility is not an adequate answer to a question about recording.
When the patient asks where the information goes, use the verified local data flow. A suitable structure is: the supplier processes specified material to create a draft; authorised people review it; the approved note enters the clinical record; other material follows the stated retention policy. Name the provider and relevant locations when those details are requested. Do not invent a retention period because the consultation is busy.
The refusal pathway: make it effortless
The response to dissent should not become a negotiation about whether the patient is sufficiently technologically informed. A simple answer is: "Of course. We will not use it, and I will take notes in the usual way."
Operationally, stop the tool, check that capture has actually ceased and continue through the alternative documentation process. Do not move the same conversation into a different unapproved recording application. Record the preference briefly where relevant to the encounter and local workflow.
An equivalent-care standard is a useful local policy commitment: declining this tool should not mean a worse appointment, a less helpful clinician or an avoidable extra booking. Monitor whether staff can deliver that commitment in practice, rather than assuming a notice makes it true.
Stopping future capture is not necessarily the same as deleting information already processed. Questions about retained material require the service's actual policy and applicable rights assessment. Staff should neither promise immediate universal deletion nor tell patients that nothing can ever be changed.
How to document it: templates for the clinical record
These are adaptable templates. Each statement should be used only when it accurately describes the encounter.
A: Informed patient, no objection, output checked. "AI scribe used to prepare a draft consultation note. Patient informed and given an opportunity to decline; no objection raised. Draft reviewed and corrected by the clinician before filing."
B: Patient declined. "AI scribe explained; patient declined. Standard note-taking used."
C: Temporary audio or transcript retention applies. "Patient informed about the AI scribe's capture and retention arrangements under the service policy. Draft reviewed and corrected before filing."
For the third version, the patient-facing explanation must genuinely have covered the relevant arrangements. Do not insert it automatically because a supplier may retain some data.
Keep the entry proportionate. The objective is a truthful record of material events, not an expansive legal narrative. A default macro claiming review is inappropriate when the note has not yet been read. Similarly, a template must not record consent to treatment merely because the patient accepted documentation assistance.
The GMC's recording-decisions guidance, checked on 10 October 2026, supports proportionate records of decisions and agreed actions. A completed form is not a substitute for the individual discussion.
Poster, waiting-room screen and website wording
A short proposed poster reads:
Our service may use an AI scribe to help prepare consultation notes. It listens during the appointment and creates a draft. Your clinician checks and corrects that draft before it becomes part of your record. You can ask us not to use the tool, or to stop it. We will take notes in the usual way instead. Please ask a member of staff about information handling or other questions.
That statement should be displayed only where it accurately describes the service. Offer an accessible version rather than assuming that a small print notice is sufficient for everyone.
A fuller proposed website paragraph reads:
We may use an AI-enabled ambient scribing system to support clinical documentation. It processes consultation information to generate draft material such as a transcript, summary or letter. The responsible clinician checks and corrects the draft before filing or using it. Our privacy information explains what is captured, the organisations involved, authorised access, retention, security and relevant patient rights. Patients can decline this tool and receive standard note-taking instead.
The website should then provide the actual details, not simply repeat that details exist elsewhere. Keep the information aligned with configuration changes, including newly enabled functions or changed suppliers. A poster describing note drafting becomes incomplete when a deployment adds other processing purposes.
Why patient trust requires more than a lawful arrangement
Healthwatch's report of 16 July 2026 drew on a representative YouGov poll of 4,039 adults conducted in April 2026, alongside a separate collection of personal accounts. Reported comfort with AI scribes differed by topic: 48% were comfortable for routine appointments, compared with 23% for domestic-abuse discussions. Those are reported attitudes, not measured rates of inaccurate records or clinical harm. The qualitative accounts should not be converted into population error estimates. See Healthwatch's research.
A fictional example illustrates the implementation question. A patient accepts the scribe while discussing an administrative concern, then begins describing coercion at home. The clinician can acknowledge that the topic has changed and offer to stop recording before continuing. Acceptance at the start need not be treated as a commitment to discuss everything through the same tool.
The same approach matters when relatives, interpreters or carers are present. Explain the room-level arrangement and avoid assuming that one person's acceptance answers every question about third-party information. Refer unusual circumstances to the approved local process rather than improvising broad assurances.
When you may need something stronger than implied consent
The direct-care explanation is not a blanket permission for every subsequent use of consultation material. Model training, product development, research, marketing, non-care analytics and extended retention require purpose-specific assessment. Sharing identifiable information outside the arrangements covered by the service's assessment also needs examination.
A fresh assessment does not necessarily mean that consent is always the appropriate solution. It means identifying the purpose, applicable legal requirements, confidentiality implications, necessity, recipients and safeguards before proceeding. Long retention needs a reason; a supplier's technical ability to retain material is not that reason.
The ICO's guidance on lawfulness in AI, checked on 10 October 2026, is relevant to this separation of purposes. The organisation should involve its information-governance and legal advisers rather than ask clinicians to resolve a new processing purpose during an appointment.
The minimum transparency and governance checklist
A useful pre-deployment review has four parts. Under patient-facing transparency, check that staff can explain capture, output, processing and choice, and that notices match reality. Test the refusal pathway with an actual workflow rehearsal.
Under documentation integrity, check that the responsible professional reviews the draft before it is used or filed. Include controls against unsupported additions, misleading copy-forward and approval macros that claim more than the clinician did. Fluent language should not be accepted as evidence of an accurate record.
Under information governance, complete or update the data protection impact assessment and document the lawful basis and processing arrangements. Review access, storage, sharing, secondary use and security. Consider the relevant NHS assurance requirements, including clinical-risk standards, DTAC and the Data Security and Protection Toolkit where applicable to the organisation and deployment.
Under clinical safety, identify the accountable clinical lead, applicable safety-case and hazard-log arrangements, and the route for reporting, investigating and learning from problems. The distinction between manufacturer and deployment responsibilities remains important; another organisation's approval cannot describe every local risk.
This is a proposed working checklist, not a claim that completing four headings establishes legal compliance or removes clinical risk.
A practical way to use iatroX alongside AI scribes
Documentation assistance and clinical-source checking serve different purposes. As described in iatroX's materials on 10 October 2026, Ask-iatroX supports referenced clinical questions, while its methodology explains retrieval and output-checking processes. Those descriptions do not make every answer correct.
The earlier version of this guide recommended orienting through the Knowledge Centre, opening the relevant NICE, CKS or SIGN source, and using a referenced scenario explanation for nuance. That remains a source-checking workflow, not a substitute for reading the applicable guidance or assessing the patient. Use general or fictional questions rather than transferring identifiable consultation material into an unrelated tool.
A record can state which guidance informed a material decision and when it was checked. It should say that safety-netting was given only when that discussion occurred. Neither a citation, a shared explanation nor an AI-generated note provides automatic legal protection.
Sources and further reading for UK services
Alongside the current NHS information-governance guidance, the original source pathway includes CQC GP Mythbuster 109, NHS England's broader ambient-scribing implementation guidance and the national ambient-scribing information page. The latter is a useful current route into national materials previously reached through NHS transformation pages.
The ICO's AI transparency guidance and Londonwide LMCs' ambient-scribe resource provide additional governance reading. None replaces checking the current supplier contract, local policy and the function actually being deployed.
Choose the right tool for the task
An appropriate scribe can help prepare documentation; a reference source can support checking medical information; a clinician still needs to establish what happened and what the patient understands. Trust becomes more credible when those roles are visible and a patient can say no without having to justify the decision.
Frequently asked questions
Is explicit consent always required for an NHS AI scribe?
NHS England's guidance checked on 10 October 2026 does not require explicit consent for the individual-care processing it describes, but requires transparency and respect for dissent. Other purposes or circumstances need their own assessment.
Can a patient ask for the scribe to be stopped?
Yes, the direct-care arrangement described in the guidance requires the service to respect dissent. Stopping capture and handling previously processed information are separate operational questions.
What should the clinician record about AI-scribe use?
Record the relevant explanation, patient preference and review actually undertaken, in proportionate terms. Do not use a template to imply that advice, consent or checking occurred when it did not.
Check the sources behind a clinical question with Ask-iatroX →