What the platform does

Health Data Safe runs a health-data platform on which each person holds their own record and shares it through explicit, revocable, purpose-scoped permissions. Every access is recorded in an audit log.

This page describes what exists today. Every component, with its version and its current status, is published at docs.datasafe.dev. We would rather you read the documentation than take our word for it.

Each person has an account that holds their health record. Sharing happens through a connection a person grants to a provider, a researcher or an application, and that connection can be withdrawn.

The account and authentication service handles sign-in, registration, multi-factor authentication and the account pages. The patient application is where a person reads and adds to their own record. The doctor dashboard is what a clinician sees once a patient has granted access.

The standards it speaks

The data model is published as YAML definitions for items, streams, event types and data sources, and it can be browsed through the data model browser. Condition coding for the rare disease registry maps onto ORPHAcodes and a shared minimum data set.

SMART on FHIR applications are supported, so an application written for that standard can work against an HDS account.

The datasets service is a REST API for medication datasets covering WHO-ATC, RxNorm and SNOMED, together with Swiss and French product data.

The integrations that exist today

A bridge connects an outside source to a person’s account, with that person’s permission.

Where the data lives

Each person chooses a region when they register, either Switzerland, hosted with Exoscale, or the United States, hosted on AWS in us-east-1.

Health data stays in the chosen region. That covers events, streams, time-series, attachments and audit logs. Only a small directory replicates across regions, to route usernames and keep accounts unique, and it does so using one-way keyed pseudonyms.

Getting the data out

Download My Data lets any account holder export their complete account as machine-readable archives, without asking anyone. The documentation ties that module to the obligations it discharges: the right of access and the right to portability under the GDPR, the individual right of access under HIPAA, and the corresponding rights under the revised Swiss Federal Act on Data Protection.

Exporting everything is also how a participant leaves, and the module exists for that.

Health Data Safe acts as data controller. A partner that processes data on the Foundation’s instructions becomes a processor, with the obligations that follow.

The published compliance matrix maps each right and duty under the GDPR, HIPAA and the Swiss nLPD onto the specific technical mechanism that satisfies it, and it comes with agreement templates.

The code is open

The platform libraries are published as open source: the core data-model library, the form components, the timeline component, the cycle interface components, the style theme and the bridge framework. An organisation that adopts this infrastructure is not adopting a dependency it cannot inspect.

What is not in the platform today

Differential privacy, synthetic data generation and federated analysis are not part of the platform. Our team works with these techniques and knows them well, and a partner whose protocol calls for one of them can have it built. We would rather say so than imply a capability that does not ship.


The full documentation, including the component status table with demo and production versions, is at docs.datasafe.dev. If you want to discuss building on this, start a collaboration.