How-To Guides

The steps for generating your own ApplicationID, generating a public/private key pair, providing the information to the HealthVault team, and installing and configuring the certificate.

Explains when and how to use master and child application IDs.

Information about the HealthVault Developer environment and the HealthVault Consumer environment.

Instructions for creating a HealthVault Hello World application.

Instructions for creating a simple HealthVault SODA client application.

Each application must register an ActionUrl on the HealthVault server. The page at this ActionUrl should be capable of understanding ten different targets that can be passed to the application by the HealthVault Web site.

Dynamically redirecting and handling shell targets

Information about interfaces between Web applications and the HealthVault Shell

Information about batching queries and deciding when to use batching.

Code for the file wrapper you can use to upload files to HealthVault.

Enabling firewall ports.

Master and child application IDs can be used for single-practice systems and for multi-physician or multi-practice online services, such as online electronic medical records and e-prescribing services.

Make sure that patient data is sent to the right person's HealthVault record from a clinical system that has no online front-end for the patient.

Review example scenarios of data exchange between HealthVault and a HealthVault-compatible clinical system.

Strategies for working around issues with non-PnP buses

You can control the way your application or device appears in HealthVault Connection Center.

Using reg files or add-in wrapper icons to switch between environments

Steps to debug your device driver when you receive a "This device cannot start. (Code 10)" error message

Information about Windows Portable Devices (WPD) technology used for HealthVault-compatible devices

How to add an extension to an existing data type.

If the data type you need doesn't already exist, you need to create a custom data type. If you need more than one custom data type, you need to create a wrapper that you can use with each custom data type.

Information on how to contact the HealthVault team to create a new platform Data Type. This is useful when you think your date can be used across multiple HealthVault ecosystem applications.

Information about the properties of the HealthRecordItem data type

Converting measurement units between display values and stored values

Information about and code for the PersonalImage type, which encapsulates the picture in a person's health record.

Using different views to track the history of a data item

Working with vocabularies, and with CodedValue types and CodableValue within a vocabulary.

Accessing schemas programmatically.

Working with Continuity of Care Records and Continuity of Care Documents in HealthVault

Information about using CCR data in HealthVault, including detailed descriptions of the transforms used to import and export data to and from a CCR.

Keeping original versions of data types distinct from updated versions

Explains the use of version stamps

How to redirect to the HealthVault Shell’s authentication and authorization pages, plus some information on simulating single sign-in using an offline connection

Optional authorization allows the user to authorize access to individual data types.

A few details on building an application that can work with multiple health records simultaneously. This is in contrast to a Single-Record Application that always operates with a single record in scope.

The HealthVault platform relies on asymmetric key cryptography to ensure that a rogue application cannot imitate a legitimate application. This document describes how to generate your private key – public key pair and register the public key with HealthVault.

Offline connections can be used to simulate single sign-in or to allow a batch process to read to and write from HealthVault records.

Using digital signatures to verify the sources of data items

Enabling firewall ports.

CAS permissions and security demands required to run a HealthVault ASP.NET application.

Steps to debug your device driver when you receive a "This device cannot start. (Code 10)" error message

Useful for debugging traffic between your application and the HealthVault servers

A few things to try if you are having connection issues with your HealthVault application

Using the Troubleshooting utility to diagnose certificate and network problems