• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2012.10a
• /
• pp.495-497
• /
• 2012

Development of application risk management for medical device software test. First, Through questionnaires, Medical device manufacturers, Analysis of software validation and risk management status. Second, Analyzed by comparing the difference between black box testing and white box testing. Third, After analyzing the potential for software analysis tools using code derived factors were quantified, Finally, Medical device risk management process so that it can be applied to build the framework by FMEA(Failure Mode and Effect Analysis) technique. Through this Difficult to build software validation and risk management processes for manufacturers to take advantage of support in medical device GMP(Good Manufacture Practice).

• Journal of Biomedical Engineering Research
• /
• v.44 no.2
• /
• pp.99-108
• /
• 2023

According to the COVID-19, development of various medical software based on IoT(Internet of Things) was accelerated. Especially, interest in a central software system that can remotely monitor and control ventilators is increasing to solve problems related to the continuous increase in severe COVID-19 patients. Since medical device software is closely related to human life, this study aims to develop central monitoring system that can remotely monitor and control multiple ventilators in compliance with medical device software development standards and to verify performance of system. In addition, to ensure the safety and reliability of this central monitoring system, this study also specifies risk management requirements that can identify hazardous situations and evaluate potential hazards and confirms the implementation of cybersecurity to protect against potential cyber threats, which can have serious consequences for patient safety. As a result, we obtained medical device software manufacturing certificates from MFDS(Ministry of Food and Drug Safety) through technical documents about performance verification, risk management and cybersecurity application.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.12
• /
• pp.543-548
• /
• 2017

In recent years, the importance of the safety of medical device software has been emphasized because of the function and role of the software among components of the medical device, and because the operation of the medical device software is directly related to the life and safety of the user. To this end, various standards have been set up that provide activities that can effectively ensure the safety of medical devices and provide their respective requirements. The activities that standards provide to ensure the safety of medical device software are largely divided into the development life cycle of medical device software and the risk management process. These two activities should be concurrent with the development process, but there is a limitation that the risk management requirements to be performed at each stage of the medical device software development life cycle are not classified. As a result, developers must analyze the association of standards directly to develop risk management activities during the development of medical devices. Therefore, in this paper, we analyze the relationship between medical device software development life cycle and risk management process, and extract risk management requirement items. It enables efficient and systematic risk management during the development of medical device software by mapping the extracted risk management requirement items to the development life cycle based on the analyzed associations.

• Journal of Applied Reliability
• /
• v.16 no.3
• /
• pp.216-223
• /
• 2016

Purpose: This paper suggests the procedure to enhance the reliability of the software of the medical device that is to cure, treat, diagnose, and prevent a disease or an abnormal health conditions. Methods: After test requirements are classified by the software requirements specification for safety and backgrounds, reliability assessment methods are suggested. Results: Verification and validation for function and safety can be performed whether the medical device software are implemented as intended. Conclusion: Procedure on the static analysis, unit test, integration test, and system test are provided for the medical device software.

• Journal of Internet Computing and Services
• /
• v.20 no.3
• /
• pp.69-75
• /
• 2019

The safety and performance of medical device software is managed through life-cycle processes, which represent the entire process of research and development (R&D). The life-cycle process of medical device software is represented by an international standard called IEC 62304, ISO/IEC 12207. In order to license the product, the manufacturer must have document artifacts that comply with the IEC 62304 standard. However, these standards only describe the content of the activity and do not provide a method or procedure for documentation. Therefore, this paper suggests R&D documentation guidelines that assist medical device software developers to have R&D documents conforming to the standards. For this purpose, this study identifies the requirements related to documentation among the requirements existing in the standard and extracts them in the form of guidelines showing only the core information of the requirements. In addition, through the Web framework implemented based on this research, the developer can evaluate whether the technical documents are written in accordance with the R&D document guidelines. Medical device software manufacturers can efficiently produce high-quality research and development documents through R&D documentation guidelines, and they can have standards-compliantresearch and development documentation required for licensing procedures.

• Journal of Biomedical Engineering Research
• /
• v.44 no.6
• /
• pp.363-376
• /
• 2023

