xSpecimen: Biobank Specimen Protection

The Problem

Biobank genetic marker data stored at single institutions creates permanent exposure risk. A single breach exposes donor identities and genetic information that can never be changed.

Biobanks store biological specimens alongside genetic markers, phenotype data, and donor identifiers. This data is stored at a single institution with centralized access control. A breach at that institution permanently compromises every donor -- genetic data cannot be rotated or revoked like a password.

Multi-institution research collaborations compound the problem. When biobanks share data for collaborative studies, complete datasets are copied to each participating institution, multiplying the attack surface proportionally.

The Old Way

The PRIVATE.ME Solution

XorIDA splits specimen data across independent research institutions. Reconstruction requires threshold cooperation between independently governed institutions.

Each donor's specimen data is split into N shares distributed across independent biobank institutions. No single institution holds enough data to identify any donor or reconstruct their genetic profile. Collaborative research proceeds through threshold reconstruction with configurable quorum sizes.

The quorum size is configurable per study. A rare disease study across 5 institutions might require 3-of-5 cooperation, while a sensitive population study might require 4-of-5. The donor's consent record specifies the minimum quorum for each authorized use.

The New Way

How It Works

A consent-aware pipeline distributes specimen data across independent institutions with configurable quorum requirements per study.

Use Cases

Developer Experience

xSpecimen provides real-time progress tracking and structured error codes to help biobank developers build reliable, auditable specimen management systems.

Progress Callbacks

Both splitSpecimen() and reconstructSpecimen() operations support onProgress callbacks for tracking long-running operations, especially useful when distributing specimen data across multiple biobank institutions.

const shares = await splitSpecimen(specimenData, {
  institutions: ['mit', 'stanford', 'oxford'],
  k: 2,
  n: 3,
  onProgress: async (event) => {
    switch (event.stage) {
      case 'validating':
        console.log('Validating consent requirements...');
        break;
      case 'splitting':
        console.log('Splitting specimen data via XorIDA...');
        break;
      case 'distributing':
        console.log(`Distributing share ${event.current}/${event.total}...`);
        break;
      case 'complete':
        console.log('Specimen data distributed successfully');
        break;
    }
  }
});

// Reconstruct with progress tracking
const result = await reconstructSpecimen({
  studyId: 'rare-disease-2026',
  institutions: ['mit', 'stanford'],
  onProgress: async (event) => {
    if (event.stage === 'verifying') {
      console.log(`Verifying HMAC for share ${event.current}...`);
    }
    if (event.stage === 'reconstructing') {
      console.log(`Reconstructing from ${event.current} shares...`);
    }
  }
});

Structured Error Handling

xSpecimen uses a Result<T, E> pattern with detailed error structures. Every error includes a machine-readable code, human-readable message, actionable hint, and documentation URL.

interface ErrorDetail {
  code: string;         // e.g., 'CONSENT_NOT_FOUND'
  message: string;      // Human-readable description
  hint?: string;        // Actionable suggestion
  field?: string;       // Field that caused the error
  docs?: string;        // Documentation URL
}

Error Categories

xSpecimen organizes error codes across multiple categories for systematic handling:

Viral Onboarding: < 2 Minute Multi-Site Setup

Zero-config biobank discovery and viral invite flow enable exponential multi-site adoption. Setup time: < 2 minutes (vs 4-8 weeks for manual biobank integration). Target viral coefficient: 1.3 → exponential consortium growth.

The 2-Minute Biobank Onboarding Flow

Traditional biobank integration requires 4-8 weeks per institution: IRB approval process, data use agreement negotiation, HIPAA business associate agreement, technical integration planning, VPN setup, database schema alignment, access control configuration, chain-of-custody documentation, CLIA/CAP compliance verification, security audit, pilot data transfer, and production rollout. xSpecimen reduces initial technical setup to under 2 minutes through zero-config biobank discovery and automatic trust establishment:

// Step 1: Initialize institutional identity (< 30 sec)
$ xspecimen init --name stanford-biobank --type research-institution
{
  "status": "initialized",
  "did": "did:key:z6MksBiobank7sP...",
  "name": "stanford-biobank",
  "type": "research-institution"
}

