This page contains a Flash digital edition of a book.
Mobile Device Usage in Healthcare


Follow These Tips and Compliance is a Cinch


WRITTEN BY BRIEN POSEY O


NE of the big trends in IT at the moment is bring your own device (BYOD). Today users


expect to be able to access corporate data not just from their desktops, but also from consumer electronic devices such as tablets and smart phones. When providing wireless device users access to corporate data, maintaining compliance with the Health Insurance Portability and Accountability Act (HIPAA) can be a bit more challenging. This article discusses several considerations for supporting mobile device usage in a healthcare environment. HIPAA does not differentiate


between computing devices. Any device that a user uses to access


network resources is defined as a workstation, whether it is a desktop, tablet, smartphone or other device. Therefore, one of the first provisions that must be taken into account is 164.310(C) Standard Workstation Security. This requirement states that organizations must implement physical safeguards for all workstations that access electronic protected health information (ePHI) to restrict access to authorized users. Another important requirement


that must be addressed is 164.310(D) (1) Device and Media Control. This requirement states that organizations are required to implement policies and procedures that govern the receipt and removal of hardware and electronic


18 CONNECTION/HEALTHCARE IT 2012.Q3


media that contain electronic protected health information into and out of a facility, and the movement of these items within the facility. To paraphrase these requirements:


Any computing device that is used to access electronic health records must be configured securely, and if a computing device stores EHRs then its whereabouts must be tracked.


Mobility and HIPAA Compliance Obviously the previously stated requirements present some major challenges when it comes to BYOD. After all, the organization does not own an end user’s personal mobile device, and therefore has no control


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36