Software CE Marking for Medical Devices and SaMD Under EU MDR

MedDeviceCorp helps software developers and medical device manufacturers get CE marking for medical device software under the EU Medical Device Regulation (MDR) 2017/745. We handle software qualification, Rule 11 classification, IEC 62304 lifecycle documentation, cybersecurity, usability, clinical evaluation and notified body review, for standalone software as a medical device (SaMD), mobile health apps, AI-based software and software embedded in hardware devices.

Whether you are a start-up launching your first app or an established manufacturer moving legacy software from the MDD to the MDR, our team gives you a clear route to software CE marking and the documents to support it.

Get a Software CE Marking QuoteSee the Process

Our Software CE Marking Services

Qualification and classification

We confirm whether your software is a medical device and assign its class under MDR Annex VIII Rule 11, with a written rationale for the notified body.

IEC 62304 documentation

Software development plan, requirements, architecture, SOUP list, verification, release and maintenance records.

MDR technical file

Annex II and III technical documentation, GSPR checklist, labelling, IFU and declaration of conformity.

Risk and usability

ISO 14971 risk management and IEC 62366-1 usability engineering, linked to software hazards.

Cybersecurity

Security risk assessment and documentation aligned with MDCG 2019-16 and IEC 81001-5-1.

Clinical evaluation

Clinical evaluation report for software following MDCG 2020-1, plus PMCF planning.

ISO 13485 QMS

A quality management system sized for software companies, integrated with your development tools.

Notified body support

Application, technical file submission and responses to reviewer questions until certification.

What Is Medical Device Software?

Under the MDR, software is a medical device when the manufacturer intends it to be used, alone or in combination, for a medical purpose listed in Article 2(1). These purposes include diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease, and diagnosis, monitoring, treatment or compensation of an injury or disability.

MDCG 2019-11 uses the term medical device software (MDSW) and describes two main types:

  • Software as a medical device (SaMD): standalone software that has a medical purpose on its own, such as an app that analyses images to detect skin cancer or calculates an insulin dose.
  • Software in a medical device (SiMD): software that drives or influences a hardware device, such as the firmware in an infusion pump or the control software of an imaging system.

The intended purpose is what decides. Software that only stores, archives, transfers or performs simple searches on data is usually not a medical device. Software that creates new medical information or supports clinical decisions for individual patients usually is.

Examples of Software That Needs CE Marking

  • Software that calculates a drug dose from individual patient data.
  • Image analysis software that helps detect stroke, fractures or tumours on CT or MRI scans.
  • Apps that track a mole over time and estimate melanoma risk.
  • Software that uses wearable data to predict epileptic seizures or detect atrial fibrillation.
  • Insulin dose calculators that use glucose readings.
  • Smartphone apps that measure breathing rate or detect sleep apnoea.
  • Clinical decision support software that suggests a diagnosis or treatment.
  • Digital therapeutics that deliver a treatment, such as cognitive behavioural therapy for a diagnosed condition.
  • Remote patient monitoring platforms that raise alarms on vital signs.

General wellness and fitness apps without a medical purpose, hospital administration systems and electronic health records used only for storage are normally outside the MDR. If you are not sure where your product falls, we provide a written qualification assessment.

Software Classification Under MDR Rule 11

Annex VIII Rule 11 is the main classification rule for medical device software. It moved most software that was Class I under the old Directive into Class IIa or higher, which means a notified body must now review it.

Software functionClass
Provides information used to take decisions for diagnosis or treatmentIIa
Those decisions may cause serious deterioration of health or a surgical interventionIIb
Those decisions may cause death or an irreversible deterioration of healthIII
Monitors physiological processesIIa
Monitors vital physiological parameters where variations could result in immediate danger to the patientIIb
All other medical device softwareI

Software that drives or influences a hardware device takes the same class as that device (Annex VIII, Section 3.3). MDCG 2019-11 gives a decision method and examples for applying Rule 11. Other rules, such as Rule 22 for active therapeutic devices with an integrated diagnostic function, can also apply. We document the classification in a rationale that cites the relevant rules and guidance, because classification is one of the first points a notified body checks.

MDR Requirements for Software: Annex I Section 17

