How to Find and Choose a Predicate Device for Your 510(k) Submission

2026-07-18 · Caduvo Team

Learn how to find and select the right predicate device for your 510(k) submission, using FDA database searches and ranking criteria to reduce testing burden and regulatory risk.

You’re staring at a device that’s new to your company but not necessarily new to the FDA. You need a 510(k) clearance, and that means finding a predicate device—a legally marketed device to which you can claim substantial equivalence. Pick the wrong one and your testing budget balloons, your review clock resets, or your submission gets rejected. Pick the right one and the path to market shortens dramatically. Here’s how to do it.

What is a predicate device?

A predicate device is a previously FDA-cleared (or pre‑amendments) device that serves as the point of comparison for your new device in a 510(k) submission. The FDA requires you to demonstrate that your device is substantially equivalent (SE) to the predicate—same intended use and either same technological characteristics or different characteristics that don’t raise new questions of safety and effectiveness.

Substantial equivalence is not an exact clone. Your device can differ in materials, design, or performance, but those differences must be well‑characterized and justify why they do not affect safety or effectiveness. The predicate device anchors that comparison.

Why your predicate choice dictates your 510(k) burden

The predicate you select sets the bar for the testing data you’ll need. If you identify a predicate with nearly identical technology and intended use, bench testing may suffice. Choose a predicate with more significant differences, and you may need animal studies, clinical data, or human factors testing.

The predicate also routes your submission to a specific FDA review branch. Branches develop deep familiarity with certain device types; matching a well‑known predicate with a long history of clearances in that branch can reduce review questions and accelerate the timeline.

A weak choice—such as a device cleared decades ago, one with a recall history, or one that required burdensome clinical studies—directly transfers that risk to your submission.

How to find predicate candidates: FDA database search workflow

Use this step‑by‑step approach to build your candidate pool.

Define your device’s intended use and technological characteristics in a single paragraph. Use the exact language you expect to see in your 510(k).
Look up your device’s FDA product code. The product code determines the regulation number and the review division. Use the FDA Product Classification database. If you aren’t sure which code fits, review the FDA medical device classification system and consult the applicable regulation.
Search the FDA 510(k) Premarket Notification database by product code. Limit results to the last 10–15 years to avoid obsolete predicates. Refine by applicant name, device name, or advisory committee if you have a specific competitor in mind.
Retrieve 510(k) summaries (K numbers) for promising entries. These publicly available documents include a section called “Substantial Equivalence Discussion” that often lists the predicate used and a comparison table of technological characteristics. Pay attention to the tests that were cited.
Expand to adjacent product codes if your initial pool is too small. A device with similar intended use but a different product code may still serve as a predicate—though the regulatory rationale requires more justification.

Record each candidate in a spreadsheet with columns for K number, applicant, date cleared, product code, intended use, technological characteristics, and any notes from the SE discussion.

Ranking your candidates: what makes a strong predicate

Not all predicates are equal. Score each candidate against the criteria below. A strong predicate will meet most of them.

Identical intended use. The indication statement should match yours as closely as possible. Differences in patient population, anatomical site, or clinical purpose increase scrutiny.
Similar technological characteristics. Compare materials, design, energy source, and principle of operation. If your device uses a different mechanism, you will need to explain why it doesn’t raise new questions.
Recent clearance. The FDA expects predicate devices to have been legally marketed at the time of your submission, but devices cleared under modern standards (post‑1997 for quality system regulation, and ideally within the last decade) provide a more predictable review environment.
Clean post‑market history. Search the FDA MAUDE database and recall listings for the predicate’s applicant and the specific device. Avoid predicates with Class I or Class II recalls related to safety issues.
Accessible performance testing. The predicate’s 510(k) summary should list specific standards or test methods. If the summary refers to proprietary or unspecified test protocols, you’ll have less visibility into FDA’s expectations.
Single predicate used. A single, well‑matched predicate is the strongest approach. A split predicate—using one device for intended use and another for technology—complicates the SE argument and often triggers additional data requests.

Create a simple scoring matrix (1–3 scale) and rank candidates. The highest‑scoring device becomes your lead predicate. Keep two runners‑up in case new information undermines your top choice.

The risks of weak or split predicates

A weak predicate is one that the FDA views as outdated or problematic. If your predicate relied on a withdrawn standard, or its clearance was based on clinical data that is no longer considered adequate, your 510(k) may be rejected as not substantially equivalent (NSE), forcing you down a de novo or PMA pathway.

A split predicate—citing one device’s intended use and another’s technology—carries its own risk. The FDA may determine that the combination of features in your device is not covered by either predicate, leading to an NSE determination. This is especially likely if the two predicates belong to different product codes or review divisions. If you must split predicates, request a pre‑submission meeting (Q‑Sub) to get FDA feedback on your strategy before you invest in testing.

Actionable takeaways

Start your predicate search early—before design freezes. The chosen predicate shapes verification testing, labeling, and risk management.
Use the FDA 510(k) database and product codes to build a pool of candidates, then narrow by recency and intended use.
Rank candidates on a handful of concrete criteria: intended use, technology, clearance date, post‑market record, testing visibility, and predicate count.
Aim for a single, recent predicate from the same product code whenever possible.
If a split predicate seems necessary, request FDA feedback through a Q‑Sub to validate your approach.