Overcoming hurdles to mHealth adoption

In a blog written 16 months ago, I named four hurdles to mHealth adoption (listed below). I suggested these issues would require swift resolution in the face of mobile's growing momentum in healthcare. So how are we doing? Let's look at my comments about each – from 2010 and today.

Issue 1: Business model
Then: A number of mobile health business models are developing, including provider services, direct-to-consumer and clinical technology integration. But questions remain over who will ultimately bear the costs for mHealth solutions – payer, provider or patient?

Now: If the 2012 Annual HIMSS Conference & Exhibition is a bellwether, the gold rush is in full fury, and revenue concern is running a distant second. To borrow a Bible phrase, “Many are called, but few are chosen.”

Issue 2: Security
Then: In a recent survey conducted by HRI, physicians cited security as their No. 1 concern about adopting mHealth solutions. To “bulletproof” sensitive information shared via wireless, mHealth suppliers may be compelled to adopt multifactor ID or security architecture akin to online banking – which could be cumbersome.

Now: In general, vendors have done yeoman-like work in embedding encryption, auto ID and device security features into their solutions. But incredibly, despite a slew of data breaches, mobile security isn't receiving the urgent attention it requires from IT departments.

Issue 3: Regulatory compliance
Then: Beyond HIPAA, the Food and Drug Administration, which regulates medical devices, is developing new guidelines for mobile health applications and devices. The agency just published a report on its 510(k) approval process for medical devices. Not to be outdone, the FCC has announced a proposal to create a new medical program experimental radio license that would create test-bed facilities, where manufacturers and developers could try out new wireless medical technologies and assess their operational readiness.

Now: The FDA has produced a list of mobile medical devices that can be regulated, but many loose ends remain. The FCC is focused on the national broadband plan; mobile health must wait.

Issue 4: Standards
Then: The ever-expanding universe of mHealth innovation has spurred concerns about a set of common standards for mobile devices and applications. Ideally, open standards (outfits like Continua Health, the mHealth Alliance, HIMSS and others are working on this) will head off the inclination of technology companies to offer their own standards sets that may require substantial retooling in the future.

Now: Still very much a work in progress, with disturbing echoes of the clinical data standards mess.

Conclusion
Then (and now): It's a mistake to conclude that these issues, which have had such a braking effect on the adoption of tethered solutions like the EHR, will exercise a similar influence on the evolution of the mHealth market. The evidence to date just doesn't support any other conclusion but that mHealth is going to become foundational to healthcare ¬–¬ faster, better, cheaper.

Rick Krohn is the president of HealthSense, Inc. and co-editor of the new HIMSS publication “mHealth: From Smartphones to Smart Systems.” The book is available in print and eBook editions.
 

Comments

red bottom shoes
We offer the Discount Christian Louboutin Shoes here covering complete collection of stunning Shoes, Boots, Sandals. our site is www.discountchristian-louboutinsale.tk
red bottom shoes http://www.discountchristian-louboutinsale.tk
Jeff Brandt
Thanks Rick for your great list. I would like to add two more Issue. Issue 5: Understand the mHealth Eco-system:
Many of the so called health apps have very little to do with the healthcare system. Mostly because there is little healthcare interoperability knowledge in the companies developing these systems. That is not to say that they don't have doctors on staff. What is needed is Medical Informatist that understand the health data eco-system, how to move and share data between systems. Issue 6: Data Silos: Today Apps are producing thousands of data "Silos". This is already and issue with our EHRs. Patient collected health data offers very little help to the patients or providers locked in the phones. True mHealth apps must be able to share the data and in a way that is understand by all stakeholders. This means being part of the providers and caregivers workflow. Jeff Brandt is CTO of Communication Software, Inc. Contributing Author new HIMSS publication “mHealth: From Smartphones to Smart Systems.” and Co-Chair of mHIMSS FAQs

Post new comment

* Fields marked with an asterisk are required.
No HTML code or hyperlinks are allowed in comments.
Login or create an account to save your mHIMSS profile.
By submitting this form, you accept the Mollom privacy policy.