Medical device software

Software Validation Authorities are demanding rules in order to outline the software validation principles used in medical device software or the validation of software used to design, develop, or manufacture medical devices. 

Specifically for medical devices, the Medical Device Software Committee of the Association for the Advancement of Medical Instrumentation (AAMI) has taken on the task of developing a standard4 for use in the medical device business sector based upon the framework established in ISO12207. 

ANSI/AAMI SW68 2001, Medical device software—Software life cycle processes. ... 

ANSI/AAMI SW68. Medical Device Software—Software Life Cycle Processes Association for the Advancement of Medical Instrumentation, 2001. 

International Electrotechnical Commission. lEC/TR 80002-1 2009. Medical device software, Part 1, Guidance on the application of ISO 14971 to medical device software. 2009. 

The standard applies not only to physical medical devices but also to software products which meet the criteria. And to this ends an additional publication lEC/TR 80002-1 2009 [13] describes in detail how the requirements can be appUed to medical device software. The standard requires that risk management activities are carried out throughout the lifecycle of the product, i.e. from vision through go-live and until decommissioning. 

Levkoff, B., Increasing Safety in Medical Device Software, Medical Device Diagnostic Industry Magazine, Vol. 18, No. 9,1996, pp. 92-97. 

Protect individual components from exploitation and develop strategies for active security protection appropriate for the device s use environment. Such strategies should include timely deployment of routine, validated security patches and methods to restrict software or firmware updates to authenticated code. Note The FDA typically does not need to review or approve medical device software changes made solely to strengthen cybersecurity. 

Abstract A recent standard for medical device software lifecycle processes, ISO/IEC 62304 (ISO 2006), assumes and specifies a software safety classification scheme, where docmnentation, verification and validation tasks to be carried out depend on the safety classification. This means that a risk-driven approach has become an accepted standard for medical devices. 

Recently, a standard for medical device software lifecycle processes, ISO/IEC 62304 (ISO 2006), has been released by a commission representing regulatory bo-... 

Software is often an integral part of MEDICAL DEVICE technology. Establishing the SAFETY and effectiveness of a MEDICAL DEVICE containing software requires knowledge of what the software is intended to do and demonstration that the use of the software fulfils those intentions without causing any unacceptable RISKS. This standard provides a framework of life cycle PROCESSES with ACTIVITIES and TASKS necessary for the safe design and maintenance of MEDICAL DEVICE SOFTWARE. This standard provides requirements for each life cycle PROCESS. 

As a basic foundation it is assumed that MEDICAL DEVICE SOFTWARE is developed and maintained within a RISK MANAGEMENT system. The MANUFACTURER shall apply a RISK MANAGEMENT PROCESS complying with ISO 14971. 

Analyzing the differenees between 8110.49 (FAA 2003) and D0178B (RTCA 1992), adopted in aireraft eertifieation, and standards for medical device software, one ean see that they depend on the characteristics of the software to be controlled. 

The MANUFACTURER of MEDICAL DEVICE SOFTWARE shall demonstrate the ability to provide MEDICAL DEVICE SOFTWARE that consistently meets customer requirements and applicable regulatory requirements. Demonstration of this ability can be by the use of a quahty management system in compliance with. .. 

ISO (2006) ISO/EC 62304 - Medical device software - Software life cycle processes. Edition 1.0... 

A Risk Driven Approach to testing Medical Device Software... 

Kuhn D, Wallace D (2000) Failure modes in medical device software an analysis of 15 years of recall data. Nat. Institute of Standards and Technology, Gaithersburg, MD USA. http //csrc. nist.gov/staff/Kuhn/final-rqse.pdf. Accessed 25 August 2010 Littlewood B, Strigini L (1993) Validation of ultrahigh dependability for software-based systems. Comm. ACM 36(11) 69-80... 

It is necessary to clarify that software in its own right, when specifically intended by the manufacturer to be used for one or more of the medical purposes set out in the definition of a medical device, is a medical device. Software for general purposes when used in a healthcare setting is not a medical device. ... 

Ray, A., Jetley, R., Jones, P., Zhang, Y. Model-based engineering for medical-device software. Biomedical Instrumentation Technology 44(6), 507-518 (2010) Ruksenas, R., Masci, P., Harrison, M.D., Curzon, P. Developing and verifying user interface requirements for infusion pumps a refinement approach. To appear in FMIS 2013 (2013)... 

---