Decentralized clinical trials (DCTs) allow trial-related activities to occur remotely, outside traditional clinical sites, using telehealth, local healthcare providers, and direct-to-patient technologies. Electronic informed consent (eConsent) is the digital process that replaces paper consent forms with interactive, multimedia-enabled electronic systems. Together, DCTs and eConsent are reshaping how sponsors enroll participants, collect data, and maintain regulatory compliance under FDA 21 CFR Part 11, ICH E6(R2), and EU CTR 536/2014. The FDA finalized its guidance on conducting clinical trials with decentralized elements in September 2024, providing the clearest regulatory framework to date for these approaches.

Key Takeaways

The FDA's September 2024 final guidance, "Conducting Clinical Trials With Decentralized Elements," provides a thorough framework for DCT implementation.
eConsent uses multimedia (video, quizzes, audio) to improve comprehension and is endorsed by the FDA's 2016 Q&A guidance on electronic informed consent.
All e-signatures in DCT workflows must comply with 21 CFR Part 11 (US), eIDAS (EU), and ICH E6(R2) GCP for audit trails, identity verification, and two-factor authentication.
DCTs can cut enrollment timelines by 30-50% and expand geographic reach, but require rigorous protocol-level planning for data integrity.
HIPAA and GDPR apply simultaneously in multinational trials, requiring careful data residency and privacy architecture.

What Are Decentralized Clinical Trials?

A decentralized clinical trial includes decentralized elements where trial-related activities occur at locations other than traditional sites. The FDA's September 2024 final guidance defines the spectrum: trials can be fully decentralized, with all activity taking place remotely, or partially decentralized (hybrid), where some activities remain at traditional sites while others are conducted remotely.

Decentralized elements include telehealth visits, home visits by local healthcare providers or mobile nurses, direct-to-patient shipment of investigational products, remote safety monitoring through wearables and mobile apps, electronic data capture, and electronic informed consent conducted outside the clinical site. The key regulatory principle is that FDA requirements are the same for trials with decentralized elements and trials without them. The protocol must specify which visits will be remote, which will be in-person, and how data integrity and participant safety will be maintained.

What Is eConsent?

Electronic informed consent (eConsent) refers to the use of electronic systems and digital media to convey trial information to participants and document their consent. The FDA and the Office for Human Research Protections (OHRP) issued joint guidance in 2016 titled "Use of Electronic Informed Consent in Clinical Investigations — Questions and Answers," which remains the primary US regulatory framework for eConsent.

Unlike simply digitizing a paper form into a PDF, eConsent can incorporate embedded videos explaining procedures and risks, interactive comprehension quizzes, audio narration for accessibility, hyperlinks to supplemental information, and electronic signature capture with identity verification. The FDA guidance clarifies that eConsent must present all required elements of informed consent under 21 CFR 50.25, allow adequate time for participants to ask questions, provide a copy of the signed document, and maintain a complete audit trail of every interaction with the consent materials.

Why DCTs Are Growing

The decentralized clinical trials market reached roughly $9.4 billion in 2025 and is projected to grow at a compound annual growth rate exceeding 14% through 2030. Several forces are driving this.

The pandemic forced the industry to adopt remote trial elements almost overnight. The FDA, EMA, and MHRA all issued guidance supporting remote consent, telehealth visits, and direct-to-patient drug delivery, and none have retracted that support. That momentum hasn't faded. Traditional trial designs require participants to travel to clinical sites repeatedly, which creates barriers for rural populations, patients with mobility limitations, and working adults. DCTs bring the trial to the participant, expanding access to historically underrepresented populations. The FDA's guidance specifically notes that sponsors shouldn't exclude participants who lack access to protocol-specified digital health technology. On the enrollment side, DCTs expand the geographic catchment area from a radius around a site to an entire region. Early adopters report enrollment improvements of 30-50% and dropout rate reductions of 20-30%.

Regulatory Framework for DCTs and eConsent

FDA Guidance on DCTs (September 2024)

The FDA's final guidance, "Conducting Clinical Trials With Decentralized Elements," published September 18, 2024, covers drugs, biological products, and devices. Key requirements include:

Protocol specification: Decentralized elements must be described in the protocol, including which visits are remote and which are in-person.
Investigator oversight: The investigator remains responsible for all trial-related activities, even those delegated to local HCPs or third-party vendors.
Data integrity: Data collected remotely must be equivalent in quality to site-collected data, with measures to limit variability.
Participant safety: Procedures for evaluating and managing adverse events identified remotely must be defined in advance.
Early FDA consultation: The guidance strongly encourages early engagement with the relevant review division, particularly for complex or first-in-human trials.

