Fitbit to use Google's new Cloud Healthcare API to make its data available to doctors, letting them regularly monitor devices
Brian Heater / TechCrunch :
Context & Ripple Effects
By mid-2018, Fitbit had already spent years building a healthcare arm: it went HIPAA compliant and put devices on 335k Target workers back in 2015, then in February bought Twine Health, a startup connecting patients with health coaches and doctors. The Cloud Healthcare API announcement is the plumbing step in that arc — instead of selling devices into wellness programs, Fitbit is wiring its sensor data directly into clinical systems through Google's cloud.
The move also prefigures what came later: Google's eventual acquisition of Fitbit, framed as being about devices rather than data, and the broader push toward cross-app health interoperability that surfaced again with Health Connect.
First-order effects
- Doctors gain standing access to patients' Fitbit device data through the Cloud Healthcare API, turning periodic check-ins into continuous remote monitoring.
Second-order effects
- The integration deepens Fitbit's dependence on Google's cloud just as its Twine Health coaching business needs exactly this kind of clinical connectivity — making Fitbit a more attractive acquisition target for Google, which closed the deal in 2021.
Third-order effects
- If wearables become routine clinical endpoints, health data consolidates around a few cloud platforms certified to handle it, shifting leverage from device makers to whoever operates the compliant data layer between consumers and providers.
The trend: Consumer wearables are evolving from fitness trackers into remotely monitored medical devices, with cloud APIs as the compliance layer that makes clinical integration possible.