Digital health technologies can reduce visit burden and collect remote data, but weak participant onboarding can turn device setup, connectivity, and missing data into recruitment and retention problems.
In this guide
Key points
- Participant onboarding should explain what the device or app collects, how often it is used, what support is available, and what happens when data is missing.
- Technical friction should be tracked as an operational blocker, not automatically treated as participant noncompliance.
- TrialsNest can help sites keep device readiness, coordinator outreach, missed setup steps, and follow-up tasks visible.
Remote data still needs an operating model
Digital health technologies can reduce visit burden and capture data remotely, but only if participants can use them consistently. A device or app that looks simple in a vendor demo can become a recruitment and retention problem if onboarding is weak.
FDA's final guidance on Digital Health Technologies for Remote Data Acquisition in Clinical Investigations provides recommendations for using DHTs to collect remote data from participants in medical product clinical investigations.
Build onboarding around the participant
Participant onboarding should explain what the device or app collects, when and how often it should be used, whether charging or connectivity is required, and who handles technical questions.
The team should also define what happens if data is missing, whether setup should be tested before relying on remote data, and how privacy and data-use language will be explained in patient-facing terms.
Case-study example
A study uses a wearable to collect activity data but does not confirm whether participants can charge it, sync it, or wear it during normal routines. Missing data later appears as noncompliance, but the root cause may be onboarding and support.
A stronger workflow would verify setup, document readiness, name the technical support path, and give coordinators a clear status for device not received, setup incomplete, syncing issue, participant question, or data missing.
Where TrialsNest fits
TrialsNest can support the operational layer by keeping device readiness, coordinator outreach, missed setup steps, and follow-up tasks visible. That helps sites separate patient burden from technical friction.
The platform should not imply that remote monitoring replaces medical care. Patient-facing language should keep remote data collection, study-team review, and regular medical care clearly separated.
Sources used for this checklist
FDA Digital Health Technologies for Remote Data Acquisition guidance: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/digital-health-technologies-remote-data-acquisition-clinical-investigations
FDA Digital Health Technologies for drug development: https://www.fda.gov/science-research/science-and-research-special-topics/digital-health-technologies-dhts-drug-development
Sources and editorial notes
Published .
This guide explains recruitment work and questions to discuss with your team.
This information is educational. Your study team makes medical, eligibility, and enrollment decisions.
See TrialsNest in action
Bring this workflow into one place.
Manage inquiries, follow-ups, records, and visits. Keep sponsors updated on progress.
Coordinator Today
Your inquiries, priorities, and upcoming visits.
- Inquiries assigned
- 14 3 pending review
- Visits today
- 6 4 in person · 2 virtual
- Action priorities
- 4 Needs attention
- Active studies
- 3 Study A · B · C
Priority tasks
- Review screening intakeInquiry 001 · Study ACompleted
- Verify specimen preparationStudy A · Due 10:00 AMCompleted
- Confirm visit windowInquiry 003 · Follow-upPending
Upcoming visits
- In personInquiry 001
Study A · Baseline visit
View visit details → - TelehealthInquiry 003
Study A · Prescreen
Review appointment → - In personInquiry 004
Study B · Week 4
View visit details →
Keep reading
Patient-reported outcomes: collection checklist for trial teams
A clinical operations checklist for collecting patient-reported outcomes with clear purpose, accessible tools, mobile support, and lower participant burden.
How research sites can reduce clinical trial screening no-shows
Operational steps research sites can use to reduce screening no-shows through clearer expectations, reminders, records readiness, and patient-friendly follow-up.
Clinical trial recruitment software resources
Resources for teams comparing clinical trial recruitment software, patient recruitment software, dashboards, workflow coverage, implementation plans, and ROI.
Patient recruitment automation with human review in clinical trials
Automation can reduce administrative friction in clinical trial recruitment, but it should support human review. The right model organizes work, reminders, records, and reporting while keeping final decisions with authorized study teams.
