Remote Monitoring Can Reduce Trial Visits. It Also Creates a New Patient Workload.

A promising claim about remote patient monitoring in clinical trials is also the one that deserves the most scrutiny: fewer journeys to a research site can mean a less burdensome study.

That can be true. A newly published framework on remote monitoring points to the scope for collecting many trial assessments at home, potentially reducing physical visits while giving clinicians a more timely view of symptoms and treatment side effects. For people managing cancer treatment, that prospect has obvious appeal.

But moving an assessment out of the clinic does not make it disappear. It changes who performs the work, when it happens and what can go wrong. The participant may now need to charge a device, understand a prompt, complete a questionnaire, take a photograph, respond to an alert, troubleshoot an app and decide whether a worrying symptom requires contact with the site. The clinical team, meanwhile, needs a clear route from incoming data to an appropriate response.

For sponsors and health-tech suppliers, this is more than an implementation detail. It is a question of research quality. If a digital layer is confusing, demanding or detached from the care experience, it can weaken retention, widen the gap between participants and produce data that look complete on a dashboard while being uneven in meaning.

A decentralised trial succeeds when it removes patient effort rather than simply relocating it.

The useful comparison is not digital versus in-person

The current debate can be too binary. Site-based trials are often portrayed as traditional and inconvenient, while remote methods are framed as inherently patient-centred. Neither description is reliable on its own.

An in-person appointment may require travel, time away from work, childcare or physical exertion at a difficult point in treatment. A well-designed remote check-in can reduce those costs and surface problems between visits rather than waiting for a scheduled consultation. In the right setting, it may improve the quality of symptom reporting because patients record an experience closer to when it occurred.

Yet a remote process can also ask more of people who have the least spare capacity. Digital confidence, language, disability, access to a suitable phone or reliable connection, and the fluctuating effects of illness all affect whether a participant can take part comfortably. A protocol designed around a confident smartphone user may therefore increase convenience for some while making the study less representative for others.

The important design question is not, “Can this assessment be completed remotely?” It is, “For whom does remote completion make participation easier, and for whom does it add a fresh obstacle?”

That distinction matters commercially as well as ethically. Recruitment claims based on broader reach will not stand if the trial silently filters out people unable or unwilling to manage its digital routine. The value of a more geographically flexible study rests on sustained participation, not on an attractive recruitment funnel.

Treat the monitoring journey as part of the protocol

The recent framework is strongest where it treats remote monitoring as a combination of measurement science, clinical relevance and user experience. That should be the starting point for any trial team.

First, define the specific decision that the data are meant to improve. A daily prompt is not justified because a platform can send one. It needs to help identify a clinically meaningful change, support a timely intervention, establish adherence or produce an outcome measure that conventional visits cannot capture well enough. More data are not automatically better data, especially when staff have to interpret them.

Second, test the real task rather than merely the interface. A usability session in which a participant clicks through a prototype is useful, but it is not the same as asking someone who feels unwell to complete a symptom log for the sixth consecutive day. Teams should observe how people understand questions, where they pause, what they do when an instruction is unclear and whether the promised benefit is visible to them. The experience includes device delivery, onboarding, helpline support and what happens after a concerning result is submitted.

Third, make the response model explicit. Patients should not be asked to report symptoms in near real time if they cannot understand when, or whether, a person will review them. Site teams need thresholds that distinguish information for routine review from information requiring action. They also need a manageable volume of alerts and a named owner for the next step. Otherwise, monitoring risks becoming a new administrative burden layered onto an already stretched research operation.

This is where patient experience and staff experience meet. A reassuring service is one that makes the path from reporting to response intelligible to both sides.

Patient-owned devices bring reach and volatility

Using participants’ own smartphones can reduce the need to distribute dedicated equipment and may feel more familiar than issuing an additional device. It can also make trials more practical across multiple sites and countries.

However, the approach imports the instability of consumer technology into a tightly controlled research environment. A recent cancer-survivorship trial using passive sensing on personal Android phones documented problems including changing operating-system permissions, dependencies on third-party services and the need to maintain software during the study. These are not peripheral technical snags. They affect continuity of data collection, comparability over time and the practical workload placed on participants and study teams.

The implication is not that bring-your-own-device approaches should be avoided. It is that the technology estate should be treated as a live part of trial design. Sponsors need contingency plans for software changes, clear minimum device requirements, alternatives for people who do not meet them, and a decision process for when an update may compromise a measure.

This is familiar territory in product design: the customer journey cannot be separated from the service infrastructure behind it. Clinical research needs the same discipline. A patient-facing app is only as reliable as the support, data flow and clinical workflow surrounding it.

Evidence needs to include effort

The commercial environment is becoming less tolerant of digital-health propositions built on engagement claims alone. Recent purchaser research in the United States found that weak patient engagement is a leading reason organisations change digital-health suppliers, while more purchasers tie payment to clinical and financial performance.

Clinical trials are not consumer subscriptions, and sponsors should be wary of importing simplistic engagement metrics. Still, the underlying lesson applies. Completion rates by themselves do not reveal whether a digital process is acceptable, equitable or clinically useful. Participants may comply because they value the trial, because staff repeatedly chase them, or because they do not want to disappoint their care team.

A better evaluation asks several questions together: Did the technology reduce travel or waiting? Did it lead to earlier or more useful clinical action? Which participants required extra support? Where did data go missing, and why? Did sites gain a clearer view of patient status, or simply another stream to manage?

Remote monitoring has a valuable role in making research more responsive to patients’ lives. But its advantage will not come from turning every symptom, behaviour or device signal into a data point. It will come from selecting the moments where digital contact replaces avoidable effort with meaningful support — and from proving that the resulting evidence is better for patients, sites and the decisions a trial is meant to inform.