Understanding Data Collection Mechanisms Used by Health and Wellness Applications (Preprint)

UNSTRUCTURED Our objective is to better understand health-related data collection across different mHealth app categories. This would help in developing a health domain model for mHealth apps to facilitate app development and data sharing between these apps to improve user experience and reduce redundancy in data collection. We identified app categories listed in a curated library which was then used to explore the Google Play Store for health/medical apps that were then filtered using our inclusion criteria. We downloaded and analysed these apps using a script we developed around the popular AndroGuard tool. We analysed the use of Bluetooth peripherals and built-in sensors to understand how a given app collects/generates health data. We retrieved 3,251 applications meeting our criteria, and our analysis showed that only 10.7% of these apps requested permission for Bluetooth access. We found 50.9% of the Bluetooth Service UUIDs to be known in these apps, with the remainder being vendor specific. The most common health-related services using the known UUIDs were Heart Rate, Glucose and Body Composition. App permissions show the most used device module/sensor to be the camera (20.57%), closely followed by GPS (18.39%). Our findings are consistent with previous studies in that not many health apps were found to use built-in sensors or peripherals for collecting health data. The use of more peripherals and automated data collection along with integration with other apps could increase usability and convenience which would eventually also improve user experience and data reliability.