This article is part 2 of a two-part series specific to complaint investigation requirements as specified in 21 CFR 820.198 (http://bit.ly/21CFR820198) of FDA QSR. This second part explains how to perform a complaint investigation and provides a complaint investigation case study.
Last week’s blog reviewed the requirements for a complaint investigation, while this blog includes the following information on how to conduct an investigation:h
- How thorough should your investigation be?
- Investigation Methods
- Verification of the Cause
- Documenting Your Investigation
- Complaint Investigation Case Study
How thorough should your investigation be?
The depth of investigation should be appropriate to importance of the complaint. If a previous complaint of similar nature has already been investigated, the investigation may only gather enough information to verify that complaint has the same root cause. However, if a complaint involves an adverse event (i.e., is reportable under 21 CFR 803), then additional information needs to be recorded in the complaint record as per 21 CFR 820.198d:
- Does the device fail to meet specifications?
- Was the device used for treatment or diagnosis?
- What was the relationship, if any, between the device and the reported event?
If the person gathering information from the complainant cannot immediately identify a cause code, or the incident involves a serious injury or death, then it is important to gather as much information as possible. Typically, the complainant will be asked to return the device to determine if the device malfunctioned.
A complaint investigation is not any different from any investigation you perform for a CAPA. The most critical first step is to determine the cause of the complaint. In order to determine the cause, you need to sample additional records and inspect the device if it is available. If the device is not available, you might also look at other product from the same lot that remains in inventory. The following article I wrote suggests seven ways to investigate a complaint when a device is not returned: http://bit.ly/DeviceNotReturned.
One of the methods described in the article above is a Ishikawa Diagram or “Fishbone Diagram.” This is one of the five root cause analysis tools that I teach in my CAPA webinar (http://bit.ly/enKapCAPAwebinar). Ishikawa Diagrams are an ideal tool for root cause analysis if you have no idea what the cause of the complaint is, because this tool provides a systematic process for narrowing down the potential causes, to the narrow few that are most likely. You are not required to use this tool, but you should describe in your complaint record what type of root cause analysis was performed.
Verification of Cause
Once you have identified the root cause, or at least narrowed your list to the most likely causes, you should then verify that the cause will actually result in the observed malfunction by recreating the scenario if possible. Ideally, you should be able to simulate the event that resulted in the complaint and demonstrate that you can reproduce the problem. This is important, because if you cannot verify the cause of a device malfunction, then you will have difficulty verifying effectiveness of corrective actions for an infrequent complaint.
Documenting Your Investigation
There is no specific format for the way a complaint investigation is documented, but most complaint records have a small section on the complaint form that allows them to write a short paragraph summarizing the investigation and the results. Unfortunately, most of the spaces provided on forms are completely inadequate for the amount of information that should be recorded. Therefore, the best approach is often to write, “See attached complaint investigation.” This is especially true if the complaint is reportable (i.e., requires MDR under 21 CFR 803). Good documentation is quantitative and specific. You need to identify which records were sampled as part of the investigation, and you should demonstrate that you have expanded your initial search to determine if the problem exists in multiple production lots of the same product code, multiple product codes within the same product family and any other product families that may use similar raw materials, design features, equipment, testing methods or procedures.
Complaint Investigation Case Study
If your company manufactures cast orthopedic implants for the knee and you receive a complaint for an implant that has a small imperfection in the bearing surface of the femoral implant, you may need to perform an investigation–especially if this has not occurred previously. You should request a return of the implant for inspection to verify that the imperfection is nonconforming and not just a cosmetic defect.
Your investigation should include review of the lot history record for the entire lot of implants–as well as any other parts that they may have been cast at the same time. All the process conditions identified throughout the manufacturing process should be compared to the validated process parameters. Special attention should be given to the inspection results that were recorded for the castings (i.e., radiographic inspection, fluorescent penetrant inspection and metallurgical inspection). Ideally, these inspection methods should be repeated for 100% of the production lot to ensure that the inspection results meet the acceptance criteria. Documentation of the investigation should include copies of all records that were reviewed and photos if visual inspections were repeated.
If you are interested in learning more about complaint handling, you might be interested in downloading the webinar that Medical Device Academy recorded last year for complaint handling and vigilance reporting (http://bit.ly/Complaint-Webinar-Landing). Leo Lagrotte, a former FDA investigator that works on our team as a consultant, also recorded a webinar related to CAPA and complaint investigations (http://bit.ly/FDACAPA). We can also help you one-on-one with a current complaint investigation you are conducting. Please don’t hesitate to contact me. Mobile: 802.281.4381 or email@example.com.