Technical overview: connectivity
An application can access a health record in several ways.
This model is designed for user-facing websites. The website can redirect a person to HealthVault to create an account or sign into an account. The user then authorizes the web application and is redirected back to the website. The website is passed sufficient information to subsequently access the health record of the person.
- The web application redirects the user to HealthVault
- The user authorizes the application
- HealthVault redirects the user back to the application
- The application stores the information sent back
- The application connects to the health record
See web connectivity.
This model provides a way to perform offline authorizations. The application creates a "connection request" with an arbitrary secret question/answer. The patient goes to HealthVault to respond to the connection request with the correct secret answer. In the meantime the application polls the HealthVault service at regular intervals to check for new authorizations.
- The provider collects an answer to a secret question.
- The provider creates a connection request and gives the user a pickup code.
- The user visits the HealthVault website.
- The user enters the pickup code and authorizes the application.
- The application learns about the authorization through polling.
See Patient Connect.
This model is designed for native software running on tablets, phones and other mobile devices. The client application communicates with HealthVault directly.
- The user installs a mobile application.
- The application detects the lack of authorization.
- The application opens an embedded browser and redirects to the authorization page.
- The user authorizes the application.
- The application detects and saves the authorization information.
Putting it together
HealthVault supports multiple connection methods for different types of application scenarios.
Next, learn about reading and writing data.