The UK government is currently emphasising the potential of innovative technology to enhance the effectiveness and efficiency of patient care. Both of the recently published NHS England highlighted the potential for harnessing the power of technology, and AI in particular, to support the delivery of healthcare. Other initiatives, such as innovator passports and the Medtech Compass, aim to reduce repetitive compliance and validation tasks and bring effective MedTech swiftly into operation.
So how does that align with recent communications from NHS England urgently halting the deployment of AI scribing tools in the NHS if they are not at least a Class I medical device? This restrictive approach seems to contradict NHS England’s own guidance that addresses whether or not an AI scribing tool should be considered a medical device.
In this blog, we will look at the current regulatory expectations for developers, and how to navigate the development process in collaboration with the NHS.
What is a medical device?
Going back to basics, the Medical Devices Regulations 2002 definition of a medical device includes software which is intended to be used for human beings for a variety of medical purposes. This can include anything within the diagnosis, monitoring or treatment space relating to injuries or diseases. It also includes software forming part of another device that is intended by the manufacturer to be used specifically for diagnosis or therapeutic purposes.
When is AI a medical device?
We recently explored some of the issues surrounding borderline devices in the healthcare space. Traditionally with borderline software products, the very basic analysis is often whether the software is simply replacing an existing “hard copy” system or if it is doing anything with the data which could influence the treatment of the patient. The same principles can be applied to AI tools.
The particular example in the NHS England briefing was AI scribing tools, which are now commonly used by clinicians to support them with note-taking in consultations with their patients. Nominally, this is a simple administrative use of AI. The line becomes less clear if the AI tool does anything on top of transcription such as summarizing the conversation (which may already be a medical device). When the AI starts interpreting symptoms, producing a summary, offering suggested treatment plans or suggestions for diagnosis, it is likely in medical device territory and would need to meet the relevant regulatory requirements to be placed on the market or put into service.
Can AI be deployed without a medical device classification?
To what extent AI tools can be used in healthcare without a medical device classification will depend on what the AI tool does and how it is being used.
Assuming the AI tool would be classified as a medical device, it could still be lawfully made available without a UKCA marking in certain limited circumstances. One of those includes where it is being used as part of a clinical investigation, usually undertaken to gather clinical data in support of the registration of the device with the MHRA. There are still regulatory safeguards in place in relation to these activities, intended to ensure that appropriate regulatory oversight is present for such activities. In those instances, the device would not necessarily be registered with the MHRA, but the investigation would be notified to them.
We would therefore assume that the NHS England guidance is aimed at products which are actively being marketed and sold, rather than deployments which are part of a proper investigation.
Practical considerations
Although the compliance hurdles for deploying AI tools in the NHS are complex (this blog only touches on the medical device angle: data privacy and information security have their own requirements), resources are available to support developers.
The starting point should be determining whether the proposed AI tool qualifies as a medical device and then which pathway and classification would apply. The MHRA’s Software Group provides support for pre-market queries and technical file reviews. There is also a helpful roadmap from the MHRA which can guide through topics like clinical evaluation and usability testing.
Depending on the tool, the AI Airlock (a regulatory sandbox launched in 2024) could be utilized by developers to test AIaMD in real-world NHS settings under regulatory supervision.
Looking beyond medical device regulation, it is also worth engaging early with clinicians and the NHS to help understand how the tool could fit into NHS workflows and understand data governance requirements. This can help design tools in alignment with clinical needs and with NHS Digital and NHS England requirements.
Conclusion
The regulatory landscape for AI in healthcare is evolving rapidly, but the direction of travel is clear: patient safety, transparency, and collaboration are paramount and early engagement with the MHRA and relevant NHS stakeholders can smooth the path to deployment of tools which could, ultimately, benefit our entire healthcare system as well as individual patients.
Our content explained
Every piece of content we create is correct on the date it’s published but please don’t rely on it as legal advice. If you’d like to speak to us about your own legal requirements, please contact one of our expert lawyers.