Rich client options

Most of our HealthVault documentation on samples focuses on building web applications but you can also use HealthVault with your rich client application.  We support two high-level approaches to doing this: Intermediate web app With this approach, your rich client application communicates with a web service that you develop.  That web service, in turn, communicates…

0

More about data type versioning

This is a supplement to Eric’s blog post on Data Type Versioning in HealthVault.  The HealthVault platform is capable of converting V2 items into the V1 schema and vice versa.  In order to simplify things for app developers, the platform will convert all versions of a type into versions that it believes this app understands.  It makes…

0

App authorization — "what the app asks for" vs "what the user authorized"

There are two different elements that you are likely to think about when you think “authorization:”  * the amount of access that your app requests — required and optional auth rules  * the amount of access that any particular user has granted Think of the first as a domain table, perhaps, and the latter as a…

0

What access do I have?

If you are using Optional Access in your HealthVault authorization rules, then at times you may want to know whether a particular user has authorized an optional piece of the data type access.  You can find out what actions are currently authorized for a {user, record, app} by calling PersonInfo.SelectedRecord.QueryPermissions.  You can read more about…

1