Guides

GuideHealthcare

Does a Healthcare AI Product Require FDA Approval?

Atul Kumar Yadav

Atul Kumar Yadav

11 min read · Updated August 1, 2026

Start reading
1,000+

AI-enabled medical devices authorised by the FDA

Intended use

is the key test for whether AI is a device

3 pathways

510(k), De Novo, and PMA, by risk

Not automatic

many administrative and wellness AI tools are not devices

Based on public FDA information as of 2024 to 2026. This guide is educational, not regulatory or legal advice. Confirm any determination with qualified regulatory experts. Figures should be re-verified before publication.

Whether a healthcare AI product needs FDA clearance depends on its intended use, not on the fact that it uses AI. If the software is intended to diagnose, treat, cure, mitigate or prevent disease, or to drive a clinical decision, it is likely a medical device and may require FDA clearance or approval. If it supports administrative work, wellness, or provides information that a clinician independently reviews, it may fall outside FDA device regulation. The deciding factor is what the product claims to do and how much a clinician relies on it.

This matters because getting it wrong is costly in both directions: shipping a device-like AI without clearance is a serious regulatory risk, while treating an administrative tool as a device wastes time and money. Importantly, this guide is educational, not regulatory or legal advice. It explains how the FDA generally thinks about AI so you can have an informed conversation with qualified regulatory experts, who make the actual determination.

How does the FDA decide if AI is a medical device?

The FDA looks primarily at intended use: what the product is designed and marketed to do. Software that is intended to diagnose, treat or inform a clinical decision about a disease or condition generally meets the definition of a medical device, including Software as a Medical Device (SaMD). Software that does not make such a claim generally does not.

Two related questions shape the answer. First, what does the product claim, in its labelling and marketing, that it does? Second, how much does a clinician rely on its output, does the clinician independently review the basis for a recommendation, or act on it directly? Higher clinical reliance and stronger clinical claims push a product toward being a regulated device. This is why the same underlying model can be a device in one product and not in another.

Which AI products usually do not need FDA clearance?

AI products that support administrative work, wellness, or that simply inform a clinician who independently reviews the reasoning often fall outside FDA device regulation. These are lower-risk uses where the software is not making or driving a clinical decision.

Common examples that are frequently not devices (subject to their specific claims and design):

  • Administrative automation. Scheduling, prior authorization, claims and billing tools.
  • Ambient documentation. AI that drafts notes a clinician reviews and approves.
  • General wellness. Tools for general fitness or wellbeing without disease claims.
  • Certain clinical decision support. CDS that displays information a clinician can independently review, and does not drive time-critical decisions, may qualify as non-device under US criteria.

The caveat matters: "usually not a device" depends entirely on the specific claims and how the tool is used. A documentation tool that started giving diagnostic suggestions could cross the line. Design and marketing decisions change the answer.

Which AI products usually do?

AI products that diagnose, detect disease, drive treatment, or that a clinician relies on without independently reviewing the reasoning generally are medical devices and typically need FDA clearance or approval. These are higher-risk, clinically consequential uses.

Common examples that are frequently devices (again, subject to specifics):

  • Diagnostic AI. Software that detects or diagnoses a condition, for example from an image.
  • Triage that drives urgent action. AI that prioritises patients for time-critical care.
  • Treatment-driving software. Tools that recommend or adjust treatment relied upon directly.
  • Continuous monitoring with clinical alerts. Software that detects deterioration and drives clinical response.

If your AI makes a clinical claim or a clinician acts on its output without independently checking the reasoning, assume it may be a device and get expert input early.

What are the FDA pathways for AI medical devices?

If your AI is a medical device, the route to market depends on its risk class. There are three main pathways.

PathwayForIn short
510(k)Moderate-risk devices with a predicateShow substantial equivalence to an existing device
De NovoNovel low-to-moderate-risk devicesEstablish a new device type and controls
PMA (Premarket Approval)High-risk devicesThe most rigorous route, strong clinical evidence

The right pathway is a regulatory determination based on the device's risk and novelty. Most AI-enabled devices to date have come through the 510(k) or De Novo routes. Your regulatory experts decide the classification and pathway; we build the software and evidence to support it.

Intended use decides whether AI is a device, qualified regulatory experts confirm it, and building to the right quality bar from the start is what keeps you safe. As an engineering partner we build and evidence; we do not provide regulatory or legal advice.

Work with Noseberry

Want this turned into a plan for your business?

Book a free call and we will apply this playbook to your situation.

Book a free call

What is a Predetermined Change Control Plan (PCCP)?

A Predetermined Change Control Plan (PCCP) is an FDA mechanism that lets a device maker pre-specify certain future changes to an AI model, and how they will be validated, so those changes can be made without a new submission each time. It is important for AI because models often need to be updated as data evolves.

For AI product teams, a PCCP is a way to keep improving a model within agreed, pre-authorised limits rather than freezing it. Authoring a strong PCCP, and building the validation and monitoring to support it, is exactly the kind of technical and documentation work we do alongside your regulatory experts. The regulatory strategy is theirs; the engineering and evidence are where we help.

How do you find out if your product needs clearance?

You find out by defining your intended use and clinical claims precisely, then reviewing them with qualified regulatory experts. The determination is not something to guess or to decide on engineering grounds; it is a regulatory judgment based on what your product claims and how it is used.

