The EU MDR medical device regulations are a set of regulations that govern the production and distribution of medical devices in the European Union. These regulations aim to ensure that medical devices have no negative impact on human health. The EU MDR is the successor of the previous Medical Device Directive (MDD).
The MDR has been in force since May 2021. By 2024, any existing medical device products certified under the MDD will need to be recertified under the MDR, if they wish to continue to be sold within the European Economic Area (EEA).
Under the MDR, in order for a medical device to be legally sold in the EU market, it must have a CE marking. In order to receive a CE marking, the medical device is subjected to a conformity assessment, which determines whether the device complies to the necessary requirements under the MDR.
The long road to the CE marking starts with classifying your software according to the MDR. We have a
handy 1-page roadmap pdf at your disposal if you are in need of some extra information.
The MDD is a much older regulation than the MDR. Back when the MDD was created in 1994, the concept of
Software as a Medical Device (SaMD) did not exist. The medical monitoring apps that are so widely used today had yet to be invented, so the MDD was not created with these solutions in mind. Thus, the MDD is now largely considered to be outdated.
Since 1994, there have been significant advancements in the use of medical devices and
SaMD.
Thus, there was a need for updated regulations that better meet the needs of this ever-evolving market.
Both the MDR and the MDD establish a regulatory framework for medical devices, but the MDR builds on certain aspects of the MDD, and goes into much greater detail. In fact, the MDR is four times longer than the MDD!
It’s important to note: nothing from the MDD has been removed from the MDR!
Notable updates included in the MDR include:
The MDR also introduces changes to how medical software products are classified, including the introduction of a new high risk software class, which covers software that can cause death or irreversible damage to a patient.
You can read more about the MDR’s impact on your choice of cloud software at
our blog post here.
The risk class of a medical device product is based on the perceived risk. The perceived risk refers to the potential impact the device can have on the human body. Here is a summary of the new software safety classes under the MDR:
Class I devices have the lowest perceived risk. In a lot of cases, it is possible for manufacturers to self-certify as a Class I device without the involvement of a notified body.
However, there are three Class I subcategories that have a higher perceived risk, and therefore require involvement of a notified body. These three subcategories are:
Class Is medical devices are products that must be presented as sterile. Examples include things like syringes, gloves used for medical examinations, colostomy bags, and stethoscopes.
Class Im medical devices are those that have a measuring feature. Examples include thermometers, measuring syringes, and blood pressure measuring devices.
Class Ir devices are those that are reprocessed or reusable. This includes things such as surgical instruments, which are cleaned and sterilised before being used again.
Class IIa devices have a medium perceived risk. For these devices, it is essential for manufacturers to receive a declaration of conformity from a notified body in order to receive a CE marking. Examples of Class IIa devices include hearing aids, catheters, dental crowns, and ultrasound equipment.
Class IIb devices have a medium to high perceived risk. For a Class IIb product to receive a CE marking, a notified body must be involved. Examples of IIb medical devices include ventilators, insulin pens, and intensive care monitoring equipment.
Class III devices have a high perceived risk, and are subjected to the most stringent requirements out of all of the MDR safety classes. This includes the
clinical evaluation stage. Class III devices tend to require permanent monitoring throughout the lifetime of the patient. Examples of these devices include pacemakers, breast implants, and prosthetic heart valves.
Under the EU MDR, a rules-based system is used to determine the risk class of a medical device. These rules can be found in Annex VIII of the MDR.
There are 22 rules in total, which are divided into four sections, each section covering a different category of devices. The sections are as follows:
Rules 1-4: non-invasive devices
These devices do not penetrate the body through any surface or orifice.
These devices penetrate the body completely or partially, through any surface or orifice.
These devices rely on a source of energy that cannot be generated by the human body in order to work.
These rules cover any devices that do not fit into the first three categories
In each category, the duration of the device’s intended use is also used to determine which rules apply. There are three duration types specified in the MDR:
Transient
Intended for continuous use for less than 60 minutes.
Intended for continuous use for between 60 minutes and 30 days.
Intended for continuous use for more than 30 days
If you are:
or
You need to know how to comply with the MDR.
When it comes to applications, it is important to remember that only medical apps fall under MDR legislation. Wellness or wellbeing apps are not covered by the MDR. If you’re interested in learning about the differences between wellness and health apps, be sure to read our
Coffee Corner blog about the blurring line between wellness and health.
If your product was certified under the MDD, and you still wish for your product to be sold within the European Economic Area (EEA), you will need to have your product recertified under the MDR by 2024.
Read more about what the MDR means for your medical device solution
here.
The process of making sure your product is compliant to the MDR can be a long and tedious, and can significantly increase the time it takes to make your medical device market-ready.
Before embarking on your MDR certification journey, you can use our
CMI tool to check how compliant your company already is.
Being compliant with the MDR places significant requirements on your cloud infrastructure. For instance, you need to ensure that you have a suitable quality management system (QMS) in place throughout the entire product lifecycle. This can be demonstrated by following the guidelines for ISO 13485:2016 and IEC 62304:2006.
It is also essential for your cloud infrastructure to be GDPR-compliant.
We know that adhering to all of these different rules and regulations involves a lot of time and effort; effort that could be used in other important areas, such as defining your business logic. It is for this reason that regulatory compliance, particularly concerning the MDR, is one of the biggest hurdles to overcome before going to market. When developing Software as a Medical Device, MDR compliance is vital, and should never be overlooked.
We are well-aware of the importance of regulatory compliance, which is why we undergo independent verification of security, privacy, and compliance controls. Our
medical Backend-as-a-Service (mBaaS) is compliant and certified to a number of global standards, including the MDR and its related requirements. Using a
certified medical BaaS does not mean your solution becomes automatically certified, but it does make the path to compliance a lot smoother.
RECENT POSTS
FREE EBOOKS
GOT QUESTIONS?
Solutions
BY USE CASE
BY CAPABILITY
BY STAGE
Getting Started
AS A DEVELOPER
AS A PARTNER
© 2023 Extra Horizon, All rights reserved
Kempische Steenweg 303, 3500, Hasselt, BE
— Hasselt, Belgium