By Dr. Ray Nims
In a previous posting, we described the responsibilities of the contract giver (contractee) and the contract acceptor (contractor) in outsourced pharmaceutical quality control testing. Our blog title: "Outsource it, and fuggedaboutit?" somewhat facetiously suggested that the outsourcing of quality control testing does not transfer quality control responsibility from the contract giver to the contract acceptor.
Elizabeth Meyers and I expanded upon this theme in a recent article in BioProcess International. Our conclusion in that article was more direct: “The use, by a pharma organization, of a contract testing lab to fulfill some or all of its Quality Control testing obligations does not absolve the contractee of its overall Quality responsibility of ensuring the safety, purity, identity, efficacy, and potency of its products.”
This point was illustrated nicely in a recent warning letter published on the FDA Website. The name of the firm involved is not important to this discussion. Among the other findings was the following:
“Your firm failed to properly evaluate a contract laboratory to ensure GMP compliance of operations occurring at the contract site.”
The FDA then provided the following detail: "...we are concerned about your firm’s fundamental understanding of what is required by your Quality Unit and the regulatory expectations for a firm that enters into agreements with contract testing laboratories. Although you have agreements with other firms that may delineate specific responsibilities to each party, you are ultimately responsible for the quality of your products and the reliability of test results. Regardless of who tests your products or the agreements in place, you are required to manufacture these products in accordance with section 501(a)(2)(B) of the Act to assure their identity, strength, quality, purity, and safety."
The take-home message from this is that in the outsourcing of quality control testing, responsibility for the outsourced testing is retained by the contract giver. Responsibilities of the contract giver include the following: selecting and qualifying the contract lab, ensuring the suitability of methods used (through qualification, transfer, verification, or validation); putting in place a Quality and business agreement; scheduling and submitting samples (including communicating expectations for sample results); providing in-life guidance; and monitoring of contract lab performance.
There is no denying that fulfilling these responsibilities requires a significant and ongoing effort on the part of the contract giver. In this respect, outsourcing of quality control testing is not so different from doing that testing in-house.
Showing posts with label outsourcing. Show all posts
Showing posts with label outsourcing. Show all posts
Friday, February 25, 2011
Tuesday, October 13, 2009
Outsource it, and fuggedaboutit?
By Ray Nims
Much has been written about the rationales and advantages for outsourcing of manufacturing and/or testing services; about the selection of outsourcing partners; and about the optimization of the pharma/contractor relationship. In any pharma/contractor relationship, there are responsibilities associated with the pharma as well as contractor responsibilities. These include both business as well as compliance responsibilities. The business realities and regulatory expectations associated with the use, by a pharma company, of a contract testing organization must be considered when the decision is made to outsource. A contract testing organization desiring to provide services for a pharmaceutical must be aware of the expectations and responsibilities associated with such a partnership. The optimal and most defensible programs will be those in which the various practices to be described below are formalized within internal Quality Systems, policies, and/or standard operating procedures as well as Quality Agreements.
Responsibilities falling upon the pharmaceutical partner include: 1) the selection of the contract testing lab; 2) commissioning and providing test samples of raw materials and products for method verification (compendial methods) and method qualification (non-compendial methods); 3) instituting of a Quality Agreements, business agreement, and/or confidentiality agreement with the contractor; 4) scheduling and shipping of test samples in accordance with the requirements of the testing lab and the test system; 5) providing in-life guidance and oversight of investigations of unexpected and out of specification results; and 6) ongoing monitoring of the performance of the contract lab and its methods.
Responsibilities primarily falling upon the testing lab include: 1) attaining and maintaining GLP or GMP compliance as appropriate for the intended use of the method; 2) providing assurance that the methods offered will be available to the client over the long term; 3) responsiveness to the sponsoring pharma and adherence to the terms of the Quality and/or business agreements; 4) method validation, verification, and or qualification as appropriate for the intended use of the method; 5) control of reagent, raw material, control, and standard inventory and quality; 6) assuring secure and retrievable data archiving; and 7) retention of staff possessing the appropriate expertise for direction of operators and the methods.
Much has been written about the rationales and advantages for outsourcing of manufacturing and/or testing services; about the selection of outsourcing partners; and about the optimization of the pharma/contractor relationship. In any pharma/contractor relationship, there are responsibilities associated with the pharma as well as contractor responsibilities. These include both business as well as compliance responsibilities. The business realities and regulatory expectations associated with the use, by a pharma company, of a contract testing organization must be considered when the decision is made to outsource. A contract testing organization desiring to provide services for a pharmaceutical must be aware of the expectations and responsibilities associated with such a partnership. The optimal and most defensible programs will be those in which the various practices to be described below are formalized within internal Quality Systems, policies, and/or standard operating procedures as well as Quality Agreements.
Responsibilities falling upon the pharmaceutical partner include: 1) the selection of the contract testing lab; 2) commissioning and providing test samples of raw materials and products for method verification (compendial methods) and method qualification (non-compendial methods); 3) instituting of a Quality Agreements, business agreement, and/or confidentiality agreement with the contractor; 4) scheduling and shipping of test samples in accordance with the requirements of the testing lab and the test system; 5) providing in-life guidance and oversight of investigations of unexpected and out of specification results; and 6) ongoing monitoring of the performance of the contract lab and its methods.
Responsibilities primarily falling upon the testing lab include: 1) attaining and maintaining GLP or GMP compliance as appropriate for the intended use of the method; 2) providing assurance that the methods offered will be available to the client over the long term; 3) responsiveness to the sponsoring pharma and adherence to the terms of the Quality and/or business agreements; 4) method validation, verification, and or qualification as appropriate for the intended use of the method; 5) control of reagent, raw material, control, and standard inventory and quality; 6) assuring secure and retrievable data archiving; and 7) retention of staff possessing the appropriate expertise for direction of operators and the methods.
Tuesday, August 4, 2009
Do You Use Risk Assessments in Auditing?
Audits are a critical component of quality systems, but are they guided by formal assessments of risk to your products? In this world of ICH Q9, can you offer even a semi-quantitative justification for your audit priorities? We have spoken to many people in the industry, and almost all mention a risk assessment being undertaken prior to an audit. But we have not found many people that formalize that risk assessment, or keep it updated from audit to audit. Even fewer communicate their scoring of risk to either their internal clients or the vendor that has been audited.
A new trend in auditing is to use a form of risk assessment both before and after the audit. A popular form is the Failure Modes and Effects Assessment, or FMEA (see, for example, http://www.sre.org/pubs/Mil-Std-1629A.pdf). In a traditional FMEA, risks of failure are identified in a detailed fashion, and scored in three categories related to the failure’s probability, detectability and severity. Scoring is done on a semi-quantitative or relative basis using an arbitrary scale such as 1-10. For an audit, you might use the same categories as they relate to a particular vendor's (or department's) ability to deliver a product or service, failure free. You could organize your FMEA according to the critical quality attributes of the product or service being delivered or according to a list of requirements from a guideline or the CFR's. Your FMEA should receive input from affected departments, and should be used for prioritization of audit items. You should have the FMEA in mind as you conduct your audit, and remember why various items received high prioritization. You may change ratings for probability or detectability based on what you observe. If instead, you confirm your evaluation, you should probe remediations that decrease your firm's primary concern. A remediation that addresses detectability, when the issue was probability, likely won’t mitigate the risk of failure.
When you return from your audit, rescore the FMEA with assessments based on your observations and data that you collected. Make sure that you share your analysis with the stakeholders. And monitor the performance of the vendor until the next audit; the data will help inform your next FMEA.
Do you already use FMEA's in audit preparation and reporting? Let us know your practices.
A new trend in auditing is to use a form of risk assessment both before and after the audit. A popular form is the Failure Modes and Effects Assessment, or FMEA (see, for example, http://www.sre.org/pubs/Mil-Std-1629A.pdf). In a traditional FMEA, risks of failure are identified in a detailed fashion, and scored in three categories related to the failure’s probability, detectability and severity. Scoring is done on a semi-quantitative or relative basis using an arbitrary scale such as 1-10. For an audit, you might use the same categories as they relate to a particular vendor's (or department's) ability to deliver a product or service, failure free. You could organize your FMEA according to the critical quality attributes of the product or service being delivered or according to a list of requirements from a guideline or the CFR's. Your FMEA should receive input from affected departments, and should be used for prioritization of audit items. You should have the FMEA in mind as you conduct your audit, and remember why various items received high prioritization. You may change ratings for probability or detectability based on what you observe. If instead, you confirm your evaluation, you should probe remediations that decrease your firm's primary concern. A remediation that addresses detectability, when the issue was probability, likely won’t mitigate the risk of failure.
When you return from your audit, rescore the FMEA with assessments based on your observations and data that you collected. Make sure that you share your analysis with the stakeholders. And monitor the performance of the vendor until the next audit; the data will help inform your next FMEA.
Do you already use FMEA's in audit preparation and reporting? Let us know your practices.
Subscribe to:
Posts (Atom)