A predicate device is a legally marketed device that you name as the benchmark for your own, and the entire 510(k) pathway rests on it: you are not proving your device is safe from scratch, you are demonstrating it is substantially equivalent to something already cleared. Choosing the predicate is therefore the highest-leverage decision in the whole submission. Pick well and your testing burden is defined and finite. Pick badly and you either face a demand for clinical data you never planned for, or a rejection that costs you months.

Projects House is an engineering firm, not a regulatory consultancy. This article is educational only and is not regulatory advice; work with a qualified regulatory professional on your actual submission.

What a predicate is doing for you

Substantial equivalence means your device has the same intended use as the predicate, and either the same technological characteristics or different characteristics that raise no new questions of safety and effectiveness. The predicate defines the comparison and, by extension, defines what you have to test. If the predicate was cleared with bench testing and biocompatibility, your path is likely bench testing and biocompatibility. If the only comparable device on the market was cleared with a clinical study, expect to be asked for clinical evidence too.

This only applies if your device is eligible for the pathway at all. Confirm first that the product is a device, and then which FDA device class and pathway it falls into — some Class II devices are exempt, novel low-risk devices may fit De Novo, and high-risk devices need PMA. Our guides to whether your product is a medical device and the FDA approval process for medical devices cover that upstream question.

What makes a predicate valid

  • Legally marketed. It was cleared through 510(k), or is otherwise legitimately on the market. A device that never received clearance cannot serve as a predicate.
  • Not withdrawn for safety. A device removed from the market because of safety or effectiveness problems is disqualified. Recalls and safety communications are worth checking.
  • Same intended use. This is stricter than "similar product." The indications-for-use statement is the text that matters, and a narrower or broader indication than yours weakens the comparison.
  • Comparable technology, or differences you can justify. Different does not automatically mean disqualified — it means you must show the difference raises no new safety questions, with data.
  • Same regulation and product code, ideally. Matching the classification regulation and product code keeps you inside an established framework with known special controls and recognized consensus standards.

Where to find candidates

Start with the public FDA databases: the 510(k) clearance database, the product classification database, and the device registration and listing data. Work backward from the classification: identify the regulation and three-letter product code that fits your device, then list every clearance under it. Read the clearance summaries — they describe what testing was accepted, which is exactly the intelligence you need.

Competitive labeling, instructions for use, and marketing materials tell you how similar devices describe their intended use. And patent literature is a surprisingly efficient map of the technical landscape: the searching techniques in our prior art search guide will surface the players and their approaches quickly, even though patents themselves have no regulatory standing here.

Comparing candidates

Build a comparison table before you commit. For each candidate, capture the intended use text, the technology, patient contact materials, energy source, key performance specifications, and the testing referenced in the clearance summary. Then judge on:

  • Closeness of intended use. The single biggest factor. A slightly older device with matching indications beats a newer device with different ones.
  • Testing burden implied. Two valid predicates can imply very different workloads. Prefer the one whose evidence package you can actually produce.
  • Clarity of the clearance summary. A detailed summary is a roadmap; a thin one leaves you guessing.
  • Material and contact match. A predicate with the same patient-contact materials simplifies your biocompatibility argument considerably.
  • Recency and standards. Very old clearances may predate the consensus standards now expected, so you may end up testing to modern standards regardless.

Naming more than one predicate is possible, and sometimes a reference device is used to support a specific characteristic. Combining predicates has to be done carefully — splicing the intended use of one with the technology of another is a classic way to invite a not-substantially-equivalent finding.

Common mistakes

  • Choosing on technical resemblance instead of intended use. The device that looks most like yours is often the wrong choice.
  • Picking the market leader by reflex. The best-selling device may have the broadest, hardest-to-match indications.
  • Choosing after the design is frozen. The predicate should shape requirements, not be reverse-fitted to a finished product.
  • Ignoring a software component. If your device includes software or is software, the documentation expectations shift substantially — see software as a medical device.
  • Assuming the predicate's testing is sufficient. Recognized standards and cybersecurity expectations evolve; an old clearance is a floor, not a ceiling.

What it means for the development plan

Once the predicate is chosen, it becomes an engineering input. Its performance specifications set your verification targets. Its materials set your biocompatibility strategy. Its clearance summary becomes a test matrix. Feed all of that into your requirements and traceability under FDA design controls so the submission is assembled during development rather than reconstructed afterward. It also sharpens the budget: knowing the exact test list early is the difference between a credible estimate and a guess, as our breakdown of FDA approval cost for a medical device makes clear.

Projects House develops medical devices with the regulatory endgame designed in from the first sketch, working alongside your regulatory consultants so engineering decisions and submission strategy stay aligned. Tell us about your device through the contact form to discuss the pathway.