Author: Dr. Suzanne Broussard
Software is now considered a medical device if that is its intended purpose according to the European Union’s definition of in vitro diagnostic (IVD) devices in the new In Vitro Diagnostic Regulation (IVDR) 2017/746.
Here we look at the scope of how this change in definition impacts software developers within the IVD space, and we use this as an example of the magnitude of the new IVDR regulation for all IVDs.
Software
Software is a medical device according to the definition of IVD if that is its intended purpose; thus, software as part of an instrument, software as a medical device, and apps are included in the definition of IVDs and fall under IVDR regulation. This included genetic testing, companion diagnostics, as well as stand-alone software.
At the Top of IVDR 2017/746, number 17 introduces software that falls under this regulation:
(17) It is necessary to clarify that software in its own right, when specifically intended by the manufacturer to be used for one or more of the medical purposes set out in the definition of an in vitro diagnostic medical device, qualifies as an in vitro diagnostic medical device, while software for general purposes, even when used in a healthcare setting, or software intended for well-being purposes is not an in vitro diagnostic medical device. The qualification of software, either as a device or an accessory, is independent of the software’s location or the type of interconnection between the software and a device.
To help medical software developers better understand the criteria “for the qualification of software falling within the scope of the new medical devices regulations,” the EU provided a guidance document on the application of the classification criteria for software. Follow the link below for The European Commission’s Medical Device Coordination Group (MDCG) 28-page guidance document released on October 11, 2019.
This guidance document clearly states in section 5.2 Classification Rules that the proper classification of medical device software requires the manufacturer to consider all classifications and implement the rules of Annex VIII of the IVDR.
Here are the examples provided for the classification of medical device software:
To fully see the magnitude of the inclusion of software as an IVD from a regulatory perspective we have created a table to highlights the regulations for software and provides a reference to the IVDR 2017/746 document. The list of requirements is extensive and includes general safety and performance requirements, technical documentation, registration of devices and economic operation, classification rules, and performance evaluation, performance studies and post-market performance follow-up.
| Title | IVDR Reference | Subject |
| General Safety and Performance Requirements | Annex I | |
| Chapter 2 13.2 (d) | Construction of devices and interaction with their environment | |
| 16 (16.116.4) | Electronic programmable systems — devices that incorporate electronic programmable systems and software that are devices in themselves | |
| 20.4 (ah) | Information in the instructions for use | |
| Technical Documentation | Annex II | |
| 1.1 (k) | Device description and specification | |
| 6.4 | Software verification and validation | |
| Registration of Devices and Economic Operations | Annex VI | |
| PART C, 3.5 | The UDI | |
| 6.2.1 | UDI assignment criteria | |
| 6.2.3 | Minor software revisions | |
| 6.2.4 (a-e) | UDI placement criteria for software | |
| Classification Rules | Annex VIII | |
| 1.4 | Implementing rules | |
| Performance Evaluation Performance Studies and Post-Market Performance Follow-Up | Annex XIII | |
| Part A, 1.1 | Performance evaluation plan | |
In summary, the regulation for all IVD devices changes with IVDR. The example above for software is just the tip of the iceberg. And, compliance with the new IVDR starts May 26, 2022. For more specific information on the time-line to transition to IVDR, classification of IVDs under IVDR, or analytical and clinical technical documentation aspects of IVDR conformity, check out our previous blog post.
Feel free to contact Criterion Edge for more details on how we can help you successfully transition your in vitro device to the IVDR.
Tags: MDR, MDR Extension
In this practical presentation, Criterion Edge uncovers what we have learned from our experience in writing MDR-compliant CERs, and how urgently applicable some of these key learnings are in preparing a robust Performance Evaluation Report (PER).
As we all know, the MDR has significantly increased both the quality and quantity of inputs needed to complete a CER, needing more up-front planning than the reports have in the past. Based on our experiences with clients both large and small, our President, Laurie Mitchell, shares some of the biggest issues we have discovered when starting an MDR CER project. Laurie also reveals some of the most successful strategies in addressing these issues, up-front and early.
In this practical presentation, Criterion Edge breaks down the steps of the SLR process and takes a wholistic approach to conducting an IVDR-compliant SLR. Using case studies, the presentation illustrates the effective use of SLR-derived data to develop the Scientific Validity Report (SVR) and the Clinical Performance Report (CPR).
In this second installment of our 2-part webinar series, Criterion Edge shares practical presentation to help you assess your CER through the critical lens of a writer and identify possible gaps for mitigation before prior to submission to regulatory authorities.
In this webinar, we share the process of systematic literature review, and discuss the tools and best practices for creating a methodologically-sound systematic literature review.
Watch this video to learn how Criterion Edge is different from the rest.
This infographic goes through 5 key questions to go through in order to control your budget.
Leading industry experts come together to discuss how the MDR affects data management within their respective units.
This report clarifies the modifications to the equivalence guidelines in MEDDEV 2.7/1 and Quality Management Systems (QMS) ISO 13485 standard to help develop strategies.
This gap analysis addresses key revisions to evaluator qualifications and scientific validity in the Clinical Evaluation (CE) MEDDEV guideline rev.4.
The changes to 2.7/1 rev. 4 suggest the need to submit more frequent CERs to regulatory authorities, however, strategies will be discussed for managing the increased requirements.
Every time a healthcare provider makes a notation in the medical chart, a significant and valuable piece of data has been created. This paper discusses the implications of this.
This piece discusses 10 key strategies to building an efficient regulatory writing process.
In this paper, we discuss a prominent clarification on the MEDDEV 2.7.1 rev 4, establishing the “state of the art” section.
The overwhelming turnout at the ‘How to Assess Your CER for MDR Readiness, Part 1’ prompted us to host a live Q+A session where President Laurie Mitchell exclusively answers all your questions.
President Laurie Mitchell returns to continue sharing more about the importance of the systematic literature review.
In this webinar, we share the process of systematic literature review, and discuss the tools and best practices for creating a methodologically-sound systematic literature review.
Establishing and defining state of the art for a medical device is no longer an isolated task – it supports the entire Clinical Evaluation Report (CER). Multiple sections of the MEDDEV 2.7/1 rev 4 compliant CER need to be supported by state of the art data, including safety and performance, risk management, and equivalence.
In this first installment of a 2-part webinar series, Criterion Edge will present strategies for assessing key components of your CER (or CER template) for possible misalignment with significant and applicable MDR requirements.
In this webinar, President Laurie Mitchell discusses why safety reviews are essential in the entire life cycle of product development.
Kyoko Hattori from Criterion Edge returns to discuss best practices for managing the adjudication process in-house, and Brian Kelly from AG Mednet will share how the “JUDI” platform can simplify the management of adjudication.
In this webinar, learn about CECs, familiarization with regulatory guidance, decision factors leading to use of a CEC, and much more.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Read more about our privacy policy here.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.
This website uses Google Tag Manager and Pardot's tracking features to collect information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!
