FDA drug recall lookup: reading a Class I/II/III notice and pharmacy triage

A community pharmacy receives a recall notice for a heparin product. The notice names a specific National Drug Code, a single lot, and a confirmed endotoxin out-of-specification result. Two aisles over, the same pharmacy stocked a different NDC of heparin from the same manufacturer — unaffected, because the recall is lot- and package-specific. A third product on the shelf, an over-the-counter cream, carries a Class I notice for confirmed microbial contamination, but only one lot is implicated. Whether the pharmacy quarantines one bottle, sweeps the entire shelf, or pulls patient-level dispensing records depends entirely on reading four fields in the right order: classification, status, the lot/NDC (code_info) block, and the reason. Misread any one of them and the pharmacy either under-responds to a Class I hazard or over-responds to a Class III labeling defect.

The FDA Enforcement Report is the authoritative public record of recalls the agency monitors, and it is the document a pharmacy triages against. Reading it well means reading each field in order, knowing which field answers the urgency question (classification), which answers the action question (status), which answers the is-my-stock-affected question (lot and NDC), and which answers the did-my-patients-get-this question (distribution scope and dispensing history). This article is a field-by-field triage workflow for the Enforcement Report, written for community and health-system pharmacy operations, pharmacy benefit and operations teams, and manufacturer market-access groups who must respond when their product appears on the list. It is not a treatment advisory. For the aggregate landscape — recall volume by year, the top recalling firms, and the reason-category breakdown — see the companion drug recalls by the numbers analysis; this article stays on the operational read a pharmacy performs at the moment a notice arrives.

The legal framework: recalls are firm-initiated, then FDA-classified

The first thing to understand about a recall notice is that FDA does not, in almost any case, "order" it. A recall is defined under 21 CFR Part 7 as a firm's removal or correction of a marketed product that FDA considers violative — and almost without exception the recalling firm initiates it; across the enforcement record, drug recalls are overwhelmingly firm-initiated and voluntary under 21 CFR 7.46. When a distributed product presents a risk of illness or injury and the firm has not acted, FDA may request a recall under 21 CFR 7.45, and its mandatory recall authority is narrow and statute-specific — biological products, medical devices, infant formula, human tissue, tobacco, and food (under FSMA) — not a general power to order the recall of a human drug. FDA's role after the firm acts is to classify the recall to indicate the relative degree of health hazard, and that classification — Class I, II, or III — is the field a pharmacy triages on first.

This sequencing matters operationally because classification frequently lags the recall itself. Firms often initiate a voluntary recall and issue their own public warning before FDA has completed its hazard assessment, and FDA now posts some recalls to the Enforcement Report under a "Not Yet Classified" status rather than waiting for classification to finish. A pharmacy that only acts once a Class I label appears may therefore be late. The triage discipline is to treat an unclassified notice with a serious-sounding reason (microbial contamination, undeclared active ingredient, incorrect active) as if it were Class I until FDA confirms otherwise.

Field 1 — Classification: Class I, II, or III answers the urgency question

Classification is the relative health-hazard rating FDA assigns under 21 CFR 7.3, and it is the field that sets triage tempo. In the 17,683-event enforcement dataset analyzed here, the distribution is:

The operational asymmetry is that Class I is the smallest bucket but the only one that demands same-day, patient-level response. FDA's definitions are precise and worth quoting directly: Class I is "a situation in which there is a reasonable probability that the use of, or exposure to, a violative product will cause serious adverse health consequences or death"; Class II is exposure that "may cause temporary or medically reversible adverse health consequences or where the probability of serious adverse health consequences is remote"; Class III is use "not likely to cause adverse health consequences." A pharmacy that treats all recalls the same will either exhaust its staff on Class III labeling defects or, worse, under-escalate a Class I contamination. Class I triggers the full playbook — immediate quarantine, physical segregation, patient identification, and prescriber notification; Class III typically triggers a return-to-distributor workflow only.

