Skip to main content

Software as a Medical Device (SaMD)

Overviewโ€‹

Software is explicitly included in the MedDO definition. Standalone software intended for a medical purpose is regulated as a medical device in its own right. Qualification guidance MDCG 2019-11 applies in Switzerland.

Qualification โ€” Does This Software Qualify as a Medical Device?โ€‹

Key qualification tests (MDCG 2019-11):

  • Does the software perform an action on data beyond storage/archival/communication/search? โ†’ Potentially a medical device
  • Does its output drive clinical management or treatment decisions? โ†’ Likely a medical device
  • Is its output solely for administrative purposes? โ†’ Generally not a medical device

Classification of SaMDโ€‹

Apply the 22 MedDO classification rules, especially Rule 11 and Rule 22. Software IVDs use IVDO Annex VIII Rule 7. Typical classes: Class I (low-risk information to professionals), IIa (medium-risk decision support), IIb (high-risk diagnostic decisions), III (life-critical closed-loop control).

IEC 62304 โ€” Software Lifecycleโ€‹

MedDO Annex I ยง 17 requires software to be developed in accordance with the state of the art. IEC 62304 defines software safety classes A/B/C and development, maintenance, and change management requirements for each class.

AI and Machine Learningโ€‹

Swissmedic follows MDCG guidance on AI/ML. Key points: AI/ML software with medical intended purpose is regulated as a medical device; training/validation datasets must be documented; algorithm updates may constitute significant changes requiring new conformity assessment.

Official Sourcesโ€‹

Disclaimer

AI-assisted content for navigation only. Always verify against official Swissmedic and Fedlex sources. Not legal or regulatory advice.