The FDA Enforcement Report is the agency's weekly publication of recalls it monitors, and for devices it is the record that carries the official recall number, classification and reason once FDA has completed its hazard assessment [1]. Searching it well is less about typing a product name into a box and more about knowing which identifier to start from, which of FDA's several recall records answers your question, and what the report cannot tell you. This guide sets out a defensible search sequence for regulatory affairs work, with the documented limits of each record stated plainly.
Start with the identifier, not the product name
A device search usually begins with a question about a specific unit, model or clearance. The identifiers that make that question answerable are the brand and model, the lot or serial number, the product code, and where applicable the 510(k) or PMA number. FDA's own reporting requirements for corrections and removals list the same categories of information firms must supply, including brand name, intended use, marketing status, model or catalog number and lot or serial number [3]. Collecting those before searching reduces the chance of matching the wrong record.
A published third-party workflow suggests starting with the Medical Device Recalls database for a specific device, then moving to the Enforcement Reports when the official classified record or recall number is needed, and checking early alerts for issues not yet classified [4]. That sequence is a suggestion from a secondary source, not an FDA instruction, and it should be treated as one possible route. FDA's own page describes access through the weekly report, quick and advanced search, and an API, without prescribing an order [1].
Reading classification and status without overreading them
Classification describes the relative health hazard of the action, not the risk class of the device. A Class II device can be the subject of a Class I recall [4]. FDA notes that classification usually follows the recalling firm's provision of the information needed to assess public health risk, and that the classification and posting should not be read as an expansion or change to a firm's voluntary public warning [1]. Firms often issue their own public statements well before FDA completes classification [1].
Status is the field most often misread. FDA states that it does not update the status of a recall after classification, so the status (open, completed or terminated) remains unchanged once published in the Enforcement Reports [2]. A record showing an active status is therefore not proof that corrective action is still underway today. Separately, FDA's openFDA documentation warns that the data should not be used to track the lifecycle of a recall [2], which constrains any internal dashboard built on that feed.
Practical detail: build the search record before you search
Before opening any FDA search interface, write down five fields: brand and model, lot or serial, product code if known, 510(k) or PMA number if known, and the date the question was asked. FDA's correction and removal reporting requirements list brand name, intended use, marketing status, model or catalog number and lot or serial number among the information firms must supply [3], which makes them the natural minimum for a search record. Add the retrieval date because Enforcement Report entries are updated after publication and the history feature only reaches back to 24 July 2018 [1]. A search without a retrieval date cannot be reproduced later.
Choosing between the Enforcement Report, openFDA and the dashboard
Three FDA-published routes reach overlapping recall data with different coverage rules. The Enforcement Report covers all recalls FDA monitors, including Class I, II, III and not-yet-classified actions [1]. The openFDA device enforcement API draws on the Recall Enterprise System, covers publicly releasable records from 2004 onward and updates weekly [2]. FDA's Recalls dashboard is based on the Enforcement Reports but displays only recalls classified on or after 08 June 2012, and only classified recalls appear in the dataset [5].
Those differences matter for any count. A query against the dashboard cannot return unclassified actions, and a query against openFDA cannot return anything before 2004. The dashboard also carries a caveat that certain information may not be presented or may have changed since posting, and directs users needing more recent or complete data for official purposes to the Division of Freedom of Information [5]. For a regulatory file, the Enforcement Report entry remains the record to cite; the other routes are for screening and volume work.
What the Enforcement Report does not establish
An Enforcement Report entry is not evidence that a device caused harm. FDA makes the equivalent point about medical device reports: submission of an MDR is not evidence that the device caused or contributed to the adverse outcome [7]. The recall record documents an action and its classification, not causation, and it does not replace the firm's own communication about what customers should do with affected units.
The report also changes after publication. FDA tracks and displays updates to a recall's classification, reason for recall, code information and product description where changes occur after initial publication, with that history available for recalls posted or updated from 24 July 2018 onward [1]. FDA may correct or change previously disclosed recall information, for example where a firm finds the recall should be expanded to more lots [2]. Any search result should therefore be re-pulled before it is relied on in a submission or a management report.
A worked search sequence for a device family
Consider a hypothetical: a regulatory affairs team is asked whether a specific orthopedic implant line has any open recall history. As a suggested workflow, the analyst would first pull the model and lot from the unit or the complaint file, then search the device recalls database by firm and product, and confirm the affected-lot list against the specific unit [4]. The classification and status would be recorded, and the recall number pulled from the Enforcement Report for documentation [4]. None of this has been tested here; it is an illustration of how the documented fields fit together.
The same team would then check whether the action appears as not yet classified, since a recent action may appear unclassified and require a later re-check for the official tier [4]. If the team needs a count of device recalls by year for a management review, the dashboard's classified-only rule and 2012 start date must be stated alongside the figure, and the count attributed to the source rather than presented as a complete recall census [5]. Where the question concerns adverse events rather than recalls, MAUDE is the relevant database, and it is a separate record with its own reporting rules [6].
Sources & references
- Enforcement Reports | FDA · www.fda.gov
- Device Enforcement Overview · open.fda.gov
- Recalls, Corrections and Removals (Devices) | FDA · www.fda.gov
- How to Check if a Medical Device Was Recalled: FDA Recall Database Lookup | MedDeviceGuide · meddeviceguide.com
- FDA Dashboards - Recalls · datadashboard.fda.gov
- Manufacturer and User Facility Device Experience (MAUDE) Database · www.accessdata.fda.gov
- Medical Device Reporting (MDR): How to Report Medical Device Problems | FDA · fda.gov
- Inspection of Medical Manufacturers - 7382.850 · www.fda.gov