SaMD development
Software that is itself a medical device, built to an IEC 62304 process from the first requirement.
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.

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.
Software that is itself a medical device, built to an IEC 62304 process from the first requirement.
Requirements, architecture, risk notes, test records and traceability, written as the work happens.
iOS and Android apps that pair with your device and show results to patients and clinicians.
Cloud services that receive device data, store it and show it on dashboards.
Threat modeling, a software bill of materials and a penetration test before release.
We follow your ISO 13485 quality procedures and feed your ISO 14971 risk file.
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.
We agree the software safety class, the documents your submission needs and the release dates, together with your regulatory lead.
Requirements, risk notes, tests and traceability are written as the code is written, following an IEC 62304 process.
Verification tests, a penetration test and the software documentation package go to your team for the submission.
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.
Yes, we follow an IEC 62304 process for device software. Requirements, risk notes, tests and traceability are produced as the code is written.
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.
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.
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.
Yes. We build iOS and Android apps in Swift, Kotlin or Flutter, and the cloud services behind them.