By Hal Craig, Trout Creek Consulting, LLC
You just received the urgent call, email, or text that a batch of commercial product made by your company’s outsourced supply chain has failed and, at first glance, the failure isn’t due to an analytical error. What do you do next?
This article provides some insights on how to approach a failed batch for an NDA/ANDA product with an emphasis on finding and resolving the root cause of the failed batch.
First Things First — Wits, Facts, Priorities, And Team
Keep your wits about you, don’t panic, and don’t jump to conclusions. Many of you probably know NASA flight director Gene Kranz’s statement about Apollo 13: “Let’s work the problem, people. Let’s not make things worse by guessing.” This is equally applicable to a failed batch.
Note the facts of the first report that you receive:
These are crucial facts because they will give you a first impression of whether patients are at risk, if a Field Alert Report (FAR) should be filed with the FDA, and if a recall is likely.
Understand your priorities because in a crisis or near-crisis situation there may be decision trade-offs. Each company may have its own view on priorities; here are mine for a failed commercial batch:
Identify the core internal team that is going to investigate and resolve this problem. Clearly, quality assurance, regulatory, and technical operations/supply chain should be involved. Depending on the failure metric, R&D will be, too. If the failure involves distributed product or might cause a drug shortage, then commercial, medical affairs, finance, legal, and other functions might also be on the team. Pick a team leader who will drive the investigation, resolution, cross-functional/cross-organizational communication, and provide cogent communication with your executive team.
Include outsourced partners on the team. While it does depend on the failure metric, assume that the drug product CMO will be on the team investigating the root cause. Other suppliers may also be involved in the investigation and resolution; the third party logistics firm and distributors will be involved in recalls and other customer/patient-facing actions. Be sure to understand inventory levels and whether forecasts and purchase orders need adjustment.
Have regular team update calls, weekly if not daily. Even an update saying “we’re on track to have results from task X tomorrow morning” is better than no report.
Resist the temptation to play the “blame game.” You need your supply chain partners to help find and resolve the cause of the batch failure as well as to grow your business. If indeed the root cause was negligence, willful misconduct, or another cGMP violation, the provisions of the supply and quality agreements will cover this in due time.
Regulatory requirements1 somewhat depend on whether the failed batch has been distributed. Briefly, if a failed NDA or ANDA batch has been distributed, or if the investigation into the failure of an undistributed batch indicates a failure of one or more distributed batches, then according to 21 CFR 314.81(b)(1) and 314.98(b), a FAR must be submitted to the FDA within three working days of receiving the following information for a distributed drug product:
Note that the NDA/ANDA applicant is responsible for submitting the FAR, even in an outsourced supply chain.
Along with FAR requirements, it is worth noting recall classifications:2
According to 21 CFR 211.192, “the failure of a batch…to meet any of its specifications shall be thoroughly investigated, whether or not the batch has already been distributed. The investigation shall extend to other batches…that may have been associated with the specific failure...” Further, 21 CFR 211.198 states “Where an investigation under 211.192 is not conducted, the written record shall include…the name of the responsible person making such a determination.” There are regulatory requirements and accountability associated with investigations.
Solving The Problem
A batch can be failed for many reasons or symptoms. Here is a partial list of symptoms derived from the FDA’s recall database: contamination (microbial or other type); cGMP deficiencies; particulates; incorrect package label or improper product in the package; failed stability specification; out of temperature storage; cracked or broken capsules; potency; and adverse events. Some symptoms have readily definable causes and fixes. Others are not so definable and could lead to a new design space or a new supplier if achieving the desired level of quality is not possible.
Here is one approach for finding more challenging root causes of failed drug product, drug substance, or raw material batches:
Once the root cause and its resolution (CAPA) have been found and demonstrated, they need to be communicated and incorporated into everyday production. Some root causes, such as the incorrect installation of a new sieving screen, are relatively easy to correct through training and having an additional person check the installation. Other root causes, such as the lack of a sufficiently robust quality culture at a supplier, are clearly more difficult to fix. Proactive supplier auditing, contracts with change control and related provisions, a quality risk management process, and engaging key suppliers for mutual understanding of the critical quality attributes to be achieved at each supplier are important tools to prevent failed batches.
Remember to work the problem and not go into an investigation with a “Who is to blame and who is going to pay for this?” attitude. The goal is to supply life-improving medicines to patients and to keep your business on track. To do this, the drug marketer needs a transparent and cooperative supply chain that will quickly respond to issues and deliver. Focus on finding the root cause of the batch failure, the resolution of that root cause, and helping patients. Once the facts are known, let the provisions of the various contracts between the drug marketer and its suppliers govern.
About The Author:
Hal Craig is the founder of Trout Creek Consulting, LLC, a strategy and life science supply chain consultancy focused on solving CMC, outsourcing, strategy, and technical challenges. Clients include venture-backed, family-owned, private equity-owned, and publicly traded companies. Mr. Craig serves on the Physical Sciences Investment Advisory Committee of Ben Franklin Technology Partners of Southeastern Pennsylvania. He has a BSChE from the University of California, Berkeley and an MBA from the University of Michigan. He can be reached at firstname.lastname@example.org.