Skip to content
FibonacciAestheticsLog inTry it free

Technology and AI

Is clinical records software a medical device? What the MDCG guidance on software says

Clinical records software and medical devices: when a system falls under the MDR, what MDCG 2019-11 guidance says, and what to ask the supplier.

The Fibonacci editorial teamUpdated on 9 min read

Lines of code on a computer screen
In this article
  1. The question behind the fear
  2. How the guidance reasons: five steps
  3. What is not a medical device
  4. What is
  5. Two clarifications that remove the shortcuts
  6. If it is: the risk class
  7. Software that drives a device
  8. And the health data regulation?
  9. What to ask the supplier
  10. What Fibonacci declares

A clinical records software is not, in itself, a medical device. The European MDCG 2019-11 guidance says so expressly for systems used to store and transfer patient records in place of paper. A single module added to the record can become one, when it processes clinical data for a medical purpose: for example to suggest a dose, flag a drug interaction or interpret a test.

The criterion is not «it has an algorithm inside», but what the manufacturer declares the software does and what it actually does to the data.

The question behind the fear

Anyone choosing a practice management system hears two things that seem to contradict each other: that you need «compliant» software and that clinical records software is a medical device requiring CE marking. Neither is accurate in that form, and it is worth knowing where the line falls.

Regulation (EU) 2017/745 on medical devices (MDR) defines what a device is, and includes software within it. But the guidance from the Commission's coordination group (MDCG) specifies that software must have a medical purpose in its own right to qualify as such, and that what counts is the intended purpose declared by the manufacturer. Not all software used in healthcare is a medical device.

How the guidance reasons: five steps

The MDCG 2019-11 guidance (opens in a new tab) sets out a path in five questions, in order.

  1. Is it software? That is, a set of instructions that processes input data and produces output data. If not, the guidance does not apply.
  2. Is it an Annex XVI product, an accessory to a device, or software that drives or influences a device? If so, it follows the fate of that device and is assessed together with it.
  3. Does it do anything to the data beyond storing, archiving, transferring, searching in a simple way or compressing it losslessly? If it does only this, it is not a medical device. If it does anything else, you carry on.
  4. Is the action for the benefit of individual patients? Software that aggregates population data, offers generic pathways not directed at a patient, contains scientific literature, atlases, models or is intended only for epidemiological studies or registries is not considered as such.
  5. Is it software with a medical purpose according to the definition? Here you look at the intended purpose: diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of a disease, and the other cases in art. 2 of the regulation.

The point that almost always decides it is the third: what the software does with the data.

What is not a medical device

The guidance gives examples, and for a doctor they are more useful than definitions.

  • Patient management systems. Information systems that support admission, appointment scheduling, insurance and billing are not in themselves medical devices.
  • Information systems used only to transfer, store, convert, format or archive data. These too are not in themselves.
  • Electronic health records used as a repository of documents and data for individual patients, when they serve only to replace paper files.
  • Software for non-medical purposes: billing, staff scheduling, email, web or voice messaging, word processing, backup, wellness or fitness apps.
  • «Simple search»: the retrieval of records by comparing metadata against search criteria, or the retrieval of information.

Even merely changing the representation of a datum, for compatibility or for appearance, does not easily qualify the software as a device.

What is

Software becomes one when it processes, analyses, interprets, calculates, creates or modifies medical information, where the creation or modification is governed by a medical purpose. The guidance explains this with examples that serve as orientation:

  • software that searches medical images for findings supporting a diagnostic hypothesis or the course of a therapy;
  • decision support systems that combine databases and algorithms with the individual patient's data to give recommendations for diagnosis, prognosis, monitoring and treatment;
  • systems that calculate the dosage of a drug or of radiation for a specific patient;
  • computer-aided detection systems that analyse images or interpret electrocardiograms.

For electronic records the guidance is explicit: integrated or alongside modules can be software with a medical purpose. Among the examples, modules that allow radiological images to be viewed and analysed with diagnostic tools, those that interpret electrocardiographic traces flagging arrhythmias, those that analyse patient data to suggest dose adjustments or flag drug interactions in someone with reduced renal function. The record remains a record; the module answers to the regulation in its own right.

Two clarifications that remove the shortcuts

The risk of harm is not a criterion. The guidance says so: the risk to patients, users or other people linked to the use of the software, including a malfunction, does not decide whether the software is a medical device. This is why «the doctor confirms it anyway» does not remove the qualification from a function that suggests a decision.

