Regulatory Open Forum

 View Only
  • 1.  MDR Annex II. 4. GSPRS

    Posted 24-May-2021 14:13

    Dear Colleagues, may I ask how you would manage the GSPR requirements in Chapter 4. of Annex II?

     The chapter requires, that "the documentation shall contain information for the demonstration of conformity with the general safety and performance requirements set out in Annex I that are applicable to the device taking into account its intended purpose, and shall include a justification, validation and verification of the solutions adopted to meet those requirements.

     The simplest solution might be to create a table, that has 6 columns, which are the followings:

    1. list of the general safety and performance requirements,
    2. apply/does not apply to the device,
    3. explanation why requirements are considered not applicable,
    4. the method(s) used to demonstrate conformity with each applicable general safety and performance requirement,
    5. the harmonised standards, CS or other solutions applied,
    6. the link to the controlled documents offering evidence of conformity with each harmonised standard, CS or other method applied to demonstrate conformity with the general safety and performance requirements. The information referred to under this point shall incorporate a cross-reference to the location of such evidence within the full technical documentation and, if applicable, the summary technical documentation.
    with the best regards and many thanks

    ------------------------------
    Peter Mikó M.D
    ArtPharm Ltd.
    Gyermely
    Hungary
    ------------------------------


  • 2.  RE: MDR Annex II. 4. GSPRS

    Posted 24-May-2021 14:38
    The longstanding best practice for demonstration of conformity is to do so via a trace matrix.  Under the MDD, it's usually called an ER Trace Matrix; under the EU MDR, a GSPR Trace Matrix.  Your suggested columns are the right ones needed to definitively demonstrate conformity under the EU MDR.  This is how we've been doing it for our clients with positive outcomes thus far.  Looks like you're on the right track!

    ------------------------------
    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: MDR Annex II. 4. GSPRS

    Posted 24-May-2021 14:55
    Dear Kevin,
    thank you for your quick answer. 
    regards

    ------------------------------
    Peter Mikó M.D
    ArtPharm Ltd.
    Gyermely
    Hungary
    ------------------------------



  • 4.  RE: MDR Annex II. 4. GSPRS

    Posted 25-May-2021 03:52
    Hello Peter, please look at the newly published MDCG 2021-8.

    Appendix 6 table B provides a template "Matrix of General safety and performance requirements". It combines your columns 4 and 5, and of course you can have as many columns as you wish, but if you follow the MDCG guidance you can be pretty confident of meeting the expectations of both Competent Authorities and Notified Bodies.

     https://ec.europa.eu/health/sites/default/files/md_sector/docs/mdcg_2021-8_en.pdf
    Europa remove preview
    View this on Europa >


    ------------------------------
    Kevin Painter
    Mentor, Medical Device Regulatory Compliance
    Poland and United Kingdom
    ------------------------------



  • 5.  RE: MDR Annex II. 4. GSPRS

    Posted 25-May-2021 05:05
      |   view attached
    Hi Peter:
    Just to add to Kevin's response/methodology, we have refinement based on two facts:
    • the Technical File should be written to the primary reader - a CA investigator following up on an adverse incident
    • some devices have complex but known inherent failure modes
    We find giving a "reference" to a number of items (e.g. GSPR G#, Risk R#, Benefit B#, Design Input I# ...) it really helps to ensure consistency and produce a readily searchable and index-able term.
    We also tend to show a mapping for any residual risks which we feel will generate a known failure, see example attached. In that way if we ever have to ship in a "technical file" to a CA to investigate a complaint, we can give them a map and hyperlinked references to assist their investigation.

    My real advice is always remember getting through an NB assessment easily is a nice to have, the real test is does: my solution facilitate investigation of a failure? The answer will depend on your product, its technologies and likely failure modes.
    Have fun as we all try to improve on this one!

    Best of luck in getting ready for tomorrow! :-)

    Neil

    ------------------------------
    Neil Armstrong FRAPS
    CEO MeddiQuest MeddiQuest Limited
    MeddiQuest
    Peterborough
    United Kingdom
    ------------------------------



  • 6.  RE: MDR Annex II. 4. GSPRS

    Posted 25-May-2021 12:20

    The fundamental intent of Technical Documentation (such as Annex II Chapter 4) is to identify which basic general safety and performance requirements apply to a subject device, and then to demonstrate conformity with such general safety and performance requirements.  The Technical Documentation is for showing evidence of fundamentally proper, safe, and effective device design and manufacturing.

    The fundamental intent of the Technical Documentation is not to facilitate device failure investigation, nor to showcase or document the failure investigation process.  For example, the GHTF has stated, "The STED would not typically be used to aid the postmarket investigation of adverse events…where different types of information are likely to be called for…"

    Though device failure investigation is certainly important, that activity is instead a requirement embodied by fundamentally different aspects of the EU MDR, which have fundamentally different purposes, such as the corresponding aspects of Article 10(9) (e.g., those on vigilance and corrective/preventive action), and such as the failure investigation requirement of Article 89(1).

    One sure way to achieve a poor audit outcome is to give assessors different information than what they've requested.  Another fine way to crash is to convolute process A with out-of-scope content from process B.  Accordingly, if a conformity assessment body has requested evidence of GSPR conformity, then I would strongly advise against responding with a showcase of the failure investigation process.  Such an approach is guaranteed to confuse and agitate the assessor, and to increase the number of nonconformities that the assessor documents.



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



  • 7.  RE: MDR Annex II. 4. GSPRS

    Posted 25-May-2021 12:22
    And obviously, it seems to go without saying, that we should not be embedding the device failure investigation process within our Technical Documentation.

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