Since our original post (below) we have made 3 additional updates to provide you with a lot more info and resources.  Check out our updates in this LinkedIn Article.

Updates are all underlined:

Mar 7, ’17 updates:

* addition of the EU Council vote & date of release of final text

* an important change that manufacturers will need to deal with, and

* addition of 4 resources to list of helpful resources

Mar 12, ’17 update: add in Table of Contents LinkedIn Article

Mar 17, ’17 update: RAPS Article by Rod Ruston

Our original post was on March 1, 2017 is titled EU MDR & IVDR – Final Versions – Are You Ready, Transition Period Starts Soon.

If you need help with your EU MDR or IVDR transition planning please email Leo Eisner at Leo at EisnerSafety dot com, or call Leo at +1 (503)-244-6151. He is the Principal Consultant of Eisner Safety Consultants.

Some of the changes manufacturers will have to deal with include:

*Quality Management Systems
*Clinical Evidence Requirements
*Authorized Representatives Requirements and Liability
*You may need to change Notified Bodies if their scope changes during the designation process
*Need to prepare and implement for Unique Device Identifiers (UDI), starting with the highest risk class
*Person responsible for regulatory compliance in your company – minimum requirements
*Classification rules will change & some devices that are not considered medical device currently will fall under the MDR
*Classification rules will impact IVDs significantly under the IVDR
*Updates to post market surveillance & vigilance requirements
*Economic operators in the supply chain will have some changes to the obligations per the MDR or IVDR

Here are some resources to share with you:

greenlight.guru Webinars on How to Prepare for the New EU Medical Device Regulations (MDR) and How to Prepare for the New EU In Vitro Diagnostics Regulations (IVDR)

For the following 3 BSI White Papers* please select the title from the BSI White Paper webpage.

BSI’s white paper* on the MDR “Planning for implementation of the European Union Medical Devices Regulations – Are you prepared?”

BSI’s white paper* on the IVDR titled “How to prepare for and implement the upcoming IVDR – Dos and don’ts”

BSI’s white paper* on the MDR & IVDR draft text (article updated Oct 2015) titled “UPDATED: The proposed EU regulations for medical and in vitro diagnostic devices”

BSI webpage for white papers* has additional white papers on medical devices / IVDs and quality system requirements.

One of my favorite blogs to follow on the MDR changes is Erik Vollebregt’s Medicaldeviceslegal.com blog.  Erik does an excellent job providing really great information on the subject and keeping his finger on the pulse of the issue at hand.

* Note, through out the BSI White paper series I have had the honor of being on the Advisory Panel to help shape the series and review each of the white papers to provide my years of experience in the medical device industry and the regulatory world.

De-notification of EU Notified Bodies under MDD

The number of EU Notified Bodies (NBs) under the MDD has dropped from about 80 to less than 60 because of the increasingly more stringent NB requirements.  Are you sure your Notified Body scope still covers your products or are they de-notified?  The French Competent Authority (National Agency for Safety of Medicines and Health Product [ANSM]) in late 2016 published an Information Bulletin.

Also, what is going to happen when the Notified Bodies apply for designation under the MDR and when will your Notified Body get approved for the designation under the MDR.  The designation process may take a year or more and some NB’s may not get designated for all they expect or they may decide to shutter their doors, among other scenarios.  So, make sure to read the notifications in the above paragraph and also stay in close contact with your NB to make sure you don’t get left in the cold without a proper NB for your product lines.

If you need help with your EU MDR or IVDR transition planning please email Leo Eisner at Leo at EisnerSafety dot com, or call Leo at +1 (503)-244-6151. He is the Principal Consultant of Eisner Safety Consultants.

I (as a medical device consultant, US TAG member of IEC SC 62A & 62D & Convener of SC62D JWG9 {IEC/ISO/AAMI/CENELEC 80601-2-58} and a past Notified Body Auditor) am really pleased to see the extremely hard work that has gone into this document and also in the value that it will pass on to all the stakeholders.  There are many stakeholders that were involved in this process including Notified Bodies, NB-MED EN 62304:2006 issues team (Thank you for your hard work.), NB-MED, COCIR (European Coordination Committee of the Radiological, Electromedical and Healthcare IT Industry), Manufacturers, OEMs, Standards Developers for EN & IEC & other national standards bodies, Test Houses, Consultants, other countries regulatory bodies (i.e. FDA, Health Canada, etc.) and more.  By use of so many different stakeholders that submitted some of these and other questions this document has a much more consistent view on the implementation issues with the complexity of the topic of medical device software.  

This document is good for learning about your specific implementation issue(s) or if you have the time I would highly recommend reading the whole document, as this will help you understand the intricacies of some of the situations of implementing EN 62304 with respect to the Medical Devices Directives (I’m sure there are more issues but a good portion have been captured by this first version).  I believe this document would be of great help to implement similar guidance documents for many other national medical device regulatory agencies around the world for IEC 62304:2006 (or their national version of the standard).

