|See screenshots...issue is resolved thanks to Google's quick work and support from the Twittersphere, which enabled me to track the issue all the way back to installation last night of an iPhone app that has a linking function to my Google Health profile. |
First and foremost, I was wrong...This is NOT a Google Health issue (per se) - it's a permissions/linked profile issue with an app (this one happens to be iPhone app). The issue is related to that app's 'opt out' process rather than 'opt in.'
The app DOES have a linked profile text page as part of the signup process, and linking commences even if you haven't entered any data in your journal via mobile interface.
Another important note, even if your profile (or profiles, since you can now create multiple profiles as a Google Health user) is linked in Google Health to any internal or external app, engine, or build (and you can have more than one) then you can delink by going to the "Settings" (top nav) "Profile" page (sub nav).
Another important note...Linked accounts, including app engine builds, will NOT appear in your "See Who Has Access" tab on the right nav. Again, this info is stored in the Settings tab on the top nav.
Google's timely and personal response on this issue today was absolutely phenomenal, and on a Sunday afternoon, in the middle of the GTUG Campout.
Thank you to Google, the GTUG Campout organizers, Google Health staff for your quick work here. I will be happy to continue to provide access and feedback on how to improve the Google Health user experience, starting with the demo of some nifty stuff our teams worked very hard to build this weekend.
Google, you are doing us proud and following the "don't be evil" ethos to a T here. Thank you again. I remain committed to helping you open source personal health control over the modification and sharing of #myhealthdata, when and where and to whom I want to share it (or not!).