The general safety and performance requirements in Annex I apply to all devices. Section 17 adds specific requirements for electronic programmable systems and software:

  • 17.1 Software must be designed for repeatability, reliability and performance in line with its intended use, with measures to reduce risks from single fault conditions.
  • 17.2 Software must be developed and manufactured according to the state of the art, taking into account the development lifecycle, risk management including information security, verification and validation.
  • 17.3 Software intended for mobile computing platforms must account for the platform features, such as screen size and contrast, and the external environment of use.
  • 17.4 Manufacturers must set out minimum requirements for hardware, IT networks and IT security measures, including protection against unauthorised access.

Section 14.2(d) and Section 18.8 also address interaction with IT environments and protection against unauthorised access. In practice, notified bodies expect IEC 62304, IEC 82304-1, IEC 62366-1, ISO 14971 and IEC 81001-5-1 to be used to show conformity with these requirements.

IEC 62304 Software Lifecycle and Safety Classes

IEC 62304 defines the lifecycle processes for medical device software. It is the standard notified bodies use to judge whether your software was developed according to the state of the art. The amount of documentation depends on the software safety class:

Class A

No injury or damage to health is possible.

Class B

Non-serious injury is possible.

Class C

Death or serious injury is possible.

IEC 62304 covers the following processes:

  1. Software development planning
  2. Software requirements analysis
  3. Software architectural design, including SOUP (software of unknown provenance) identification
  4. Software detailed design (Class B and C as required)
  5. Software unit implementation and verification
  6. Software integration and integration testing
  7. Software system testing
  8. Software release
  9. Software maintenance
  10. Software risk management, linked to ISO 14971
  11. Software configuration management
  12. Software problem resolution

Note that the IEC 62304 safety class (A, B, C) is different from the MDR device class (I, IIa, IIb, III). A Class IIa device can contain Class C software items. We help you set both correctly and keep them consistent across the file. We also provide a full set of IEC 62304 SOPs and templates that fit into your ISO 13485 system.

Integrating ISO 13485 With IEC 62304

MDR Article 10(9) requires every manufacturer to have a quality management system, and for Class IIa and above the notified body audits it, usually against ISO 13485. Software companies often find this hard, because ISO 13485 was written with physical products in mind and their teams already work in agile development tools.

The answer is to build one integrated system. ISO 13485 provides the overall QMS: management responsibility, document control, CAPA, supplier control, complaint handling and post-market surveillance. IEC 62304 sits inside the design and development process (ISO 13485 clause 7.3) and defines how software is planned, built, tested and released. ISO 13485 clause 4.1.6 also requires validation of software used in the QMS itself, such as your issue tracker or test tools.

We map IEC 62304 activities to your existing tools, such as Jira, Git and CI pipelines, so records are created as part of normal development rather than written afterwards. Agile methods are acceptable when the outputs required by IEC 62304 are produced and controlled. AAMI TIR45 is a useful reference for agile practice in regulated software.

Technical Documentation for Software CE Marking

The technical file for software follows MDR Annexes II and III, with software-specific content added. A typical file includes:

  • Device description, intended purpose, intended users, and qualification and classification rationale
  • Software version history and UDI assignment, including the software version in the UDI-PI
  • GSPR checklist with the standards and evidence used for each requirement
  • Software development plan, requirements specification and architecture
  • SOUP and third-party library list with risk assessment
  • Verification and validation reports, with traceability from requirements to tests
  • Known anomalies list and release notes
  • Risk management file to ISO 14971
  • Usability engineering file to IEC 62366-1
  • Cybersecurity file: threat model, security risk assessment, security testing and SBOM
  • Clinical evaluation report and PMCF plan
  • Labelling, instructions for use (electronic IFU where allowed) and minimum IT requirements
  • Post-market surveillance plan and, for Class IIa and above, PSUR
  • EU declaration of conformity

Cybersecurity for Medical Device Software

Cybersecurity is now one of the most reviewed areas in a software CE marking file. The MDR requires protection against unauthorised access, and MDCG 2019-16 explains how notified bodies expect manufacturers to meet this across the product lifecycle.

Our cybersecurity support includes threat modelling, a security risk assessment linked to safety risk management, secure design requirements, a software bill of materials (SBOM), penetration and vulnerability testing plans, and a post-market process for monitoring and patching vulnerabilities. We align the documentation with IEC 81001-5-1, so the same file can also support FDA premarket cybersecurity expectations if you plan to sell in the USA.

Clinical Evaluation of Medical Device Software

Every medical device needs a clinical evaluation, including software. MDCG 2020-1 explains how to build clinical evidence for MDSW on three pillars:

