Datacubed Health vs MyDataHelps (CareEvolution)(ePRO)

Clinical-trial and research teams comparing participant-facing ePRO for clinical trials, investigator-led studies, cohorts and registries, with integrated EDC options for clinic-heavy protocols.

Guide updated How we compare

Compare within ePRO

Study fit, side by side

These notes describe the products in the ePRO guide.

Datacubed Health

Best for
Sponsor studies that want an engagement-focused eCOA app with expert configuration
What to consider
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.
Less suitable for
Study teams that must configure and launch without an expert-led implementation process.

Study-fit source

Read product profile

MyDataHelps (CareEvolution)

Best for
Academic and federally funded studies combining ePRO with wearable or EHR data, using self-service configuration or a scoped custom participant experience
What to consider
MyDataHelps lets researchers design a study in a free self-service Designer, with a validated instrument library, flexible schedules, eConsent and a REDCap integration. Participants use the shared MyDataHelps app; CareEvolution has built a white-label version for the All of Us Research Program. Its security credentials are US federal frameworks (NIST 800-53, NIH Authority to Operate) rather than ISO 27001 or SOC 2.
Less suitable for
Teams expecting a separately branded app to be the default shared-app deployment; confirm custom-app delivery scope and requirements.

Study-fit source

Read product profile

Compare the features

Both products use the same category definitions. Product order is editorial; products are not ranked.

Full ePRO feature comparison

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.

Datacubed Health vs MyDataHelps (CareEvolution) (ePRO): category feature evidence and sources. Products are not ranked.
Category featureDatacubed HealthMyDataHelps (CareEvolution)
Participant app and study branding
Feature definitions
Supported
A native or browser-based participant app works on the participant’s own device.
Extended support
Own-phone access plus a documented separately branded study app or custom participant application beyond the shared vendor-app experience. Offline operation is assessed separately.
Supported

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

Source
About this support label

Own-device participant access is documented. A separately branded study app is not established by this source; offline support and limitations remain described in the feature note and at-a-glance information.

Extended support

Participants normally use the shared MyDataHelps app. CareEvolution also documents a separate white-label All of Us app supporting enrollment, eConsent, ePRO and participant engagement; a custom deployment must be scoped.

Source
About this support label

The documented All of Us white-label app establishes a separately branded participant deployment. This does not mean a branded deployment is included in the standard shared app.

Questionnaires and scheduling
Feature definitions
Supported
Questionnaires have schedules, event triggers or participant-specific availability.
Extended support
Base support plus a validated or curated instrument library and event-triggered scheduling.
Supported

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

Source
Extended support

Library of validated instruments and NIH common data elements, schedules relative to participant events or criteria, and versioned screening and consent.

Source
About this support label

A validated instrument library and schedules relative to participant events or criteria are documented.

Time to launch and self-service build
Feature definitions
Supported
A study build process or setup timeline is documented.
Extended support
Base support plus a self-service study builder and a stated launch or data-capture timeline.
Supported

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

Source
Extended support

Self-service no-code Designer with a free account; CareEvolution states a trial can launch in hours.

Source
About this support label

A self-service no-code Designer and a stated trial-launch timeline are documented.

Compliance and security
Feature definitions
Supported
Support for relevant trial or security standards or controls is stated.
Extended support
Base support plus public ISO or SOC certificate or audit-report evidence and relevant trial controls.
Supported

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

Source
About this support label

Trial or security standards are stated; public certificate or audit-report evidence is not established.

Supported

States HIPAA and Part 11 compliance and NIST 800-53 controls assessed by a FedRAMP 3PAO with an NIH Authority to Operate, but names no ISO 27001 or SOC 2 certification.

Source
About this support label

Trial or security standards are stated; public certificate or audit-report evidence is not established.

eConsent and data connections
Feature definitions
Supported
eConsent shares a platform or integration with ePRO or EDC.
Extended support
Base support plus a documented API for study-data connections.
Extended support

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

Source
About this support label

eConsent shares the ePRO ecosystem with API integrations to study and health-record systems.

Extended support

eConsent with e-signatures, a documented two-way REDCap integration, and REST APIs and SDKs.

Source
About this support label

eConsent, a two-way REDCap integration, REST APIs and SDKs are documented.

Published pricing and terms
Feature definitions
Supported
A pricing basis, model or contract terms beyond contact sales are published.
Extended support
Base support plus numerical production pricing or a usable free production option with its conditions stated.
Unknown

No pricing model, prices or contract terms published.

Source
About this support label

No pricing basis, model or contract terms are published in this note.

Unknown does not mean unavailable. The public evidence does not establish support under this category’s definition.

Unknown

A free Designer account to build and explore a study; paid pricing for running studies is not published.

Source
About this support label

A free Designer account is documented, but it does not establish production pricing or terms for running a study.

Unknown does not mean unavailable. The public evidence does not establish support under this category’s definition.

The guide update date reflects guide edits. Vendor statements are attributed in the evidence.

Keep the category in view

Compare these products with the other tools in the ePRO guide using the same feature definitions.

More ePRO comparisons featuring one of these products.