A second field tracks depth of recall — how far into the distribution chain the correction must reach — and it generally tracks classification. FDA's recall strategy for each event specifies a level: consumer or user level (the product may have reached patients), retail level (pharmacy or store shelves), or wholesale level (distribution above the pharmacy). A Class I recall is generally conducted at the consumer level, which is what obligates patient outreach; a Class II recall is generally retail-level, meaning the action is to pull stock and return it without necessarily reaching back to patients who already received it. Reading the classification and the depth together tells the pharmacy whether its duty stops at the shelf (retail or wholesale depth) or extends to everyone dispensed the product (consumer depth). A recall conducted only at wholesale depth may not require a community pharmacy to act at all if it caught the product upstream of the dispensing shelf.

Field 2 — Status: Ongoing, Completed, or Terminated answers the action question

Status tells the pharmacy whether the recall is live or closed, and therefore whether it owes an action. The enforcement data carries three values:

The actionable subset is the 2,453 Ongoing events, and within those, the 208 that are simultaneously Class I and Ongoing are the highest-priority notices in the entire dataset — serious health hazard, still live, product still potentially in the channel. A pharmacy monitoring cadence that filters to Ongoing + Class I will surface the recalls that genuinely require same-day response and will not be distracted by the large volume of long-terminated historical records. A Terminated record is closed for operational purposes; the pharmacy's only duty on a terminated record is to confirm none of the affected lots remain on its shelves or in automated dispensing cabinets from a prior sweep.

A common confusion is the distinction between a recall and a market withdrawal. A market withdrawal is a firm's removal of a product with a minor violation that would not be subject to FDA legal action — it does not appear as a classified recall and does not carry the same triage weight. Reading a notice carefully enough to distinguish "recall" from "market withdrawal" prevents over-response.

Field 3 — The code_info block: lot numbers and NDCs answer the is-my-stock-affected question

This is the field that determines whether the recall touches the pharmacy at all, and it is the field pharmacies are least equipped to act on. The code_info block in an enforcement record identifies the exact units affected — by lot number, expiration date, and often NDC. A typical Class I entry reads "Lot # N008235, Exp 8/31/2024"; another reads "ALL LOTS, exp 12/31/2027." The triage step is to match the recalled lots against the pharmacy's own inventory and dispensing records.

The operational gap is that most dispensing pharmacies are not required to document the lot number on the label given to a patient, which means a pharmacy that dispensed the recalled product often cannot, from its own records, determine which patients received the affected lot. The recall notice is lot-specific; the pharmacy's patient-level trail frequently is not. This is why the triage workflow depends on lot capture upstream — inventory systems, automated dispensing cabinet transactions, and barcode scans that record lot and expiration at receiving and dispensing. Industry guidance from ASHP and requirements under USP 797 (effective November 1, 2023) and several state boards of pharmacy push NDC, lot, and expiration logging into IV workflow systems, in part so that recalls can be traced to the patient. Two-dimensional barcodes such as GS1 DataMatrix encode lot and expiration directly and make that capture automatic; older linear barcodes carry only the NDC and leave the lot to manual entry.

The practical reading rule: a notice that names specific lots requires a targeted shelf sweep and a lot-matched patient query; a notice that says "ALL LOTS" requires a full product sweep and outreach to every patient dispensed the product within the notice's date range. The NDC field narrows the sweep further — when the recalled NDC differs from the NDC the pharmacy stocks, the pharmacy is unaffected, which is the single most common reason a recalled product never reached a given pharmacy's shelves.

Field 4 — Reason: the clinical signal behind the classification

The reason field explains why the product is violative, and it shapes the clinical message the pharmacy sends to patients and prescribers. Common reasons and their triage implications:

The reason is what a pharmacist translates into patient-facing language. "Endotoxin out of specification in an injectable" is a stop-use, contact-your-prescriber message; "label mix-up between two strengths" is a verify-your-bottle message.

Field 5 — Distribution pattern and dates: scope and timing

