eConsent for Pediatric Trials: Lessons From Three 2025 Programs

Why Pediatric eConsent Is the Hardest eConsent Problem

Adult eConsent has reached operational maturity. The FDA’s 2016 joint guidance with OHRP on electronic informed consent (recently consolidated into broader digital health technology guidance) established the regulatory envelope, and the operational patterns are well-understood across CROs and sponsors. Pediatric eConsent is materially harder because the regulatory architecture is doubled: 21 CFR 50 Subpart D requires both parental or guardian permission and the assent of the minor where the minor is capable of providing it. The IRB must determine the age at which assent is required, the form assent takes, and the documentation that demonstrates it was obtained appropriately.

The operational consequences are not trivial. A single eConsent session may involve a guardian completing a consent form designed for adult literacy, a 14-year-old completing an assent form designed at a developmentally appropriate reading level, a 7-year-old being walked through a pictographic assent designed for younger children, and an audit trail that captures all three actions plus the supervising clinician’s verification. The platform must support this without requiring three separate logins, three separate workflows, or three separate sign-offs that lose synchronization.

The three 2025 programs whose patterns we reconstruct each navigated this differently, and the differences are instructive. The oncology program emphasized clinician-led co-review; the rare disease program leaned heavily on family-paced asynchronous review; the vaccine program emphasized broad-population workflows that scaled across multiple age strata. The structural logic of each is recognizable in the public record.

The Three 2025 Program Patterns

The three pediatric eConsent programs we reconstruct here are composites drawn from publicly available signals: sponsor presentations at ACRO clinical research conferences, CRO partnership announcements, IRB working group discussions, and industry coverage of pediatric trial operations. We synthesize the structural pattern without attributing to any single program.

The oncology pediatric program operated in a tertiary care center context where consent conversations were necessarily clinician-led. The eConsent platform was used as a structured complement to the in-person conversation rather than a substitute for it. Guardian consent and minor assent were captured in the same session, with the assent workflow adapted dynamically based on the child’s age and developmental status.

The rare disease program operated across a globally distributed enrollment pattern where families often traveled significant distances to participating sites. The program leaned into asynchronous family review: the eConsent materials were made available before the in-person visit, families reviewed them at home, and the in-person session focused on questions and signature capture. The technology stack had to support secure remote access without compromising the chain of custody on the signed forms.

The vaccine program operated at much higher enrollment volume than the other two, with broad age stratification from infants through adolescents. The workflow had to scale across age groups while preserving the differentiation that 21 CFR 50 Subpart D requires. The technology stack emphasized configurability: the same platform could produce a pictographic assent for a 6-year-old and a full text assent for a 16-year-old, with appropriate IRB-approved variants for each.

The Guardian/Assent Dual Workflow

The single most consequential design decision in pediatric eConsent is how the guardian consent and minor assent are bound into one workflow. The three program patterns converged on a similar structural answer despite their different operational contexts.

The workflow operates in three logical phases. In the first phase, the guardian completes the parental permission form, including all required elements: study purpose, procedures, risks, benefits, alternatives, confidentiality, voluntary participation, and contact information. This is structurally identical to an adult consent flow, with the addition that the guardian is explicitly identified as completing permission on behalf of the minor.

In the second phase, the minor completes the assent process, with the form variant chosen based on the IRB-approved age stratification. For minors below the IRB-determined age of assent capability, this phase is omitted and the IRB’s determination is documented in the audit trail. For minors above that age, an age-appropriate assent form is presented and signed.

In the third phase, the supervising clinician verifies that the guardian and minor have had the opportunity to ask questions, that the information has been presented in an understandable form, and that the consent and assent are being given voluntarily. This verification produces its own audit entry tied to the same session.

The key technical requirement is that all three phases produce linked records in a single session-level audit trail. Inspectors who probe pediatric eConsent want to see, in one document set, that guardian permission was obtained, that assent was obtained or appropriately excluded, that the clinician verified the process, and that all three actions occurred in the appropriate sequence. Platforms that produce three separate documents in three separate workflows fail this test even when each individual document is complete.

IRB Acceptance Patterns and What Determines Them

IRB acceptance of pediatric eConsent has been the most variable element across the three program patterns. Some IRBs have been enthusiastic adopters; others have required substantial work to reach approval. The structural factors that determine the difference are recognizable.

The first factor is the IRB’s institutional comfort with electronic consent generally. IRBs that have approved adult eConsent successfully are materially more likely to approve pediatric eConsent quickly, because the underlying regulatory and operational frameworks are already familiar. IRBs that are reviewing eConsent for the first time as part of a pediatric protocol face the burden of evaluating both the eConsent modality and the pediatric-specific elements simultaneously.

The second factor is the assent form’s developmental appropriateness. IRBs scrutinize whether the form is written and presented at a level the target age group can understand. Programs that engaged pediatric communication specialists or used readability validation tools in the assent development moved through IRB review faster than programs that submitted assent forms developed by adult-focused medical writers.

