Drug Shortage & Discontinuation Monitor (FDA) avatar

Drug Shortage & Discontinuation Monitor (FDA)

Pricing

from $10.00 / 1,000 results

Go to Apify Store
Drug Shortage & Discontinuation Monitor (FDA)

Drug Shortage & Discontinuation Monitor (FDA)

Track US drug shortages and permanent discontinuations from the FDA's own database — by drug, therapeutic category or manufacturer — with alerts when a product becomes unavailable or is discontinued.

Pricing

from $10.00 / 1,000 results

Rating

0.0

(0)

Developer

Sasha Ebashu

Sasha Ebashu

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Tracks US drug shortages from the FDA's own database and tells you what changed since the last run — including the event that matters most to a buyer: a product being discontinued for good rather than merely out of stock.

Built on the FDA's public API. No key, no login, no scraping.

What you get

One row per FDA shortage record:

FieldWhat it is
genericName / brandNames / substanceNameThe drug, as FDA names it plus the brand names it ships under
company / contactWho reported the shortage, and the phone number FDA publishes for them
statusCurrent, To Be Discontinued, Resolved
isDiscontinuingThe product is going away permanently — plan around it, don't wait it out
availabilityAvailable, Limited Availability, Unavailable — normalised (see limits)
therapeuticCategoryAnesthesia, Pediatric, Psychiatry, Oncology…
dosageForm / presentation / packageNdc / productNdcsExactly which pack is affected
route / pharmClass / rxcui / applicationNumbersClinical and regulatory identifiers for joining to your own data
firstPostedAt / updatedAt / daysInShortageHow long this has been going on
drugRecordsInShortage / drugCompaniesAffected / drugUnavailableCountPer-drug context across the whole database — is one supplier struggling, or the entire market?

Monitor mode

Run it on a schedule and every record is labelled against the previous run:

changeTypeMeans
to_be_discontinuedThe product is being withdrawn permanently — the highest-priority event
became_unavailableSupply has stopped
resolvedThe shortage is over
availability_changeSupply level moved (e.g. Available → Limited)
status_changeAny other status move
new_shortageFirst time seen in this scope
unchangedNothing moved

The order is deliberate: it is what a pharmacy or procurement team has to act on first, not the order the fields happen to sit in. Turn on Output only changed records for a pure alert feed.

Input

FieldWhat it does
Drugs to watchGeneric names, matched as substrings — lisdexamfetamine finds Lisdexamfetamine Dimesylate Capsules. Empty = every drug.
Therapeutic categoriesFDA's own categories.
CompaniesThe reporting manufacturer, substring match.
StatusesDefaults to Current + To Be Discontinued; add Resolved for history.
Only fully unavailableDrop partial and limited supply, keep the hard stops.
Monitor mode / Output only changedThe alert behaviour above.

Notes & limits

Properties of the source, measured rather than assumed:

  • One drug is many records. FDA files a row per company and presentation — Lisdexamfetamine currently spans 90 records across 13 companies, Ropivacaine 49. Rows are kept faithful to the source, and the per-drug rollup fields give you the aggregate without losing the detail.
  • The FDA data contains a typo, and it is handled. availability holds both Unavailable and the misspelled Unvailable. Filtering on the correct spelling silently drops the affected record, so availability is normalised — availabilityRaw keeps the original text so nothing is hidden.
  • The whole database is downloaded every run (~1,700 records, two requests — openFDA caps limit at 1000 and rejects 1001). Filters are applied locally on purpose: a server-side filter could hide a record that later reappears and would then read as "new". It also keeps the per-drug rollups true to the entire database rather than to your slice.
  • Resolved is rare — 25 records against 1,177 Current and 450 To Be Discontinued. FDA removes resolved entries rather than archiving them, so this is not a shortage history.
  • Dates are the FDA's own posting dates, in MM/DD/YYYY, converted to ISO in the output.
  • The Actor honours your Maximum cost per run and stops when the cap is reached.