Abstract
Medical devices are safety-critical systems that must comply with standards during their development process because of their intrinsic potential of producing harms. Although the existing trend of an increasing complexity of medical hardware and software components, very little has been done in order to apply more mature safety practices already present on other industrial scenarios. This paper proposes a methodology to enhance the Model-Based System Engineering (MBSE) state-of-art practices from the safety perspective, encouraging the use of safety cases and providing guidance on how to show the correspondent traceability for the development artifacts. We illustrate our methodology and its usage in the context of an industrial Automated External Defibrillator (AED). We suggest that medical device industry could learn from other domains and adapt its development to take into account the hazards and risks along the development, providing more sophisticated justification, as, for example, the impact of design decisions.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Alemzadeh, A., Iyer, R.K., Kalbarczyk, Z., Raman, F.: Analysis of safety-critical computer failures in medical devices. IEEE Secur. Priv. 11(4), 14–26 (2013)
MHRA: Report on Devices Adverse Incidents in 2010 (2011). http://www.mhra.gov.uk/home/groups/dts-bs/documents/publication/con129234.pdf
The Boston Consulting Group: EU Medical Device Approval Safety Assessment: A comparative analysis of medical device recalls 2005–2009 (2011). http://www.eucomed.org/uploads/Press%20Releases/BCG%20study%20report.pdf
Wallace, D.R., Kuhn, D.R.: Failure modes in medical device software: an analysis of 15 years of recall data. Int. J. Reliab. Qual. Saf. Eng. 8(4), 351–371 (2001)
The Health Foundation: Supplements to: Using safety cases in industry and healthcare (2012). http://www.health.org.uk/public/cms/75/76/313/3847/Using%20safety%20cases%20in%20industry%20and%20healthcare_supplements.pdf?realName=yjOYNa.pdf
Mäder, P., Jones, P.L., Zhang, Y., Cleland-Huang, J.: Strategic Traceability for Safety-Critical Projects. IEEE Softw. 30(3), 58–66 (2013)
Eucomed: Towards a regulation that guarantees patient safety, ensures patient access and keeps innovation in Europe (2013). http://www.eucomed.org/uploads/Modules/Publications/20130130_2013_eucomed_detailed_position_on_proposal_mdd_revision.pdf
Kelly, T.: Arguing Safety - A Systematic Approach to Managing Safety Cases. Ph.d. thesis, Department of Computer Science, The University of York (1998)
ISO 26262 International Organization for Standardization (ISO), “ISO/DIS 26262: Road vehicles - functional safety,” (2011)
Bloomfield, R., Chozos, N., Embrey, D., Henderson, J., Kelly, T., Koornneef, F., Pasquini, A., Pozzi, S., Sujan, M.-A.: A Pragmatic Review of the Use of Safety Cases in Industry–Lessons and Prerequisites for their Application in Healthcare (2011)
Eagles, S., Wu, F.: Safety Assurance Cases for Medical Devices. In: AAMI 2014, Biomedical Instrumentation & Technology, February 2014
GSN Community Standard. Version.: Origin Consulting GSN Community Standard Version 1 (2011)
International Electrotechnical Commission Medical device software – Software life cycle processes. INTERNATIONAL IEC STANDARD 62304 First edition 2006-05. International Electrotechnical Commission (2006). Accessed 2 June 2012
ISO 14971 - medical devices – application of risk management to medical devices. Technical report, International Organization for Standardization (2010)
IEC/TR 80002-1:2009: Medical Device Software Part 1: Guidance on the application of ISO 14971 to medical device software. ISO, Switzerland (2009)
ISO/IEC 42010 (IEEE Std) 1471-2000: Systems and Software engineering- Recomended practice for architectural description of software-intensive systems, ISO/IEC/(IEEE), p. 23
Rick, K., Mark, K., Paul, C: ATAM: Method for Architecture Evaluation, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical report CMU/SEI-2000-TR-004 (2000). http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=5177
Dobrica, L., Niemelä, E.: A survey on software architecture analysis methods. IEEE Trans. Softw. Eng. 28(7), 638–653 (2002)
Rozanski, N., Woods, E.: Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. Addison-Wesley Professional, Reading (2005)
Antonino, P., Trapp, M..: Improving consistency checks between safety concepts and view based architecture design. In: Proceedings of 12th International Probabilistic Safety Assessment and Management Conference, PSAM 2014, Honolulu, Hawaii, USA, 22–27 June 2014
DeLuca Jr., L., et al.: Analysis of automated external defibrillator device failures reported to the food and drug administration. Annals Emerg. Med. 59(2), 103–111 (2012)
Knight, J.C.: Safety critical systems: challenges and directions. In: Proceedings of the 24th International Conference on Software Engineering, ICSE 2002, pp. 547–550, 25 May 2002
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2015 Springer International Publishing Switzerland
About this paper
Cite this paper
Ruiz, A., Barbosa, P., Medeiros, Y., Espinoza, H. (2015). Safety Case Driven Development for Medical Devices. In: Koornneef, F., van Gulijk, C. (eds) Computer Safety, Reliability, and Security. SAFECOMP 2014. Lecture Notes in Computer Science(), vol 9337. Springer, Cham. https://doi.org/10.1007/978-3-319-24255-2_14
Download citation
DOI: https://doi.org/10.1007/978-3-319-24255-2_14
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-24254-5
Online ISBN: 978-3-319-24255-2
eBook Packages: Computer ScienceComputer Science (R0)