Studies that collect data from participants' own consumer wearables (Apple Health, Health Connect, Fitbit, Garmin, Oura and similar) alongside ePRO in the same participant app.
These notes describe the products in the Wearables guide.
Fitabase
Best for
Academic teams collecting Fitbit or Garmin data who need close sync and battery monitoring
What to consider
Fitabase focuses on Fitbit and Garmin data, with second-level heart rate, minute-level activity and dashboards for sync times and battery levels, plus automated SMS reminders as an add-on. Its Engage app adds surveys and EMA but no eConsent. Its public security page describes Azure hosting and encryption but makes no Part 11, HIPAA or GDPR statement.
Studies that need ongoing participant engagement alongside wearable data, questionnaires, consent and follow-up in one study app
What to consider
WeGuide connects wearable-data collection with ongoing participant engagement, ePRO, eConsent, reminders and follow-up in a branded study app. Garmin is a native integration; other supported devices may supply data through Apple Health or Health Connect, and Fitbit Air support is listed. Raw accelerometer and gyroscope data are documented at 25 Hz on supported Garmin models only. Apple independently describes an MCRI project using a WeGuide-developed app to share Apple Watch ECGs with researchers. Confirm the study’s devices, data routes and export requirements.
Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.
Expand a feature definition or support note for context and its original source.
Fitabase vs WeGuide (Wearables): category feature evidence and sources. Products are not ranked.
Category feature
Fitabase
WeGuide
Consumer wearable coverageFeature definitions
Supported
Integration with a named consumer wearable platform or health-data service is documented.
Extended support
Base support plus Apple's health-data service and either Health Connect or Google Fit integrations.
Fitabase
Supported
Fitbit (through the Google Health API) and Garmin devices only.
Garmin is native; Apple Health and Health Connect are supported data routes, and Fitbit Air support is listed. Other makers’ data depends on the metrics their apps share with the phone health store. Confirm the proposed model and route.
Raw accelerometer and gyroscope data at 25 Hz are documented for supported Garmin models. Phone health-store data and Fitbit Air support do not imply the same raw-sensor access.
Sync-status dashboards and automated sync-lapse SMS alerts are documented; SMS alerts are a premium add-on.
WeGuide
Supported
Wear and sync reminders through push notifications and in-app messaging, and live adherence monitoring; a sync-status dashboard is not described publicly.
SSL and access logging establish security controls; trial-specific compliance statements are not documented.
WeGuide
Supported
WeGuide states ISO 27001:2022 certification, HIPAA support (BAA on request), GDPR and FDA 21 CFR Part 11 support, and TGA Class I registration (ARTG 355337). The public page does not supply the certificate or an audit report.