ePRO (Electronic Patient-Reported Outcomes)

ePRO (electronic Patient-Reported Outcome) is the data-collection modality in which a clinical trial participant reports symptom, quality-of-life, or functional-status information directly into an electronic system — an app, a provisioned tablet, a wearable, or a web portal — rather than onto a paper form later transcribed by staff. It is one of the four Clinical Outcome Assessment (COA) types the U.S. FDA formally distinguishes: Clinical Outcome Assessment (COA) covers Patient-Reported Outcome (PRO), Clinician-Reported Outcome (ClinRO), Observer-Reported Outcome (ObsRO), and Performance Outcome (PerfO) — ePRO is specifically the electronic-capture-mode subset of the PRO category, not a separate COA type on its own.

The regulatory basis: FDA’s 2009 PRO guidance

FDA’s final guidance for industry, Patient-Reported Outcome Measures: Use in Medical Product Development to Support Labeling Claims, issued December 8, 2009 (following a February 2006 draft), is the primary document sponsors work against when a PRO instrument — electronic or paper — is intended to support a labeling claim about symptom benefit. The guidance recognizes multiple modes of PRO administration (interview, paper, electronic, web-based, and interactive voice response) and calls out specific concerns unique to the electronic mode: the principal investigator’s ability to access and control the ePRO data as the study’s electronic source documentation for FDA inspection purposes, database security, and safeguards against losing adverse-event information reported through the ePRO channel rather than through the standard site-reported pathway. Where a sponsor administers the same instrument through more than one mode (for example, paper at some sites and ePRO at others), FDA reviews the comparability of the resulting data before permitting the results to be pooled.

Why ePRO exists as a distinct capture stream from the CRF

A trial’s primary data record — the Electronic Data Capture (EDC) system and its electronic case report forms (eCRFs) — is built for data entered or reviewed by site personnel: visit data, lab values, adverse-event assessments, and clinician-observed findings. ePRO data is captured through a separate patient-facing system (often called an eCOA platform when it also handles ClinRO/ObsRO/PerfO instruments) precisely because the PRO definition requires the response to come from the patient without amendment or interpretation. Routing a PRO instrument through a coordinator’s eCRF entry — even electronically — breaks that chain, which is why a transcribed paper diary does not qualify as ePRO even once it lives in an electronic database. Most modern trial data architectures integrate ePRO output into the sponsor’s broader clinical database alongside EDC/CDMS data for analysis, but the ePRO capture event itself remains a distinct, patient-originated record. See the Clinical Data Management guide for how ePRO, EDC, and CDMS fit together as parts of the same overall data pipeline.

Instrument validation and selection

An ePRO deployment is only as good as the instrument delivered through it. Sponsors select PRO instruments with an established concept of interest and context of use — either through FDA’s voluntary Clinical Outcome Assessment (COA) Qualification Program, which produces a qualified instrument any sponsor can use without re-justifying its suitability, or through instruments with an independent validation history in the relevant population and disease area. Widely used examples include NCI’s PRO-CTCAE (patient-reported adverse-symptom reporting, designed as a patient-facing complement to the clinician-scored CTCAE) and PROMIS (the NIH-funded Patient-Reported Outcomes Measurement Information System) item banks and short forms. Migrating a validated paper instrument onto a new electronic mode of administration is itself a step that typically requires equivalence testing (commonly called migration or mode-equivalence testing) rather than being assumed automatically valid, since wording, layout, and response-scale rendering can all shift patient responses.

Compliance and completion-rate monitoring

Because ePRO data is often the primary or key secondary endpoint supporting a symptom-benefit label claim, sponsors and monitors track completion compliance closely — not just whether a form was eventually completed, but whether it was completed within the instrument’s defined recall window (same-day diary entries are far more reliable than a patient reconstructing a week from memory). ePRO platforms typically provide site- and study-level compliance dashboards flagging missed entries, out-of-window entries, and device or connectivity issues in near-real time, giving the site staff a chance to intervene before data becomes unusable. This compliance-monitoring function is one of the practical reasons trials increasingly prefer ePRO over paper PRO diaries: paper diaries cannot be timestamped at the point of entry, so a clinical monitor has no reliable way to confirm a paper diary entry was actually made on the date recorded (a long-documented problem sometimes called ‘parking-lot compliance’ where diary entries are filled in en route to the study visit rather than daily as instructed).

BYOD versus provisioned devices

Trials deploy ePRO through either provisioned devices (a tablet or device the study issues and controls) or BYOD (bring your own device, where the patient uses their own phone or computer via a web portal or app). Provisioned devices give the sponsor more control over the software environment and reduce the risk of a patient lacking a compatible device, but add logistics and device-management cost. BYOD reduces that overhead and can improve patient acceptability, but introduces variability in screen size, connectivity, and device familiarity that instrument developers and eCOA vendors need to account for in interface design and equivalence testing.

Data integrity and 21 CFR Part 11

Because ePRO records commonly serve as source data supporting a labeling claim, the same electronic-records expectations that apply to EDC apply here: audit trails, access controls, and (where electronic signatures are used) signature manifestations consistent with 21 CFR Part 11. Sponsors document the ePRO system’s validation status, data-transfer and reconciliation process with the broader clinical database, and business-continuity plan (what happens if a device fails or a patient loses connectivity) as part of the overall study data-management plan.

Related terms

• Clinical Outcome Assessment (COA) — the parent framework: PRO, ClinRO, ObsRO, and PerfO.
• Electronic Data Capture (EDC) — the site-facing eCRF system ePRO data is distinct from but often integrated with.
• 21 CFR Part 11 — the electronic-records/signatures regulation governing ePRO data integrity.
• Clinical Data Management — how ePRO, EDC, and CDMS fit into the overall trial data pipeline.