What FDA Enforcement History Tells You About a Predicate

A 510(k) clearance represents FDA's assessment of a device at a point in time. The clearance determination is based on the submission — the intended use, technological characteristics, and supporting data the manufacturer provided. It doesn't reflect what FDA learned about that device type in the years after clearance.

FDA's enforcement record — warning letters, recalls, untitled letters, and adverse event patterns — fills that gap. It reflects how regulators have engaged with the device type post-market: what manufacturing failures they found during inspections, what safety signals emerged through adverse event reporting, and what compliance failures were significant enough to prompt formal enforcement action.

For predicate research, this record is relevant in ways that aren't immediately obvious from the clearance database alone.

Warning letters and what they reveal

CDRH warning letters are issued when inspections find significant violations of the Quality System Regulation (or QMSR since February 2026), current Good Manufacturing Practices, or post-market reporting requirements. They're public record, searchable by company and subject on FDA's website.

For predicate research, the most relevant warning letters are those that:

• Cite CGMP violations for the same device type — suggesting the manufacturing environment behind the predicate may not have met the standards FDA expected at clearance
• Cite premarket approval violations — the manufacturer marketed a device modification without obtaining a new 510(k), which raises questions about whether the cleared predicate represents the device as actually manufactured
• Remain open — indicating unresolved compliance issues that FDA has not yet found adequately corrected
• Were issued close in time to the clearance you're relying on — the overlap between the inspection period and the clearance date is most significant

Recalls and device type history

A recall doesn't disqualify a predicate. FDA's own guidance acknowledges that a recalled device can still serve as a valid predicate — the recall addresses a specific issue with specific marketed units, not the fundamental regulatory status of the cleared device type.

But recall history for a predicate's product code is relevant context. Patterns of recalls in a device type — particularly Class I recalls citing design defects or labeling failures — reveal how FDA and the industry have understood the device's risk profile post-market. That understanding shapes how FDA reviewers approach new submissions in the same space.

If your device addresses a failure mode that has generated significant recall activity in the predicate's product code, that can be an asset in your submission — your design specifically mitigates a documented risk. If your device shares the characteristics that have driven recalls, that's a risk to address proactively.

Adverse event signals and evolving FDA thinking

FDA's post-market surveillance — through MAUDE reports, MDR analysis, and its own monitoring programs — continuously informs how the agency thinks about device types. Significant adverse event signals can lead to guidance updates, new special controls, or letters to industry that change the regulatory expectations for a device category.

If FDA has issued guidance or letters to industry in response to adverse event patterns in your predicate's product code since the predicate was cleared, those documents may affect what your submission needs to demonstrate — even if the requirements aren't formally codified in new special controls.

This is one reason why predicate research should include a review of the FDA's letters to industry and guidance activity for the relevant device type, not just the clearance database. A predicate that was uncontroversial in 2020 may sit in a product code that FDA has scrutinized heavily since then.

How to use this in practice

Enforcement history is most useful as a tiebreaker and a flag. When two predicate candidates have similar regulatory fit, the one with a cleaner enforcement record is generally the stronger choice — all else equal. When a candidate has a significant enforcement history, that's a flag to investigate further before committing, not an automatic disqualifier.

The research takes time. FDA's enforcement records are spread across multiple databases — warning letters, recalls, adverse events — that don't connect to the 510(k) clearance database. Running this check for each predicate candidate manually adds hours to a workflow that's already fragmented.

The alternative — committing to a predicate without checking the enforcement record, and discovering a problem during FDA review — is more expensive.