We're delighted by the interest expressed in Google Health, especially
as we recognize that successful integrations are a key part of the
platform's value proposition to users.
Over the past few days, we have received a number of requests on next
steps to integrate. Here are the steps:
1) To gain access to the development sandbox (known as h9), please
write to h9access at google.com and indicate which e-mail addresses
from your organization should receive access. All e-mail addresses
should be from the same domain.
2) You will then receive a request to sign an NDA.
3) After you sign the NDA, all submitted e-mail addresses should
receive an e-mail that details how to access /h9. In the future, this
process will be more automated and will involve an online form that
can be signed. We thank you for your patience as that process is
being worked out.
4) Once you gain access to /h9, you can develop using localhost (which
is automatically registered).
5a) If your organization is an established medical institution that
holds primary health data, you can inform us of your interest to
integrate here: http://services.google.com/events/healthpartners
I got also the error "Invalid Request" , can you show me detail how to
write to h9access at google.com and indicate which e-mail addresses
Hope your help,
Thank Jerry
> from your organization should receive access
On May 23, 2:09 am, Jerry <jerryp...@gmail.com> wrote:
> We're delighted by the interest expressed in Google Health, especially
> as we recognize that successful integrations are a key part of the
> platform's value proposition to users.
> Over the past few days, we have received a number of requests on next
> steps to integrate. Here are the steps:
> 1) To gain access to the development sandbox (known as h9), please
> write to h9access at google.com and indicate which e-mail addresses
> from your organization should receive access. All e-mail addresses
> should be from the same domain.
> 2) You will then receive a request to sign an NDA.
> 3) After you sign the NDA, all submitted e-mail addresses should
> receive an e-mail that details how to access /h9. In the future, this
> process will be more automated and will involve an online form that
> can be signed. We thank you for your patience as that process is
> being worked out.
> 4) Once you gain access to /h9, you can develop using localhost (which
> is automatically registered).
> 5a) If your organization is an established medical institution that
> holds primary health data, you can inform us of your interest to
> integrate here:http://services.google.com/events/healthpartners
> We're delighted by the interest expressed in Google Health, especially
> as we recognize that successful integrations are a key part of the
> platform's value proposition to users.
> Over the past few days, we have received a number of requests on next
> steps to integrate. Here are the steps:
> 1) To gain access to the development sandbox (known as h9), please
> write to h9access at google.com and indicate which e-mail addresses
> from your organization should receive access. All e-mail addresses
> should be from the same domain.
> 2) You will then receive a request to sign an NDA.
> 3) After you sign the NDA, all submitted e-mail addresses should
> receive an e-mail that details how to access /h9. In the future, this
> process will be more automated and will involve an online form that
> can be signed. We thank you for your patience as that process is
> being worked out.
> 4) Once you gain access to /h9, you can develop using localhost (which
> is automatically registered).
> 5a) If your organization is an established medical institution that
> holds primary health data, you can inform us of your interest to
> integrate here:http://services.google.com/events/healthpartners
> Sorry for bothering you about the same topic " Invalid Request". I
> sent 2 e-mails with request to provide access to H9. But I did not get
> reply.
> May be I am doing something wrong?
> Can you explan how long it sould take? What needs to be done to
> register?
> So I need your help, basically.
> Thanks
> On May 22, 3:09 pm, Jerry <jerryp...@gmail.com> wrote:
> > Hello everyone,
> > We're delighted by the interest expressed in Google Health, especially
> > as we recognize that successful integrations are a key part of the
> > platform's value proposition to users.
> > Over the past few days, we have received a number of requests on next
> > steps to integrate. Here are the steps:
> > 1) To gain access to the development sandbox (known as h9), please
> > write to h9access at google.com and indicate which e-mail addresses
> > from your organization should receive access. All e-mail addresses
> > should be from the same domain.
> > 2) You will then receive a request to sign an NDA.
> > 3) After you sign the NDA, all submitted e-mail addresses should
> > receive an e-mail that details how to access /h9. In the future, this
> > process will be more automated and will involve an online form that
> > can be signed. We thank you for your patience as that process is
> > being worked out.
> > 4) Once you gain access to /h9, you can develop using localhost (which
> > is automatically registered).
> > 5a) If your organization is an established medical institution that
> > holds primary health data, you can inform us of your interest to
> > integrate here:http://services.google.com/events/healthpartners
I'm currently trying to use OAuth authentication with Google
Health. I've done steps one through three that Jerry posted but step
four has stumped me. All of the documentation I can find on how to use
h9 seems to only directly apply to the SubAuth authentication with
little notes about OAuth intermixed (notes like: "you can also use
OAuth," which aren't incredibly helpful.) Is there some documentation
that gives step-by-step instructions on how to use h9 in conjunction
with OAuth? If not, perhaps my question(s) can be answered here. As of
right now I have two domains registered on the "regular" Google site.
The domains are registered, verified and my certificates have been
uploaded. I have a Java app running in Tomcat that is making a
successful request to
https://www.google.com/accounts/OAuthGetRequestToken?...scope=http%3A...
This request is returning successfully and eventually I'm redirected
to the weaver login page. When I login (with the account that has been
approved for testing) the browser displays an error page that says:
I'm assuming the problem is that my domain isn't registered on weaver,
only on the real site. So two questions. 1) When testing on h9 should
I be using this URL: https://www.google.com/accounts/OAuthGetRequestToken or should I be using something more like
https://www.google.com/h9/accounts/OAuthGetRequestToken and 2) where do I register my domains so that they work on weaver or
do I have to use http://localhost? If I have to use localhost then I
have a bunch of other questions but I'll wait for an initial answer
before delving too deep in that direction.
> > On May 22, 3:09 pm, Jerry <jerryp...@gmail.com> wrote:
> > > Hello everyone,
> > > We're delighted by the interest expressed in Google Health, especially
> > > as we recognize that successful integrations are a key part of the
> > > platform's value proposition to users.
> > > Over the past few days, we have received a number of requests on next
> > > steps to integrate. Here are the steps:
> > > 1) To gain access to the development sandbox (known as h9), please
> > > write to h9access at google.com and indicate which e-mail addresses
> > > from your organization should receive access. All e-mail addresses
> > > should be from the same domain.
> > > 2) You will then receive a request to sign an NDA.
> > > 3) After you sign the NDA, all submitted e-mail addresses should
> > > receive an e-mail that details how to access /h9. In the future, this
> > > process will be more automated and will involve an online form that
> > > can be signed. We thank you for your patience as that process is
> > > being worked out.
> > > 4) Once you gain access to /h9, you can develop using localhost (which
> > > is automatically registered).
> > > 5a) If your organization is an established medical institution that
> > > holds primary health data, you can inform us of your interest to
> > > integrate here:http://services.google.com/events/healthpartners
If I change my oauth_consumer_key value from www.mydomain.com to a bad
domain name www.baddomain.com then I never reach the login page (I get
a bad oauth_consumer_key error before even getting the chance to
login). So I feel confident that the authentication process is
recognizing my domain but for some reason the domain isn't fully
registered to be used with Google Health. I'm not sure what to do to
fix this.
Shawn
On Aug 22, 9:39 am, Shawn Kessler <skess...@gmail.com> wrote:
> I'm currently trying to use OAuth authentication with Google
> Health. I've done steps one through three that Jerry posted but step
> four has stumped me. All of the documentation I can find on how to use
> h9 seems to only directly apply to the SubAuth authentication with
> little notes about OAuth intermixed (notes like: "you can also use
> OAuth," which aren't incredibly helpful.) Is there some documentation
> that gives step-by-step instructions on how to use h9 in conjunction
> with OAuth? If not, perhaps my question(s) can be answered here. As of
> right now I have two domains registered on the "regular" Google site.
> The domains are registered, verified and my certificates have been
> uploaded. I have a Java app running in Tomcat that is making a
> successful request tohttps://www.google.com/accounts/OAuthGetRequestToken?...scope=http%3A...
> This request is returning successfully and eventually I'm redirected
> to the weaver login page. When I login (with the account that has been
> approved for testing) the browser displays an error page that says:
> I'm assuming the problem is that my domain isn't registered on weaver,
> only on the real site. So two questions. 1) When testing on h9 should
> I be using this URL: https://www.google.com/accounts/OAuthGetRequestToken > or should I be using something more likehttps://www.google.com/h9/accounts/OAuthGetRequestToken > and 2) where do I register my domains so that they work on weaver or
> do I have to usehttp://localhost?If I have to use localhost then I
> have a bunch of other questions but I'll wait for an initial answer
> before delving too deep in that direction.
> Thanks for you help,
> Shawn
> > > On May 22, 3:09 pm, Jerry <jerryp...@gmail.com> wrote:
> > > > Hello everyone,
> > > > We're delighted by the interest expressed in Google Health, especially
> > > > as we recognize that successful integrations are a key part of the
> > > > platform's value proposition to users.
> > > > Over the past few days, we have received a number of requests on next
> > > > steps to integrate. Here are the steps:
> > > > 1) To gain access to the development sandbox (known as h9), please
> > > > write to h9access at google.com and indicate which e-mail addresses
> > > > from your organization should receive access. All e-mail addresses
> > > > should be from the same domain.
> > > > 2) You will then receive a request to sign an NDA.
> > > > 3) After you sign the NDA, all submitted e-mail addresses should
> > > > receive an e-mail that details how to access /h9. In the future, this
> > > > process will be more automated and will involve an online form that
> > > > can be signed. We thank you for your patience as that process is
> > > > being worked out.
> > > > 4) Once you gain access to /h9, you can develop using localhost (which
> > > > is automatically registered).
> > > > 5a) If your organization is an established medical institution that
> > > > holds primary health data, you can inform us of your interest to
> > > > integrate here:http://services.google.com/events/healthpartners
Our Google Health app was looking good earlier, but upon running my revoke function, I now receive a 401 error and cannot proceed more, as if the sessionToken don't authenticate as earlier expected. Here's my revoke function:
|
