510(k), De Novo, PMA Pathways

A practical guide to 510(k), de novo, pma pathways for compliance practitioners.

What This Lesson Covers

510(k), De Novo, PMA Pathways is a key topic within AI in Healthcare (FDA). In this lesson you will learn the underlying regulation or standard, what it requires, how to operationalize it, and the common compliance pitfalls. By the end you will be able to apply 510(k), de novo, pma pathways in real compliance work with confidence.

This lesson belongs to the Sector-Specific Regulation category of the AI Compliance & Regulation Deep Dive track. AI regulation has crossed from niche policy concern to load-bearing operational requirement — teams that treat compliance as a core engineering discipline ship faster, win bigger deals, and avoid existential incidents.

Why It Matters

Master healthcare AI regulation. Learn FDA SaMD framework, 510(k) pathway, De Novo, PMA, predetermined change control plan (PCCP), HIPAA + AI, and EU MDR/IVDR for AI.

The reason 510(k), de novo, pma pathways deserves dedicated attention is that the gap between teams that take AI compliance seriously and teams that don't is widening every quarter. Two AI products with the same capabilities can end up in very different positions when regulators, customers, journalists, or affected individuals ask the hard questions. Compliance done well is a competitive advantage — not just a tax.

How It Works in Practice

Below is a worked example showing how to apply 510(k), de novo, pma pathways in real compliance work. Read it once, then map it to your own AI use cases and regulatory exposure.

# FDA SaMD AI/ML pathway
FDA_PATHWAYS = {
    "510(k)":  "Substantial equivalence to predicate; ~90% of AI medical devices",
    "De_Novo": "Novel low/moderate risk; no predicate available",
    "PMA":     "Class III high-risk; full clinical trials",
    "Pre_Cert": "Pilot for software-only manufacturers (paused as of 2025)",
}

# Predetermined Change Control Plan (PCCP) - approved Mar 2024
# Allows pre-authorized model updates without new 510(k) for each one
PCCP_REQUIREMENTS = {
    "scope": "Specific, pre-defined modifications to the AI model",
    "modification_protocol": [
        "Description of modifications to be made",
        "Methods used to develop, validate, implement modifications",
        "Performance metrics, statistical analysis plan",
        "Update procedures and version control",
    ],
    "impact_assessment": [
        "Risks, benefits, and intended use considered",
        "Patient safety, validity, reliability assessed",
    ],
}

# EU MDR/IVDR for AI (parallel system to FDA)
EU_MEDICAL_AI = {
    "MDR": "Medical Device Regulation - applies to most AI medical devices",
    "IVDR": "In Vitro Diagnostic Regulation - applies to diagnostic AI",
    "Risk_classes": "Class I, IIa, IIb, III - parallel to FDA's I/II/III",
    "Interaction_with_AI_Act": "AI medical devices = high-risk under EU AI Act + MDR/IVDR",
}

Step-by-Step Walkthrough

1. Confirm scope and applicability — Read the regulation's scope sections carefully. Many AI teams waste months on requirements that turn out not to apply to their use case.
2. Classify your AI use case — Risk tier, sector, decision type, jurisdiction. Most regulations are graduated — obligations follow risk.
3. Map specific obligations — List every concrete obligation that applies. Distinguish "do" requirements from "document" requirements from "monitor" requirements.
4. Build the evidence pipeline — Automate generation of the documentation, logs, and attestations that will be requested. Treat them like CI artifacts.
5. Establish the operating cadence — Quarterly internal reviews, annual external audits, ad-hoc on regulatory updates. Calendar everything.

When To Use It (and When Not To)

510(k), De Novo, PMA Pathways applies when:

• You operate in (or plan to enter) a jurisdiction or sector that the regulation covers
• Your AI use case meets the regulation's scope and risk thresholds
• The cost of non-compliance (fines, lost deals, reputation) outweighs the cost of compliance
• You need to demonstrate compliance to enterprise customers, partners, or regulators

It is the wrong move when:

• The regulation simply does not apply to your scope, sector, or risk tier — do not over-comply for vanity
• A simpler product change avoids the regulatory exposure entirely
• You are still iterating on the use case — lock in the scope first, then layer compliance
• You are using compliance as an excuse to delay shipping a feature you actually want to delay for other reasons

Compliance Operating Checklist

• Have you confirmed scope and applicability with named legal counsel?
• Is the use case classified under each applicable regulation, with documented reasoning?
• Are obligations mapped to specific owners (not "the team")?
• Is there an automated pipeline producing the required documentation and evidence?
• Are there scheduled reviews to refresh the compliance posture as the AI evolves?
• Is there a clear playbook for incident reporting and regulator engagement?

Next Steps

The other lessons in AI in Healthcare (FDA) build directly on this one. Once you are comfortable with 510(k), de novo, pma pathways, the natural next step is to combine it with the patterns in the surrounding lessons — that is where compliance goes from a one-off review to an operating system. AI compliance is most useful as a system, not as isolated reviews.