Key takeaways
- Software is a medical device when its intended purpose is medical, such as diagnosis, monitoring or treatment, not because of the technology it uses.
- MHRA guidance says booking, prescription request and virtual consultation software is unlikely to be a device if it only has an administrative function.
- Symptom checkers and triage tools that judge seriousness or likelihood may be devices; tools that only signpost are unlikely to be.
- Disclaimers do not change the answer if the product makes or implies medical claims.
Why practices need to know the rules
The MHRA says many software and AI products used in health and social care are regulated in the UK as medical devices[1]. At the same time, AI is arriving in general practice quickly: in a 2025 Nuffield Trust and RCGP survey, 28% of GPs said they currently use AI tools in clinical practice[2]. Of all GPs, 13% use tools provided by their practice and 11% use tools they obtained themselves[3], which means some AI use happens outside any practice-level check.
Practices are not usually the manufacturer, so most legal duties under the medical device regulations fall on the supplier. But the practice chooses what to buy, decides how it is used and is responsible for patient safety in its own setting. Buying a tool that should be a regulated device but is not, or using a device outside its intended purpose, creates clinical and legal risk for the practice.
The test: intended purpose
Whether software is a medical device depends on what the manufacturer says it is for, its intended purpose, and whether that purpose is medical. Medical purposes include diagnosis, prevention, monitoring, prediction, prognosis and treatment or alleviation of disease or injury. The technology does not decide the answer: a simple spreadsheet can be a device if it calculates doses, and a sophisticated AI system may not be if it only manages bookings.
The MHRA's guidance on stand-alone software sets out examples. Software used to book an appointment, request a prescription or have a virtual consultation is unlikely to be considered a medical device if it only has an administrative function, and an electronic patient record that simply replaces a patient's paper file does not meet the definition[4]. The guidance applies to software placed on the Great Britain market, where the UKCA mark is used for medical devices[4].
| Function | Likely status | Why |
|---|---|---|
| Online appointment booking and reminders | Unlikely to be a device | Administrative function only |
| Repeat prescription requests | Unlikely to be a device | Administrative, no clinical decision by the software |
| Video or text consultation platform | Unlikely to be a device | A channel for the clinician, who makes the decisions |
| Electronic record that replaces paper notes | Not a device | Stores information without changing it |
| Symptom checker that ranks likely conditions | May be a device | Indicates likelihood of a match |
| Triage that assigns urgency or red flags from symptoms | May be a device | Filters by severity or seriousness |
| Tool that only signposts, such as see your GP or go to A&E, without assessing likelihood | Unlikely to be a device | Signposting to suitable care only |
| Dose calculator or treatment recommender | Likely to be a device | Drives a clinical decision |
Symptom checkers, triage and AI assistants
The grey zone for practices is software that talks to patients before a clinician does. MHRA guidance says symptom checkers that output a subset of matching conditions, indicate the likelihood of a match, recommend treatment or filter by red flag, severity or probability may be devices[4]. Software that offers only reference information, lists all matching conditions without ranking them, or only signposts the user to suitable care is unlikely to be a device[4]. Symptom checkers are class I unless they allow direct diagnosis, in which case they are class IIa[4].
AI phone and chat assistants used for reception tasks fall on either side of the line depending on what they do. An assistant that collects the reason for a call, books an appointment and passes the request to a care navigator is doing administrative work. One that decides from symptoms whether a patient needs a same-day appointment, or tells them their problem is not serious, is making a clinical judgement and may be a medical device. Ask suppliers exactly which side their product is on, and see the intended purpose statement in writing.
A product that says 'for information only' is still a medical device if it makes medical claims elsewhere. MHRA guidance says general disclaimers are not acceptable where medical claims are made or implied in labelling or promotion[4].
Questions to ask a supplier
What is the intended purpose?
Ask for the written intended purpose or intended use statement. Check it matches how you plan to use the product, and how the supplier markets it.
Is it a medical device, and what class?
If yes, ask for the class, the UKCA or CE marking that applies in Great Britain and the MHRA registration details.
If not, why not?
Ask for the supplier's reasoning. A clear answer that maps to MHRA guidance is reassuring; a vague one is not.
Where is the clinical safety evidence?
Ask for the supplier's clinical safety case and hazard log under the NHS clinical risk management standard for manufacturers, and confirm who your own clinical safety officer will be under the standard for deploying organisations.
How are changes managed?
AI products change. Ask how updates are tested, how you will be told and whether a change could alter the intended purpose.
How are incidents reported?
Agree how the supplier will tell you about safety issues and how you will report problems to them and to the MHRA.
Responsibilities when a product is a device
- Use it only within its intended purpose. Using a device for a purpose the manufacturer has not claimed can make the practice responsible for the risk.
- Train staff on what the device does and does not do, and on what to do when its output seems wrong.
- Keep a local clinical safety record of how the device is used in your workflows.
- Report problems with software as a medical device through the Yellow Card scheme in England and Wales; Scotland and Northern Ireland have their own reporting routes[1].
- Review use when the supplier releases a significant update.
Data protection is a separate question
Medical device status and data protection are different tests. A booking tool that is clearly not a device still processes special category health data and needs a lawful basis, a data processing agreement and, usually, a data protection impact assessment. A regulated device can still be set up in a way that breaches data protection law. Ask both sets of questions every time.
For AI tools, ask specifically where data is processed, whether recordings or transcripts are kept and for how long, and whether patient data is used to train or improve the supplier's models. If the answer to the last question is yes, check the legal basis and whether patients can opt out, and record the decision in the DPIA.
What GPs are doing with AI, and what worries them
Among GPs who use AI, 57% use it for clinical documentation and note-taking and 44% for administrative tasks[5]. Among GPs not using AI, professional liability and medico-legal issues were a concern for 89% and lack of regulatory oversight for 88%[6]. Patients share some of that caution: healthcare is the area where UK adults most often say AI needs careful management to prevent negative outcomes, at 29%[7].
Regulatory status answers part of the liability question. A tool that is a properly classified and registered device has been through conformity assessment; a tool that is administrative only should be used only for administrative work. The risk sits in the middle: products used for clinical decisions without being regulated for them.
A practice policy on AI and clinical software
- Keep a register of every software tool that touches patient care or patient data, including free tools.
- Require approval from a named lead before any new tool is used, including tools staff find themselves.
- Record each tool's intended purpose and whether it is a medical device.
- Check data protection, including where data is processed and whether it is used to train the supplier's models.
- Ban the entry of identifiable patient information into consumer AI tools that have not been approved.
- Review the register every six months and remove tools no longer in use.
Example: two AI front-door tools compared
Example: a fictional practice considers two products. Product A answers calls, takes the patient's details and reason for contact, books routine appointments from rules set by the practice and sends anything clinical to a care navigator. Its intended purpose is administrative, and the supplier explains why it is not a device. Product B asks about symptoms, assigns an urgency level and tells low-urgency patients to self-care. Its supplier says it is not a medical device, but its marketing talks about safe triage.
The practice's clinical safety officer concludes that Product B's real function is triage by seriousness, which MHRA guidance suggests may be a device, and asks the supplier for its regulatory position in writing. Until that arrives, the practice pilots only Product A, with a clinical safety review after three months.
Frequently asked questions
Is an online booking system a medical device?
Usually not. MHRA guidance says software used to book appointments, request prescriptions or hold virtual consultations is unlikely to be a device if it only has an administrative function.
Is an AI triage tool a medical device?
It may be. If it assesses symptoms to judge seriousness or likelihood of a condition, it may meet the definition. If it only signposts to suitable care, it is unlikely to.
Who is responsible for registering a medical device with the MHRA?
The manufacturer, or their UK responsible person. The practice should check the registration and use the device within its intended purpose.
How do we report a problem with medical device software?
In England and Wales, report it through the MHRA Yellow Card scheme, and tell the supplier. Scotland and Northern Ireland have their own incident reporting systems.
References
GOV.UK (Medicines and Healthcare products Regulatory Agency) (2025). Software and artificial intelligence (AI) as a medical device (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑
Medicines and Healthcare products Regulatory Agency (GOV.UK) (2023). Medical device stand-alone software including apps (including IVDMDs) (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑
GOV.UK (Department for Science, Innovation and Technology) (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