SaMD Software Validation

Software as a Medical Device (SaMD) Validation & Cybersecurity Regulations

Updated: Jun 2025QTC Global Compliance TeamRegulatory reference content

Introducing IEC 62304 lifecycles for SaMD and embedded firmware, software safety classifications, and compilation of U.S. FDA/EU cybersecurity vulnerability document packs.

Key answer

Medical device software (both SaMD and embedded firmware) must follow the IEC 62304 software lifecycle. Depending on safety severity, software is classified into Class A, B, or C. For U.S. and EU filings, manufacturers must include cybersecurity management plans, Software Bill of Materials (SBOM), static analysis, penetration test data, and vulnerability management procedures.

Core Controlled Stages in IEC 62304

Software auditors inspect the Traceability Analysis to verify compliance from software requirements specifications (SRS), design details, unit testing, to system integration tests.

  • Software Requirements Specification (SRS): defining inputs, data transmission, and UI risks
  • Software architecture & detailed design: separating modules to prevent cascading errors
  • Verification: unit tests, integration tests, and system validation (scripts and bug tracking logs)

FAQ

What is an SBOM and why does the FDA mandate it?+

An SBOM lists all third-party libraries, open-source code, and commercial modules in the device software. The FDA mandates this to allow regulatory bodies and healthcare organizations to identify affected medical hardware when global software security vulnerabilities arise.

Next steps

If this topic applies to your product, facility, or supply chain requirement, start by confirming the target market, customer-required standard, existing documents, audit history, and expected timeline.