Answers are grounded in this paper and cite their sources.
Analytical review highlights regulatory differences and improves risk classification for software in medical devices.
In modern conditions of development of medical technologies, software becomes an integral part of medical devices and plays one of the key roles in modern medicine. Software provides the functioning of medical equipment, contributes to the automation of the processes of diagnostics, treatment and monitoring of patients' health. Aim. To analyze the regulatory and legal regulation of medical device software in Ukraine and the EU, to identify key differences and problematic aspects in the classification of software as a medical device, and to outline possible ways to improve regulatory approaches to ensure the safety and effectiveness of such products. Materials and Methods. An analytical review of the regulatory and legal acts of Ukraine and the European Union regulating the circulation of medical devices, in particular software that is their integral part or an independent medical device, was conducted. Results and Discussion. In recent years, in the field of conformity assessment of medical devices, the number of cases when software becomes an integral part of medical devices or exists as a stand-alone medical device has been increasing. Ukrainian legislation regulates the introduction of such products into circulation in accordance with the Law of Ukraine "On Technical Regulations and Conformity Assessment" and Resolutions of the Cabinet of Ministers No. 753, 754, 755. However, in the technical regulation on medical devices (Resolution No. 753) remains uncertainty in the classification of risks for software as a stand-alone medical device, which creates difficulties in conformity assessing. The European Regulation (EU) 2017/745 has eliminated some of these uncertainties by introducing new concepts such as “compatibility”, “interoperability” and requirements for software, including its security and compliance with modern IT standards. Clear rules for classifying software by risk level have been defined (Rule 11), which allows it to be assigned to classes from I to III depending on the impact on the patient’s health. However, the question of a possible overestimation of the risk class for software in its own right remains open due to difficulties in determining the severity of possible consequences. The solution may be an approach that takes into account the impact of the software on various systems of the body, which is, in our opinion, more reasonable. Conclusions. The regulation of software as a medical device has been significantly improved in the EU Regulation 2017/745. It is necessary to improve the risk classification methodology for software in its own right in order to avoid unjustified overestimation of the risk class and reduce subjectivity in decision-making. A promising direction is to link the risk class of software to specific physiological systems of the body, which will allow a more objective assessment of the level of potential danger and avoid unnecessary complication of conformity assessment procedures. Thus, the TR currently in force in Ukraine needs to be revised, improved and harmonized in accordance with existing international approaches.
No takes yet. Share an insight, caveat, or question.
Kharchenko et al. (2025) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: