A patient story can make participation understandable. It can also make one experience feel universal. The difference is design and disclosure.

The direct answer

Patient stories should be used to explain lived experience, not imply safety, efficacy, or a typical outcome. Ethical stories are voluntary, representative, contextualized, balanced about difficulty and uncertainty, and paired with factual study information and a clear reminder that experiences vary.

Stories make abstract participation concrete.

A visit schedule is a table. A patient describing the early train, childcare handoff, infusion day, and recovery period turns that schedule into lived reality. Narrative can help prospective participants imagine questions that formal materials do not naturally surface.

That power is useful when it increases comprehension. It becomes risky when emotional identification substitutes for evidence. A compelling account can be remembered more easily than base rates, study limitations, or the fact that another patient's outcome may not apply.

Social proof can normalize questions or manufacture confidence.

Hearing from peers may reduce isolation and show that uncertainty is normal. It can also suggest that participation is safe, expected, or successful simply because someone similar chose it. Similarity is not evidence of an individual's likely result.

The ethical objective is not to make participation appear popular. It is to make the decision more imaginable and the questions more informed. Stories should include doubt, burden, support, and unresolved uncertainty rather than presenting a frictionless conversion narrative.

Build guardrails before collecting the story.

Patients need clear consent for how their account, image, health information, and words will be used. They should understand the audience, channels, duration, editing process, and whether they can withdraw future use. Compensation, if any, should be transparent.

Editorial review should check representativeness, factual context, balance, accessibility, and implied claims. Stories should never promise benefit, minimize risk, or suggest that a person's experience is typical. Composite or dramatized content must be labeled clearly.

Pair narrative with the information needed to decide.

A story can introduce a topic, but the patient still needs protocol-specific facts about purpose, procedures, alternatives, uncertainty, privacy, burden, cost, and support. Narrative and evidence should work together rather than compete for attention.

The strongest use of lived experience is often co-design. Patients and caregivers can help teams identify missing questions, unrealistic assumptions, and language that fails to match real life. Their stories then improve the system, not just the campaign.

Sources.

  1. FDA, Patient-Focused Drug Development Guidance Series
  2. HHS OHRP, The Belmont Report
  3. CTTI, Patient Group Engagement Recommendations
  4. ClinicalTrials.gov, How to Read Study Results
Rebecca Schelkun, Vice President, Patient Readiness at Jumo Health

About the author

Rebecca Schelkun

Vice President, Patient Readiness

Rebecca is Vice President of Patient Readiness at Jumo Health. She combines public health expertise in epidemiology and biostatistics with experience across health equity, patient advocacy, pediatrics, rare disease, and clinical trial strategy. At Jumo, she turns protocol demands and lived experience into education, decision support, and expectation alignment patients can use.

Next in Patient Activation in Practice

Transparency Must Include the Hard Parts. →