eConsent Requirements: A Guide for Clinical Trials
Direct answer
eConsent requirements center on validated systems, time stamped audit trails, authenticated electronic signatures, role based access, version control, and retrievable records. In the United States these expectations come from FDA guidance and 21 CFR Part 11, with ICH E6(R3) adding reinforced expectations for computerized systems and participant comprehension. Trials in the European Union add the Clinical Trial Regulation, eIDAS, and GDPR.
What is eConsent?
Electronic informed consent, or eConsent, uses digital technology to present study information and obtain participant consent in clinical trials. Instead of a paper form, participants review materials through a phone, tablet, or web portal. They can interact with multimedia content, answer comprehension questions, and sign electronically.
eConsent is not just a digital version of paper. It changes how participants engage with study information and how teams document the consent process. Regulatory agencies in the US and EU have recognized it as a valid method for obtaining informed consent, provided it meets specific requirements.
Why eConsent requirements matter
Regulatory frameworks for eConsent exist to protect participants and ensure data integrity. When a consent process moves from paper to digital, the systems behind it must meet standards for electronic records, signatures, and audit trails. These requirements apply to sponsors, CROs, and sites using eConsent in any clinical trial, whether in-person, hybrid, or fully decentralized.
Understanding the key requirements helps teams choose the right platform, prepare for audits, and avoid compliance gaps that could delay study startup or compromise data quality.
FDA and 21 CFR Part 11
The FDA and the HHS Office for Human Research Protections (OHRP) issued joint guidance on electronic informed consent in 2016, titled "Use of Electronic Informed Consent in Clinical Investigations: Questions and Answers." When electronic records or signatures are used to satisfy FDA recordkeeping requirements, the systems must comply with 21 CFR Part 11, which governs electronic records and electronic signatures in FDA regulated clinical trials.
| Requirement | What it means for eConsent |
|---|---|
| Validated systems | The eConsent platform should be validated to ensure it works as intended |
| Audit trails | Time stamped records for key consent events, signatures, version changes, and record modifications |
| Electronic signatures | Signatures should be linked to the record and verified through authentication |
| Access controls | Only authorized users can view, edit, or sign consent documents |
| Record retention | Electronic consent records must be retained and available for inspection |
The FDA guidance also encourages sponsors to consider how eConsent can support participant comprehension. Features like interactive quizzes, multimedia content, and adjustable reading levels can help participants understand what they are agreeing to.
ICH E6(R3) and the 2025 GCP update
ICH adopted the E6(R3) Principles and Annex 1 in January 2025, representing the most significant revision to Good Clinical Practice since E6(R2) in 2016. Annex 2 was subsequently adopted in June 2026, and all three components are now consolidated into a single guideline. Implementation depends on adoption by local regulatory authorities.
ICH E6(R3) reinforces expectations around informed consent, computerized systems, data governance, audit trails, and participant understanding. Key areas relevant to eConsent include:
- Audit trail expectations: Electronic systems used in clinical trials should maintain validated audit trails that record key consent events and modifications.
- Participant comprehension verification: eConsent systems can support participant understanding through built-in knowledge checks and interactive content, helping document that participants understood the study information.
- Remote consent: The guideline addresses obtaining consent remotely, including via telemedicine or video call, which is especially relevant for decentralized trials.
- Ongoing consent and re-consent: Clearer expectations for re-consenting participants when new information emerges during a trial, including tracking which version of the consent a participant signed.
- System validation: Electronic systems used in clinical trials, including eConsent, should be validated to ensure they meet GCP standards.
EU regulatory considerations
- Clinical Trial Regulation (EU) 536/2014: Permits electronic consent procedures, provided that member states allow it and suitable methods ensure authenticity and traceability.
- eIDAS Regulation (EU) No 910/2014: Governs electronic signatures. A qualified electronic signature is legally equivalent to a handwritten signature.
- GDPR: Applies to personal data collected during the consent process, including how it is stored, processed, and shared.
Implementation varies by member state. Some countries require an initial in-person discussion before electronic consent can be used. Sponsors running multi-country trials should plan for country-specific regulatory reviews before study startup.
Practical steps for eConsent compliance
Choose a validated platform. The eConsent system you select should come with validation documentation, including IQ/OQ/PQ records or a Computer Software Assurance approach. Ask vendors for their validation summary report before committing.
Verify electronic signature compliance. Confirm that signatures meet 21 CFR Part 11 or eIDAS requirements, depending on your regulatory jurisdiction. The system should authenticate the signer and link the signature to the consent record.
Review audit trail capabilities. The system should capture time stamped records for key consent events: when a participant opened the consent, when they completed comprehension checks, and when they signed.
Plan for version control. When a protocol amendment requires updated consent, the system should track which version each participant signed and flag who needs re-consent.
Test participant comprehension. Use built-in quizzes or knowledge checks to help document understanding. This supports both regulatory expectations and the quality of consent.
Prepare for inspection. Ensure that consent records are exportable, retrievable, and available for regulatory inspection throughout the study and retention period.
For a side by side look at how different vendors handle these requirements, see our eConsent software comparison.
How Curebase approaches eConsent
Curebase eConsent is designed to meet FDA 21 CFR Part 11 and ICH GCP standards, with validated electronic signatures, version-controlled consent documents, role-based access, and a complete audit trail of every view, edit, and signature event. Because eConsent is built into the same platform as eCOA/ePRO, Electronic Data Capture for Clinical Trials, and participant engagement, signed participants flow directly into screening and data collection without manual hand-offs.
Conclusion
eConsent requirements are not just about checking a regulatory box. They define how sponsors protect participants, maintain data integrity, and build trust in the consent process. With ICH E6(R3) now adopted and decentralized trials becoming more common, getting eConsent right matters more than ever.
Choose a platform that handles validation, audit trails, and version control so your team can focus on running the study. Learn more about Curebase's approach to eConsent.
Frequently asked questions
What are the core eConsent requirements for clinical trials?
eConsent systems used to satisfy FDA recordkeeping requirements must support validated software, time stamped audit trails, authenticated electronic signatures linked to the record, role based access controls, and retention of consent records for inspection. Trials in the EU add requirements from the Clinical Trial Regulation, eIDAS, and GDPR.
Does eConsent have to comply with 21 CFR Part 11?
Yes. When electronic records or electronic signatures are used to meet FDA recordkeeping requirements, the systems behind them must comply with 21 CFR Part 11, which governs electronic records and electronic signatures in FDA regulated clinical trials.
What does ICH E6(R3) change for eConsent?
ICH E6(R3) reinforces expectations around informed consent, computerized systems, data governance, audit trails, and participant understanding. For eConsent this means validated audit trails, support for comprehension verification, guidance on remote consent, clearer expectations for re-consent and version tracking, and system validation.
Is electronic consent allowed in the European Union?
Clinical Trial Regulation (EU) 536/2014 permits electronic consent procedures provided member states allow it and suitable methods ensure authenticity and traceability. Implementation varies by member state, and some countries require an initial in-person discussion before electronic consent can be used.
How should sponsors verify an eConsent platform is validated?
Ask the vendor for validation documentation before committing, including IQ/OQ/PQ records or a Computer Software Assurance approach, along with a validation summary report. Confirm that electronic signatures meet 21 CFR Part 11 or eIDAS requirements for your jurisdiction.
How does eConsent handle protocol amendments and re-consent?
The system should apply version control to consent documents, track which version each participant signed, and flag participants who need to be re-consented when a protocol amendment or new safety information changes the consent form.