The Table of Contents gives a good glimpse into the realm of the issues covered in this document and covers the following topics.  I also provide a further glimpse into the document by summarizing some of the specific issues within those sections (these are the indents furthest to the right):

• Introduction (background of the purpose, rationale, the main team members, and how to provide more feedback on the document)
• Abbreviations (Section 1)
• Questions and Answers (Section 2 – Heading of sections 2.1 – 2.7)
• Scope of EN 62304 (Section 2.1)
• Goes into various different scenarios and discusses the implication and implementation issues around these scenarios: such as SAAS, Embedded software including FPGA’s (a hotly contested issue) with single chip computers, Hardware Description Languages specifying FPGAs, Stand alone software, Medical apps, Excel macros, Open & closed systems, Internet or cloud based, Server based systems, Network devices.  In addition to this list of scenarios this section also goes into questions about certification; is Validation included in this standard & if not where does it get covered; what are the expectation of the Notified Bodies with regard to the standard; can you use only part of the standard; why do class A software to EN 62304; what is IEC 82304 about (software only products); among other questions.
• Placing Software as Medical Device on the Market (Section 2.2)
• Explain ‘placing medical device (in this case software or software {s/w} as part of a system) on the market’ in EU if EN 62304 is sufficient, by itself to do this; can I change my intended use and avoid these EU guidelines and regulations; Conformity Assessment routes of the MDD; other countries acceptance / requirement of the standard; can you sign-off on documents electronically; classification of software as a MEDICAL DEVICE; how do Notified Bodies (NB’s) confirm compliance to the standard; among other questions.
• Life-cycle Processes (Section 2.3)
• If s/w development is an outsourced activity what does NB expect; does this std have an equivalent expectation to requirements such as those addressed in FDA Part 11 (Electronic Records & Signatures) in the US; details on the review process at the end of each iteration when updated versions are available during the design and development of the software; does the std require a specific development process; how split up the requirements/responsibilities of the std between the manufacturer and s/w sub-contractor; how do the maintenance activities in the std relate to ISO 20000/ITIL; what are the artifacts (documents) required by EN 62304; at what level does the Problem Resolution Process apply; does software refactoring require a formal change request; what to include in the Technical File to show compliance with EN 62304; how can agile processes be EN 62304 compliant; among other questions.
• Risk Assessment and Risk Management (Section 2.4)
• How deal with risk control measures; when & why can the safety class of a s/w SYSTEM be reduced; how use ISO 14971 with EN 62304; explain Hazard, Cause, Sequence of Events in the context of software; when should we expect additional Software Hazard Analysis guidance within EN 62304; among other questions.
• Classification and Segregation (Section 2.5)
• What is segregation and how do I prove effective; use of a specific class(es) of s/w using COTS (commercial off-the-shelf) what criteria used; how does severity under intended use relate to s/w safety class; is s/w class optional; can you downgrade the classification of the system without a fully hardware protective system; does the compiler need to be classified under EN 62304; how are development platforms & tools related to s/w safety class; relation between Risk Analysis at System level & S/W Safety Classes; explain how the 3 safety classification in the std differ from the FDA’s 3 levels; correlate IEC 61508 SIL levels to EN 62304 safety classifications; s/w classification is a real issue with big implications; among other questions.
• Specifications, testing and tools (Section 2.6)
• I’m a manufacturer of medical devices – how do I document my requirements and tests; web-based medical s/w – does the std have specific requirements related to digital cert’s, (http or https) server requirements; in regard to the std how deal with risk analysis and functional specs; appropriate level of granularity of requirements as design input, design description; which (if any) of the tracing requirements are meant to be bi-directional; questions around deployment of the s/w; what is required of open source code from the std; among other questions.
• SOUP (Software of Unknown Provenance) and Legacy Software (Section 2.7)
• How assess & qualify suppliers of SOUP s/w, when the s/w hasn’t been developed for incorporating into a medical device; what testing & documentation does EN 62304 require for SOUP to meet the std; s/w that is either stand-alone or embedded which was designed prior to publication of EN 62304 but still being placed on the market (legacy product) – what needs to be done; if legacy s/w needs significant change, what processes & documents are required to achieve &/or maintain compliance with EN 62304 and when are changes considered significant;
• References (No Section Number – just after Section 2.7)
• Software Problem Resolution Process (Annex 1)
• Helpful diagram – There are several entry points to the problem resolution process, both during development and maintenance of the software (refer to question 2.3.12).
• SOUP selection, assessment & qualification (Annex 2)
• Flowchart & text to explain an example
• Traceability (Annex 3)
• The 3 flowcharts show an overview of the dependencies which need to be traced according to EN 62304 for all 3 classes – refer to note in bottom left corner of page to know which class the flowcharts apply to (refer to question 2.6.7).
• Position paper on direct diagnosis (COCIR, 2011) (Annex 4)
• As the different stakeholders may interpret this term differently, COCIR and EUROM VI wanted to share their understanding of the term “direct diagnosis”. (Refer to question 2.5.13)

