Remote eConsent: Documenting Identity Without Excluding Participants

Remote consent creates a narrow operational problem. A one-time passcode sent to a phone number the participant typed in proves only that someone holds that phone. If an enrollee is hospitalized on consent day and an adult family member enters the code and signs, the signature is not the participant's. 21 CFR 11.100 requires the signature to be unique to one individual and requires the organization to verify identity before it sanctions the signature. Procedures and endpoint data collected on the strength of that signature lack valid consent from the participant, so they cannot be treated as consented data for that person. The opposite error is a rigid photo-ID upload. Eligible participants who lack a current driver's license or passport, a stable address, or the camera the vendor expects never reach the signature step, and the decentralized design then enrolls a narrower population than the protocol described.

The workable design is a documented, risk-proportionate method ladder and an identity note filed with each consent. Only 21 CFR 11.100 makes identity verification a legal condition that must be completed before the organization establishes, assigns, certifies, or otherwise sanctions the electronic signature. The UK and EU texts reviewed here are guidance or a non-binding recommendation, and none of them mandates a proprietary technology or a commercial identity-proofing vendor.

Under United States law, 21 CFR 11.100(b) states that before an organization establishes, assigns, certifies, or otherwise sanctions an individual's electronic signature, or any element of that signature, the organization shall verify the identity of the individual. Section 11.100(a) requires each electronic signature to be unique to one individual and not reused or reassigned. The December 2016 joint guidance from the Food and Drug Administration (FDA) and the Office for Human Research Protections (OHRP), Use of Electronic Informed Consent in Clinical Investigations: Questions and Answers, places the remote-consent duty in Question 2. If any or all of the consent process takes place remotely and is not personally witnessed by study personnel, the electronic system must include a method to ensure that the person signing is the subject who will participate or the subject's legally authorized representative. Question 2 lists examples and points to Question 7: a state-issued identification or other identifying documents, personal questions, biometric methods, or visual methods.

Question 7, for FDA-regulated clinical investigations, states that Part 11 is meant in part to prevent fraudulent use and that FDA does not specify any particular identity-verification method. Its examples are official identification, such as a birth certificate, a government-issued passport, or a driver's license, and security questions. Question 6 answers a different question: how an electronic signature may be created. It allows computer-readable ID cards, biometrics, digital signatures, and username-and-password combinations, and it says FDA does not mandate a particular creation method. Those tools do not, by themselves, prove who is holding the credential. The same Question 2 also records OHRP's limit for research under the sole authority of 45 CFR part 46: verification may not be possible or necessary for every study. OHRP encourages a risk-based approach and gives social-behavioral minimal-risk research as the example that will not typically warrant verification. FDA-regulated investigations still follow Questions 2 and 7. FDA's October 2024 guidance, Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers (Procedural, Revision 1), confirms the same restraint in Question 26. Part 11 does not specify a method for verifying the person who will sign under 11.100(b). Methods may include, and are not limited to, official government-issued identification, security questions, or strong digital login credentials accompanied by multi-factor authentication or video observation.

To satisfy regulatory inspectors, trial teams must maintain a strict analytical separation between the three core pillars of electronic consent integrity: identity proofing, session authentication, and signature attribution. Confusing these three operational layers invariably leads either to vulnerable protocol workflows or to unsupportable audit findings.

When selecting an identity-verification methodology for a multicenter or global decentralized clinical trial, clinical operations teams must navigate diverse national regulatory expectations without fragmenting the trial into incompatible operational silos. A comparative analysis of health authority guidance across the United States, United Kingdom, and European Union reveals strong conceptual convergence on proportionality, even where local statutory mechanisms diverge.

In the United Kingdom, the Medicines and Healthcare products Regulatory Agency (MHRA) and the Health Research Authority (HRA) set the standard in their Joint Statement on Seeking Consent by Electronic Methods (version 1.2, September 2018). The statement chooses the signature class by asking whether, taking the recruitment and consent procedures together, you can trust that the person who signed is who they say they are, can trust that the consent form they signed has not been altered, can trust when the signature was applied, and can demonstrate that trust if required. For clinical trials of investigational medicinal products conducted remotely, the statement says it may not always be possible to verify identity. Identity may be checked visually on a video link, through a local NHS site, or in person with official photo identification before any research intervention. Where that in-person check can be completed before the intervention, a simple electronic signature will normally be acceptable. Where it is not possible to verify identity, for example by checking official photo ID, an advanced or qualified electronic signature may be preferable, though it is not legally required. For research other than those trials, any form of simple electronic signature will normally be adequate to document consent. The statement does not name a vendor or require an identity-document upload.

