Datacubed Health logo

Datacubed Health review (2026)

Headquarters King of Prussia, Pennsylvania, USAFounded 2016

eCOA and ePROeCOA and ePROeConsentPatient engagementConnected sensors and integrationsReports and dashboards
Facts last verified Nov 10, 2026How we compare

Study fit

Sponsor studies that want an engagement-focused eCOA app with expert configuration

Explore documented features
Visit datacubed.com

Study fit

Datacubed offers native iOS and Android eCOA with offline use, optional gamification and eConsent in one ecosystem, with API integrations to EDC systems. Its stated average from setup to go-live is seven to ten weeks, and it publishes no pricing information. It states Part 11, HIPAA and GDPR compliance but names no ISO 27001 or SOC 2 certification publicly.

From our review on the ePRO list, which is one of the guides that includes this product.

Best for

  • Sponsor studies that want an engagement-focused eCOA app with expert configuration
  • Wearables Sponsor eCOA studies that add phone-based health data to questionnaires

Not for

  • Teams that want published prices or a self-service build

Documented features

Best ePRO software for clinical trialsFeature details
Participant app and study branding

BYOD on iOS and Android, online or offline, with reminders; an own-brand option is not documented.

Source
Questionnaires and scheduling

No-code authoring with complex and cycle-based schedule logic for PRO, ClinRO, ObsRO and PerfO; no public instrument library.

Source
Time to launch and self-service build

Datacubed states a 7 to 10 week average from setup to go-live, configured with its consultants.

Source
Compliance and security

States Part 11, HIPAA and GDPR compliance; no ISO 27001 or SOC 2 certification found on its public pages.

Source
eConsent and data connections

eConsent in the same ecosystem as ePRO, with API integrations to EDC, RTSM and EHR systems.

Source
Published pricing and terms

No pricing model, prices or contract terms published.

Source
Compare these features side by side
Best software for wearable data collection in clinical trialsFeature details
Consumer wearable coverage

Apple Health and Google Fit plus other connected sensors and medical devices.

Source
Data depth and granularity

Wearable data granularity is not documented on its public pages.

Source
ePRO in the same app

ePRO, eCOA and eConsent in the same participant app.

Source
Adherence and sync monitoring

Real-time dashboards for compliance, retention and device usage; automated non-sync alerts are not described.

Source
Compliance and security

States Part 11, HIPAA and GDPR compliance; no ISO 27001 or SOC 2 certification found on its public pages.

Source
Published pricing and terms

No pricing model, prices or contract terms published.

Source
Compare these features side by side

At a glance

Headquarters

King of Prussia, Pennsylvania, USA

Source
Founded

2016

Source
Pricing model

Not published

Source
Free trial or demo

Needs facts

21 CFR Part 11 / EU Annex 11

Part 11 stated; Annex 11 not stated

Source
GDPR and HIPAA

Both stated

Source
Security certifications

No ISO 27001 or SOC 2 named publicly

Source
Languages

100+ languages across 60+ countries (stated)

Source
API and integrations

API integrations with EDC, CTMS, RTSM, EHR and safety systems

Source
Own-phone app (BYOD)

iOS and Android BYOD, or provisioned devices

Source
Works offline

Yes (stated)

Source
Wearable data

Apple Health, Google Fit and other connected sensors

Source
eConsent

Yes, in the same ecosystem

Source
Setup time

7 to 10 weeks average from setup to go-live (stated)

Source

What it covers

  • eCOA and ePRO
  • eConsent
  • Patient engagement
  • Connected sensors and integrations
  • Reports and dashboards

Module names as Datacubed lists them. See the sourced feature statements for details and limitations.

Pricing

Pricing model: Not published

Not published

Alternatives to Datacubed Health

Work at Datacubed Health and see something out of date? Send us a public source and we will check it and update the page.

Request a correction