Operationalizing the Patient Voice: Converging U.S., EU, and UK Requirements and the Role of Real-World Patient-Reported Data

During the past decade, the FDA has moved patient input from the periphery of drug development toward its methodological core.

What began as a directive in the 21st Century Cures Act (2016) is now a four-part guidance series specifying, in operational detail, whom to collect patient experience data from, how to identify what matters to those patients, how to translate that into a clinical outcome assessment (COA), and how to qualify that assessment as a regulatory endpoint. Three of the four guidances are final.

Comparable expectations are emerging in the EU and UK through separate instruments. For organizations that already hold structured, longitudinal, patient-reported data at scale, this convergence is an opportunity; for sponsors beginning from a single advisory board or a small set of interviews, it is a widening gap.

The FDA PFDD guidance series

The 21st Century Cures Act directed the FDA to develop strategies for soliciting patients' perspectives during medical product development and to factor those perspectives into regulatory decisions. Successive Prescription Drug User Fee Act reauthorizations provided the delivery mechanism: a Patient-Focused Drug Development initiative organized around four methodological guidance documents, each addressing a different link in the chain from patient experience to regulatory decision (Table 1).

Read together, the series describes a single pipeline:

• Identify a representative population (Guidance 1).
• Determine what matters to that population (Guidance 2).
• Select or develop a measurement tool that captures it (Guidance 3).
• Qualify that tool as an endpoint on which the agency can rely (Guidance 4).

The direction of travel is consistent — regulators expect patient experience data to meet the same standard of rigor as any other source of clinical evidence, rather than treating it as a qualitative supplement. Adjacent FDA activity reinforces the trajectory.

In March 2026, the agency finalized updated guidance on incorporating voluntary patient preference information across a device's total product life cycle. That same month, the FDA's Center for Drug Evaluation and Research (CDER) and Center for Biologics Evaluation and Research (CBER) issued a Federal Register request for information on the use of digital health technologies in clinical investigations — an indication that patient-generated data captured outside the clinical setting is now within scope.

Patient-focused drug development is also anticipated to feature in the PDUFA VIII reauthorization.

Parallel developments in the EU and UK

The FDA is not acting in isolation. During a comparable period, the EU and UK have each established mechanisms that make patient input a documented and defensible part of the regulatory record, not a single mandate, but three instruments oriented in the same direction (Table 2).

The International Council for Harmonisation's ICH E6(R3), the globally harmonized Good Clinical Practice guideline, is the clearest structural parallel to PFDD. It asks sponsors to engage stakeholders, including patients, during protocol development, and to identify the critical-to-quality factors on which a trial depends using a quality-by-design approach that presupposes some prior determination of what matters to the people enrolling.

ICH E6(R3) became a legal requirement for UK trials on 28 April 2026, alongside the most substantial reform of UK clinical-trials regulation in two decades. For the first time, that reform makes it a statutory requirement to involve people with relevant lived experience in a trial's design, management, conduct, and dissemination, and to offer participants a lay summary of results.

The EU's HTA Regulation introduces a second, downstream instrument. Joint Scientific Consultations and Joint Clinical Assessments — in force since January 2025 for oncology medicines and advanced therapy medicinal products, and expanding to further categories through 2030 — formally incorporate patient input into the EU-level clinical assessment that informs national reimbursement decisions. The EMA's reflection paper on patient experience data adds a methodological layer, recommending qualitative work to identify what matters followed by quantitative work to measure it at scale, a sequence that maps closely onto the first two PFDD guidances.

The common thread across all three jurisdictions is consistent: patient input must be documented, sized, and defensible, rather than asserted.

Common operational gaps

The guidance is explicit about the standard; meeting it in practice is more difficult. Three gaps recur across clinical and HEOR teams:

Representativeness (Guidance 1). Advisory boards, patient councils, and single-site interview cohorts are convenient but rarely representative of the population a trial enrolls and often skewed by geography, disease severity, access to specialty care, and willingness to volunteer.

Concept identification (Guidance 2). Programs frequently begin from clinician assumptions about which symptoms or impacts are most burdensome and then validate them with a small qualitative sample; a sequence Guidance 2 explicitly cautions against, because it leads rather than elicits.

