How to Evaluate a 510(k) Predicate Before Committing

Choosing a predicate is the most consequential decision in a 510(k) submission. Switch predicates mid-review and you've effectively started over. Choose one that FDA scrutinizes heavily and you'll spend months in Additional Information cycles. The time to evaluate is before you commit — not during review.

Most predicate evaluation stops at the clearance record: product code match, intended use overlap, technological characteristics. That's the necessary starting point, not the complete picture. A thorough evaluation adds three more layers: post-market safety history, manufacturer enforcement record, and predicate chain integrity.

Layer 1 — Clearance fit

The basics apply before anything else. Your predicate must have the same intended use and either the same technological characteristics or differences that don't raise new safety questions. Before moving to deeper evaluation, confirm:

• Same product code — not just the same device category, the same three-letter code
• Intended use statement that your device's indication tracks closely
• Clearance within the last 5-7 years when possible, reflecting current FDA thinking
• No special controls your device cannot meet
• Decision type of Substantially Equivalent — not Not Substantially Equivalent with a subsequent appeal

If a candidate doesn't pass this layer, don't proceed to deeper evaluation. The additional research is only worth doing for candidates that could actually work.

Layer 2 — Post-market safety history

Once you have a shortlist of candidates that pass the clearance fit test, check the adverse event record for each. FDA's MAUDE database contains reports submitted when a device may have caused or contributed to patient harm or malfunction. Search by product code for each candidate and review:

• Total report volume relative to other candidates in the same code
• Proportion of death and injury reports versus malfunction reports
• Whether reports concentrate around a specific failure mode relevant to your device's design
• Trend over the last 2-3 years

A high adverse event count isn't disqualifying — high-volume devices generate more reports. What matters is whether the pattern reveals anything about the device type's performance that's relevant to your SE argument or your testing strategy.

Layer 3 — Manufacturer enforcement history

Check whether the predicate applicant has received CDRH warning letters. Open warning letters — particularly those citing CGMP violations, CAPA deficiencies, or premarket approval issues — provide context about the manufacturer's quality system that isn't visible in the clearance record.

This layer is most relevant when:

• The warning letter was issued close in time to the predicate clearance you're relying on
• The cited violations relate to the device type or manufacturing process behind the predicate
• The letter cites premarket approval violations — the manufacturer made changes to the device without a new 510(k)
• The letter remains open, indicating unresolved compliance issues

A manufacturer's enforcement history doesn't automatically weaken a predicate. But it's information worth having before you build a submission around their device.

Layer 4 — Predicate chain integrity

For complex SE arguments, trace the predicate chain back at least 2-3 generations. Identify whether any link in the chain involved a significant technological jump that FDA might flag during review. Look for De Novo decisions in the chain — they're valid predicates but establish new device types, which carries different implications than a traditional 510(k) chain.

Deep chain analysis isn't necessary for every submission. It becomes relevant when your SE argument is complex, the device type has attracted FDA scrutiny, or you're relying on a relatively recent predicate that itself relied on a clearance with an unusual review history.

Making the decision

After running all four layers on your shortlist, you're looking for the candidate with the strongest combination of regulatory fit, post-market safety record, clean enforcement history, and defensible chain. In most cases, one candidate will be clearly stronger. In others, tradeoffs require judgment — a stronger intended use match against a more complex adverse event record, or a cleaner chain against a less precise product code match.

Document your reasoning. If FDA asks about your predicate selection — which they may in an AI request or during review — having a written rationale that addresses each layer of the evaluation is more useful than a one-line answer about product code match.