At European level, the recommendation paper on decentralised elements in clinical trials, Version 02 dated 1 October 2025, was published on 29 October 2025 and supersedes the December 2022 version. It was drafted with the HMA Clinical Trial Coordination Group, the European Commission Clinical Trial Expert Group, and the EMA GCP Inspectors Working Group, and it includes perspectives from the European medicines regulatory network. The Clinical Trials Advisory Group endorsed it on 15 October 2025. The paper says its views are not legally binding. For a remote informed-consent interview, it recommends a real-time audio and video discussion. The investigator should make every effort to check the identity of a participant who is not already known to them, and the participant should have the right to ask for proof of the investigator's identity if they have not been in contact before. The sponsor should ensure that participants and investigators can have the interview on site if they prefer. Only in duly justified cases may the remote option be the only one offered. The national-provisions appendix is country-specific. Finland's entry, citing the Client Data Act, says the participant should be identified reliably, for example through suomi.fi or an equivalent, and that the signature method must be advanced or qualified. That row is not an EEA-wide rule.

In the United States, FDA finalized Conducting Clinical Trials With Decentralized Elements in September 2024. Investigators may obtain informed consent electronically or on paper at a participant's remote location if applicable regulatory requirements are met. Obtaining informed consent is an investigator responsibility. If it is delegated, the person obtaining consent should have detailed protocol knowledge and the training and credentials to answer questions. FDA does not consider obtaining informed consent an appropriate activity for a local healthcare provider. The guidance does not itself prescribe how to verify the participant's identity. Elsewhere it says study records should capture visit type (telehealth or in person), visit location, date, and the data originator. It also treats real-time video and audio interaction as a live exchange, not an electronic record under Part 11. The visit still has to be documented, for example in a visit note, and an electronic note is kept in a system subject to Part 11. How remote collection of endpoints relates to these visit rules is discussed in the review of decentralized endpoint collection operating rules.

The following decision matrix synthesizes the five primary regulatory baselines, outlining their legal status, accepted verification pathways, fallback allowances, and inspection documentation standards.

None of those authorities publishes a four-tier product workflow. A sponsor can still write one, so sites do not invent a method at the first consent and do not turn the strictest check into the only check. The ladder below is that kind of protocol choice. It orders methods the sources already accept, from a live look at a known patient plus an independent identifier, through an inspected official document that is not retained, to a deferred in-person check before the intervention. The protocol should label the ladder as the sponsor's method, with the authority for each rung cited beside it.

flowchart TD
  A["Candidate identified for remote eConsent"] --> B{"Already known to the investigator?"}
  B -- Yes --> C["Tier 1: live video plus identifiers from a source the participant did not just supply"]
  B -- No --> D{"Official photo ID available to inspect?"}
  D -- Yes --> E["Tier 2: investigator inspects the document during the consent contact and does not keep the image"]
  D -- No --> F{"Independent clinical or pharmacy source available?"}
  F -- Yes --> G["Tier 3: check facts from that unshared source"]
  F -- No --> H["Tier 4: defer in-person verification until before the intervention"]
  C --> I["File method, verifier, signer role, source, time, and outcome with the consent"]
  E --> I
  G --> I
  H --> I
  I --> J["Only then sanction the electronic signature under 21 CFR 11.100"]

To understand how an eConsent identity SOP functions in practice, consider a clearly hypothetical Phase II multicenter decentralized clinical trial evaluating an investigational oral small-molecule immunomodulator in adult patients with moderate-to-severe active ulcerative colitis. The protocol is structured as a fully decentralized study: participants undergo screening online, review the informed consent document asynchronously on personal smartphones or tablets, discuss the study with an investigator via telehealth, electronically sign the consent form, and receive study drug by specialized temperature-monitored courier directly to their homes. Primary efficacy endpoints rely on daily patient-reported outcomes (PROs) capturing stool frequency and rectal bleeding indices via an eCOA mobile application, supplemented by remote pharmacokinetic biospecimen sampling.

Prior to First Subject First Visit (FSFV), the trial's clinical operations lead, data management director, and lead biostatistician met to finalize the study's Standard Operating Procedure (SOP) governing participant identity verification. Two opposing implementation proposals exposed the critical failure modes that threaten decentralized trials.

In this hypothetical, the first build was self-service. The participant typed a name, an email address, and a mobile number, received a six-digit passcode by SMS, and used that code to open and sign the consent. One prospective participant was hospitalized on the morning of the scheduled consent discussion and did not use the phone. That afternoon an adult sibling saw the text, entered the code, and typed the participant's name, intending to hold a place in the trial. The sibling was not a legally authorized representative.

