As I see it, hospitals have developed a new and rapidly emerging problem when it comes to managing mobile health services. Not only do they face major obstacles in controlling staff use of tablets and smartphones, they’re right in the center of the growing use of these devices for health by consumer. It’s BYOD writ even larger.
Admittedly, most of the consumers who use mobile devices don’t rely that heavily on them to guard and guide their health. The healthiest of consumers may make a lot of use of wearable fitness bands, and a growing subset of consumers may occasionally leverage their phone’s video capabilities to do telemedicine consults, but few consumers base their medical lives around a mobile device.
The chronically-ill patients that do, however, are very important to the future of not only hospitals — which need to keep needless care and readmits to a minimum if they want to meet ACO goals — but also the insurance companies who finance the care.
After all, the more we dig into mHealth, the more it appears that mobile services and software can impact the cost of care for chronic conditions. Even experiments using text messages, the lightest-weight mobile technology available, have been successful at, for example, helping young women lose weight, change their diets, and slash their risk of cardiac problems. Just imagine the impact more-sophisticated technologies offering medication management, care coordination, blood glucose and pulse ox tracking could have on patients needing support.
But there’s a catch here. A long as mHealth services are delivered via the patient’s own device, the odds of successfully rolling out apps or connected health monitoring services are minimal. I’d argue that such mHealth services will only have a major impact on sick patients if the technology and apps are bolted to the hospital or clinic’s IT infrastructure. And the operating system used by patients, be it Android or iOS, should be the same one the hospital supports among its employees, or maintaining apps, OS upgrades and patches and even firmware upgrades will be a nightmare to maintain.
Given the security and maintenance issues involved in fostering a connection between provider and patient, I’d argue that providers who are serious about advanced mHealth services absolutely must give targeted chronically-ill patients a locked-down, remote controlled smartphone or tablet (probably a smartphone for mobility) and lock out their networks from those trying to use connected apps on a rogue device.
Will this be expensive? Sure, but it depends on how you look at costs. For one thing, don’t you think the IT staff costs of managing access by various random devices on your network — or heaven forbid, addressing security holes they may open in your EMR — far exceed even the $700-odd retail price for such devices?
This might be a good time to get ahead of this issue. If you’re forced to play catch up later, it could cost a lot more.