Design of a secure remote management module for a software-operated medical device

References

[1] Alemzadeh H, Iyer R, Kalbarczyk Z, Raman J. Analysis of safety-critical computer failures in medical devices. Security Privacy IEEE 2013; 11: 14–26.10.1109/MSP.2013.49Search in Google Scholar

[2] Brannigan VM. Software quality regulation under the Safe Medical Devices Act of 1990: hospitals are now the canaries in the software mine. In Proceedings of the 15th Annual Symposium on Computer Application in Medical Care. Washington, DC; New York: McGraw Hill, 1991: 238–242.Search in Google Scholar

[3] Brooks G, Kenney T. Consumer trends fuel medical device innovation. Medical Electronics Design, 2010, http://www.medicalelectronicsdesign.com/article/consumer-trends-fuel-medical-device-innovation, Accessed August 2017.Search in Google Scholar

[4] Burnik U, Dobravec S, Meža M, Vučnik M. Telenadzor: sodoben oddaljeni servisni dostop in uporabniška podpora na napravah 2D-DL: poročilo o opravljeni študiji. (Telecontrol: a contemporary remote service access and end user support for 2D-DL devices: case report) tech. rep., University of Ljubljana, 2009.Search in Google Scholar

[5] Catelani M, Ciani L, Diciotti S, Dori F, Giuntini M. ISO 14971 as a methodological tool in the validation process of a RIS-PACS system. In Medical Measurements and Applications Proceedings (MeMeA), 2011 IEEE International Workshop on, pp. 408–412, May 2011.10.1109/MeMeA.2011.5966726Search in Google Scholar

[6] Cooper T, Eagles S. Aiming for patient safety in the networked healthcare environment. IT Horizons 2010; 4:18–20, http://www.aami.org/publications/ITHorizons/2010/18-20_StandardsRegs_Cooper.pdf, Accessed August 2017.Search in Google Scholar

[7] Council Directive 93/42/EEC of 14 June 1993 concerning medical devices, http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:01993L0042-20071011, 1993, Accessed August 2017.Search in Google Scholar

[8] Dzung D, Naedele M, von Hoff T, Crevatin M. Security for industrial communication systems. Proc IEEE 2005; 93: 1152–1177.10.1109/JPROC.2005.849714Search in Google Scholar

[9] FDA. Title 21: Food and Drugs, Part 860 – Medical Device Classification Procedures. Electronic Code of Federal Regulations, 1978, https://www.ecfr.gov/cgi-bin/retrieveECFR?gp=1&SID=9557aadd484e0d12d825cf3c20aadc38&ty=HTML&h=L&mc=true&r=PART&n=pt21.8.860. Accessed August 2017.Search in Google Scholar

[10] Haigh T, Landwehr C. Building code for medical device software security. IEEE Cybersecurity, 2015.Search in Google Scholar

[11] Hamzeh K, Pall G, Verthein W, Taarud J, Little W, Zorn G. Point-to-point tunneling protocol (PPTP), The Internet Society RFC 2637, 1999, https://tools.ietf.org/pdf/rfc2637.pdf, Accessed August 2017.10.17487/rfc2637Search in Google Scholar

[12] Hanna S, Rolles R, Molina-Markham A, Poosankam P, Fu K, Song D. Take two software updates and see me in the morning: the case for software security evaluations of medical devices. In Proceedings of the 2nd USENIX conference on Health security and privacy, no. August, pp. 6–6, USENIX Association, 2011.Search in Google Scholar

[13] Institute of Medicine (US). Committee on the Public Health Effectiveness of the FDA 510 (k) Clearance Process, I. Medical devices and the public’s health: the FDA 510 (k) clearance process at 35 years. National Academies Press, Washington, DC, 2011.Search in Google Scholar

[14] ISO. Medical device software – software life cycle processes. ISO 62304:2006, International Organization for Standardization, Geneva, Switzerland, 2006.Search in Google Scholar

[15] ISO. Medical devices – application of risk management to medical devices. ISO 14971, International Organization for Standardization, Geneva, Switzerland, 2007.Search in Google Scholar

[16] ISO. Application of risk management for IT-networks incorporating medical devices. ISO 80001, International Organization for Standardization, Geneva, Switzerland, 2010–2015.Search in Google Scholar

[17] Kumar A. Not complying with IEC 62304 for software design could be detrimental on many levels. Medical Electronics Design, no. May/June, pp. 13–17, 2011.Search in Google Scholar

[18] Lincoln JE. Product risk management under ISO 14971:2007. J Validation Technol 2009; 15: 10–18.Search in Google Scholar

[19] Ortiz S. Virtual private networks: leveraging the Internet, Computer 1997; 11: 18–20.10.1109/2.634834Search in Google Scholar

[20] Prasad D, Ray S, Majumdar AK, et al. Real time medical image consultation system through internet. J Healthc Eng 2010; 1: 141–154.10.1260/2040-2295.1.1.141Search in Google Scholar

[21] Rafeh R. A proposed approach for safety management in medical software design. J Med Syst 2013; 37: 9925.10.1007/s10916-012-9925-0Search in Google Scholar PubMed

[22] Rakitin R. Coping with defective software in medical devices. Computer 2006; 39: 40–45.10.1109/MC.2006.123Search in Google Scholar

[23] Rakitin SR. Networked medical devices: essential collaboration for improved safety. Biomed Instrum Technol 2009; 43: 332–338.10.2345/0899-8205-43.4.332Search in Google Scholar PubMed

[24] Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, amending Directive 2001/83/EC, Regulation (EC) No 178/2002 and Regulation (EC) No 1223/2009 and repealing Council Directives 90/385/EEC and 93/42/EEC, http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L:2017:117:FULL&from=EN, 2017, Accessed August 2017.Search in Google Scholar

[25] Sametinger J, Rozenblit J, Lysecky R, Ott P. Security challenges for medical devices. Commun ACM 2015; 58: 74–82.10.1145/2667218Search in Google Scholar

[26] Schrenker R. The case for a systems focus in healthcare. IT Horizons 2010; 4: 13–17.Search in Google Scholar

[27] Steffen A, Hientzsch D. Software-based risk management documentation for medical devices. Biomed Tech 2013; 58: 1.10.1515/bmt-2013-4236Search in Google Scholar PubMed

[28] Tanabian M. “Testing android devices,” Medical Electronics Design, no. May/June, 2011.FDA, “Applying human factors and usability engineering to medical devices”, Guidance for Industry and Food and Drug Administration Staff (nonbinding recommendations), U.S. Department of Health and Human Services, Food and Drug Administration, Center for Devices and Radiological Health,Office of Device Evaluation, 2016, https://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm259760.pdf, Accessed August 2017.Search in Google Scholar

[29] Van Roy P, Haridi S. Concepts, techniques and models of computer programming. Cambridge, MA: The MIT Press, 2004.Search in Google Scholar

[30] Vogel, DA. Medical device software verification, validation and compliance. Norwood, MA: Artech House, 2010.Search in Google Scholar

[31] White paper of Joint NEMA/COCIR/JIRA Security and Privacy Committee. Remote Services in Healthcare – Use Cases and Obligations For Customer and Service Organizations, http://www.medicalimaging.org/wp-content/uploads/2011/02/Remote-Service_2008-08-06_final.pdf, 2008, Accessed August 2017.Search in Google Scholar