Zero-Knowledge Collaboration Engine

Zero-Knowledge Encrypted Real-Time Collaboration Workbench for Clinical Genetics

Up to 10 Concurrent Collaborators, Email-Verified Access Control, Client-Side AES-256-GCM Encryption, Asynchronous Sync, and Metadata Audit Trails

Biogistry Real-Time Collaboration Workbench & Zero-Knowledge Security Engine
Biogistry Zero-Knowledge Encrypted Real-Time Collaboration Workbench Interface

Client-Side AES-256-GCM Zero-Knowledge Security

All workspace state updates are encrypted in browser memory prior to transmission. Cryptographic keys never reach central cloud servers.

Email-Verified Invites & Authenticated Access

Strict invitation allowlists ensure only signed-in clinicians with matching invited email addresses can access collaboration rooms.

Up to 10 Concurrent Active Collaborators

Multi-user pedigree co-authoring supporting up to 10 team members simultaneously with live peer cursors and node selection rings.

Asynchronous & Synchronous Co-Editing

Team members do not need to be online at the same time. Encrypted state snapshots allow collaborators to review and edit asynchronously.

HIPAA Metadata Audit Trail Logging

Track invitation, access, and room lifecycle metadata for legal compliance while keeping all patient health data strictly private.

Complete Zero-Knowledge Real-Time Collaboration Workbench for Precision Genetics

Multidisciplinary collaboration is central to modern clinical genetics and genomic medicine. Genetic counselors, medical geneticists, oncologists, maternal-fetal medicine specialists, cytogeneticists, and laboratory directors must frequently review complex multi-generational family trees, evaluate variant pathogenicity, and align on surveillance guidelines during case conferences, tumor boards, and grand rounds.

However, traditional clinical collaboration software creates severe operational and regulatory obstacles. Legacy pedigree software forces clinicians to share static screenshot files over email, manually copy-paste clinical updates between isolated workstations, or host unencrypted screen-sharing calls where cursor interactions are laggy and individual edits cannot be co-authored. Cloud-hosted document editors, on the other hand, require uploading Protected Health Information (PHI) to third-party central databases, introducing unacceptable HIPAA, GDPR, and institutional data governance vulnerabilities.

Biogistry solves these enterprise challenges with the Zero-Knowledge Encrypted Real-Time Collaboration Workbench. Built from the ground up for privacy-sensitive medical genetics teams, our real-time collaboration engine combines multi-user co-authoring for up to 10 active collaborators with client-side AES-256-GCM end-to-end encryption. Multiple clinicians can simultaneously draw pedigree structures, adjust kinship connections, enter diagnostic variant records, and inspect chromosome maps on a shared canvas with zero risk of PHI exposure to cloud servers.


How Real-Time Collaboration Works Without Central Data Holding: The Sealed Relay Model

A common misconception in web applications is that co-authoring requires a central cloud server to store, read, and master the unencrypted patient data. In traditional cloud office tools (such as Google Docs, Microsoft 365, or Figma), a central cloud database holds the unencrypted master document. The server inspects every keystroke, stores readable text on cloud hard drives, and parses user data for search indexing. In medical genetics, this model creates grave HIPAA and data sovereignty compliance violations.

Biogistry completely dismantles this misconception by operating on a Zero-Knowledge Sealed Relay Architecture. The central server never holds, reads, or masters your patient health data.

Stage System Node / Entity Encryption & Data Boundary Security & Privacy Guarantee
1. Local State Encryption Host Workstation Browser Encrypts document updates in browser memory using AES-256-GCM key Encryption key remains strictly local; zero plaintext leaves the device
2. Lockbox Transmission Opaque Payload Envelope Prepares binary payload (Uint8Array) prepended with random 12-byte IV Data formatted as unreadable binary blob prior to network transfer
3. Blind Server Relay Biogistry Central Server Verifies recipient email against invitation allowlist and routes blob Server acts as blind courier; holds zero keys and cannot inspect contents
4. Local State Decryption Guest Workstation Browser Decrypts opaque binary payload using local browser URL key fragment Decryption occurs strictly inside recipient browser memory
5. Canvas Render & Sync Shared Pedigree Canvas Merges decrypted CRDT document vector and renders updated canvas Live visual synchronization achieved without central server data holding

The Sealed Lockbox Relay Analogy

