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.
These notes describe the products in the ePRO guide.
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.
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.
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.
MyDataHelps (CareEvolution) vs WeGuide (ePRO): category feature evidence and sources. Products are not ranked.
Category feature
MyDataHelps (CareEvolution)
WeGuide
Participant app and study brandingFeature 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.
MyDataHelps (CareEvolution)
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.
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.
WeGuide
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.
Dedicated institution-branded native app listings and configurable participant features meet the same published study-branding definition used for all products.
Questionnaires and schedulingFeature 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.
MyDataHelps (CareEvolution)
Extended support
Library of validated instruments and NIH common data elements, schedules relative to participant events or criteria, and versioned screening and consent.
A validated instrument library and schedules relative to participant events or criteria are documented.
WeGuide
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.
A self-service no-code Designer and a stated trial-launch timeline are documented.
WeGuide
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.
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 securityFeature 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.
MyDataHelps (CareEvolution)
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.
Trial or security standards are stated; public certificate or audit-report evidence is not established.
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.