GB
You've built a sleep-tracking ring. Or a fertility app. Or maybe you've got some very clever AI helping clinicians spot conditions earlier.
You're probably calling it innovation, wellness, digital health or smart living.
But here's the catch: UK medical device regulations don't really care what label you've given it.
If your product is intended to diagnose, monitor, prevent or manage a medical condition, the UK's regulator, the Medicines and Healthcare products Regulatory Agency (MHRA), may consider it a medical device. That can trigger a range of regulatory obligations including classification, registration and compliance requirements.
So, let's talk about when your shiny health tech product might actually be a regulated medical device in the UK, and what founders need to do about it.
In simple terms, a product is considered a medical device if its intended purpose involves diagnosing, preventing, monitoring or treating a medical condition.
Under the UK Medical Devices Regulations 2002, a product (including healthcare apps and standalone software) may be classified as a medical device if it is intended to:
• Diagnose, prevent, monitor or treat disease
• Compensate for injuries or disabilities
• Investigate, replace or modify the anatomy or physiological processes
• Support clinical decision-making
The key phrase here is intended use.
It's not just about what your product does. It's about what you say it does through your website, marketing materials, app store listings, sales presentations and investor decks.
For example, if you're positioning your platform as helping with:
• PCOS management
• Fertility tracking
• Mental health screening
• Diagnostic test interpretation
you may be entering software as a medical device territory, even if your product is primarily software.
Less likely to be a medical device: general wellness tracking, lifestyle recommendations, a fitness coaching app, or sleep habit logging.
More likely to be a medical device: detecting or monitoring a medical condition, diagnostic recommendations, clinical decision support software, or sleep disorder detection.
Software as a Medical Device (SaMD) refers to software that performs a medical function without being part of a physical medical device.
In other words, the software itself is the medical device.
This is increasingly relevant for health tech startups because many modern products rely on algorithms, machine learning and digital platforms rather than traditional hardware.
Examples include AI-powered diagnostic tools, fertility tracking applications that make health-related predictions, and mental health platforms that assess symptoms or screen users for potential conditions.
The MHRA has published specific guidance on software as a medical device because software products can fall within medical device regulations even when there is no wearable, sensor or physical equipment involved.
Usually not.
A friendly reminder: disclaimers like "for informational purposes only" won't save you if the rest of your marketing suggests otherwise.
If your health app implies that users can rely on it for diagnosis, treatment decisions or clinical advice, the regulator may still classify it as a regulated medical device 🩺.
It's the overall impression that matters, not just the disclaimer.
This is particularly important for startups working in:
• AI diagnostics
• Mental health screening
• Fertility prediction apps
• Symptom-checking tools
where even subtle wording can trigger medical device classification.
Medical devices are classified according to risk. The higher the risk to patients, the greater the regulatory requirements.
Class I (low risk): basic health monitoring apps, non-invasive devices
Class IIa (medium risk): fertility prediction software, some diagnostic tools
Class IIb (higher risk): clinical decision support software influencing treatment
Class III (highest risk): life-supporting or implantable devices
The classification affects:
• The level of assessment required
• Technical documentation requirements
• Clinical evidence expectations
• Ongoing compliance obligations
AI software and diagnostic tools frequently fall into Class IIa or above, particularly where treatment decisions could be influenced by the software's outputs.
If your product qualifies as a medical device, don't panic. But do get organised.
1. Determine your device classification
Your classification determines which regulatory requirements apply and how much evidence you'll need to provide.
2. Complete conformity assessment and obtain the relevant marking
Most devices require a conformity assessment before being placed on the market. Depending on the circumstances, this may involve UKCA marking or continued reliance on CE marking during transitional arrangements.
Current transitional arrangements mean certain CE-marked devices can continue to be accepted in Great Britain until between 2028 and 2030, depending on device type and certification status.
3. Register with the MHRA
Medical devices marketed in Great Britain generally need to be registered with the MHRA before being supplied.
4. Prepare clinical safety and performance documentation
You'll need evidence demonstrating that the device is safe, performs as intended and is supported by appropriate risk management processes.
Good news. But that doesn't mean you're entirely off the hook.
You may still need to consider:
• UK GDPR and the Data Protection Act 2018 if you're processing health or personal data.
• CQC registration if you're delivering or arranging regulated clinical activities.
• NHS partnerships and procurement requirements.
• NHS DTAC (Digital Technology Assessment Criteria) if you're planning to work with NHS organisations or integrate with NHS systems.
Even products that fall outside medical device regulations can face significant compliance obligations.
The UK regulatory landscape continues to evolve.
Recent MHRA reforms introduced enhanced post-market surveillance requirements. Manufacturers are increasingly expected to actively monitor safety and performance data after products have been launched and, in some cases, provide periodic safety reporting.
The UK is also introducing Unique Device Identification (UDI) requirements to improve product traceability throughout the supply chain and make it easier to identify safety issues when they arise.
Another area that causes confusion is Northern Ireland. While Great Britain follows the UK Medical Devices Regulations framework, Northern Ireland continues to align with the EU Medical Device Regulation (EU MDR) regime under separate arrangements.
For founders operating across multiple markets, understanding these differences early can save considerable time and cost later.
