There is no way to be compliant with HIPAA using appengine at this time. So your statement is not true: http://groups.google.com/group/google-appengine/browse_thread/thread/aef13f580f46bd13
moreover, it has nothing to do with Google Health, which is a consumer focused PHR. Given that, I am not sure how your comment here is relevant to the topic. -FT On Jun 28, 1:30 am, Peter Retief <[email protected]> wrote: > Google does offer a variety of API's and its distributed database via > appengine, nothing is stopping a developer from creating a Hospital > Information System > > Peter > > On 27 June 2011 20:54, Harsh Kumar <[email protected]> wrote: > > > > > > > > > Hi, > > I would second Fred here. I seriously feel that Google Health has potential. > > Though i would as well agree that it may not be viable for Google from a > > business point of view. Hence i would request you guys at Google to open > > source it. Let the community take the work which you people have done. > > Googlers who have worked on Google Health can help the community to ramp up > > and take the project forward. > > I agree that without the Google infrastructure to be able to continue would > > be difficult, but its not impossible provided the community comes forward to > > support it financially as well. > > I am not a big fan of Google Health and i seriously think that the design > > needs to be tweaked a bit to make it better. But again having said that it > > is best of lot that we have today. > > Thanks, > > Harsh Kumar > > > On Tue, Jun 28, 2011 at 00:07, Fred Trotter <[email protected]> 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 Trotter > >>http://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 > >> [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. > > > -- > > 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. -- 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.
