Start with the affected product and action
The product description, stated reason, and action are the core of a recall record. Read them together. A short device name may omit the model, configuration, or other scope details needed to understand the record. Follow the original FDA link and any manufacturer communication it identifies.
Keep the recall number with the record. Where supplied, the recall-event number helps identify related product records, but it should not erase their separate product descriptions.
Recall class is different from device class
FDA assigns recall classifications to indicate the relative health hazard of a recall. Class I represents the most serious category, Class II covers situations involving temporary or medically reversible consequences or a remote probability of serious consequences, and Class III concerns situations unlikely to cause adverse health consequences.
The device’s regulatory class is a separate classification system. A Class II medical device does not necessarily have a Class II recall. MedTech Watch keeps these fields distinct instead of inferring one from the other.
An unknown class is still unknown
The device-recall dataset and the enforcement dataset contain different fields. MedTech Watch enriches a recall with an enforcement classification only when the recall number matches. If there is no confirmed match, the classification is shown as unavailable.
That missing value does not mean that FDA has determined there is no hazard. It means the linked classification was not available in the data used for this page. Check the original source for the latest record.
Read status alongside the dates
Recall initiation, FDA record creation, classification, and termination dates are separate fields. The recalling firm’s action can begin before FDA classification appears. A status change also does not change the historical initiation date.
MedTech Watch preserves the source’s status wording and shows available dates with explicit labels. An absent date is not replaced with the collection date, and a source field is not silently interpreted as a prediction about what happens next.
- Which product and models does the record describe?
- What reason and action does the source state?
- Is the class sourced or unavailable?
- Which event does each displayed date describe?
Check what the action actually covers
A recall description can specify model numbers or lots. Preserve that wording when recording the affected scope instead of expanding it to every product sold by the company.
If an enforcement record matches the recall number, its available classification can enrich the page. A name match alone is insufficient, and a missing classification is not a low-risk classification.