Healthcare Misses the Point of GoogleFit

This post was originally published in HL7Standards, a CorepointHealth affiliate following the Google I/O announcements regarding GoogleFit and AndroidWear.

As expected last Wednesday at the Google I/O developer conference, Google Play Product Manager Ellie Powers announced a new fitness SDK for digital healthcare applications and device developers, GoogleFit. Unlike competing healthcare data aggregators such as Apple’s HealthKit, Microsoft’s Healthvault, and Samsung’s SAMI, GoogleFit is more focused as a set of fitness-focused APIs for developers to leverage while building third party applications.

Apple recently announced HealthKit at their WWDC in early June and has taken an aggressive approach toward centralized personal healthcare data curation. This includes collaborations with Mayo Clinic and Epic. HealthKit, based largely on Apple’s Passbook app, relies on users to engage with their platform, in-house apps, proprietary biosensors and industry partnerships.

Conversely, Google’s a la carte approach focuses more on personal daily workflow models and integrating everyday tasks into a common platform to help establish trends which can provide actionable insights. The GoogleFit SDK will allow data from user-chosen health, fitness and wellness devices to play nice with a variety of Android devices and platforms, curating all user data in one place, in one app, of the user’s choice. With established partnerships such as Samsung, Motorola, Fossil, LG, Intel, RunKeeper, Basis, Polar, Adidas, Nike, and more, AndroidWear and GoogleFit complement the already available social, location, notification and community applications, allowing information sharing across multiple platforms, and thereby keeping users engaged.

Google has also promised to keep the same data takeout policy that it has applied to their other applications, leaving the user in control of data ownership and able to share, delete or export their information as they choose. Strong data ownership rights, and this exportability capability adds significant development potential over other platforms. This policy is in stark contrast to Apple’s historical data ownership policies which are particularly concerning when considering possible integration with Epic health systems.

Parallel to the GoogleFit announcement was AndroidWear, several Android smartwatch roll-outs (LG’s G, Samsung Gear Live and a very nice Moto360 for later this summer), the Open Automotive Alliance collaboration for Android Auto API development with 40 partners, an unlimited encrypted Google Drive enterprise storage solution and several new cloud developer tools and updates.

Additionally, Google VP Sundar Pichai described the new Android UI as “designed for form factors beyond mobile, truly cross platform” hinting at a future run at the desktop market and beyond. Together, with Chromecast mirroring, Android TV, the already acquired Nest, and several other virtual reality, interactive, education, and ATAP Group projects, these disparate ventures integrate broad human experiences into one tightly optimized package centered on a wearable format. In Apple’s HealthKit, a user’s personal health data is the pieces of a puzzle, and Apple’s app would be the whole picture. In Google’s offering from this past week, GoogleFit data is just one piece along with all the other platform offerings to create the whole user picture.

This integrated approach addresses both Google’s lack of a competitive wellness and fitness market offering, and the problem of wearable device user retention seen by stand-alone health tracking devices.

Essentially, instead of focusing on creating yet another isolated health and wellness platform, Google is breaking down data silos between common everyday actions, including health and wellness data. It’s not far fetched for a user’s car to respond to a driver’s real time data, or an integration with Nest allowing for a safer aging in place experience for elderly users. Simpler integrations? Menu and dinner take-out data with your Withings scale or social fitness training and education in a remote situation.

Unfortunately it is still unclear how, if at all, any of the big three aggregate platforms are addressing the data input issues that stem from third party devices. Not only are many popular wearable devices inaccurate (Samsung is notorious for this), but most do not output user data in a raw format, instead opting for some level of aggregation, leaving developers to hack APIs or reverse engineer devices. While this may be sufficient for current applications, it is not a scalable standard as wearable technology matures to include medical metrics, especially if EHR and clinical integration is on the horizon.


Leave a Comment
Note: you must be signed into your GitHub account to leave a comment. Why?