When most people hear the word “recall”, they picture a headline, a Warning Letter, or a product being pulled from shelves. In highly regulated industries, especially biologics, medical devices, and pharmaceuticals, a recall is much more than a public notice. It’s a structured way to protect patients, users, and healthcare providers when a distributed product may be unsafe, ineffective, mislabeled, defective, or otherwise out of compliance. Today we are reviewing the basics of recalls and this intricate, but critical, process. Let’s dive in!
The Food and Drug Administration (FDA) describes recall as a firm’s removal, or correction of a marketed product that FDA considers to violate the laws it administers, and for which the Agency could take legal action. It may be initiated voluntarily by a company, or at the request of the FDA [1] . Basically, if a product already reached the market and a serious enough problem is found, the company may need to act quickly to fix it, remove it, warn customers, or all of the above.
So what is the difference between recall, market withdrawal, and field correction? A “recall” generally involves a product problem serious enough that FDA would consider enforcement action if the firm did not address it. A “market withdrawal” is usually a less serious occurrence where it may involve a minor issue, a business decision, normal stock rotation, or a situation that FDA would not typically treat as grounds for legal action. A “field correction” is an action taken where the product is already located, such as updating labeling, repairing a device, inspecting inventory, or notifying consignees to take a specific action, but does not require product to be returned to the manufacturer.
For medical devices, FDA’s correction and removal framework is especially important. A company may not physically take back a device, but it may still need to report a correction or removal if the action is intended to reduce a health risk or remedy a violation that may present a health risk.
Recall Classifications are grouped into three (3) categories [2] :
Class I: The most serious category. Use of the product could cause serious adverse health consequences or death.
Class II: Use of the product may cause temporary or medically reversible health consequences, or the chance of serious harm is remote.
Class III: Use of the product is not likely to cause adverse health consequences, but the product still violates FDA requirements.
FDA recall expectations do not stand alone. They connect to the quality systems companies use every day to design, manufacture, test, release, distribute, and monitor products.
The following regulations are commonly part of the recall conversation, based upon the associated product:
21 CFR Part 210: focuses on drug Current Good Manufacturing Practice (CGMP) framework which sets the foundation for drug manufacturing expectations and helps frame whether manufacturing controls were adequate.
21 CFR Part 211: focuses on finished pharmaceuticals CGMP which includes requirements for production, laboratory controls, records, investigations, complaints, and distribution practices that often become central during recall decisions.
21 CFR Part 820: focuses on medical device quality management system regulation, this connects recalls to design controls, corrective and preventive action, complaint handling, purchasing controls, production controls, and medical device files.
21 CFR Part 1271: focuses on human cells, tissues, and cellular and tissue-based products (HCT/Ps) which addresses donor eligibility, Current Good Tissue Practice (CGTP), tracking, complaint files, adverse reaction reporting, and other important controls for HCT/Ps.
What happens when a problem is found?
A recall often begins with a signal (such as, but not limited to):
A complaint
Adverse event
Failed test
Out of specification result
Labeling error
Sterility concern
Software defect
Distribution mistake
Supplier issue
Inspection finding
The company then:
1) Evaluates the health hazard
2) Determines the scope of affected lots or units
3) Identifies where product went, develops a recall strategy
4) Communicates with customers
5) Reports to the FDA when required, and completes effectiveness checks to confirm the message reached the right people [3]
The organization basically has to answer these urgent questions: What happened? Who could be impacted? How risky is the issue? and What action will reduce the risk?
During recall, documentation becomes the map. Batch records, medical device files, complaint files, distribution logs, supplier records, investigation reports, and corrective action files help the company determine exactly which products are affected and where they went. Without reliable records, a company may have to recall more products than necessary, or worse, miss affected products entirely.
Recalls are not just regulatory events but are public health events. Whether the product is a biologic, HCT/P, drug, or medical device, the goal is the same [4,5,6,7] : act quickly, communicate clearly, correct the problem, and prevent it from happening again. Companies that build strong quality systems before something goes wrong are better prepared to protect patients, satisfy FDA expectations, and preserve trust when the unexpected happens.
Thanks for joining and see you next time as we continue following industry trends!
Have a question? Contact us here!