Issue link: https://viewer.e-digitaledition.com/i/101407
assertion would be an unremarkable platitude of risk management, but in health care, continues Gallagher, by and large, that���s not the case. ���Usage of mobile devices should be managed by IT departments,��� says Gallagher, who regularly advises the Office of the National Coordinator on this issue. ���They���re going to need to decide what types and models of devices they will support.��� Still, with users pulling toward universal access and risk management specialists urging caution where personal health information (PHI) is concerned, creating mobile security policies is a process of negotiation and accommodation. This can be seen as a terrain/fence conundrum. In risk management, the more valuable the terrain is, the bigger the fence needed to surround it. If users chafe at high fences, one solution may be to devalue the terrain, which can be done through a combination of technology and access policies. So, for example, says Gallagher, ���The organization is probably OK in allowing the contract physician to access or view records in an ASP [application services provider] model, accessing it across an Internet connection that is secured with a VPN [virtual private network] and viewing patient information.��� In other words, physicians can view data but cannot download or store it, making the device less risky, as it is generally free of PHI unless physicians are actually using it. Another way to devalue the terrain, says Brill, is to focus on tasks rather than devices. ���First, you think about functionality,��� he says. ���What do you want to be able to do remotely? It may be that there are things you would normally do at your desk but that you are not needed to do remotely. So, for example, at your desk, you might have access as an administrator to insurance and payment and credit card data. You probably don���t need that if you are working remotely. ���If you do need it, it would be on an exception basis, so you start to get the ability to say, ���What is it I need to do both functionally and at a more micro level?��� By matching requirements with capabilities, you start to get a [security] model based on a need to access through mobile means, as opposed to, ���Let���s just duplicate everything we have and assume it will all go well.������ In this way, any one device will have had only narrowly defined data sets pass across it, thus limiting the possibility of large-scale data breaches based on a single missing device. security shopping list What about the nuts and bolts of securing mobile devices? + application level encryption, which creates a unique encryption just for that application, is preferable, says Andrew Jaquith, CTO at Perimeter E-Security and former senior analyst at Forrester Research. + autodestruct functions are also desirable, continues Jaquith. Such functions can prompt the device to wipe itself after a certain number of incorrect password entries. + No jail-broken devices should access organizational data, says Murphy. + Finally, black lists or white lists (essentially, ���not-these��� or ���only-these���) of applications may be the way to go, with IT monitoring devices to make sure they are compliant. How do you juggle all these balls at once? Jaquith suggests a mobile device management program (MDM). A sort of app-of-apps, MDM might offer firmware over-the-air updates, diagnostics, remote access and security functions, as well as serve as a gatekeeper for apps. Furthermore, MDM obviates some of the discussion about bring-yourown-device security. Instead of having a conversation about every permission and restriction, organizations can offer the user a simpler option: Install our MDM if you want to access our data and applications. That���s a choice everyone should be able to live with. Are you implement ing a mobile device management policy? What have you learned? Follow the discussion at www.MDNews.com. ��� himss mobile security toolkit crEatEd By a volunteer workgroup of Healthcare Information and Management Systems Society (HIMSS) Mobile, the toolkit will help organizations develop and implement mobile security policy for corporate and personally owned devices. The toolkit contains resources with tips on securing a wireless network, smartphones and other mobile devices, as well as a sample user agreement. Visit www.himss.org/ASP/topics_PStoolkit_ MobileSecurity.asp to download the toolkit.

