510(k) Substantial Equivalence: How to Identify and Document Your Predicate Device

What Substantial Equivalence Actually Means

Substantial equivalence is the legal standard FDA uses to determine whether a new Class II medical device is as safe and effective as a legally marketed predicate device. If FDA determines that your device is substantially equivalent to a predicate, it receives 510(k) clearance. If FDA cannot make that determination — or determines that your device is not substantially equivalent — your device is automatically classified as Class III and requires a PMA unless you pursue De Novo classification.

The standard is established in Section 513(i) of the Federal Food, Drug, and Cosmetic Act. A device is substantially equivalent to a predicate if it: (1) has the same intended use as the predicate, and (2) has the same technological characteristics as the predicate — OR — has different technological characteristics that do not raise new questions of safety and effectiveness and the device is at least as safe and effective as the predicate.

This two-path structure is important to understand before selecting a predicate. Path 1 (same intended use, same technological characteristics) is straightforward — essentially a "same device, different manufacturer" comparison. Path 2 (same intended use, different technological characteristics with no new safety/effectiveness questions) is the path most new devices must navigate, and it is more demanding from an evidentiary standpoint.

The substantial equivalence determination is made by FDA on the basis of the information in your 510(k) submission. You are responsible for identifying the predicate, structuring the comparison, and providing the evidence FDA needs to make the determination. If you do not structure this correctly, FDA will issue a Not Substantially Equivalent (NSE) decision or an Additional Information (AI) request that adds months to your timeline.

How to Identify a Valid Predicate Device

A predicate device must be a legally marketed device — meaning it was cleared through a previous 510(k), was on the market before May 28, 1976 (a "preamendment device"), or was reclassified from Class III to Class II or Class I with special controls. A device that received PMA approval cannot serve as a 510(k) predicate.

Using the 510(k) database: FDA's 510(k) database (accessible at accessdata.fda.gov) is the primary source for identifying cleared predicates. Search by product code, device name, or indication. Product codes are particularly useful because they represent FDA's classification of device types — all 510(k)s with the same product code share the same classification and special controls, making them structurally similar predicates.

Predicate selection criteria: - Intended use match: The predicate's intended use must match your device's intended use. FDA defines intended use as the general purpose of the device. A device intended to measure blood glucose cannot be predicated on a device intended to measure blood oxygen, even if they share similar sensor technology. - Technological proximity: The closer your technology is to the predicate, the simpler your substantial equivalence argument. Predicates that differ significantly from your device in how they achieve their intended use will require more extensive performance testing and a more complex SE argument. - Regulatory status: Confirm that the predicate is still legally marketed. If the predicate was recalled, voluntarily removed from the market, or had its clearance rescinded, it may not be an acceptable predicate. FDA has discretion in these situations. - Special controls applicability: The predicate's classification determines the special controls that apply to your device. Selecting a predicate in a product code with extensive special controls means your device must meet all of those controls. Verify that your device can meet the applicable special controls before committing to a predicate.

Multiple predicates: FDA allows use of a "split predicate" — two different predicates, one for intended use and one for technological characteristics. Split predicates are acceptable but require careful documentation. You must clearly identify which predicate addresses intended use and which addresses technological characteristics, and explain why the split is appropriate. Overuse of split predicates or use of more than two predicates in a single submission will prompt increased FDA scrutiny.

Documenting the Substantial Equivalence Comparison

The substantial equivalence comparison is the analytical core of your 510(k) submission. FDA reviewers use the comparison to determine whether they can make a substantial equivalence finding. A poorly structured comparison is the most common reason for Additional Information requests in 510(k) reviews.

The comparison table format: FDA expects a side-by-side comparison table that addresses intended use and technological characteristics. The table should list each relevant characteristic, the predicate's specification or description, your device's specification or description, and whether they are the same or different. For any characteristic listed as "different," you must provide a separate explanation of why the difference does not raise new questions of safety and effectiveness.

Technological characteristics to address: The technological characteristics comparison should cover the features and design that are relevant to device safety and effectiveness — not an exhaustive engineering specification list. Relevant characteristics typically include: materials of construction (especially for patient-contacting components), energy type (electrical, mechanical, radiation), how the device interacts with the patient or user, software functionality if applicable, and sterility or biocompatibility characteristics if relevant.

