Hi Michael, Nop, maxdrive is just my handle, my name is Emmanuel Caulin and i'm working in a Medical Software company. I'm tasked to have a look at Google Health and what we can develop for our customers in the future.
Thanks for your reply and hopefully Google guys can help me out on some of my questions. Regards, On Nov 16, 9:08 am, Michael Jahn <[email protected]> wrote: > Hi MaxDrive (is that your given name? > > (wink) > > okay - i have BCCed someone at Google who I think really cares about this, > and perhaps he (or someone from his team) might reply... > > in the real world, when I get a prescription - well, and edits should happen > before it is 'filled' - but lets face it, the fact is, someone might get a > persciption that is 'miss-filled' - that is "oops, we spelled things > incorrectly, they could not read our writing - or - sheesh - you didn't tell > me you were on XYZ ! > > Now, the fact is, there are instances where, after a fact - someone should > be able to delete / correct that, but - humm - well maybe that might not be > the Physician, and perhaps once thing are right, that should be fixed by the > pharmacist. > > I am not here to debate that... > > but CLEARLY this points to a permissions issue - who is 'vetted' who is > 'authorized' and all that. > > Not sure if Google Heath offers much more than "username password" - for the > PHR owner - and "something else" for others... > > And frankly, I am not sure I know how to advise them - perhaps Dr. Kibbe > might have a thought or to on the logistics of who should be able to do > what... > > Michael Jahn > Jahn & Associates > PDF Conversion Specialist > 1824 North Garvin Avenue > Simi Valley > California 93065 > Office: (805) 527 8130 > Cell: (805) 217 6741 > Email: [email protected] > Skype: michaelejahn > Twitter:http://twitter.com/michaelejahn > Blog:http://michaelejahn.blogspot.com/ > > > > On Sun, Nov 15, 2009 at 2:11 PM, maxdrive <[email protected]> wrote: > > Hi Michael, > > > Actually you can't delete/update someone's profile if you're just > > invited or the patient just shared his profile to you, this is view > > only. > > > Google Health doesn't recommend ClientLogin API simply because of this > > strategy, you need the patients google account (username, password, > > and profileid) all the time to do all the processes (insert, update, > > delete operations) whereas the AuthSub / OAuth strategy, the patient/ > > user must login to Google Health site first (so this means that the > > patient/user doesn't have to give his/her account to Data Provider) > > and if he/she wish to import his/her data from a certain Data Provider > > he/she has to link the Data Provider first to Google Health and by > > doing so the patient / user is redirected to Data Provider site (this > > of course if his/her Data Provider already registered by Google > > Health), the patient needs to login using his/her account on his/her > > Data Provider and if successfully authenticated then Google Health > > will give a token that the Data Provider and Google Health will use to > > do the processes. > > > But as a developer, i would like to ask Google Health technical guys, > > if possible, to give me some clarification on the process, who > > triggers who, etc. > > > I hope the Google guys would shed light on my questions. :) > > > I have more questions though... > > > On Nov 15, 10:15 pm, Michael Jahn <[email protected]> wrote: > > > @ MaxDrive > > > > your wrote; > > > > "... unfortunately when > > > using ClientLogin API (I'm talking about the desktop application > > > deployment) you really need the patient's google account and profileid > > > to successfully do the processes." > > > > Well, gee wiz wally - i would hope so ! > > > > (smile) > > > > I assume that; > > > > 1. My Google Health profile is private and unaccessable UNLESS I provide > > an > > > invitation > > > > 2. That you can only ADD to my profile (you can't go in a delete anything > > > thing I put or others added > > > > 3. That when I invite you, you can SEE my profile, but you can't really > > edit > > > it... > > > > and perhaps this means... > > > > 4. You better send the data correctly, as I have no idea if what you > > > "appeand' can then be recalled or fixed ! > > > > Does that make sense ? > > > > Remember, I am a marketing guy, not a coder - this is what I would EXPECT > > > the the behavior to be, but that may not be the case ! > > > > Michael Jahn > > > Jahn & Associates > > > PDF Conversion Specialist > > > 1824 North Garvin Avenue > > > Simi Valley > > > California 93065 > > > Office: (805) 527 8130 > > > Cell: (805) 217 6741 > > > Email: [email protected] > > > Skype: michaelejahn > > > Twitter:http://twitter.com/michaelejahn > > > Blog:http://michaelejahn.blogspot.com/ > > > > On Sun, Nov 15, 2009 at 12:58 PM, maxdrive <[email protected]> wrote: > > > > Hi Michael, > > > > > Thanks for the reply. I actually managed to query my test profile in > > > > Google Health using ClientLogin API but my little disappointment > > > > though is that the API is not very well documented which lead me to > > > > really dig in on the code and made some trial and error tests. The > > > > advantage though is it made me more aware of how the API worked. Right > > > > now i'm trying to insert, update and delete entries. > > > > > Going back to my previous questions, How is patient data from Data > > > > Provider sent to Google Health when patient / user links it > > > > successfully in the Google Health panel? Maybe i missed something on > > > > the documentation or is not very clear to me. > > > > > Concerning the Google Account of patient, yes, unfortunately when > > > > using ClientLogin API (I'm talking about the desktop application > > > > deployment) you really need the patient's google account and profileid > > > > to successfully do the processes. > > > > > Let me know your thoughts. > > > > > Regards, > > > > > On Nov 13, 10:36 pm, Michael Jahn <[email protected]> wrote: > > > > > Hi, > > > > > > This is my 'guess' - i believe that a notice is sent to the Google > > > > Account. > > > > > > To test - I would be happy to use my "fictitious patient" account to > > > > link > > > > > to you, then you can see what happens. > > > > > > Or - if you do not want to (or can't) share your details for some > > reason > > > > ( > > > > > that's okay !) > > > > > > use the one Google permitted me to set up for testing... > > > > > > ================================================= > > > > > the "patient" account > > > > > > Google Health account information for Pebbles Flintstone > > > > > >http://www.google.com/profiles/pebbles.flintstone.test > > > > > > Go to --> https://www.*google*.com/*health*< > > > >https://www.google.com/health> > > > > > > user name --> pebbles.flintstone.test > > > > > > password --> pdfhealthcare > > > > > > email address --> [email protected] > > > > > > ============================================== > > > > > > hope this helps ! > > > > > > Michael Jahn > > > > > Jahn & Associates > > > > > PDF Conversion Specialist > > > > > 1824 North Garvin Avenue > > > > > Simi Valley > > > > > California 93065 > > > > > Office: (805) 527 8130 > > > > > Cell: (805) 217 6741 > > > > > Email: [email protected] > > > > > Skype: michaelejahn > > > > > Twitter:http://twitter.com/michaelejahn > > > > > Blog:http://michaelejahn.blogspot.com/ > > > > > > On Fri, Nov 13, 2009 at 8:06 AM, maxdrive <[email protected]> > > wrote: > > > > > > Hi, > > > > > > > I just want to have some clarification during the process when > > patient > > > > > > successfully links a data provider to google health, is patient > > data > > > > > > sent automatically to google health from data provider? Also about > > > > > > sending notices, how is the data provider send data to google > > health? > > > > > > is he going to store the username and password of the patient > > (google > > > > > > account) to successfully send the data to google health? > > > > > > > Thanks. > > > > > > > -- > > > > > > > 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]. > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/googlehealthdevelopers?hl=.-Hidequoted > > > > text - > > > > > > - Show quoted text - > > > > > -- > > > > > 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]. > > > > For more options, visit this group at > > > >http://groups.google.com/group/googlehealthdevelopers?hl=.-Hide quoted > > text - > > > > - Show quoted text - > > > -- > > > 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]. > > For more options, visit this group at > >http://groups.google.com/group/googlehealthdevelopers?hl=.- Hide quoted text > >- > > - Show quoted text - -- 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]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=.
