Compliance & Regulatory

    FDA SaMD (Software as a Medical Device)

    SaMD, or software as a medical device, is FDA's classification for software intended for a medical purpose, such as diagnosis or treatment guidance, that runs independently of hardware. Whether a product qualifies as SaMD changes its entire regulatory and development path, so this needs to be determined during discovery, not after launch.

    Key takeaways

    • FDA class for software with a medical purpose, standalone from hardware
    • Intended use and claims determine whether a product qualifies
    • Risk tier scales validation and documentation expectations
    • Classification changes timeline, cost, and lifecycle from the start
    • Overstated claims can push a tool into a stricter category

    What FDA SaMD means

    SaMD is the FDA's classification for software intended to perform a medical purpose, such as informing diagnosis or guiding treatment, without being part of a hardware medical device. The defining question is intended use: what the software claims to do and how much a clinician or patient is expected to rely on it. Software that only stores or displays data generally sits outside this category, while software that interprets data to drive a medical decision may fall inside it.

    Classification is risk-based and depends on both the seriousness of the condition and how directly the software's output informs care. Higher-risk intended uses carry more rigorous expectations around clinical validation, documentation, quality processes, and post-market monitoring. This is why the same underlying feature can sit on very different regulatory paths depending on the claims you make about it.

    The practical consequence is that regulatory status has to be settled during discovery, not discovered after launch. A product that qualifies as SaMD needs a development lifecycle built around design controls, traceability, and evidence, which changes timelines, cost, and how the team works. Marketing language and product claims also matter, since overstating what the software does can pull an otherwise lower-risk tool into a stricter category.

    Explore this on Agnotic

    Where FDA SaMD shows up in how we build.

    Frequently asked questions

    It comes down to intended use: whether the software is meant to inform or drive a medical decision such as diagnosis or treatment. Software that only stores, transfers, or displays data typically falls outside the category, while software that interprets data clinically may fall inside it. This is a regulatory determination best made with qualified guidance during discovery, not a casual self-assessment.

    Talk through your build with an engineer

    Tell us what you're building and the systems it needs to talk to, and we'll map a clear, compliant path to launch.