Skip to content

PROM collection & automation: fixing the 70% drop-off problem

AnyHealth.AI team · 5 July 2026 · 9 min read

Patient-Reported Outcome Measures are the backbone of every value-based healthcare platform: they are how you prove that surgery, physiotherapy or a care programme actually made patients better. They are also operationally fragile. Across post-operative programmes, roughly 70% of patients stop responding by the month 3–6 timepoints - exactly when the data matters most.

The problem is worse than missing data

Non-response is not random. The patients who stop answering are disproportionately the ones doing poorly - in pain, discouraged, or disengaged from their care. So a PROM dataset with 30% capture isn’t just sparse; it is biased toward good outcomes. A biased 80% capture rate should be treated as a failure, not a win. Any serious PROM collection programme has to target two numbers: the capture rate and the bias gap between good-outcome and poor-outcome responders.

Why traditional PROM software fails

  • One-size-fits-all delivery - the same email survey link for a motivated marathon runner and an overwhelmed 78-year-old.
  • Clinical, cold framing - patients in pain drop out of forms that feel like paperwork.
  • Wrong channel - portal logins and email links create friction at exactly the wrong moment.
  • No recovery path - when a patient goes quiet, most systems just… stop.

The adaptive approach: same instrument, adaptive delivery

Our PROM engagement layer (Aria) keeps the clinical instrument constant - a validated questionnaire like KOOS-12 at every milestone - but adapts everything about the delivery on WhatsApp:

  • Behaviour personas. Each patient carries a predicted mix (e.g. 50% detail-oriented coach, 40% needs emotional framing, 10% time-poor micro-survey). Delivery starts with the most likely persona.
  • Automatic persona switching. If engagement drops mid-flow, the system re-frames in the next persona’s tone instead of losing the patient - and escalates to a human nurse call as the final backstop.
  • Conversational, one-question-at-a-time flow - with time estimates upfront and critical items first, so partial completions still capture what matters clinically.
  • Two-day splits. A patient who can’t finish today politely resumes tomorrow, rather than being marked non-responsive.
  • Value back to the patient. Recovery trends, milestone celebrations and a pre-op “time capsule” unsealed as progress rewards - reasons to keep answering.

Targets that keep programmes honest

We hold PROM automation to: ≥80% critical-item capture at months 3 and 6 (versus ~30% baselines), a non-response bias gap of ≤10 points between good and poor outcome groups, and ≥80% first-message reply at week 1. Digital patient follow-up that hits those numbers feeds honest data to clinicians, registries and value-based contracts.

Where this fits in your stack

PROM automation shouldn’t be an island. It rides the same WhatsApp relationship as appointment reminders, medication adherence and remote patient engagement - one assistant, one conversation thread, one patient record synced to your EMR. That continuity is why patients keep responding: the same “person” who booked their surgery is the one asking how their knee feels.

Running an outcomes programme and losing patients at month 3? Email us or book a demo - we’ll show Aria adapting to a disengaging patient live.

Capture the outcomes you’re missing

See adaptive PROM delivery in action.

Book a demo