Why EHDS Needs Open Infrastructure

EHDS introduces shared obligations across Europe, but it does not provide a shared implementation layer.

This creates a major strategic risk. Without reusable infrastructure components, Member States and organisations may independently rebuild:

• policy engines
• mediation layers
• interoperability mappings
• audit systems
• secure processing mechanisms

The result could be fragmented architectures, inconsistent governance models, increased compliance costs, and reduced interoperability.

This publication explains why open infrastructure is essential for the long-term success of EHDS.

The article explores the role of open-source implementation patterns, transparency and auditability in public infrastructure, reusable governance-aware components, and interoperability acceleration through shared standards.

The publication also positions OpenEHDS as an open implementation initiative for EHDS operational reality.

Rather than building proprietary platforms or monetising health data, OpenEHDS focuses on reusable infrastructure, transparent governance, interoperability primitives, and compliance-by-design building blocks.

The shared problem is implementation, not legal intent

The EHDS Regulation creates common legal obligations, but many operational choices remain to be implemented by Member States, health data access bodies, health data holders and vendors. Dataset catalogues, data quality labels, SPE controls, permit workflows, pseudonymisation pipelines, audit logs and output review processes all need working software.

If each jurisdiction builds these layers independently, the result may be formally compliant but practically fragmented. Researchers will face different application experiences. Institutions will procure incompatible components. Vendors will optimise for proprietary ecosystems. Smaller organisations may struggle to participate at all.

Open infrastructure reduces this risk by making reference components visible, reusable and auditable. It does not replace national legal choices. It gives them a common technical foundation.

Why open source is a trust mechanism

In health data infrastructure, transparency is not decoration. It is part of legitimacy. Public institutions should be able to inspect how permits are enforced, how logs are generated, how output rules are applied, and how policy decisions flow into technical controls.

Open-source components also help procurement. Instead of buying opaque logic, institutions can procure services, support and deployment around shared standards and inspectable implementations. This lowers dependency on a single supplier and makes interoperability easier to verify.

Closing thought

EHDS will succeed only if its common legal framework is matched by common implementation capacity. Open infrastructure is not a side project. It is one of the practical ways to prevent the European Health Data Space from becoming a patchwork of incompatible, expensive and opaque systems.