The scenario
A clinician wants to roll out Heidi, Tortus, Dragon DAX or another ambient scribe across the clinic.
The board approves the subscription.
No DPIA has been completed. No vendor evidence file exists. No patient transparency statement is in place. No human-review workflow has been documented. No incident reporting pathway for AI errors has been established.
Evidence to have ready before routine deployment
- Supplier clinical safety evidence, such as DCB0129 where applicable, confirmed in writing
- Local clinical safety review structure, such as DCB0160-style safety case, hazard log and monitoring plan where relevant
- DPIA likely required or strongly indicated for DPO/legal review where special category health data, voice processing and new technology are involved
- Patient transparency: clear explanation before use, with objection or dissent route where applicable
- Human review workflow: clinician reviews and edits AI-generated notes before they enter the patient record
- Staff guidance and training on approved use, scope and oversight expectations
- Incident reporting pathway for AI-related errors or unexpected outputs
- Board-level benefit-risk review before and after deployment
What ELSA AI does
- Produces an Ambient Scribe Assessment Sheet mapping vendor evidence status, data flows, DPIA readiness, patient transparency, clinical safety indicators and human oversight across the tool being deployed
- Identifies evidence gaps against NHS England ambient scribe guidance, used as a governance-standard signal for private clinics adopting similar clinical AI workflows
- Structures the evidence so the clinic’s Clinical Safety Officer, DPO and board can review, adopt and own the final position
- Produces a DPIA readiness workpack and patient transparency wording as part of the Clinical AI Safe Usage Launchpad™, aligned to ICO and NHS England expectations where relevant
ELSA AI does not provide clinical safety sign-off, act as Clinical Safety Officer or approve DCB0160 documentation. Final clinical safety decisions remain with the clinic’s appointed Clinical Safety Officer or clinical safety lead.
Ambient scribe rollout
Do we need a DPIA for our ambient scribe?
A DPIA is likely required or strongly indicated where an ambient scribe processes consultation audio, clinical notes, patient identifiers, special category health data, voice data or new technology workflows.
ELSA AI does not make the final legal determination. We identify the DPIA indicators, map the evidence gaps, and prepare a DPIA readiness position for DPO/legal review.
The final DPIA decision and sign-off remain with the clinic's DPO or legal adviser.
Advisory governance support only. Not legal advice, clinical safety sign-off, DPIA sign-off, insurer coverage advice, CQC certification or ICO approval.