What is Software as a Medical Device?
We support the world's largest medical device manufacturers to navigate this complex regulatory environment and achieve commercial success.
Who Needs SaMD Support?
Any business developing, marketing, or deploying software with a medical purpose will require specialist SaMD regulatory expertise to achieve compliance. Businesses ranging from digital health startups through to established medical device manufacturers expanding into software-based solutions need to be prepared for medical device regulations. Increasingly these regulations intersect with regulations covering cybersecurity and AI safety.
Our clients seek our support at varied stages of product development and commercialisation. Common engagement triggers include preparing for UK market entry, establishing a regulatory classification, implementing a quality management system, addressing NHS procurement requirements, responding to regulators and preparing for investor due diligence.
What Does SaMD Compliance Involve?
The route to market for SaMD products involves a series of regulatory, quality, clinical, and post-market surveillance activities which demonstrate safety, performance, and compliance.
- 1
Qualification and Classification
The first step is to determine whether your product qualifies as a medical device based on its intended purpose, marketing and risk. If a product qualifies as a medical device it will be classified from Class I to Class III.
- 2
Quality Management System
Manufacturers will require an ISO 13485 aligned or certified Quality Management System (QMS) to manage design, development, supplier controls, documentation, and ongoing compliance.
- 3
Software Lifecycle and Risk Management
Software development will align with standard IEC 62304 and risks are managed based on alignment and certification against ISO 14971. This stage includes addressing software planning, design, verification, validation, cybersecurity, and risk control activities.
- 4
Clinical Evaluation
Your product must be safe and effective for implementation according to its intended medical purpose and forecast clinical benefits. This is a highly complex stage and may involve a range of activities depending on the classification status of your product including literature reviews, performance testing, validation studies, clinical trials and clinical data analysis. The primary output is a Clinical Evaluation Report (CER).
- 5
Conformity Assessment and Market Access
Once all the required evidence and documentation has been developed and approved we then recommend manufacturers pursue UKCA or CE certification.
- 6
Post-Market Surveillance
When a product is certified and placed in a market, you are still obligated to monitor product performance, manage complaints, investigate incidents, and maintain ongoing compliance. Post-market surveillance is a priority area for regulators and has expanded its remit in recent years to include monitoring risks such as cybersecurity vulnerabilities.
Common Software as a Medical Device Challenges
The most common challenge for our clients is determining whether their software product qualifies as a medical device and, if so, determining the correct classification based on a target market’s regulatory standards.
Many of our clients also come to us after struggling to retrofit medical device requirements onto products that have already been developed using agile software practices or even sold prior to updated regulations addressing SaMD. For example, implementing ISO 13485 and IEC 62304 after development has already started can create delays, additional costs, and documentation gaps.
Many of our clients now invest significantly in AI and this creates additional challenges for clinical evidence generation, algorithm change management, transparency, explainability, hallucinations and cybersecurity.
Given these complexities, having access to experts specialising in clinical safety, cybersecurity and medical device regulation is essential for accelerating compliance and market entry.
How The AbedGraham Group Supports SaMD Compliance
Qualification and Classification Assessment
We help you determine whether your product qualifies as a medical device, establish its classification, and develop the documentation you need to address market entry in the UK and Europe.
End-to-End Regulatory Delivery
We offer an end-to-end service from initial assessment through to MHRA registration including technical documentation development and post market surveillance.
Quality Management and Software Lifecycle Implementation
We design, implement, and optimise ISO aligned systems such as ISO13485, ISO14971, ISO42001 and ISO27001 that are critical for demonstrating safety and quality for your products.
AIaMD and Clinical Evaluation Support
We have specialist expertise for assessing AI centric products through our ISO42001 trained auditors and support our clients to define product features and requirements so that only essential features are introduced into a regulated market.
Outsourced Regulatory Leadership and Post-Market Surveillance Support
For clients requiring ongoing support, we provide outsourced regulatory leadership, post-market surveillance monitoring, vigilance processes, regulatory horizon scanning and UK Responsible Person (UKRP) services for international manufacturers.
Why Choose AbedGraham for SaMD Compliance?
At The AbedGraham Group we combine deep expertise in clinical safety, cybersecurity and medical device regulation to support our clients to navigate complex SaMD and AIaMD requirements with confidence.
We consult businesses of all sizes from startups to global manufacturers. Our documentation always withstands regulatory scrutiny and supports your product roadmap. Rather than working as external advisors, our consultants will integrate closely with your teams to deliver tailored solutions that support long-term compliance.

