Difference between revisions of "Microsoft HealthVault"

From Clinfowiki
Jump to: navigation, search
(Security features)
m (References)
Line 28: Line 28:
  
 
(2) HealthVault press release: http://www.microsoft.com/presspass/events/healthvault/default.mspx
 
(2) HealthVault press release: http://www.microsoft.com/presspass/events/healthvault/default.mspx
 +
 +
(3) http://www.microsoft.com/presspass/events/healthvault/docs/HealthVaultFS.doc
  
  

Revision as of 11:04, 13 November 2007

On October 4, 2007, Microsoft(R) Corporation released Microsoft HealthVault (1,2). Microsoft has taken pains to clarify that HealthVault is not intended to be a personal health record (PHR), but instead will be a platform that could service numerous personal health applications (PHAs). Several features of this platform include:

  • Interfaces to support medical and monitoring devices
  • Security features

Integration with PHAs and medical devices

To encourage integration of PHAs and medical devices with HealthVault, Microsoft provides developers with a free software development kit (SDK) and has published the APIs for HealthVault. Microsoft does not host third-party applications that have HealthVault interfaces; instead, developers host their own applications and create their own business models.

Microsoft has already partnered with a number of medical device vendors to allow information to be uploaded to HealthVault. The end user achieves device integration by going to the Connection Center on the HealthVault website. Devices include monitors for blood pressure, heart rate, and glucose from manufactures including Omron, Microlife, Lifescan, and Polar.

Security issues

To ensure private and secure storage, According to its press release Microsoft houses HealthVault "in the same secure data centers that run other Microsoft online services, but ...HealthVault traffic [is isolated] onto a virtually separate network servers [are located] in physically separate, locked cages" [3]. All data is encrypted on transmission, even inside the data center. A "minimal access data model" is used to constrain the data that is shared with other people, PHAs, and devices.'

Authentication is simply by password when HealthVault is used as a standalone PHR. For HealthVault to fulfill its promise as a platform for an interoperable PHR, more complicated authentication issues will need to be solved. Microsoft states that patient users can grant access into their HealthVault to trusted partners like their personal physicians.

Business model

Microsoft plans to monetize HealthVault based on its search engine (HealthVault Search). Queries may be directed based on personal health content stored in HealthVault. However, users will be given the option of not passing on health information to HealthVault search.

Benefits and concerns

Microsoft reports a commitment to interoperability with a multitude of applications and devices by creating interfaces that are compliant with standards such as the ASTM Continuity of Care Record (CCR) and HL7 Clinical Document Architecture (CDA). However, it is well recognized that standards such as these incorporate a great deal of latitude in encoding data. Thus, two systems can be entirely compliant with these standards without being able to parse each other's content.

Microsoft's entry into the arena is likely to set more restrictive de facto standards for encoding data, much as Microsoft Word has become a de facto standard for encoding word processing data. This is a double edged sword. Microsoft's more restictive standard could become a lingua franca among PHAs, devices, and even EHRs. On the other hand, Microsoft's history of incorporating, then modifying and co-opting standards (such as Java) creates concern about Microsoft's commitment to interoperability using community-derived terminologies and messaging functions.

References

(1) HealthVault site: http://www.healthvault.com/

(2) HealthVault press release: http://www.microsoft.com/presspass/events/healthvault/default.mspx

(3) http://www.microsoft.com/presspass/events/healthvault/docs/HealthVaultFS.doc


Stephen E. Ross MD University of Colorado - Denver School of Medicine