We have a webapp that pushes data up to Google into the Procedures section. There can be multiple data items, and the data items within our app can increase over time. We let the user push the data items to their Google Health Procedures manually, one at a time. We track which items were pushed to Google, and display the shared items differently than the unshared items. We are using the AuthSub authentication mechanism.
Because the user is allowed to remove data items from the Google side, we need to be able to check the Google profile to determine whether any of the data items perviously pushed from our application were subsequently removed from the Google side. I have tried using the CCRDataObjectID returned from the GoogleService insert() method, hoping that was persistent and that it matched the profiles Procedures listing. But when I would pull the Procedures listing using the GoogleService query() method, I found that the CCRDataObjectIDs in the list did not match the CCRDataObjectID returned from the insert(). So, I ended up querying Google before I pushed a data item, and then re-querying Google after the data item push is complete. I expect to find 1 additional item in the Procedures listing, and I save off the CCRDataObjectID from this Procedure for subsequent tracking. At first this seemed to work, but I have occasionally noticed situations where the 2nd query returns the exact same set of data as the first -- there is no additional Procedures item. This has occurred even in situations where I can see the new data item in the Google Health record itself. It happens intermittently and so far I have not been able to reliably reproduce it. - Is my approach for data synchronization the proper way to do this? - Is there something else I should be doing instead? - If this is the only way to synchronize, am I seeing a timing problem? Should I sleep <X> ms before I try the 2nd profile query? Thanks for any help with this, Laurie Tynor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
