BACPAC II.doc

Bulk Actives Postapproval Changes: BACPAC IISource: Pharmaceutical TechnologyBy: John Curran, Wendy Mavroudakis, Dave RidgeOriginally published: November 2, 2005 The US Food and Drug Administration has issued a Guidance for Industry entitled BACPAC I: Intermediates in Drug Substance Synthesis (1) but has yet to issue a companion document that would cover postapproval changes from the final intermediate to the active pharmaceutical ingredient (API). Because of the significant value in a guidance that will provide clarification as well as regulatory relief for late-stage API postapproval changes, the Pharmaceutical Research and Manufacturers of Americas (PhRMAs) API Technical Group assembled a working group to compile industry recommendations for consideration by FDA in the development of BACPAC II, as it had done for BACPAC I (2). The US regulatory environment for chemistry, manufacturing, and control (CMC) issues is changing rapidly, driven largely by FDAs new Pharmaceutical Quality for the Twenty-First Century initiative. Under this system, changes to API processes will be assessed on the basis of risk with regards to concepts of quality-by-design (e.g., design space, critical process parameters, process analytical technology PAT) that are used to develop robust API manufacturing processes. Accordingly, it is understood that a future FDA guidance addressing both API documentation for original new drug applications and postapproval changes might be appropriate under the new system. For some period of time, however, there will be many legacy products on the market for which more traditional development principles were followed. For such products, the present discussion would be applicable in terms of defining potential areas for regulatory clarification and relief. The PhRMA BACPAC II Working Group identified the following important concepts, which industry hopes FDA will consider during the development of the new BACPAC II guidance: A decision-tree approach would allow for an easy-to-follow pathway to decision-making in determining a filing category based on a logical assessment of risk. Changes can be categorized as site changes, specification changes, and process changes. A quality evaluation pre- and postchange is required for an adequate assessment of risk. For any change in which a comparable or higher level of quality cannot be ensured, a prior approval supplement (PAS) is required. The effect of changes in analytical methods can be adequately assessed using current scientific principles, including validation. Risk assessment should be considered in determining filing categories. The proposals made herein identify but limit those changes that are considered to have a significant potential to adversely affect quality, thus requiring a PAS. The last true solution (LTS) should be used as an additional point in the assessment of potential risk to API quality. To show how these concepts can be applied, the PhRMA Working Group has developed a proposed BACPAC II decision tree and has worked with a specifications and BACPAC Working Group operating under the direction of the Product Quality Research Institute (PQRI). The PQRI group also has developed a BACPAC II proposal that is fundamentally aligned with this position paper. PhRMA believes that this decision tree represents an approach that will provide clarification and regulatory relief for industry while respecting the concept that the later in the process that a change occurs, the more significant the potential for adverse impact. Nonetheless, it is also reasonable to believe that the proposals contained herein representing late-stage regulatory relief can be achieved without compromising quality or public safety, particularly because all changes will require data to demonstrate that there is no adverse effect. The PhRMA Working Group recommendations focus on the determination of the filing category. It is fully recognized that ultimately BACPAC II, as in BACPAC I, also will contain guidance for supporting data to be included in the regulatory submissions. Although the latter is not discussed in detail in this article, the group requests that FDA also consider the nature and potential influence of the change in determining its recommendations for supporting data. In general, PhRMA believes that, other than in cases of changes with high potential risk (e.g., prior-approval changes), drug product data should not be required in support of the regulatory filing for API changes. Acceptance of this point lies in the concept that all relevant API (or any postfinal intermediate) quality standards be identified and included in pre- and postchange quality comparisons. As we discuss, such relevant quality standards may extend beyond regulatory specifications and must be carefully assessed on a case-by-case basis. Background In the late 1990s, FDA began to draft a guidance document to cover postapproval changes to API manufacturing. In response to that initiative, a PhRMA BACPAC Working Group published its recommendations for FDA consideration in its development of a single guidance document for bulk active postapproval changes (BACPAC) (2). These recommendations included an assessment of changes based on the potential influence of the change on the quality of the final API. Factors such as where in the API synthesis the change occurred were taken into account. This recommendation used a decision tree as the device for determining filing status for changes and introduced the concept of the last true solution as a key factor in assessing potential risk and hence filing requirements. While drafting its BACPAC guidance, FDA released a guidance for postapproval changes (3), which included the scientifically sound premise of establishing filing requirements for a change based on the potential for an adverse effect on the identity, strength, quality, purity, or potency of the product. This Change guidance used the final intermediate (i.e., the last compound synthesized before the reaction that produces the drug substance) as a key point in assessing API risk and filing requirements. Subsequently, FDA revised its guidance for postapproval changes (4), hereafter referred to as the Changes guidance. Nonetheless, PhRMA noted several provisions in that guidance lacked validity when applied broadly; for example, that a PAS is required for: a change in the route of synthesis of a drug substance; any process change made after the final intermediate processing step in drug substance manufacture; a new regulatory analytical method; relaxing or deleting specifications.In February 2001, FDA released its BACPAC I guidance (1), which provided guidance on the filing categories and recommended supporting data for API changes up to and including the manufacture of the final intermediate. Several general considerations were cited in that document that supported opportunities for regulatory relief. For example, it was recognized that the risk of adverse change is generally acknowledged to be greater when a modification occurs near the end of a drug substance manufacturing process rather than the beginning. Accordingly, under BACPAC I, it is allowable to file certain early-stage synthesis changes as changes being effected in 30 days (CBE-30), rather than as PAS. BACPAC I also indicated that the final intermediate was chosen as the break point in this attempt to categorize risk because . physical properties of the drug substance will not be affected by changes made up to that point. PhRMA proposes herein, as it did in its 1998 article, that physical properties of the drug substance will not be affected by changes before the last true solution (i.e., the processing point at which the drug substance is completely dissolved for the last time), assuming chemical comparability before and after the change. Therefore, this new break point offers a logical and scientifically sound basis for an assessment of potential risk further downstream from the final intermediate and, therefore, offers an additional opportunity for further regulatory relief. This point will be key to the following discussion about process changes. In addition, we present proposals related to site and specification changes that provide clarity to many everyday situations that are not addressed clearly in the current guidance. Discussion of the decision treeThe PhRMA Working Group proposals for BACPAC II relate to three elements of the decision tree: site changes, specification changes, and synthesis or process changes. Site changes. The provisions for reporting API manufacturing site changes for the steps from the final intermediate through the finished API, as contained in the Changes guidance, are appropriate for inclusion into a BACPAC II guidance. It is appropriate to report manufacturing site changes in a CBE-30 supplement. Only changes involving sites that have not been FDA-qualified (i.e., those have not been FDA-inspected or are found not to be CGMP-compliant) should require a PAS. The assumption is that the manufacturing-site change does not also involve changes to the manufacturing process or specifications. If multiple changes are involved, then the filing should be in accordance with the most restrictive individual changes, as is current practice. Figure 1: The site changes element of the proposed decision tree. Abbreviations: PAS denotes prior approval supplement, and CBE-30 denotes changes-being-effected in 30 days.The only deviation from the Changes guidance lies in a site change for analytical testing. If a CGMP-compliant site has transferred methods in accordance with agency guidelines, including cross validation, then both a science-based assessment and a risk assessment would suggest that the potential for adverse impact is minimal and that such a change should be handled as an annual report rather than as a CBE-30. Figure 1 shows the site change section of the proposed decision tree, and Table I compares current and proposed site-change requirements. Specification changes. BACPAC II will cover all changes to the final intermediate specification, specifications for starting materials, reagents, raw materials, and solvents used in the process after the final intermediate and the finished API specification. Specification is used in this article in a broad sense, in accordance with the FDA definition, to include tests, analytical procedures, and acceptance criteria. As in BACPAC I, the authors encourage FDA to include the changes to controls of critical steps (e.g., test for monitoring critical reaction progress or for control of critical reaction events) in the scope of this section of the guidance. Although FDAs Changes document provides guidance in this area, the attempt to address the wide spectrum of raw material, drug substance, and drug product issues in a single document renders that document cumbersome. PhRMA believes that the proposed decision tree provides needed clarification, while, in certain cases, providing for a lesser reporting burden without the potential to negatively affect API quality assurance. Figure 2: The specification changes element of the proposed decision tree. Abbreviations: PAS denotes prior approval supplement, and CBE-30 denotes changes-being-effected in 30 days.In the proposed decision tree for specifications (see Figure 2), the first decision point is whether the change is being made to comply with a change in compendial requirements. We propose that all changes made to comply with an officially recognized compendium can be made in an annual report. Although this represents a deviation from the Changes guidance, it does correlate with the FDAs position as presented in the Federal Register notice (5) regarding enforcement discretion on this issue. The second decision point is highly critical. It calls for determining whether the change can provide the same or better quality assurance for the intended purpose. If such ensurance cannot be demonstrated and clearly documented, then the change should be submitted in a PAS. This is consistent with the current Changes guidance that correctly categorizes the risk of these changes as having a substantial potential to have an adverse effect on quality. The next decision point focuses on changes to an alternate analytical method that provides same or better quality assurance. In accord with current guidance, such changes can be filed in an annual report. Proceeding through the decision tree, one must next assess whether the change is to an analytical method only with no change to acceptance criteria. If so, one looks at the risk associated with the change to determine the filing mechanism. Examples of low-risk changes include reasonable changes in the operating conditions or minor modifications in operating detail such as sample preparation or the determination of system suitability. These changes are generally reported to ensure alignment of the registration dossier with current operating practice, which may have been altered, within acceptable limits, to account for factors such as column-to-column or equipment variability over time. Therefore, PhRMA proposes these changes be reported in an annual report. If the change is beyond one of minor method detail, it must be determined if the method change involves the regulatory analytical method for the API. This criterion recognizes that changes to the final API regulatory analytical methods present somewhat greater risk than changes to analytical methods for the crude API, final intermediate, solvents, starting materials, and reagents. Therefore, PhRMA recommends that changes to the API regulatory analytical procedures be placed in the CBE-30 category and that other analytical method changes be placed in the CBE filing category. It must be remembered that all such changes have already passed the criterion of same or increased level of quality assurance. This differentiation provides for a greater FDA oversight of changes to API regulatory analytical procedures by allowing time to review at least summary data and yet allowing for efficient implementation of equivalent or superior analytical methods. This type of regulatory relief would greatly assist in allowing industry to modernize analytical methods without the unnecessary burden of a PAS as currently mandated by the Changes guidance. On the other major branch of the decision tree, one must analyze specification changes other than analytical method changes. First, one must address cases in which the specification change involves tightening or adding an acceptance criterion. These changes may be the result of improved process capability resulting in minimal risk and should be allowed in an annual report. As with all method and specification changes, it is expected that validation of new methods and any proposed new acceptance limits would be consistent with current guidance (e.g., International Conference on Harmonization ICH). Other cases may not involve tightening or adding specifications, and potential impact on API quality should be addressed. Such cases may involve the elimination of certain tests. Elimination of tests may, on initial glance, seem to fail the same or increased level of quality assurance criterion, but there are numerous examples in which eliminating a test does not affect quality assurance; for instance, the removal of a residual solvent test for a solvent no longer used or the elimination of a redundant test as in the case of multiple identification tests. Another example is the revising (widening or shifting) of acceptance criteria associated with an improved analytical method (e.g., thin-layer chromatography to high-performance liquid chromatography, in which assay methods may not have the same acceptance criteria). If such changes involve the finished API specification, then the change should be filed as a CBE-30. Specification changes for the final intermediate and other materials would warrant a CBE filing. Again, this approach would allow FDA time to review summary data for changes to the API specification and ensure that the same or increased level of quality assurance has been demonstrated. The proposed decision tree provides a logical path for determining a filing category for any specification change. To supplement this tool, Table I provides some examples of these types of changes and their filing categories under the current Changes guidance and the proposed flowchart for easy comparison. PhRMA believes there is opportunity for FDA to provide regulatory relief in changes to specifications at and after the final intermediate by limiting the requirement for PAS to changes that are not demonstrated to provide the same or increased level of quality assurance. This regulatory relief would allow industry to easily implement improved analytical methodology and modernize specifications, thus improving overall product quality assurance. Figure 3: The synthesis or process changes element of the proposed decision tree. Abbreviations: PAS denotes prior approval supplement, and CBE-30 denotes changes-being-effected in 30 days.Synthesis and process changes. PhRMA acknowledges the general considerations presented in BACPAC I such as the risk for adverse effects increases as changes are made later in the process as opposed to earlier. We also understand that this is the basis for the provision in the Changes guidance that requires a PAS for any process change made after the final intermediate processing step in the drug substance manufacture. Understandably, late-stage changes offer fewer opportunities to remove or reduce impurities by means of purification and also present the potential to introduce changes in the APIs physical properties. Nonetheless, PhRMA believes that this is an overly conservative position,