make sense... On Sat, Dec 12, 2009 at 10:40 AM, Jim Pharis <[email protected]> wrote:
> I'm curious what the logic behind why Google Health only allows ClientLogin > to update/delete records and not AuthSub. I can think of several important > use cases of why an app that integrates with Health would need to, at the > minimum, update a record. > > Lets take an example. A Dr is using an app that integrates with Google > Health. The Dr decides that a medication that has been prescribed needs to > change because there could be a harmful interaction with a new medication > that the Dr wants to prescribe. The only thing the Dr could do would be to > add the new medication. The Dr would have to ask the patient to go into > Google Health and delete the old medication. That doesn't make any sense to > me. It seems like the Dr should at least be able to add a note to the > existing medication that invalidates it. > > TIA > - Jim > > -- > 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]<googlehealthdevelopers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/googlehealthdevelopers?hl=en. > -- Bess Ho UI Architect / Developer / Designer iPhone Developer Silicon Valley Web Builder (SVWB) Founder The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- 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.
