Regulatory Open Forum

 View Only
  • 1.  Complaints

    Posted 20-Jun-2018 02:06

    Hi,

     

    Do all alleged deficiencies need to be logged in as complaints ? Is there a threshold to differentiate them as technical support or service enquiries or feedback ? If they do not fit in any of these , they get flagged as complaint?

     

    Also do all complaints need an adverse event evaluation , can there be a criteria set for categories of complaint that would require an evaluation for an adverse event?

     

     

    Thanks & Regards,

     

    Rashmi Pillay
    Regulatory Affairs Associate


    Ellex 

    3-4 Second Avenue

    Mawson Lakes SA, 5095

     

    T + 61 8 7074 8105
    rpillay@ellex.com

    W ellex.com

    .............................................................................
     
    One Powerful Vision.

    Confidentiality: This e-mail is from Ellex Medical Pty Ltd, ABN 35 008 276 060. The contents are confidential and intended only for the named recipient of this e-mail. If the reader of this e-mail is not the intended recipient you are hereby notified that any use, reproduction, disclosure or distribution of the information contained in the e-mail is prohibited. Viruses: Any loss/damage incurred by using this material is not the sender's responsibility. No warranty is made that this material is free from computer virus or other defect. Ellex Medical Pty Ltd entire liability will be limited to resupplying the material. If you have received this e-mail in error, please reply to us immediately and delete the document. 

     



     



  • 2.  RE: Complaints

    Posted 20-Jun-2018 08:41
    You can have different categories, but you have to be really careful and closely follow the terminology in the definition of a complaint. And you should be very clear in your SOPs as to how you are defining those exceptions.

    As an example, it is fairly common that parts replaced during routine servicing are not deemed to be complaints unless they fail prior to the indicated service interval. If, for instance, a site did not have the correct service completed, failure of a known "wear part" after the published life cycle would not be deemed a complaint. However, you should be sure and document these instances with the justification as to why it isn't a complaint. Similarly, a known bug, described in the release notes (and relevant reg submission) that occurs "as expected" could be an exception, as it is known and in the labeling. However, be careful, because if that bug starts to manifest itself in ways not int he release notes, it would be a complaint.

    As for adverse event evaluation, it depends. Generally, all complaints should be assessed for whether they did produce an AE, or potentially can in the future. However, to the extent there are well-characterized complaints to which that answer is known, you don't necessarily have to assess every time - you can reference a previous assessment.

    g-

    ------------------------------
    Ginger Glaser RAC
    Chief Technology Officer
    MN
    ------------------------------



  • 3.  RE: Complaints

    Posted 20-Jun-2018 11:04
    I agree with Ginger. In addition, to your question
    "Also do all complaints need an adverse event evaluation , can there be a criteria set for categories of complaint that would require an evaluation for an adverse event?"

    Yes, if there was any harm to patient-regardless of whether or not the device caused the harm. There is a 'malfunction' category that would need to be reported as an MDR if you determine that the continued usage of device would lead to patient injury or death.

    I found this document useful, its a GHTF document from SG2 that includes representatives of the regulatory authorities and industry representatives of the USA, Europe, Canada, Japan and Australia. "Medical Devices Post Market Surveillance: Global Guidance for Adverse Event Reporting for Medical Devices", 30 November 2006


    I did not find an updated IMDRF guidance (because GHTF is essentially IMDRF now), but the concepts apply. Also, make sure your procedures dictate the investigational methods.



    ------------------------------
    Vidyalakshmi Jayaraman
    RA Specialist
    Marlborough MA
    United States
    ------------------------------



  • 4.  RE: Complaints

    Posted 20-Jun-2018 11:50

    For the US, I advise caution here. Every allegation of a deficiency in the attributes listed in 820.3(b) is a complaint and must enter the 820.198 complaint system.

    Every complaint must be evaluated, 820.198(a)(3), to determine if it is a reportable. There are no exceptions. (The Warning Letters are replete with cases in which manufacturers failed to prform an evaluation of every complaint.) However, evaluation is an often misunderstood concept. While there is no formal quality definition (such as ISO 9000:2015) the concept means to compare a situation against a set of criteria to make a decision. In this case the facts of the complaint are compared against the reportability criteria to decide on reportability. If yes, then follow Part 803 as well as 820.198. If not, continue to follow 820.198.

    If the evaluation determines the complaint is potentially reportable, it must be investigated under 820.198(d). There are other cases in which the investigation is not required if there is a prior investigation. This does not hold for potentially reportable events.

    I use the term potentially reportable, because the final decision on whether or not to report is made in Part 803 and documented in the MDR Event File, 803.18(b)(1)(i).



    ------------------------------
    Dan O'Leary
    Swanzey NH
    United States
    ------------------------------



  • 5.  RE: Complaints

    Posted 22-Jun-2018 01:29
    ​Hi,

    Although the complaint definition is harmonised for the FDA and ISO 13485 , the requirements of complaint handling are different .'For ISO 13485,there needs to be an initial recorded review and evaluation of the complaints to determine if the feedback received is a complaint as defined in 3.4 of ISO 13485.It is important to note that this evaluation is not the same as a complaint investigation.The evaluation is performed to determine whether the information is truly a complaint or not and to determine whether the complaint needs to be investigated or not.'

    ------------------------------
    RashmiAdelaideAustralia
    ------------------------------



  • 6.  RE: Complaints

    Posted 22-Jun-2018 06:22
    The definitions of a complaint in QSR and ISO 13485:2016 are not quite harmonized. QSR includes "effectiveness" but ISO 13485:2016 does not. ISO 13485:2016 includes "usability" but QSR does not.

    ------------------------------
    Dan O'Leary
    Swanzey NH
    United States
    ------------------------------



  • 7.  RE: Complaints

    Posted 24-Jun-2018 04:37
    ​I found the same requirement in the FDA preamble , so is it right to say that once a complaint is reviewed to be valid only then they need an evaluation for investigation and reportability?

    Section 820.198(a) sets forth the general requirement for

    establishing and maintaining a complaint handling procedure and

    includes a few items that the procedure needs to address. Section

    820.198(b) discusses the initial review and evaluation of the

    complaints in order to determine if complaints are ``valid.'' It is

    important to note that this evaluation is not the same as a complaint

    investigation. The evaluation is performed to determine whether the information is truly a complaint

    or not and to determine whether the complaint needs to be investigated

    or not. If the evaluation decision is not to investigate, the

    justification must be recorded. Section 820.198(c) then describes one

    subset of complaints that must be investigated, but explains that

    duplicative investigations are not necessary. In cases where an

    investigation would be duplicative, a reference to the original

    investigation is an acceptable justification for not conducting a

    second investigation. Section 820.198(d) describes another subset of

    complaints that must be investigated (those that meet the MDR criteria)

    and the information that is necessary in the record of investigation of

    those types of complaints.



    ------------------------------
    RashmiAdelaideAustralia
    ------------------------------



  • 8.  RE: Complaints

    Posted 24-Jun-2018 07:14

    Yes. The correct order a) review for validity, b) evaluate for reportability (which requires investigation), c) evaluate for investigation.

    As an example, a customer complains that the device arrived one week late. This is not a complaint in the sense of 820.198 because it doesn't meet any of the attributes in 820.3(b). The review should result in a "satisfaction compliant" or a "regulatory complaint". These are not mutually exclusive; a complaint could be in both categories.

    A company must take care to perform the review for validity correctly. Information may come into a company through different paths. For example, there may be a customer service function that receives calls or at technical function that answers question on the device use. Review each call for validity as a "regulatory complaint". Lastly, many companies, judging from Warning Letters, don't realize that all warranty claims are "regulatory complaints". They typically have the reliability or durability attribute.



    ------------------------------
    Dan O'Leary
    Swanzey NH
    United States
    ------------------------------