HealthVault now supports Global Availability. Multiple HealthVault instances collaborate to bring HealthVault to audiences around the world. See the HealthVault documentation
In order to support multiple instances, applications must keep track of which instance the record in use resides. Calling ConnectionFactory.GetConnectionForInstance() will return a connection with the correct urls for HealthVault. The ui-jaxb sample application
has been updated to demonstrate the behavior.
When redirecting the Shell, a new class ShellUrlBuilder will correctly create redirect Urls. If your application is multi-instance aware, set the property setAllowInstanceBounce(true). During sign in, the user may bounce to a different HealthVault instance
than originally redirected to. When returning to your application, the query string parameter "instanceid" will let you know in which HealthVault instance the user authorized their record.
The Android sample will automatically detect the correct instance and set HealthVault's platform url correctly.
Configuring Globally Aware applications is a little tricky right now. HealthVault has two instances: US and UK. You will need to configure your application in both instances if you want to be global.
If you are outside of the US, use:
Config Center: config.healthvault-ppe.co.uk
If you are inside of the US, us:
Config Center: config.healthvault-ppe.com
If you can configure your application in both config centers, you can configure your application to be globally aware and automatically detect the best instance for your consumers. To create your application in both instances:
- Create two Microsoft Accounts
- Use one to create a HealthVault account in the US
- Use one to create a HealthVault account in the UK
- Use the appropriate HealthVault account to configure your application in each instance
In order to use the US config center, your HealthVault account must say that you are within the US -- you can set it to whatever you like.