FDA product code

An FDA product code is the three-letter classification that identifies a generic device type and determines which regulatory pathway applies to it. In the cataloged openFDA records it behaves as the join key between endpoints: the Registration & Listing API tags its product-code fields, MAUDE's per-device arrays carry device identification, and both the 510(k) Clearances API and the GUDID API expose product code fields.

That consistency is what makes cross-endpoint analysis possible. Because the code identifies the generic type, clearance records, adverse-event reports and establishment listings can be aggregated to the same device category without name matching, which is unreliable since manufacturers market one device type under many brand names.

• Without the code, joins break. Matching MAUDE adverse events to 510(k) clearances by brand name undercounts, because the same generic device type ships under many names. The product code is the field both endpoints share.

• Denominators depend on it. Any adverse-event rate for a device category needs the code to define the population of cleared devices it is measured against.

• Pathway questions resolve to the code. Whether a device followed 510(k) premarket notification is a property of its classification, so regulatory and procurement teams should capture the code alongside the part number.

1. Confirm the field is exposed. Both the 510(k) Clearances API and the GUDID API carry product code fields; verify them before designing a pipeline.

1. Enumerate the type from Registration & Listing. The API's product-codes tags let you list the devices filed under a given code.

1. Join MAUDE on the code, not the name. MAUDE's per-device arrays carry device identification that keys to the same classification.

1. Watch for multi-code product lines. A line can span several codes, so category totals should be checked for double counting before they become denominators.

1. Read the clearance record itself. The 510(k) clearance entry explains what the pathway document does and does not certify.

The product code is best understood next to the pathway document it points to:

510(k) clearance is the regulatory pathway many product codes resolve to, and its record shows what a clearance does and does not certify for one device type.

The device records keyed to product codes sit in the catalog's health-care-equipment data, health-care-supplies data pages.