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
------------------------------
Original Message:
Sent: 24-May-2021 14:13
From: Peter Miko
Subject: MDR Annex II. 4. GSPRS
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:
- list of the general safety and performance requirements,
- apply/does not apply to the device,
- explanation why requirements are considered not applicable,
- the method(s) used to demonstrate conformity with each applicable general safety and performance requirement,
- the harmonised standards, CS or other solutions applied,
- 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
------------------------------