According to the COVID-19, development of various medical software based on IoT(Internet of Things) was accelerated. Especially, interest in a central software system that can remotely monitor and control ventilators is increasing to solve problems related to the continuous increase in severe COVID-19 patients. Since medical device software is closely related to human life, this study aims to develop central monitoring system that can remotely monitor and control multiple ventilators in compliance with medical device software development standards and to verify performance of system. In addition, to ensure the safety and reliability of this central monitoring system, this study also specifies risk management requirements that can identify hazardous situations and evaluate potential hazards and confirms the implementation of cybersecurity to protect against potential cyber threats, which can have serious consequences for patient safety. As a result, we obtained medical device software manufacturing certificates from MFDS(Ministry of Food and Drug Safety) through technical documents about performance verification, risk management and cybersecurity application.The purpose of this study is to conduct a usability assessment to ensure that ergonomic design has been applied so that the ventilator central monitoring system can improve user satisfaction, efficiency, and safety. The rapid spread of COVID-19, which began in 2019, caused significant damage global medical system. In this situation, the need for a system to monitor multiple patients with ventilators was highlighted as a solution for various problems. Since medical device software is closely related to human life, ensuring their safety and satisfaction is important before their actual deployment in the field. In this study, a total of 21 participants consisting of respiratory staffs conducted usability test according to the use scenarios in the simulated use environment. Nine use scenarios were conducted to derive an average task success rate and opinions on user interface were collected through five-point Likert scale satisfaction evaluation and questionnaire. Participants conducted a total of nine use scenario tasks with an average success rate of 93% and five-point Likert scale satisfaction survey showed a high satisfaction result of 4.7 points on average. Users evaluated that the device would be useful for effectively managing multiple patients with ventilators. However, improvements are required for interfaces associated with task that do not exceed the threshold for task success rate. In addition, even medical devices with sufficient safety and efficiency cannot guarantee absolute safety, so it is suggested to continuously evaluate user feedback even after introducing them to the actual site.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.16 no.6
• /
• pp.313-321
• /
• 2021

The global market for medical devices is huge, and it will continue showing remarkable growth in the future. However, due to the entry barrier to develop medical devices, many domestic companies have technical problems in entering the medical device industry. In this paper, we introduce an open platform that can help with research and development for companies in the healthcare industry. This open platform consists of a hardware part and a software part. A hardware part is combined into CPU, base and other modules that are easy to replace and assemble. A software part is based on application software for development developed by Bionet. We test the performance of the open medical device platform using a biosignal processing algorithm.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2006.11a
• /
• pp.571-574
• /
• 2006

2006년 5월 국제전기기술위원회(International Electrotechnical Commission, IEC) TC62(의료용전기기기기술위원회) SC62A(의료용전기기기 공통특성에 관한 세부분과위원회)에서 의료기기 소프트웨어의 생명주기 프로세스에 관한 국제규격인 IEC 62304, Ed.1을 제정하였다. 전체 내용은 크게 일반적인 요구사항(General requirements)과 소프트웨어 개발과 유지보수에 대한 프로세스(Software development & maintenance process)로 구성되어 있다. 그리고 소프트웨어 개발과 유지보수 프로세스가 진행되는 동안에 기본적으로 확보되어야 하는 소프트웨어 위험관리와 형상관리에 대한 프로세스 Software risk management & configuration management process)를 규정하고, 또한 문제 발생 시 이를 해결하기 위한 소프트웨어 문제 해결 프로세스(Software problem resolution process)를 규정하고 있다. 이는 기존의 정보통신 분야에서 사용되던 소프트웨어 생명주기 프로세스인 ISO/IEC 12207 규격과 외형상 많은 차이를 나타내고 있다. 이에 본 논문에서는 의료기기 소프트웨어의 생명주기 프로세스에 관한 국제규격인 IEC 652304를 분석하여 실제 의료용 소프트웨어 개발 및 유지보수 작업들이 어떠한 방식으로 이루어지는지를 분석하고, 또한 기존의 소프트웨어 생명주기 프로세스인 ISO/IEC 12207 규격과의 차이점을 비교 분석하여 본 규격에 대한 근본적인 활용 방안을 모색하고자 한다.

• Journal of Information Technology Services
• /
• v.22 no.4
• /
• pp.21-35
• /
• 2023

Software as Medical Devices (SaMD) is a growing category of medical devices that are composed of software to perform one or more medical purposes. SaMD is less likely to cause physical harm compared to conventional medical devices, particularly medical electrical equipments, and may be more vulnerable to privacy issues. This difference was acknowledged and resulted in introducing new regulation guidance specifically for cybersecurity of SaMD. It guides stakeholders of SaMD what to consider in what context in terms of cybersecurity. This study examines the current guidance of how cybersecurity is considered for SaMD by analyzing current medical device standards, then suggest which concept or details beyond current medical device standards may be applicable through analysis of international standards documents published for software in general.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.13 no.8
• /
• pp.4174-4190
• /
• 2019

IEC 62304 is a standard for the medical device software lifecycle. Developers must develop software that complies with all specifications in the standard for licensing. However, because the standard contains not only a large number of specifications, but also domain-specific information and association relationships between specifications, it requires considerable effort and time for developers to understand and interpret the standard. To support developers, this paper presents a method for extracting the contents of the IEC 62304 standard as a goal model, which is the core methodologies of requirements engineering. The proposed method analyzes the grammar of the standard to robustly extract complex structures and various information from standard specifications and define rules that extract goals and links from syntactic element units. We validated the actual extraction process for the standard document experimentally. Based on the extracted goal model, developers can intuitively and efficiently comply with the standard and track specific information within the medical software and standard domains.