Endpoint defensibility (Guidances 3 and 4). A COA is fit-for-purpose only if its content can be traced to what patients themselves identify as meaningful. An instrument assembled first and justified afterward is vulnerable under regulatory scrutiny.

The contribution and limits of patient-reported real-world data

A distinct category of real-world data is built to capture the layer this guidance addresses: large-scale, structured, patient-reported symptom burden and treatment response as the patient perceives and rates it. This differs materially from electronic health record (EHR) and claims data.

Claims and EHR data remain the stronger sources for utilization, adherence, and safety at population scale; however, those sources filtered out the patient's subjective experience by design once the encounter became a code. Patient-reported data is one of the few real-world sources that retains it.

The two data types are therefore complementary rather than competing. Used appropriately, a large patient-reported dataset is most valuable early and in parallel with the guidance's required steps, not as a substitute for them. Specifically, sponsors can:

Use large-scale symptom and severity data to prioritize which concepts to explore in Guidance 2 concept-elicitation interviews, rather than starting from clinician intuition alone.

Use effectiveness-by-treatment patterns to flag candidate COA domains for validation, and to identify instances in which a planned endpoint may omit an outcome patients consistently report as meaningful.

Use demographic and comorbidity breakdowns to assess whether a planned advisory-board or interview cohort under-represents identifiable subgroups before Guidance 1 fieldwork begins.

The limits warrant equal emphasis, because with regulators and experienced reviewers the explicit statement of those limits is what qualifies a source for inclusion. Patient-reported platform data are self-reported and self-selected.

Contributors are not randomly sampled from the disease population; they are individuals motivated to seek out and share treatment experiences, which skews toward particular severities, ages, and levels of health engagement. Sponsors should report any effectiveness signal with its sample size and, where available, a confidence interval, and should flag or suppress cells below a reasonable minimum-sample threshold rather than present them at face value.

A jurisdiction-specific caveat also applies: a cohort assembled on a US-centric platform may not carry the geographic, linguistic, or health-system composition that an EU member state or National Health Service–based trial must represent. Sponsors should therefore check cohort composition against the population the submission covers and supplement it with local fieldwork when the fit is thin.

Accordingly, patient-reported real-world data should be treated as any other real-world data source would be: valuable for generating and prioritizing hypotheses, and explicitly out of scope for the confirmatory, representative-sampling work the guidance requires downstream. A signal reported with candid caveats about cohort composition and known biases is more defensible than a stronger-sounding claim that cannot withstand scrutiny.

Conclusion

The PFDD guidance series has converted “the patient voice” from an aspiration into a methodology, with three of four guidances final and a fourth in draft. The EU and UK have established parallel expectations of their own, through ICH E6(R3), a new statutory requirement for lived-experience involvement in the UK, and patient input within EU Joint Clinical Assessments.

Across all three jurisdictions, the methodology rewards sponsors who arrive with a well-informed hypothesis about what matters to patients and whom they need to consult, and it affords little latitude to data presented without its limitations. Large-scale, structured, patient-reported data can meaningfully sharpen that hypothesis before the qualitative and psychometric work begins. It cannot, and should not, be expected to perform that work itself.

About the Author

Julie Ross is CEO of StuffThatWorks, a patient-reported real-world data platform spanning chronic conditions. The author's company affiliation is disclosed in the interest of transparency; this article is intended as an analysis of the regulatory landscape.

References

1. US Food and Drug Administration. FDA patient-focused drug development guidance series for enhancing the incorporation of the patient's voice in medical product development and regulatory decision making. fda.gov.
2. US Food and Drug Administration. Patient-focused drug development: selecting, developing, or modifying fit-for-purpose clinical outcome assessments. Final guidance, October 2025.
3. Federal Register. Notices on FDA's March 2026 final guidance on voluntary patient preference information and March 2026 request for information on digital health technologies in clinical investigations.
4. European Medicines Agency. Reflection paper on patient experience data.
5. International Council for Harmonisation. ICH E6(R3) Good Clinical Practice guideline. Final, January 2025.
6. Health Research Authority and Medicines and Healthcare products Regulatory Agency (MHRA). Guidance accompanying the Medicines for Human Use (Clinical Trials) (Amendment) Regulations 2025 (in force 28 April 2026).
7. Regulation (EU) 2021/2282 on health technology assessment.