Lost on application id's RRS feed

  • Question

  • Hi,

    We are a little lost on application id's and what we need to do.

    We are adding functionality to our application (windows forms) that will upload a CCR file to HealthVault.  Our application is sold to individual doctors offices.  We plan to use the Drop-Off-Pick-Up method.

    Do we need to generate a master id and child id's or just a single application id?  Is the application id and master id the same thing?  If we need to generate both, then that means we have to get with each office and do something special as part of our upgrade to our next release?

    We are trying to make this as simple as we can.  Any advice will be appreciated.


    Monday, May 2, 2011 6:42 PM


All replies

  • Hello,

    If you are planning to ship the same software instances into different practices which you need to uniquely identify, then please refer to have HealthVault Master Child Application architecture. This allows you to create child app ids for each of the practices.

    You can find our MSDN documentation on when to use HeathVault Master Child Application IDs from here, http://msdn.microsoft.com/en-us/healthvault/cc451928

    HealthVault Master Child Application scenario is also explained in our wiki page, http://partners.mshealthcommunity.com/hv_eco/w/wiki/master-child-applications.aspx

    Hope this helps,

    Thank you

    Anish Ravindran
    • Proposed as answer by Anish Ravindran Monday, May 2, 2011 8:08 PM
    • Marked as answer by Roger99 Wednesday, May 4, 2011 8:31 PM
    Monday, May 2, 2011 8:07 PM
  • Thank you Anish.

    Is there any reason we would need to "uniquely identify" any practice.  If we are doing drop off, does this require master/child id's?  We are trying to understand what extra work will be required when we distribute our application to new and existing clients.


    Monday, May 2, 2011 9:47 PM
  • If the practices have their own branding elements (logo, success message), privacy and terms of use for a customer to uniquely identify which practice they are going authorize their record, then this is indeed.

    Thank you,

    Anish Ravindran
    Monday, May 2, 2011 10:43 PM
  • Thanks again.

    In the drop-off/pick-up model, I do not believe there is any authorization going on, or am I incorrect?  We are starting to look at this model of master/child.  Our hope was to not get involved at each doctor site but get them connected easily without us.


    Tuesday, May 3, 2011 9:40 PM
  • Yes. You are correct there is no authorization required in the Drop-Off/Pick-Up.

    Since you want each doctor site to get them connect to HealthVault without through you, Master Child architecture looks good. But in this case, each doctor site needs to configure the certificate settings so that the child can communicate to HealthVault.

    On the other side, if you go with a normal Application ID and want doctor sites to connects with HealthVault, without through you, then you need to distribute the single certificate to all doctor sites which a violation to HealthVault policies.

    You can also have a normal Application ID and have a server component which can avoid distribution of certificates. Each Doctor sites can communicate to server component which you are hosing and this server can communicate to HealthVault.

    Thank you,


    Anish Ravindran
    Wednesday, May 4, 2011 6:35 PM
  • Thank you Anish.

    I'm sure there will be other questions in the near future.


    Wednesday, May 4, 2011 8:31 PM