The openFDA Drug Shortages API makes current and resolved shortage information queryable. A record can identify a drug, presentation, status, and shortage reason. It does not automatically reveal the full commercial supply chain behind that record.
What the network adds
Shortage coverage often stops at “demand increased” or “manufacturing delay.” A supply map keeps several mechanisms separate: active ingredient availability, production capacity, quality release, distribution, and demand.
These are different nodes because they imply different questions. More demand is not repaired the same way as a quality hold. A distribution allocation can create local scarcity even when manufacturing output is unchanged.
The network also prevents a causal shortcut. A public record can report a reason category without exposing every upstream supplier, site, contractual relationship, inventory position, or allocation rule. Those missing edges should remain missing. A visually complete supply chain built from assumptions would be more persuasive and less reliable than a partial map with explicit unknowns.
The correct unit of analysis
Track the affected presentation — strength, dosage form, route, and package — rather than treating every product with the same generic name as equally unavailable. That distinction is essential for a useful comparison table.
| Level | Example question |
|---|---|
| Active ingredient | Is the same ingredient constrained across manufacturers? |
| Finished product | Which dosage form and strength is listed? |
| Presentation | Which package or delivery configuration is affected? |
| Manufacturer | Who reports the status and reason? |
| Time | When did the status first appear and when did it change? |
Two records with the same generic drug name can therefore represent different operational realities. Combining them into one red “shortage” node may erase the very detail a pharmacist, reporter, or supply analyst needs.
This diagram is a conceptual reading aid. It does not assert a cause for any specific drug shortage and should not guide patient care or substitution decisions.
Reading a status change responsibly
“Current,” “resolved,” and “discontinued” describe different states, but a state change does not by itself explain nationwide availability at every location. Resolution in a public record can coexist with replenishment time in distribution channels. Conversely, an individual facility can report difficulty obtaining a product that is not represented as a national shortage in the same way.
A citable update should name the exact product presentation, previous state, new state, observation time, and source URL. It should separate a manufacturer's reported reason from the reporter's analysis. If the reason text changes, store both versions rather than silently replacing the earlier statement.
A daily public tracker worth citing
A strong shortage page would show additions, resolved records, status duration, and reason categories, then link every row to FDA. The visual should label manufacturer claims separately from FDA status. Historic snapshots matter because the API's current state alone may not explain when the status changed.
The tracker should answer four reader questions without requiring API knowledge:
- What precisely is affected?
- What changed since the last check?
- Who supplied the reason and what did they say?
- Which facts remain unknown from the public record?
Summary charts can count presentations or records, but must disclose the denominator. Counting generic drug names, manufacturer records, and package presentations produces different totals; none should be labeled simply “number of drugs” without definition.
For newsroom or operations use, the same nodes can be rearranged in a MyMap concept map, with a source URL attached to each factual relationship.
Safety and editorial limits
This page cannot recommend alternatives, dosing changes, or substitutions. Those decisions belong to qualified clinicians and pharmacists using current patient-specific information. The public-data workflow also cannot reveal confidential inventories or contractual causes. Our editorial job is narrower: make the official status, stated reason, time sequence, and known relationships easier to inspect.
Update policy
The prototype establishes the information architecture. A production tracker should store daily snapshots, detect field changes, and publish only meaningful diffs — not create a new article for an unchanged record.
Meaningful diffs include a new listing, a changed availability status, a revised shortage reason, or a resolved record. Cosmetic formatting and API ordering changes should not trigger publication. Every automated alert needs a human-readable before-and-after record so an editor can verify that the change is substantive.