Boston Children’s doc shares best practices for building mHealth solutions

Man typing on laptop at desk

Successful bring-your-own-device deployments for healthcare providers require a strategy that identifies potential issues that could arise, as well as the potential return-on-investment.

In addition, there must be pilot phases and battle-testing of solutions to eliminate challenges. Then comes developing a deep launch team and outlining an educational and training plan.

Those requirements, according to Michael Docktor, M.D., clinical director of innovation and director of clinical mobile solutions at Boston Children’s Hospital, are just several best practices BCH learned during its two clinical mobile BYOD efforts.

One of the hospital’s biggest decisions, he shares, was whether to build in-house or buy a solution in its effort to deploy a secure texting app in 2012. With the latter option, BCH found limitations, as there were just five choices.

“Beyond the initial cursory review, a deep dive is necessary with each chosen vendor, discussions of features, timelines, integrations and costs which will be a time and resource consuming process,” he recommends.

One thing providers and payers can’t do is nothing when it comes to mHealth, Docktor says, given growing interest by staff and consumers and expectations from both groups for faster, nimbler and more convenient care options.

“Now, more than ever, there is a tremendous groundswell of interest, money and resources begin poured into helping the healthcare industry cater to their mobile workforce,” he says.

For more information:
- read Docktor’s blog post