Addressing performance differences: When your device has different technological characteristics, you must demonstrate that it is at least as safe and effective as the predicate. This is done through performance data — bench testing, biocompatibility testing, software testing, or clinical data. The testing must be adequate to characterize the specific difference and must be compared to an objective standard or to the predicate's performance where predicate data is available.

The substantial equivalence narrative: In addition to the comparison table, your 510(k) should include a narrative that walks FDA through your substantial equivalence argument — starting with intended use equivalence, addressing each technological difference, explaining the performance data that supports each conclusion, and arriving at a clear statement that the device is substantially equivalent to the predicate. FDA reviewers appreciate a well-organized narrative that anticipates questions.

Common Reasons FDA Issues NSE Decisions or AI Requests

Understanding why FDA declines to find substantial equivalence helps manufacturers structure stronger submissions. The most common SE-related issues that generate NSE decisions or AI requests fall into predictable categories.

Intended use mismatch: The most common SE rejection reason. If your device's intended use, as described in your indications for use statement, does not match the predicate's cleared intended use, FDA cannot make a substantial equivalence finding on intended use — which ends the SE analysis. Review the predicate's cleared indications for use statement carefully before finalizing your own.

New intended use through different technological characteristics: FDA has held that a device with the same labeled intended use but different technological characteristics that effectively expand the clinical utility of the device may be considered to have a new intended use. If your device's technology enables clinical applications that the predicate cannot perform, FDA may determine that this constitutes a new intended use even if the label language appears similar.

Inadequate performance data: When technological differences exist, performance data must be adequate to support the conclusion that those differences do not raise new safety or effectiveness concerns. FDA reviewers will assess whether the testing protocol is appropriate, whether the sample size is adequate, whether the test conditions reflect clinical use, and whether the acceptance criteria are justified. Inadequate performance data is the most common cause of Additional Information requests in technology-difference 510(k)s.

Novel technology without predicate performance basis: If your device incorporates technology that has not previously been cleared — a new energy modality, a new material, a new diagnostic principle — it may be difficult or impossible to demonstrate substantial equivalence because there is no performance baseline from a cleared predicate. These devices may be better candidates for De Novo classification rather than 510(k).

Predicate selection problems: FDA may challenge your predicate choice if the predicate is not closely enough related to your device, if you are relying on a recalled or withdrawn device, or if the predicate itself was cleared through a questionable SE finding. Building your submission on a strong, recently-cleared, product-code-specific predicate reduces this risk.

Using Q-Submissions to Validate Your Predicate Strategy

For devices with complex substantial equivalence arguments — novel technological characteristics, split predicates, or technology areas with limited cleared predicate history — a Pre-Submission (Q-Sub) meeting with FDA is an extremely effective risk reduction tool. FDA's Pre-Sub program allows manufacturers to receive written FDA feedback on predicate selection, comparison approach, and performance testing strategy before submitting the 510(k).

When to use a Q-Sub for predicate strategy: - Your device has technological characteristics that differ meaningfully from available predicates - You are considering a split predicate approach and want FDA concurrence - You are uncertain whether your intended use statement matches the predicate's cleared intended use - Your device incorporates technology (AI/ML, new materials, new energy types) that FDA has not previously cleared in your product code - You have received an NSE decision on a previous submission and want to revise your predicate approach

What to include in a predicate-focused Q-Sub: Your Q-Sub request should clearly present: your proposed predicate(s) with their 510(k) numbers, your proposed intended use comparison, the technological differences you have identified and your proposed approach to addressing them, the performance testing you are planning, and your specific questions for FDA. The more specific your questions, the more useful FDA's written feedback will be.

Acting on Q-Sub feedback: FDA's written Q-Sub feedback is not legally binding, but it is strong guidance. If FDA states in a Q-Sub that your proposed predicate is acceptable and your testing approach is appropriate, that position is unlikely to change during 510(k) review unless new information emerges. If FDA identifies concerns with your predicate strategy in a Q-Sub, address those concerns before submitting — not after receiving an AI request.

Timeline considerations: A Pre-Sub meeting request takes approximately 70 days from submission to FDA written feedback (under the current MDUFA V goals). Factor this into your 510(k) timeline. For first-time submissions or novel technology, the Q-Sub investment is almost always worth the time.

---

Ready to implement this? Download our FDA Pre-Submission Toolkit.