Risk-Based Monitoring and Device Telemetry in Decentralised Trials
Why the device is a monitorable data source — and why its telemetry belongs in the risk-based monitoring plan, not outside it
REGULATORY OPERATIONSIn a decentralized trial the device is both a risk to the data and the richest source of monitoring signal — its telemetry belongs inside the monitoring plan.
Uptime, sync, completeness, sensor health, version drift and capture timing are all observable continuously; none is monitoring until someone owns the indicator and a breach has somewhere to go. Name the device risks, give each an owned indicator with a pre-specified range, and wire every breach to action.
Six device indicators: none is monitoring until it is owned and routed
Risk: non-use and data loss. An absent signal is ambiguous — failure or non-use — and the plan resolves it.
Risk: data stranded on the device or its relay. Drives reconciliation before lock.
Risk: capture below schedule. Drives query activity in data management.
Risk: drift or fault. Where the DHT is a medical device, may be a device deficiency or reportable incident.
Risk: validated-state drift. Routes to the Trigger Register and change control as the early warning.
Risk: adherence. Tells the study when, not only whether, the participant captured.
Telemetry is monitoring only as an owned indicator with a routed action
ICH E6(R3) requires monitoring whose extent and nature follow the identified risks (s.3.11.4); nothing in it excludes the device that generates the data.
A connected device yields a continuous, time-stamped record of its own operation — continuous rather than sampled, contemporaneous rather than reconstructed — that a site visit never could.
Telemetry is silent when a device is off or suspended; a participant's own handset narrows collection; central review can unblind; the analytics are a validated computerized system.
Version drift goes to the Trigger Register and change control; sensor-health signals to vigilance where the DHT is a device; completeness and sync to data management before lock.
Five steps, from device risk to routed signal
- 1Identify device-side risks — which device behaviors threaten safety or data reliability in this decentralized setup.
- 2Define the indicators — turn each risk into a named indicator with an owner and a data definition.
- 3Instrument the telemetry — capture uptime, sync, completeness, sensor health and version data in a controlled, traceable way.
- 4Set acceptable ranges and actions — pre-specify the range for each indicator from this study's risks, and the action a breach triggers.
- 5Feed the register and lifecycle — route signals into the Trigger Register (QPP-08), change control (QPP-07) and vigilance (QPP-18).
ICH E6(R3) s.3.10, 3.10.1, 3.10.1.3, 3.11.4; Annex 2 (Step 4, 3 June 2026) · FDA risk-based monitoring guidance (2013) and Q&A guidance (2023) · EMA/INS/GCP/112288/2023 · HMA/EC/EMA Recommendation paper, Version 02
© qointa 2026 – Public – Uncontrolled when printed · Not legal advice; this summary does not classify any device.
sales@qointa.com · qointa.com
More from the library
Digital Health Technologies in Clinical Trials — A Regulatory Position-Paper Series
One device, several perimeters: a framework for assessing the regulatory impact of the technologies a trial relies on.
Read more →Who Is the Manufacturer? Economic-Operator Roles in DHT Supply Chains
How provisioning, importing, kitting and modifying a device assign manufacturer, importer and distributor duties — often by operation of law.
Read more →You Can Delegate the Work, Not the Accountability: Vendor Qualification and Oversight under ICH E6(R3)
The sponsor’s duty to qualify and oversee its DHT vendors — distinct from who holds the economic-operator role.
Read more →Talk to a specialist
Bring one device and one protocol — a wearable, a sensor, an app, anything. We will tell you which regulatory perimeters it opens and what it takes to close them.
Book a 15-minute call