A later source-data check would compare the consent audit trail with the admission record. The trail would show a signature. The hospital record would show that the participant was admitted and was not the person holding the phone. The signature fails 21 CFR 11.100 in two ways: it is not the participant's signature, and nobody verified the participant's identity before it was applied. Question 7 of the 2016 guidance describes Part 11 as aimed in part at preventing fraudulent use. The example stays hypothetical: one unsigned participant, one family member with the phone, and endpoint data that cannot ride on that signature.

Baseline diaries and remote biospecimen results collected after that signature would lack valid consent from the participant. They should be quarantined for that person, further procedures stopped, and the deviation reported to the IRB. A timestamp conflict between a consent audit trail and an external record is the kind of participant-level discrepancy discussed in the review of clinical data reconciliation for eCOA and EDC. Hold that participant's data until the consent record is repaired or the participant is withdrawn.

After that deviation, the hypothetical quality lead required every applicant to upload a driver's license or passport and to pass a real-time facial scan before the consent form would open. Recruitment then stalled. People without a current license or passport, people in shared or temporary housing, and people whose phones could not produce the image the vendor required could not pass the screen.

Candidates who reached the helpline described reluctance to upload a facial template to a commercial platform. The control had become a filter. Enrollment tilted toward people with current credentials, newer phones, and comfort uploading biometrics. That is the exclusion risk described in the ethics literature cited below.

The study team resolved both failure modes by replacing the all-or-nothing digital hurdle with an approved, documented four-tier verification escalation ladder:

1. Tier 1 (Known Patients): If the prospective participant was referred by their treating gastroenterologist at an affiliated clinical site, the investigator confirmed their identity during the live telehealth consent conference by visually matching the participant against existing electronic health record (EHR) photographs and corroborating unshared clinical identifiers (e.g., date of initial endoscopy, historical biologic medication history).

2. Tier 2 (Official Photo ID Inspection): For newly referred participants who possessed government credentials, the investigator conducted a visual check during the secure telehealth session, inspecting the participant holding their driver's license or passport to camera, or utilized the secure portal to inspect the document without retaining unredacted identity images.

3. Tier 3 (Independent-Source Clinical Knowledge Checks): For participants lacking government photo identification, the investigator cross-referenced independent clinical data obtained directly from the participant's primary care provider or dispensing pharmacy (such as confirming the date and dosage of a historical prescription or previous diagnostic laboratory facility). Crucially, this information was drawn from external records, not from data the participant had entered into the trial's online screening questionnaire.

4. Tier 4 (Deferred In-Person Verification): For participants who could not complete Tiers 1 through 3 remotely, the hypothetical protocol allowed remote education and a provisional consent discussion, then an in-person check by trial personnel on the delegation log before the first dose. FDA's decentralized-elements guidance does not treat a local healthcare provider as an appropriate person to obtain consent, so this visit is investigator-supervised trial staff, not an ad hoc local clinician. The check uses whatever secondary material the IRB has already approved, and it is completed before the intervention, which is the timing MHRA/HRA and the Leeds CTRU describe for an in-person confirmation.

This ladder eliminated fraudulent proxy signing by enforcing live, human investigator verification against independent data, while completely removing the digital photo-ID barrier that had excluded vulnerable patients. Managing these protocol amendments and operational adjustments across study phases is further examined in our guide to eConsent reconsent and version linking.

Establishing an identity verification ladder is clinically meaningless unless the trial can reconstruct exactly how, when, and by whom each verification was completed during a regulatory inspection. Regulatory inspectors from the FDA, EMA, or MHRA do not evaluate an eConsent process based on marketing claims in vendor brochures; they inspect the primary source documentation filed in the Trial Master File (TMF) and the Investigator Site File (ISF).

Signed consent and the identity note are source documents. Keep them in the investigator site file, and file the sponsor copy where the trial's TMF plan places informed-consent evidence. The TMF Reference Model filing zones follow the CDISC model: Zone 05 is Site Management, and an informed-consent artifact can exist at trial, country, and site level. The record those zones need, drawing on the Leeds paper, FDA's visit-record recommendation, and the MHRA/HRA demonstrability question, is a note an inspector can read: method, verifier, signer, independent source, time, and outcome.

The block below is an illustrative record for a different, fictional participant from the failure-mode story. Names, identifiers, and timestamps are examples of fields, not a real trial file.

