Apple integrates Health and Activity data so it must be HIPAA compliant.Well, that seems pretty silly.
Thanks for the reply.
I do not think Apple has stated it's reasoning for why Health data are device-locked. So, the HIPAA defense may just be a guess. Regardless, the OP is right-- it is silly. Activity and fitness data are not controlled by HIPAA. So this data problem is just poor design and architecture.Apple integrates Health and Activity data so it must be HIPAA compliant.
They haven't and it is just a guess. However Apple promotes and considers their reputation in part built on user privacy. Any breach of user privacy is considered a failure and Apple was severely burned in the picture/iCloud brute force attack. I bet engineers have reminders posted to NEVER let that happen again. So Apple is not likely to allow your personal fitness/health data to be venerable to an easy phishing breach since it would reflect back to Apple.I do not think Apple has stated it's reasoning for why Health data are device-locked. So, the HIPAA defense may just be a guess. Regardless, the OP is right-- it is silly. Activity and fitness data are not controlled by HIPAA. So this data problem is just poor design and architecture.
My hunch is that this will come. Apple will have to split Activity and Health. Activity will maintain its activity data and have export utilities. Then, it will feed into Health. It is data redundancy, but Apple needs to figure out how to export complete geocoded activity data in an industry standard format.It would really make sense for apple to create a health app or work out app for the Mac to recieve this type of info. They must have a reason for not doing it. Perhaps they are supporting the 3rd party app developers?