The "Works with Microsoft HealthVault" Logo Program for Devices
The HealthVault logo helps give consumers confidence that a device is compatible with HealthVault, and associates the device with a premium, trouble-free experience. The logo allows customers to quickly identify products that are designed to work with HealthVault and meet the usability and performance requirements. For the consumers who are looking for a device that works with HealthVault, the devices with a logo will have an advantage over those without one.
Before a device manufacturer can qualify to display a “Works with Microsoft HealthVault” logo on products and packaging, the manufacturer must complete several agreements in addition to certifying the device by a Microsoft-designated independent testing organization to ensure that certain standards of quality and usability are met.
1. Complete the Agreements
NOTE: Development and testing can start prior to completing the agreements.
All manufacturers must complete the following agreements prior to obtaining the logos, branding guidelines, and HealthVault inserts for the device packaging:
- HealthVault Solution Provider Agreement
- HealthVault Logo License Agreement (Amendment to the HealthVault Solution Provider Agreement)
Prior to using the logo or inserts in a product, the manufacturer must complete a HealthVault Logo License Agreement Schedule B for that product. The manufacturer can submit a Schedule B after receiving a passing certification ID from the test lab. The Schedule B is considered complete once the manufacturer receives a counter signed version from Microsoft.
NOTE: It is possible to list multiple products on one schedule B as long each product has a passing certification ID.
Please contact hvlogo@microsoft.com for copies of the agreements or to request logos, branding guidelines and HealthVault inserts once the proper agreements have been signed.
2. Develop a HealthVault compatible driver for your device
Manufacturers wishing to connect their devices to a PC to upload data to HealthVault must develop a driver that is compatible with HealthVault Connection Center (HVCC). HVCC is an application that runs on the PC and manages the data exchange between the device and HealthVault.
There are many different types of HealthVault enabled devices today some of which are fitness watches, pulse oximeters, blood pressure devices, peak flow meters, weight/body composition scales, and pedometers. The HealthVault team encourages the addition of new device types and different varieties of the current device types.
Learn how your device may fit into the HealthVault ecosystem
Download the HealthVault Device Driver Development Kit (DDK) to learn more about how to develop a HealthVault-enabled driver for your device
Browse a directory of consultants that may be able to help you develop a driver for your device
3. Certify Your Device
The Works with Microsoft HealthVault Test Kit includes the requirements, test procedures, and tools required to self test your device prior to submitting to a Microsoft-designated independent testing lab (ITL). The ITL will use the same requirements, test procedures and tools to verify your device has passed the tests.
NOTE: ITLs will test against the Works with Microsoft HealthVault Device Logo Program v1.0 requirements up until June 24, 2009. All devices submitted to an ITL after June 24, 2009 will need to conform to the Works with Microsoft HealthVault Device Logo Program v1.20 requirements.
Browse the directory of consultants for a Microsoft authorized test lab that can certify your device
Once you have found a test lab, please contact them directly to certify your device and obtain a certification ID.
HealthVault Self-Testing
The Works with Microsoft HealthVault Test Kit includes a set of HealthVault Logo Testing Instructions. Manufacturers are encouraged to self test their devices using these test cases prior to submitting to the ITL to increase their chances of passing the verification test.
Note: The devices that are submitted to the testing lab for verification must have the firmware that will be released to market. Therefore, you should self test using that firmware.
HealthVault Certification Testing
Once your device passes the self-test, submit it to the ITL for verification. Be sure the device is programmed with the firmware you will be releasing to market, as this is requirement for certification.
Each ITL has their own cost structure and process for submitting products so please contact the ITL directly for details. Browse the directory of consultants for a Microsoft authorized test lab that can certify your device
Once testing is complete, the ITL should provide you with the testing results along with a certification ID if the device passed. Once you have the certification ID, you are ready to complete and submit the Schedule B. Please contact hvlogo@microsoft.com for a copy of the Schedule B.
NOTE: No product can use the logo until a Schedule B has been completed specifically for that product.
Windows Hardware Quality Labs (WHQL) Testing
The device driver is required to pass WHQL in addition to the HealthVault certification tests. If your driver has not passed WHQL, the ITL cannot give you a certification ID. Some of the ITLs will provide WHQL services in addition to HealthVault certification. Please contact the ITL for details.
For more about WHQL testing, please follow this link:http://www.microsoft.com/whdc/getstart/testing.mspx