ECG data from Google Health integration
AllRedundantBug1 week ago
I am looking to get ECG data via the Google Health API integration. I can't find any documentation for this integration at https://tryterra.co/integrations. When I configure the integration in my dashboard the configurable scopes are: Activity & Fitness, Health Metrics, Nutrition, and Sleep. To retrieve ECGs, Google's API requires the googlehealth.ecg.readonly scope which doesn't seem to be covered.
Can I configure additional provider-specific OAuth scopes when authenticating a Google Health user? If this isn't supported through the authentication API, can Terra enable it for my integration, and does Terra's Body API support retrieving the corresponding ECG data? Right now, I am getting empty ECG and AFib classification arrays from the Terra body API.
Can I also ask about the googlehealth.irn.readonly scope which is for irregular heartbeat notifications.
Vanessaadmin1 week ago
Hi,
ECG data from Google Health isn't available through Terra yet but we will most likely roll this out in the next few weeks. Today Terra's Google Health integration doesn't request the googlehealth.ecg.readonly scope. The four configurable scope groups you see in the dashboard (Activity & Fitness, Health Metrics, Nutrition, Sleep) map to the four Google Health scope categories Terra currently requests at consent. ECG lives in a separate Google scope that isn't wired up, and googlehealth.irn.readonly for irregular heartbeat notifications is in the same situation. That's why the ecg_signal and afib_classification_samples arrays on the Body payload come back empty for Google Health users.
Provider-specific OAuth scopes aren't configurable through the authentication API. The scope set per provider is centrally managed, and the dashboard toggles are the only way to adjust what gets requested on the consent screen. Extra Google scopes like googlehealth.ecg.readonly and googlehealth.irn.readonly can't be bolted onto an individual auth session.
On the data side, Terra's Body payload does model ECG and AFib classification (ecg_signal and afib_classification_samples under heart_data), and those fields are populated today for providers that expose ECG waveforms through their APIs, such as Withings. Google Health isn't one of them yet, so there's no fetch path that would fill those fields even if the scope were granted at auth.
Google Health field coverage is documented here if it helps in the meantime: https://docs.tryterra.co/help-center/help-topics/data-api-sdk/provider-coverage-and-per-provider-data-availability/google-health-data-coverage
RedundantBug2 days ago
Thanks for the reply. Is there a web page for news of when new enhancements roll out that I can keep an eye on?