AI & Medical Devices
Talk to a SaMD Specialist
Book a discovery call today to discuss your SaMD requirements for the UK market.
Services Related to SaMD
DCB0129 Clinical Safety
Clinical safety support for software manufacturers supplying digital health technologies to the NHS, including hazard assessments, safety cases, and compliance with DCB0129 requirements.
DSPT Audit Services
Independent assessment and support for organisations seeking compliance with the NHS Data Security and Protection Toolkit (DSPT), helping demonstrate good data security and information governance practices.
Frequently asked questions
Software may qualify as a medical device if it is intended to diagnose, prevent, monitor, predict, treat, or alleviate a disease or medical condition. The intended purpose of the software is the primary factor regulators consider when determining whether it falls within medical device regulations. General wellness, administrative, or lifestyle applications typically do not qualify as Software as a Medical Device (SaMD).
SaMD is classified according to the risk associated with its intended purpose and the significance of the information it provides to healthcare decisions. Depending on the jurisdiction and device function, software may fall into Class I, IIa, IIb, or III. Higher classifications generally require greater levels of clinical evidence, regulatory scrutiny, and independent conformity assessment.
If your software qualifies as a medical device and is being placed on the Great Britain market, UKCA marking requirements apply. The route to compliance depends on the device classification and applicable regulations. Manufacturers must also register relevant devices with the MHRA before placing them on the market.
Artificial Intelligence as a Medical Device (AIaMD) is a subset of SaMD. While all AIaMD products are software medical devices, not all SaMD products use artificial intelligence. AIaMD solutions utilise AI or machine learning techniques to perform medical functions such as diagnosis, prediction, monitoring, or clinical decision support.
IEC 62304 is the internationally recognised standard for medical device software lifecycle processes. In most cases, manufacturers developing SaMD are expected to apply IEC 62304 principles throughout software development, maintenance, verification, and change management activities. Compliance helps demonstrate that software has been developed using a controlled and risk-based approach.
While requirements vary depending on device classification and market, most manufacturers benefit from implementing an ISO 13485-compliant Quality Management System. ISO 13485 provides a structured framework for design controls, document management, supplier oversight, corrective actions, and ongoing regulatory compliance, supporting both market access and organisational maturity.
Medical device compliance and NHS procurement requirements are not the same. While SaMD regulation focuses on safety, performance, and market access, NHS organisations may also require suppliers to demonstrate compliance with the Digital Technology Assessment Criteria (DTAC), covering areas such as cybersecurity, clinical safety, interoperability, and data protection.
Timescales vary significantly depending on the complexity of the software, its classification, the maturity of existing quality systems, and the target markets. Early-stage products may require several months to establish the necessary documentation and evidence, while higher-risk products requiring external conformity assessment can take considerably longer.
An Emergency Use Authorisation (EUA) is a regulatory mechanism that allows certain medical products to be deployed during declared public health emergencies before full regulatory approval has been completed. EUAs are jurisdiction-specific and typically apply only in exceptional circumstances where there is an urgent public health need.
Manufacturers based outside the United Kingdom who wish to place medical devices on the Great Britain market generally require a UK Responsible Person (UKRP). The UKRP acts as the manufacturer's local regulatory representative, supports communications with the MHRA, and fulfils specific regulatory obligations required under UK medical device regulations.
