Skip to content
DT Nova
Services

Medical device software development for SaMD, connected devices and companion apps

Medical devices software development is ordinary software engineering with a much higher bar for proof. The code has to work, and you have to be able to show how it was specified, designed, verified, risk-managed and released, every time it changes. We build software as a medical device, apps and cloud services that work with medical devices, and the clinical software around them, inside your quality management system and to the lifecycle standards notified bodies and the FDA expect. Hosting is in the EU, and your company owns the code.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

First question: is it a medical device?

Whether software is a medical device depends on its intended purpose, not on its technology. The EU Medical Device Regulation defines a medical device as any instrument, apparatus, appliance, software, implant, reagent, material or other article intended by the manufacturer to be used for one or more specific medical purposes, and states that software shall also be deemed to be an active device (Regulation (EU) 2017/745, Article 2, consolidated version of 10 January 2025). The European Commission's guidance on qualification and classification of software, MDCG 2019-11, was revised on 17 June 2025 and sets out the decision steps.

In the United States, the Federal Food, Drug, and Cosmetic Act excludes certain software functions from the device definition, including functions intended for administrative support of a health care facility, such as appointment schedules and billing, functions for maintaining or encouraging a healthy lifestyle that are unrelated to the diagnosis or treatment of a disease, and certain electronic patient record functions (21 U.S.C. 360j(o)). (All read on 11 November 2026.)

ExampleUsuallyWhy
Appointment booking or staff scheduling appNot a deviceAdministrative purpose
General fitness or wellness appNot a deviceNo specific medical purpose
Record viewer that displays data as enteredOften not a deviceStores and displays without interpreting
Dose calculator, symptom triage, diagnostic supportDeviceInformation used for diagnosis or treatment decisions
App that controls or reads a medical deviceDevice or accessoryPart of the device's function
Remote monitoring of vital signsDevice, often higher classMonitoring of physiological processes

This is the manufacturer's decision and must be documented, but we raise it in the first conversation, because it shapes everything that follows. If your product is clearly not a device, see telemedicine app development or EHR software development.

Classification under Rule 11

Most standalone medical software in the EU is classified under Rule 11 of the MDR. Software intended to provide information which is used to take decisions with diagnosis or therapeutic purposes is class IIa, unless the decisions may cause death or an irreversible deterioration of health (class III) or a serious deterioration of health or a surgical intervention (class IIb). Software intended to monitor physiological processes is class IIa, or class IIb when it monitors vital parameters where variations could result in immediate danger to the patient. All other software falls in the lowest class (Regulation (EU) 2017/745, Annex VIII, Rule 11, read on 11 November 2026).

The class decides how much a notified body is involved and how much evidence it expects. A product idea that would land in class IIb can sometimes be scoped down to a lower class by changing what the software claims to do; that is a regulatory and clinical decision, and it is far cheaper to make before the first line of code.

What the regulation expects from the software

The MDR's general safety and performance requirements are short on software, but every sentence matters. For devices that incorporate software or software that are devices in themselves, the software shall be developed and manufactured in accordance with the state of the art taking into account the principles of development life cycle, risk management, including information security, verification and validation. Software intended for mobile platforms shall be designed taking into account the specific features of the platform, and manufacturers shall set out minimum requirements for hardware, IT networks and IT security measures, including protection against unauthorised access (general safety and performance requirements, sections 17.2 to 17.4, read on 11 November 2026).

In practice, the state of the art means the harmonised and recognised standards: IEC 62304 for the software lifecycle, ISO 14971 for risk management, IEC 62366-1 for usability engineering and ISO 13485 for the quality management system. In the United States, the FDA's Quality Management System Regulation, effective 2 February 2026, incorporates ISO 13485:2016 by reference into 21 CFR Part 820 (FDA, Quality Management System Regulation, read on 11 November 2026), so one quality system can serve both markets.

How we work inside your quality system

The manufacturer owns the quality system, the technical documentation and the regulatory decisions. We work as a supplier inside it, following your procedures, and every piece of work leaves the record your procedures require:

Where you do not yet have a quality system, we say so plainly and recommend bringing in a regulatory consultant to set it up; building the software first and documenting later is the most expensive route there is.

Cybersecurity for connected devices