{
  "trialIdentifier": "EXAMPLE-UC-2026",
  "subjectId": "EXAMPLE-104-028",
  "consentVersion": "v3.0-example",
  "verificationTimestampUtc": "2026-09-28T14:35:10Z",
  "verificationTier": "tier-1-video-independent-source",
  "verifier": {
    "name": "Example Investigator, MD",
    "role": "Principal investigator",
    "delegationLogTaskId": "DL-EXAMPLE-CONSENT"
  },
  "signer": {
    "role": "subject",
    "legalAuthorityVerified": true
  },
  "independentSource": {
    "sourceType": "care-record-not-entered-by-participant",
    "referenceIdentifier": "EXAMPLE-REF",
    "dataPointsCorroborated": [
      "historical-procedure-date",
      "prior-therapy"
    ]
  },
  "encounterModality": "two-way-telehealth-video",
  "verificationOutcome": "verified",
  "precedesIntervention": true
}

No clinical trial operating in real-world conditions can assume that 100% of eligible participants will successfully navigate digital identity verification on their first attempt. Protocol teams must establish formal, pre-approved fallback mechanisms approved by the institutional review board or independent ethics committee (IRB/IEC) before study activation.

Health authority regulations and established trial network frameworks provide explicit precedents for handling absent documentation or participant verification difficulties:

• FDA Question 8, pediatric assent: Question 8 of the 2016 eIC Q&A says that, depending on the verification method, a child may lack the documentation needed to prevent fraudulent use of an electronic signature, and a driver's license is the example. If so, and depending on the investigation, it may be reasonable for the parent to initially document the child's assent, which can then be verified when the investigator first sees the child. Question 8 addresses a child who lacks identity documentation. For an adult without photo identification, write the path from the MHRA/HRA remote-CTIMP paragraph and the Leeds practice, and put any before-the-intervention timing in the protocol.

• DAIDS refusal procedure, for DAIDS sites: The DAIDS Age and Identity Verification FAQ is a network procedure for DAIDS clinical research sites, not a regulation for sponsors generally. Initial age and identity verification is done at the first visit, before the person participates, generally during consent at screening and enrollment and before study procedures. Identity is confirmed at later visits so the same participant is present. Each site SOP should say what happens if a participant refuses identity confirmation, including whether the participant may continue and how the refusal is documented. If the local IRB or ethics committee approves that SOP, the site follows it. Participants who lack a document, as distinct from those who refuse, are handled in the method ladder above.

• MHRA/HRA advanced or qualified signature: Where a remote CTIMP cannot verify identity, for example by checking official photo ID, the September 2018 MHRA/HRA statement says an advanced or qualified electronic signature may be preferable because it uniquely identifies the signer and provides greater assurance. The same sentence says this is preferable and not legally required. For research other than CTIMPs, a simple electronic signature will normally be adequate.

• Leeds CTRU proportionate checks: The Leeds CTRU paper in Trials (2024) describes one UK unit's REDCap process as it was used in that unit's ethically reviewed trials. For patients already known to recruiters, identity could be confirmed visually on a video call and/or by checking basic identifiers such as name and date of birth. Information used for the check had to come from a source other than what the patient had previously supplied. In-person confirmation at the first trial visit was acceptable if it preceded the intervention. Sites were instructed to document the step whenever remote eConsent was used.

When implementing an eConsent framework within configurable platforms such as REDCap, trial data managers must ensure that electronic signature fields, version-locking instruments, and verification logs are tightly integrated. Operational configurations for these workflows are detailed in our guide on the REDCap eConsent framework.

The ultimate ethical hazard in decentralized trial design is allowing identity verification procedures to silently mutate into de facto eligibility criteria. When an identity-proofing tool requires cutting-edge smartphones, flawless optical character recognition of government IDs, or high-bandwidth video streams, the trial ceases to be an inclusive scientific investigation and becomes a demographic filter.

In an extensive ethical evaluation of decentralized clinical trials and informed consent technologies published in Health Care Analysis (2024/2025), van Rijssel, van Thiel, and van Delden, writing for the Trials@Home consortium, describe how verification of identity is less self-evident in a decentralized trial than at a site and can place a burden of proof of trustworthiness on the participant. The paper's point is that the participant has to demonstrate trustworthiness, for example through an online identity check or by opening medical records.

The same paper says that requiring digital or health literacy may unintentionally exclude groups from decentralized trials. Design choices can answer that risk: an assisted telephone path, a paper consent, and an in-person interview, alongside the electronic path.

That design choice lines up with the October 2025 recommendation paper. The paper expects sponsors to keep an on-site informed-consent interview available, and it allows a remote-only option only in duly justified cases. The paper's own notice says the views are not legally binding. Building a system that can offer both paths is a validation problem, discussed in the overview of validating computerized endpoint capture systems.

By treating identity verification as a sponsor-owned, risk-proportionate protocol procedure rather than a commercial software checkbox, trial teams protect participant rights, preserve data integrity under 21 CFR Part 11 and ICH GCP, and ensure that decentralized clinical trials expand access to research rather than restricting it.