The buzz surrounding the development and use of smartphone apps and other software to “manage healthcare” and “wellness” isn’t going away any time soon.
It is a situation that creates significant headaches for people developing software that may, or may not, be viewed as (part of) a medical device. Uncertainty that presents significant risk to their development plans, activities and investment, especially when the software part of the product sits on the cusp of the medical device space.
Earlier this year, we discussed how the FDA’s approach to this rapidly evolving market segment was bringing clarity (if you’d like a refresher, you can read the article here). Let’s turn now to the approach taken in the EU.
EU treatment of software as a medical device
Developers have often referred to the MEDDEV Guidelines, as tools to help interpret the requirements of directives/regulations for medical devices. The guidelines have been regarded as just that, and not legally binding – so there hasn’t been certainty over how well they interpret EU law. But, now there is a legal ruling from the EU Court of Justice (CJEU) on the grounds for classifying software as a medical device.
Essentially the CJEU ruled that software is a medical device if it has at least one functionality that allows its use for a medical purpose set out in the definition of a medical device in the MDD (as amended):
- Diagnosis, prevention, monitoring, treatment or alleviation of disease,
- Diagnosis, monitoring, treatment, alleviation of or compensation for an injury or handicap,
- Investigation, replacement or modification of the anatomy or of a physiological process,
- Control of conception
The software does not have to work directly in or on the human body to be classed as a medical device. The purpose of using the software is important, rather than the manner in which an effect is produced to the human body.
Why this should matter to you
The CJEU decision validates the criteria in MEDDEV guidance for classification of software medical devices, so they can be relied on with greater confidence both by the industry and regulatory authorities. Developers of medical devices that are entirely or partly software can use the MEDDEV decision tree with confidence.
Determining if Software is a Medical Device or IVD
MEDDEV 2.1/6 includes a handy decision tree to help you determine if your software is a medical device:
There’s a similar decision tree to help you determine if your software is an in-vitro diagnostic device:
As you might expect, the devil is in the detail, for both of these classification routes.
Reducing and Managing Risk
The CJEU ruling means that development projects can have a greater degree of confidence that they’re applying the correct classification to their products, and hence massively reduce the risk that their activities are inadequate to satisfy regulatory authorities. The ultimate benefit is in avoiding unnecessary costs, unwarranted testing and use of resources, whilst ensuring that, for those software that are truly medical devices, sufficient testing and documentation are provided to demonstrate regulatory compliance.
You may find it useful to seek an independent, expert opinion on the outcome of using the decision trees for classifying your software development, before embarking on an expensive and lengthy programme.
If you would value a conversation to get the ball rolling, get in touch with us today.