Pre-Flight Mission Control

How do clinical coordinators configure and deploy digital forms using Pre-Flight Mission Control?

Before any consent document can be sent to a patient, it must pass through Pre-Flight Mission Control. This centralized dashboard acts as the final gatekeeper, allowing clinical coordinators to configure participant identities, lock down security preferences, establish patient comprehension checks, embed educational media, and execute the final cryptographic seal.

What is Pre-Flight Mission Control?

Pre-Flight Mission Control is the command dashboard that bridges document creation and patient deployment. Think of it as a pre-launch checklist. It ensures that before a legal document leaves the clinical team’s control, all regulatory safety nets—such as signature mappings, identity gates, geofencing coordinates, and comprehension quizzes—are fully locked, validated, and ready for execution.

The dashboard automatically adapts its checklist based on the document’s legal consent category:

Standard Clinical Consent (4 Steps): Dedicated to inpatient admissions, surgical procedures, and standard anesthetic consents. It is organized into:
1. Signers & Identity
2. Comprehension (Teach-Back)
3. Engagement (Education)
4. Final Review & Lock
Research Consent (5 Steps): Enforced for clinical trials and research-focused interventions. Due to stringent international guidelines and privacy requirements, it introduces a dedicated, non-downgradable Security & Access phase as Step 2, separating enrollment manifest validations from standard identity configurations.

How do you configure Signers & Identity in Step 1?

The first stage of Pre-Flight defines who must sign the active document and under what conditions their identity is verified.

What is the standard Circle of Care manually entered signer setup?

For standard clinical procedures, coordinators manually construct the Circle of Care. This involves entering the exact names and contact details (email and mobile numbers) for all required signatories (e.g., the Subject, Impartial Witness, Healthcare Provider, or Interpreter). The coordinator also defines whether verification requires individual PIN codes or a shared global PIN.

What is the research study setup using an Enrollment Manifest CSV?

For clinical trials, manual subject data entry is bypassed to protect patient privacy. Instead, coordinators upload a pre-validated Enrollment Manifest in a standard table format (CSV). The system parses this manifest to map study subjects, their pre-allocated identifiers, and secure authentication tokens. The coordinator then manually assigns the Principal Investigators and witnesses to complete the signing loop.

How is Geographic Hardening configured to lock down signing via strict GPS?

To prevent out-of-jurisdiction signing and protect institutional liability, coordinators can toggle Geographic Hardening:

GPS Capture: Clinical coordinators capture the precise satellite coordinates (latitude and longitude) of the clinic or hospital facility using the browser’s location sensor.
Lockdown Radius: Establish a strict boundary (ranging from 100 meters to 10 kilometers) around the facility.
Strict Enforcement: The system captures the signer’s real-time GPS location when they attempt to sign. If they are outside the lock-down radius, access is instantly denied. There is no administrative override or clinical bypass for this lock.

In Research Mode, Step 2 displays a summary of the platform-enforced Security Auth Gates that will safeguard the document. These verification parameters are locked in automatically based on the regulatory risk profile of the selected consent category and cannot be manually downgraded.

The security gates function through a multi-tiered verification sequence that balances maximum patient ease-of-use with legally binding non-repudiation:

Universal Security Gates (All Form Types):
- Automated Human Verification: Uses an automated human-verification challenge (Turnstile) to block robotic queries and prevent database denial-of-service attempts.
- Secret Access PIN: Required to be entered before showing any details, titles, or metadata of the clinical form. This secret is shared with the participant externally.
- One-Time Passcode (OTP): A temporary code dispatched directly to the participant’s verified email address to confirm active inbox access.
Enhanced Verification Gates (Research and Parental Consent):
- Biometric Passkey Sign-Off: The most robust verification gate. Rather than demanding biometrics before viewing, biometric device-unlock verification is strictly requested at the very end of the workflow, only when the participant clicks to finalize their signature and submit the signed document. Using the device’s native fingerprint scanner or facial recognition (e.g. Face ID, Touch ID, or Windows Hello), the participant performs a simple one-click verification that securely binds the signature. (Note: This seamless flow will be explained in comprehensive detail in the Security Architecture documentation).

Additionally, the system automatically uses the participant’s secure token to derive unique cryptographic keys, creating individual encrypted envelopes for the clinical data. This ensures patient records remain unreadable to unauthorized third parties, satisfying strict privacy standards.

How is comprehension verified using the Step 3 Teach-Back quiz protocol?

To satisfy legal standards of true informed consent, clinicians can activate the Teach-Back Protocol. This comprehension safety net ensures that patients actually understand what they are consenting to before signing:

AI-Powered Analysis: The platform’s clinical engine analyzes the actual sections of your custom document (such as risk lists, procedural steps, and recovery guidelines).
Quiz Generation: The system automatically generates a set of multiple-choice comprehension questions tailored specifically to your document’s text.
Unlock Requirement: The patient must successfully pass this multiple-choice quiz during their signing session. If they fail, the signature panels remain locked.
Attempt Restrictions: To prevent study manipulation and ensure clinical integrity, the system limits the coordinator to 3 AI quiz generation attempts per document.

How do clinicians increase patient engagement using Step 4 Education Vault and Clinical Chat?

Patient comprehension is enhanced by supporting self-paced review and direct communication:

Education Vault: Coordinators can embed up to 3 educational video resources (from YouTube or Vimeo) detailing the procedure. You can toggle Enforced Watch Time to ensure the patient watches the entire clinical video before the signature fields unlock.
Clinical Chat: Toggling this feature enables an interactive chat messenger box. If a patient is reviewing the document at home and has questions, they can type them directly into the interface, sending an alert back to the clinical care team.

How does the final Forensic Lock and deployment process work in Step 5?

The final phase of Pre-Flight validates the entire package for deployment. The system runs an automated check to verify that all placed signature blocks on the canvas are successfully mapped to active signatories in the care circle.

Once finalization is triggered:

Immutable SHA-256 Seal: The master consent template is frozen and signed with an immutable cryptographic footprint. Any subsequent change to the document text will instantly void the seal.
End-to-End Encryption: The workspace key is encrypted under each signer’s verified credential, creating fully secure individual content envelopes on the server.
Universal Master Enrollment Link: For clinical trials, a single, universal enrollment portal is generated. When participants access this link, the system securely clones the study template, generating a unique instance for their trial session.
Same-Room Session: For co-located or bedside visits, the system launches a terminal display showing a dynamic clinic QR code. The clinician displays the screen, and the patient scans the QR code on their personal smartphone or tablet to begin the sequential signing workflow.