510(k) vs PMA: Differences in FDA Device Approval and Clearance
The Essential Guide to Requirements Management and Traceability
Chapters
- 1. Requirements Management
- Overview
- 1 What is Requirements Management? A Complete Guide
- 2 Why do you need Requirements Management?
- 3 Four Stages of Requirements Management Processes
- 4 Adopting an Agile Approach to Requirements Management
- 5 Status Request Changes
- 6 Conquering the 5 Biggest Challenges of Requirements Management
- 7 Three Reasons You Need a Requirements Management Solution
- 8 Guide to Poor Requirements: Identify Causes, Repercussions, and How to Fix Them
- 9 What Is a Requirements Management Plan? A Practical Guide
- 2. Writing Requirements
- Overview
- 1 Functional requirements examples and templates
- 2 What Is a Product Requirements Document? A Complete PRD Guide
- 3 What Is a User Requirement Specification (URS)? How to Write and Manage One
- 4 Identifying and Measuring Requirements Quality
- 5 How to Write a System Requirements Specification (SRS) Document
- 6 The Fundamentals of Business Requirements: Examples of Business Requirements and the Importance of Excellence
- 7 What Is a Compliance Risk Assessment? Steps, Framework, and Examples
- 8 Adopting the EARS Notation to Improve Requirements Engineering
- 9 Jama Connect Advisor™
- 10 Frequently Asked Questions about the EARS Notation and Jama Connect Advisor™
- 11 How to Write an Effective Product Requirements Document (PRD)
- 12 Functional vs. Non-Functional Requirements
- 13 What Are Nonfunctional Requirements and How Do They Impact Product Development?
- 14 What Is a Software Design Specification? Key Components + Template
- 15 Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS)
- 16 8 Do’s and Don’ts for Writing Requirements
- 17 Project Requirements: Types, Process, and Best Practices
- 3. Requirements Gathering and Management Processes
- Overview
- 1 Requirements Engineering
- 2 Requirements Analysis
- 3 A Guide to Requirements Elicitation for Product Teams
- 4 Requirements Gathering Techniques for Agile Product Teams
- 5 Requirements Gathering in Software Engineering: Process, Techniques, and Best Practices
- 6 Defining and Implementing a Requirements Baseline
- 7 Managing Project Scope — Why It Matters and Best Practices
- 8 Requirements Decomposition and How AI Supports It
- 9 How Long Do Requirements Take?
- 10 How to Reuse Requirements Across Multiple Products
- 4. Requirements Traceability
- Overview
- 1 What Is Traceability in Product Development? A Guide for Regulated Teams
- 2 Tracing Your Way to Success: The Crucial Role of Traceability in Modern Product and Systems Development
- 3 Bidirectional Traceability: What It Is and How to Implement It
- 4 What is Engineering Change Management (ECM)? A Complete Guide
- 5 Change Impact Analysis (CIA): A Short Guide for Effective Implementation
- 6 What is Meant by Version Control?
- 7 Key Traceability Challenges and Tips for Ensuring Accountability and Efficiency
- 8 The Role of a Data Thread in Product and Software Development
- 9 Unraveling the Digital Thread: Enhancing Connectivity and Efficiency
- 10 What is a Traceability Matrix? A Guide to Requirements Traceability
- 11 How to Create and Use a Requirements Traceability Matrix (RTM)
- 12 Requirements Traceability Matrix Pros and Cons: A Practical Guide
- 13 Live Traceability vs. After-the-Fact Traceability
- 14 Overcoming Barriers to Live Requirements Traceability™
- 15 Requirements Traceability, What Are You Missing?
- 16 Requirements Traceability: Links in the Chain
- 17 What Are the Benefits of End-to-End Traceability During Product Development?
- 18 FAQs About Requirements Traceability
- 19 Product Traceability for Regulated Industries: A Complete Guide to Audit-Ready Compliance
- 5. Requirements Management Tools and Software
- Overview
- 1 Selecting the Right Requirements Management Tools and Software
- 2 Why Investing in Requirements Management Software Makes Business Sense During an Economic Downturn
- 3 Why Word and Excel Alone is Not Enough for Product, Software, and Systems Development
- 4 Can You Track Requirements in Excel?
- 5 What Is Application Lifecycle Management (ALM)?
- 6 Is There Life After DOORS®?
- 7 Can You Track Requirements in Jira?
- 8 Checklist: Selecting a Requirements Management Tool
- 6. Requirements Validation and Verification
- 7. Meeting Regulatory Compliance and Industry Standards
- Overview
- 1 Understanding ISO Standards
- 2 Understanding ISO/IEC 27001: A Guide to Information Security Management
- 3 What is DevSecOps? A Guide to Building Secure Software
- 4 Compliance Management
- 5 What Is Functional Safety (FuSa)? Standards, Lifecycle, and Where Programs Fail
- 6 What is FMEA? Failure Mode and Effects Analysis Guide
- 7 TÜV SÜD: Ensuring Safety, Quality, and Sustainability Worldwide
- 8 What is IEC 62443? A Guide to Industrial Cybersecurity
- 9 DFARS Compliance: A Guide for Defense Contractors
- 10 CMMC vs FedRAMP: What’s Different and Which One Applies to You
- 8. Systems Engineering
- Overview
- 1 What is Systems Engineering? A Guide for Modern Engineering Teams
- 2 How Do Engineers Collaborate? A Guide to Streamlined Teamwork and Innovation
- 3 The Systems Engineering Body of Knowledge (SEBoK)
- 4 What Is MBSE? Model-Based Systems Engineering Explained
- 5 Digital Engineering Between Government and Contractors
- 6 Digital Engineering Tools: The Key to Driving Innovation and Efficiency in Complex Systems
- 9. Automotive Development
- Overview
- 1 Understanding IATF 16949: A Quick Guide to Automotive Quality Management
- 2 What Is ISO 21434? Automotive Cybersecurity Engineering Explained
- 3 What Is ISO 26262? A Guide to Functional Safety in Automotive
- 4 What Is ASIL? A Guide to Automotive Safety Integrity Levels in ISO 26262
- 5 What Is SOTIF? A Guide to ISO 21448 for ADAS Safety
- 10. Medical Device & Life Sciences Development
- Overview
- 1 The Importance of Benefit-Risk Analysis in Medical Device Development
- 2 Software as a Medical Device: Revolutionizing Healthcare
- 3 What’s a Design History File, and How Are DHFs Used by Product Teams?
- 4 Navigating the Risks of Software of Unknown Pedigree (SOUP) in the Medical Device & Life Sciences Industry
- 5 What Is ISO 13485? A Guide to Medical Device Quality Management Systems
- 6 What You Need to Know: ANSI/AAMI SW96:2023 — Medical Device Security
- 7 ISO 13485 vs ISO 9001: Understanding the Differences and Synergies
- 8 What Is IEC 62304? A Guide to Medical Device Software
- 9 What Is a Device Master Record (DMR)? Definition and FDA Requirements
- 10 Failure Modes, Effects, and Diagnostic Analysis (FMEDA) for Medical Devices: What You Need to Know
- 11 Embracing the Future of Healthcare: Exploring the Internet of Medical Things (IoMT)
- 12 What Is General Safety and Performance Requirements (GSPR)? What You Need To Know
- 13 What Is IEC 62366? A Guide to Medical Device Usability Engineering
- 14 What Is the Quality Management System Regulation (QMSR)?
- 15 510(k) vs PMA: Differences in FDA Device Approval and Clearance
- 11. Aerospace & Defense Development
- Overview
- 1 What Is ARP4754A? A Complete Guide to Civil Aircraft and Systems Development Assurance
- 2 Understanding ARP4761A: Guidelines for System Safety Assessment in Aerospace
- 3 What Is DO-254? A Complete Guide to Airborne Hardware Design Assurance
- 4 What Is DO-178C? A Complete Guide to Airborne Software Certification
- 12. Architecture, Engineering, and Construction (AEC industry) Development
- 13. Industrial Manufacturing & Machinery, Automation & Robotics, Consumer Electronics, and Energy
- 14. Semiconductor Development
- 15. AI in Product Development
- Overview
- 1 What Is AI in Product Development? A Complete 2026 Guide
- 2 AI Test Case Generation: A Complete Guide for Regulated QA Teams
- 3 Using AI to Write Software Requirements: What Works and What Doesn’t
- 4 What Is the Model Context Protocol (MCP) for Requirements Management?
- 5 AI for Systems Engineering: Benefits, Risks, and How to Start
- 6 How to Automate Requirements Management
- 7 Artificial Intelligence in Requirements Management
- 16. Risk Management
- 17. Product Development Terms and Definitions
Chapter 10: 510(k) vs PMA: Differences in FDA Device Approval and Clearance
Chapters
- 1. Requirements Management
- Overview
- 1 What is Requirements Management? A Complete Guide
- 2 Why do you need Requirements Management?
- 3 Four Stages of Requirements Management Processes
- 4 Adopting an Agile Approach to Requirements Management
- 5 Status Request Changes
- 6 Conquering the 5 Biggest Challenges of Requirements Management
- 7 Three Reasons You Need a Requirements Management Solution
- 8 Guide to Poor Requirements: Identify Causes, Repercussions, and How to Fix Them
- 9 What Is a Requirements Management Plan? A Practical Guide
- 2. Writing Requirements
- Overview
- 1 Functional requirements examples and templates
- 2 What Is a Product Requirements Document? A Complete PRD Guide
- 3 What Is a User Requirement Specification (URS)? How to Write and Manage One
- 4 Identifying and Measuring Requirements Quality
- 5 How to Write a System Requirements Specification (SRS) Document
- 6 The Fundamentals of Business Requirements: Examples of Business Requirements and the Importance of Excellence
- 7 What Is a Compliance Risk Assessment? Steps, Framework, and Examples
- 8 Adopting the EARS Notation to Improve Requirements Engineering
- 9 Jama Connect Advisor™
- 10 Frequently Asked Questions about the EARS Notation and Jama Connect Advisor™
- 11 How to Write an Effective Product Requirements Document (PRD)
- 12 Functional vs. Non-Functional Requirements
- 13 What Are Nonfunctional Requirements and How Do They Impact Product Development?
- 14 What Is a Software Design Specification? Key Components + Template
- 15 Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS)
- 16 8 Do’s and Don’ts for Writing Requirements
- 17 Project Requirements: Types, Process, and Best Practices
- 3. Requirements Gathering and Management Processes
- Overview
- 1 Requirements Engineering
- 2 Requirements Analysis
- 3 A Guide to Requirements Elicitation for Product Teams
- 4 Requirements Gathering Techniques for Agile Product Teams
- 5 Requirements Gathering in Software Engineering: Process, Techniques, and Best Practices
- 6 Defining and Implementing a Requirements Baseline
- 7 Managing Project Scope — Why It Matters and Best Practices
- 8 Requirements Decomposition and How AI Supports It
- 9 How Long Do Requirements Take?
- 10 How to Reuse Requirements Across Multiple Products
- 4. Requirements Traceability
- Overview
- 1 What Is Traceability in Product Development? A Guide for Regulated Teams
- 2 Tracing Your Way to Success: The Crucial Role of Traceability in Modern Product and Systems Development
- 3 Bidirectional Traceability: What It Is and How to Implement It
- 4 What is Engineering Change Management (ECM)? A Complete Guide
- 5 Change Impact Analysis (CIA): A Short Guide for Effective Implementation
- 6 What is Meant by Version Control?
- 7 Key Traceability Challenges and Tips for Ensuring Accountability and Efficiency
- 8 The Role of a Data Thread in Product and Software Development
- 9 Unraveling the Digital Thread: Enhancing Connectivity and Efficiency
- 10 What is a Traceability Matrix? A Guide to Requirements Traceability
- 11 How to Create and Use a Requirements Traceability Matrix (RTM)
- 12 Requirements Traceability Matrix Pros and Cons: A Practical Guide
- 13 Live Traceability vs. After-the-Fact Traceability
- 14 Overcoming Barriers to Live Requirements Traceability™
- 15 Requirements Traceability, What Are You Missing?
- 16 Requirements Traceability: Links in the Chain
- 17 What Are the Benefits of End-to-End Traceability During Product Development?
- 18 FAQs About Requirements Traceability
- 19 Product Traceability for Regulated Industries: A Complete Guide to Audit-Ready Compliance
- 5. Requirements Management Tools and Software
- Overview
- 1 Selecting the Right Requirements Management Tools and Software
- 2 Why Investing in Requirements Management Software Makes Business Sense During an Economic Downturn
- 3 Why Word and Excel Alone is Not Enough for Product, Software, and Systems Development
- 4 Can You Track Requirements in Excel?
- 5 What Is Application Lifecycle Management (ALM)?
- 6 Is There Life After DOORS®?
- 7 Can You Track Requirements in Jira?
- 8 Checklist: Selecting a Requirements Management Tool
- 6. Requirements Validation and Verification
- 7. Meeting Regulatory Compliance and Industry Standards
- Overview
- 1 Understanding ISO Standards
- 2 Understanding ISO/IEC 27001: A Guide to Information Security Management
- 3 What is DevSecOps? A Guide to Building Secure Software
- 4 Compliance Management
- 5 What Is Functional Safety (FuSa)? Standards, Lifecycle, and Where Programs Fail
- 6 What is FMEA? Failure Mode and Effects Analysis Guide
- 7 TÜV SÜD: Ensuring Safety, Quality, and Sustainability Worldwide
- 8 What is IEC 62443? A Guide to Industrial Cybersecurity
- 9 DFARS Compliance: A Guide for Defense Contractors
- 10 CMMC vs FedRAMP: What’s Different and Which One Applies to You
- 8. Systems Engineering
- Overview
- 1 What is Systems Engineering? A Guide for Modern Engineering Teams
- 2 How Do Engineers Collaborate? A Guide to Streamlined Teamwork and Innovation
- 3 The Systems Engineering Body of Knowledge (SEBoK)
- 4 What Is MBSE? Model-Based Systems Engineering Explained
- 5 Digital Engineering Between Government and Contractors
- 6 Digital Engineering Tools: The Key to Driving Innovation and Efficiency in Complex Systems
- 9. Automotive Development
- Overview
- 1 Understanding IATF 16949: A Quick Guide to Automotive Quality Management
- 2 What Is ISO 21434? Automotive Cybersecurity Engineering Explained
- 3 What Is ISO 26262? A Guide to Functional Safety in Automotive
- 4 What Is ASIL? A Guide to Automotive Safety Integrity Levels in ISO 26262
- 5 What Is SOTIF? A Guide to ISO 21448 for ADAS Safety
- 10. Medical Device & Life Sciences Development
- Overview
- 1 The Importance of Benefit-Risk Analysis in Medical Device Development
- 2 Software as a Medical Device: Revolutionizing Healthcare
- 3 What’s a Design History File, and How Are DHFs Used by Product Teams?
- 4 Navigating the Risks of Software of Unknown Pedigree (SOUP) in the Medical Device & Life Sciences Industry
- 5 What Is ISO 13485? A Guide to Medical Device Quality Management Systems
- 6 What You Need to Know: ANSI/AAMI SW96:2023 — Medical Device Security
- 7 ISO 13485 vs ISO 9001: Understanding the Differences and Synergies
- 8 What Is IEC 62304? A Guide to Medical Device Software
- 9 What Is a Device Master Record (DMR)? Definition and FDA Requirements
- 10 Failure Modes, Effects, and Diagnostic Analysis (FMEDA) for Medical Devices: What You Need to Know
- 11 Embracing the Future of Healthcare: Exploring the Internet of Medical Things (IoMT)
- 12 What Is General Safety and Performance Requirements (GSPR)? What You Need To Know
- 13 What Is IEC 62366? A Guide to Medical Device Usability Engineering
- 14 What Is the Quality Management System Regulation (QMSR)?
- 15 510(k) vs PMA: Differences in FDA Device Approval and Clearance
- 11. Aerospace & Defense Development
- Overview
- 1 What Is ARP4754A? A Complete Guide to Civil Aircraft and Systems Development Assurance
- 2 Understanding ARP4761A: Guidelines for System Safety Assessment in Aerospace
- 3 What Is DO-254? A Complete Guide to Airborne Hardware Design Assurance
- 4 What Is DO-178C? A Complete Guide to Airborne Software Certification
- 12. Architecture, Engineering, and Construction (AEC industry) Development
- 13. Industrial Manufacturing & Machinery, Automation & Robotics, Consumer Electronics, and Energy
- 14. Semiconductor Development
- 15. AI in Product Development
- Overview
- 1 What Is AI in Product Development? A Complete 2026 Guide
- 2 AI Test Case Generation: A Complete Guide for Regulated QA Teams
- 3 Using AI to Write Software Requirements: What Works and What Doesn’t
- 4 What Is the Model Context Protocol (MCP) for Requirements Management?
- 5 AI for Systems Engineering: Benefits, Risks, and How to Start
- 6 How to Automate Requirements Management
- 7 Artificial Intelligence in Requirements Management
- 16. Risk Management
- 17. Product Development Terms and Definitions
510(k) vs PMA: Differences in FDA Device Approval and Clearance
When a Food and Drug Administration (FDA) reviewer opens a premarket submission, the pathway your team selected determines the evidence standard, review timeline, user fee, and post-market obligations your company will carry for as long as the device stays on the market. Choose well, and the submission moves on the standard you planned around. Choose the wrong pathway, and you can add months of rework, misallocate clinical resources, and end up with a submission strategy that never matched the device’s risk profile in the first place.
For medical device teams preparing a first submission or launching a new product line, the 510(k) vs Premarket Approval (PMA) decision shapes every downstream activity. This guide walks through how the FDA classifies devices, where the two pathways diverge, how to determine which one applies to your device, and the documentation failures that most often delay a submission.
What Is the FDA Device Approval and Clearance Process?
FDA regulates medical devices through a risk-based classification system that assigns each device to one of three classes, and that classification determines which premarket pathway applies and how much evidence FDA requires before a device can reach the U.S. market.
Class I devices carry the lowest risk and are subject only to general controls. Most are exempt from premarket review entirely. Class II devices carry a moderate risk, require general and special controls, and typically undergo the 510(k) pathway. Class III devices support or sustain human life, present a potentially unreasonable risk of illness or injury, and require the most rigorous review through PMA. FDA’s device classification system is the starting point for any pathway decision.
510(k) Clearance Explained
The 510(k) premarket notification derives its authority from Section 510(k) of the Federal Food, Drug, and Cosmetic Act (FD&C Act) and is a comparative pathway. FDA evaluates whether the new device is substantially equivalent to a legally marketed predicate device.
FDA’s substantial equivalence review first compares the new device’s intended use with that of the predicate. If the intended use differs, the FDA finds the device Not Substantially Equivalent (NSE). If the intended use matches, the FDA then evaluates whether differences in technological characteristics raise new questions of safety or effectiveness. The new device may differ from the predicate in materials, design, or energy source if the submitter demonstrates the device is at least as safe and effective.
Clinical data is conditional for 510(k) submissions, not universally required. When technological differences raise new safety questions, FDA can and does request clinical evidence during substantive review. The FY 2026 standard user fee is $26,067, with a reduced fee of $6,517 for small businesses with gross receipts of $100 million or less.
PMA Approval Explained
PMA is the FDA process for evaluating the safety and effectiveness of Class III medical devices under Section 515 of the FD&C Act. Class III includes devices such as implantable pacemakers, breast implants, and implantable cardioverter defibrillators.
Before approving a PMA, the sponsor must provide valid scientific evidence demonstrating reasonable assurance of safety and effectiveness for the device’s intended use, without reference to any predicate. Clinical studies supporting a PMA must comply with Investigational Device Exemption (IDE) regulations, along with informed consent and Institutional Review Board (IRB) oversight requirements.
FDA’s PMA process uses an 180-day review clock. The FY 2026 standard user fee is $579,272, with a small business fee of $144,818. PMA development costs extend well beyond the application fee itself, especially when clinical studies and post-approval obligations are involved.
510(k) vs PMA: The Core Differences
The two pathways diverge across nearly every dimension that affects submission planning, resource allocation, and post-market compliance. The table below summarizes where, using the FY 2026 Medical Device User Fee Amendments (MDUFA) fee schedule, the figures.
| Dimension | 510(k) Clearance | PMA Approval |
| Outcome terminology | “Cleared” | “Approved” |
| Primary device classes | Class I (non-exempt), Class II | Class III |
| Legal standard | Substantial equivalence to the predicate | Valid scientific evidence of safety and effectiveness |
| Predicate required | Yes | No |
| Clinical data | Conditional | Generally required |
| FY 2026 standard user fee | $26,067 | $579,272 |
| Annual periodic report | Not required | Required, $20,275/yr |
| Post-market change reporting | New 510(k) may be required | PMA supplement required (FY 2026 standard supplement fee $64,434, real-time supplement fee $16,108) |
| Post-Approval Studies | Not applicable | May be required as a condition of approval |
PMA fees are substantial, which makes total lifecycle cost planning a material part of the business case. Both pathways carry identical obligations under Medical Device Reporting (MDR) rules, Quality System and Good Manufacturing Practice (GMP) requirements, and Section 522 postmarket surveillance studies.
How to Determine Which Pathway Your Device Requires
Start with the FDA Product Classification Database. Searching by device name identifies the closest generic device type and its three-letter product code, which helps you determine the likely submission pathway.
If the database indicates 510(k) is required, the next step is searching for a single legally marketed predicate with the same intended use, since split predicates, or relying on different devices for intended use and technological characteristics, are inconsistent with the 510(k) regulatory standard. A valid predicate must meet one of these conditions:
- Pre-amendment marketing: The device was legally marketed before May 28, 1976.
- Downward reclassification: FDA reclassified the device from Class III to Class II or I.
- Prior substantial equivalence: The device was found to be substantially equivalent through a prior 510(k) submission.
- De Novo authorization: The device was granted marketing authorization via the De Novo process.
When no suitable predicate exists, the device team must assess whether general controls alone, or general and special controls together, provide reasonable assurance of safety and effectiveness. If controls are sufficient and the device carries low-to-moderate risk, the De Novo classification pathway applies. If controls are insufficient and the device is high-risk or life-sustaining, PMA is the route.
For novel devices without predicates, De Novo can be a strategic choice. When the FDA grants a De Novo request, a new classification regulation is established for the entire device type, and the newly classified device becomes a valid predicate for future 510(k) submissions. The De Novo fee is materially lower than the standard PMA application fee.
For ambiguous situations, such as novel technology, unclear classification or regulatory pathway questions, or potential combination products, FDA recommends seeking early feedback through a Pre-Submission (Q-Sub) before committing to a pathway. For formal combination-product jurisdiction determinations, sponsors may instead need a Request for Designation.
Common Documentation Failures That Delay FDA Submissions
FDA uses the Refuse to Accept (RTA) checklist to screen submissions for basic completeness before substantive review. A 510(k) with documentation failures can substantially extend the review process because hold time from Additional Information (AI) requests does not count toward the review clock.
Three deficiency patterns recur most frequently across both pathways:
- Broken requirements traceability: Missing links between requirements and verification are a common inspection finding because ambiguous design inputs make it difficult to demonstrate that those inputs have been verified.
- Incomplete design history file: Under design control requirements, manufacturers must maintain a Design History File (DHF) demonstrating that the design was developed in accordance with design controls. FDA warning letters have cited broad DHF deficiencies, including missing design plans, input requirements, outputs, reviews, risk analyses, verification and validation, and design transfer documentation.
- Risk file traceability gaps: ISO 14971:2019 requires the risk management file to provide traceability for each identified hazard, and reviewers have flagged misapplication of benefit-risk analyses in ways that do not support the record’s regulatory purpose.
For PMA submissions specifically, FDA regulations state that applications lacking required information may not be approved, and FDA may refuse to file an application that is not sufficiently complete to permit substantive review. DHF integrity and traceability deficiencies identified during pre-approval facility inspections can independently block PMA approval, regardless of the adequacy of the written submission.
How Jama Connect® Supports 510(k) vs PMA FDA Device Approval
When teams manage design inputs, outputs, risk items, and test cases across disconnected systems, the traceability gaps described above surface late, delaying submissions. Jama Connect is a cloud-based requirements management and traceability platform for complex, regulated product development that connects those records in a single system across the full development lifecycle, so coverage gaps are identified early, while there is still time to close them, rather than during an RTA screen.
Its medical device framework aligns with ISO 13485, 21 CFR 820.30, IEC 62304, and ISO 14971, and Review Center supports 21 CFR Part 11-compliant electronic signatures for formal sign-off. Dexcom reported a 60% improvement in systems engineering efficiency with Jama Connect by centralizing requirements and applying Live Traceability™ throughout its development process.
Choose the Right FDA Pathway Early
The pathway decision is not only a regulatory formality at the front of a program. It sets the clinical evidence you have to generate, the people and budget you commit, and the reporting you owe the FDA for the life of the device, which is why a pathway chosen late or for the wrong reasons is expensive to unwind.
Jama Connect supports this work by keeping requirements, design outputs, risk records, and verification linked in one place, so the traceability an FDA reviewer expects is a byproduct of development rather than a reconstruction effort before submission. If your team is spending more time assembling documentation than building the device itself, start a free 30-day trial of Jama Connect.
Frequently Asked Questions About 510(k) vs PMA
Is a 510(k) faster than a PMA?
Yes, by a significant margin. A 510(k) is typically reviewed on a shorter timeline than an original PMA, and the real gap is often larger because PMA applicants must complete IDE-approved clinical trials before they can even submit. Third-party review through the Accredited Persons Program can shorten 510(k) review in some cases, and clean DHF and traceability practices reduce preparation time before submission.
Can a device switch from a PMA to a 510(k) pathway?
It can, but only through formal FDA reclassification. FDA must change the device type from Class III to Class II or Class I after determining that general controls alone, or general and special controls together, provide reasonable assurance of safety and effectiveness. Manufacturers can also petition the FDA for downward reclassification. FDA initiated a proceeding to reclassify automated external defibrillators (AEDs) from Class III to Class II amid concerns about recalls and device malfunctions over a multi-year period.
What happens if no predicate device exists?
The De Novo classification pathway under Section 513(f)(2) of the FD&C Act provides a route for novel devices that carry low-to-moderate risk but lack a predicate. De Novo applies to new device types that fall outside the 510(k) framework because there is no legally marketed predicate, yet do not require a PMA because general and special controls can establish reasonable assurance of safety and effectiveness. FDA reviews these requests on a separate track, and the De Novo fee is materially lower than the PMA application fee.
Does FDA clearance mean the same thing as FDA approval?
No, and the distinction carries legal consequences. A 510(k) results in “clearance,” meaning the FDA found the device substantially equivalent to a predicate, while a PMA results in “approval,” meaning the FDA independently determined the device is safe and effective based on valid scientific evidence. Describing a 510(k)-cleared device as “FDA-approved” in marketing materials creates a misbranding risk under the FD&C Act and exposes the company to advertising and consumer protection disputes.
This article was authored by Tom Rish and published on June 18, 2026.
Book a Demo
See Jama Connect in Action!
Our Jama Connect experts are ready to guide you through a personalized demo, answer your questions, and show you how Jama Connect can help you identify risks, improve cross-team collaboration, and drive faster time to market.