Keep clinical purpose and confirmation in change control
MHRA guidance distinguishes administrative ambient scribing from products with a medical intended purpose. Review changes to clinical recommendations, confirmation and promotional claims before extending the workflow.
Keep sources linked to the record used for review. The diagram does not represent automatic approval.
An ambient scribing product can change through a model update, workflow integration or new promotional claim. A previous assessment of its regulatory status needs to be reconsidered when those changes affect its intended purpose. A confirmation step is part of that review, rather than an independent exemption from device regulation.
The MHRA’s guidance on ambient voice technology-enabled products, published on 29 July 2026, sets out administrative and medical-purpose examples for Great Britain. Its scope is England, Wales and Scotland. Northern Ireland has a separate applicable device regime. Use the guidance to assess the particular product and workflow, not to assign one status to every scribing tool.
Put intended purpose and clinical confirmation into change control. Retain the assumptions supporting the current assessment and identify which changes require a new one. Clinical review can reduce risk, but does not remove a medical intended purpose from a product that has one.
Where the line actually falls
The guidance’s examples distinguish documenting existing information for clinician review from features intended to recommend diagnoses or treatment. Product functionality and the claims made about it both matter. The presence of a human reviewer alone does not determine the outcome.
The practical review should examine whether an output restates source information, adds a recommendation or influences a clinical action. Technical difficulty is not the classification test. Preserve representative outputs and the stated purpose so regulatory specialists can assess the change in context.
- 01 Capture Audio becomes a transcript. Nothing is added.
- 02 Restate Summary, letter, code — all from what was said.
- 03 Derive A diagnosis or a follow-up nobody mentioned.
- 04 Act The order is placed, or the record is written.
An autonomous path into clinical action deserves particular scrutiny. The MHRA’s announcement also states that clinicians remain responsible for reviewing and verifying generated outputs before their use in patient care. Map the actual handoff, including any route that bypasses confirmation.
Review instructions for use, labelling, websites and sales material together with the software. A medical-purpose claim can affect qualification even when the underlying feature performs administrative work. A general disclaimer does not neutralise conflicting claims elsewhere. The promotional review therefore needs an owner within the change process.
Keep the original intended-purpose assessment linked to release changes. New functionality can require reassessment even when the product began as an administrative tool.
Keep confirmation within the assessed workflow
Human review can be both a risk control and a material feature of the intended workflow. Treat its presence, scope and operation as recorded assumptions. A proposal to remove a confirmation step requires review of those assumptions before its throughput benefit is accepted.
For a particular administrative-use assessment, clinician review may form part of the conditions supporting the conclusion. Removing it can change the workflow that was assessed. Determine the resulting status with the manufacturer’s regulatory affairs function rather than treating a click as the sole classification rule.
A change to clinical confirmation should reopen the workflow assessment before release.
Check whether confirmation operates in practice. Preselected codes, automatic saves, timeouts and bulk acceptance can change what a clinician actually reviews. Observe representative use and test bypass paths. The interface label alone does not show that the intended review took place.
What to do about it
Include intended purpose in release acceptance. Ask whether the change adds a clinical recommendation, changes a promotional claim or allows an output to reach a record or action through a different review path. Preserve the answer and escalate material changes before deployment.
Contract for notification if you are deploying rather than building. A supplier’s roadmap is now part of the deploying organisation’s regulatory position, and the deploying organisation does not see it. The announcement of the guidance puts the duty to identify a change in a product’s functionality that may alter its regulatory status on NHS boards, and that is a duty which cannot be discharged without the supplier’s cooperation. Ask for it in writing before the renewal, not after the release note.
Read the marketing copy as a regulated artefact. The claims that set intended purpose are usually written by people who have never seen the change-control process. A single sentence added to a pricing page can make a medical claim that the engineering team would not recognise as one.
Evaluate the intended boundary. Check unsupported additions to summaries and whether reviewers can inspect, amend and reject outputs before use. Record edits, review actions and bypass behaviour together. An edit rate alone cannot establish that review was adequate, and a lack of edits does not prove that it was absent.
A similar change-control principle applies where intended use and oversight affect other regulatory obligations. It is an architectural inference, not a claim that every regime uses the same qualification test. The sector response, including techUK’s position statement of 14 August 2026, supports reading the guidance alongside the actual medical-purpose claims.
What this does not tell you
This is guidance on how existing medical device law applies. It is not a change in the law, and it does not decide the status of any particular product. Classifying a specific product is a regulatory question for its manufacturer, and the legal interpretation stays with counsel and the regulatory affairs function. The institute assesses readiness and maps controls against obligations. It does not determine device status for anyone, and no assessment here or anywhere else substitutes for the manufacturer’s own determination.
Nor does the guidance settle what counts as adequate clinician review, or what a deploying organisation must do under NHS England’s separate expectations for these products. Both are open, and a piece that pretended otherwise would be selling certainty that does not exist.
Before accepting a release, the clinical safety officer should locate changes to recommendations, confirmation paths and promotional claims. Join those records to the manufacturer’s assessment and the deploying organisation’s safety review. A product’s earlier status should remain traceable to the conditions that still hold.