Message from discussion
Please consider opening Google Health instead of killing it
Received: by 10.101.197.29 with SMTP id z29mr569562anp.12.1309387373135;
Wed, 29 Jun 2011 15:42:53 -0700 (PDT)
X-BeenThere: googlehealthdevelopers@googlegroups.com
Received: by 10.101.179.39 with SMTP id g39ls329330anp.4.gmail; Wed, 29 Jun
2011 15:42:49 -0700 (PDT)
Received: by 10.101.118.1 with SMTP id v1mr563954anm.14.1309387369231;
Wed, 29 Jun 2011 15:42:49 -0700 (PDT)
Received: by 10.150.33.26 with SMTP id g26msybg;
Wed, 29 Jun 2011 11:01:32 -0700 (PDT)
Received: by 10.236.135.20 with SMTP id t20mr604651yhi.8.1309370490118;
Wed, 29 Jun 2011 11:01:30 -0700 (PDT)
Received: by 10.236.135.20 with SMTP id t20mr604650yhi.8.1309370490090;
Wed, 29 Jun 2011 11:01:30 -0700 (PDT)
Return-Path: <brettptho...@gmail.com>
Received: from mail-gx0-f176.google.com (mail-gx0-f176.google.com [209.85.161.176])
by gmr-mx.google.com with ESMTPS id l51si739168yhe.1.2011.06.29.11.01.30
(version=TLSv1/SSLv3 cipher=OTHER);
Wed, 29 Jun 2011 11:01:30 -0700 (PDT)
Received-SPF: pass (google.com: domain of brettptho...@gmail.com designates 209.85.161.176 as permitted sender) client-ip=209.85.161.176;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of brettptho...@gmail.com designates 209.85.161.176 as permitted sender) smtp.mail=brettptho...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by mail-gx0-f176.google.com with SMTP id 7so823530gxk.35
for <googlehealthdevelopers@googlegroups.com>; Wed, 29 Jun 2011 11:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type;
bh=9yDBZYWigig9RRNBVEvML6vMKCRgJDsTuk5A5dvw1NU=;
b=KqECm5lNa/HkQ2KAwYHG9U4mTQWcV+YnDFyqmkiyQGsjLR8XfvS0Lh0bB8SIqP1FGz
gINinSliF843ufbKjYHenw33GxP6hYYFdpsPopKW6g/RHDT4y6rQo4l9UVOsPIu8bt3Y
xLzu2EwR9Z346SW25zi12UDY6z6v766szn+YY=
Received: by 10.236.191.73 with SMTP id f49mr1349301yhn.154.1309370488146;
Wed, 29 Jun 2011 11:01:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.61.72 with HTTP; Wed, 29 Jun 2011 11:01:07 -0700 (PDT)
In-Reply-To: <0e46f1da-832a-4f75-a59a-74af88c75...@28g2000yqu.googlegroups.com>
References: <c096d1a1-56a5-4bc9-9cf7-85e42904f...@y30g2000yqb.googlegroups.com>
<a86eec6a-ad8b-4610-a9fc-c3e016a7e...@f39g2000prb.googlegroups.com> <0e46f1da-832a-4f75-a59a-74af88c75...@28g2000yqu.googlegroups.com>
From: Brett Thomas <brettptho...@gmail.com>
Date: Wed, 29 Jun 2011 14:01:07 -0400
Message-ID: <BANLkTimfymdQpJctOgNcNASzST7wG0G...@mail.gmail.com>
Subject: Re: [Google-Health-API] Re: Please consider opening Google Health
instead of killing it
To: googlehealthdevelopers@googlegroups.com
Content-Type: multipart/alternative; boundary=20cf303f6a42d349cf04a6dd927d
--20cf303f6a42d349cf04a6dd927d
Content-Type: text/plain; charset=ISO-8859-1
I agreed with this blog post, which suggests that a nonprofit should support
google health services as a public service:
http://thehealthcareblog.com/blog/2011/06/27/why-we-need-an-independent-health-data-utility/
If anybody knows of any movement there, please reply to this list so we know
how to get involved
On Wed, Jun 29, 2011 at 11:45 AM, pablopazos <pablo....@gmail.com> wrote:
> It would be nice if Google can open source the core and the apis of
> Google Health, I think the community can continue the project and
> improve it.
>
> Cheers,
> Pablo Pazos
> http://informatica-medica.blogspot.com/
>
> On 28 jun, 00:40, Sarkis Dallakian <dallaky...@gmail.com> wrote:
> > Greetings everyone,
> >
> > I agree with Fred and Harsh in that Open Sourcing portions of Google
> > Health would be beneficial, to say the least. I starred this topic not
> > only to follow this, but also since I'm interested in both online and
> > offline health.
> >
> > Best Wishes,
> > Sarkis
> >
> > https://profiles.google.com/dallakyans
> >
> > On Jun 27, 11:37 am, Fred Trotter <fred.trot...@gmail.com> wrote:
> >
> > > Hi,
> > > First, let me say that I am sorry to see Google Health go. I
> > > think it was a worthy project, and despite my criticism over the years
> > > I have always admired your smooth delivery and classic design.
> >
> > > I would ask that you consider Open Sourcing portions of Google Health.
> > > For me, the order of priority is the following:
> >
> > > 1. please Open Source your API. This way, the Open Source community
> > > can work on cloning your offerings using existing PHR projects like
> > > Indivo X.
> > > 2. If you can release reference implementations of you API related
> > > code (i.e. your feed/CCR mix) that would be especially helpful.
> > > 3. Please consider Open Sourcing other important components, I know
> > > you have a blue button parser, for instance, that could exist as a
> > > separate Open Source project.
> > > 4. Please consider Open Sourcing your whole codebase.
> >
> > > I know #4 is a long shot. Unlike Google Wave, Google Health was never
> > > intended (as far as I know) to exist outside the confines of Googles
> > > considerable hosting infrastructure. Even if you released the code, it
> > > might not be possible for any of us to make it work. If that is the
> > > case than a full Open Source release would be still-born and mostly
> > > useless to the community.
> >
> > > Still I want to point out that Open Sourcing Google Health is not an
> > > all-or-nothing issue and that many of use have invested deeply in your
> > > technology. Open Sourcing what you can is a good way for us to recover
> > > some of our investment.
> >
> > > Thank You,
> > > Fred Trotterhttp://www.fredtrotter.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Health Developers" group.
> To post to this group, send email to
> googlehealthdevelopers@googlegroups.com.
> To unsubscribe from this group, send email to
> googlehealthdevelopers+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/googlehealthdevelopers?hl=en.
>
>
--20cf303f6a42d349cf04a6dd927d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I agreed with this blog post, which suggests that a nonprofit should suppor=
t google health services as a public service:=A0<a href=3D"http://thehealth=
careblog.com/blog/2011/06/27/why-we-need-an-independent-health-data-utility=
/">http://thehealthcareblog.com/blog/2011/06/27/why-we-need-an-independent-=
health-data-utility/</a><div>
<br></div><div>If anybody knows of any movement there, please reply to this=
list so we know how to get involved<br><br><div class=3D"gmail_quote">On W=
ed, Jun 29, 2011 at 11:45 AM, pablopazos <span dir=3D"ltr"><<a href=3D"m=
ailto:pablo....@gmail.com">pablo....@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">It would be nice if Google can open source =
the core and the apis of<br>
Google Health, I think the community can continue the project and<br>
improve it.<br>
<br>
Cheers,<br>
Pablo Pazos<br>
<a href=3D"http://informatica-medica.blogspot.com/" target=3D"_blank">http:=
//informatica-medica.blogspot.com/</a><br>
<div><div></div><div class=3D"h5"><br>
On 28 jun, 00:40, Sarkis Dallakian <<a href=3D"mailto:dallaky...@gmail.c=
om">dallaky...@gmail.com</a>> wrote:<br>
> Greetings everyone,<br>
><br>
> I agree with Fred and Harsh in that Open Sourcing portions of Google<b=
r>
> Health would be beneficial, to say the least. I starred this topic not=
<br>
> only to follow this, but also since I'm interested in both online =
and<br>
> offline health.<br>
><br>
> Best Wishes,<br>
> Sarkis<br>
><br>
> <a href=3D"https://profiles.google.com/dallakyans" target=3D"_blank">h=
ttps://profiles.google.com/dallakyans</a><br>
><br>
> On Jun 27, 11:37=A0am, Fred Trotter <<a href=3D"mailto:fred.trot...=
@gmail.com">fred.trot...@gmail.com</a>> wrote:<br>
><br>
> > Hi,<br>
> > =A0 =A0 =A0First, let me say that I am sorry to see Google Health=
go. I<br>
> > think it was a worthy project, and despite my criticism over the =
years<br>
> > I have always admired your smooth delivery and classic design.<br=
>
><br>
> > I would ask that you consider Open Sourcing portions of Google He=
alth.<br>
> > For me, the order of priority is the following:<br>
><br>
> > 1. please Open Source your API. This way, the Open Source communi=
ty<br>
> > can work on cloning your offerings using existing PHR projects li=
ke<br>
> > Indivo X.<br>
> > 2. If you can release reference implementations of you API relate=
d<br>
> > code (i.e. your feed/CCR mix) that would be especially helpful.<b=
r>
> > 3. Please consider Open Sourcing other important components, I kn=
ow<br>
> > you have a blue button parser, for instance, that could exist as =
a<br>
> > separate Open Source project.<br>
> > 4. Please consider Open Sourcing your whole codebase.<br>
><br>
> > I know #4 is a long shot. Unlike Google Wave, Google Health was n=
ever<br>
> > intended (as far as I know) to exist outside the confines of Goog=
les<br>
> > considerable hosting infrastructure. Even if you released the cod=
e, it<br>
> > might not be possible for any of us to make it work. If that is t=
he<br>
> > case than a full Open Source release would be still-born and most=
ly<br>
> > useless to the community.<br>
><br>
> > Still I want to point out that Open Sourcing Google Health is not=
an<br>
> > all-or-nothing issue and that many of use have invested deeply in=
your<br>
> > technology. Open Sourcing what you can is a good way for us to re=
cover<br>
> > some of our investment.<br>
><br>
> > Thank You,<br>
> > Fred Trotterhttp://<a href=3D"http://www.fredtrotter.com" target=
=3D"_blank">www.fredtrotter.com</a><br>
<br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;Google Health Developers" group.<br>
To post to this group, send email to <a href=3D"mailto:googlehealthdevelope=
rs@googlegroups.com">googlehealthdevelopers@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:googlehealt=
hdevelopers%2Bunsubscribe@googlegroups.com">googlehealthdevelopers+unsubscr=
ibe@googlegroups.com</a>.<br>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/googlehealthdevelopers?hl=3Den" target=3D"_blank">http://groups.google=
.com/group/googlehealthdevelopers?hl=3Den</a>.<br>
<br>
</div></div></blockquote></div><br></div>
--20cf303f6a42d349cf04a6dd927d--