Google Health Data Types and Fitbit Google Health Fallback

[chrisnowak]

Overview

Based on #624

Implements a number of google health daily data types. I was not super comprehensive; I scoped this mostly to things that were similar to things we already supported from other sources (in particular Fitbit) vs. trying to support every google fit type in here.

Additionally, all Fitbit types other than RestingCaloriesBurned fall back to Google Health when Fitbit data is not available will prefer Google Health if it is available. So long as participants connect to Google Health by the time Fitbit api is discontinued their data should look uninterrupted and we should not need to adjust any existing views.

Edit: Originally had it fall back to Google Health, but it appears that there are differences on things like sleep time and sedentary time. Google Health is consistent with the Google Health app now, so it should prefer Google Health when it's available.

e.g.
My Fitbit API sleep data says 7h 54m last night
Google Health API sleep data says 8h 18m
The Google Health app says 8h 18m

Security

Consider potential security impacts and complete the following checklist.
REMINDER: All file contents are public.

• I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.
  • Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
  • There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.
• These changes do not introduce any security risks, or any such risks have been properly mitigated.

Testing

Consider whether the changes might have device-specific behaviors (screen padding, new APIs, etc.) and check one of the following boxes:

• This change can be adequately tested using the MDH Storybook.
• This change requires additional testing in the MDH iOS/Android/Web apps. (Create a pre-release tag/build and test in a ViewBuilder PR.)

Documentation

Consider whether there are any documentation impacts and check one of the following boxes:

• I have added relevant Storybook updates to this PR.
• If this feature requires a developer doc update, I have tagged @CareEvolution/api-docs.
• This change does not impact documentation or Storybook.

Reviewers

Assign to the appropriate reviewer(s). Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including:

• Subject-matter experts
• Style/editing reviewers
• Others requested by the content owner

Consider "Squash and merge" as needed to keep the commit history reasonable on main.

[Copilot]

Pull request overview

This PR expands the device-data “daily data” layer to support a broad set of Google Health V2 data types, and updates Fitbit-backed daily types (and intraday heart rate) to prefer Google Health when available to smooth the Fitbit retirement transition.

Changes:

• Add Google Health daily data providers + daily data type definitions (sleep, steps, heart rate, activity minutes/zones, calories, distance, etc.).
• Update Fitbit daily types (and intraday HR provider ordering) to prefer Google Health data when present, while preserving existing Fitbit-configured type keys.
• Update combined daily types/providers to include Google Health, add translations for the new “wear-time” label, and pin npm in the publish workflow for Node 20 compatibility.

Reviewed changes

Copilot reviewed 36 out of 37 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/helpers/heart-rate-data-providers/combined-intraday-heart-rate-providers.ts	Adds Google Health intraday HR type mapping + source ordering helper to prefer Google Health over Fitbit.
src/helpers/daily-data-types/google-health.tsx	Introduces Google Health daily data type definitions (labels/icons/formatters/availability).
src/helpers/daily-data-types/fitbit.tsx	Wraps Fitbit daily types to prefer Google Health providers while keeping existing Fitbit type keys.
src/helpers/daily-data-types/combined.tsx	Adds Google Health as an additional availability source for unified/combined types.
src/helpers/daily-data-types/all.ts	Registers Google Health type definitions into the global daily type list.
src/helpers/daily-data-types.tsx	Extends DailyDataType and DailyDataTypeDefinition.dataSource to include Google Health.
src/helpers/daily-data-providers/index.ts	Re-exports Google Health providers and the “prefer over Fitbit” wrapper.
src/helpers/daily-data-providers/google-health.ts	Implements Google Health V2 daily providers (rollups, totals, unit conversions).
src/helpers/daily-data-providers/google-health-preferred-over-fitbit.ts	Adds a wrapper that prefers Google Health per-day and falls back to Fitbit on missing days.
src/helpers/daily-data-providers/data-collection-helper.ts	Adds the googleHealthEnabled flag mapping for availability checks.
src/helpers/daily-data-providers/combined-steps.ts	Adds Google Health as an additional steps source in the combined steps provider.
src/helpers/daily-data-providers/combined-sleep.ts	Adds Google Health as an additional sleep source in the combined sleep provider.
src/helpers/daily-data-providers/combined-resting-heart-rate.ts	Adds Google Health as an additional resting HR source in the combined RHR provider.
src/helpers/daily-data-providers/combined-active-calories-burned.ts	Adds Google Health as an additional active-calories source in the combined provider.
package.json	Bumps package version for this Google Health iteration.
package-lock.json	Updates lockfile version metadata to match the package version bump.
locales/en.json	Adds translation for wear-time.
locales/es.json	Adds translation for wear-time.
locales/de.json	Adds translation for wear-time.
locales/fr.json	Adds translation for wear-time.
locales/fr-CA.json	Adds translation for wear-time.
locales/it.json	Adds translation for wear-time.
locales/nl.json	Adds translation for wear-time.
locales/pl.json	Adds translation for wear-time.
locales/pt.json	Adds translation for wear-time.
locales/pt-PT.json	Adds translation for wear-time.
locales/ro.json	Adds translation for wear-time.
locales/so.json	Adds translation for wear-time.
locales/sw.json	Adds translation for wear-time.
locales/tl.json	Adds translation for wear-time.
locales/fil.json	Adds translation for wear-time.
locales/vi.json	Adds translation for wear-time.
.github/workflows/cicd-publish.yml	Pins npm to v11 to avoid Node 22 requirement on the Node 20 publish runner.
tests/helpers/heart-rate-data-providers/combined-intraday-heart-rate-providers.test.ts	Adds tests asserting Google Health is preferred over Fitbit for intraday HR.
tests/helpers/daily-data-providers/google-health.test.ts	Adds unit tests for key Google Health daily providers and conversions.
tests/helpers/daily-data-providers/google-health-preferred-over-fitbit.test.ts	Adds unit tests for the per-day preference/fallback wrapper.
tests/helpers/daily-data-providers/combined-active-calories-burned.test.ts	Extends combined active calories tests to include Google Health.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[lynnfaraday]

This needs to go through the localization hub or else everything will get out of sync. I can help if you like.

[lynnfaraday]

Synced with locale hub. This hub PR needs to be merged at the same time as this one: https://github.com/CareEvolution/localization-hub-strings/pull/3

(It's stacked on the locale hub PR for the other google health PR to mirror the merge order of these two MDHUI PRs)

[lynnfaraday]

Would external folks get these names from the alldatatypes endpoint?

[chrisnowak]

Ah yes, and this comment should be removed

[lynnfaraday]

My comments have been addressed. Defer to Garrett on the rest.

[greinard]

Looks good to me.

I'll make that UT adjustment we spoke about offline, which once merged, will cause some test failures here. Once those are fixed up, should be good to 🚢 whenever you are ready.