activity)

Data Being Collected: Clearly state which types of data (e.g., HR, SpO₂, motion, temperature) will be recorded

Duration and Frequency: Describe how often and for how long the wearable will collect data

Who Will Access the Data: Indicate if investigators, sponsors, monitors, or third-party vendors will review the data

Risk Disclosure: Address possible physical risks (e.g., skin irritation), privacy risks, or emotional discomfort

Withdrawal Rights: Affirm that participants can stop using the wearable without penalty

Sample Language for Key Consent Sections

Below is a sample template of consent language suitable for wearable use:

“You will be asked to wear a wrist-based device that records your heart rate, activity levels, and sleep patterns. The device will collect this data continuously during the study. These data will be used to assess your overall health and study-related outcomes. The device does not provide real-time medical alerts and should not be used for diagnosis or treatment decisions. Your data will be encrypted and transmitted securely to a central database accessed only by authorized study personnel.”

Consider breaking longer sections into bullet points or FAQs to aid comprehension, particularly in eConsent interfaces.

Data Privacy and Participant Rights

Since wearables generate high-frequency personal health data, ICFs must include clear privacy language:

• Data Storage: Clarify whether data is stored on the device, phone app, or cloud
• Retention Period: Indicate how long data will be stored post-study
• De-Identification: Describe measures to anonymize or pseudonymize subject data
• Access Rights: Specify whether participants can review or request deletion of their data
• Regulatory Disclosure: Include that data may be reviewed by the FDA or other authorities

You may reference FDA’s guidance on eSource and DHT for more detailed regulatory expectations.

eConsent Integration and Multimedia Enhancements

When consent is obtained electronically, sponsors and CROs must ensure that the wearable information is clearly presented and understood through:

• Interactive Walkthroughs: Demonstrate wearable usage with animations or videos
• Device Simulators: Let participants virtually “test” device interfaces
• Pop-up Definitions: Explain technical terms like “biometric,” “data sync,” or “signal drop”
• Multilingual Translations: Ensure all materials are culturally and linguistically appropriate

All content must be version-controlled and Part 11 compliant. Consider integrating modules from platforms like PharmaValidation for audit-ready templates.

Assessing Participant Understanding

To meet ethical and regulatory standards, comprehension of wearable-related consent content must be verified. Sponsors can:

• Include quizzes at the end of each consent section
• Use teach-back methods during site visits or onboarding calls
• Track time spent on wearable-specific sections
• Flag inconsistent answers or skipped sections in the eConsent backend

Documentation of comprehension checks must be archived for IRB and regulatory review.

IRB/IEC Review and Approval Best Practices

IRBs often request revisions or clarifications in wearable language. Common feedback includes:

• Too much technical jargon—e.g., “photoplethysmography” vs “pulse sensor”
• Missing clarity on continuous data capture and potential privacy risks
• Lack of explanation about what happens if the wearable is lost or broken
• Ambiguity in data retention and data sharing with third-party cloud vendors

Submit a wearable-specific FAQ appendix alongside the ICF, or include a separate “Digital Tools Addendum” for faster IRB review.

Real-World Case Example: eConsent for a Sleep Trial

A decentralized clinical trial used a wearable ring to track sleep and HRV for anxiety treatment assessment. IRB feedback led to the following improvements:

• Added an animated tutorial for device placement and Bluetooth syncing
• Revised “data access” section to specify that sponsors would not view raw PII
• Explained that no clinical feedback or diagnostic alerts would be generated
• Included a helpline number in case of device malfunction or non-compliance

These changes led to faster IRB re-approval and reduced protocol deviations due to wearable misuse.

Template Checklist for Wearable-Specific Consent Language

• [ ] Purpose of wearable usage explained in lay language
• [ ] Specific signals/data types collected are listed
• [ ] Duration, wear instructions, and use expectations provided
• [ ] Risks, discomforts, and privacy limitations addressed
• [ ] Withdrawal procedures and device return explained
• [ ] Device troubleshooting and training resources shared
• [ ] Data access, sharing, and cloud storage disclosed
• [ ] IRB-required disclaimers and contacts included

Conclusion: Transparency and Trust Through Better Consent

Wearables provide enormous promise in clinical research—but only when participants fully understand what participation entails. Well-drafted informed consent language builds transparency, protects participants, and ensures trial compliance with GCP, IRB, and privacy standards.

By integrating clear, visual, and participant-friendly language on wearable use, sponsors and CROs can foster trust and support ethical, audit-ready trial execution.