Predicate Device Strategy for FDA 510(k) Submissions

Identifying a predicate device starts with confirming your device classification, product code, regulation number, intended use, and key technological characteristics. From there, you review legally marketed devices with relevant FDA clearance history and compare indications, design features, performance expectations, and risk profile. A strong predicate is not just similar on paper; it must support a credible substantial equivalence argument across the full 510(k) submission.

A predicate device is a legally marketed medical device used as the comparison point in a 510(k) submission. It helps demonstrate substantial equivalence by showing that your device has the same intended use and either the same technological characteristics or differences that do not raise new questions of safety and effectiveness. The predicate anchors the FDA's review of your submission strategy and supporting evidence.

Yes, in some cases a 510(k) may reference more than one predicate, particularly when different predicates support different aspects of the comparison. However, this approach must be handled carefully. The FDA expects a clear, logical rationale showing how the combined comparison still supports substantial equivalence without creating confusion, inconsistency, or new safety and effectiveness questions.

A defensible predicate aligns closely with your device's intended use, indications for use, technological characteristics, and regulatory classification. It should also provide a practical basis for comparing performance testing, labeling, software, biocompatibility, sterility, or other relevant evidence. The best predicate is not always the closest commercial competitor; it is the one that supports the clearest and most sustainable substantial equivalence argument.

A weak predicate choice can trigger FDA questions, Additional Information requests, or a finding that substantial equivalence has not been established. It may expose technological differences that require more testing, weaken your intended use comparison, or create inconsistencies across the submission. In practice, poor predicate selection often leads to longer review timelines, added remediation work, and a less efficient path to clearance.

No. Predicate analysis varies by device type, risk profile, technology, and the complexity of the intended use statement. Some submissions can rely on a straightforward comparison to a single well-matched predicate, while others require deeper analysis of software functions, performance standards, special controls, or multiple comparison points. The level of analysis should match the regulatory complexity of the device and the likely FDA review focus.

Ideally, yes. Predicate strategy should be established early enough to shape your testing plan, documentation structure, and claims strategy. The selected predicate influences which performance characteristics matter most, what standards may apply, and how differences must be justified. Finalizing the strategy before major testing reduces the risk of generating incomplete or misaligned evidence that later needs to be repeated or supplemented.

Yes, a Pre-Sub can be valuable when predicate selection is complex, the technology is novel, or there is uncertainty about testing expectations. A well-prepared Q-Sub package allows you to present the proposed predicate rationale, explain key differences, and ask targeted FDA questions before filing the 510(k). This can reduce uncertainty, improve planning, and help avoid preventable issues during formal review.