To understand how Biogistry enables live multi-user collaboration without holding your data, consider the Sealed Lockbox Relay Analogy:

  1. The Shared Key: Imagine a heavy steel lockbox. Only you and your invited clinical colleagues possess the physical key to open it.
  2. Local Client Assembly: When you add a new patient or update a cancer diagnosis on your pedigree canvas, your workstation browser places the update inside the steel box and locks it using your private key (AES-256-GCM encryption in browser memory).
  3. The Blind Courier: Your browser hands the locked steel box to a courier (Biogistry's central relay server). The courier cannot see inside the box, cannot pick the lock, and possesses zero keys. The courier simply inspects the recipient's security badge (checking that their signed-in email matches your invited guest allowlist) and passes the locked box to your colleague.
  4. Local Client Decryption: Your colleague receives the locked steel box and turns their private key (stored strictly in their workstation browser memory) to unlock the box and render the updated family tree.
  5. Asynchronous Lockboxes: Even when working asynchronously across different shifts, the courier stores only locked steel boxes. When your colleague logs in hours later, they receive the unopened locked box and decrypt it locally on their device.

Under this model, your workstation browser is the sole authority. Central servers act strictly as blind digital couriers, holding zero plaintext data, zero decryption keys, and zero readable patient records.


Overcoming Privacy and Compliance Obstacles in Multidisciplinary Clinical Collaboration

Traditional real-time collaboration platforms were engineered for general document editing, not for the strict compliance, identity verification, and cryptographic isolation demands of precision genomic healthcare. Medical genetics departments face five systemic collaboration hurdles:

1. Unrestricted Share Links and Unauthenticated Access Risks

Generic meeting software allows anyone who possesses a shared link to join a collaboration room. In healthcare settings, unauthenticated link sharing creates grave privacy risks. Biogistry eliminates free-form link access by requiring guest collaborators to be signed into their verified institutional accounts. Room access is restricted strictly to email addresses explicitly invited by the room host.

2. Central Server Plaintext Storage and PHI Exposure

Standard cloud collaboration tools process document states in plaintext on central application servers. Storing patient identifiers, hereditary cancer risk scores, and clinical diagnosis notes on third-party cloud infrastructure creates major regulatory risks under HIPAA, GDPR, and state health privacy laws.

3. Synchronous Only Co-Editing Constraints

In busy clinical schedules, aligning multiple specialists for a live video call or simultaneous editing session is extremely difficult. Traditional tools fail when collaborators are offline, requiring teams to email exported files back and forth. Modern clinical workflows require seamless support for both real-time synchronous sessions and asynchronous co-editing across different shifts and time zones.

4. Absence of Audit Logging for Legal Governance

Institutional health systems require strict administrative accountability for shared data rooms. Without verifiable logs showing who created a room, which email accounts were invited, when participants joined, and when access was revoked, healthcare organizations cannot demonstrate compliance during legal or HIPAA audits.

5. Network Degradation and Packet Latency in Clinical Environments

Hospital enterprise networks frequently feature aggressive deep packet inspection (DPI) firewalls and restricted WebSockets. Standard real-time tools disconnect completely or freeze when encountering corporate proxy delays.


Client-Side AES-256-GCM Zero-Knowledge Security Model and Ephemeral Handshake

The cornerstone of Biogistry's real-time collaboration engine is its Zero-Knowledge Client-Side Encryption (CSE) Architecture. All encryption and decryption operations take place strictly within the client workstation's browser memory using native WebCrypto algorithms.

Security Layer Technical Execution Clinical Privacy Guarantee
1. Key Generation Cryptographically strong AES-256-GCM key generated in browser memory Key exists only on client workstations; never transmitted to server endpoints
2. Ephemeral Key Handshake Key embedded exclusively in URL hash fragment (#key=...) HTTP specification dictates browsers never send hash fragments to web servers
3. Automatic Hash Scrubbing URL hash fragment scrubbed via browser history replacement upon room join Prevents key persistence in browser history, proxy logs, or copy-pasted URLs
4. Email Allowlist Gatekeeper Room relay verifies signed-in user email against host invitation list Blocks uninvited users or non-matching email addresses before socket connection
5. Payload Encryption 100% of document updates and cursor vectors encrypted before transmission Relay servers process only opaque binary payloads (Uint8Array)
6. Metadata Audit Trail Cryptographic logging of room lifecycle, email invites, and join/leave events Stores governance metadata only; zero patient health data is ever recorded

How Ephemeral Key Handshake and Email Gatekeeping Work

When a clinician initiates a new collaboration session, Biogistry generates a fresh 256-bit symmetric encryption key directly in the workstation browser memory. The host specifies the recipient clinician email addresses authorized to join the room. The host application constructs a secure invitation link where the room identifier is placed in the standard URL path, while the secret encryption key is placed in the URL hash fragment (#room=...&key=...).

According to World Wide Web Consortium (W3C) and IETF standards, web browsers strictly omit the hash fragment from HTTP request headers sent over network wires. Consequently, network routers, internet service providers, cloud load balancers, and Biogistry's own relay infrastructure never see, process, or log the decryption key.

Handshake Step Operational Trigger System Security Check Client & Relay Security Action
Step 1: Local Key Minting Host initiates collaboration session Generates 256-bit WebCrypto AES key in browser memory Secret key placed in URL hash fragment (#key=...)
Step 2: Email Allowlist Setup Host specifies recipient clinician emails Authorizes guest emails on room access table Uninvited user accounts or non-matching emails are blocked
Step 3: Identity Verification Guest clicks room invitation link Server checks signed-in user session against allowlist Denies access with 403 response if email does not match
Step 4: URL Hash Scrubbing Authenticated guest enters room Guest browser reads key from local URL hash fragment Immediately scrubs key from URL via history.replaceState()
Step 5: Zero-Knowledge Co-Editing Collaborators edit pedigree canvas All updates encrypted locally before socket routing Relay routes opaque binary blobs with zero server key access

Because central relay servers hold zero decryption keys, Biogistry operates under a strict Zero-Knowledge Architecture: even if a central server were physically compromised or subpoenaed, zero readable patient data, pedigree structure, or clinical notes could ever be extracted.


Asynchronous Co-Editing and Real-Time Multi-User Collaboration

Biogistry supports both high-speed live co-authoring and flexible asynchronous collaboration, enabling genetics teams to work together effectively regardless of schedule alignment.

1. Real-Time Synchronous Co-Authoring for Up to 10 Collaborators

During live multidisciplinary case conferences, up to 10 active team members can open the shared pedigree canvas simultaneously:

  • Fluid Color-Coded Remote Cursors: Live mouse pointers displaying clinician name, professional title, and custom border color.
  • Active Selection Rings: Visual indicators highlighting nodes currently being inspected or edited by colleagues, preventing overlapping modifications.
  • Ephemeral Drag Previews: Smooth drag motion indicators streaming live node position updates across connected screens at up to 30 frames per second.

2. Asynchronous Collaboration (Both Users Need Not Be Online Simultaneously)

Clinicians do not need to be online at the exact same moment to collaborate. In busy hospital settings, a genetic counselor can build a 3-generation pedigree during a morning patient intake and invite an attending oncologist for review.

When the oncologist logs in hours later:

  1. The system verifies the oncologist's signed-in email address against the room allowlist.
  2. The browser fetches the latest encrypted state snapshot preserved in the zero-knowledge room storage.
  3. The oncologist's browser decrypts the workspace locally using the room key.
  4. The oncologist adds tumor pathology notes and updates variant pathogenicity designations.
  5. The updated encrypted snapshot is saved, allowing the counselor to review the changes when returning to work the following day.

3. Automated CRDT Conflict Resolution

Both live multi-user editing and asynchronous updates are managed by Conflict-Free Replicated Data Types (CRDTs). If two clinicians edit different properties of the same individual node (for example, one clinician updates biological sex while another records a new cancer diagnosis), the CRDT mathematical model merges both edits deterministically without document corruption, data loss, or locking popups.


Granular Host Access Control, One-Click Revocation, and Key Rotation

Security governance in medical settings requires strong host authority. Biogistry equips session hosts with administrative controls to manage room membership and secure clinical discussions.

Host Security Management Capabilities:

Host Control Action Operational Mechanism Clinical Security Outcome
Host Identity Verification Host authority verified via cryptographically signed HMAC token Prevents guest participants from claiming administrative privileges
Email Allowlist Enforcement Room server checks guest session against host invited email list Blocks uninvited users or non-matching accounts automatically
One-Click Participant Kicking Host issues encrypted kick packet targeting specific client ID Instantly revokes access, terminates connection, and blocklists client ID
Instant Invite Key Rotation Host generates a fresh AES-256 key without destroying room history Immediately invalidates previous invite links; requires re-inviting active peers
HIPAA BAA Agreement Access Host activates formal Business Associate Agreement controls Enables institutional compliance logging and enterprise governance features
Automatic Idle Session TTL Rolling 12-hour session expiration timer resets on activity Prevents abandoned collaboration rooms from remaining active indefinitely

Instant Participant Revocation Flow

If an unauthorized participant gains access or a team member leaves a consultation early, the room host can open the collaboration management panel and click Revoke Access next to the user's name.

The system executes a two-stage revocation sequence:

  1. Encrypted Application Revocation: The host emits a signed revocation packet to all connected peers. The target client application immediately wipes the local session state and displays a revocation notification.
  2. Relay Hard Termination: The relay server adds the target client ID to an active blocklist, closes the connection with a revocation status code, and rejects any future handshake requests from that client.

HIPAA Metadata Audit Logs for Legal and Institutional Governance

Healthcare organizations operate under strict data governance and regulatory compliance mandates. Demonstrating compliance requires maintaining verifiable logs of data room activity while ensuring protected health data remains completely private.

Biogistry resolves this dual requirement by implementing Metadata-Only Legal Audit Logging.

Audit Event Category Logged Metadata Fields Legal and Governance Purpose
Room Creation Room ID, host user ID, host email, creation timestamp Establishes formal ownership and session initiation timeline
Participant Invitation Invited guest email addresses, granted role (collaborator/viewer), timestamp Documents authorized access permissions for compliance reviews
Access Verification Authenticated user email, client ID, connection timestamp, HTTP status Proves only authorized, signed-in staff accessed the session
Access Revocation Host user ID, revoked participant email, target client ID, revocation timestamp Demonstrates immediate enforcement when revoking team member access
Key Rotation Host user ID, rotation timestamp, updated invite link generation event Records cryptographic key lifecycle management

Strict Privacy Boundary: Zero Patient Data in Audit Records

It is critical to note that Biogistry's audit logging infrastructure records metadata only. Patient names, dates of birth, medical record numbers, pedigree chart structures, calculated disease risk scores, and variant annotations are never written to audit tables or server logs.

Legal teams and hospital privacy officers can export host-signed JSON audit logs to demonstrate exactly who had access to a consultation room, while guaranteeing that patient health information remains 100 percent encrypted and isolated within client browser memory.


Real-World Clinical Workflows and Multidisciplinary Scenarios

Biogistry's Zero-Knowledge Real-Time Collaboration Workbench is designed for diverse clinical and research workflows across modern healthcare networks.

Scenario 1: Hereditary Cancer Multidisciplinary Tumor Board

During a weekly GI cancer tumor board, an attending genetic counselor, surgical oncologist, and molecular pathologist review a complex Lynch syndrome family history.

  • The genetic counselor hosts a collaboration session and explicitly invites the oncologist and pathologist by their institutional email addresses.
  • While the oncologist reviews surgical margins on a secondary screen, the genetic counselor updates the pedigree tree with newly reported maternal aunt colon cancer diagnoses.
  • The molecular pathologist live-selects the proband's node and attaches MSH2 pathogenic variant annotations and IHC staining reports.
  • Upon reaching clinical consensus, the team finishes the live co-authoring session with full assurance of client-side encryption.

Scenario 2: Asynchronous Prenatal and Cytogenetics Case Review

A maternal-fetal medicine specialist and a cytogenetic technologist review a high-risk prenatal case involving a fetal microdeletion detected via amniocentesis microarray.

  • Operating on different clinic shifts, the cytogeneticist opens the shared room, pans across Chromosome 22 in Focus View Mode, and pins a 2.5 Mb deletion at band q11.21 (DiGeorge Syndrome region).
  • The cytogeneticist logs off, leaving the encrypted snapshot saved in room storage.
  • Later that afternoon, the maternal-fetal specialist logs in, authenticates via email match, views the updated idiogram pin, and adjusts the recurrence risk calculation sheet for the neonatal intensive care team.

Scenario 3: Multi-Institutional International Genomic Research Consortium

Researchers across three academic medical centers collaborate on a rare neurodevelopmental disease study involving multi-generational consanguineous families.

  • Up to 10 team members join the zero-knowledge session simultaneously without installing desktop software.
  • The team co-authors complex radial consanguinity pedigrees and computes Wright's inbreeding coefficients across shared workspaces.

Detailed Data Security and Processing Specifications Matrix

The following matrix details how Biogistry processes data categories locally within browser memory, ensuring zero cloud privacy exposure throughout live collaboration sessions:

Data Processing Category Specific Data Elements Handled Local Execution & Encryption Boundary
Symmetric Room Key 256-bit AES-GCM WebCrypto key object Stored strictly in volatile browser memory; never sent to server endpoints
Invite Hash Fragment #room=...&key=... URL hash payload Read by client browser; instantly scrubbed via history.replaceState()
Email Allowlist Verification Signed-in user email against invited email list Authenticated at network edge; blocks uninvited users before connection
Pedigree Topology State Individual nodes, sex, affected status, union pairings Encrypted in client memory using AES-256-GCM before socket transmission
Live Cursor & Drag Vector Pointer (X, Y) coordinates, selected node IDs, active drag positions Encrypted using AES-256-GCM and streamed live to connected room peers
Metadata Audit Trail Room creation, invited guest emails, join/leave timestamps Logged securely in encrypted metadata database; stores zero patient health data
Host JWT Authority Cryptographically signed HMAC SHA-256 token Validated at network edge to enforce host revocation rights
Asynchronous State Sync Encrypted CRDT document update logs and snapshots Stored as opaque binary blobs on relay; decrypted only in client memory

Start Co-Authoring Clinical Genetics Workspaces Securely Today

Streamline your clinical case conferences and genetic counseling workflows with high-speed, zero-knowledge real-time collaboration. Co-author complex pedigree charts, inspect chromosome maps, and collaborate across teams with absolute privacy confidence.

Launch Real-Time Workbench or Explore Clinical Features

Frequently Asked Questions

Does Biogistry hold or store our patient health data on central cloud servers during collaboration?

No. Biogistry operates under a strict zero-knowledge sealed relay model. The central server acts purely as a blind courier passing opaque, client-side encrypted binary lockboxes between authenticated workstations. The server holds zero decryption keys, zero plaintext data, and zero readable patient records. All document state calculations, rendering, and decryption occur exclusively inside your workstation browser memory.

How can team members collaborate asynchronously if they are not online at the same time?

Biogistry supports both real-time synchronous co-authoring and asynchronous collaboration. When a clinician edits a pedigree chart, their browser encrypts the updated document state vector locally using AES-256-GCM before syncing. When a colleague logs in later, their authenticated browser fetches the latest encrypted snapshot and decrypts it locally in memory. Clinicians do not need to be online simultaneously to co-author family trees.

How does email-verified access control prevent unauthorized room access?

Biogistry strictly enforces email-authenticated access control. Session hosts must explicitly invite guest collaborators by their email address. When a guest attempts to join a room, the system verifies that the guest is signed in and that their authenticated email matches the room invitation allowlist. Free-form link sharing is blocked; uninvited users or non-matching accounts are denied access immediately.

What information is recorded in the room audit log for legal and compliance purposes?

To meet HIPAA and institutional governance standards, Biogistry records strict metadata-only audit logs. Audit logs record room creation timestamps, host account details, invited guest emails, participant join and leave times, and access revocation events. Patient health data, pedigree structures, variant details, and consultation notes are never recorded in audit logs.

How many collaborators can co-author a single workspace simultaneously?

Biogistry supports real-time collaboration for up to 10 active team members simultaneously per room. Collaborators see real-time peer presence, color-coded live pointer cursors, active node selection rings, and fluid drag positioning on the shared pedigree canvas.

Does real-time collaboration require installing desktop software or browser plugins?

No. Biogistry operates entirely within modern Web standards (HTML5, WebCrypto API, and WebSockets). Collaborators join sessions instantly via web browser on any operating system, including Windows, macOS, Linux, iPadOS, and Android, with zero installation required.

Experience Biogistry Pedigree Builder

Build standardized genetic pedigree charts online with zero PHI transmission and zero double data entry.