Confirm the product-level signal before naming resident impact
Start with FDA's record and inspect ingredient, dosage form, strength, presentation, company information, availability, and update date. Save the checked date with the work item, then verify the dispensing pharmacy's actual supply situation before identifying resident impact.
A national listing does not establish that every presentation is unavailable to every pharmacy. A local problem may also appear before a broad public status changes. Hold both facts at once: the federal source describes the national signal, while the dispensing pharmacy can confirm the product and supply path relevant to its residents.
Avoid a drug-name-only alert. A shared ingredient may cover several strengths, dosage forms, presentations, or suppliers with different availability. If the notice and local record cannot yet be matched at the necessary level, mark the scope unconfirmed rather than broadening it by assumption.
Build a resident-impact worklist without prescribing from it
Identify potentially affected residents and facilities, then route the list to the responsible dispensing and clinical teams. Keep the current product detail and timing beside each name, but do not encode an unapproved substitute as though it were an order or imply that every listed resident will need a therapy change.
The worklist should help people find and own questions. It should not collapse supply confirmation, clinical review, authorization, dispensing, monitoring, and follow-up into one shortage status.
- Match basis: the product, strength, dosage form, presentation, and source record used to flag the item.
- Local status: what the dispensing pharmacy confirmed, when, and for which supply route.
- Resident context: the current order and information the responsible reviewer needs to frame the question.
- Owner: the dispensing, clinical, or facility contact responsible for the next decision or confirmation.
- State: unconfirmed, review needed, decision recorded, action in progress, or follow-up pending, using locally defined terms.
- Next point: the date or event that will trigger another supply check or resident review.
Keep supply facts separate from clinical decisions
A confirmed supply constraint answers an operational question; it does not select a resident-specific response. Route the current facts to the responsible professionals and preserve the recommendation, authorized decision, timing, and any monitoring or documentation plan that follows.
If no change is made, keep the available rationale or supply resolution with the item rather than closing it as a generic nonissue. If a temporary change is authorized, distinguish proposed, ordered, dispensed, and later reviewed. Those states protect the resident story from being rewritten by the latest supply update.
Test the exceptions that make a shortage queue unreliable
Use synthetic or appropriately protected data to test a product with two strengths, a resident who transferred facilities, a partial local supply, a late pharmacy response, and an authorized temporary change. Ask whether the system preserves the match basis, shows uncertainty, and routes urgent work outside the routine MRR batch.
Then correct one product detail and update the national status. Inspect the resident worklist, timeline, report, and export. The demonstration can show whether the workflow handles changes and provenance; it cannot predict local availability, choose a substitute, or establish a clinical outcome.
Recheck residents when the public or local status changes
A resolved national status does not necessarily mean every local channel has stock immediately. Reconfirm local supply and review any temporary therapies, orders, documentation, or monitoring plans created during the shortage. Give each remaining item an owner instead of assuming the public update closes it.
Likewise, a new update should not erase the earlier record. Keep when the practice learned of the signal, what the pharmacy confirmed, which residents were reviewed, what decisions were authorized, and what remained unknown at each point.
Measure whether the handoff worked, not whether the alert fired
After the episode, inspect missed matches, duplicate outreach, delayed ownership, and temporary changes that lacked a clear return review. Those are bounded process findings a small practice can improve.
An alert count is not evidence that residents were affected or protected. The durable value is a traceable route from a product-specific signal to local confirmation, resident-specific decision-making, and an honest closeout.