PB6 Released

  • Article

The PB6 release of the platform and SDK are now live on the PPE servers. You can download the SDK from the usual place.

The following are the major features for the release.

Fetch size control

By default HealthVault will only return a certain number of "full" health record items for any query. It then returns the "keys" for the remaining items that matched the query which can then be queried for by ID. HealthRecordItemCollection automatically manages this paging for you. However, if you want further control over the count of full items retrieved on each request, MaxFullItemsReturnedPerRequest can be set to optimize for smaller sets of data. For example, let's say the data being retrieved is being displayed in a GridView and the results are shown 10 items per page. Rather than get the default number of full things, you can request 10 full items per request. Then only if the user clicks to the second page would you need to get the next 10 items.

Versioning

PB6 now allows us to version data types.  HealthRecordItem.IsDownVersioned can be used to determine whether an application is able to update a specific data item.

Patient Connect

The Microsoft.Health.Package.ConnectPackage class is used to support the Patient Connect scenario.

Group Membership Type

The GroupMembership type is used by an organization to indicate that the person described in the record is a member of a specific group. Here’s a scenario:

  1. An employee goes to an employee portal and registers to take advantage of a fitness benefit which allows them to use an application to track their progress.
  2. The employee authorizes the portal to write to their HealthVault record, and the portal writes a group membership entry where name=”SpecialProgram”, value=”FabrikamFitnessProgram”.
  3. The employee runs the fitness application, and authorizes is to see GroupMembership instances. The application queries and finds the FabrikamFitnessProgram instance, and verifies that the instance was created by the employee portal.
  4. The application allows the user to use the program, and bills the company for the benefit.