Open, auditable infrastructure for EHDS secondary use
OpenEHDS is a neutral, non-commercial foundation initiative building interoperable, privacy-by-default, and operationally realistic components for EHDS. We focus on making complex secondary use workflows publicly understandable and practically deployable.
See the Programs
Mission grounded in EHDS reality
OpenEHDS works from a simple premise: EHDS needs infrastructure that is interoperable by design, privacy-preserving by default, operationally realistic, and publicly understandable.
- Built as a neutral, non-commercial foundation model
- Designed to support cross-sector and cross-country collaboration
- Created as a practical bridge between legal frameworks and technical implementation
- Structured to support institutions, regulators, patient groups, researchers, and technology teams
Focused on secondary use end-to-end
We focus on EHDS secondary use, where regulatory, technical, and organizational complexity is highest. The scope covers the full lifecycle of controlled data access and processing.
- Preparing datasets for secondary use
- Controlled access based on time-bound and purpose-bound data permits
- Operation inside secure processing environments
- Auditability, transparency, and lifecycle governance
- Policy-aware handling of opt-out rules and legal exceptions
Open components, not a data operator
EHDS requires a controlled data mediation layer. OpenEHDS makes this layer transparent and reusable through open reference components, while explicitly not acting as a data host or permit authority.
- Permit-aware dataset assembly engines
- Policy enforcement modules for purpose limitation and access constraints
- Connectors across data holders, access bodies, and secure environments
- Audit, logging, lineage, TTL, and controlled deletion mechanisms
- Not a health data access body, not a secure processing operator, not a commercial data platform
Signals from early collaboration
These are deliberately placeholder quotes shaped to reflect the intended value proposition of the foundation.
A clear software and publication structure makes it much easier to explain where the project is headed and what can be reused.
Implementation Lead
Regional Delivery Partner
The strongest part of this setup is that it looks like a real operating platform, not a temporary placeholder microsite.
Technical Advisor
Interoperability Working Group
A visible GitHub path and a structured community page lower the threshold for getting involved.
Open Source Maintainer
Contributor
Even placeholder content can build confidence if the architecture clearly communicates programs, roadmap, and operating logic.
Programme Sponsor
Public Sector Stakeholder
Join the neutral implementation dialogue
OpenEHDS invites institutions, regulators, patient organizations, researchers, and technology teams to co-create reusable, auditable EHDS components for secondary use.
Contact OpenEHDS