A search is not always «simple». The guidance excludes simple search, but notes that a search function in the interface or a search that uses natural language processing is not simple if it contributes to achieving a medical purpose.

To these is added a recommendation on form: the intended purpose must be written in a well-defined way, without ambiguity, because classification errors arise from ambiguity. In modular software every module must meet the requirements in its own right.

If it is: the risk class

Software that provides information used to take decisions with a diagnostic or therapeutic purpose falls under rule 11 of the classification rules of the regulation. The guidance reports it as follows: class IIa, except where the decisions may cause death or an irreversible deterioration of health (class III) or a serious deterioration or a surgical intervention (class IIb). Software that monitors physiological processes is IIa, except for vital parameters whose variation may put the patient in immediate danger (IIb). Everything else is class I.

Whoever manufactures the software must ensure they have met all the requirements for placing it on the market and for conformity assessment, and must support the medical indications they declare with adequate clinical evidence. If they cannot do so, the software cannot bear the CE marking as a medical device nor present those indications.

Software that drives a device

In the aesthetic medicine practice there is a separate case, which the guidance treats on its own: software that operates or influences a device. It does not have a medical purpose in its own right and does not create medical information, but it drives or regulates a device. In that case it is considered part of the device, or its accessory, and follows the regulation of the device: classification rule 3.3 says that software that drives or influences a device falls into the same class as the device. The guidance adds that its principles also apply to Annex XVI products, that is, those without a medical purpose that the regulation treats as devices. The topic of devices is in Annex XVI of the medical devices regulation.

And the health data regulation?

Alongside the MDR there is Regulation (EU) 2025/327 on the European Health Data Space (EHDS), which regulates electronic health record systems. Here the question changes: it is not whether the record is a medical device, but what a records system must meet to be placed on the European market. The regulation provides for a CE marking of conformity for these systems, affixed by the manufacturer before placing on the market (art. 41). Art. 27 says how the two worlds fit together: whoever produces a medical device that declares interoperability with the harmonised software components of a record must demonstrate compliance with the requirements of Annex II.

The MDCG guidance distinguishes three cases: the records system that is itself a device, the module of a record that is one, and the device that declares interoperability with a record. Recital 42 of the regulation, which the guidance reports, adds that components falling within the definition of a medical device, an in vitro diagnostic or a high-risk AI system must be certified under the regulation that concerns them.

The two regimes are therefore distinct and add up when needed. On the EHDS part, the dates and the state of play are in the European Health Data Space and on the European compliance page.

What to ask the supplier

A list to pass on to whoever sells or leases you a practice management system:

  • What is the intended purpose of the software, in writing, for each module?
  • Are there functions that suggest doses, grades on a scale, diagnoses or therapies? If so, does the supplier consider them a medical device, and in which class?
  • If so: is there CE marking under the MDR? Can I read the declaration of conformity?
  • If not: on what reasoning does the supplier exclude the qualification, and where is it written?
  • Does the software drive or regulate devices in the practice (lasers, pulsed light)? Who is responsible for the conformity of the whole?
  • What does the supplier say about the requirements of the health data regulation for electronic health records?

What Fibonacci declares

Fibonacci presents itself as a clinical record, not as a medical device, and keeps the distinction in the way it designs its functions. The clearest case is dictation: when you say a fact reported by the patient (an allergy, a drug) it fills it in; when you describe a judgement expressed on a scale (phototype, grades of the physical examination) it does not translate it into a grade, and the selector stays empty until you decide. Why the choice is this is explained in dictation during the consultation.

As for the CE marking provided for by the health data regulation, the European compliance page explains that today no manufacturer can affix it, because the Commission's implementing acts are missing.

What Fibonacci does for this

This is how it looks in Fibonacci, with sample data:

The patient record in Fibonacci, with sample data

Sources

  1. MDCG 2019-11 rev. 1 (June 2025): qualification and classification of software in the MDR and IVDR regulations (opens in a new tab)
  2. Regulation (EU) 2025/327, European Health Data Space (EHDS), Articles 27 and 41 and recital 40 (opens in a new tab)

These articles explain what regulations and guidelines require and what is documented in the medical record. They are not legal or tax advice on your situation and do not say how to treat a patient.

Try Fibonacci in your practice for 15 days, no credit card needed

Within one working day we call you: together we set up your practice and import your data.

Try it free

Read next

All articles