nology developers are using to structure and present content in browsers. Before choosing an app that utilizes HTml5, consider which browser you use, as not all browsers are HTml5 compatible. • Smartphone or tablet? Find out if the app is designed for each of these device types. In doing so, you will improve your user experience. • Features. Consider calculations, interactions, notifications, favorites, and tools. ask yourself: am I able to perform the same functions using a mobile device as a PC? even though a mobile device will not provide all the same features as a PC or support full transactions, it should have all the practical features you will need to do your work. FEATURE sTOrY THe jOurNal OF THe HealTHCare BIllINg aND maNagemeNT assOCIaTION 13 • Offline usage. Determine which features must be available offline, if any. If you don’t have an Internet connection, you will not be connected to the “backend,” and you may not have access to some of the data or features you need. Mobile Device Management The HIPaa Privacy rule causes concern for those who wish to employ mobile technology throughout their organization. However, mobile device management (mDm) incorporates greater visibility and control of the endpoint device. mobile framework must manage not only the business applications, but also the devices themselves. Conducting a mobile assessment should be an IT department’s first step. Organizations should evaluate the following: • How do we secure devices, data, and apps? • What type of policies, governance, and support does our organization need when supplying new mobile device technology? • What access and storage limitations must be implemented and enforced to protect proprietary information while enabling access to low-risk edge applications? evaluating the features related to each mobile operating system (Os) is just as important as assessing the tasks and features of mDm products. all mDm products offer the ability to configure PINs and passwords; however, each mobile Os determines the PIN or password length, strength, and complexity. mobile framework must manage not only the business applications, but also the devices themselves. The following are features to look for: REMOTE WIPE • several products offer remote wipe, but does yours report the status after the wipe has been completed? • Does your product begin a wipe if the product has been compromised, or only if a user initiates the remote wipe function? PASSWORD POLICIES • utilize the mDm’s application sandbox to encrypt passwords and sensitive data. ENCRYPTION • Data at rest and in transit should be protected from unauthorized users or devices. • review the network traffic between the device and servers, as well as any files saved by the application or transferred during backups. • encrypt backup files and employ end-to-end data encryption. • Full disk and memory encryption are critical with the use of sIm/sD cards. • ensure the level of encryption is not weak and cannot be easily penetrated. CODE SIGNING • Code signing confirms the author and checks that the code has not been corrupted or altered since the last signing. • Version information can also be provided. • This is primarily for the use of developers. Improve Response Time and Control mobile technology in healthcare supports the knowledge we appreciate having access to. The mobile technology trend is here to stay, so be excited to access software that is fluent, improves response time, and offers more control of claims processing. Implementing security protocols or mobile device management are steps organizations can take to ensure the privacy and confidentiality of patient information. Lauren Collins has almost 20 years of experience designing and implementing global network infrastructures.
Billing_NovDec14
To see the actual publication please follow the link above