Skip to content
ZINOS
A data governance office at dusk, closed folders on a long table, a server room behind glass.

A health data holder, on your own terms.

Describe your datasets and answer access requests under the European Health Data Space from one governed layer inside your hospital.

Example

Under the European Health Data Space, hospitals become health data holders: they describe their datasets for national catalogues and supply data when an access body approves a request.

In the data hub, the records you must describe already sit together, so descriptions come from what you hold, and every release is logged.

Three duties, answered from one place.

One set of permissions covers every record you describe and supply.

A hospital records office at dusk, archive shelving and one quiet workstation.
  • Dataset descriptions drawn from the records actually held
  • Every record type under one permission system
  • Releases prepared from one layer, every release logged
  • Records kept in raw form, so new requests need no re-collection

How a data request is answered.

  1. Dataset described
  2. Request approved
  3. Release prepared
  4. Release logged

A national paediatric oncology register runs on this software today.

Questions data holders ask.

Does the platform meet the EHDS duties for us?

No software can. The platform is EHDS-aligned: it holds and governs the records the duties cover, and your hospital meets the duties.

When do the duties begin?

Secondary-use duties begin in March 2029, with trial and genomic data following in March 2031.

Does this apply outside the EU?

No. This page covers EU hospitals. Our regional pages set out the rules elsewhere.

A hospital records office at dusk, archive shelving and one quiet workstation.

Prepare your data before 2029.

Book a call about the datasets your hospital holds, and invite your DPO, IT, and quality leads.

Book a demo