Services · Build

Software as a Medical Device development

The full SaMD lifecycle: analysis, software validation, development, QA, deployment and process documentation, in line with the Medical Device Regulation, FDA requirements and international standards. For startups and large healthcare projects alike.

IEC 62304ISO 13485ISO 14971EU MDR / FDA

Built for certification from the start

We design software that reduces human data-entry errors and duplicated processes, and we prepare the certification evidence as part of the development lifecycle, not after it.

Our team’s experience developing software as a medical device is backed by knowledge of the EU Medical Device Regulation, healthcare regulatory requirements and safety risk management.

Development and certification follow

  • US FDA regulation requirements
  • ISO 13485:2016 — quality management systems for regulatory purposes
  • IEC 60601-1 — medical electrical equipment and systems
  • ISO 14971 — application of risk management to medical devices
  • IEC 62304 — medical device software lifecycle processes
  • IEC 62366 — usability engineering for medical devices
  • Cybersecurity requirements
See it in practice

Case study: how to develop and certify a medical device.

Read more →·Project: cosmetic medical device.Open →

What clients say

Enzo Costanza, VP of Product Development, Real Time Medical
“Hitech was most impressive with how quickly [they] understood our unique medical application needs and [their] ability to leverage their medical experience to get up to speed in a very short period of time.”
Enzo CostanzaVP of Product Development, Real Time Medical

Frequently asked questions

What is Software as a Medical Device (SaMD)?

Software intended for medical purposes — diagnosis, prevention, monitoring or treatment — that works on its own, without being part of a hardware medical device.

What regulations apply to medical device software in the EU?

The EU Medical Device Regulation (MDR 2017/745), together with standards such as IEC 62304 for the software lifecycle and ISO 14971 for risk management.

What documentation is required for certification?

A full technical file: software requirements and architecture, risk analysis, verification and validation records, usability documentation and post-market surveillance procedures. We prepare it as part of the development lifecycle.

Can you join an existing medical device project?

Yes. We can join at any stage — from planning a new device to preparing documentation and closing gaps in an existing project ahead of certification.

Tell us what you’re building

We’ll reply within one business day with next steps.