FDA eConsent Q&A Guidance (2016)

The FDA/OHRP joint guidance addresses how to present eConsent information, how and where to conduct the consent process (including remotely), how to use electronic signatures to document consent, how to verify identity electronically, how to handle pediatric consent, and how to ensure privacy and security. It doesn't create new requirements; it applies existing informed consent regulations (21 CFR 50 and 45 CFR 46) to electronic methods.

EU CTR 536/2014

The EU Clinical Trial Regulation 536/2014 requires that informed consent be written, dated, and signed by both the person conducting the consent discussion and the participant. The regulation permits electronic methods, but investigators must ensure eConsent doesn't discriminate against people uncomfortable with technology, alternative paper methods must remain available, and sole use of eConsent must be justified in the protocol. Under eIDAS, e-signatures used for consent in EU trials should meet at least the Advanced Electronic Signature (AES) standard.

ICH E6(R2) and E6(R3)

ICH E6(R2) Section 5.5 requires computerized systems to conform to requirements for completeness, accuracy, reliability, and consistent performance. While E6(R2) doesn't contain specific eConsent provisions, its requirements for audit trails, access controls, and data integrity apply to any electronic consent system. The newer ICH E6(R3), finalized in 2025, explicitly addresses electronic consent, digital tools such as video conferencing and interactive multimedia, and decentralized trial conduct.

21 CFR Part 11 applies to eConsent. Any electronic record that satisfies an FDA predicate rule must comply with 21 CFR Part 11. Informed consent under 21 CFR 50 is a predicate rule. Every eConsent system used in FDA-regulated trials must provide unique user identification, two-component authentication, signature meaning capture, immutable audit trails, and signature-record binding.

E-Signature Requirements in DCT Workflows

Decentralized trials generate a wide range of documents requiring compliant electronic signatures. The following table maps DCT document types to their requirements.

Document Type	Signers	DCT-Specific Considerations	Regulatory Basis
Informed Consent Form (ICF)	Participant, investigator or designee	Remote identity verification required; witness may sign via video	21 CFR 50, ICH E6 4.8, EU CTR Art. 29
Protocol amendments / re-consent	Sponsor, PI, participant	Participants must be re-consented remotely when protocol changes affect them	21 CFR 312.30, ICH E6 4.8.2
Monitoring visit reports	Clinical research associate (CRA)	Remote monitoring generates reports from centralized review, not site visits	ICH E6 5.18.6
Safety reporting (SAE/SUSAR)	Investigator, medical monitor	Remote AE identification requires defined escalation procedures	21 CFR 312.32, ICH E6 4.11
Investigator delegation logs	Principal investigator	Must include local HCPs and third-party vendors performing delegated tasks	ICH E6 4.2
Local HCP task logs	Local healthcare provider, PI	FDA guidance specifically addresses documentation of local HCP activities	FDA DCT Guidance (2024)
Device accountability logs	Investigator, participant	Direct-to-patient shipment requires chain-of-custody documentation	21 CFR 812.140, ICH E6 8.3

Each document must be signed with an e-signature system that meets Part 11 requirements for audit trails, identity verification, signature meaning capture, and record integrity.

eConsent Best Practices

Multimedia Content for Comprehension

The FDA's eConsent guidance supports multimedia to improve participant understanding. Strong implementations include short explanatory videos (2-5 minutes) covering key risks and procedures, interactive diagrams of study timelines, knowledge-check questions after each major section, and audio narration options. Research published in JMIR Human Factors (2025) confirms that eConsent materials developed following established guidelines achieve high comprehension scores across diverse populations in multinational trials.

Remote Identity Verification

When consent is obtained outside a clinical site, sponsors must establish signer identity. Methods include video-call verification where the investigator confirms identity against a government-issued ID, knowledge-based authentication, multi-factor authentication combining something the participant knows (password) with something they have (mobile device), and credential issuance workflows where identity is verified once for subsequent signatures.

Audit Trail Requirements

The eConsent audit trail must capture more than just the signature event: every page viewed, time spent on each section, comprehension quiz responses, questions asked and answers provided, the signature event with timestamp and meaning, subsequent document access, and re-consent events. This level of detail is what separates a regulatory-grade eConsent system from a simple electronic signature on a PDF. Platforms built for regulated environments, like Certivo, capture these interactions automatically with hash-chain integrity verification.

