ePRO, EMA, RWD: Three Terms People Keep Using Interchangeably

I read a lot of protocols and grant drafts, and the same thing keeps happening. "ePRO," "EMA," and "real-world data" get used as if they're synonyms. They aren't. One is a delivery channel, one is a measurement design, one is a source category. They stack on top of each other, they don't replace each other.

This matters for your score. When a reviewer hits "we will use RWD to measure symptoms" in your Significance section, they notice, because RWD isn't an instrument. Imprecise vocabulary reads as unfamiliarity, and unfamiliarity sinks your Approach.

Here's how I keep the three straight.

ePRO is a delivery channel

Electronic patient-reported outcomes (ePRO) means a patient-reported outcome administered electronically instead of on paper. A PRO, on any medium, is a report of health status that comes straight from the patient with no clinician translation. The "e" only tells you how it's delivered.

The anchor is the FDA's 2009 PRO Guidance, which accepts patient-reported data for labeling claims when the instrument has adequate measurement properties. Later guidance is clear that electronic delivery is fine when it's shown equivalent to the validated paper form. Equivalence is the load-bearing word. If you're porting a validated paper instrument to an app, plan for an equivalence substudy or a citation-based rationale.

What ePRO doesn't tell you is when, how often, or in what state the patient answered. That's EMA's job.

EMA is a measurement design

Ecological momentary assessment (EMA), sometimes called experience sampling, is a data collection strategy, not a technology. The defining features, from Shiffman, Stone & Hufford (2008), are momentary (current or recent state, so memory doesn't distort it), ecological (in the patient's real environment, not a clinic), and repeated (many assessments over time, often several a day).

EMA today is usually delivered electronically, which makes most modern EMA a subset of ePRO. The two words still emphasize different things. "ePRO" foregrounds that the instrument is validated and the data is regulator-acceptable. "EMA" foregrounds that you picked a sampling strategy to beat recall bias and capture within-person variability.

Reach for "EMA" when the sampling design is doing real scientific work, like when your Innovation argument is that earlier studies missed something by asking patients to recall a whole week at once. Reach for "ePRO" when you're describing the regulatory pathway or validated electronic delivery. Both can sit in one protocol: validated ePRO instruments on a weekly schedule, plus event-triggered EMA prompts catching symptom intensity in the moment.

RWD is a source classification

Real-world data (RWD) is a category of source, not a measurement method. The FDA's RWE framework defines it as data on patient health or care delivery collected outside traditional RCTs: EHRs, claims, registries, PROs, wearables, mobile health.

Here's the distinction that trips people up. ePRO and EMA describe how you collect. RWD describes what kind of study the data came from. Data from a prospectively planned RCT, even collected through an ePRO app using EMA sampling, generally isn't RWD. It's interventional trial data. The same app dropped into a natural history study or registry produces RWD. The app never changed. The study design did.

Real-world evidence (RWE) is the clinical evidence you derive by analyzing RWD. RWD is the ingredient. RWE is the dish.

How they stack

One concrete example sorts it out:

• A validated questionnaire like PROMIS-29 is a PRO instrument.
• Delivered on a phone, it's ePRO.
• Delivered several times a day in the moment, it's EMA, and still ePRO.
• Collected in a natural history study, the result is RWD.
• A filing that uses that dataset to support a label claim rests on RWE.

One app, one study, four concepts, none interchangeable.

How to use each term in an aims page

1. Don't write "we will use RWD to measure symptoms." RWD isn't a measurement method. You collect ePRO or EMA data that, depending on design, may qualify as RWD.
2. Don't write "EMA will provide validated outcomes." EMA is a sampling strategy. Your instruments still need their own psychometric support. EMA cuts recall error; it doesn't validate anything.
3. Separate study design from delivery. "Real-world ePRO data" smashes a source category and a delivery method together. State the design (interventional or observational) and the delivery (ePRO) on their own.
4. Call EMA prompts "prompts" or "assessments," not "surveys." A handful of items in under two minutes isn't a survey, and "survey" inflates the burden a reviewer pictures. (See survey fatigue.)

This is also where Forma fits. We don't replace your validated instrument, we administer the one your field already trusts and wrap continuous real-world data around it: daily logs, wearables, automatic location-linked context, patient-submitted media. Validated instrument plus. The instrument carries the regulatory weight. The surrounding stream carries the variability a quarterly clinic visit never sees. Name each layer for what it is and your Approach reads like someone who's run this before.