Share via

HealthVault 0908 Release Notes

  • Article

HealthVault 0908 release is now available in the production and pre-production environments, with this release we are removing the beta label from HealthVault. UPDATE: Associated .NET SDK for this release is now available.

Below is the summary of changes in this release:

SODA (Software on Device Authentication)

SODA enables support for the creation of client and mobile HealthVault applications. Prior to SODA, this was – for the most part – not possible, because it would have required wide distribution of the private key your application uses to authenticate with the platform. SODA allows applications to create ‘instances’ of themselves. These instances are able to provision themselves with unique private keys and everything they need to authenticate with the HealthVault platform. The associated .NET SDK will be available shortly.

Full documentation on SODA is being written and will be posted as soon as it is available.

AllocatePackageID

This new API allows applications to request a DOPU package ID before sending the DOPU package. The DOPU package can then be sent later together with the allocated package ID. In discharge scenarios, for example, a patient does not have to wait until the package has been transferred to HealthVault before receiving the information necessary to later retrieve the package (package ID and passphrase).

CCR / CCD reconciliation improvements

  • Reconcile UI: The UI has been completed overhauled and now consists of three pages – an introduction page, the reconcile page, and a summary page.
  • The introduction pages explains the process and prepares the user. It also provides an option to simply add all the new data and bypass the remaining pages.
  • The reconcile page has been redesigned based on extensive usability research. The page focuses on letting the user see and review the data before adding it to their HealthVault record.
  • The user has the ability to choose not to add items, and to replace an existing item in their record with one from the file.
  • The summary page shows the user all the items added from the CCR to their HealthVault record. If the user came from an application, the summary page provides a link to return to the user to that application.
  • Duplicate Detection: The reconcile page now automatically detects items that are exact duplicates. If an exact duplicate exists in the HealthVault record, we will default the item to not be added to the HealthVault record. The user can override this and add it if desired.
  • Billed vs. Diagnosed Conditions: The reconcile page now automatically detects Conditions that are possibly billed, and suggests that the user review the items before adding to their record. At this time, Conditions coded with anything other than SNOMED CT are flagged for review.

CCR Import / Export

  • Data Mapping Improvements: The ‘tohv’ and ‘toccr’ transforms have been vastly improved. The transforms are now more robust and support the import and export of significantly more data elements to and from CCR.
  • Improved Import Support: The ‘tohv’ transform is now imports the following into their appropriate HealthVault data types: Blood Pressure, Blood Glucose, Cholesterol Profile, Height, Weight. Prior to 0908 these were only imported to the generic vital-sign or lab-test-results data types.
  • Improved Export Support: The ‘toccr’ transform now supports the following new data types: Payer, Directive, Condition, Family History, Allergy, Medication, Immunization, Height, Weight, Blood Pressure, Blood Glucose, Cholesterol Profile, Vital Signs, Lab Test Results, Procedure, Encounter
  • Export to CCR: Users can now export their record to a CCR using the HealthVault Shell. This can be accessed by selecting “See all” in the record switcher, and then clicking the “Export record” link.
  • Documentation: Documentation of the data mappings to and from CCR is being written and will be published to MSDN as soon as it is available.
  • Compatibility: The changes to the ‘tohv’ and ‘toccr’ transforms were significant. If your application is using these transform and begins to encounter issues, the old transforms are still available from platform. The old transforms are available as ‘tohv_v1’ and ‘toccr_v1’. Please note that the old transforms are no longer supported, and are provided as a compatibility fallback only.

Please leave feedback in the comments.