What OpenEHDS builds and what it does not do

OpenEHDS is an enabler: it builds reference components and architecture patterns for EHDS secondary use.

What we build

• permit-aware dataset assembly engines
• policy enforcement modules for access and purpose constraints
• connectors across data holders, access bodies, and secure environments
• audit, logging, lineage, and TTL lifecycle components

What we do not do

• we do not act as a health data access body
• we do not host or monetize medical data
• we do not operate secure processing environments

This role separation builds trust and improves component reusability across national implementations.