Cargando…
A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies
BACKGROUND: Hospitals today are introducing new mobile apps to improve patient care and workflow processes. Mobile device adoption by hospitals fits with present day technology behavior; however, requires a deeper look into hospital device policies and the impact on patients, staff, and technology d...
Autores principales: | , , , , , |
---|---|
Formato: | Online Artículo Texto |
Lenguaje: | English |
Publicado: |
JMIR Publications Inc.
2016
|
Materias: | |
Acceso en línea: | https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4880739/ https://www.ncbi.nlm.nih.gov/pubmed/27169345 http://dx.doi.org/10.2196/mhealth.4424 |
_version_ | 1782433843534364672 |
---|---|
author | Al Ayubi, Soleh U Pelletier, Alexandra Sunthara, Gajen Gujral, Nitin Mittal, Vandna Bourgeois, Fabienne C |
author_facet | Al Ayubi, Soleh U Pelletier, Alexandra Sunthara, Gajen Gujral, Nitin Mittal, Vandna Bourgeois, Fabienne C |
author_sort | Al Ayubi, Soleh U |
collection | PubMed |
description | BACKGROUND: Hospitals today are introducing new mobile apps to improve patient care and workflow processes. Mobile device adoption by hospitals fits with present day technology behavior; however, requires a deeper look into hospital device policies and the impact on patients, staff, and technology development. Should hospitals spend thousands to millions of dollars to equip all personnel with a mobile device that is only used in a hospital environment? Allowing health care professionals to use personal mobile devices at work, known as bring-your-own-device (BYOD), has the potential to support both the hospital and its employees to deliver effective and efficient care. OBJECTIVE: The objectives of this research were to create a mobile app development guideline for a BYOD hospital environment, apply the guideline to the development of an in-house mobile app called TaskList, pilot the TaskList app within Boston Children’s Hospital (BCH), and refine the guideline based on the app pilot. TaskList is an Apple operating system (iOS)-based app designed for medical residents to monitor, create, capture, and share daily collaborative tasks associated with patients. METHODS: To create the BYOD guidelines, we developed TaskList that required the use of mobile devices among medical resident. The TaskList app was designed in four phases: (1) mobile app guideline development, (2) requirements gathering and developing of TaskList fitting the guideline, (3) deployment of TaskList using BYOD with end-users, and (4) refinement of the guideline based on the TaskList pilot. Phase 1 included understanding the existing hospital BYOD policies and conducting Web searches to find best practices in software development for a BYOD environment. Phase 1 also included gathering subject matter input from the Information Services Department (ISD) at BCH. Phase 2 involved the collaboration between the Innovation Acceleration Program at BCH, the ISD Department and the TaskList Clinical team in understanding what features should be built into the app. Phase 3 involved deployment of TaskList on a clinical floor at BCH. Lastly, Phase 4 gathered the lessons learned from the pilot to refine the guideline. RESULTS: Fourteen practical recommendations were identified to create the BCH Mobile Application Development Guideline to safeguard custom applications in hospital BYOD settings. The recommendations were grouped into four categories: (1) authentication and authorization, (2) data management, (3) safeguarding app environment, and (4) remote enforcement. Following the guideline, the TaskList app was developed and then was piloted with an inpatient ward team. CONCLUSIONS: The Mobile Application Development guideline was created and used in the development of TaskList. The guideline is intended for use by developers when addressing integration with hospital information systems, deploying apps in BYOD health care settings, and meeting compliance standards, such as Health Insurance Portability and Accountability Act (HIPAA) regulations. |
format | Online Article Text |
id | pubmed-4880739 |
institution | National Center for Biotechnology Information |
language | English |
publishDate | 2016 |
publisher | JMIR Publications Inc. |
record_format | MEDLINE/PubMed |
spelling | pubmed-48807392016-06-08 A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies Al Ayubi, Soleh U Pelletier, Alexandra Sunthara, Gajen Gujral, Nitin Mittal, Vandna Bourgeois, Fabienne C JMIR Mhealth Uhealth Original Paper BACKGROUND: Hospitals today are introducing new mobile apps to improve patient care and workflow processes. Mobile device adoption by hospitals fits with present day technology behavior; however, requires a deeper look into hospital device policies and the impact on patients, staff, and technology development. Should hospitals spend thousands to millions of dollars to equip all personnel with a mobile device that is only used in a hospital environment? Allowing health care professionals to use personal mobile devices at work, known as bring-your-own-device (BYOD), has the potential to support both the hospital and its employees to deliver effective and efficient care. OBJECTIVE: The objectives of this research were to create a mobile app development guideline for a BYOD hospital environment, apply the guideline to the development of an in-house mobile app called TaskList, pilot the TaskList app within Boston Children’s Hospital (BCH), and refine the guideline based on the app pilot. TaskList is an Apple operating system (iOS)-based app designed for medical residents to monitor, create, capture, and share daily collaborative tasks associated with patients. METHODS: To create the BYOD guidelines, we developed TaskList that required the use of mobile devices among medical resident. The TaskList app was designed in four phases: (1) mobile app guideline development, (2) requirements gathering and developing of TaskList fitting the guideline, (3) deployment of TaskList using BYOD with end-users, and (4) refinement of the guideline based on the TaskList pilot. Phase 1 included understanding the existing hospital BYOD policies and conducting Web searches to find best practices in software development for a BYOD environment. Phase 1 also included gathering subject matter input from the Information Services Department (ISD) at BCH. Phase 2 involved the collaboration between the Innovation Acceleration Program at BCH, the ISD Department and the TaskList Clinical team in understanding what features should be built into the app. Phase 3 involved deployment of TaskList on a clinical floor at BCH. Lastly, Phase 4 gathered the lessons learned from the pilot to refine the guideline. RESULTS: Fourteen practical recommendations were identified to create the BCH Mobile Application Development Guideline to safeguard custom applications in hospital BYOD settings. The recommendations were grouped into four categories: (1) authentication and authorization, (2) data management, (3) safeguarding app environment, and (4) remote enforcement. Following the guideline, the TaskList app was developed and then was piloted with an inpatient ward team. CONCLUSIONS: The Mobile Application Development guideline was created and used in the development of TaskList. The guideline is intended for use by developers when addressing integration with hospital information systems, deploying apps in BYOD health care settings, and meeting compliance standards, such as Health Insurance Portability and Accountability Act (HIPAA) regulations. JMIR Publications Inc. 2016-05-11 /pmc/articles/PMC4880739/ /pubmed/27169345 http://dx.doi.org/10.2196/mhealth.4424 Text en ©Soleh U. Al Ayubi, Alexandra Pelletier, Gajen Sunthara, Nitin Gujral, Vandna Mittal, Fabienne C. Bourgeois. Originally published in JMIR Mhealth and Uhealth (http://mhealth.jmir.org), 11.05.2016. https://creativecommons.org/licenses/by/2.0/This is an open-access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0/ (https://creativecommons.org/licenses/by/2.0/) ), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mhealth and uhealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included. |
spellingShingle | Original Paper Al Ayubi, Soleh U Pelletier, Alexandra Sunthara, Gajen Gujral, Nitin Mittal, Vandna Bourgeois, Fabienne C A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies |
title | A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies |
title_full | A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies |
title_fullStr | A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies |
title_full_unstemmed | A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies |
title_short | A Mobile App Development Guideline for Hospital Settings: Maximizing the Use of and Minimizing the Security Risks of "Bring Your Own Devices" Policies |
title_sort | mobile app development guideline for hospital settings: maximizing the use of and minimizing the security risks of "bring your own devices" policies |
topic | Original Paper |
url | https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4880739/ https://www.ncbi.nlm.nih.gov/pubmed/27169345 http://dx.doi.org/10.2196/mhealth.4424 |
work_keys_str_mv | AT alayubisolehu amobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT pelletieralexandra amobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT suntharagajen amobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT gujralnitin amobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT mittalvandna amobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT bourgeoisfabiennec amobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT alayubisolehu mobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT pelletieralexandra mobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT suntharagajen mobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT gujralnitin mobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT mittalvandna mobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies AT bourgeoisfabiennec mobileappdevelopmentguidelineforhospitalsettingsmaximizingtheuseofandminimizingthesecurityrisksofbringyourowndevicespolicies |