Reading FDA device recall code information requires mapping codes to specific fields in two public sources: the weekly Enforcement Report and the CDRH Medical Device Recalls database. The Enforcement Report supports searching by a dedicated code-information field. The CDRH database returns product codes, recall numbers, and optional PMA or 510(K) identifiers. A professional evaluation should connect each field to the recalling firm's own communication, because FDA records may summarize or omit portions of the original lot and serial detail. The classification shown in either source can lag behind the action date [2]. This guide follows the named fields, explains the decision points where a record may be incomplete, and shows how to check identity, scope, and status in sequence. It concludes with a concrete evaluation example and a short set of verifiable field definitions drawn from the cited FDA documents.

The Two Public Recall Records

FDA recall information appears in the Enforcement Report and in the CDRH Medical Device Recalls database. The Enforcement Report page states that it includes recalls monitored by FDA from Class I through III, as well as actions that are not yet classified, as described in 21 CFR 7.50 [1]. The CDRH database contains medical device recalls classified since November 2002 and, since January 2017, may also include correction or removal actions initiated by a firm before FDA review [2]. These are related but not interchangeable records, so code information read from one source should not be assumed to appear identically in the other without checking the original firm notice.

The Enforcement Report search screen includes a field named Code Information, alongside Product Description, Recall Class, Recalling Firm, Status, Recall Number, Reason for Recall, Classification Date, and Event ID [1]. FDA defines Code Information as a list of all lot and/or serial numbers, product numbers, expiration dates, sell or use by dates, and similar identifiers appearing on the product or its labeling [1]. A search on that field lets a reader test whether a lot or catalog string appears in the published record. The CDRH database search screen offers separate Product Name and Product Code fields for in vitro devices, a Recall Class selector, PMA or 510(K) number, Recall Date, Recall Number, Reason for Recall, and Recalling Firm [2]. The cited source does not describe how lot, serial, UDI, or catalog strings should be entered in those fields, so a reader should not assume that an identifier accepted by the Enforcement Report Code Information field can be searched identically in the CDRH database.

Fields That Actually Carry Device Codes

The term recall code information can refer to several different fields. Device records commonly use product codes, catalog or model numbers, lot or serial numbers, and the UDI. The CDRH search screen lists Product Code as a searchable field for in vitro devices and PMA or 510(K) Number as a separate field [2]. A document about Part 806 reporting identifies the UDI as a distinct element, recommending submission of either the UDI-DI alone or the full UDI with all parentheses and special characters preserved [4]. That distinction matters because a UDI-DI may identify a model while only the production identifiers capture lot or serial scope.

For mandatory recall orders, 21 CFR Part 810 specifies that a cease distribution and notification order should include identifying information for the device: the name and classification name or usual name, the model or catalog or product code numbers, the manufacturing lot numbers or serial numbers or other identification numbers, and the UDI appearing on the label or package [7]. Readers should therefore treat model, catalog, product code, lot, serial, and UDI as separate fields rather than as synonyms. A record may carry a catalog string but no lot range, or a UDI-DI but no full UDI, leaving the affected-unit scope unresolved without the firm's notification.

Field Definitions for Reference

When reading a record, use the Enforcement Report's own label definitions. Voluntary or Mandated designates whether a recall was initiated voluntarily by a firm on its own, after an FDA request, or under mandatory recall authority, a court order, or an FDA order; Recall Initiation Date is the date the firm first began notifying the public or consignees; Initial Firm Notification of Consignee or Public records the method used [1]. Press releases are linked where available, and more than one press release may be listed for a single recall [1]. Those links are often the clearest route back to the original code list, product names, and clinical instructions that a database row omits.

Reading Classification, Status, and Dates

Recall class describes relative risk, not progress toward completion. FDA states that a Class I recall involves a reasonable chance of serious health problems or death, Class II involves temporary or reversible health problems or a slight chance of serious health problems or death, and Class III involves a situation where a product is not likely to cause any health problem [6]. The Enforcement Report includes not yet classified actions and warns that classification usually occurs after the recalling firm supplies information needed to assess public health risk [1]. A reader who sees an unclassified code match should therefore record that risk has not yet been assigned rather than infer lower severity.

Status is a separate field with its own vocabulary. The Enforcement Report definitions describe Completed as the point at which the firm has retrieved and impounded all outstanding product that could reasonably be expected to be recovered or has completed all product corrections [1]. Terminated occurs when FDA determines that reasonable efforts have been made under the recall strategy and disposition is commensurate with the degree of hazard [1]. The CDRH database states that the status is updated if FDA identifies a violation and classifies the action as a recall and again when the recall is terminated [2]. Status and classification therefore evolve on different schedules, and a current status value should not be treated as proof that every downstream consignee acted.

Where Code Ambiguity Comes From

A recall may cover an entire lot, model, or product line because the firm knows a problem affects a group of products but cannot predict which individual devices are defective [6]. In those cases, a single lot number may define the entire affected population, while in other recalls the same field covers only a portion of units. FDA guidance for recall submissions recommends explaining whether a problem affects all units subject to recall or only a portion of the units in the lots subject to recall [5]. Public database records do not always reproduce that explanatory sentence, so a code match alone cannot show whether an individual device is included.

Another source of ambiguity is the difference between a recall and a correction or removal that does not yet violate FDA law. FDA uses the term recall when a manufacturer takes a correction or removal action to address a problem that violates FDA law; recalls occur when a device is defective, could be a risk to health, or both [6]. A correction addresses a problem in the place where the product is used or sold, while a removal removes it from that location [6]. Since January 2017, the CDRH database may include actions initiated before FDA review, and the create date indicates when FDA classified the recall, not necessarily that the recall is new [2]. A professional reading must therefore separate the action date from the classification date and the possibly later status update.

A Concrete Evaluation Sequence

A suggested workflow for evaluating a device code is to first capture the identifier format from the label or package. If the string is the full UDI, its application identifiers should be treated as literal data, not reformatted, because FDA recommends submitting UDI information with all parentheses and special characters as provided [4]. If only the UDI-DI is available, record that it identifies the device model rather than a specific unit. Next, run the same string through the Enforcement Report Code Information field, which FDA defines as a list of all lot and/or serial numbers, product numbers, expiration dates, sell or use by dates, and similar identifiers appearing on the product or its labeling [1]. The CDRH database search screen lists Product Name and Product Code as separate fields for in vitro devices, but the cited source does not state that lot, serial, UDI, or catalog strings can be searched in those fields [2]. A positive match in the Enforcement Report confirms only that the string appears in a record; it does not confirm that the reader's unit is part of the affected distribution.

After matching a record, extract the Recall Number, Recall Class, Status, Classification Date, and Recalling Firm, then compare those fields with the firm's original recall notification or press release where available [1]. The firm communication may contain lot ranges, consignee instructions, and UDI lists that the public database record summarizes. Read receipts or certified delivery receipts are not confirmation that a consignee took appropriate action [4]. The final check is whether the record is an unclassified or pre-review action and whether the status is completed or terminated, because neither condition proves that a specific unit was returned, corrected, or destroyed [1][2]. This sequence keeps the code lookup verifiable without inventing clinical or legal conclusions from the database alone.