Patient-reported outcomes: measuring real-world persistence

Tell us about your project

Please reach out to us about your project and see how we can help you accomplish your goals.

We value your privacy and will never share your contact information

Please note that submissions without a valid business email address or business phone number may not receive a timely response

Healthcare Solutions

If you're in healthcare, you owe it to yourself to learn how you can make your everyday business processes more efficient and save money at the same time. We can help in automating many of your routine and repetitive tasks, including Patient Engagement surveys.

Contact us to learn more

Transportation Solutions

If you're in the transportation business, you can automate many of your routine tasks like package notifications, surveys, collection calls and more. Improve your customer satisfaction by extending your service hours without extending your costs.

Connect with us to learn more

What survey numbers hide about interruptions, side effects, and access

Patient-reported outcome (PRO) data is only useful if it reflects what people actually do between visits. A single headline satisfaction score can mask three operational realities: patients stop and restart therapies for cost or side effects, different age groups answer on different channels, and stigma or privacy concerns change who responds at all. Recent reporting that Everyday Health surveyed people using GLP-1 medications is a reminder – if your PRO program treats everyone the same way, you will miss these patterns.

The operational problem matters because interruptions are not a single event – they are a timeline. Each patient has their own clock: when they start, when they miss a refill, when side effects appear, and when a cost barrier prompts a pause. A survey program that cannot track those per-person timelines will measure the loudest voices, not the true patient experience.

What survey numbers often hide

Here’s the thing – an aggregate satisfaction percentage tells you about respondents, not nonrespondents. Programs that rely on one channel, usually web or email, tend to oversample younger, tech-comfortable people and undercount older adults or those with limited English proficiency (LEP). That creates sample bias and can overstate persistence or understate safety concerns.

Beyond bias, two other blind spots are common. First, cycling behavior: many patients go off a medication because of cost, coverage gaps, or temporary side effects, then restart later. Unless your system captures a timestamped interruption and links it to subsequent responses, you cannot quantify persistence. Second, the signal that matters operationally is the early-warning item – an answer that should trigger outreach, a clinician review, or a benefits-navigation conversation. Too many PRO systems collect answers and then park them in a report no one watches.

How to design per-person follow-up that detects interruptions

Design choices that work in practice are straightforward and low-tech: make the workflow per-person, channel-flexible, and conditional. That means each enrolled patient keeps their own schedule for check-ins; reminders go by the channel that person uses and prefers; and certain answers branch to a different follow-up than routine, satisfied responses.

  • Time-based check-ins tied to a patient’s start date – not a calendar batch – so missed refills and pauses show up as gaps.
  • Channel mix that includes voice-first outreach, SMS, and secure messaging so you reach older adults and people without smartphones as well as younger cohorts.
  • Simple branching logic so a report of severe nausea or a missed dose triggers an escalation path – a nurse callback, a secure clinician message, or routing to benefits counseling.

Multilingual delivery and translated open-ended responses matter here. If a large part of your population prefers a language other than English, those responses are the ones that will expose coverage or affordability problems. Plan for that in your outreach from day one; see our notes on multilingual survey delivery for operational questions most programs skip.

When a patient flags side effects, the workflow should do two things: surface the response quickly to a human reviewer, and record the event in a way that links back to the patient’s timeline. That combination is what lets operations spot patterns – for example, whether interruptions cluster at insurance reauthorization points or after dose escalation.

Tradeoffs and the checks operations teams should ask for

There are honest tradeoffs. More frequent check-ins increase detection but risk survey fatigue. A wide channel mix raises complexity. Automated routing can miss nuance. The practical way through is to choose a minimum viable set of checks you can audit:

  • Can the program run per-patient schedules and show who missed a scheduled check-in?
  • Does the system translate or transcribe open-ended comments so one team can review feedback across languages?
  • Is there a clear escalation path defined for specific item responses, and can you see when an escalation was sent and who acknowledged it?

Documentation matters too. Health systems and payers should ask whether the messaging and alerts are stored in an auditable way that a reviewer can point to later. Also confirm the program is designed to support Health Insurance Portability and Accountability Act (HIPAA) expectations for protected health information – not as marketing copy, but as a required posture when routing clinical signals and safety alerts.

Operationally, the most useful first step is a small pilot that tracks cycling events and their causes – cost, side effects, or simple forgetfulness – and ties those events to actions you can take, like benefits navigation outreach or earlier clinical follow-up. For practical guidance on safety-focused outreach, review our piece on patient outreach automation and operational checks for safety.

The honest answer is that a structured, per-person PRO program is less about fancy AI and more about the basics: the right cadence, the right channel, language access, and clear rules for when an answer becomes an operational event. When those elements line up, you turn survey scores into something your clinical and navigation teams can act on.

Related coverage: The Metabolic Revolution: GLP-1s, Obesity and Weight Loss – Everyday Health