Click on the weblink to see the initial request for questions that we posted on our website 26 May 2012.  To see the posting please go to http://www.eisnersafety.com/do-you-know-how-to-use-en62304-med-dvc-sw-life-cycle-as-implemented-under-themdd-aimdd-doc/

Team-NB is a voluntary organization of Medical Device Notified Bodies (doesn’t represent all EU NB’s under the 3 Medical Device Directives) and as of 12 Nov 2012 there are now 35 members.  During the 9 Oct 2012 Assembly in addition to the adoption of the CoC three (3) new members were unanimously added (LGA InterCert GmbH – Nurnberg Deutschland, UDEM – Ankara Turkey, and ALBERK QA TECKNIC – Istanbul Turkey).

The Version 3.0 Code of Conduct for Notified Bodies under Directives 90/385/EEC, 93/42/EEC, & 98/79/EC is a very thorough document which is 31 pages long and includes the Unannounced Inspections (or Unannounced Audits of Medical Device Manufacturers that are Certified under the applicable Medical Directive) which comes from the recently proposed Medical Device Regulations.  As of the 30 October 2012 News Release 14 Notified Bodies had signed the V3.0 CoC and 2 additional NBs (LNE/G-MED & DQS) signed prior to 12 Nov 2012.  It is anticipated that more NBs will sign in the near future as they adopt the policies covered within the V3.0 CoC which shows their commitment to improve the implementation of the EU CE marking certification of medical devices through clarified organizational criteria, management of competence and assessment practices.  The major topics in the document are:

• Implementation, enforcement and monitoring of the Code of Conduct
• Qualification and Assignment of Notified Body Assessment Personnel
• Minimum time for Notified Body assessments
• Unannounced visits
• Sampling of class IIa and IIb technical files
• Design Dossier Reviews
• Rules for subcontracting
• Rules for Certification Decisions 

Further revisions will be made to be in line with the new developments of the European legislation.

The European Competent Authorities have formed a Central Management Committee (CMC) to achieve greater consistency in the interpretation and implementation of the requirements related to the medical devices sector (MDD, AIMDD & IVDD).  The CMC has issued decisions that need to be considered and implemented by medical device manufacturers.You can find the decisions at http://www.cmc-md.eu/decisions.html.  Four decisions have been issued to date:

1.     Classification and Boderline Queries (23FEB2011) – States classification decisions along with rationales for:

– Wound irrigation solutions containing antimicrobial agents (Class III under rule 13)
– System to determine bacterial contamination in blood products (falls under the IVDD)
– Qualification of Gallipots as medical devices (not a medical device)

2.     Notified Body Best Practice Guides (23FEB2011) – This does NOT affect manufacturers.  It lists the Notified Body Operations Group (NBOG) Best Practice Guides (NBP) and states that all notified bodies are expected to follow these best practices.

3.     Address of the Manufacturer and EU Representative (issued 23Feb2011, updated 7JUN2011) – The ‘address of the manufacturer’ as required in the Essential Requirements on the labels and instruction for use, is the address of the registered place of business of the legally responsible manufacturer and shall include:

– street/road,
– number/house/floor,
– postal code
– city
– state/region and
– country

The same details have to be provided for the address of the authorized representative.
NOTE:  This is more extensive that what the FDA typically requires for an address.

4.     Readability of Instructions for Use (14MAR2012) – It must be assured, that patients and professionals may use the devices as intended by the manufacturer and any ambiguities with regard to the proper and safe use due to deficiencies in the readability of IFUs are avoided.  To that end:

a.     Appropriate checks should be performed by the manufacturer on suitable samples of target users whether IFUs are  really readable and assure proper and safe use of the device.  This includes consideration of font size, quality of translations, and understandability of texts and graphics.
b.     Post-market surveillance procedures have to be sensitive to any indications of bad readability via vigilance or other channels and to any necessary corrective measures.
c.     Special care has to be taken to enable users to properly identify changes to the previous version of the IFU on the basis of a risk assessment.

As dates/revisions are not posted with the document titles, it may be difficult to determine at-a-glance if the decisions have been updated.  Please take care when checking for updates that you inspect the document of interest.

Notified Bodies have been asked to audit these particular points.  You should anticipate that some or all of these issues will be reviewed during your next audit.

If you have any questions on this matter please feel free to contact us at Leo@EisnerSafety.com.

A request for practical questions and issues has just been launched and the invitation letter for FAQ on EN62304 (a short 2 page document) and publication of the FAQ is expected by end of September 2012.  The request document is asking for your questions and any proposed answers (if you have those too) to be submitted by the end of May 2012 so you better hop on the bandwagon and get those off to the e-mail address of FAQ62304@VDE.com.  I think some of these dates may slip a little but that is not confirmed yet.  If I get confirmation of any changes in dates I will advise as soon as I can.

This may sound familiar as this is a similar process to the FAQ document that was issued in Jan/Feb of this year for the EN 60601-1, 3rd ed. Implementation FAQ document.