Regulatory Pathways for Medical AI
Navigating the regulatory landscape for bringing an AI-based medical device to market. This section covers U.S. FDA requirements in depth, with orientation to international frameworks.
When Does Your AI Algorithm Become a Medical Device?
The SaMD definition, the Clinical Decision Support exemption (and why imaging AI almost always fails it), and the key question of intended use that determines regulatory status.
6.2Device Classification: Class I, II, and III
How the FDA classifies medical devices by risk, where most AI/ML tools fall, and what classification means for the regulatory burden you will face.
6.3The 510(k) Pathway: Substantial Equivalence to a Predicate
The most common pathway for AI medical devices. How to identify predicates, what "substantial equivalence" means, timeline and cost, and what a complete submission includes.
6.4The De Novo Pathway: First-in-Class Devices
When no predicate exists for your novel algorithm. The De Novo process, strategic advantages of creating a new classification, and how it differs from 510(k).
6.5Premarket Approval (PMA) and When It Applies
The highest-burden pathway, required for Class III devices. When PMA applies to AI/ML, what clinical evidence is required, and strategies for avoiding Class III classification.
6.6Breakthrough Device Designation: Faster Review for Innovative AI
Eligibility criteria, the application process, benefits (interactive review, priority review, data development exclusivity), and realistic expectations for timeline savings.
6.7Good Machine Learning Practice (GMLP): The 10 Guiding Principles
The FDA/Health Canada/MHRA consensus principles for AI/ML medical device development. What each principle means in practice and how to build compliance into your development process.
6.8Predetermined Change Control Plans (PCCP)
How to plan for post-market model updates before your initial submission. What a PCCP contains, why the FDA created this framework, and how it enables continuous learning without resubmission.
6.9Software Lifecycle Requirements: IEC 62304
The international standard for medical device software development. Safety classifications, required documentation, and what this means for how your engineering team must work.
6.10Design History File and Quality Management System Essentials
The documentation infrastructure regulators expect: design inputs, design outputs, verification, validation, risk management, and why a QMS must be in place before your first submission.
6.11International Regulatory Frameworks: EU MDR, Health Canada, and Beyond
A comparative overview of regulatory requirements across jurisdictions. CE marking under the EU Medical Device Regulation, Health Canada's SaMD framework, and the emerging impact of the EU AI Act.
6.12Post-Market Surveillance and Real-World Monitoring
Your obligations after clearance: adverse event reporting, complaint handling, performance monitoring, and the growing expectation for real-world performance data.