Proposal for a Regulation on the European Health Data Space (EHDS)vsTEFCA — Trusted Exchange Framework and Common Agreement
See exactly how Proposal for a Regulation on the European Health Data Space (EHDS) controls map to TEFCA — Trusted Exchange Framework and Common Agreement. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
Proposal for a Regulation on the European Health Data Space (EHDS) maps to TEFCA — Trusted Exchange Framework and Common Agreement with 20% coverage across 5 directly mapped controls. Analysis of 25 Proposal for a Regulation on the European Health Data Space (EHDS) controls identifies 20 compliance gaps — primarily concentrated in Secondary Use - Governance and Access.
Source: TheArtOfService Knowledge Graph | 25 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 13 of 13 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Primary Use - Infrastructure and Governance(2 mappings)
EHR Systems Requirements(11 mappings)
Related Comparisons
Other Proposal for a Regulation on the European Health Data Space (EHDS) comparisons
Other TEFCA — Trusted Exchange Framework and Common Agreement comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between Proposal for a Regulation on the European Health Data Space (EHDS) and TEFCA — Trusted Exchange Framework and Common Agreement?
Proposal for a Regulation on the European Health Data Space (EHDS) has 25 controls across its framework, while TEFCA — Trusted Exchange Framework and Common Agreement covers 23 controls. Direct mapping analysis identifies 5 overlapping controls (20% coverage). The frameworks diverge most significantly in Secondary Use - Governance and Access, where 5 Proposal for a Regulation on the European Health Data Space (EHDS) controls have no direct TEFCA — Trusted Exchange Framework and Common Agreement equivalent.
How many controls map between Proposal for a Regulation on the European Health Data Space (EHDS) and TEFCA — Trusted Exchange Framework and Common Agreement?
Of 25 total Proposal for a Regulation on the European Health Data Space (EHDS) controls, 5 map directly to TEFCA — Trusted Exchange Framework and Common Agreement controls — representing 20% coverage. The remaining 20 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping Proposal for a Regulation on the European Health Data Space (EHDS) to TEFCA — Trusted Exchange Framework and Common Agreement?
20 Proposal for a Regulation on the European Health Data Space (EHDS) controls have no direct equivalent in TEFCA — Trusted Exchange Framework and Common Agreement. The highest concentration of gaps is in Secondary Use - Governance and Access with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between Proposal for a Regulation on the European Health Data Space (EHDS) and TEFCA — Trusted Exchange Framework and Common Agreement?
The domain with the highest gap count is Secondary Use - Governance and Access (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.