The distribution_pattern field names where the recalled product was distributed (e.g., "Nationwide in the USA," "USA Nationwide and Bahamas," or a list of states). This scopes the patient-outreach effort and tells a pharmacy whether its region is even in the recall's footprint. The date fields anchor the event: recall_initiation_date (when the firm began the recall), report_date (when it posted to the Enforcement Report), and center_classification_date (when FDA classified it). A notice with an initiation date months before its classification date is a reminder that the recall was live — and the product potentially dispensable — during the gap; a pharmacy checking only classified notices may have dispensed affected product in the interim.

How a pharmacy learns: the notification field

The initial_firm_notification field records how the recalling firm first told consignees about the recall. In the data analyzed here, 9,007 events used a Letter, 2,706 a Telephone call, 2,571 a Press Release, 1,725 a multi-channel combination (email, fax, letter, press release, telephone, or visit), and 1,181 an E-Mail. The practical implication for a pharmacy is that recall notices arrive through multiple, redundant channels — distributor communications, manufacturer letters, FDA alerts, and news media — and best-practice pharmacy operations subscribe to more than one so that a single missed channel does not become a missed recall. A procurement or drug-information line that consolidates these incoming notices is the intake point of the triage workflow.

Worked examples: how the fields drive the triage response

These are real records from the enforcement data analyzed for this article.

Example 1 — Class I, Ongoing, sterile-product contamination: Baxter heparin

Classification Class I, status Ongoing, product heparin in 0.9% sodium chloride, 2 units/mL, 1,000 mL, NDC 0338-0433-04, lot N008235, expiration 8/31/2024, reason "microbial contamination of sterile products; out of limit results obtained for endotoxin testing," distribution nationwide, notified by Letter. The triage response is full: quarantine the specific NDC and lot from all storage locations including IV rooms and automated dispensing cabinets, identify every patient or unit that received an infusion from lot N008235, and notify prescribers of the endotoxin finding. The lot specificity means heparin from other lots or other NDCs is not implicated and need not be disrupted.

Example 2 — Class I, Ongoing, non-sterile microbial contamination: MG217 cream

Classification Class I, status Ongoing, product MG217 Multi-Symptom cream (colloidal oatmeal 2%), lot 1024088, expiration 11/30/2026, reason confirmed Staphylococcus aureus, distribution USA nationwide and Bahamas, notified by Letter. This is an over-the-counter product, which complicates patient identification — the pharmacy has no prescription trail for an OTC purchase. The triage response is shelf sweep of the named lot, point-of-sale or signage notification for consumers who may have purchased it, and removal from any stock bottles used in compounding. Other lots and other MG217 presentations are unaffected.

Example 3 — Class I, Ongoing, undeclared actives, ALL LOTS: Mojo Max Fusion

Classification Class I, status Ongoing, product "Mojo Max Fusion XXX," code info ALL LOTS, expiration 12/31/2027, reason marketed without an approved NDA/ANDA with FDA analysis revealing undeclared sildenafil (13.1 mg/capsule) and tadalafil (13.8 mg/capsule), distribution U.S. nationwide, notified by E-Mail. The "ALL LOTS" scope converts this into a full product sweep rather than a lot-targeted one, and the undeclared PDE5 inhibitor reason elevates the drug-interaction risk — particularly with nitrates — making consumer-facing outreach the priority. Products marketed without an approved application are a recurring Class I pattern and typically warrant public-health-scale notification rather than pharmacy-by-pharmacy reconciliation.

The triage workflow, in order

