HealthVault Application Information

Download the HealthVault Application Information Template (TBD) and fill it out and email it as part of the Go-Live review process or you copy the below table into a Word document instead.

Company Name
Application Name
ApplicationId
Application Description 1-3 paragraphs about the scenarios that your application enables, how this adds value for users, what data flows into our out of other HealthVault applications and devices, etc. Note that this is a more verbose description than the one in your application configuration. Microsoft will use this description internally in order to educate our business folks about what the coolest applications do. So tell us why your application is awesome!

architecture: Integration Model How do your end users set up and authorize the initial connection with HealthVault? Common answers are:
  • Online
  • Link/Offline
  • PatientConnect
  • DOPU
  • SODA
  • Master/Child : Please mention the expected number of child applications. Online or Offline?
architecture: Trigger What event causes data to be copied between your application and HealthVault? Common answers are:
  • automatic/scheduled job
  • user-initiated
  • provider-initiated
  • event-initiated
  • not applicable as data is always stored in HealthVault
architecture: data flow direction If data is copied back and/or forth between your application and HealthVault, which of these descriptions most closely matches the direction of data flow?
  • Data is only copied from your application TO HealthVault
  • Data is only copied FROM HealthVault to your application
  • Data is copied both ways when a trigger event occurs
  • Data is synced between app & HealthVault in the background
  • All data is native to HealthVault
App Directory Preference Would you like to be listed in the HealthVault Application Directory? Microsoft hosts two directories - a Personal directory which only includes applications that are open to all users and an Industry directory which can include any live application. If you want to be listed, are you eligible for both of the directories or just the Industry directory?

Consultant Did you hire and third-party consultants to assist in developing your HealthVault integration? Such companies are eligible to be listed in our Consultant Directory once one of their clients' applications is live on HealthVault.

Programming Language(s) Which language or languages did you use to write your HealthVault integration? Which languages and technologies does the rest of your application use?

.NET SDK Version : If you used the Microsoft HealthVault .NET SDK, what is the version number on the DLLs that you are currently using? Refer to the file version number by right clicking on the HealthVault DLL's. Select properties and then click on Details Tab. The "File version field" will give you the version number of the HealthVault DLL's that you are currently using. You can find HealthVault DLLs in HealthVault standard installation path: Example:"C:\Program Files\Microsoft HealthVault\SDK\DotNet\Assemblies", We encourage everyone to use the most up-to-date DLLs when they go live. To know which version is the latest version, see the "Version" field under "Quick Details" in HealthVault SDK Download page.

Expected Volume Do you have projections on how many users you expect and how quickly you expect them? Do you have projections on how much data they will be pushing into HealthVault?

Security/Privacy Contact Info

We need a security/privacy contact email address from your company. This will be the alias that we notify if we discover a critical security or privacy issue with your application, or if we discover a critical security or privacy issue with HealthVault that needs your attention. We strongly recommend that this be a shared alias and not a single individual, as individuals can take vacations or can change positions.

Customer Support Contact Info Customer Support information - our agents will attempt to handle simple issues related to your application but if they get asked a more complex question then they will need to refer the end user to your team. Please provide a phone number, email address and/or website where these end users can go for support. On a similar note, if your customer support staff receives questions about HealthVault and needs to refer end users to HealthVault support, please send them to http://support.healthvault.com.

pricing/monetization How do you plan to monetize your application, if at all?
  • Ad-funded
  • subscription
  • one-time purchase
  • not monetized
Test Account Credentials Username & Password for a production account that the Microsoft team can use to explore your application. Account should be populated with reasonable test data once the application's integration with HealthVault is live. Note that the account will often not yet be live when this document is submitted.