Guide · RegulationUpdated October 14, 2026

eConsent regulations guide: what FDA, EMA and HHS expect

There is no single eConsent law. Electronic informed consent sits on top of consent rules that already exist: 21 CFR Parts 50, 56 and 11 in the US, the Common Rule for HHS-supported research, and the EU Clinical Trials Regulation with national law. This guide maps the texts, the guidance and what to check in a system.

  • FDA, HHS and EU texts mapped
  • Requirements to controls checklist
  • Not legal advice

Free sandbox · No credit card · 21 CFR Part 11 aligned

Which regime applies · illustrative
FDA (Parts 50, 56, 11)HHS (45 CFR 46)EU CTR + national
Drug or device study under an IND or IDE
NIH-funded academic study, no FDA product
NIH-funded study of an FDA-regulated drug
Interventional drug trial in EU member states
Multinational trial with US and EU sites
Demo mapping only. Your regulatory adviser decides which rules govern your study.

The short version

  • eConsent changes the medium, not the duties. The elements of consent, the need for a documented, signed and dated record, and IRB or ethics review still apply when consent is electronic.
  • In the US, Part 11 follows Parts 50 and 56. FDA and OHRP's joint Q&A (final December 2016) says Part 11 generally applies where Parts 50 and 56 do. An electronic signature on FDA-regulated consent therefore needs a Part 11-capable system.
  • HHS-supported research uses 45 CFR 46. The revised Common Rule added a key-information requirement and a broad-consent pathway. Where FDA and HHS rules both apply and differ, the Q&A says to follow the one that gives greater protection.
  • The EU is a patchwork on top of one regulation. The Clinical Trials Regulation sets consent principles; member states set details, and EMA and heads of agencies have issued non-binding recommendations on remote consent.
  • Consent to take part is not GDPR consent. The two are different legal concepts and should be explained separately in the form.

The landscape

Why eConsent regulation feels scattered

People searching for "eConsent regulations" usually expect a rulebook. There is not one. Regulators have taken the view that existing consent requirements are technology neutral and have issued Q&A guidance explaining how electronic tools can meet them. That is good news for flexibility and awkward for clarity: the answer to "is this eConsent flow acceptable" comes from several documents read together, plus the IRB or ethics committee that approves your process.

This guide sorts those documents into three groups: FDA, HHS and the EU. It is the regulatory companion to our product and drafting pages. For the technical side of signatures, read electronic signatures for clinical trials; for software selection, eConsent software for clinical trials; for writing the form, how to write an eConsent form. Everything below is a summary of public documents and secondary sources. Read the current primary texts and take advice before you rely on it.

The map

Key texts by regime

RegimeCore textsWhat they say about electronic consentApplies to
FDA21 CFR Part 50 (consent elements at 50.25, documentation at 50.27), Part 56 (IRBs), Part 11 (electronic records and signatures)Consent must be documented by a signed and dated form and a copy given to the signer; an electronic signature must meet Part 11; the IRB reviews the process and contentClinical investigations of FDA-regulated drugs, biologics and devices
FDA guidance"Use of Electronic Informed Consent: Questions and Answers" (December 2016); "Informed Consent" (August 2023); "Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers" (October 2024)Non-binding. Explain how electronic tools can meet consent requirements and what systems should provide. The 2023 guidance supersedes the 1998 guide and does not reflect the 2018 Common RuleIRBs, investigators and sponsors
HHS45 CFR 46 (revised Common Rule, effective 2019): 46.116 general requirements, key-information summary and broad consent; 46.117 documentationConsent must contain the required elements and be documented; the 2016 Q&A is hosted by OHRP and discusses electronic approachesHuman subjects research conducted or supported by HHS and institutions that apply the rule
ICHICH E6 informed consent provisions (R2 and the adopted R3)Consent must be documented by a written, signed and dated form; electronic means are accepted where the system and process meet requirementsSponsors and investigators following GCP
EUClinical Trials Regulation 536/2014 (consent articles), national laws, EMA/HMA recommendation paper on decentralised elements (13 December 2022), GDPRThe regulation sets consent principles; many details, including accepted forms of electronic or remote consent, are left to member states. The paper is non-binding and includes an overview of national provisionsInterventional clinical trials of medicinal products in the EU

Summarized from public documents and secondary sources on 2026-10-14. Wording is paraphrased. Verify against the current primary text.

United States · FDA

FDA: Parts 50, 56 and 11 read together

FDA's informed consent rules in Part 50 set the elements of consent, require that consent be documented in a form signed and dated by the participant or legally authorized representative, and require that a copy go to the person signing. Part 56 requires IRB review. Part 11 sets conditions under which electronic records and electronic signatures are considered trustworthy and equivalent to paper. FDA and OHRP's Q&A on electronic informed consent, finalised in December 2016, brings these together for electronic tools. It states that Part 11 generally applies to electronic consent where Parts 50 and 56 apply, and that research outside those parts is generally outside Part 11 as well.

