Datacubed Health vs WeGuide(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

WeGuide

Best for
Clinical trials and research studies where ongoing participant engagement, scheduled questionnaires and follow-up need to work together in a branded app
What to consider
WeGuide connects participant-reported outcomes with ongoing engagement throughout a clinical trial or research study. Screening, eConsent, scheduled questionnaires, reminders, follow-up and wearable data can work together in a branded iOS and Android app. The workflow suits studies that need participants to contribute between visits or over time, including investigator-led studies, cohorts and registries. Connect an EDC when the protocol needs additional clinical-data workflows. Typical configuration is stated as two to four weeks; partial offline support depends on study setup.
Less suitable for
Protocols requiring extensive in-visit clinical data entry, complex eCRF/query workflows, medical coding or drug-supply management from the participant platform.

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 WeGuide (ePRO): category feature evidence and sources. Products are not ranked.
Category featureDatacubed HealthWeGuide
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

Native iOS and Android participant apps with the organization’s branding, configured welcome screens and study features, and dedicated Apple and Google store listings under the organization’s name.

Source
About this support label

Dedicated institution-branded native app listings and configurable participant features meet the same published study-branding definition used for all products.

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

A curated assessment-instrument catalogue plus recurring engagements and enrollment-, response- or score-triggered follow-up. Instrument permissions and appropriate language versions must be checked for the study.

Source
About this support label

The published catalogue and event-triggered follow-up meet the existing definition; catalog inclusion does not grant an instrument license.

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

Research teams configure schedules, reminders, content, consent and forms in a no-code Program Builder. WeGuide states typical study configuration takes two to four weeks, with its delivery team alongside and app publishing and integrations scoped during implementation.

Source
About this support label

The public page documents team-configurable no-code study workflows and a typical two-to-four-week configuration timeline. Delivery support and app publication remain part of implementation.

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

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.

Source
About this support label

Certification and trial/privacy controls are stated publicly; the certificate and audit report are not available in the cited public material.

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 in the same app plus an Integration Engine with REDCap, Castor and Medidata Rave connections over REST or FHIR APIs.

Source
About this support label

In-app eConsent connects study data through REST or FHIR APIs to named EDC systems.

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.

Supported

Quoted per study, with hosting, support and modules included. Email hello@weguide.health for a study-specific quote; price amounts are not published.

Source
About this support label

The public page specifies a per-study quote basis, but does not publish price amounts.

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.