Well, from my understanding, difference between an update and an edit is: I would be "editing" a medication record on my end (via Java Web application) and then pass the info via VO and then convert it into XML using a library, which then would be passed to google health using Google Health (I am not using H9) to "update" that particular medication record.
The converting to XML bit would give me my CCR. All of the steps that I mentioned above, work for me... except the last one, which is to send the edited medication back, so that it updates it, in the Google Health's database. (I started a thread here, if you are interested, to ask few questions in order to help solve the last step: http://groups.google.com/group/googlehealthdevelopers/browse_thread/thread/edd11649763ee9b5) What did you end up using for EntryId? and Where did you get this from? >From my debugs, I found that EntryId was: "profileId"_digest I will keep at it, let's see what happens! On Jul 25, 1:05 am, petem <[email protected]> wrote: > Well, yes and no. I found that I could achieve a result by POSTing a > notice on the register feed using ../register/ui/profileID. Not the > same thing I know but it's not really clear to me what the difference > between editing and updating is. As well it seemed to make a > difference when I stopped using Python/PyCurl and started using a > combination of Python and Curl. It was only a test bench facility so > the detail didn't matter. > > As for the rest of my query about what else besides the CCR needs to > accompany it, I never got a response to that either. I included most > of the atom stuff and minimal CCR - worked for me. As to what was > minimal or not lead to other questions about how to use a "notice" but > once again there's no one to talk to. > > I guess no one knows these things, and we're all awaiting the > Light :-) Is a "notice" any good to you? > > On Jul 25, 12:08 pm, GHUser <[email protected]> wrote: > > > Hi petem, > > > have you made any progress on your original query? > > > I am trying to update my medication record as well... however, I > > cannot even send it! > > > What are you using for your "entryID"? > > > Any help, appreciated! > > > Thanks > > > On Jun 15, 2:39 am, petem <[email protected]> wrote: > > > > I'm using the profile feed with ClientLogin. Should I be using the > > > register feed instead? > > > > On Jun 15, 12:01 pm, petem <[email protected]> wrote: > > > > > I've moved a little ahead in this. I'm now getting a return code of > > > > 200 instead of 411. Successful perhaps but the new data is not showing > > > > up when I redo the category query GET. I've tried the full header, > > > > body, CRR, footer with new nodes; and I've also tried a cut down CCR > > > > PUTing merely medication, productname and fulfillment history, all > > > > without being able to verify the addition. Is there perhaps a time > > > > lag? > > > > > On Jun 13, 5:13 pm, petem <[email protected]> wrote: > > > > > > I need to append a fulfilment record to specific medication data, but > > > > > am confused about how to do this. Is it a case of following > > > > > thishttp://code.google.com/apis/health/docs/2.0/developers_guide_protocol... > > > > > , so that a fulfllment gets injected into the tree before PUTing it > > > > > back? How much of the CCR needs to go with it to give it context, ie > > > > > profileID, medication product name, all the CCR? > > > > > > I haven't seen theEntryIDreferenced before. If I've previously > > > > > programmed a category query (for Medications), is there anentryIDin > > > > > there somewhere?- Hide quoted text - > > > > > - Show quoted text -- 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] 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 -~----------~----~----~----~------~----~------~--~---
