Hi Dave, Comments are inline.
On Dec 11, 1:34 pm, Dave <[email protected]> wrote: > I'm investigating this service for the company I am working for. > I've been reading through some forum posts and general documentation > but have gotten confused. > > Q) What is the difference between H9 and Production? I saw the page > on certificates, permissions, etc. but, if it only holds MY Personal > Data then who cares? I am importing/exporting information from/to > doctors, pharmacies, etc. I'm obviously missing something here. The idea behind H9 is that it should be used solely for development purposes. It is meant to be an API playground/sandbox for 3rd-party application to experiment with the API using test data. We don't want prematurely expose applications to the production /health (and a user's real health data) until their integration is fully tested. > > Q) Can I create new profiles? It looks like NO. There can only be > one profile >> me <<. So, as a data provider, if I want to publish > patient information, that patient would have to create a profile > first? Yes, you can create multiple profiles in the Google Health UI ('Create a new profile' link, bottom of the left navbar). That is, a single Google Account can have multiple Google Health profiles attached to it. You _cannot_ create new profiles programmatically using the API. If the patient has a Google Account but has never used Google Health, a default profile will be created for them during the AuthSub linking process. > > Q) If the patient is responsible for the information they pull the > data from my server? How does that happen. The examples I have found > have all been about accessing >> my << data. Data providers typically will only push data to a user's Health profile. This is done by sending a notice to a user's profile: http://code.google.com/apis/health/docs/2.0/reference.html#AuthSubRegisterFeed The permission parameter in AuthSub/OAuth mitigates the push/pull limitations: http://code.google.com/apis/health/docs/2.0/developers_guide_protocol.html#Authenticating 3rd party services will use permission=1 to both pull and potentially push data to a user's Health profile. However, they typically only pull data, and use it to do something interesting. > > Q) Is there a model for data through push, pull, or both? The model can be both push and/or pull depending on what the permission parameter is set to. > > Q) Is it possible to store documents (.pdf) as opposed to discrete > data? Not currently. But we're aware this is a feature users want to see. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en -~----------~----~----~----~------~----~------~--~---