// Step 2: Connect to a biobank consortium (< 90 sec)
$ xspecimen connect cancer-genomics-consortium
{
  "status": "connected",
  "consortium": "cancer-genomics-consortium",
  "coordinator": "did:key:z6MksCancer...",
  "institutions": ["mit", "oxford", "mayo-clinic"],
  "quorum_requirement": "3-of-5",
  "elapsed_seconds": 1.4
}

// Step 3: Start collaborating immediately
const { connectBiobank } = require('@private.me/xspecimen');
const connection = await connectBiobank('cancer-genomics-consortium');
await splitSpecimen(specimenData, {
  institutions: connection.value.institutions,
  k: 3,
  n: 5,
  studyId: 'melanoma-trial-2026'
});

Zero-Config Biobank Discovery (3-Tier Lookup)

The connectBiobank() function accepts consortium names, institution domains, or URLs and automatically discovers connection details through a 3-tier lookup system:

Viral Invite Flow (< 10 sec creation, < 60 sec acceptance)

The invite system enables exponential consortium growth through effortless institution-to-institution invitations. Creating an invite takes < 10 seconds, accepting takes < 60 seconds, and the invite recipient automatically becomes a potential inviter themselves.

$ xspecimen invite mayo-clinic-biobank --email biobank@mayo.edu
{
  "status": "created",
  "invite_url": "https://xspecimen.to/invite/b8Np2y...",
  "qr_code": "data:image/svg+xml,...",
  "expires_at": "2026-04-19T...",
  "consortium": "cancer-genomics-consortium",
  "message": "Share this link: https://xspecimen.to/invite/b8Np2y..."
}

When the recipient clicks the invite link, they see a one-click acceptance page with the consortium's study info, quorum requirements, and participating institutions. Accepting the invite automatically establishes the connection, adds the institution to the consortium trust registry, and enables specimen data sharing.

Viral Coefficient Model: VC = 1.3

Viral coefficient (VC) measures how many new institutions each existing institution brings. The formula: VC = (collaborations per institution) × (invite rate) × (acceptance rate). xSpecimen targets VC > 1.0 for exponential consortium growth:

Zero-Downtime Migration (Dual-Mode Adapter)

For existing biobank integrations using VPN tunnels, SFTP transfers, or legacy APIs, xSpecimen provides a DualModeBiobankAdapter that runs xSpecimen and legacy transfer mechanisms simultaneously. This enables zero-downtime migration with gradual rollout and usage tracking:

const { DualModeBiobankAdapter } = require('@private.me/xspecimen');

// Create dual-mode adapter (tries xSpecimen first, falls back to legacy)
const adapter = new DualModeBiobankAdapter({
  xspecimen: xspecimenClient,   // Optional: add when ready
  fallback: {
    type: 'sftp',
    host: process.env.BIOBANK_SFTP_HOST,
    credentials: process.env.BIOBANK_SFTP_KEY,
  },
});

// Transfer specimen data (automatically tries xSpecimen → legacy)
const result = await adapter.transferSpecimen(specimenData, {
  institutions: ['mit', 'stanford'],
  studyId: 'lung-cancer-2026'
});

// Track migration progress
const metrics = adapter.getMetrics();
console.log(`xSpecimen usage: ${metrics.xspecimenPercentage}%`);
// Output: "xSpecimen usage: 81%"

// Remove fallback when 100% migrated
adapter.removeFallback();

Comparison: xSpecimen vs Traditional Biobank Integration

Use Cases for Viral Growth

Integration

import { splitSpecimen, collaborateSecure } from '@private.me/xspecimen';

// Split specimen data across 5 institutions (3-of-5)
const shares = await splitSpecimen(specimenData, {
  institutions: ['mit', 'stanford', 'oxford', 'eth', 'tokyo-u'],
  n: 5,
  k: 3
});

// Collaborate with quorum-based reconstruction
const result = await collaborateSecure({
  studyId: 'rare-disease-2026',
  institutions: ['mit', 'stanford', 'oxford']
});

Security Properties

Verifiable Data Protection

Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.

Ready to deploy xSpecimen?

Talk to Ren, our AI sales engineer, or book a live demo with our team.

Ship Proofs, Not Source

xSpecimen generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.

Use Cases