A patient who finds a daily eDiary confusing or time-consuming doesn't usually complain they just stop completing it consistently, or drop out of the study altogether. Compliance and retention data often gets analyzed after the fact, but the root cause frequently traces back to specific, avoidable design choices made in how the ePRO instrument itself was built. Here are six that actually matter.
A daily assessment that takes patients ten minutes when it was designed to take two creates real fatigue over a multi-month study. Testing actual completion time with representative patients before finalizing an instrument catches this gap before it affects retention at scale.
Complex or ambiguous question wording forces patients to re-read and second-guess responses, adding friction to every single entry. Plain, direct language tested with actual patients not just clinicians reduces this friction meaningfully.
A reminder that arrives during a patient's workday or sleep hours gets ignored or resented. Reminder timing that can be configured around patient-reported routine, within protocol-allowed windows, improves genuine compliance rather than just technical delivery.
Many patients only interact with the ePRO instrument on a mobile device. An interface genuinely designed for mobile — not a desktop form technically viewable on a phone — reduces the friction of small text, awkward scrolling, and misclicks that erode compliance over time.
Uncertainty about whether an entry actually saved creates anxiety and sometimes duplicate entries. Clear, immediate confirmation removes that uncertainty and builds patient confidence in the tool over the study duration.
Assessments added to an ePRO instrument after initial design even individually reasonable additions accumulate burden the same way added visit assessments do. Each addition should be weighed against total patient burden, not just its own individual justification.
| Design Choice | High Burden | Low Burden |
|---|---|---|
| Entry time | Untested, longer than intended | Tested against actual patient completion time |
| Question wording | Complex, ambiguous | Plain, tested with patients |
| Reminder timing | Fixed regardless of routine | Configurable around patient schedule |
| Interface | Desktop form on mobile | Genuinely mobile-first |
| Confirmation | Unclear if entry saved | Immediate, clear confirmation |
| Scope | Accumulates additions over time | Weighed against total burden |
ICH E6(R3) places patient centricity among its core principles, and patient-reported data quality depends directly on sustained, genuine engagement rather than compliance achieved through reminders alone. Burden that drives dropout or inconsistent completion undermines the data quality the instrument was designed to capture in the first place.
Cloudbyz's ePRO/eCOA solution is built mobile-first, with configurable reminder timing designed to work around patient routines rather than a single fixed schedule. Because it's connected to EDC on the same platform, compliance data is visible in context alongside broader study data, supporting earlier identification of burden-driven compliance issues.
See how Cloudbyz's ePRO/eCOA platform is designed around patient burden — book a demo with your own instrument design.