Choose the firms and categories you need to follow
Start with the recalling-firm name from a known record and the relevant product codes. These provide complementary ways to find records: a name follows a particular source identity, while a code follows a category even when an unfamiliar firm appears.
Review the public recall history before configuring alerts. Check that a name refers to the intended business and that a code returns the type of products you expected. A broad category may include several distinct codes.
Keep the recall identifier with your notes
Open each relevant record and retain its recall number and original FDA link. Read the product description, stated reason, action, distribution information, and status where available. Do not reduce an entire recall to a short headline when the affected models or action are important to the question.
A recall event can be represented by multiple product records. MedTech Watch labels counts as recall records and retains the FDA recall-event number where supplied. Counting rows is not necessarily the same as counting separate recall events.
Check which date is being shown
Initiation, record creation, classification, and termination dates refer to different events. A recently detected record can describe an action initiated earlier. The date shown in a feed must be read with its label, not assumed to mean that the recall began that day.
The public monthly reports group recall records by initiation date. The general recall feed prefers the FDA classification date when available and labels its fallback dates. These views answer different questions and can therefore produce different month-by-month groupings.
Review changes as well as new records
A recurring watch should preserve the distinction between a newly detected record and an update to one already collected. Changes to action text, status, or other source fields may be relevant even when the recall identifier stays the same.
MedTech Watch collects recall data from openFDA’s weekly dataset and checks for changes. The paid weekly brief links back to the full records; a failed import is reported as a collection problem rather than “no new records.”
- Confirm the firm and product scope.
- Read the reason and action in the source.
- Retain the recall number and event number.
- Distinguish source dates from detection dates.
Keep the purpose clear
This workflow supports competitive intelligence. Weekly public-data monitoring is not an emergency notification service or a replacement for validated postmarket-surveillance processes. Use the manufacturer’s and FDA’s original communications when a recall action affects your own use of a device.
A changed record is not necessarily a new recall
A previously collected recall can later gain a classification or a revised action in the source. Treat that as an update to the identified record, retaining the original initiation date when provided.
Several recall records may belong to one recall event. A monthly count of records is therefore not automatically a count of separate recall events.