The third factor is the workflow’s accommodation of family dynamics. Pediatric consent conversations often involve more than one guardian, sometimes with the involvement of grandparents or extended family. IRBs that have raised concerns about family dynamics in adult-focused eConsent platforms become more concerned in the pediatric context. Programs that designed the workflow to accommodate multi-guardian review and multi-party question-asking moved through IRB review more smoothly than programs that assumed a single guardian present at the in-person visit.

The Technical Architecture That Held Up

The technical architecture choices that distinguished the successful 2025 programs from less successful ones are recognizable. The platforms that worked had four characteristics in common.

Configurable assent variants tied to IRB approvals. Rather than hardcoding one assent form, the platforms supported multiple IRB-approved variants that could be selected based on the minor’s age and the IRB’s age determination. The selection logic was auditable; changes to the variant catalog required documented IRB acknowledgment.

Linked session audit trails. Guardian permission, minor assent, and clinician verification all produced records linked to a single session ID, with the sequence of actions preserved. The audit trail was queryable across the linked records, not just within each.

Identity verification proportionate to the workflow. Guardian identity verification matched the standards used in adult consent. Minor identity verification was lighter (a minor cannot generally produce government-issued ID) but was tied to the guardian’s verification through the session linkage. The platforms did not attempt to apply adult identity-verification standards to minors, which would have failed in practice.

Secure remote access for asynchronous family review. The rare disease program in particular required that families could access eConsent materials securely from home. The platforms that worked supported time-limited secure links, encrypted document delivery, and audit trails for remote access that were preserved alongside the in-person signature capture.

Platforms that failed in the 2025 programs typically failed on the audit trail dimension. Three separate documents with three separate identifiers, no session-level linkage, no preserved sequence — these patterns produced submissions that IRBs approved reluctantly and that became headaches at inspection.

Failure Modes Observed in the 2025 Programs

The failure modes observed across the three program patterns fall into four categories.

Workflow desynchronization. A guardian completes consent in the morning, the minor completes assent in the afternoon, the clinician verifies the next day. By the time the records are reviewed, the linkage between them is unclear. This was the most common failure mode and was almost always caused by platform limitations rather than process failures.

Assent form age inappropriateness. An IRB-approved assent form developed for adolescents was used for a younger sibling enrolled later in the same program. The platform did not flag the mismatch; the clinician did not catch it during the in-person session. The finding emerged during a routine monitoring visit and required rework of the consent for the affected subject.

Identity verification gaps. The guardian’s identity was verified through the platform’s standard adult workflow, but the linkage between the guardian and the minor was not documented in a way that an inspector could follow. The platform recorded that “John Smith” consented and “John Smith Jr.” assented, but the relationship was not in the audit trail.

Remote access chain-of-custody breaks. Families accessed eConsent materials from home using shared family devices. The platform’s audit trail recorded that the materials were accessed but could not document which family member did so. When questions emerged about whether the guardian or another family member had reviewed the materials, the audit trail could not answer them.

Each of these failure modes has a documented response in the public signal from CRO presentations and ACRO working groups. The responses are recognizable enough that the 2026 cohort of pediatric programs can anticipate and design around them.

Operational Playbook for 2026 Pediatric Programs

For sponsors and CROs running pediatric programs in 2026, the operational playbook drawn from the 2025 patterns has five elements.

1. Engage IRBs early on the dual workflow. Before submitting the protocol, share the eConsent workflow design with the central IRB or lead site IRB. Walk through the guardian-assent-verification sequence. Address family dynamics, multi-guardian review, and age stratification explicitly. This investment compresses approval timelines materially.

2. Develop assent variants with pediatric communication specialists. Adapted-from-adult assent forms consistently fail IRB review. Investment in age-appropriate development pays back in faster approval and stronger family experience. The investment is modest relative to the program’s overall cost.

3. Select platforms with session-level audit trails. The single most important technical requirement is that guardian permission, minor assent, and clinician verification produce linked records in one auditable session. Platforms that cannot demonstrate this should be evaluated cautiously even if their other features are attractive. The FDA guidance on use of electronic informed consent reinforces the audit trail expectation that platforms must satisfy.

4. Plan for asynchronous family review. Even programs that do not formally support asynchronous review will encounter families that want to review materials before the in-person visit. Platforms with secure remote access and preserved chain-of-custody handle this well; platforms without it accumulate workarounds that erode audit trail quality.

5. Train clinicians on the dual workflow. Adult eConsent training does not prepare clinicians for the pediatric variant. Training should explicitly cover the guardian/assent sequence, the age determination logic, the family dynamics that may emerge, and the verification step’s role. CTTI’s project work on informed consent and pediatric trials provides reference materials that can anchor internal training.

The 2025 cohort has done the work of mapping the territory. The 2026 cohort can move materially faster by adopting the patterns that worked, anticipating the failure modes that emerged, and engaging the IRB conversation explicitly. The cost of doing so is small; the cost of repeating the 2025 cohort’s learning curve is large.

References & Sources