AuroraMed v0.2.0 is a synthetic-data pilot. See exactly what's built →

Ledger, sync, offline and hardware requirements · C0965

How would server-to-server clinical transfers be protected?

Designed, not yet built

Short answer

The server-to-server transfer, three streams part of the specification (REQ-3401) says server-to-server clinical data transfer must use three simultaneous streams with interleaved decoy traffic and secret sharing so no single stream carries decryptable content. No. The specification describes it, but the pilot does not include it. Acceptance check: capturing any one stream yields no plaintext; test decrypt from one or two streams fails.

This is designed, not built.

Specification item
REQ-3401
Specification priority
P0 (of P0 to P3)
Tiers
Medium, Large

Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.

Related answers

See it in context: Server-to-server transfer, three streams · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo