Manager
Regulatory Affairs | 10+ Years of Experience Medical device
Introduction
Selecting an appropriate predicate device is an important step in preparing an FDA 510(k) submission for Software as a Medical Device (SaMD) and Software in a Medical Device (SiMD). However, software developers often face a specific regulatory concern: what happens when no legally marketed medical software has exactly the same functionality, intended purpose, or technological design?
This situation is increasingly common as medical software incorporates artificial intelligence (AI), machine learning (ML), cloud-based processing, image analysis, clinical decision support, and connected healthcare technologies.
The absence of an identical software product does not automatically prevent a 510(k) submission. FDA’s substantial equivalence framework does not require two devices to be identical. Instead, manufacturers must establish the appropriate similarities in intended use and demonstrate that technological differences do not raise different questions of safety and effectiveness.
A structured predicate selection strategy, supported by software verification, validation, and performance evidence, can help manufacturers determine the appropriate regulatory pathway.
What Is Predicate Selection for SaMD and SiMD?
A predicate device is a legally marketed medical device used as a comparison to demonstrate substantial equivalence in an FDA 510(k) submission.
- SaMD (Software as a Medical Device): Software intended to perform one or more medical purposes independently, without being part of a hardware medical device.
- SiMD (Software in a Medical Device): Software that is embedded in, incorporated into, or operates as part of a hardware medical device and supports or controls its medical functionality
For both categories, predicate selection involves evaluating the device’s intended use, indications for use, technological characteristics, performance, and associated risks.
FDA does not require an identical software interface, algorithm, or technical architecture. However, the proposed device must meet the applicable substantial equivalence criteria.
Why Is Finding an Exact Software Predicate Difficult?
Medical software evolves faster than traditional medical devices. New products may introduce capabilities that were not available in previously cleared devices.
Common reasons include:
- Different algorithms: New AI/ML models may use different computational methods to generate diagnostic or clinical outputs.
- New intended applications: Software may introduce additional diagnostic functions or support different clinical decisions.
- Different data inputs: New products may process imaging, sensor readings, patient records, or real-time monitoring data.
- Cloud-based architecture: Software may use remote servers, connected platforms, or distributed processing instead of local installation.
- Advanced automation: Software may automate functions previously performed through manual clinical assessment.
These differences require careful regulatory evaluation rather than selecting a predicate based only on similar product descriptions.
How to Select a Predicate When No Exactly Similar Software Exists
If no valid predicate exists, manufacturers should not force a comparison with an unrelated device.
If no suitable predicate device exists, manufacturers should evaluate whether the De Novo classification pathway is appropriate. De Novo is intended for novel devices for which general controls, or general and special controls, can provide reasonable assurance of safety and effectiveness. Devices that require Class III regulatory controls generally require Premarket Approval (PMA), unless another applicable regulatory pathway is available.
A device presenting higher risks or requiring a different level of regulatory oversight may require a Premarket Approval (PMA) application.
What Should Manufacturers Prepare Before an FDA 510(k) Submission?
A well-supported SaMD/SiMD regulatory strategy should include:
- Device classification and product code assessment.
- Clearly defined intended use and indications for use.
- Predicate and reference device search documentation.
- Substantial equivalence comparison matrix.
- Software architecture and design documentation.
- Software verification and validation reports.
- Risk management and cybersecurity documentation.
- Clinical or analytical performance evidence, as applicable.
These documents help establish a clear regulatory rationale and support the FDA review process
Accelerate Market Access with End-to-End Regulatory Guidance
How Operon Strategist Supports SaMD/SiMD Regulatory Submissions
Operon Strategist provides medical device regulatory consulting and turnkey project support for manufacturers planning product development, regulatory approvals, and global market entry.
Support includes:
- FDA 510(k) regulatory strategy and predicate selection.
- Medical device classification and regulatory pathway assessment.
- Software technical documentation and DHF support.
- ISO 13485 quality management system implementation.
- Risk management and clinical evaluation support.
- CE MDR/IVDR and UKCA regulatory consulting.
- CDSCO registration and manufacturing/import licensing.
- US FDA, SFDA, and other international market registration support.
- Medical device manufacturing setup, GMP facility planning, and cleanroom compliance.
With experience supporting medical device projects across international markets, Operon Strategist helps manufacturers align regulatory requirements with product development and commercialization plans.
Get Your Medical Device Market-Ready with Expert Regulatory Support
FAQ's
Is a n identical predicate device required for SaMD FDA 510(k) clearance?
No. FDA does not require an identical predicate. The manufacturer must demonstrate the same intended use and establish that any technological differences do not raise different questions of safety and effectiveness.
Can AI-based medical software use a traditional software device as a predicate?
Potentially. The suitability depends on intended use, indications, technological characteristics, and whether the differences can be adequately supported with performance and safety evidence.
Can multiple predicate devices be used in an FDA 510(k) submission?
Yes. FDA permits multiple predicates in certain circumstances. However, the submission should identify a primary predicate, and a split-predicate approach is not acceptable.
What happens when no suitable predicate exists for a medical software product?
The manufacturer may evaluate the FDA De Novo pathway if the device meets the eligibility requirements. Higher-risk devices may require a PMA.
What evidence is required for SaMD and SiMD FDA submissions?
Evidence may include software verification and validation, risk management, cybersecurity documentation, algorithm performance testing, human factors evaluation, and clinical or analytical performance data, depending on the device.
Manager – Regulatory Affairs | 10+ Years of Experience
Medical device regulatory professional specializing in US FDA 510(k), EU MDR CE marking, Software as a Medical Device (SaMD), regulatory strategy, technical documentation, and risk management. Her expertise includes regulatory submissions, device classification, and regulatory gap assessments.