The Q&A is non-binding, but IRBs and sponsors use it as a reference. In outline, it encourages the following: the IRB reviews the electronic process and the content participants will see; the system lets participants ask questions and, where appropriate, talk to staff; the identity of the signer is verified by a method appropriate to the risk; the record of consent is retained with the signature and date; and the participant gets a copy in paper or electronic form. Treat these as summaries, since the guidance gives more detail and examples.

Two later FDA documents matter. The August 2023 final guidance on informed consent supersedes FDA's 1998 guide and restates what the IRB and investigator should see in the form, including compensation and undue influence. The October 2024 final Q&A on electronic systems, records and signatures replaced the 2007 guidance on computerised systems and addresses audit trails, data security and how Part 11 applies when digital health technologies or service providers are involved. Our 21 CFR Part 11 compliance checklist goes through the system controls in detail.

United States · HHS

HHS and the revised Common Rule

Research conducted or supported by HHS, including most NIH-funded work, falls under 45 CFR 46. The revised Common Rule, effective in 2019, requires consent to begin with a concise, focused presentation of the key information that helps a prospective participant decide, and it created a broad-consent pathway for storage and secondary use of identifiable information and biospecimens. Documentation requirements in 46.117 accept electronic formats. The practical effect for an eConsent flow is that the first screen or section should present the key information in a way that supports comprehension, not as a buried paragraph.

Many academic studies are both HHS-supported and subject to FDA rules, for example an NIH-funded trial of an investigational drug. The joint Q&A says to follow the regulation that gives greater protection where they differ. Your IRB will normally tell you which standard it applies; the IRB explainer and our IRB submission checklist describe what to prepare. For academic investigators, eConsent for academic clinical research covers typical set-ups.

European Union · EMA and national law

EU: one regulation, many national details

The EU Clinical Trials Regulation 536/2014 sets out when and how informed consent is given in interventional trials of medicines, including principles for participants who cannot consent themselves and for minors. It applies directly in member states, but the practical acceptance of electronic or remote consent, identity verification and signatures varies by country and by ethics committee. In December 2022 the EMA, the Heads of Medicines Agencies and the European Commission published a recommendation paper on decentralised elements in clinical trials, which covers electronic informed consent and gives an overview of national provisions. It is non-binding and risk-proportionate in tone. Check whether it has been updated since.

Two other EU regimes matter. The GDPR governs personal data, and the consent to take part in a trial is distinct from consent as a GDPR legal basis; many trials rely on other legal bases for data processing and explain this in the information sheet. The EMA guideline on computerised systems and electronic data in clinical trials sets expectations for the system itself, including audit trails and access control; see our EMA computerised systems guideline guide and EU CTR clinical trial software. For the UK, which has its own rules, see the UK MHRA regulations guide.

Because the EU position depends on member state and ethics committee, the safest approach is to ask the ethics committee in each country whether it accepts your electronic process, and to document the answer in the submission. Remote patient consent for clinical trials and eConsent for decentralized clinical trials cover remote workflows.

Requirements to controls

What to check in an eConsent system

The expectations below recur across the FDA, HHS and EU material. The right-hand column says what to ask or test; for Capture, it also says what the product does.

The IRB or ethics committee can review exactly what participants will see

Export or screenshot the full flow. Keep the approved text and screenshots of the flow on file, and test the staff view as well as the participant view.

The participant identity is verified at signing

Ask what verification the system uses. In Capture, participants sign on screen after a two-step process that includes mandatory email OTP confirmation.

The participant acknowledges the legal effect of the signature

Capture requires the participant to acknowledge a legal-binding statement before signing.

The person obtaining consent also signs, with meaning

Investigator or authorized staff countersign with password re-authentication and a legal-meaning statement; the document is Fully Executed only after countersignature.

Witness and representative signatures are supported when needed

Capture supports an optional witness co-signature and Legally Authorized Representative signature. See impartial witness eConsent and LAR consent.

The signature is bound to the exact document signed

Each Capture signature is cryptographically linked (hashed) to the document content at signing time.

Signed record, date and time are retained with an audit trail

Signed consent exports as PDF with embedded signature data, timestamps and audit trail.

The participant gets a copy

Decide how and when the signed copy is provided, and say so in the form.

Access is role-based and changes are traceable

Role-based access with PII segregation and a field-level, append-only audit trail.

Versions are controlled and consent can be repeated when the document changes

Plan how you will handle new versions and whether participants must re-consent. Ask the vendor how your workflow is handled before you rely on it.

