Microsoft HealthVault

From Clinfowiki
Jump to: navigation, search

On October 4, 2007, Microsoft(R) Corporation released Microsoft HealthVault. Although HealthVault is potentially very important for the development of personal health records (PHRs), HealthVault is not a PHR. Instead, HealthVault is a platform that could service numerous personal health applications (PHAs). Microsoft's plan for a secure, interoperabile platform appears more robust than previous failed PHR efforts from vendors, but broad user and developer acceptance of the platform remains speculative.

Integration with PHAs, medical devices, and electronic health records (EHRs)

Currently, the HealthVault interface has minimal functionality. Users can set up accounts and self-enter a medical history. Microsoft, however, 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.

To encourage integration of additional medical devices and PHAs with HealthVault, Microsoft provides developers with a free software development kit (SDK) and has published the APIs for HealthVault. The HealthVault API is accessible from programming environments including Microsoft .NET, Win32, Java, and PHP [3]. HealthVault currently supports only Web applications, but support for client applicaions is being considered for the future. Microsoft does not host third-party applications that have HealthVault interfaces. Instead, developers host their own applications and create their own business models.

One of the most exciting aspects of HealthVault is Microsoft's explicit commitment to creating data exchange interfaces that are compliant with standards such as the HL7 Continuity of Care Document (CCD) and the related ASTM Continutiy of Care Record (CCR). This provides the potential for true interoperability among PHAs and electronic health records (EHRs). However, it is well recognized that standards such as these accomodate a great deal of latitude in encoding data. Thus, two systems can be entirely compliant with CCD and CCR and still have very limited ability 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, extending, and co-opting standards (such as Java) brings Microsoft's ongoing commitment to community-derived terminologies and messaging framerworks into question.

Security issues

To ensure private and secure storage, 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" [4]. 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 provided by Microsoft LiveID (the successor to Microsoft Passport). Third-party applications can inherit authtentication-protected pages. The authorization configuration of applications must be approved by Microsoft before the application goes live, to ensure that the data exchange is limited to the minimal set of data required by the application.

Authentication is relatively straightforward when HealthVault is used as a standalone PHR. Once users create an account, they can enter their own medical history, supplement it with data from a monitoring device such as a blood pressure montior, and use a third-party application registered with Microsoft to get personalized advice based on these data.

Authentication necessarily becomes more complicated for true interoperability, such as exchanging data with a health care organizations's electronic health record (EHR). Hsealth care organizations will need patient users to register their HealthVault with their own systems in some manner. Interaction could then occur in one of several ways:

  • Health care organizations could accept LiveID as authentication
  • Health care organizations could require their own authentication for patient users and require a seperate sign-in to LiveId for online access to HealthVault information
  • Health care organizations could require their own authentication for patient users, and arrange for offline access to HealthVault information

Business model

Microsoft has explicitly stated that HealthVault was not developed as a philanthropic endeavor: it is intended to be an application with a sustainable 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, since some patients will be sensitive about receiving disease-targeted commerical content, users will be given the option of not passing on health information to HealthVault search.

HealthVault is currently only available for users in the United States.

What HealthVault may mean for PHRs

Bert Van Hoof from Microsoft's Consumer Health Soultions discussed HealthVault as part of a late-breaking topics panel at the Americal Medical Informatics Association (AMIA) Annual Sympsoium in Chicago on November 12, 2007. Several times, panel and audience members remarked that Microsoft has done more in one week to promote interoperable personal health records than advocates have been able to do in five years. As the proverbial 800 pound gorilla, Microsoft is one of the few organizations with the market dominance and clout to to get notice from a mulitude of users and developers, which is undoubtedly good for advocates of PHRs. On the other hand, it is understandable that Microsoft's enormity, its commercial interests, and its history of clumsy early releases of products may engender concern and scorn. Nonetheless, if Microsoft is truly committed to supporting a PHA application platoform for the long haul, HealthVault will be a landmark in the history of patient-centered health information technology.

We will learn more about the impact of another 800 pound gorilla, Google, in the PHR field when specifics about Google Health are released in early 2008 [5].

Microsoft HealthVault is a cloud-based platform designed to put people in control of their health data. It helps people collect, store, and share health information with family members and participating healthcare providers. It connects with a variety of third-party applications and devices to help people manage their fitness, diet, and health data. It offers a privacy- and security-enhanced foundation on which a broad ecosystem of solution providers, device manufacturers, and developers build innovative new health and wellness management solutions. [1]

HealthVault enables a connected ecosystem that currently includes more than 300 applications and more than 80 connected health and fitness devices in the U.S. [1]


HealthVault is a free personal health record (PHR) system with a web based and mobile platforms started in 2007 by Microsoft cooperation. It was originally designed to be used in the United States only but in 2010 it developer expanded it use the United Kingdom. The system allows users to store their health and fitness data. The system interoperate with other wearable healthcare devices (like watches) thereby allowing for the transfer of health and fitness data into the individual HealthVault record. It also allows for the bidirectional storage of medical imaging records. Users are required to create an user’s account. [2]



HealthVault, allows a user to keep his or her personal health information in one place, online, and available to him or her at anytime. HealthVault provides users with the ability to connect to their health record via apps and personal health devices.

  • Apps: HealthVault can connect with over 120 different apps. Examples include: Microsoft Health, New York Presbyterian Hospital, Aetna Personal Health Record, and Louisiana Healthcare Connections. [3]
  • Personal Health Devices: HealthVault can connect with over 251 different devices such as scales, blood pressure monitors, FitBit, and blood glucose meters.[3]

Information and data from these apps and devices can be managed and tracked via your HealthVault record.

The list below shows the different details that HealthVault can keep track of:

  • Medications
    • CVS Pharmacy offers connection of your prescriptions to your HealthVault: Your CVS/pharmacy prescription history (up to the previous 18 months) will be sent to your HealthVault record once you complete the connection process. Future updates to your prescription history will be made to your HealthVault record on a daily basis. New prescription information will be sent to your HealthVault record within 48 hours of in-store pickup. [4]
  • Allergies
  • Health history
  • Fitness
  • Blood pressure
  • Lab results
  • Conditions and illnesses
  • X-rays, scans, and other images
  • Health and wellness data. [3]

HealthVault also allows a user to:

  • be prepared for upcoming doctor appointments by bringing current medication and allergy lists
  • have health data readily available for emergency responders
  • obtain health records, lab results and medication histories from health centers a user visits
  • monitor health and fitness goals. [3]

HealthVault provides users with the ability to connect to their health record via apps and personal health devices.

    • Apps: Over 120 apps, including


  1. 1.0 1.1 Microsoft HealthVault
  2. Microsoft HealthVault
  3. 3.0 3.1 3.2 3.3
  4. Connect My CVS/pharmacy Prescriptions to My Microsoft HealthVault Record


External Links


  1. HealthVault site:
  2. HealthVault press release:

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