SaMD development and medical device software built with the documents your submission needs.

We build software as a medical device (SaMD) and the apps and cloud services around devices. The work follows an IEC 62304 process, and we produce the software documentation the FDA asks for. Your regulatory team owns the submission.

Glass measuring cylinder with a blue sphere on top, lit against a dark background

What does SaMD development involve?

Onix Health builds software as a medical device (SaMD) and the companion apps and cloud services around devices, following an IEC 62304 process from the first requirement. Requirements, architecture, risk notes, test records and traceability are written as the code is written, inside your ISO 13485 quality system. Before release we do threat modeling, a software bill of materials and a penetration test. Your regulatory team owns the FDA submission.

What we build: samd & medical device

1

SaMD development

Software that is itself a medical device, built to an IEC 62304 process from the first requirement.

2

FDA software documentation

Requirements, architecture, risk notes, test records and traceability, written as the work happens.

3

Companion mobile apps

iOS and Android apps that pair with your device and show results to patients and clinicians.

4

Device-to-cloud services

Cloud services that receive device data, store it and show it on dashboards.

5

Cybersecurity work

Threat modeling, a software bill of materials and a penetration test before release.

6

Work inside your quality system

We follow your ISO 13485 quality procedures and feed your ISO 14971 risk file.

How the project runs

  1. 1

    Free technical audit

    Five working days. We look at your current system, data and plans, and you get a written report with what we found and what we would do.

  2. 2

    Plan with your regulatory team

    We agree the software safety class, the documents your submission needs and the release dates, together with your regulatory lead.

  3. 3

    Build with the paperwork

    Requirements, risk notes, tests and traceability are written as the code is written, following an IEC 62304 process.

  4. 4

    Test, secure, hand over

    Verification tests, a penetration test and the software documentation package go to your team for the submission.

Technology and standards

  • Swift
  • Kotlin
  • Flutter
  • C++
  • Python
  • Node.js
  • React
  • PostgreSQL
  • AWS
  • Built to an IEC 62304 software process
  • FDA software documentation produced with the code
  • Works inside your ISO 13485 quality system
  • Feeds your ISO 14971 risk file
  • Penetration test passed before launch

Questions about samd & medical device

1

What is SaMD?

SaMD, or software as a medical device, is software that is a medical device on its own, without being part of hardware. An app that analyzes data to help diagnose a condition is one example.

2

Can you build to IEC 62304?

Yes, we follow an IEC 62304 process for device software. Requirements, risk notes, tests and traceability are produced as the code is written.

3

Will you get our software FDA cleared?

No, the FDA submission belongs to you and your regulatory team. We produce the software documentation the submission needs and answer technical questions during review.

4

What software documents does the FDA need for SaMD?

It depends on the device's risk level, and FDA guidance lists the documents for each level. They usually include requirements, architecture, risk analysis, test records and cybersecurity information.

5

Do you have a quality management system for medical devices?

We work inside your ISO 13485 quality system and follow its procedures. If you do not have one yet, plan it with a regulatory consultant before development starts.

6

Can you build the companion app for our device?

Yes. We build iOS and Android apps in Swift, Kotlin or Flutter, and the cloud services behind them.