From the first time patients' medical history was documented by Hippocrates was documented around 400 BC, healthcare has come a long way in patient services. The technological advancements have been a major reason for a lot of developments in healthcare industry. However, the advent of mobility has changed the landscape drastically. Mobility finds its uses in so many functions of healthcare, that it is a wonder we survived so long without it. From payer-provider networks to doctor-patient interactions to remote help during critical procedures, connected smart devices find their use everywhere.
1. Numerous use-cases, multiple services, and innumerable benefits – these define the M-services in the business of health. However, there are some underlying features that all these services must have in order to be viable for consumption. These are more like the building blocks that need to be put together to create large-scale services.
2. Authentication – The most simple (seemingly) and basic feature requirement is the ability to connect and securely log on to internal enterprise systems from wireless devices. There are single-factor, two factor, and multi-factor authentication mechanisms that can be used. The service should support the same.
3. Encryption – Most data in the healthcare vertical is sensitive, confidential, and regulated through various compliance frameworks. It is important to be able to securely store and transmit data. FIPS 140-2 validated 128, 196 or 265-bit AES encryptions are standard for securing data and maintaining tunnels from the device to the datacenter.
4. Application Persistence – Even when network connections are interrupted, as might happen when a physician enters an elevator or an ambulance traverses a tunnel, The app should have the ability to maintain both the network session and any open applications. Applications shouldn't lose data even when in the middle of a transmission.
5. Internetwork switching – When users cross network boundaries and access multiple networks, the application should automatically handle any separate network logins without requiring user intervention. This is especially relevant for cellular communication, since the user might be in a spotty coverage area. Switching access points wile roaming on a wi-fi campus is another use case.
6. Policy control – Policy Management heightens security and productivity by controlling how applications, users and devices access networks. It is possible to allow only specific clinical applications, prohibit Web browsing, only allow access to an intranet or specific clinical sites, or to set restrictions based on connection speed or time-of-day.
7. Network Access management – Network Access Management verifies that devices meet the pre-requisites such as patches, operating system updates, and active antivirus with current signatures – before allowing a connection.
8. Quality of Service – Traffic-shaping capabilities give priority access to network bandwidth to the most critical applications, so that Web browsing or large file downloads don't interfere with the medical mission. Patient monitoring systems or applications that physicians depend on such as point-of-care, CPOE or PACs, may be assigned higher priority than scheduling and billing.
9. Device Management – Managing hundreds of devices deployed throughout a medical center, inside ambulances or carried by roaming home-health workers is difficult, especially when management activities can't risk interfering with clinical duties.
10. Analytics and Notifications – Monitoring performance across multiple networks is a challenge, especially when those networks are outside of IT's direct control. Analytics report on device and network usage, while notifications alert administrators about problems – often before they reach a threshold that could impact clinicians. This can dramatically decrease help desk calls, and assist in resolving issues before they impact patient care.