Introduction
Most MedTech IP teams treat the 510(k) submission and the patent FTO as separate workstreams that happen to run in parallel. The regulatory team selects a predicate device based on substantial equivalence criteria — same intended use, comparable technology characteristics, equivalent safety and effectiveness. The IP team conducts an FTO based on the product’s feature set. The two teams hand their outputs to the same product manager and rarely speak to each other about the implications of each other’s decisions.
The problem with this separation is that predicate device selection — the core 510(k) strategic decision — directly determines which part of the patent landscape the FTO must cover. The predicate defines the technology comparison the FDA will make. It defines the product category the device is entering. And it defines the patent classification space where the most relevant blocking patents sit. A predicate selected without an IP lens may solve the regulatory equivalence problem while creating a patent clearance problem that a different predicate choice would have avoided.
This intersection between the 510(k) framework and FTO scope is systematically underappreciated in MedTech IP strategy. Our analysis of how to read the medical device patent landscape before entering a new therapeutic category covers the landscape structure for MedTech market entry. This article covers the more specific question: how the predicate device chosen for 510(k) clearance directly determines the scope of the FTO that must accompany it — and how aligning the two decisions produces better outcomes than running them in parallel without coordination.
How the 510(k) Predicate Framework Works — and Why It Matters for FTO
What substantial equivalence requires: The 510(k) process allows a medical device to reach the US market without a full PMA if it can be shown to be substantially equivalent to a legally marketed predicate device. Substantial equivalence requires the same intended use as the predicate, and either the same technological characteristics or, where the technology differs, evidence that the different technological characteristics do not raise new questions of safety and effectiveness and that the device is at least as safe and effective as the predicate. The FDA’s equivalence determination is made within the product code classification that the predicate defines — and that classification is the same one that organises the relevant patent landscape.
How predicate selection determines the technology comparison: By selecting a predicate device, the 510(k) submitter is telling the FDA: my device is equivalent to this specific cleared device in this specific product code. That choice of predicate and product code defines the technology space the FDA will assess the submission against. It is also the technology space where the most directly relevant blocking patents are held — because the patent landscape in a product code reflects the prior art and the existing IP positions in the same technology category the FDA uses to assess substantial equivalence.
Why the patent landscape shifts with every predicate choice: A device that could be cleared against multiple potential predicates in different product codes will face a different patent landscape depending on which predicate is selected. Predicate A in product code X sits in a patent landscape dominated by three large established device companies. Predicate B in product code Y sits in a landscape with fewer active patents and a more accessible whitespace picture. The regulatory team selects the predicate that produces the cleanest regulatory equivalence argument. The IP team, if not consulted, may later discover that the selected predicate has put the product in a denser and more expensive patent landscape than the alternative would have.
Three Ways Predicate Selection Changes Your FTO Scope
Scenario 1: Same intended use, same technology as the predicate. The simplest 510(k) case is also the simplest FTO case. If the new device uses the same technology as the predicate in the same product code, the FTO scope is defined by that product code classification and the patent holders active within it. The predicate holder’s own patents are the primary FTO reference — because they define the IP that protects the technology the new device is being compared against. The risk: if the predicate holder holds broad patents on the core technology, the new device may be in direct competition with a patent-protected product without a clear design-around path.
Scenario 2: Same intended use, different technology — the 510(k) technological equivalence argument. Where the new device achieves the same intended use through a different technological approach, the 510(k) requires a performance-based equivalence argument. For FTO, this scenario expands the scope because the new technology may cross patent classification boundaries. The device’s primary technology may sit in a different patent sub-classification from the predicate’s technology — and the FTO must cover both: the product code classification where the predicate sits and the technology classification where the new device’s components are patented.
Scenario 3: Split predicates — the most complex FTO picture. The FDA allows 510(k) submissions to use split predicates: one predicate for intended use and a different predicate for technological characteristics. A split predicate submission draws on two different product code classifications to establish substantial equivalence. For FTO, this is the most complex scenario: the device must be cleared against the patent landscape of both predicate product codes, plus any cross-domain blocking positions at the intersection of the two technology areas. Split predicate FTO requires a deliberately wider scope than single-predicate FTO.
The Predicate’s Patent Portfolio as an FTO Input
Why the predicate holder’s own patents matter: The predicate device was legally marketed before the new device’s 510(k) submission. This means the predicate holder has likely filed and received patents on the core technology during the predicate’s market life. Those patents cover the same technology characteristics that the 510(k) substantial equivalence argument will cite. A new device that is substantially equivalent to the predicate in its technology characteristics may therefore be at risk of infringing the predicate holder’s patents on those same characteristics — particularly where the equivalence argument cites specific design features, material properties, or performance parameters that are covered by the predicate holder’s patent claims.
How predicate patents define the technology boundary the FDA has accepted: The predicate’s patent portfolio — specifically the patents covering the technology features cited in the substantial equivalence comparison — is the best available map of what the FDA has already accepted as the defining technology of that product code. Patents covering the predicate’s performance-critical features identify exactly which technology elements are central to the device category. For FTO purposes, these are the highest-priority patents to assess, because they cover the technology the new device must match to achieve substantial equivalence.
Using predicate patent analysis to identify the minimum FTO scope: A predicate patent analysis — a targeted review of the patents held by the predicate device manufacturer covering the technology features cited in the substantial equivalence comparison — gives the FTO team a verified, FDA-anchored starting point for scope definition. It identifies the patent holders whose technology the new device is being compared against, the specific technology elements that are central to the comparison, and the classification codes where the most relevant blocking patents are concentrated. This is a more targeted and more FTO-relevant starting point than a generic product category search.
“The predicate device is not just the regulatory reference point for substantial equivalence. It is the IP landscape reference point for FTO scope. The technology features the FDA compares are the same technology features that the predicate holder has patented. Using the predicate’s patent portfolio as the FTO scope anchor gives the clearance analysis an FDA-validated foundation rather than a generically-defined product category search.”
How to Time FTO Around the 510(k) Submission Process
The 510(k) submission timeline creates specific FTO timing requirements. Our guide on when to conduct an FTO search sets out the general timing framework. For 510(k) submissions specifically, three timing points matter.
- Pre-submission FTO — before the predicate is finalised: The most valuable FTO timing is before the predicate device selection is locked. At this stage, the IP team can review the patent landscape implications of different predicate options and provide input to the regulatory team about which predicates expose the device to denser patent landscapes and which offer a cleaner FTO picture. This pre-predicate FTO is not a full clearance analysis — it is a comparative landscape assessment that informs the predicate selection decision from an IP perspective. For devices where multiple predicates are viable, this input can shift the predicate choice toward a less patent-dense technology category without compromising the regulatory equivalence argument.
- Post-clearance, pre-launch FTO update: 510(k) clearance from the FDA does not mean the device is patent-cleared. After 510(k) clearance is obtained, a full FTO analysis should be conducted against the patent landscape in the product code and technology classifications confirmed by the clearance decision. The clearance defines the product category with FDA finality — and the FTO should be scoped to that category specifically, rather than the broader product category that pre-submission landscape analysis may have covered.
- The De Novo pathway and its FTO implications: Where a device cannot establish substantial equivalence to any existing predicate, the De Novo pathway creates a new product code classification. For FTO, a De Novo submission means the product is entering a patent classification space that may have no direct predicate comparison — but it will be assessed against the closest existing technology classifications. The FTO must cover both the new product code that the De Novo creates and the existing technology classifications that were considered during the De Novo review.
Design-Around Options When a Predicate-Adjacent Patent Blocks
Modifying technology features vs. changing predicate selection: When the FTO identifies a blocking patent in the predicate’s technology space, there are two categories of response: modify the device technology to avoid the blocking patent claim (standard design-around) or reconsider the predicate selection to move the device into a different technology classification where the blocking patent does not apply. The second option is available only before the 510(k) submission is filed — after submission, the predicate is fixed and only technology modification is available. This is the strongest argument for aligning the FTO with the predicate selection process rather than running it as a post-submission exercise.
When a predicate change resolves the FTO problem: If the blocking patent is specific to the technology characteristics of a particular predicate, and a different predicate in a different product code would achieve the same intended use clearance without citing those technology characteristics, the predicate change is a regulatory design-around as well as an IP design-around. The device reaches the market through a different product code that sits in a less blocked patent landscape. The regulatory and IP teams working together before submission is the only way to identify this option before it closes.
When a predicate change creates a new FTO problem: Not every alternative predicate is a cleaner FTO choice. A predicate in a different product code may sit in a patent landscape that is equally dense or more complex. The comparative landscape assessment that should precede predicate finalisation maps this for all viable predicate options — giving the product team a complete picture of the IP implications of each regulatory pathway before the submission commits the choice.
How Our FTO Service Covers Medical Devices Under the 510(k) Framework
Our freedom to operate service covers medical device FTO aligned to the 510(k) predicate framework — predicate patent analysis to identify the minimum FTO scope, comparative landscape assessment for pre-predicate selection decisions, full FTO clearance post-510(k) clearance scoped to the confirmed product code classification, and split predicate FTO for devices that use multiple predicate product codes. For MedTech companies at the intersection of a 510(k) submission and a patent clearance requirement, we structure the FTO engagement to align with the regulatory milestones rather than running as a separate parallel process that misses the predicate selection window where the most valuable IP input can be made.
Planning a 510(k) submission? Predicate selection and FTO scope are the same decision made twice by different teams. Our service aligns the two — covering predicate patent analysis, comparative landscape assessment for predicate options, and full post-clearance FTO. → Contact Us
Conclusion: The Takeaway
The 510(k) predicate device and the FTO scope are not independent decisions. The predicate defines the technology space the FDA will assess the device against — and that technology space is the same one where the most relevant blocking patents are held. Running the regulatory and IP workstreams in parallel without alignment at the predicate selection stage means missing the window where a different predicate could have produced both a valid regulatory equivalence argument and a cleaner patent clearance picture.
MedTech companies that bring IP input to the predicate selection decision — before the submission locks the technology comparison — have access to a design-around option that the regulatory team cannot create alone and the IP team cannot access after the submission is filed. That alignment is the difference between a predicate that solves the regulatory problem and one that solves both the regulatory problem and the patent clearance problem at the same time.