A sensible sequence: write down exactly what your product does, what it claims, and how a clinician uses its output; compare that against the device definition and relevant FDA guidance; and engage regulatory experts early to confirm classification and pathway. Building correctly for either outcome from the start, with quality and documentation appropriate to the risk, keeps your options open and avoids expensive rework.

Common FDA-and-AI mistakes

The costly mistakes come from deciding regulatory questions informally or too late. Avoid these.

  • Assuming AI automatically needs, or does not need, FDA clearance. It depends on intended use.
  • Deciding classification on engineering grounds. It is a regulatory determination for qualified experts.
  • Letting scope creep change your device status. Adding diagnostic features can cross the line.
  • Building without quality controls, then trying to submit. Retrofitting evidence is very hard.
  • Ignoring model updates. Plan for change with a PCCP rather than freezing the model.
  • Treating a vendor as a regulatory consultancy. Engineering partners build; regulatory experts advise.

The through-line: intended use decides it, regulatory experts confirm it, and building to the right quality bar early keeps you safe.

How do you get started?

Start by writing a precise intended-use statement and clinical claims, then review them with qualified regulatory experts before you build features that could change your device status. Clarity on what you claim is the foundation for every regulatory decision that follows.

A practical first step is to define intended use and design the software to the appropriate quality bar, with the validation, traceability and documentation a submission would need, working alongside your regulatory team. This is how we approach medical device software development and responsible healthcare AI: we build correctly for the risk and support your submission, while your experts own the regulatory strategy.

Conclusion

Whether a healthcare AI product needs FDA approval depends on its intended use, not on the presence of AI. Diagnostic, treatment-driving and high-reliance clinical tools are generally medical devices that need clearance or approval; administrative, wellness and independently-reviewed decision-support tools often are not. The right route, 510(k), De Novo or PMA, follows from the device's risk and novelty.

Define your intended use precisely, engage regulatory experts early, and build to the right quality bar from the start, and you avoid both the risk of shipping an unclear device and the waste of over-engineering an administrative tool. This guide is educational, not regulatory advice, so pair it with qualified experts. If you want a technical partner to build clinical AI to the right standard, talk to our team.

Key takeaways

  • Whether healthcare AI needs FDA clearance depends on intended use, not on it being AI.
  • AI that diagnoses, treats or drives a clinical decision is generally a medical device (SaMD) and may need clearance or approval.
  • Administrative, wellness, and independently-reviewed decision-support tools often fall outside FDA device regulation.
  • The main pathways are 510(k), De Novo and PMA, chosen by risk and novelty.
  • A Predetermined Change Control Plan (PCCP) lets AI models be updated within pre-authorised limits.
  • Classification is a regulatory determination for qualified experts, not an engineering decision.
  • This guide is educational, not regulatory or legal advice; confirm with qualified regulatory experts.
Atul Kumar Yadav

About the author

Atul Kumar Yadav

Founder & CEO, Noseberry

Atul has spent over a decade building AI, data and cloud systems for enterprises and high-growth companies across 20+ countries, with 250+ products delivered.

Connect on LinkedIn

Take this guide with you, or turn it into a plan

Download the full PDF to keep, or book a free call and we will apply this playbook to your business.

Book a free call

Frequently asked questions

It depends on the product's intended use. If the AI is intended to diagnose, treat or drive a clinical decision about a disease or condition, it is likely a medical device that may require FDA clearance or approval. Administrative and wellness AI often is not a device. A qualified regulatory expert confirms the determination.

Intended use. Software intended to diagnose, treat, cure, mitigate or prevent disease, or to inform a clinical decision that a clinician relies on, generally meets the medical device definition, including Software as a Medical Device (SaMD).

Usually not, when it drafts documentation a clinician reviews and approves and makes no diagnostic or treatment claim. But this depends on its specific claims and use; adding clinical decision features could change the answer.

The three main pathways are 510(k) for moderate-risk devices with a predicate, De Novo for novel lower-risk devices, and PMA for high-risk devices. The right pathway depends on the device's risk and novelty and is determined by regulatory experts.

A Predetermined Change Control Plan lets a device maker pre-specify certain future model changes and how they will be validated, so the model can be updated within agreed limits without a new submission each time. It is important because AI models evolve.

Some CDS is exempt from device regulation under US criteria, for example when it displays information a clinician can independently review and does not drive time-critical decisions. Other CDS is a device. It depends on the function and how it is relied upon.

We can help you build to the right quality bar and prepare technical documentation, but the classification decision is a regulatory determination made by qualified regulatory experts. We work alongside them; we do not provide regulatory or legal advice.

It is a serious regulatory risk that can lead to enforcement action. If your AI may meet the device definition, engage regulatory experts before launch rather than after.

No. This guide is educational, explaining how the FDA generally approaches AI so you can have an informed conversation with qualified regulatory and legal experts, who make the actual determination.

Want this applied to your business?

Book a free call and we will turn this playbook into a plan for your situation.

Book a free call

Step 1 · Pick a date

Book a 30-min demo

30 minutes UTC
August 2026
SMTWTFS

Mon-Fri, 10:00-23:30 IST. Past dates and weekends are unavailable.