FDA Warning Letters


Page 11 of 25« First...78910111213141516...Last »
  1. Warning Letter: Failure to have procedures (ucm342647)

    Tags: | |

    We address this response below, in relation to each of the noted violations. These violations include, but are not limited to, the following: 1. Failure to adequately validate a process whose results cannot be fully verified by subsequent inspection and test, as required by 21 CFR 820.75(a).

    Your supplier, which was used to fill ampoules was disqualified for this service due to quality issues , but was left on your approved suppliers list because the supplier is still approved for other services. The supplier remained on the approved supplier list for all products, and/or services. There is no method for disqualifying suppliers from providing specific products and/or services. The response dated January 7, 2013 cannot be assessed at this time. Your response states that all supplier evaluation and control procedures will be revised to include an appropriate mechanism to ensure suppliers are qualified and disqualified on a product or service-specific basis. These procedures will also be reviewed to assure compliance with the Quality System Regulation . Additionally, you will also electronically prevent the issuance of purchase orders unless a supplier is approved for a specific product or service.

    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: Failure to validate (ucm337808)

    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). For example, your firm uses custom automatic machines in the needle production process. Your firm stated that it performed software validation for the automatic machines and that the software protocol was tested, but these validation activities were not documented.

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

    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). For example: There is no evidence that validation was completed for the [redacted] software used by your firm to provide the customer with the graphic representation of the flow rate of the device. [redacted], indicated that your firm did not have user requirements, input, or output requirements for the [redacted] software.

    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 implement SOP (ucm336120)

    Tags: | |

    Specifically, your firm has no standard operating procedures implemented to determine if the complaint received represents an MDR reportable event.  Your firm documents complaints in a computer system called [redacted]; however, this practice is inadequate because you failed to implement a standard operating procedure… Failure to implement procedures to ensure all purchased or otherwise received product and services conform to specified requirements, as required by 21 CFR 820.50.  Specifically, your firm failed to define, document, and implement purchasing control procedures to ensure the Nurse Call hardware purchased from your contract manufacturer conforms to your firm’s specified requirements.

    • Failure to establish and maintain adequate procedures to control the design of the device in order to ensure specified design requirements are met, as required by 21 CFR 820.30(a)(1).  For example, your firm failed to establish and maintain written procedures to control the design process, including requirements for design inputs, design outputs, design reviews, design verification/validation, design transfer and design changes for the Nurse Call and Focus devices.

    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: Newer Software not validated (ucm340300)

    Tags: | |

    Failure to establish and maintain procedures for validating the device design to ensure that devices conform to defined user needs and intended uses and shall include testing of production units under actual or simulated use conditions, as required by 21 CFR 820.30(g). For example: Your firm’s design validation procedures outlined in Section 4.6 of the Design Control Procedure, Doc. No. [redacted] do not ensure that the results of the design validation, including identification of the design, methods, the date, and the individuals performing the validation are documented in the Design History File (DHF). Thirty test records from a clinical study conducted as part of the design validation for the AnyView A8 Monitor were reviewed. The results of the design validation, including the identification of the design, the unit tested, the date, and the individuals performing the validation were not documented. In addition, the investigator noted that a software revision had since occurred; however, your firm admitted that the newer software version had not undergone software validation.

    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. 483 from BioQuality, Vol. 14(9): Use of Uncontrolled Excel Spreadsheet

    Tags: | |

    Uncontrolled Excel spreadsheet is used for: • issuance of deviation numbers • tracking deviations to closure • trending deviation data This has resulted in: • CAPAs not always being linked to associated deviations • Deviation priority levels not always being consistent Validation of QC lab software failed to demonstrate adequate security: • Analysts have the ability to overwrite original data • No individual user names and passwords limiting access to the system “


    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: Lack of system control (ucm075766)

    Tags: | | | |

    You failed to establish and maintain process control procedures , including documented instructions and written SOPs for steps in the testing of blood and blood components [21 CFR 606.100(b), 820.70(a)(1)]. Specifically: “a) There are no written procedures describing computer software[redacted] functional requirements or descriptions of functions and there is no computer manual. The database functions as the information management tool used to collect, organize, process, analyze, secure and maintain testing data. “We also note that you have failed to establish an adequate system for authorizing, granting, and rescinding computer access to functions in the [redacted] and adequate computer security provisions to assure data integrity. Current users do not use appropriate access such as passwords and user-id and personnel who have changed jobs still have access to the system.

    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 report significant software changes (ucm339489)

    Tags: | |

    Specifically, the Alcon LenSx Laser System was cleared via K101626, with operating software version 2.02. Your firm has since made multiple revisions to the software, and the LenSx Laser System was running software version 2.13 at the time of the inspection. FDA reviewed your software changes from version 2.02 to version 2.13 and determined that some changes are significant with respect to your original premarket clearance submission and may affect the safety and efficacy of the device. A new 510(k) is required for these changes. … It is your responsibility to report to FDA all significant modifications, including software changes that may change the design or performance and/or affect the safety and efficacy of your devices.

    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: No Corrective Action validation plan (ucm332838)

    Tags: | |

    Your firm had not completed any corrective or preventive actions and had not evaluated the effectiveness of your supplier’s corrective actions… E.    Failure Investigation and Corrective/Preventive Action Form No. 497, dated 08/02/2011, stated that DPM Central Station had a software anomaly which caused the trend data for a patient to be replaced by another patient.  On 05/12/2011, your firm released a product correction letter to the field to correct the issue via a software upgrade.  The CAPA effectiveness verification method was identified as verifying that all documents in the corrective action have been modified.  However, your firm was not able to provide any documentation to demonstrate that the CAPA has been verified for effectiveness and that it does not adversely affect the finished device.

    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: Computers have not been validated (ucm331623)

    Tags: | | |
    • Failure to establish and maintain corrective and preventive action procedures, as required by 21 CFR 820.100(a). For example, there are no written Corrective and Preventive Action procedures.

    • Failure to establish and maintain procedures for receiving, reviewing, and evaluating complaints by a formally designated unit, as required by 21 CFR 820.198(a). For example, there are no written complaint procedures.

    We reviewed your firm’s response and concluded it was not adequate. Although the response states complaint procedures are being established, there is no indication the software to be installed on the service technicians computers has been validated. In addition, a systemic corrective action is not addressed in your response.

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


Page 11 of 25« First...78910111213141516...Last »