Data protection is addressed

Hosting region (EU Frankfurt or USA N. Virginia), encryption at rest and in transit, and a privacy notice that explains retention.

Walk an inspector through a signed consent

Create a consent in the free sandbox, sign it as a test participant, countersign it as staff and open the exported PDF with its audit trail. It shows you what to put in front of your IRB. No credit card.

Try eConsent free

How Capture handles it

Consent flow with Part 11-aligned controls

Capture provides 21 CFR Part 11-aligned controls for eConsent. Participants sign on screen, staff countersign, and the signed document leaves as a PDF carrying the evidence an IRB or inspector asks to see.

  • On-screen signature with email OTP confirmation and an acknowledgement of the legal-binding statement.
  • Countersignature by authorized site staff with password re-authentication.
  • Optional witness and Legally Authorized Representative signatures.
  • Signature hashed to the exact document content at signing time.
  • PDF export with signature data, timestamps and audit trail.
  • Consent templates for basic trials, pediatric assent, biobanks and more, starting from the basic clinical trial consent template.
eConsent for clinical trials
Electronic signature

Meaning of signature

I have reviewed this adverse event and confirm the assessment of seriousness, severity and causality.

Signer

Dr. A. Ozola, PI

Password

••••••••••

Verified on the serverAutofill blockedSingle-use token
Sign

Boundaries

What the software cannot decide for you

Software does not make a consent process compliant on its own. The IRB or ethics committee must approve the process and content. The sponsor decides whether the system is suitable and validated for its use. The investigator remains responsible for ensuring that consent is informed and voluntary, which a screen cannot do. Capture provides the technical controls, and validated use is shared with the sponsor.

Also be careful with claims that go beyond the documents. This page does not say that FDA, EMA or any ethics committee has certified Capture, and no regulator certifies eConsent software in that way. If your study needs multilingual consent or specific re-consent workflows, confirm the current capability with the Capture team before you plan around it. This is general information, not legal advice.

In practice

Taking an eConsent process through ethics review

  1. 1

    Identify the rules that apply

    FDA, HHS, EU or national law, or a combination. Ask your regulatory adviser or IRB.

  2. 2

    Describe the process

    Who obtains consent, how identity is verified, how the participant asks questions, how signatures are collected and how a copy is provided.

  3. 3

    Show the screens

    Give the IRB the exact text and screens participants will see, and the staff view.

  4. 4

    Describe the system controls

    Audit trail, access control, signature binding and export. Ask your vendor for any statement you need.

  5. 5

    Test before enrolment

    Run test consents in the sandbox, including countersignature and export, and file the result with the submission.

  6. 6

    Control versions

    Keep each approved version of the form and a record of which participants signed which version.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Is electronic informed consent allowed by the FDA?

Yes. FDA and OHRP's Q&A on electronic informed consent (final December 2016) explains how electronic tools can meet the requirements of 21 CFR Parts 50 and 56 and, where signatures are electronic, Part 11. IRB review of the process is expected.

Does 21 CFR Part 11 apply to eConsent?

The Q&A says Part 11 generally applies where Parts 50 and 56 apply, so for FDA-regulated studies an electronic signature on consent should come from a system with Part 11 controls. Research outside those parts is generally outside Part 11. Confirm with your IRB and sponsor.

What does the Common Rule say about electronic consent?

The revised Common Rule (45 CFR 46, effective 2019) requires key-information up front and allows documentation in electronic form. The joint FDA and OHRP Q&A applies to HHS research as well. Where FDA and HHS rules both apply, follow the one giving greater protection.

Is eConsent accepted in the EU?

It depends on the member state and the ethics committee. The EU regulation sets principles, and a December 2022 EMA, HMA and Commission recommendation paper on decentralised elements discusses electronic consent without being binding. Ask each country's ethics committee.

Is consent to participate the same as GDPR consent?

No. They are separate concepts. Many trials process personal data under another GDPR legal basis. Explain both clearly and take advice from a data protection officer.

Does the FDA certify eConsent software?

No. Regulators do not certify software in that sense. Sponsors and IRBs decide whether a system is suitable, based on its controls and validated use.

What controls does Capture provide for eConsent?

On-screen signature with mandatory email OTP, a legal-binding acknowledgement, staff countersignature with password re-authentication, optional witness and LAR signatures, hashing to the exact document, role-based access and PDF export with timestamps and audit trail. These are Part 11-aligned controls; validated use is shared with the sponsor.

Is this legal advice?

No. Check the current texts and ask your regulatory adviser, IRB or ethics committee.

Test an eConsent flow free

Free sandbox with every feature. No credit card, and you pay only when you go live with real participants.

Try eConsent free