|
|
Technical and non technical checklist
Non technical items
| Logo |
A logo that represents the application; it does not need to be the same as the Company Logo in the Application Directory.
Size: 120 pixels (w) x 60 px (h); 120 KB max. |
| Company Logo |
The solution provider's corporate logo appears on both the Web site listing page and on the Web site profile page. This logo is the official corporate logo only. It should not include any positioning taglines or marketing messages. Logo artwork should be prepared to fit within a space of 100 pixels wide by 40 pixels high. Logos should be sharp, easily readable, and rendered in full color on a white or transparent background in PNG format. |
| Company Name |
The solution provider's consumer brand name appears on both the Web site listing page and on the Web site profile page. |
| Corporate Web Site |
Links to the solution provider's corporate Web site appear on both the Web site listing page and on the Web site profile page. This URL should link to the home page of the solution provider's corporate Web site. |
| Application Name |
Name of the application that will be used to identify it. For example, it will be shown to the user when they are authorizing the application for access to their HealthVault record. |
| Short Description |
Description of the application that is shown to the user when they authorizing the application. Suggested character limit is 200. |
| Web Site Name |
The name of the Web site appears on both the Web site listing page and on the Web site profile page. |
| Web Site Address |
A link to the Web site appears on the Web site profile page. This URL should link to your home page. |
| Web Site Description |
A short summary description of the Web site appears on both the Web site listing page and on the Web site profile page. This description should be no longer than 30 words. |
| Web Site Version Number |
The version number of the Web site appears on the Web site profile page. If available, a link to the Web site’s version history may be added next to the version number. This URL should link to the version history on the partner’s own corporate Web site. |
| Web Site Screen Shots |
Screen shots of the Web site appear on the Web site profile page, accompanied by captions. The captions under each screen shot should be short, descriptive, and no longer than 5 words. There is a strict limit of three screen shots per Web site profile page. Screen shots should be in full color and fit within a space of 150 pixels wide by 100 pixels high. For security reasons, the file format must be PNG. |
| License Agreement |
A link to the legal terms that appear on the Web site profile page. This URL should link to the terms on your site that apply to your application. |
| Privacy Statement |
A link to the Privacy Statement that appears on the Web site profile page. This URL should link to the privacy statement on your site that applies to your application. |
| Detailed Information |
More detailed information and links about the application can appear on the Web site profile page. The content of the information appearing on this page must be accurate and relevant to the benefits of how the Web site works with TELUS health space. The content in this section should be no longer than 300 words. |
| Contact Information |
Support contact information (phone/email/URL) that TELUS health space Customer Support can refer an end-user to, as appropriate. |
| Solution Provider Agreement |
You work with the TELUS health space Business Development team to complete a solution provider agreement. You can kick off this process by e-mailing thsbd@telus.com. |
Technical items
| Data access reason |
End-user-facing text that accurately describes the reasons for needing access to the data types that the application is requesting access to. This is shown to the user when they are authorizing the application. |
| Data access while the user is logged in |
For each data type, specify the type of access that the application requires (read, update, create, delete). You can find a list of types in the Learn section of the HealthVault Dev Center on MSDN. |
| Data access while the user is not logged in |
For each data type, specify the type of access that the application requires (read, update, create, delete). You can find a list of types in the Learn section of the HealthVault Dev Center on MSDN. |
| ApplicationID |
The ApplicationID that you are using and expect to go live with. |
| Public certificate |
A 2048-bit key that corresponds to the private key that the application will be using to identify itself to HealthVault. |
| Access to create an OpenQuery |
[yes/no] Do you require this? This may require an extra clause in your solution provider agreement. |
| Access to send email via TELUS health space |
[yes/no] Do you require this? This may require an extra clause in your solution provider agreement.
Provide the domain name from which e-mail will originate. |
| ActionURL |
The HealthServiceActionPage URL that will handle the following target values: Home, ServiceAgreement, Help, AppAuthReject, AppAuthSuccess, SelectedRecordChanged, ShareRecordSuccess, ShareRecordFailed, Privacy, and SignOut. |
| Automatic user sign in |
Specify whether or not your users should be able to elect to be signed in automatically the next time they return to your application, and if so, specify how many seconds the user should stay signed in for (unless they click 'sign out' or delete their cookies). |
| Add Shortcut to Connection Center |
A link to a signed MSI that the user can download and run that will install a shortcut for the partner Web site in their HealthVault Connection Center. This URL should link to the MSI hosted on the partner's own Web site. We will be providing you with a sample MSI that you can use as a template. |
|
|
About our partners
Canada’s leading health associations, organizations and technology providers are partnering with us to help you.
To find out who, click here 
|
|
|