As Accountable Care Organizations and medical homes start thinking about alternative quality contracts that reimburse for keeping patients healthly and not for delivering more care, it's likely that wellness care will include home telemonitoring between clinician visits.
Devices will include electronic scales for measuring fluid retention in CHF patients, blood pressure measurement for refractory hypertension, glucometers for diabetics, and home spirometry for patients with COPD or asthma.
I recently tested a home monitoring product that illustrates the future of consumer healthcare devices, emerging approaches to interoperability, and the need for consistent transport standards.
The Withings Internet Connected Body Scale incorporates several mainstream technologies to achieve a highly functional result. Here's how it works:
After taking the scale out of the box, you connect it to your USB port (only used during setup) and launch the scale configuration website. You specify the wireless access point and security settings to use and link the scale to a web-based account. You set up users in your account and provide basic height/age/preferred method for body mass index calculation. Technologies used - WiFi with WEP or WPA security, HTTPS, and USB.
Once the scale is associated with your account, using it is simple. When you stand on the scale, it wirelessly uses a RESTful protocol to compare your weight with the list of known scale users on your account, probabilistically choosing the right user by matching weights. It retrieves demographic information, calculates body mass index, and % body fat, then sends the data to the user account.
Once posted, there are multiple data options - graphing over time, PDF of measured weights, automated posting to Google Health, automated posting to Microsoft Healthvault, and even posting in realtime to Twitter (I'm not sure who would want to do this). Technologies used include PDF rendering, calling the Google API, and calling the Microsoft Health API.
I had my Withings scale updating my Google Health account (shown above) in real time via WiFi in about 5 minutes after opening the box. No programming or technical knowledge was required. This illustrates the power of standardized APIs.
Here's the technical detail of how the scale's API works.
A few observations on interoperability.
Although Withings did something remarkable by incorporating WiFi, WEP, WPA, HTTPS, REST, Google Health, Microsoft Health, and PDF in one product, it does require that the device posts to the Withings website and that this website manages interoperability with other website APIs.
Per the discussion by the NHIN Direct Implementation Group, imagine a world in which all vendors have agreed on a consistent RESTful or SMTP-based transport protocol using a well defined addressing mechanism, such as described in my Health URL blog. Imagine that the payload adhered to a consistent, vocabulary controlled format such as the work being done by the Continua Alliance. The scale could directly interact with Google, Microsoft or other vendor sites. The only scale configuration needed is to specify the Health URL of each user.
As Beacon Communities focus on advanced interoperability that engages patients and families for disease management, I'm confident that devices such as the Withings scale will be widely deployed in homes.
Over the next few years, I'm hopeful that devices will evolve from interoperability that works by embracing multiple proprietary APIs to a single simple interop that begins with common transport and addressing standards and progresses to demand for rapid adoption of common content standards.
Kudos to the Withings engineering team for great steps on the journey to bring interoperability to the home.
0 comments:
Post a Comment