xScan: Medical Imaging Protection

The Problem

Medical images stored on single servers are high-value breach targets. A single compromise exposes thousands of patient scans containing embedded patient identifiers.

DICOM files from MRI, CT, and X-ray scanners contain far more than pixel data. They embed patient names, dates of birth, medical record numbers, referring physicians, and diagnostic codes. A PACS (Picture Archiving and Communication System) breach exposes not just images but complete patient identities linked to their medical conditions.

Healthcare imaging data is growing exponentially. A single MRI study generates 500MB to 2GB. Hospitals store millions of studies, creating massive centralized targets. Traditional encryption protects data at rest but leaves a single point of decryption failure.

The Old Way

The PRIVATE.ME Solution

XorIDA splits large imaging files with automatic chunking optimized for DICOM structure. No single storage node holds enough data to reconstruct any portion of any image.

Medical images are automatically chunked based on configurable sizes optimized for the imaging modality. Each chunk is independently split into N shares and distributed across separate storage nodes. Per-chunk HMAC signing ensures any tampering is detected at the individual chunk level.

Reconstruction requires the threshold number of shares for every chunk. An attacker who compromises a single storage node obtains fragments that are information-theoretically impossible to reconstruct without the remaining shares.

The New Way

How It Works

A multi-stage pipeline handles large medical images with automatic chunking, parallel splitting, distributed storage, and chunk-level integrity verification.

Use Cases

Integration

import { splitImage, reconstructImage } from '@private.me/imagesplit';

// Split a DICOM image across 3 nodes (2-of-3 threshold)
const shares = await splitImage(dicomBuffer, {
  n: 3,
  k: 2,
  chunkSize: 1048576  // 1MB chunks
});

// Reconstruct from any 2 of 3 share sets
const image = await reconstructImage(
  [shares[0], shares[2]]
);

Viral Onboarding: < 2 Minute M2M Setup

One-Line Connection (SDK)

import { connect } from '@private.me/agent-sdk';

// Zero-config discovery
const imagingNode = await connect('radiology-pacs-node');

// Use immediately for secure image storage
const result = await imagingNode.send({
  type: 'store-imaging-study',
  data: { studyID: 'MRI-20260412-001', shares: dicomShares }
});

Network effects: When your imaging partner already uses Xlink, connection is instant. When they don't, you send an invite (< 10 sec), they accept (< 60 sec), and all future connections are instant.

CLI Alternative

# Initialize once
xlink init

# Connect to imaging node
xlink connect radiology-pacs-node

# Invite a healthcare partner to join
xlink invite partner-imaging-center

Zero-Downtime Migration

import { DualModeAdapter } from '@private.me/agent-sdk';

// Both Xlink AND your existing API key work
const adapter = new DualModeAdapter({
  xlink: imagingAgent,
  fallback: { apiKey: process.env.PACS_API_KEY }
});

const result = await adapter.call('store-study', {
  studyID: 'MRI-20260412-001',
  shares: dicomShares
});

// Track adoption progress
console.log(adapter.getMetrics());
// { xlinkPercentage: 73, xlinkCalls: 146, fallbackCalls: 54 }

As your imaging partners adopt Xlink, your xlinkPercentage automatically increases. No code changes required.

Why Medical Imaging Needs Viral M2M

• Time-critical diagnostics: Radiologists need instant access to imaging studies. API key setup delays can postpone critical diagnoses.
• Multi-site coordination: Healthcare involves PACS systems, teleradiology networks, research archives, and AI training nodes. Manual key exchange across 5+ parties is untenable.
• Network effects: Each hospital's adoption reduces friction for their entire imaging ecosystem—partners connect instantly to multiple imaging nodes.

Growth projection: Month 1 (100 imaging centers) → Month 12 (74,185 imaging centers) with VC = 1.2

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 xScan?

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

Ship Proofs, Not Source

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

Use Cases