Recalls, tracing and suspect products

What you will learn

• Distinguish FDA recall classes without confusing them with DEA schedules.
• Match a recall notice to exact product and lot information.
• Recognize the quarantine and investigation response to suspect supply.

Before you start

A lot number identifies a manufacturing batch. A recall concerns removal or correction of a product with a problem. A DEA schedule classifies controlled substances; it is unrelated to an FDA recall class.

Severity does not identify the affected bottles

FDA Class I recalls involve a reasonable probability of serious health consequences or death. Class II involves temporary or medically reversible harm, or a remote probability of serious harm. Class III involves a situation unlikely to cause adverse health consequences.

The class helps communicate risk. The notice's product, strength, package and lot information identifies what is affected. A Class III recall still requires the specified action; “lower risk” does not mean “ignore it.”

Imagine a fictional notice names product X, 10 mg tablets, lot AB12. Your shelf has lot AB12 and lot AB13. Compare every stated identifier. Do not assume the entire brand is recalled if the notice names one lot, and do not miss the affected lot because another bottle is unaffected.

Change the notice so it includes all lots of the identified product. The scope changes. The correct inventory set follows the notice, not yesterday's assumption.

Pause and predict

A bottle's generic name matches a recall, but the strength and lot have not been checked. Is that enough to finish the recall search?

Trace where the product came from

The Drug Supply Chain Security Act (DSCSA) creates tracing and verification duties for covered prescription drugs. Pharmacies must work with authorized trading partners and have processes for suspect and illegitimate products. A suspect product has a reason for concern; investigation determines whether it is illegitimate.

For example, damaged or suspicious packaging plus inconsistent tracing information should not be “fixed” by entering an expected code. Quarantine the affected product so it cannot be dispensed, preserve the packaging and transaction information, and alert the responsible pharmacist.

If a product is determined illegitimate, required notifications and disposition steps apply, including FDA and relevant trading partners. The technician supports the documented process; do not make an unsupported declaration that a product is counterfeit or return it to usable inventory without authorization.

Keep product identifiers in their roles

The National Drug Code (NDC) identifies a drug product/package listing; it is not a lot number or expiration date. An NDC listing also does not itself prove FDA approval. A barcode scan can help match a record but cannot by itself settle product legitimacy.

In a fictional recall exercise, two packages have the same NDC and different lots. Only one lot is named. The NDC match narrows the product family, while the lot comparison completes the stated batch check. If the notice's scope is broader, follow that broader scope.

Try it without the walkthrough

1. A notice is an FDA Class II recall. Does that mean the medicine is a DEA Schedule II controlled substance?
2. A fictional notice recalls product Y, strength 5 mg, lot C7. A bottle is product Y, strength 5 mg, lot C8. Is it within the stated lot-specific scope?
3. A package has inconsistent tracing information but a scannable NDC. What should happen before it is treated as available stock?

Keep this pattern

Recall class describes risk; identifiers define scope; tracing supports investigation. Preserve evidence and prevent uncertain stock from being dispensed.