Technical building blocks you run on-premise—aligned with EHDS policy discussions, without turning the website into legal advice.
Discussions around the European Health Data Space (EHDS) focus on machine-readable dataset catalogs, data-holder-side pseudonymisation, and controlled environments for secondary use—exact obligations depend on applicable law and your role. Many sites are still assembling an integrated stack for that. We build technical infrastructure you run on-premise, in your environment, without mandatory external cloud lock-in. We are a small team—we state scope and limits clearly.
EHDS is an evolving policy area: what applies to your organisation depends on applicable law, your role, and your contracts. We provide engineering and technical orientation. Legal assessment, formal compliance decisions, and DPO work remain with you and your professional advisors.
EHDS-oriented programmes typically call for machine-readable dataset catalogs from data holders (subject to applicable rules). Ferrum DRS provides the technical base with structured dataset metadata that can be exported into catalog formats. A dedicated HealthDCAT-AP generator can automate this export path.
EHDS-related guidance often stresses early pseudonymisation at the data-holder side—not only far downstream (confirm duties for your case). BioResearch Assistant supports privacy-conscious pseudonymisation on-premise so raw source data stays under your institutional control.
For secondary use, controlled environments with auditable execution and limited data movement are a common planning theme. Ferrum WES/TES offers a technical baseline: controlled workflow execution, audit logging, and clear process boundaries—implementation remains your responsibility.
Synaptic Four provides technical IT consulting and infrastructure only. Analyses look at technical and organisational-technical fit—they are not legal advice, not a DPO decision, and not a compliance verdict for your organisation.
Consulting, 2-3 weeks, technical analysis
Technical review of your infrastructure against typical EHDS planning themes, with a prioritised action plan. Optional add-on modules cover secondary-use intake (SPE/metadata/HDAB pathway) and MII/FDPG gap analysis. No legal verdict; engineering orientation.
Learn more →Custom development, On-premise, BUSL-1.1
Project-based implementation on top of Ferrum: catalog export baseline, SPE baseline configuration, and integration with existing pseudonymisation workflows. Legal responsibility stays with you.
Learn more →