Published on 22/12/2025
How to Design Monitoring Plans for Continuous Wearable Data in Clinical Trials
Introduction: Why Monitoring Wearable Data Requires a New Approach
Traditional monitoring strategies in clinical trials focus on periodic review of static data—case report forms (CRFs), lab values, and visit summaries. However, wearable technologies introduce continuous, high-frequency data streams that require entirely different oversight models.
Wearable sensors may collect data every second or minute, including heart rate, movement, sleep, or vital signs, generating gigabytes of data per subject. Regulatory agencies now expect sponsors to define and implement fit-for-purpose monitoring plans that ensure GCP compliance, subject safety, and data quality.
Regulatory Guidance on Digital Health Monitoring
The FDA and EMA have acknowledged that real-time and remote monitoring of wearable-derived data needs dedicated planning. According to the FDA’s 2023 DHT Guidance:
“The sponsor is responsible for ongoing review of data generated by digital health technologies for safety signals,
Similarly, the EMA emphasizes that risk-based monitoring strategies must be adapted to new modalities such as wearables and eSource. This includes automated signal detection, missing data reports, and sensor performance monitoring.
Core Components of a Wearable Monitoring Plan
An effective monitoring plan for wearable data should address the following:
- Signal Quality Monitoring: Detect dropouts, sensor noise, low battery alerts
- Compliance Tracking: Detect subjects not wearing the device as instructed
- Endpoint Data Monitoring: Track derived endpoints (e.g., daily step count, HRV) over time
- Alert Handling: Real-time notifications for clinical anomalies (e.g., abnormal heart rate)
- Data Transmission Monitoring: Ensure data uploads are timely and complete
These components should be reflected in the study’s Monitoring Plan document and referenced in the Protocol and Statistical Analysis Plan (SAP).
Tools for Real-Time Oversight and Trend Monitoring
CROs and sponsors must use fit-for-purpose tools and dashboards to visualize and track wearable data in near real-time. Essential features include:
- Subject-level dashboards for compliance (e.g., % hours worn)
- Site-level summary of data availability and dropout rates
- Threshold alerts for abnormal readings (e.g., SpO₂ < 90%)
- Visualization of trends over time (e.g., mobility degradation)
- Audit trail of alert reviews and resolutions
Integration with the eCRF and eTMF ensures traceability of review activities. Dashboards may be built internally or procured from validated digital health vendors.
Risk-Based Categorization of Monitoring Activities
Monitoring intensity should align with the device’s role in the study:
- Primary Endpoint Devices: Require continuous oversight, predefined alert thresholds, and full audit trail
- Secondary Endpoint Devices: Periodic trend analysis and batch-level review may suffice
- Exploratory Devices: May not require full monitoring but should still have a data completeness log
These categories help CROs allocate monitoring resources and justify oversight in the trial’s Risk Assessment document.
Deviation Management for Wearable-Generated Data
Wearable-specific deviations must be captured, tracked, and reported consistently. Common deviations include:
- Subject non-compliance (device not worn for >4 hours/day)
- Sensor failure (e.g., data loss due to Bluetooth sync issues)
- Data anomaly (implausible step count or HR spike)
Each deviation should be:
- Logged in a centralized deviation tracker
- Assessed for impact on primary/secondary endpoints
- Investigated by site/CRO with documentation of root cause
- Linked to subject profile in the eTMF and reported in the Clinical Study Report (CSR) if relevant
Example Monitoring Matrix
| Data Stream | Monitoring Frequency | Monitoring Type | Responsible Party |
|---|---|---|---|
| Heart Rate | Daily | Automated Alerts + Weekly Trending | Clinical Safety Monitor |
| Sleep Duration | Weekly | Trend Monitoring | Data Scientist |
| Device Wear Time | Daily | Compliance Report | CRA |
Case Study: Remote Monitoring of a COPD Trial
In a Phase 2 COPD trial, subjects used a wearable oximeter to transmit SpO₂ data twice daily. The CRO designed an automated monitoring system with the following features:
- Threshold alerts for SpO₂ below 89%
- SMS alerts to investigators when 3 consecutive low readings occurred
- Central dashboard tracking daily compliance rates by site
- Weekly report to DSMB summarizing data completeness and alerts
During inspection, FDA auditors praised the sponsor for real-time escalation processes and linked SOPs covering wearable data review.
Best Practices for Implementing Wearable Monitoring Plans
- [ ] Define all data streams and expected frequency
- [ ] Establish monitoring roles and responsibilities
- [ ] Implement alert thresholds and triage workflows
- [ ] Create training materials for site teams on wearable deviations
- [ ] Link monitoring documentation to the TMF (Section 06.03.02)
- [ ] Document system validations for dashboards and alert logic
- [ ] Plan periodic reviews for monitoring plan effectiveness
Conclusion: Future-Proofing Clinical Trial Oversight
Wearables offer transformative opportunities for data collection in clinical research, but they also require a paradigm shift in monitoring strategy. Real-time, proactive, and automated oversight is essential to uphold subject safety and data integrity.
Sponsors and CROs must adopt tailored monitoring plans that reflect the nuances of continuous data streams while aligning with evolving global regulatory expectations. Visit PharmaSOP for ready-to-deploy SOP templates for DHT monitoring workflows, and explore global frameworks via the EMA.