• (919) 844 2494
  • FDA Warning Letters


    1. Warning Letter: Failure to validate (ucm257091)

      Tags: | |

      Failure to establish and maintain adequate procedures for the identification, documentation, validation or where appropriate verification, review, and approval of design changes before their implementation, as required by 21 CFR 820.30(i). For example, your firm was unable to provide a documented design development timeline or work instruction for IMPAX CV 7.8.SU1 of the IMPAX CV 7.8 software design change that resulted in [redacted], approval for Global Release and Delivery on 7/30/2010.

      View the original warnng letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    2. Warning Letter: Failure to validate a change (ucm252701)

      Tags: | |

      Failure to establish and maintain adequate procedures for the identification, documentation, validation or where appropriate verification, review, and approval of design changes before their implementation as required by 21 CFR 820.30(i). For example: Your firm issued an ECN (R9180) on July 7, 2009, which changed the revision of the controller software used in the 300B and 700B model scooters from revision #8 to revision #9. This change increased the motor resistance from [redacted]. There is no documentation to indicate that this change was validated/verified .

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    3. Warning Letter: Failure to demonstrate validation (ucm251784)

      Tags: | |

      Your firm provided “Device Inspection Record” dated October 11, 2007, and Report No. SV-25 Rev 0 “Software Validation Report” dated May 30, 2008 as the only two design validations conducted for the LVT100 design project.

      • Device Inspection Record” and Report No. SV-25 Rev 0 do not reference the serial numbers of the LVT100s used in the validation activities. Therefore, your firm was unable to demonstrate that these design validation activities were performed on initial production units, lots, or batches, or their equivalents. Although the person responsible stated that initial production units were used in both validations, DHRs were not maintained.
      • Your firm did not develop any validation protocols for “Device Inspection Record” and Report No. SV-25 Rev 0.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    4. Warning Letter: Failure to allow FDA access to records (ucm256987)

      Tags: | |

      Failure to permit any authorized FDA employee, at all reasonable times, to access, to copy, and to verify your complaint records, as required by 21 CFR 803.18(d)(3). For example, complaints received after September 1, 2009, and maintained in your File Maker Pro database system, could not be filtered and retrieved for review during your 2010 inspection.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    5. Warning Letter: Failure to validate CAPA effectiveness (ucm250065)

      Tags: | |

      Failure to adequately verify or validate that the corrective and preventive action is effective and does not adversely affect the finished device, as required by 21 CFR 820.100(a)(4). …. design changes were approved, but no validation or verification activity evaluating the effectiveness of the corrective action was performed or documented. Failure to validate an automated data processing system used as part of the quality system, as required by 21 CFR 820.70(i). For example: a. The CPRPlus database used from 2006 to the present to track AEDs and conduct audits of tracked AEDs was not validated.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    6. Warning Letter: Failure to validate (ucm249221)

      Tags: | |

      You have failed to validate with a high degree of assurance, a process where the results cannot be fully verified by subsequent inspection and test, (21 CFR 820.75(a)). Specifically: You have not validated the preparation of the [redacted] bonding solution which is used to bond the [redacted] subassembly, a component of the Trima ACCEL disposable set; You have not validated the preparation of the [redacted] which is used to bond the [redacted]subassembly and [redacted] subassembly, components of the Spectra disposable sets.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    7. Warning Letter: Failure to provide validation (ucm253115)

      Tags: | |

      Failure to establish and maintain a design history file (DHF) for each type of device as required by 21 CFR 820.30(j). For example, the following documentation was not present: a) Formal documented reviews of the design results, b) The identification, validation, or where appropriate verification of design changes and, c) The results of the design validation, including identification of the design, date, and individuals performing the evaluation.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    8. Warning Letter: No documentation of software validation results (ucm247475)

      Tags: | |

      Documentation of all software validation results  for the i.v.STATION was not completed per your firm’s Design Control, (D R&D 33.00) and the Design and Development Planning (P R&D 01.01) procedures. For the [redacted]  software validation test, the output is to verify that the procedure was completed correctly and that the “bag contains the requested volume of the drug.” The test completion date and the volume of the drug were not recorded. Additionally, successful completion of the [redacted]software validation test is to verify “that the syringe contains the required volume of drug.” The completion date and the volume of the drug in the syringe were not recorded, per procedure, for this test as well.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    9. Warning Letter: System not validated (ucm243585)

      Tags: | |

      In addition, we remain concerned that your [redacted] adverse drug experience reporting system has not been fully validated, and may have resulted in inaccurate assessment and untimely submission of 15-day alerts. The current application was released into production on November 9, 2009 using an Interim Validation report (IVR) that is still not final. Critical issues (deviations) identified in your interim validation report during the inspection included the following, but is not limited to: lack of training for your [redacted] support team, incomplete SOPs and Work Instructions, and inaccurate data migration of legacy adverse experience cases from your previous adverse drug experience database, [redacted]. Currently, your [redacted] system does not display accurate clock dates on MedWatch forms for cases which were initially entered in [redacted] and later entered into [redacted] due to the receipt of additional information (follow-up) for the same cases. MedWatch forms printed out from [redacted] for these migrated cases are documented as initial 15-day reports, instead of follow-up reports. Also, the report date in Block B5 of the MedWatch form is the print date, not the actual date of submission. Shortcomings such as these affect the accuracy, reliability, consistency of the system and your firm’s ability to discern invalid or altered electronic records or make timely submissions to FDA as required.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>

    10. Warning Letter: Failure to provide adequate procedures (ucm242439)

      Tags: | |

      Failure to establish and maintain adequate procedures for validating the device design, as required by 21 CFR 820.30(g). For example, you have no documentation of “white box” testing of the embedded device software for the Spine Six device as required by your firm’s design control procedure.

      View the original warning letter.


      Recommended Solutions

      Compliance Training >>

      Recommended Solutions

      ExcelSafe >>

      Recommended Solutions

      Ofni Clinical >>

      Recommended Solutions

      Part 11 Toolkit >>

      Recommended Solutions

      Part 11 Advisor >>

      Recommended Solutions

      MedWatch Reporter >>

      Recommended Solutions

      Computer Validation >>

      Recommended Solutions

      Custom Programming >>

      Recommended Solutions

      Validating MS Excel Spreadsheets >>

      Recommended Solutions

      Access Databases >>