Skip to content

Minor Assent & Same-Device Handoff

Clinical Guide: Minor Assent & Same-Device Handoff

This guide explains how the ConsentCollect platform securely manages pediatric consent and child assent in compliance with clinical trial regulations (such as FDA 21 CFR Part 11 and HHS pediatric research guidelines).


1. Clinical Overview

In pediatric research and clinical procedures, obtaining consent is a dual-step process:

  1. Parental Permission / Guardian Consent: The adult legally responsible for the child reviews the full, detailed Informed Consent Form (ICF) and executes a signature.
  2. Minor Assent: If the child is of assent-capable age (typically 7–17 years old), they must review a simplified, age-appropriate explanation of the procedure and provide their assent.

ConsentCollect automates this sequence on a single device, ensuring children are not subjected to technical hurdles (like emails, PINs, or geofences) while cryptographically linking both signatures on the ledger.


2. Setting Up Minor Assent in the Builder

When creating a form or editing its settings, toggle Minor Assent Capable to True.

Step 2: Configure the Two Document Views

Once enabled, the Builder Workspace displays two canvas tabs:

  • Parental ICF (Adult View): Set up the full medical or study details, required initials, checkboxes, and the Parent/Guardian signature slot.
  • Minor Assent (Child View): Set up a simplified explanation of the procedure written at a 3rd-to-4th-grade reading level.

[!IMPORTANT] To ensure compliance, the platform automatically appends a non-removable Child Signature Slot to the Assent blueprint. You cannot finalize or deploy the form if the Assent view contains no sections.


3. Pre-Flight Circle of Care Setup

During the Pre-Flight check, clinicians map participants to the required signature slots.

For the Minor Assent participant:

  • Automatic Autofill: The minor’s legal name defaults to "Minor Patient", email defaults to "handoff@consentcollect.com", and PIN code defaults to "0000".
  • Enforced Lock: All minor participant fields are strictly read-only and locked in the UI to prevent clinicians from accidentally assigning separate emails or security gates to the child.
  • CSV Manifests (Trial Mode): If uploading a high-throughput enrollment CSV, you do not need to supply email or secret columns for the child. The validation engine automatically bypasses minor roles to prevent setup failures.

4. The In-Person Signing Workflow

When the clinician deploys the consent request, the signing sequence proceeds in a strict, regulated order:

StepSignatory / ActorAction & InterfaceCompliance Status
1Parent / GuardianOpens email invitation link, completes required initials, checkboxes, and signs full document.Guardian Permission Signature committed to ledger.
2SystemLocks Parental ICF signature and displays the Pass the Device handoff transition screen.Triggers handoff state; saves parent signature state.
3Parent / GuardianHands physical device over to the child and clicks “Launch Child Assent”.Initiates child-assent token session.
4Minor PatientReviews simplified assent text (with optional Read-Aloud audio player).Pre-signing verification bypass active.
5aMinor Patient (Agree)Signs the child-assent signature canvas pad.Both signatures cryptographically bound. Forensic audit logs same-device inheritance. Form status sets to completed.
5bMinor Patient (Refuse)Clicks “I do not want to do this / Decline” and confirms refusal.Form status sets to void. voidReason logged as Minor declined assent. Principal Investigator is alerted.

1. Guardian Signature

The Parent/Guardian receives the email link, verifies their identity (via PIN, OTP, or Passkey), completes the required checkmarks/initials, and signs.

2. Device Handoff Screen

Immediately upon the guardian committing their signature, the screen transitions to the Device Handoff Transition. The page instructs the parent to hand the device to their child and provides a prominent “Launch Child Assent” trigger.

  • Crash Recovery / Resumption: If the browser crashes, is closed, or loses power after the parent signs, clicking the parent’s original email invitation link will automatically redirect directly to the Device Handoff Screen. The parent does not need to sign again, and the child’s progress is not lost.

3. Child-Friendly Signing View

When the Child Assent launches, the interface adapts to pediatric accessibility standards:

  • Volume Reader (“Read to Me”): A text-to-speech player is embedded at the top of the page, allowing children to listen to the assent document read aloud.
  • Accessibility Enhancements: Touch targets and buttons are padded to at least 56px and the signature pad canvas is expanded by 40% to accommodate developing motor skills.
  • Verification Bypass: Minors are exempt from geofences, PIN codes, quiz gates, and OTP codes. They bypass all ingress gates to prevent friction.
  • Persistent Branding: The clinical institution’s logo and branding remain permanently visible at the top of the screen to maintain professional context.

4. Assent Refusal Pathway

Pediatric guidelines mandate that children have the right to refuse participation.

  • A prominent “I do not want to participate / Decline” button is rendered on the minor’s view.
  • If clicked, a child-friendly confirmation dialog appears: “Are you sure you do not want to participate?”
  • Confirming this instantly voids the entire consent request. The database logs the void state as Minor declined assent, and the investigator is notified.

5. Forensic Integrity & Audit Logs

ConsentCollect maintains a strict forensic audit trail for pediatric consent:

  • Cryptographic Binding: During finalization, the parent’s signature seal binds the SHA-256 hashes of both Parental ICF sections and Minor Assent sections combined into a single tamper-evident cryptographic block.
  • Audit Trail Inherited Log: When the minor signs, the system fetches the preceding guardian signature and appends the following log to the immutable audit ledger:

    "Authentication inherited via continuous same-device session from Guardian [Guardian's Name] ([Guardian's Participant ID])"

  • Redacted Public Keys: Investigator and clinician secret access tokens inside metadata are automatically redacted in public queries to prevent public exposure.
  • Combined PDF Print: When printed, the platform outputs both the Parental ICF and the simplified Minor Assent document stacked sequentially in one unified PDF file.