In U.S. medical device regulation, few decisions have as much downstream impact as predicate selection. For manufacturers pursuing the 510(k) pathway, the predicate device is not just a reference point, it often determines the shape of the submission, the depth of required evidence, and ultimately the likelihood of clearance.
Yet many teams still treat predicate analysis as a late-stage procedural step. In reality, experienced regulatory organizations know it is a strategic lever that should be engaged early. In 2026, that strategic importance has intensified: approximately 85% of 510(k) submissions that enter review receive a Substantially Equivalent (SE) decision; meaning roughly 15% do not obtain clearance.
The gap between those outcomes is often rooted in predicate strategy, not device quality. For AI/ML-enabled devices specifically, the median time to clearance in 2025 was 142 days, but a quarter of devices were cleared in under 90 days, demonstrating the potential for a rapid path to market when submissions are well-prepared.
The right predicate can streamline testing plans, clarify risk positioning, and support a clean substantial equivalence argument. The wrong one can trigger multiple deficiency cycles or even a Not Substantially Equivalent (NSE) determination. Understanding how to approach predicate selection with intention rather than assumption is essential for predictable 510(k) success in 2026.
What Is a Predicate Device?
A predicate device is a legally marketed medical device that serves as the reference point in a 510(k) submission. Manufacturers use it to demonstrate that their new device is substantially equivalent in intended use and technological characteristics.
In September 2023, the FDA issued draft guidance specifically addressing predicate selection: “Best Practices for Selecting a Predicate Device to Support a Premarket Notification [510(k)] Submission” (Docket FDA-2023-D-3134) recommends selecting a predicate that was cleared using well-established methods, meets or exceeds expected safety and performance, is without unmitigated use-related or design-related safety issues, and is without an associated design-related recall. While still in draft form as of May 2026, FDA reviewers are actively applying this lens. Manufacturers should incorporate these best-practice criteria into predicate evaluation from the outset, not treat them as optional guidance.
Types of Predicate Relationships
Predicate relationships exist along a spectrum. How closely the new device aligns with the predicate will directly influence FDA scrutiny.
Same Intended Use, Same Technology
This is the most straightforward and lowest-risk scenario. The new device shares both intended use and core technological characteristics with the predicate.
In these cases, submissions typically rely on well-structured bench testing and performance comparisons. When the equivalence story is clean and well supported, review tends to proceed more smoothly.
Same Intended Use, Different Technology
Innovation rarely stands still. Many modern devices introduce new materials, software features, or delivery mechanisms while maintaining the same intended use.
Here, the regulatory burden shifts. The central question becomes whether the technological differences introduce new questions of safety or effectiveness.
Manufacturers must clearly articulate:
- What is different
- Why the difference does not create new risk
- How testing supports equivalence
This is one of the most common pressure points in 510(k) review.
Multiple Predicate Approaches
In certain circumstances, manufacturers may consider multiple predicates to support different aspects of a device comparison. While this can be appropriate, it requires careful structuring.
The FDA generally expects a clearly defined primary predicate. Overly complex predicate frameworks can dilute the substantial equivalence argument or create confusion around intended use alignment. When multiple predicates are used, the logic must be explicit, disciplined, and easy for reviewers to follow.
Predicate with PCCP Authorization
The FDA finalized Predetermined Change Control Plans (PCCPs) guidance in December 2024. PCCPs allow manufacturers to pre-specify and pre-authorize certain iterative software modifications, including AI/ML model updates, without requiring a new 510(k) submission for each change. Importantly, if a predicate device had an authorized PCCP, the substantial equivalence comparison is made to the predicate before its PCCP-implemented changes. This means manufacturers must carefully research whether a candidate predicate holds a PCCP and what changes have been implemented under it; as the comparison is not to the device’s current state but to its state at original clearance.
In 2025, approximately 10% of all AI/ML device clearances included PCCPs, signaling growing industry adoption. Understanding the PCCP dimension of predicate selection is now an essential competency for any team developing AI-enabled medical devices
How to Select the Right Predicate
Predicate selection is both analytical and strategic. Strong teams begin the process early, often in parallel with product development. The FDA’s September 2023 Best Practices draft guidance adds four concrete criteria that should now anchor every predicate evaluation:
Select a predicate that was cleared using well-established methods, including FDA-recognized voluntary consensus standards, guidance documents, qualified medical device development tools, or widely accepted scientific literature. Select a predicate that meets or exceeds expected safety and performance. Select a predicate that is without unmitigated use-related or design-related safety issues. Select a predicate that is without an associated design-related recall.
These criteria work alongside, not instead of, the traditional intended use alignment, technological comparison, and risk analysis framework. A predicate that passes all four Best Practice criteria but has weak intended use alignment is still a poor choice. A predicate with strong intended use alignment but an associated recall history is now explicitly flagged by FDA as a risk. Teams should systematically document their evaluation against both frameworks.
Building a Predicate Comparison Strategy
A strong predicate comparison reads less like a checklist and more like a coherent regulatory argument. Reviewers should be able to quickly understand the logic, evidence, and conclusion.
Clinical and Performance Benchmarking
Effective comparison packages typically include:
- Clear indications comparison
- Side-by-side technological characteristics tables
- Performance testing summaries
- Biocompatibility and safety assessments
- Software or cybersecurity validation where applicable
Well-designed comparison tables remain one of the most powerful tools in a 510(k) submission because they reduce reviewer friction and make equivalence easier to evaluate.
Lessons from Deficiencies and NSE Outcomes
Across the industry, many predicate-related deficiencies follow familiar patterns:
- Intended use comparisons that are too vague
- Technological differences that are acknowledged but not fully justified
- Assertions of equivalence without supporting data
- Gaps in performance testing
- Overreliance on marketing language rather than technical evidence
Teams that proactively study these patterns are better positioned to avoid avoidable review cycles.
A strong predicate comparison reads less like a checklist and more like a coherent regulatory argument. Effective comparison packages include clear indications comparisons, side-by-side technological characteristics tables, performance testing summaries, biocompatibility and safety assessments, and software or cybersecurity validation where applicable.
A new dimension active from 2026: as of February 2, 2026, the FDA’s Quality Management System Regulation (QMSR) took effect, requiring manufacturers to align their quality management systems with ISO 13485:2016. For 510(k) submissions, QMS compliance is now a prerequisite reviewers actively examine; clearance may be withheld if QMS failures pose a serious risk. While QMS compliance is not part of the predicate comparison itself, it is now a parallel submission requirement that teams must ensure is in place before submitting. A strong predicate strategy can be undermined by a QMS deficiency that triggers a completely separate review concern.
Risks & Limitations of Predicate Reliance
While the predicate framework enables efficient market access, it is not without limitations. Regulatory expectations continue to evolve, and reliance on equivalence alone is not always sufficient.
Outdated Technology Concerns
The FDA has shown increasing sensitivity to predicates based on older technology. If a predicate reflects legacy design or outdated safety expectations, reviewers may request stronger justification or additional data.
Manufacturers should assess:
- The age of the predicate clearance
- Evolution of applicable standards
- Postmarket safety signals
- Availability of more modern comparators
Choosing the closest predicate is not always the safest strategic choice.
Evidence Gaps and Rising Expectations
Evidence expectations (particularly for software-driven, connected, and AI-enabled devices) continue to rise. A minimal comparison strategy that may have passed review years ago may now trigger requests for expanded validation.
Forward-looking teams build predicate strategies that anticipate this trajectory rather than reacting to it mid-review.
The FDA has shown increasing sensitivity to predicates based on older technology. Manufacturers should assess the age of the predicate clearance, evolution of applicable standards, postmarket safety signals, and availability of more modern comparators.
Recent data gives manufacturers a concrete benchmark: among 159 510(k) devices cleared with ML-enabled predicates in 2024, the median predicate age was 2.2 years (IQR 1.2–4.1 years), with 64.5% of predicates themselves being ML-enabled. This data suggests that for AI/ML devices specifically, using predicates cleared within the last 2–3 years is increasingly the norm and deviating significantly from that range may invite scrutiny. Selecting a predicate that reflects current technology expectations rather than legacy design is not just a best practice; it is increasingly the baseline reviewer expectation.
Predicate Analysis in Global Strategy
Predicate thinking does not exist in a U.S. vacuum. Manufacturers increasingly need regulatory strategies that scale globally.
For example, EU MDR equivalence requirements are typically more stringent and often demand deeper clinical justification. Technical documentation structures differ, and risk management expectations are frequently higher.
Organizations that treat U.S. predicate strategy and global equivalence planning as separate exercises often face rework and timeline pressure later. Early alignment reduces duplication and supports more efficient market expansion.
Predicate thinking does not exist in a U.S. vacuum. Manufacturers increasingly need regulatory strategies that scale globally. EU MDR equivalence requirements are typically more stringent, often demanding deeper clinical justification, and technical documentation structures differ significantly.
A meaningful 2025 development for global AI/ML device strategies: in August 2025, the FDA collaborated with Health Canada and the UK’s MHRA to publish five guiding principles for PCCPs in ML-enabled devices, establishing an international framework for adaptive oversight of AI/ML device modifications. For manufacturers pursuing parallel U.S., Canada, and UK market access, this trilateral PCCP alignment creates real documentation efficiency opportunities; a well-structured PCCP built for FDA can increasingly serve as the foundation for Health Canada and MHRA change management planning as well.
Role of Technology & RIM Systems
As product portfolios expand, predicate management becomes as much a data challenge as a regulatory one.
Modern Regulatory Information Management (RIM) systems enable teams to:
- Track historical predicate decisions
- Map technological characteristics across device families
- Maintain living comparison tables
- Monitor postmarket signals tied to predicates
- Support inspection and audit readiness
Digitizing predicate intelligence helps organizations move from reactive submission building to repeatable regulatory execution.
As product portfolios expand, predicate management becomes as much a data challenge as a regulatory one. Modern Regulatory Information Management (RIM) systems enable teams to track historical predicate decisions, map technological characteristics across device families, maintain living comparison tables, monitor postmarket signals tied to predicates, and support inspection and audit readiness.
The data scale is real: among 2024 ML-device clearances alone, 97.5% of 510(k) submissions cited an identifiable predicate, with predicate reuse across submissions remaining uncommon at 9.9%. For manufacturers managing multiple product lines across multiple submission cycles, the number of predicate relationships to track; each with its own safety history, recall status, PCCP authorization state, and standards alignment grows rapidly. Digitizing predicate intelligence is not a nice-to-have; it is a scaling necessity.
Conclusion
Predicate device selection is not an administrative formality, it is the structural foundation of a successful 510(k) strategy. In 2026, that foundation is more complex than ever: FDA Best Practice criteria now explicitly address recall history and safety profiles; QMSR compliance is a parallel submission prerequisite; PCCP authorizations require manufacturers to compare to predicates at their original cleared state; and evidence expectations for AI/ML devices continue to rise across cybersecurity, demographics, and performance transparency.
Organizations that approach predicate analysis with discipline, start early, and support their equivalence argument with clear, well-organized evidence consistently experience smoother FDA interactions and more predictable clearance timelines. As regulatory expectations continue to mature, the manufacturers that stand out will be those that treat predicate strategy as a core competency; supported by strong data, thoughtful risk analysis, and scalable regulatory infrastructure.
Q&A
Q: What is a predicate device?
A: A predicate device is a legally marketed medical device used as the reference in a 510(k) submission to demonstrate that a new device is substantially equivalent in intended use and technological characteristics.
Q: How do manufacturers select a predicate device?
A: Manufacturers evaluate intended use alignment, technological similarities, risk profile, regulatory status, and available performance data to identify the most appropriate legally marketed device for comparison.
Q: Can multiple predicates be used?
A: Yes, in certain situations multiple predicates may be used to support different aspects of a comparison. However, the FDA generally expects a clearly defined primary predicate and a well-justified rationale for any multi-predicate strategy.
Q: What are common risks in predicate comparison?
A: Common risks include weak intended use alignment, poorly justified technological differences, reliance on outdated predicates, insufficient performance data, and incomplete comparison tables.
Q: How do FDA predicate requirements differ from PMA?
A: The 510(k) pathway relies on demonstrating substantial equivalence to a predicate device, while the PMA pathway requires independent demonstration of safety and effectiveness through more extensive clinical and scientific evidence.
