Regulatory Open Forum

 View Only
Expand all | Collapse all

NB requesting evidence MDCG documents are used as SOTA in device development

  • 1.  NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 11-Jun-2021 12:06
    Hello Everyone,

    Our Notified Body has asked us to "clarify where the evidence for using and considering MDCG guidelines can be found". They referenced GSPR #1  "...taking into account the generally acknowledged state of the art " with the request. We currently do not list MDCG documents in our Applicable Regulatory Standards (ARS) list because that list has been specific to standards that contain requirements. We do use MDCG documents and they are sometimes referenced within individual documents (e.g. our EUDAMED procedure), we just haven't added them to our ARS.

    Adding MDCG documents to our ARS list seems a simple (one document only) solution but I would like to hear from the forum if listing MDCGs in the ARS list is typical. If there are other, simpler solutions that I can use to respond to the NB, please feel free to share them.

    Thank you.

    Mark



    ​​​

    ------------------------------
    Mark Mortellaro
    Sr. Principal Regulatory Scientist
    Senseonics
    Clarksburg MD
    United States
    ------------------------------


  • 2.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 11-Jun-2021 13:22
    Edited by Kevin Randall 11-Jun-2021 13:23
    If a Notified Body (NB) asked me to "clarify where the evidence for using and considering MDCG guidelines can be found", I would interpret that as a request for a pointer to the QMS element containing the organization's policy / procedures for giving due consideration to MDCG guidelines.  Such an element would fit nicely within the QMS aspect implemented to address EU MDR Article 10(9) third paragraph indent (a) (i.e., in the strategy for regulatory compliance, including compliance with conformity assessment procedures).

    The EU MDR doesn't mandate conformity with MDCG guidelines, and reiterates (e.g., in Article 105) that the corresponding role of the MDCG is to contribute to the development of guidance. I suspect that the NB is not actually trying to mandate conformity with MDCG guidelines.  But if so, then I would politely discuss that MDCG guidelines are not mandatory, not legally binding, and that manufacturers have the liberty to devise other conformity solutions if such an alternative approach still meets EU MDR requirements.


    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 3.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 12-Jun-2021 05:34
    Hi Mark,

    if it is a new project, I propose my clients to replace the  generic list of potentially applicable standards by a project specific regulatory affairs plan. In this RA plan I can list all applied regional guidance like MDGC or FDA docs. The "classical" >Applicable Regulatory Standards< document may than be transferred into a QMS element how to establish such an RA-plan. One good side effect is, that the change of an overall ARS than does not trigger adaption work in other projects, the next benefit is that the RA-plan does list what is used and hence helps to avoid discussions why a particular guidance is not suitable for usage.   

    If it is an existing product, I would check whether the client creates a STED. If yes, I would check to list the aktual applied guidance documents (with a proof of application) in the STED.

    About STEDs: I propose to always create a STED which serves as an high level description (into the product, the state of the art, the system interfaces) and as table of content for the complete Tech Doc / DHF. Such STED is beneficial to steer which documents are presented to regulators. 


    ------------------------------
    Uwe Zeller | Regulatory Affairs / Risk Management Consultant
    Biberach an der Riß, Germany
    ------------------------------



  • 4.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 12-Jun-2021 08:29
    Good morning,

    For my understanding, considering subject of this post, the NB is referring to SPR1. The performance and safety requirement (SPR 1) of the Medical Device Regulations EU 2017/745) generally corresponds to MDD ER 1. In fact, much of the text is the same. This requirement states that the devices shall be ‘designed and manufactured in
    such a way’ that safety of patients and users shall not be compromised. As with ER 1 in the directives, this is under the normal conditions of use. The concept of ‘performance’ is brought in from MDD ER 3 to this requirement. The design and construction should conform to safety principles, taking into account the ‘generally acknowledged state of the art’ as required in to MDD ER 2.

    The primary reference for the information required about safety and intended performance as for the ‘generally acknowledged state of the art’ is given by the international standards.

    In case of SPR1 we need to consider the definition of state of art given by MEDDEV 2.7/1 rev.4 “The current knowledge/ state of the art in the corresponding medical field, such as applicable standards and guidance documents, information relating to the medical condition managed with the device and its natural course, benchmark devices, other devices and medical alternatives available to the target population” and more recent MDCG 2020-6.

    There is also a “new” guideline MDCG 2021-5 that explain this topic in very clear way.

    “...there are different sources providing references, definitions and practical examples on the “state of the art”, all of them non-legally binding but still useful to consider. It is the case of horizontal and vertical guidance documents, agreements of working parties, European and international standards, sectorial papers etc., as the following ones, among others:....”

    So for my understanding the best and sufficient reply will be to high light the use of more recent standards “The most recent editions of standards published by the standardisers should be considered as reflecting state-of-the-art, regardless of the OJ referencing” and the most recent guidelines.


    K


    ---------------------------------
    Katarzyna Chrusciel
    Engineer

    Italy
    ---------------------------------





  • 5.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 12-Jun-2021 08:46
    In addition for SOTA evaluation I will suggest to summarize standards and clinical practice guidelines of the medical field.

    The MDCG 2020-6 guidance mentioned before provides some more information on state of the art and similar devices:

    "Evaluation of state of the art, including evaluation of clinical data from similar devices. Data from similar devices may be also important to establish whether the device under evaluation and similar devices belong to the group of devices considered as “well established technologies” (WET)...Data from similar devices may be used, for example, to demonstrate ubiquity of design, lack of novelty, known safety and performance profile of a generic group of devices, etc.

    I hope this can help.

    K

    ---------------------------------
    Katarzyna Chrusciel
    Engineer

    Italy
    ---------------------------------





  • 6.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 02:14
    Hello,

    I've checked the last "NSAI Position on use of State of the Art Standards"  and there is cleary stated:

    "Under MDR 2017/745 and IVDR 2017/756, clients should consider the use of standards to demonstrate 'state of the art' and this should be documented within your GSPR checklist in order to comply with the requirements of Annex I"

    So, probably it is the best place where link the MDCG guidelines, especially related to clinical evaluation and design.

    Best regards,
    K

    ------------------------------
    Katarzyna Chrusciel
    Engineer
    Italy
    ------------------------------



  • 7.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 13:38
    Remember that standards are different than guidance documents.  In other words, guidance documents are not standards.  Accordingly, I would advise that guidance documents (such as MDCG guidelines) are outside the intended scope of the NSAI Position on use of State of the Art Standards.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 8.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 14:10
    Dear Kevin,

    The differences are obvious… but for development of product (title of this thread) I will use exactly same approach as stated by NSAI. I will list the MDCG guidelines in GSPR check list and especially for clinical evaluation and all topics given as task in Article 105.

    This is only my opinion
    K

    ---------------------------------
    Katarzyna Chrusciel
    Engineer

    Italy
    ---------------------------------





  • 9.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 08:23
    Hi, I had the exact same question from my NB + how do we keep track. We indicated that the MCDG are reviewed during the RA monitoring (RA intelligence) and from then we verify the impact on the product or our processes (Management review and/or DnD review). The NB was satisfied with this answer.

    ------------------------------
    Lina Ramirez
    Mechelen
    Belgium
    ------------------------------



  • 10.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 09:01
    Good day all,

    I was reading through this and hesitated respond, but I have to sigh when Notified Body auditors are just reading from a checklist and more importantly writing poor nonconformity statements.  As stated by others, MDCG guidance documents are exactly that: guidance.  We are falling into the auditing conundrum we had under the MDD/IVDD and using guidance documents as requirements like they did the MEDDEV documents.  There is no argument from a state of the art perspective, but this would be handled different from requirements.

    You are exactly right Mark that your ARS is listing standards which you are using as requirements within your quality management system, i.e. ISO 13485, ISO 14971.  But be careful citing MDCG documents in your procedures, make sure you clearly identified these as guidance documents and used only for guidance, NOT as requirements within your own process.  They will use that little loophole, 'Well you cite it in your procedure, that means you are saying you are complying with the document' mentality instead using common sense knowing these are guidance documents.  How we fell into the auditing clinical evaluation against MEDDEV 2.7/1 as a guidance document.  Also from the same point of view, careful adding to your ARS because you want to clearly indicate these are guidance documents and not being used as requirements.

    I agree with Lina's approach as these should be part of your regulatory intelligence and as Kevin said part of regulatory strategy for compliance.  When any external origin document is revised, updated, new version, etc., there should be an assessment for impact.  Guidance documents are helpful to keep track of from a regulatory intelligence perspective, not a requirements perspective because it does give regulatory agencies current thinking, e.g. U.S., Australia, Canada.  When you are putting together your system make sure this is regulatory intelligence for guidance documents and not identifying new requirements as you would if an ISO standard or regulation was updated.

    ------------------------------
    Richard Vincins RAC
    Vice President Global Regulatory Affairs
    ------------------------------



  • 11.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 13:51

    Dear all,

    Probably I'm wrong, but I'm not so sure that this MDCG guidelines are "only guidelines". 

    For my understanding the Auditor asked for what is stated in MDR. I don't consider this request "poor" but  absolutely appropriate  "clarify where the evidence for using and considering MDCG guidelines can be found "

    ANNEX VII REQUIREMENTS TO BE MET BY NOTIFIED BODIES, in article related to "Conformity assessment activities" it is clearly stated: the notified body shall ensure that audit findings are appropriately and consistently classified in accordance with the requirements of this Regulation and with relevant standards, or with best practice documents developed or adopted by the MDCG.

    The notified body shall, where relevant, take into consideration available CS, guidance and best practice documents and harmonised standards, even if the manufacturer does not claim to be in compliance.

    For Clinical evaluation assessment in particular, it is stated that: These procedures referred to in the first paragraph shall take into consideration available CS, guidance and best practice documents.

    Also the Article 105 of MDR list of all task of the MDCG.

    In particular (c), (d) and (e) are interesting in device development. I list them below.

    (c)        to contribute to the development of guidance aimed at ensuring effective and harmonised implementation of this Regulation, in particular regarding the designation and monitoring of notified bodies, application of the general safety and performance requirements and conduct of clinical evaluations and investigations by manufacturers, assessment by notified bodies and vigilance activities;

    (d)        to contribute to the continuous monitoring of technical progress and assessment of whether the general safety and performance requirements laid down in this Regulation and Regulation (EU) 2017/746 are adequate to ensure safety and performance of devices, and thereby contribute to identifying whether there is a need to amend Annex I to this Regulation;

    (e)        to contribute to the development of device standards, of CS and of scientific guidelines, including product specific guidelines, on clinical investigation of certain devices in particular implantable devices and class III devices;

     

    In article 106 it is also stated: The clinical evaluation guidance referred to in point (c) of paragraph 10 shall be published following consultation with the MDCG.

    paragraph 10 (c) : (c) to develop and review clinical evaluation guidance and performance evaluation guidance for performance of conformity assessment in line with the state of the art with regard to clinical evaluation, performance evaluation, physico-chemical characterisation, and microbiological, biocompatibility, mechanical, electrical, electronic or non-clinical toxicological testing;

    It would probably be advisable to seek the advice of some lawyer.

    Best regards,

    K



    ------------------------------
    Katarzyna Chrusciel
    Engineer
    Italy
    ------------------------------



  • 12.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 15:06

    Indeed Katarzyna, it is not uncommon for NBs and other parties to assert more weight to guidance documents than what is fundamentally intended for guidance documents. This is no surprise in light of narratives like those in MDCG 2019-6 which can seem conflicting.  For example, all in one paragraph, MDCG 2019-6 states, "…guidance documents are by definition not compulsory…", yet then goes on to say, "…However, all guidance documents endorsed by the MDCG reflect the interpretation of the EU law jointly agreed by the authorities which are in charge of interpreting and applying the EU law.  Hence notified bodies should be encouraged to apply these guidance documents (also taking into consideration Section 1.6.2 of Annex VII to the MDR/IVDR1).  Furthermore, it is to be noticed that the European Court of Justice often refers to guidance documents when developing its rulings. Hence Notified Bodies have an interest, also in terms of liability risk, to follow that guidance".

    I contend that the forgoing MDCG 2019-6 narrative and similar ones from EU MDR Annex VII are recommendations for NBs in the context of their unique role as conformity assessment bodies, and thus tangential to NB liability as unique and distinguished from the manufacturer's liability.  Accordingly, it is not surprising, and is probably for good measure, that conformity assessment bodies assert accepted guidelines as a baseline during conformity assessments.  But regardless of such baseline practices by NBs, MDCG 2019-6 nevertheless ultimately reminds us of an important boundary:  Non-conformities will not be raised against standards or guidance but need to be phrased against legal requirements.

    Accordingly, the fundamental purpose of guidelines remains intact, as do the basic intentions of the EU MDR (and the MDD); specifically, that manufacturers have the liberty to devise and employ alternative conformity solutions if such solutions fulfill GSPR requirements.

    Again, this remains the case even though EU MDR Annex VII requires NBs to "give consideration" to guidelines and best practices.  I suggest that "giving consideration" be interpreted in accordance with my preceding explanation above.  In other words, I advise that "giving consideration" does not mean mandate; indeed, such an approach would run contrary to longstanding European legislative and other precedent holding that neither standards nor guidelines are legally binding (unless a particular standard or guideline is specifically demanded by a legislation).  In fact, MDCG 2021-5 applies a similar permutation of this principle even in the context of the almighty SOTA and GSPR #1, reminding us that giving account of SOTA does not mean SOTA is mandated.

    By similar reasoning I also advise that the provisions of EU MDR Articles 105 and 106 defining the roles of the MDCG, including its participation in the development of guidelines, do not undo the aforementioned principles and fundamentals regarding the basic intentions for, and limitations of, standards and guidelines.

    Manufacturers, as the penultimate experts on the development of their devices, need to retain their right to devise and apply GSPR conformity assessment solutions appropriate for the manufacturer's devices.  Such solutions might be based on conformity with a standard or guideline, or they might not.





    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 13.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 15-Jun-2021 07:35
    Awesome Kevin

    You have made a good argument here.

    ------------------------------
    Ginger Cantor, MBA, RAC
    Founder/Principal Consultant
    Centaur Consulting LLC
    River Falls, Wisconsin 54022 USA
    715-307-1850
    centaurconsultingllc@gmail.com
    ------------------------------



  • 14.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 15-Jun-2021 07:28
    Richard, I love your voice of rationality.

    Once you start applying guidance as requirement, one is entering a deep black hole.  Because- why stop there, what about position papers, podium policies at conferences from FDA, etc.

    Just a really bad practice.  I agree.


    ------------------------------
    Ginger Cantor, MBA, RAC
    Founder/Principal Consultant
    Centaur Consulting LLC
    River Falls, Wisconsin 54022 USA
    715-307-1850
    centaurconsultingllc@gmail.com
    ------------------------------



  • 15.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 13:53
    Giving due consideration to MDCG guidelines as SOTA should be integrated into the EU MDR regulatory strategy (see my preceding post in this thread about that).

    But an NB's expectation for keeping track of MDCG guidelines (or other documents of external origin) is generally driven by a fundamentally different requirement, specifically, such as that prescribed by EN ISO 13485 clause 4.2.4, second paragraph, indent (f) regarding control of documents of external origin.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 16.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 14:16
    Hallo all,

    It seems that we are all in alignment, that such guidance needs to be appraised, whether we call it regulatory strategy, regulatory intelligence or regulatory affairs planning.

    I see ISO 13485 clause 7.2.1 (c) as the "anchor" why guidance documents need to be systematically retrieved, appraised and  (based on the appraisal) be applied: Citation: "Determination of requirements related to product... The organization shall determine: ... applicable regulatory requirements related to the product;"

    ------------------------------
    Uwe Zeller | Regulatory Affairs / Risk Management Consultant
    Biberach an der Riß, Germany
    ------------------------------



  • 17.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 15:27
    ISO 13485 clause 7.2.1(c) reminds us that organizations shall determine applicable regulatory requirements related to the subject device.  ISO 13485 establishes that applicable "regulatory requirements" encompasses requirements contained in any law applicable to the user of ISO 13485, and then it cites examples of "applicable law" to be "statutes, regulations, ordinances or directives".  Accordingly, because guidelines are not applicable law (i.e., not legally binding), I don't associate ISO 13485 clause 7.2.1(c) with guidelines and standards unless a particular guideline or standard is demanded by the applicable law.  For example, the MDD and EU MDR legislatively demand conformity with harmonized standards for symbols.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 18.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 16:42
    Hello Kevin,

    I continue to have a different interpretation and maybe a European law expert might help with guidance. 
    1st. At the moment, there is no harmonized standard for the MDR. Our standardization community did see that the latest request (link) is moving, but it will take time to even get the basic horizontal standard 13485 harmonized. Also, not all standards used in the field will be harmonized. This will require some thinking, as an ISO/IEC standard is state of the art whether itis harmonized or not. 
    2nd. Example: Even once the ISO 13485 will be harmonized, a manufacture is not forced to apply it. In legal terms, "only" MDR article 10 (10) is binding. 
    3rd. State of the art provided as (harmonized) standard gets its impact by the >presumption of conformity<. If a manufacture applies (harmonized standards), the presumption of conformity applies. 
    4th. I conclude (and recommend) that MDCG documents  have a similar attribute of presumption. That is leading me to the conclusion, that MDSG documents establish their own class of regulatory requirements which has to be considered.
    5th. In the end we might reach a hierarchy: harmonized standards << standards << EU Guidance | PS I did not address common specifications yet.

    ------------------------------
    Uwe Zeller | Regulatory Affairs / Risk Management Consultant
    Biberach an der Riß, Germany
    ------------------------------



  • 19.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 19:17
    Edited by Kevin Randall 14-Jun-2021 19:18
    Hi Uwe, many thanks for your comments; I always appreciate your keen insights and expertise.

    Correct, no standards have yet been harmonized for the EU MDR, as has been extensively discussed in prior Forum discussions.  Further discussion of that situation seems to be outside the scope of this thread.  However, it was still germane to respond to the mention that was made of ISO 13485 clause 7.2.1(c) regulatory requirements in relation to guidelines and standards, and to give an example [the only one that comes to my mind in the MDD and EU MDR are their general demands for conformity with harmonized symbols standards (when such harmonized standards exist)].

    The voluntary nature of harmonized standards and the benefit of the associated presumption of conformity has been discussed at length in other Forum discussions, for example here: https://connect.raps.org/communities/community-home/digestviewer/viewthread?MessageKey=1b365fc8-cd3c-443a-9d5c-0962a690ef1b&CommunityKey=5af348a7-851e-4594-b467-d4d0983b6d89&tab=digestviewer#bm1b365fc8-cd3c-443a-9d5c-0962a690ef1b

    I suspect that when an NB requests explanation of how an organization tracks changes to documents of external origin, it will typically involve an organization that holds an ISO 13485 registration.  Thus I mentioned that scenario in my prior post.  But per the other Forum discussions about the voluntary nature of standards, I certainly agree that an organization may not hold an ISO 13485 registration yet still be found to be in conformity with the EU MDR's QMS requirements.

    MDCG guidance "should" be "considered".  But within the limits of my other associated narratives in this thread, MDCG guidelines don't generally have legal authority, and thus aren't generally to be handled as legally binding by NBs.

    Establishing an internal policy on the hierarchy of application of harmonized standards, non-harmonized, standards guidelines, etc., may certainly be a good idea for certain organizations.  Yet I will continue to advise manufacturers not to forget that their is no legislative basis for such a hierarchy (except for rare examples such as the one I cited above about symbols standards).  Other than such rare cases, manufacturers have the aforesaid general liberties to decide on what type of conformity solutions will be employed.  Manufacturers need to retain that right, and should staunchly defend that right, in order to keep a balance against agency overstep.

    Thanks also Uwe for introducing the topic of CS (which are generally mandatory instruments, but are not standards, and certainly are not guidelines, and thus should not be approached as a standard or guideline).  Seems like you might have some wisdom for us regarding CS in their own rights and I would be edified to learn your corresponding thoughts on CS in a separate thread on that topic.

    Thanks again Uwe for your keen insights and expertise.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 20.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 16:25
    Offline I received another comment that bears mentioning about how to record one's application of MDCG guidelines.  Specifically, regardless of whether the organization chooses a harmonized standard, an unharmonized standard, a guideline, a best practice, or some other conformity assessment solution, the organization needs to be sure to identify and record (and justify) such solution in the GSPR checklist.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 21.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 16:33
    Edited by Vidya Jayaraman 14-Jun-2021 16:52
    Hi Kevin,

    In response to your point that non conformities cannot be raised against a guidance - can review questions be raised claiming non-compliance with a guidance specifically MDCG 2020-6? The NB has commented that we have insufficient clinical evidence because our device is not a Well established device per criteria identified in MDCG 2020-6. The device is a class 3 implantable, wondering if that automatically disqualifies it from the WET category. Ironically, the MDR does not define WET and between MDCG and MDR, MDR takes precedence.

    Of course under MDD, they did agree that the device was "well established" , the terminology did not exist until April 2020 when MDCG 2020-6 was released.

    Thanks,
    Vidya

    ------------------------------
    Vidya
    USA
    ------------------------------



  • 22.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 18:26
    Hi Vidya,

    I can't definitively address any particular scenario without full insights about the background facts and data.  But let me first reiterate that it is MDCG 2019-6 (rather than my own interpretation) that states that "Non-conformities will not be raised against standards or guidance but need to be phrased against legal requirements."  Indeed, without a corresponding ruling from the European Court of Justice (or perhaps even with a corresponding ruling), I know of no legal basis for phrasing a nonconformity against a standard or guidance.  Instead, nonconformities are to be phrased with respect to a legislative requirement (such as an applicable GSPR for example).

    I don't believe class 3 implantable devices are automatically disqualified from being included in the WET category.  For example, EU MDR Article 61(8) acknowledges that certain implantable and class 3 devices may be found to be WET and thus eligible to be legally exempted from clinical investigations.  In other words, if class 3 implantable devices were automatically disqualified from being included in the WET category, then there would be no grounds for Article 61(8) to exist.

    Further to my preceding explanations, and also to Annex IX section 5.1(a), an NB's conclusions about class III implantable device clinical evidence are to be focused on whether the clinical evidence sufficiently addresses the benefit-risk determination, the consistency of that evidence with the intended purpose and medical indication or indications, and the PMCF plan (if any).  As noted in my prior narratives, pursuant to EU MDR Annex VII, the NB is expected to "give consideration" to relevant guidelines, but shouldn't be citing guidelines in nonconformity narratives.  Instead, a nonconformity needs to be written with respect to a legislative requirement, such as an applicable GSPR.  A recipient's response to such a nonconformity (or proposed nonconformity) needs to be focused on demonstrating that the clinical evidence sufficiently addresses the applicable GSPR.  In any event, the recipient needs to have a scientifically-defensible basis explaining why its conformity solutions sufficiently address applicable GSPR.  This should be all stakeholders' fundamental focus rather than conformity with a guideline (unless the manufacturer has already declared that it applied the guideline as its conformity solution).

    As an aside, remember that, for class III implantable devices not meeting MDCG 2019-6's WET definition, 2019-6 nonetheless accepts clinical evidence from studies with potential methodological flaws where data can still be quantified and acceptability justified.  So, if the clinical evidence measures up to this level of data quality, then there is grounds to declare conformity with MDCG 2019-6 even if the device fails that guideline's WET criteria.

    Note also that the EU MDR definition of clinical evidence means clinical data and evaluation results that are of sufficient amount and quality to allow a qualified assessment of whether the device is safe and achieves the intended clinical benefit(s), when used as intended by the manufacturer.  This represents a potential wide spectrum of data, and certainly seems to give ample opportunity for all parties to rely on the clinical data from a legacy device.  If an NB is claiming that there is insufficient clinical evidence, then the NB must be able to fundamentally support a claim that the clinical evidence doesn't allow a qualified assessment of the device's safety and efficacy.  That seems to be a high bar, and certainly a subjective one, to be supported by the NB regarding a legacy device with extensive EU marketing tenure.

    As another aside for an MDD-certified device being recertified under the EU MDR, be sure that the deliberations aren't being calibrated based on criteria for "equivalent devices".  This is because clinical data from an MDD-certified device being recertified under the EU MDR is not data from an "equivalent device"; instead such data are data from the same device.​

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 23.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 15-Jun-2021 11:03
    Appreciate your detailed, well-crafted response as always, Kevin. I have a few follow up questions:

    1) What do you think of this Q from the NB - "Would you please provide a CER that is in full compliance with the MDR, MEDDEV 2.7/1 rev.4, MEDDEV 2.12/2 rev.2, and all relevant MDCG guidance's including MDCG 2020-6"
    other than MDR, everything else is not legally binding, as we all know...They have made reference to MDCG 2020 in several other questions. For instance, "As this is not considered sufficient clinical evidence per MDCG 2020-6 section 5"

    2) When you say guidance should only be "considered" - could you provide examples?

    3) If NB cannot raise questions asking demonstration of compliance to MDCG per legal requirements, I'm assuming we can't respond using MDCG as basis, is that correct? For instance, use MDCG definition of WET as basis for sufficiency of clinical evidence.

    4) Other than politely pointing out to NB that some of their asks are unreasonable (not saying they are in our case, just a hypothetical), is there any other way to appeal their decision like the FDA appeal process?

    ------------------------------
    Vidya
    USA
    ------------------------------



  • 24.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 15-Jun-2021 16:25

    Thanks, Vidya for the four additional questions.  A lot to unpack there; forgive me for the lengthy (yet still abbreviated) answer.  For liability reasons, a full response would need to happen under the covering of a consulting agreement and via direct communications, as a forum venue leaves ample opportunity for misunderstandings.  I'll do my best to give a general answer that I hope will contain some useful nuggets.

     
    But before generally responding to the four questions, let me for the record first add to my prior narratives by stating that my firm's general policy is to encourage clients to always make a good faith effort to conform with applicable guidelines such as the MDCG guidelines (which in the case of clinical evaluation and PMCF, also point us back to certain aspects of MEDDEVs).  Reinventing wheels is in my opinion to be avoided wherever possible and appropriate.  And like Uwe wisely mentioned, when organizations apply such guidelines, NBs tend to give a something like a presumption of conformity similar to the way they respond to harmonized standards.  I've said before in the Forum that, even though we may indeed have legal and technical grounds for alternative approaches, it is true that the path of least resistance has definite benefits, often being less burdensome in the end then fighting an agency.  But when push comes to shove, and especially in a scenario where GSPR conformity can legitimately be achieved via a route other than the paradigm(s) recommended in a guideline, then it is, for multiple reasons, imperative that manufacturers retain the right to employ customized solutions.  That principle is paramount in the MDD and EU MDR and must not be dismissed by any NB.

    My responses to the four questions:

    1) In the context of clinical evaluation, let me first say that my firm's general processes for clinical evaluation are based on the aforesaid MEDDEVs as adapted for the EU MDR, and on related MDCG guidelines.  But if an NB says, "Would you please provide" evidence of conformity to non-binding guidance documents, then I would be cautiously optimistic that the NB realizes guidelines are not mandatory.  And if an organization finds itself in a scenario where conformity with those guidelines isn't appropriate, then I reiterate what I said before:  Specifically, an NB's conclusions about clinical evidence are, by legislation, to be focused not on guideline conformity, but instead on GSPR-related focal points like whether the clinical evidence sufficiently addresses the benefit-risk determination, whether the evidence is consistent with the intended purpose and medical indication or indications and sufficiently address device safety and performance, and whether the PMCF plan (if any) is adequate.

    Accordingly, if an NB lodges an objectionable request/demand for conformity with non-binding clinical evaluation guidelines, then an organization's response needs to be primarily focused on demonstrating that the clinical evidence sufficiently addresses the applicable GSPR, and needs to do this in terms of the aforesaid NB clinical evidence assessment focal points.  Ultimately, in responding to such an NB request, an organization needs to state its rebutting position respectfully and scientifically, and then ultimately declare that the organization believes that its clinical evidence sufficiently address the applicable GSPRs and NB focal points.

    If a scientifically reasonable case can in fact legitimately be made, and is made, then that can have several positive effects: It tends to relieve the NB's aforesaid liability; it makes it easier for the NB to accept the alternative route; and it also puts the onus back onto the NB to scientifically lodge a rebutting position.  That final effect is important; indeed, it's easy for an NB to cite an organization for not following a guideline or standard (and NBs know that many organizations readily capitulate), but it's not so easy for the NB to scientifically invalidate the organization's reasonable scientific rebuttal.  Once an organization makes a scientifically reasonable rebuttal, I've found that it often settles the issue.

    As an aside, my experience has been that NB assessors (and even FDA inspectors) often want to help and offer alternative suggestions.  But remember that they can't do that without violating the code of ethics.  They are only allowed to state the apparent nonconformity, and without consulting or giving overt hints.  When I do my clients' internal audits in a consulting capacity where I have slightly more liberty to collaborate toward the greater goal of improvement and public health, I remind my clients, "…Listen, I have to write my findings a certain way within regimented boundaries that often make it seem like I'm demanding a certain 'inside the box' solution.  But that's not the intent of the finding; remember that I'm always open to hearing alternative solutions…"  I've found that this same dynamic often (but of course not always) exists with agency auditors.  Accordingly, when I'm in the auditee role, and if an outside-the-box solution is needed, then I be sure to lodge it and see the auditor's reaction before reaching conclusions about the apparent unreasonableness of the auditor.  If an assessor is in fact unreasonable, then I've repeatedly lobbied and appealed successfully in the past (I'll talk briefly about that below in question 4).

    2) As noted in my prior post, the NBs are obligated by the EU MDR to "take into consideration" guidance and best practice documents.  MDCG 2019-6 gives a hint that this means that NBs are "encouraged to apply these guidance documents" (again revealing the non-binding nature of guidelines) during conformity assessments.  A myriad of examples show NBs doing this, such as when an NB requests (or inappropriately demands) conformity with MDCG or MEDDEV guidelines.

    3) "…If NB cannot raise questions asking demonstration of compliance to MDCG per legal requirements…":  I would say that the NBs can raise questions about compliance with guidelines, and are legislatively allowed to do so as part of taking the guidelines "into consideration" under EU MDR provisions like Annex VII.1.6.2.  NBs can ask such questions, but NBs aren't allowed to lodge nonconformities about guideline conformity.  Remember that a big part of the game is NBs asserting the guidelines in hopes that the auditee has already complied, or will easily agree to comply (and in reality, that is often the easiest for everyone as noted before).

    "…I'm assuming we can't respond using MDCG as basis, is that correct?" I would say that's actually incorrect.  Although this thread has a lot of posturing, huffing, and puffing about pushing back against potential NB overreach, don't let those contingency narratives and tactics give you the wrong idea.  As regulated entities, we are absolutely and intrinsically encouraged to apply MDCG guidelines since all MDCG-endorsed guidance documents do in fact reflect "the interpretation of the EU law jointly agreed by the authorities which are in charge of interpreting and applying the EU law."

    4) There is indeed an appeals process that can be pursued in the event an organization can't come to terms with the NB through the regular channels.  I personally consider this type of approach to be a last resort, but have leveraged parts of it successfully before.  Note that the appeals process is generally governed by the standards that govern the NB (e.g., the EN ISO/IEC 17021 series).  I would actually say the appeals process starts by default in all conformity assessments by way of the fact that an auditor's findings and the auditee's response are subject to independent review by someone else within the NB.  That is a first opportunity for appeal that is already baked into the regular process.  Thereafter where needed, the next step is usually filing a formal complaint with the NB via its internal complaint process (see the NB contract and other NB procedures for a particular NB's complaint process).  If that doesn't resolve the issue, then a complaint can be filed with the authority that designated the notified body.  These appeal steps can take months or longer to play out, but are nonetheless appropriate in some cases.  And don't forget that in the midst of all this for the context of clinical evaluation of class III implantables (and certain other devices), the NB's clinical evaluation assessment report and the manufacturer's CER and PMCF documents are forwarded to the Commission and in turn to the Article 106 relevant expert panel for its opinion about the sufficiency of the level of clinical evidence.  So that intrinsic class III implantable clinical evaluation review mechanism also may provide an opportunity for appeal.  But as I mentioned above, I advise to only use an appeals process as a last resort.  In most scenarios, I believe that NBs prefer to avoid a formal appeals process.

    Hope this helps!

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2021 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 25.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 15-Jun-2021 17:14

    Thanks Kevin,  this is a very good response to this challenge.

    All,

    I like to add a pragmatic thought. There is the clinical evaluation assessment report template MDCG 2020-13 (link), and this template was not yet mentioned in this sub-thread about clinical evaluation.
    In my understanding, NB's are "motivated" to apply this template strictly and (maybe due to a lack of experience) an NB user of this template might be "glued" to the wording. This does not help a manufacture directly, but maybe we can use the template to understand the dead loop of the NB user and employ the understanding of the template to push information to the NB user , so that the NB user can overcome this dead loop.

    .... and my typical question: does this thought help us?

    Greeting and good night from the south of Germany. 



    ------------------------------
    Uwe Zeller | Regulatory Affairs / Risk Management Consultant
    Biberach an der Riß, Germany
    ------------------------------



  • 26.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 14-Jun-2021 16:50
    Hi all, one more though:

    That the applied Guidance relates to the GSPR Annex I documentation goes without saying. 
    My comments are relate to the start of this thread (in my words: how do I document the planning). >> there should be a process frame to initially identify the relevant content (aka requirements) of this documents. The objective evidence, that content of these documents have been applied, is than part of the GSPR. 

    Does this make sense?

    ------------------------------
    Uwe Zeller | Regulatory Affairs / Risk Management Consultant
    Biberach an der Riß, Germany
    ------------------------------



  • 27.  RE: NB requesting evidence MDCG documents are used as SOTA in device development

    Posted 16-Jun-2021 12:32
    I want to thank all for this lively discussion. I had intended to send my thanks earlier but the discussion get going! My company cites our ARS in our Strategy for Regulatory Compliance SOP (and others SOPs) so we have selected to add a "Guidance" table into the ARS document, after the Standards table. The new table will be preceded by instructions on use of the guidance documents. Our Strategy SOP will be updated if needed (current language may be adequate). We have chosen to compile the guidance documents into the ARS because it will be the simplest way for us to keep track of them, as we keep track of Standards.

    Thank you all.

    Mark

    ------------------------------
    Mark Mortellaro
    Sr. Principal Regulatory Scientist
    Clarksburg MD
    United States
    ------------------------------