1. Read classification first. Class I = immediate, patient-level playbook; Class II = quarantine and return with preventive outreach; Class III = routine return. Treat an unclassified notice with a serious reason as Class I until confirmed.
2. Filter by status. Act on Ongoing notices; archive Terminated ones. The intersection of Class I and Ongoing is the highest-priority set.
3. Match the code_info block to inventory. Pull the named lots and NDCs from shelves, automated dispensing cabinets, floor stock, code carts, kits, and any compounding stock. Use "ALL LOTS" notices to sweep the entire product.
4. Match lots to dispensing records. Identify patients who received the affected NDC and lot; where lot-level data is missing, identify all patients dispensed the product within the notice's date window.
5. Translate the reason into a clinical message. Determine whether patient outreach should be stop-use-and-contact-prescriber, verify-your-bottle, or routine return.
6. Scope by distribution pattern and dates. Confirm the pharmacy's region is in the recall's footprint and check whether affected product could have been dispensed between initiation and classification.
7. Quarantine with full identification. Segregate recalled product with name, NDC, lot, expiration, recall number, and effective date; mark it not for patient use; and prepare it for return to the distributor.
8. Recheck incoming purchases. Continue to monitor receiving for a defined period — two to four weeks is standard — so that an affected lot already in transit does not re-enter the shelves after the sweep.
9. Document the response. Record what was quarantined, the count, the patients notified, and the communication, for inspection and for the pharmacy and therapeutics committee where applicable.
10. Subscribe to redundant notification channels. Ensure recall notices are not missed because a single distributor or manufacturer communication failed.

What operations and access teams should monitor

For pharmacy operations, the discipline is a standing triage process with a single intake point, a lot-capturing inventory system, and a documented patient-outreach protocol scaled to classification. The recurring failure mode is not missing the notice — notices arrive through multiple channels — but being unable to match the recalled lot to the patient because lot data was never captured at dispense. Investing in barcode-driven lot capture is the single highest-leverage fix for recall readiness. For manufacturer market-access and quality teams, an Ongoing Class I notice on the firm's own product is a commercial-operations event as much as a quality event: it triggers field communications, specialty-pharmacy and distributor notifications, potential formulary or benefit-design review by payers monitoring supply continuity, and a documented effectiveness check that FDA expects the firm to perform as part of its recall strategy. And for any team building a recall-monitoring process, the enforcement data's heavy Class II share and its long tail of Terminated records are the reason a raw subscription is noisy — filter to Ongoing first, then to Class I, and triage the remainder on classification and lot specificity rather than treating every notice as equal.

This article is for informational purposes only and does not constitute medical advice, treatment guidance, or direction for any specific facility. Recall status, classification, and lot information change; always verify current records in the FDA Enforcement Report and follow your organization's recall procedures before acting.

Last updated: June 13, 2026.

Sources

• FDA. "Enforcement Report Information and Definitions" (Classification I/II/III; Status: On-Going, Completed, Terminated; recalling firm; 21 CFR 7.50). fda.gov
• FDA. "Enforcement Reports" (recall definition; voluntary firm-initiated recalls; pending/"Not Yet Classified" posting; market withdrawals). fda.gov
• FDA. "21 CFR Part 7 — Enforcement Recall Policy" (recall definitions and Class I/II/III health-hazard classification; depth of recall and recall strategy). ecfr.gov
• FDA. "Understanding Drug Recalls: What to Know and What to Do" (Class I generally conducted at the consumer level, Class II at the retail level; patient instructions by class; effectiveness checks). fda.gov
• Gilchrist, S. "Overview of the FDA's Drug-Recall Process," U.S. Pharmacist (recall strategy: depth, public warning, effectiveness checks; Enforcement Report tracking of classification, reason, code, and product updates since July 2018). uspharmacist.com
• ASHP. "Guidance on Medication Recalls" (quarantine labeling with NDC/lot/expiration; sweeping storage locations, ADCs, floor stock, and kits; monitoring incoming purchases for 2–4 weeks; patient communication). ashp.org
• ASHP. "Best Practices: Automation and Information Technology" (USP 797 lot/expiration logging effective November 1, 2023; 2D barcodes such as GS1 DataMatrix encoding NDC, lot, and expiration). publications.ashp.org
• Gaffney, A., et al. "Automating Individualized Notification of Drug Recalls to Patients: Complex Challenges and Qualitative Evaluation" (lot numbers often not documented on dispensed labels; prescribers cannot determine patient-level exposure). PMC
• FDA. "Recalls, Corrections and Removals (Devices)" (Class I/II/III definitions under 21 CFR 7.3(m); recall strategy and effectiveness checks). fda.gov
• Hemophilia Federation of America. "Understanding FDA Drug Recall Procedures" (Class I/II/III distinctions; market withdrawal vs. recall). hemophiliafed.org