When is software a medical device?

Software is a medical device when the manufacturer intends it for a medical purpose, such as diagnosis, monitoring, treatment or prediction of disease. Then the EU Medical Device Regulation (MDR) applies, which usually classifies software as at least class IIa. Pure administration software such as scheduling or billing is not a medical device.

The intended purpose decides

It is not the technology that decides but what the manufacturer intends the software for:

  • Medical device: software that provides information for diagnostic or therapeutic decisions, monitors vital signs or calculates doses.
  • Not a medical device: appointment booking, billing, practice organisation, plain storage and transfer of data without medical analysis.

What applies to a medical device

  • MDR: Regulation (EU) 2017/745 has applied since May 2021. Rule 11 usually classifies software that supports diagnostic or therapeutic decisions as class IIa or higher.
  • Conformity assessment: from class IIa with a notified body.
  • Development to IEC 62304: the standard describes the life cycle of medical software, from requirements through testing to maintenance.
  • Quality and risk management: for example to ISO 13485 and ISO 14971.

How we classify our own work

HealthFusion, our practice software, is in development and brings patient records, appointments and documentation together. Whether and how a feature falls under the MDR is a question of intended purpose, clarified before it is built. This article is not regulatory advice.

Sources

  1. Regulation (EU) 2017/745 on medical devices (MDR) · Publications Office of the European Union

The first step is a conversation

You describe what you have in mind. If we are a good fit, you receive a fixed-price offer for a clearly described scope. The call is free.