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.
Medrio
Best for
Mid-size sponsors that want ePRO, eConsent and EDC configured in-house
What to consider
Medrio says its ePRO goes from contract to data capture in four weeks, built with a no-code tool on the same platform as its EDC and eConsent. Participants complete assessments in a browser rather than a native app. Medrio lists ISO 27001, SOC 2 and Part 11 compliance and describes subscription pricing without publishing prices.
Less suitable for
Protocols that require a native downloadable iOS or Android participant app instead of browser-based ePRO.
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.
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.
Medrio vs MyDataHelps (CareEvolution) (ePRO): category feature evidence and sources. Products are not ranked.
Category feature
Medrio
MyDataHelps (CareEvolution)
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.
Medrio
Supported
Web-based ePRO on any internet-connected device with customizable reminders; no native app.
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.
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.
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.
Medrio
Supported
No-code builder with branching, support for licensed or ad hoc assessments, and activation based on consent status or date; no ready instrument library is listed.
Library of validated instruments and NIH common data elements, schedules relative to participant events or criteria, and versioned screening and consent.
Trial or security standards are stated; public certificate or audit-report evidence is not established.
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.