A TPLC report is a category, not a device
FDA's Total Product Life Cycle database stitches a device's premarket and postmarket record into one report — 510(k)s, PMAs, adverse events, and recalls in a single view. The key it stitches on is the product code, a generic device type shared by every maker in it, so the counts on "your" report belong to a category, not to your device.
By Connor Griggs — Regulatory & Quality Strategist
Open a device’s Total Product Life Cycle report and it looks like the one page you always wanted: the clearances and approvals that let the device onto the market, then the adverse events and recalls that followed, side by side, one device from submission to the present. It reads like a dossier. It is built like an index, and the thing it is indexed by is not your device.
What the report actually joins on
TPLC integrates data from several separate CDRH databases — device classification, 510(k) clearances, PMA approvals, MAUDE adverse-event reports, and CDRH recalls — into a single record of premarket and postmarket activity. The field it joins them on is the product code: the three-letter code FDA assigns to a generic type of device, not to a submission, a brand, or a company. FDA states the consequence plainly in its own disclaimer: only records that carry a product code are included, and any record in a source database that has no product code is left out of TPLC entirely.
The category, not the device
A product code is shared by every manufacturer of that generic device type. So the recall list and the adverse-event counts on the TPLC report you pulled for “your” product code are the recalls and reports for everyone’sdevice in that code — your competitors’ events, the discontinued models, the private-label versions, all of it, summed. The report answers a real question, but a broader one than it appears to: how has this category behaved, not how has this device behaved. Read it as a record of your own device and you inherit numbers that were never about your device at all.
The counts move, and they are not events
Even read correctly as a category, the numbers carry the caveats of the databases underneath. FDA notes that TPLC presents adverse-event information as device-problem countsdrawn from MAUDE, where a single report may carry several problem codes and reference more than one event — so a count is not a tally of events, and cannot be read as one. The agency also warns that as the source databases are refreshed, the counts in a TPLC report change; and that adverse events filed under the Alternative Summary Reporting program before its 2017 change are not in MAUDE or TPLC at all. On top of that sits the limit MAUDE carries everywhere: report counts have no denominator, so none of these figures is a rate.
Why this pipeline reads the parts, not the whole
FDA Radar ingests the component feeds directly — the Federal Register, warning letters, and openFDA’s enforcement (recall) and 510(k) endpoints — and keeps each item keyed to the firm and record it came from. That is the opposite of what TPLC does. A portfolio watch needs to attribute a recall to a specific product and a specific firm; a category rollup deliberately dissolves exactly that attribution. TPLC is a fine instrument for its own question — orienting yourself in a device type before you have specific records — and the wrong instrument for the question “did something happen to mydevice.”
The practice
Use a TPLC report the way it is built: to read a category’s premarket and postmarket shape at a glance, early, before you have narrowed to specific submissions and recall numbers. Do not lift a recall count or an adverse-event figure off it and attach that number to your own device in a file, a report, or a board slide — the number belongs to the product code, and the product code belongs to everyone in it. Which events in a category are actually relevant to a specific device is a judgment for a regulatory professional reading the underlying records, one at a time, with the context this rollup removes. This is a description of how a public database is keyed — regulatory intelligence and method, never regulatory advice.
Primary sources
- FDA — Total Product Life Cycle for Medical Devices (CDRH Transparency)
- FDA — Total Product Life Cycle (TPLC): Data Sources and Disclaimers
- FDA — TPLC database (accessdata.fda.gov)
- FDA — About the MAUDE Database
- FDA Radar — what we monitor and how often
Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.