Valid clinical association

Evidence that the software output is linked to the targeted clinical condition, based on literature, guidelines or your own studies.

Technical performance

Evidence that the software reliably and accurately produces the intended output from the input data.

Clinical performance

Evidence that the output gives a clinically relevant result in the target population and use environment.

For diagnostic and AI software, clinical performance is usually shown with sensitivity, specificity and predictive values on representative, independent data sets. We write the clinical evaluation plan and report for your software and set up PMCF to collect real-world performance data. Read more about our clinical evaluation report services.

AI and Machine Learning Software CE Marking

AI-based medical software goes through the same MDR process as other software, but notified bodies look closely at data management, model training and validation, and how the model behaves after release. Key topics include data sources and bias, separation of training and test data, performance across patient sub-groups, explainability for users, and change control for model updates.

The EU Artificial Intelligence Act (Regulation (EU) 2024/1689) adds further requirements. AI systems that are medical devices needing notified body assessment are classed as high-risk AI systems, and their AI Act obligations apply from 2 August 2027. The aim is a single conformity assessment covering both the MDR and the AI Act. We help you plan your technical documentation now so it can be extended for AI Act requirements such as data governance, logging, transparency and human oversight.

Software CE Marking Process: Step by Step

  1. Qualification: confirm the software is a medical device and define the intended purpose.
  2. Classification: apply Rule 11 and other relevant rules, and write the classification rationale.
  3. Gap analysis: review your existing development records, QMS and documents against MDR and IEC 62304.
  4. QMS: implement or adapt ISO 13485 with integrated IEC 62304 procedures.
  5. Development documentation: complete plans, requirements, architecture, SOUP, verification and validation.
  6. Risk, usability and cybersecurity: complete the ISO 14971, IEC 62366-1 and security files.
  7. Clinical evaluation: prepare the clinical evaluation plan and report following MDCG 2020-1.
  8. Technical file: compile Annex II and III documentation, labelling and IFU.
  9. Notified body: select a notified body, submit the application and support the QMS audit and technical file review.
  10. CE marking and registration: sign the declaration of conformity, affix the CE mark and register in EUDAMED.
  11. Post-market: run PMS, PMCF, vigilance and change control for every new software release.

Class I software that does not need a notified body follows the same steps except the notified body review. The manufacturer self-declares conformity.

How Long Does Software CE Marking Take?

Software classNotified body needed?Typical time to CE mark
Class INo (self-declaration)3 to 6 months
Class IIaYes9 to 15 months
Class IIbYes12 to 18 months
Class IIIYes, with stricter review18 months or more

These are typical ranges. The actual time depends on how complete your development records are, the clinical evidence available and notified body availability. Starting with a gap analysis and a good-quality technical file is the most reliable way to shorten the review.

Software Updates After CE Marking

Software changes often. Under the MDR, each change must be assessed to decide whether it is significant. Changes that affect the intended purpose, the classification, the clinical performance, the algorithm or the safety of the device may need notified body approval before release, and may need a new UDI-DI. Minor bug fixes and security patches that do not change performance usually follow your internal change control.

We set up a change assessment procedure, linked to your release process, so each version is documented, risk-assessed and correctly reported. This keeps your CE certificate valid while you continue to improve the product.

Moving Legacy Software From MDD to MDR

Many software products were self-certified as Class I under the old Medical Device Directive. Under MDR Rule 11 most of them are now Class IIa or higher and need a notified body. Regulation (EU) 2023/607 extended the transition period for legacy devices to 2027 or 2028, depending on class, but only for manufacturers that met the conditions, including applying to a notified body and signing a written agreement by the 2024 deadlines.

During the transition, no significant changes may be made to the design or intended purpose of the legacy device. For software that is updated often, this is a major limitation. We help you plan the move to MDR certification so product development is not blocked.

Common Notified Body Findings on Software Files

  • Classification rationale does not address all Rule 11 criteria or the severity of decisions informed by the software.
  • Software requirements not traceable to tests, or tests not traceable to risks.
  • SOUP and open-source libraries not listed or not risk-assessed.
  • IEC 62304 safety class not justified, or inconsistent with the risk file.
  • Cybersecurity limited to a statement, with no threat model or security testing.
  • Clinical evaluation missing technical or clinical performance data for the software output.
  • Minimum IT requirements for hardware, operating systems and networks not defined in the IFU.
  • No procedure to decide whether a software change is significant.

