Product qualification for software solutions in the healthcare sectoris crucial as if a software qualifies as a medical device (“MDSW”), the software itself may be subject to the medical device regulations. Software can be considered a medical device provided that it falls under the definition of Act CLIV of 1997 on Healthcare (“Healthcare Act”). The definition of medical device in the Healthcare Act has been amended in line with Regulation (EU) 2017/745 on medical devices (“MDR”) and the EU In Vitro Diagnostic Medical Devices Regulation (“IVDR”) for harmonisation purposes.
The primary decisive factor is the product’s intended purpose as described by the manufacturer of the software. Other decisive factors are regulated in the MDR and the IVDR. E.g., if the software is intended to process, analyse, create or modify medical information, it may be qualified as MDSW, provided that it is governed by a medical intended purpose. Therefore, it is important that manufacturers carefully classify the software and pay close attention to any local guidelines published that clarify the classification criteria contained in the MDR and the IVDR. Furthermore, the requirements of the MDR must be observed, including obligations for quality management processes, appropriate conformity assessment procedures and CE marking. If a product is considered as medical device, the legal manufacturer has to comply with all these obligations before the product is placed on the market in Hungary.
In Hungary, authorities and courts apply the MDR taking into account the available guidance on the EU level (in particular MDCG guidance) and guidance provided by the Hungarian authority (legal predecessor: the National Institute of Pharmacy and Nutrition (OGYÉI), as of 1 August 2023, the National Centre for Public Health and Pharmacy (NNGYK)).
Section 3 point h) of the Healthcare Act defines medical device by reference to Article 2 point (1) of the MDR. Pursuant to Article 2 point (1) of the MDR, medical device means any instrument, apparatus, appliance, software, implant, reagent, material or other article intended by the manufacturer to be used, alone or in combination, for human beings for one or more of the following specific medical purposes:
- diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease;
- diagnosis, monitoring, treatment, alleviation of, or compensation for, an injury or disability;
- investigation, replacement or modification of the anatomy or of a physiological or pathological process or state; or
- providing information by means of in vitro examination of specimens derived from the human body, including organ, blood and tissue donations,
and which does not achieve its principal intended action by pharmacological, immunological or metabolic means, in or on the human body, but which may be assisted in its function by such means.
The differentiation between a medical device and a consumer product – which does not fall within the scope of the MDR – can largely be influenced by the manufacturer who defines the intended purpose of the respective product. Mere lifestyle/everyday apps (e.g., for fitness tracking, nutritional recommendations, resilience exercises, meditation training without a medical purpose) are generally not intended for therapeutic purposes.
Not only is the explicitly described intended purpose relevant but so are the instructions for use and the promotional materials (e.g., website, information in App Store) regarding the specific product. Possible indicative terms in connection with the intended purpose and corresponding functions can be, for example: alarming, analysing, calculating, detecting, diagnosing, interpreting, converting, measuring, controlling, monitoring, amplifying. Indicative functions for classification as a medical device can be, amongst others, the following: Decision support or decision-making software, e.g., regarding therapeutic measures; calculation, e.g., of dosing of medicines (as opposed to mere reproduction of a table from which users can deduce the dosage themselves); monitoring patients and collecting data, e.g., by measurements if the results thereof have an influence on diagnosis or therapy. Pure data storage, archiving, lossless compression (i.e., using a compression procedure that allows the exact reconstruction of the original data), communication, or simple search functions do not in themselves result in classification as a medical device.
Medical devices are – generally speaking – assigned to risk classes. The classification is decisive for the conformity assessment procedure that the respective product must undergo. The classification is mainly based on the vulnerability of the human body (invasiveness) and takes into account the potential risks associated with the release or exchange of energy (activity) and the duration of use of the medical device. They are assigned to Classes I, IIa, IIb or III, whereby Class I comprises those products with the lowest risk potential.
The classification rules for software devices are listed under annex VIII chapter III, rule 11 MDR. Software can fall into risk class I. However, due to the new interpretation rules this will likely be an exception only. Most software as medical device will be classified as class IIa or higher. This is important from a practical point of view because such software then needs to undergo a conformity assessment procedure applied by a notified body.
The detailed rules for medical devices in Hungary are included in Decree 4/2009. (III. 17.) of the Minister of Health on medical devices and ESzCsM Decree 8/2003. (III. 13.) on in vitro diagnostic medical devices, which have also been updated and amended in line with the MDR and IVDR.
Furthermore, as per product classification, it should be noted that medical devices that can be given to the lay end users for personal use qualify as medical aids in Hungary and are subject to a special legal regime.