The European Medical Device Regulation (EU MDR) establishes a robust, transparent regulatory framework intended to improve clinical safety and support consistent market access for manufacturers. Its requirements cover qualification, classification, clinical evaluation, conformity assessment and CE marking, technical documentation, and quality management systems (QMS).
For continued innovation, SaMD manufacturers should understand the applicable EU MDR requirements and maintain a robust system supporting their devices and software functionalities. Relevant guidance, including the updated MDCG 2019-11 rev.1 issued in June 2025, can help with software qualification and classification. This supports product quality, patient safety, and regulatory compliance.
The product must adhere to the definition of a “medical device”, “software”, or in vitro diagnostic medical device according to Regulation (EU) 2017/745– MDR and/or Regulation (EU) 2017/746 – IVDR.
ISO 14971 and IEC 62304 are international standards that support risk management and software lifecycle processes, respectively, in demonstrating compliance with applicable EU MDR requirements. The former Medical Devices Directive (MDD 93/42/EEC) has been replaced by the MDR framework, subject to applicable transitional provisions.
How SaMD classified in Europe
1. Annex VIII, Chapter III, Rule 11 of the EU MDR addresses software classification. Software intended to provide information used to make decisions for diagnostic or therapeutic purposes is generally Class IIa, unless the impact of those decisions requires a higher classification:
a. If such decisions may cause serious deterioration of a person’s state of health or a surgical intervention, the software is Class IIb. Classification depends on the software’s intended purpose and the impact of its decisions.
b. If such decisions may cause death or irreversible deterioration of a person’s state of health, the software is Class III. This is a decision-impact criterion and should not be inferred merely from the device with which software is used.
c. Software intended to monitor physiological processes is generally Class IIa, or Class IIb where it monitors vital physiological parameters whose variations could result in immediate danger. All other software falling under Rule 11 is Class I. Imaging software, for example, cannot automatically be assumed to be Class I without assessing its intended purpose.
2. Annex I of the EU MDR sets out General Safety and Performance Requirements. Section 15 addresses devices with a diagnostic or measuring function and requires sufficient accuracy, precision, and stability for their intended purpose, based on appropriate scientific and technical methods. Relevant testing activities include:
a. Verification testing is crucial to ensure that the software algorithm conducts proper measurements.
b. Validation testing is needed to support what the users see and how they may interpret results.
c. Performance testing supports analytical accuracy and resolution of measurement (e.g., SpO2 specification +/- 2% within range).
3. Annex I, Section 17 addresses electronic programmable systems, including software, and software that is a device in itself. Such systems must be designed for repeatability, reliability, and performance in line with their intended use, with software developed according to the state of the art and with consideration of risk management, information security, verification, and validation. Relevant activities include:
a. Software verification testing needs to link to hazards identified for the software and/or hardware interface.
b. Software life-cycle development is key for managing hazards, verification, validation, and cybersecurity issues.
c. Interoperability with other software-controlled devices and their connectivity via Wi-Fi, Bluetooth, and networks must be addressed.
Involvement of Notified Body in EU MDR
Notified Bodies are organizations designated by national authorities of EU Member States to assess the conformity of devices where notified-body involvement is required before they are placed on the EU market or put into service. They conduct applicable conformity assessments and QMS audits and review relevant technical documentation. The scope of assessment and any testing depend on the device, its classification, and the applicable conformity assessment procedure; not all technical documentation requires laboratory verification.
The European database on medical devices (EUDAMED) includes a Notified Bodies and Certificates module for relevant certificate information. From 28 May 2026, the first four EUDAMED modules—Actor registration, UDI/Devices, Notified Bodies and Certificates, and Market Surveillance—became mandatory to use under the applicable transition rules. EUDAMED supports transparency and information exchange among stakeholders under the MDR and IVDR frameworks.
Application process requirements
For the Application process of EU MDR, manufacturers should review and consider the following requirements:
1. Quality Management System (QMS) and Regulatory Requirements: Medical device software manufacturers must demonstrate that their products consistently meet applicable customer and regulatory requirements. An appropriate QMS aligned with ISO 13485:2016 can support compliance with the EU MDR, alongside the regulation’s specific obligations.
Manufacturers should apply the relevant edition of EN IEC 62304, including the applicable amendments, for medical device software lifecycle processes. IEC 62304:2006 and Amendment 1:2015 remain important references; the applicable harmonized standards and their status should be checked for the specific conformity assessment.
The 2015 amendment introduced important updates to software lifecycle requirements, including clarifications affecting software safety classes. Manufacturers should determine the applicable requirements for Classes A, B, and C based on the amended standard rather than assuming all activities apply identically to every class.
This would include:
a. Use of the software resolution process
b. Retesting after changes
c. Documenting known residual anomalies
d. Archiving software
e. Ensuring reliable delivery of released software
f. Applying the requirements early in development
Manufacturers must determine the appropriate software safety class and document how the applicable IEC 62304 requirements are met. This documentation can be maintained within the quality management system and software lifecycle records.
2. Premarket Requirement: This includes the following considerations:
a. Classification requirements, including applicable rules for software, nanomaterials, absorbable devices, and active devices, based on the intended purpose and device characteristics
b. The applicable conformity assessment procedure, including Notified Body involvement where required
c. Compliance with the general safety and performance requirements
3. Technical Documentation Requirements: It covers all aspects of product realization and the entire life cycle. We are supporting the following technical documentation:
a. User Requirements
b. Product Requirements
c. Gap Analysis
d. Regulatory compliance
e. Traceability Matrix
4. Post-Market Surveillance Requirements: Depending on the device class and applicable provisions, these may include a Post-Market Surveillance Report (PMSR), Periodic Safety Update Report (PSUR), Summary of Safety and Clinical Performance (SSCP), and Post-Market Clinical Follow-up (PMCF) evaluation reports. These documents do not apply in the same way to every device classification.
5. Risk Management Requirements: The manufacturer shall apply a risk management process complying with ISO 14971. Risk Assessment and Clinical Evaluation should be updated using data and information gathered through post-market surveillance and lessons learned from any implemented preventive and/or corrective actions.
Medical device manufacturers need to be aware of the above requirements and obligations with regards to SaMD and we are happy to provide the assistance to our clients for all these processes with the expertise in EU MDR standards.
This blog is written by Sonali Hinge at Decos.
Decos is a cutting-edge technology services partner ready to meet your software needs in the medical domain. If you have a question on one of our projects or would like advice on your project or a POC, just contact Devesh Agarwal. We’d love to get in touch with you!