Choosing an ePRO solution impacts patient compliance, data completeness, and the reliability of patient-reported outcomes in clinical trials. It is more than a software procurement decision.
Regulators do not mandate one specific ePRO technology. However, when PRO data support clinical endpoints or regulatory claims, sponsors must be able to demonstrate that the instruments, collection methods and resulting data are fit for purpose.
The FDA recommends planning procedures to reduce missing PRO data, including patient and investigator training, reminders, and completion monitoring. Its guidance also recognises that electronic collection can reduce patient burden by enabling assessments outside the clinic. The EMA reflection paper on health-related quality-of-life measures similarly emphasises the validity, reliability, and interpretability of PRO measures.
What should sponsors evaluate in an ePRO solution?
A practical ePRO evaluation should cover six connected areas:
- regulatory readiness and data integrity.
- Patient usability and accessibility.
- Data-collection options.
- Integration with the EDC.
- Time-window and reminder management.
- Real-time compliance monitoring.
A robust platform must perform well in all six areas. Advanced features in one aspect cannot offset poor usability, fragmented data flows, or insufficient assessment controls.
Regulatory readiness and data integrity
Start by establishing whether the ePRO solution can operate within the regulatory framework for the study. For FDA-regulated research, this includes controls supporting 21 CFR Part 11 requirements for electronic records and electronic signatures. The assessment should also cover audit trails, access controls, system validation, data security, and traceability.
Sponsors should ask:
- is the platform validated for its intended use?
- Are all data creation and modification activities traceable?
- How are user access and authentication controlled?
- Can the vendor provide relevant validation documentation?
- How are backups, disaster recovery and data retention managed?
- Can the system document how and where each assessment was completed?
The latest ICH E6(R3) Good Clinical Practice guideline reinforces a proportionate, risk-based approach to trial quality and managing computerised systems. A vendor should explain how its controls address risks associated with the specific study, not just provide a list of certifications.
Red flag: the vendor claims that the software is “compliant” but cannot provide validation evidence or explain shared responsibilities between the provider, sponsor and CRO.
Patient usability, accessibility and multilingual support
The most effective ePRO solution is one that patients can use accurately and consistently, not simply the one with the most features. Interfaces should be clear for all ages, health conditions, digital skill levels, and physical or cognitive abilities. Evaluate the entire patient journey, from login to support requests.
Check whether the solution provides:
- responsive interfaces for smartphones, tablets and computers.
- Simple authentication without unnecessary patient burden.
- Clear instructions and readable controls.
- Accessibility features appropriate to the target population.
- Consistent questionnaire presentation across devices.
- Multilingual interfaces and controlled questionnaire versions.
Vendors should explain how their electronic implementation maintains the meaning and measurement properties of each instrument.
Linguistic validation goes beyond translating interface labels and may require authorised versions, cultural adaptation, back-translation, and approval workflows.
Red flag: the product demonstration focuses on the sponsor dashboard but does not show the full experience from the patient’s perspective.
If your study includes diverse populations or short assessment windows, explore how ACTide ePRO supports multilingual, patient-friendly data collection.
Data-collection modes and study continuity
Data-collection options should reflect the protocol and patient population. Depending on the study, patients may submit data through a mobile device, tablet, or web browser, either at home or at the site. Evaluate:
- supported devices and operating systems.
- Bring-your-own-device and provisioned-device models.
- Browser-based and mobile access.
- Behaviour under weak or interrupted connectivity.
- Offline capabilities, if required.
- Synchronisation and duplicate-prevention controls.
- Device replacement and account-recovery procedures.
Offline mode should not be treated as a simple yes-or-no feature.
Sponsors need to understand which functions remain available, how timestamps are managed, when data synchronises, and how conflicts are prevented.
Red flag: the vendor promises “any device, anywhere” without defining technical limitations, supported versions or the behaviour of data during connectivity loss.
Native EDC integration and controlled data flow
A stand-alone ePRO platform can increase reconciliation work and delay data access. Before selection, map the full data journey from questionnaire completion through review, cleaning, analysis, and export.
Important questions include:
- does ePRO data enter the central clinical database directly?
- Is manual import or re-entry required?
- How are patient and visit identifiers aligned?
- Are data changes traceable across systems?
- Can validation rules and review workflows be applied centrally?
- How quickly can study teams access new responses?
Native integration reduces transfers and avoids creating parallel data repositories. With ACTide eCRF, patient-reported information is managed within the wider clinical data environment instead of being reconciled through disconnected workflows.
Study teams should also evaluate how questionnaires are configured and maintained. The ability to build controlled study structures through ACTide Designer can support consistency between protocol requirements, patient assessments and the eCRF.
Red flag: integration depends on recurring spreadsheet exchanges or custom development that has not been included in the proposed implementation timeline and price.
Time windows, reminders and missed assessments
Assessment timing can determine whether a response is clinically meaningful.
A symptom diary completed outside its protocol-defined window may not be equivalent to one recorded at the intended time. The ePRO platform should let teams configure:
- opening and closing times for each assessment.
- Recurring schedules.
- Time-zone handling.
- Visit-related and event-triggered questionnaires.
- Patient reminders and escalation rules.
- Rules for late, missed or partially completed sessions.
The FDA’s guidance on core patient-reported outcomes in cancer clinical trials recommends establishing procedures to mitigate missing data and documenting reasons for missing PRO assessments. This makes reminder logic and missing-data visibility part of the study’s evidence strategy, not just convenience features.
Ask whether timing rules can be adjusted by study, patient cohort, or individual patient when allowed by the protocol. The system should never silently overwrite the original schedule or hide out-of-window entries.
Red flag: missed questionnaires disappear from the patient interface without creating a traceable status or reason for non-completion.
Real-time compliance monitoring
Sponsors and CROs should not discover low completion rates at database lock. The platform should make non-compliance visible while corrective action remains possible.
Useful monitoring capabilities include:
- completion rates by site, visit and questionnaire.
- Missing and partially completed assessments.
- On-time versus out-of-window submissions.
- Trends by country and language.
- Patient-level follow-up indicators.
- Configurable alerts for declining compliance.
- Exportable reports for study oversight.
Dashboards should enable investigation, not just display summary percentages.
Teams must be able to identify affected sites, visits, or assessments without exposing patient data to unauthorised users.
Red flag: the system reports only overall completion rates and cannot identify where or why missing data are accumulating. A study-specific demonstration is the best way to test these workflows.
CTA: Request an ACTide ePRO demo to assess questionnaire scheduling, patient data capture and central monitoring against your protocol.
Key questions to ask an ePRO vendor
A structured discussion with the vendor should extend beyond the standard product presentation.
How are incomplete or missed sessions handled?
Ask the vendor to demonstrate the entire process. Check what patients see, what the study team sees, and what information reaches the analysis dataset. The platform should distinguish between:
- questionnaire that was never opened.
- Partially completed questionnaire.
- Submission made outside the permitted window.
- Technical failure.
- Deliberate patient decision not to respond.
These situations may require different operational and statistical treatment.
Does the system support validated scales?
Ask about the implementation process for instruments such as PROMIS, EQ-5D, BPI, and PGIC, not just whether they can technically be reproduced. The vendor should clarify:
- whether licensing remains the sponsor’s responsibility.
- How authorised wording and formatting are preserved.
- Whether electronic equivalence evidence is required.
- How scoring algorithms are implemented and verified.
- How instrument versions are controlled.
A platform’s ability to configure a questionnaire does not automatically grant permission to use a copyrighted instrument.
How are translations and back-translations managed?
Determine whether the vendor provides linguistic-validation services or only technical implementation. Ask how translated versions are approved, linked to the correct country and language, tested on target devices, and maintained throughout the study.
How are protocol amendments managed after go-live?
The vendor should demonstrate how changes are assessed, configured, tested, approved and released without affecting previously collected data. Version history and the effective date of each questionnaire must remain traceable.
What patient and site support is available?
Clarify operating hours, supported languages, escalation times, and responsibilities. Support should also cover device replacement, forgotten credentials, connectivity issues, and questions about system use without guiding patients’ clinical responses.
Common mistakes when choosing an ePRO platform
An unsuitable system can cause more than operational inconvenience. It may result in low completion rates, avoidable missing data, and evidence that is difficult to interpret.
Selecting a stand-alone tool without assessing reconciliation
A lower initial software price can hide the cost of transfers, mappings, validation, and repeated reconciliation. Evaluate the total data workflow, not just the patient-facing application.
Underestimating patient experience
A workflow that seems simple to a digital product team may still be difficult for elderly, fatigued, or low-tech participants. Evaluate usability with representative users and devices before launch.
Treating reminders as a complete compliance strategy
Notifications help, but excessive reminders can cause fatigue. Completion also depends on appropriate questionnaire length, clear instructions, site engagement, patient training, and accessible support.
Ignoring post-launch support
Studies change after go-live. Protocol amendments, new countries, updated questionnaires, and device problems require defined response times and controlled processes.
Assuming translation equals linguistic validation
Direct translation alone may alter a scale’s meaning or comparability. Sponsors must verify instrument licences, authorised language versions, and the required validation methodology.
ACTide ePRO: integrated, configurable and patient-friendly
ACTide ePRO supports direct electronic collection of patient-reported data through responsive interfaces across smartphones, tablets, and desktops. Capabilities includes:
- responsive patient data-entry interfaces.
- Multilingual support.
- Configurable questionnaires.
- Device notifications.
- Secure authentication options.
- Image and file upload.
- Real-time data collection.
- Direct storage in the ACTide eCRF database.
Integration with ACTide eCRF helps study teams manage patient-reported and site-collected information within the same clinical data environment.
ACTide Designer supports configuring study structures and data-collection workflows without creating an isolated ePRO process.
The final choice should be based on the protocol, population, endpoints, and operational model of each trial. A focused demonstration can reveal whether the solution fits these requirements before implementation begins.
Request a personalised ACTide ePRO demo and evaluate the patient journey, questionnaire configuration, integrated data flow and compliance monitoring against your study needs.