510(k) Predicate Device is a legally marketed medical device that a manufacturer cites in a Premarket Notification to demonstrate substantial equivalence for a new device. The predicate shares the same intended use and comparable technological characteristics, letting the U.S. FDA clear the new device without requiring full premarket approval.
What is a 510(k) Predicate Device?
The 510(k) pathway, named after section 510(k) of the U.S. Federal Food, Drug, and Cosmetic Act, lets a manufacturer market a moderate-risk device by showing it is substantially equivalent to a device already on the market. That comparison device is the predicate. A valid predicate must be legally marketed: cleared through an earlier 510(k), grandfathered before 1976, or down-classified from premarket approval.
Substantial equivalence does not mean identical. The new device and its predicate share the same intended use, and either the same technological characteristics or different ones that do not raise new questions of safety and effectiveness. The predicate anchors the entire submission to FDA’s Center for Devices and Radiological Health (CDRH).
Why a 510(k) Predicate Device matters in medical device development
Predicate choice shapes cost, timeline, and clearance odds. Pick a strong predicate, and the submission moves through review with fewer Additional Information requests. Pick a mismatched one, and you risk a Not Substantially Equivalent (NSE) decision, which can push the device toward De Novo classification or full Premarket Approval (PMA), adding months or years.
The predicate also defines the testing burden. Differences between your device and the predicate drive what verification and validation data the FDA expects. A poorly scoped comparison can surface late, after design freeze, when changes are expensive. For Class II devices, the predicate is often the single most consequential regulatory decision a team makes early.
How the 510(k) predicate comparison works
Selecting and defending a predicate follows a repeatable sequence:
- Search FDA’s 510(k) database and product classification database for legally marketed devices with the same intended use and product code.
- Confirm the candidate is valid and not subject to a safety recall, which the FDA discourages citing.
- Build a side-by-side comparison of intended use, indications, design, materials, energy source, and performance specifications.
- Identify every difference and decide whether it raises new questions of safety or effectiveness.
- Generate bench, biocompatibility, electrical safety, or software data to close those gaps.
- Document the equivalence argument, mapping each characteristic to evidence.
This work sits inside the design controls required by FDA 21 CFR Part 820.30 and a quality system aligned with ISO 13485. Risk management per ISO 14971 informs which differences matter. For devices with software, IEC 62304 governs the lifecycle evidence; electrical devices are tested against the IEC 60601 family. You may cite more than one predicate, but the primary intended use must trace to a single predicate.
Common challenges and best practices
The frequent failure is intended-use drift. Teams pick a predicate that looks similar technically but serves a different clinical purpose, and the FDA rejects the equivalence claim. Match intended use first, technology second.
Split predicates cause trouble too. Borrowing intended use from one device and technology from another invites scrutiny and often an NSE outcome. Keep the intended-use predicate clean.
Citing a recalled predicate is a known risk. FDA best practice steers submitters toward predicates without unresolved safety problems and toward more recent clearances that reflect current performance expectations. Older predicates can still be valid, though they may not represent the state of the art reviewers now expect.
Lock the predicate during early feasibility, not after design freeze. Run a gap analysis against the predicate’s known performance data, then plan verification testing to match. Keep a clear comparison table in the Design History File so the equivalence story stays auditable.
How SJML helps with 510(k) Predicate Device
SJML provides regulatory strategy and device classification as part of its Compliance-as-a-Service offering, including FDA 510(k) preparation and the technical files and Design History File that support a submission. The QARA team helps identify a defensible predicate, structure the substantial equivalence comparison, and scope the verification and validation evidence needed to close gaps. Because design, engineering, and in-house testing labs for electrical safety, EMC, and reliability sit under one roof, performance data for the comparison can be generated alongside development. Risk management to ISO 14971 and quality systems to ISO 13485 are built in.
Frequently asked questions
A valid predicate is a legally marketed device with the same intended use as the new device, and either equivalent technological characteristics or differences that do not raise new questions of safety and effectiveness. It must have reached the market lawfully, through prior 510(k) clearance, pre-1976 status, or down-classification, and should not be under an unresolved safety recall.
Yes. A submission can cite multiple predicates, often a primary predicate plus additional ones, when a single device does not cover every feature. The intended use must trace to one primary predicate. Mixing intended use from one device and technology from another, a split predicate, is discouraged and frequently leads to a Not Substantially Equivalent finding.
Without a valid predicate, the 510(k) pathway is closed. A low-risk to moderate-risk device with no predicate can pursue the De Novo classification request, which creates a new classification and can later become a predicate itself. Higher-risk devices generally require Premarket Approval (PMA) with clinical evidence rather than a substantial equivalence argument.
No. The predicate can be any legally marketed device, regardless of manufacturer. Submitters routinely cite competitor devices as predicates. You do not need permission from the predicate’s manufacturer, since the comparison relies on publicly available clearance information and the device’s established intended use and characteristics.
Related terms
- Substantial Equivalence
- Premarket Notification (510(k))
- De Novo Classification
- Premarket Approval (PMA)
- Design History File (DHF)