Connected medical software is a security target, and both markets now require evidence. In the United States, a cyber device is a device that includes software, has the ability to connect to the internet, and contains technological characteristics that could be vulnerable to cybersecurity threats. A premarket submission for a cyber device must include a plan to monitor, identify and address postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure; processes that provide a reasonable assurance that the device and related systems are cybersecure, with postmarket updates and patches; and a software bill of materials, including commercial, open-source and off-the-shelf components (21 U.S.C. 360n-2, section 524B of the FD&C Act, read on 11 November 2026). In the EU, the MDR's information security requirements in its general safety and performance requirements apply.

We build the security work into the lifecycle: threat modelling for each interface, secure update paths for apps and devices, a software bill of materials generated at every build, dependency monitoring, and a documented way for researchers and customers to report vulnerabilities. For an outside review of an existing product, see security audit services.

AI in medical device software

Machine learning in a medical device brings a second layer of rules. Under the EU AI Act, AI systems that are safety components of products covered by EU product legislation listed in the Act's first annex, which includes the MDR, or that are such products themselves, are high-risk where the product requires third-party conformity assessment. Under the Act as amended by the Digital Omnibus on AI, those high-risk requirements apply from 2 August 2028 (AI Act Service Desk, Article 113, read on 11 November 2026). The practical consequences arrive earlier: training data has to be documented and representative, model versions locked and traceable, and performance monitored after release. We treat a model as a software item with its own requirements, data records and verification, not as a black box attached to the app.

Health data and hosting

Medical software processes health data, which the GDPR treats as a special category with stricter conditions for processing (Regulation (EU) 2016/679, Article 9). Cloud parts run in an EU data region in your company's account, with encryption, access by role, audit logging and documented backup and recovery. Where the product is also sold in the United States, the HIPAA requirements for business associates are handled in the contracts and the architecture. For hospital-side apps, see our guide to hospital mobile apps; for software sold as a subscription to clinics, see the guide to healthcare SaaS.

What we build

How a project runs

  1. Intended purpose and boundary. We work with your regulatory lead on what the software claims to do, its likely class and where the device boundary sits.
  2. Plan and scope in writing. Development plan, deliverables, records, the procedures we follow and a fixed price for the first phase.
  3. Requirements and architecture. User needs, software requirements, risk controls and architecture, reviewed and approved before most of the code is written.
  4. Build and verify in increments. Short iterations with automated tests and traceability kept current, so the documentation is never months behind the code.
  5. Release and support. A verified release package for your technical documentation, then maintenance under change control, including security updates.

You own it

As a standard term, the source code, the build pipeline and the design records sit in your company's own accounts, and cloud hosting is in your name in an EU data region. Your quality system holds the records, not ours. You can keep us for maintenance, run it yourself or hand it to another team. See prices.

Questions we get

Is our app a medical device?

It depends on its intended purpose, as stated by the manufacturer. Under the EU Medical Device Regulation, software is a medical device when it is intended for a specific medical purpose, such as diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease. An appointment app or a general wellness app is usually not; an app that calculates a dose or analyses data to support a diagnosis usually is. The European Commission's MDCG 2019-11 guidance explains the decision steps.

Who is the manufacturer when you build the software?

Your company, if the product is placed on the market under your name. The manufacturer holds the quality management system, the technical documentation, the risk management file and the conformity assessment. We work inside your quality system as a supplier, following your procedures and producing the records they require.

Which standards do you work to?

For the software lifecycle, IEC 62304; for risk management, ISO 14971; for usability, IEC 62366-1; and for the quality management system that surrounds them, ISO 13485. Which ones you claim, and which edition, is decided in your quality system and technical documentation; we follow it.

What does the FDA expect for software in a connected device?

For a cyber device, which includes software and can connect to the internet, a premarket submission must include a plan to monitor and address postmarket cybersecurity vulnerabilities, processes that provide reasonable assurance the device is cybersecure with updates and patches, and a software bill of materials including commercial, open-source and off-the-shelf components. We build those records as the software is written, not afterwards.

Can you update software that is already certified?

Yes, under change control in your quality system. Each change is assessed for its effect on safety, performance and the device's classification and certificate before it is made, then verified and documented. Some changes need to be reported to or approved by the notified body or the FDA before release.

Who owns the code?

Your company. The source code, the build pipeline and the design records sit in your own accounts, and hosting for cloud parts is in your name, in an EU data region by default.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote