The EHDS Compliance Matrix shows the approval chain status for every dataspace participant. Under EHDS Articles 45–53, secondary use of health data requires a complete chain:
- Access Application — data user submits a request with purpose, justification, and ethics approval (Art. 45)
- HDAB Review & Approval — the national Health Data Access Body evaluates the request (Art. 46)
- Dataset Grant — approval is linked to a specific dataset via GRANTS_ACCESS_TO (Art. 49)
- Contract — a data usage contract governs the DataProduct described by the dataset (Art. 53)
Click any row to see the detailed approval chain breakdown. HDAB authorities (MedReg, HealthGov) review applications rather than submitting them.
Participant Compliance Matrix
Loading compliance data from graph…
EHDS Verifiable Credentials
DCP credential definitions registered on IssuerService — presented during DSP negotiation
Loading…
DCP Trust Chain — Credential Presentation Flow
IssuerService→ signs VC →IdentityHub→ stores →DCP Presentation→ verifies →Policy Engine→ evaluates →✓ Access Granted
Trust Center — Pseudonym Resolution
EHDS Art. 50/51 — HDAB-designated trust centers enabling cross-provider longitudinal patient linkage without exposing real identities to researchers. Provider pseudonyms are resolved to research pseudonyms inside the Secure Processing Environment only.
Loading trust centers…
Security Model — Threat Mitigations
⚠Researcher accesses raw dataSPE + TEE enforce aggregate-only output (k ≥ 5)
⚠Provider re-identificationProvider-specific pseudonyms (local key per provider)
⚠Cross-provider linkage leakTrust Center under HDAB authority only
⚠Trust Center collusionStateless or key-split design; full audit trail
⚠Pseudonym reversalOne-way HMAC mapping; revocable by HDAB