Re-consent isn't optional. When a protocol amendment materially affects participants, re-consent must be obtained. In a DCT, the eConsent system must support version-controlled consent documents, automated notification to affected participants, tracking of re-consent completion, and a clear audit trail distinguishing original consent from re-consent events. Failure to re-consent after material amendments is a common FDA inspection finding.

Accessibility and Language

eConsent systems must accommodate participants with visual impairments (screen reader compatibility), hearing impairments (captions on video content), limited literacy (plain language summaries), and limited technology experience (intuitive interfaces). For multinational DCTs, consent materials must be translated into each participant's native language and reviewed by local ethics committees, with version control maintained across all language variants.

Security and Compliance Considerations

HIPAA for US Participants

When DCT activities involve protected health information (PHI) of US participants, HIPAA applies to telehealth platforms, data from wearable devices, eConsent systems collecting health information, and local healthcare providers accessing participant data. Sponsors must execute Business Associate Agreements (BAAs) with all technology vendors handling PHI. See our guide on HIPAA-compliant electronic signatures for detailed requirements.

GDPR for EU Participants

Trials enrolling EU participants must comply with GDPR regardless of sponsor location. DCTs create additional considerations: data collected on personal devices in participants' homes, cross-border transfers for centralized monitoring, and participant rights to access and data portability. A lawful basis for processing must be established under Article 9(2)(a) or 9(2)(j). See our GDPR compliance guide for a full analysis.

Multi-Factor Authentication for Remote Signers

21 CFR Part 11 Section 11.200 requires non-biometric electronic signatures to employ at least two distinct identification components. In a DCT setting where signers can't be visually verified, best practice combines a unique password (something the signer knows) with a time-based one-time password from a mobile authenticator app (something the signer has).

Data Residency

Multinational DCTs must address data residency requirements that vary by jurisdiction. EU law restricts transfers outside the European Economic Area unless adequate safeguards are in place (Standard Contractual Clauses or an adequacy decision). The eConsent platform must support configurable data storage locations or demonstrate compliant cross-border transfer mechanisms.

Implementation Roadmap

A phased approach reduces risk and builds organizational capability.

Phase 1: Foundation (Months 1-3)

Select and validate a Part 11-compliant e-signature and eConsent platform.
Develop SOPs for remote consent, identity verification, and remote monitoring.
Train internal teams on DCT processes and engage FDA early for complex designs.

Phase 2: Hybrid Pilot (Months 3-6)

Implement decentralized elements in a single study as a hybrid trial.
Deploy eConsent with multimedia content and comprehension assessments.
Collect feedback from investigators, participants, and monitors to refine processes.

Phase 3: Scale (Months 6-12)

Expand decentralized elements across additional studies based on pilot learnings.
Deploy multinational capabilities including multi-language eConsent.
Integrate e-signature data with EDC, CTMS, and Trial Master File systems.

Phase 4: Optimization (Ongoing)

Analyze enrollment, retention, and data quality metrics across trial designs.
Refine eConsent content based on comprehension results and participant feedback.
Expand to fully decentralized designs where scientifically appropriate.

Start hybrid, then go fully decentralized. Organizations that attempt a fully decentralized trial without prior hybrid experience often hit unexpected problems: participant technology issues, investigator discomfort with remote oversight, and gaps in adverse event management. A hybrid pilot builds confidence and refines workflows before you remove the safety net of traditional site infrastructure. Certivo's platform supports both hybrid and fully decentralized workflows with the same compliant infrastructure.

The Bottom Line

Decentralized clinical trials and electronic informed consent aren't experimental anymore. The FDA's September 2024 final guidance on DCTs, the established eConsent Q&A guidance, and the newly finalized ICH E6(R3) provide a clear regulatory path forward. The operational benefits are real: broader geographic reach, faster enrollment, improved retention, and reduced participant burden. But they only materialize when the underlying e-signature and eConsent infrastructure meets the full range of regulatory requirements.

That means 21 CFR Part 11 compliance for every electronic record and signature. Audit trails that capture not just the signature but the entire consent journey. Multi-factor authentication for remote signers. HIPAA and GDPR compliance for multinational participant populations. And validation documentation that will withstand FDA, EMA, and MHRA inspection.

Start with a platform built for regulated clinical workflows. Validate it. Build your SOPs. Run a hybrid pilot. Scale based on evidence. For more on clinical trial e-signature requirements, see our guide on electronic signatures in clinical trials. For EU-specific requirements, see our EU CTR 536/2014 guide. To see how Certivo handles these requirements, explore our compliance capabilities.

Decentralized Clinical Trials & eConsent: E-Signature Requirements