FDA Warning Letters


  1. Warning Letter: No software validation (ucm330805)

    Tags: | | |

    Failure to establish and maintain adequate procedures for implementing corrective and preventive action to include requirements for (1) analyzing quality data to identify existing and potential causes of nonconforming product or other quality problems, using appropriate statistical methodology, where necessary; (2) investigating the cause of nonconformities; (3) identifying actions needed to correct and prevent recurrence of nonconforming product and other quality problems; (4) verifying and validating corrective and preventive actions to ensure that the actions do not adversely affect the products; (5) implementing and recording changes necessary to correct and prevent identified quality problems; and (6) disseminating information related to quality problems and nonconforming product, as required by 21 CFR 820.100(a).
    For example, review of three out of [redacted] Corrective and Preventive Action (CAPA) records revealed:

    a) Q-case #[redacted] concerned [redacted]. Your firm’s investigation identified and processed the corrective actions as a production nonconformance, but statistical methods were not used to quantify the problem. The corrective action of [redacted] was implemented, but validation was not conducted or documented to ensure that the corrective actions was effective and did not adversely affect the product.

    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 >>

  2. Warning Letter: Inadequate software validation (ucm323748)

    Tags: | |

    The Verification Test for the Programming/Verification of code chips (no document control number) dated 4/21-22/2005 is inadequate in that: i. There is no document control number . ii. Step 6 of the verification test requires a repeat of the step [redacted] times, [redacted] for a total of sample size of [redacted]. Instead, the protocol/raw data indicates only [redacted] blank code chips were utilized to conduct the programming/code chip download challenge (i.e., [redacted] chips for each of the [redacted] code chip types). iii. Upon download of the code chip information, there was no verification activity to ensure that the integrity of the performance data, which is unique to each lot code, was not compromised. iv. The raw data associated with the download challenge/programming of the [redacted] chip is missing from the Programming/Verification of Code Chips documents.

    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: Failed to validate computer software (ucm178264)

    Tags: | |

    Failure to validate computer software for its intended use according to an established protocol when computers or automated data processing systems are used as part of production or the quality system as required by 21 CFR 820.70(i).

    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 validate computer software (ucm319510)

    Tags: | |

    Failure to validate computer software for its intended use according to an established protocol, when computers or automated data processing systems are used as part of production or a quality system, according to established procedure, as required by 21 C.F.R. 820.70(i). For example, there are no procedures that describe the qualification and maintenance of the Sorting software for decay calculations on brachytherapy seeds sorted into inventory. There are no software verification and validation requirements defined in your firm’s procedures, and there are no records documenting that the Sorting software is fully validated for its intended uses.

    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: Lack of spreadsheet controls (UCM 311326)

    Tags: | | |

    Specific violations observed during the inspection include, but are not limited, to the following: Your firm has not established appropriate controls designed to assure that laboratory records include all data secured in the course of each test, including graphs, charts, and spectra from laboratory instrumentation, properly identified to show the specific component, drug product container, closure, in-process material, or drug product, and lot tested [21 CFR 211.194 (a)(4)]. Specifically, the inspection revealed that your firm has not established written procedures to control and account for electronically generated worksheets used by analysts to record analytical test results. Analysts in your QC laboratory print an uncontrolled number of worksheets from computers throughout the QC laboratory without supervision.

    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 Provide Staff with Database Access (ucm303979)

    “Acorda Drug Safety staff should have SOPs, work instructions, database access, and training sufficient to ensure adequate surveillance, receipt, evaluation, follow-up, and reporting of adverse event information for all of the firm’s products.”

    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 documentation (ucm293443)

    Tags: | |

    Failure to validate computer software used as a part of production or the quality system for its intended use according to an established protocol, as required by 21 CFR 820.70(i). For example, your firm could not provide any documentation to demonstrate that the software used for the 6111 PCB (Printed Circuit Board) check machine [redacted] was validated for its intended use. Your firm’s Department Manager of Regulatory Affairs stated that the software used for the PCB check machine has not been 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 >>

  8. Warning Letter: Failure to establish procedures (ucm279058)

    Tags: | | |

    Failure to establish and maintain 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).

    Failure to establish and maintain procedures to ensure that all purchased or otherwise received product and services conform to specified requirements, as required by 21 CFR 820.50. For example: Your firm does not have a purchasing control procedure and has not evaluated the contract manufacturer to ensure that manufacturing processes are appropriately validated. In addition, there are no maintenance procedures in place, nor has your firm established procedures to ensure that all purchased or otherwise received product and services conform to specified requirements.

    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: Failure to exercise appropriate controls (ucm279058)

    Tags: | | |

    Your firm has failed to exercise appropriate controls over computer or related systems to assure that changes in master production and control records, or other records, are instituted only by authorized personnel [21 CFR 211.68(b)]. For example: a. Your firm did not put in place requirements for appropriate usernames and passwords to allow appropriate control over data collected by your firm’s computerized systems including UV, IR, HPLC, and GC instruments. All employees in your firm used the same usemame and password. In addition, you did not document the changes made to the software or data stored by the instrument systems. Without proper documentation, you have no assurance of the integrity of the data or the functionality of the software used to determine test results. b. Your firm had no system in place to ensure appropriate backup of electronic raw data and no standard procedure for naming and saving data for retrieval at a later date. In your response, you state that you will maintain backup of electronic raw data and all technicians will have their own user identification (ID) and password.

    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: No contols over computer system (ucm278262)

    Tags: | |

    Your firm has failed to exercise appropriate controls over computer or related systems to assure that the input to and output from the computer or related systems of formulas, other records, or data, are checked for accuracy [21 C.F.R. § 211.68(b)]. For example, your firm’s custom software for your Master Batch Production record, referred to as the “I-131 Database,” has not been validated. This software is responsible for generating the batch production record, performing calculations to produce varying concentrations of drug product, and generating label information for customer vials and lead pigs.

    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 >>