We check for each of these before submission and, if you already have findings, write the responses and update your file.

Why Choose MedDeviceCorp for Software CE Marking

Software-focused team

Regulatory specialists who understand development, testing and release cycles, not only documents.

Full CE marking support

From qualification to certificate, including QMS, technical file, clinical evaluation and notified body response.

EU and US ready

Documentation built so it can also support FDA submissions for software as a medical device.

Local offices

Support from our offices in India, the USA and the UK, for software companies worldwide.

Non-EU manufacturers also need an EU Representative before placing software on the EU market. We provide this service alongside CE marking.

Software CE Marking FAQs

Does my software need CE marking?

Your software needs CE marking if it has a medical purpose as defined in MDR Article 2(1), such as diagnosis, monitoring, prediction or treatment of disease for individual patients. Software used only for administration, storage or general wellness usually does not.

What is the difference between SaMD and SiMD?

SaMD (software as a medical device) is standalone software with its own medical purpose. SiMD (software in a medical device) drives or influences a hardware device and is assessed as part of that device.

What class is my medical device software?

Most medical software is classified under MDR Annex VIII Rule 11. Software that informs diagnostic or treatment decisions is at least Class IIa, and can be IIb or III depending on the possible impact of those decisions.

Can medical software be Class I under MDR?

Yes, but only when it does not provide information for diagnostic or therapeutic decisions and does not monitor physiological processes. Since Rule 11, relatively few medical software products remain Class I.

Is IEC 62304 mandatory for CE marking?

IEC 62304 is a standard, so it is not legally mandatory. However, MDR Annex I Section 17.2 requires software to be developed according to the state of the art, and notified bodies expect IEC 62304 to be followed in practice.

What are the IEC 62304 software safety classes?

Class A means no injury is possible, Class B means non-serious injury is possible, and Class C means death or serious injury is possible. The class decides how much documentation is required.

Do I need ISO 13485 for software CE marking?

You need a quality management system under MDR Article 10. For Class IIa and above, the notified body audits it, and ISO 13485 is the standard used to show conformity.

Does medical software need a clinical evaluation?

Yes. All medical devices, including software, need a clinical evaluation. MDCG 2020-1 explains how to show valid clinical association, technical performance and clinical performance for software.

How much does software CE marking cost?

The cost depends on the software class, the state of your development records, clinical evidence needs and notified body fees. Contact us with your product details for a fixed-price proposal.

How long does software CE marking take?

Class I software can be ready in 3 to 6 months. Class IIa and IIb software usually takes 9 to 18 months, including notified body review. Class III software takes longer.

How are software updates handled after CE marking?

Each change must be assessed for significance. Significant changes to intended purpose, performance, algorithm or safety may need notified body approval and a new UDI-DI before release.

What cybersecurity documents does a notified body expect?

Typically a threat model, security risk assessment, security requirements, test evidence, an SBOM and a post-market vulnerability management process, following MDCG 2019-16 and IEC 81001-5-1.

Can a mobile health app be a medical device?

Yes. A mobile app with a medical purpose, such as calculating doses or detecting a condition, is medical device software and needs CE marking. Annex I Section 17.3 adds requirements for mobile platforms.

How does the EU AI Act affect medical software?

AI-based medical software that needs notified body assessment is a high-risk AI system under Regulation (EU) 2024/1689. Its AI Act obligations apply from 2 August 2027, alongside MDR requirements.

Does software need a UDI?

Yes. Medical device software needs a UDI. The software version is part of the UDI-PI, and changes affecting performance, safety or data interpretation require a new UDI-DI.

Do non-EU software companies need an EU Representative?

Yes. Manufacturers located outside the EU must appoint an EU Representative before placing their software on the EU market, as required by MDR Article 11.

Can the same documentation be used for the FDA?

Much of it can. IEC 62304, ISO 14971, IEC 62366-1 and cybersecurity documentation are recognised by both the EU and the FDA, although the submission format and clinical evidence expectations differ.

What do you need from us to start?

A description of the software, its intended purpose and users, your current development and test records, and any existing QMS documents. We start with a qualification, classification and gap analysis.

Start Your Software CE Marking Project

Talk to our software CE marking consultants in India, the USA or the UK and get a fixed-price proposal for qualification, classification, IEC 62304 documentation and notified body support.

Get a Software CE Marking Quote