<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v27i1e69813</article-id>
      <article-id pub-id-type="pmid">40266673</article-id>
      <article-id pub-id-type="doi">10.2196/69813</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Interoperability Framework of the European Health Data Space for the Secondary Use of Data: Interactive European Interoperability Framework–Based Standards Compliance Toolkit for AI-Driven Projects</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Sarvestan</surname>
            <given-names> Javad</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Thun</surname>
            <given-names>Sylvia</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Bushuyev</surname>
            <given-names>Sergiy</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Hussein</surname>
            <given-names>Rada</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Ludwig Boltzmann Institute for Digital Health and Prevention</institution>
            <addr-line>Lindhofstraße 22</addr-line>
            <addr-line>Salzburg, 5020</addr-line>
            <country>Austria</country>
            <phone>43 57 255 82713</phone>
            <email>rada.hussein@dhp.lbg.ac.at</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1257-4848</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Gyrard</surname>
            <given-names>Amelie</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3938-5617</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Abedian</surname>
            <given-names>Somayeh</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6427-6941</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Gribbon</surname>
            <given-names>Philip</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7655-2459</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Martínez</surname>
            <given-names>Sara Alabart</given-names>
          </name>
          <degrees>MEng</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0006-2862-3447</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Ludwig Boltzmann Institute for Digital Health and Prevention</institution>
        <addr-line>Salzburg</addr-line>
        <country>Austria</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Trialog</institution>
        <addr-line>Paris</addr-line>
        <country>France</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Fraunhofer Institute for Translational Medicine and Pharmacology</institution>
        <addr-line>Frankfurt am Main</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Fraunhofer Cluster of Excellence for Immune-Mediated Diseases (CIMD)</institution>
        <addr-line>Frankfurt</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>TIC Salut Social Foundation</institution>
        <addr-line>Barcelona</addr-line>
        <country>Spain</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Rada Hussein <email>rada.hussein@dhp.lbg.ac.at</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>23</day>
        <month>4</month>
        <year>2025</year>
      </pub-date>
      <volume>27</volume>
      <elocation-id>e69813</elocation-id>
      <history>
        <date date-type="received">
          <day>9</day>
          <month>12</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>31</day>
          <month>1</month>
          <year>2025</year>
        </date>
        <date date-type="rev-recd">
          <day>12</day>
          <month>2</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>20</day>
          <month>2</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Rada Hussein, Amelie Gyrard, Somayeh Abedian, Philip Gribbon, Sara Alabart Martínez. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 23.04.2025.</copyright-statement>
      <copyright-year>2025</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2025/1/e69813" xlink:type="simple"/>
      <abstract>
        <p>The successful implementation of the European Health Data Space (EHDS) for the secondary use of data (known as EHDS2) hinges on overcoming significant challenges, including the proper implementation of interoperability standards, harmonization of diverse national approaches to data governance, and the integration of rapidly evolving AI technologies. This work addresses these challenges by developing an interactive toolkit that leverages insights from 7 leading cancer research projects (Integration of Heterogeneous Data and Evidence towards Regulatory and HTA Acceptance [IDERHA], European Federation for Cancer Images [EUCAIM], Artificial intelligence Supporting Cancer Patients across Europe [ASCAPE], Personalised Health Monitoring and Decision Support Based On Artificial Intelligence and Holistic Health Records [iHelp], Central repository for digital pathology [Bigpicture], Piloting an infrastructure for the secondary use of health data [HealthData@EU] pilot, and improving cancer diagnosis and prediction with AI and big data [INCISIVE]) to guide in shaping the EHDS2 interoperability framework. Building upon the foundations laid by the Towards the European Health Data Space (TEHDAS) joint action (JA) and the new European Interoperability Framework (EIF), the toolkit incorporates several key innovative features. First, it provides interactive and user-friendly entry modules to support European projects in creating their own interoperability frameworks aligned with the evolving EHDS2 requirements technical and governance requirements. Second, it guides projects in navigating the complex landscape of health data standards, emphasizing the need for a balanced approach to implementing the EHDS2 recommended standards for data discoverability and sharing. Third, the toolkit fosters collaboration and knowledge sharing among projects by enabling them to share their experiences and best practices in implementing standards and addressing interoperability challenges. Finally, the toolkit recognizes the dynamic nature of the EHDS2 and the evolving regulatory landscape, including the impact of AI regulations and related standards. This allows for continuous adaptation and improvement, ensuring the toolkit remains relevant and useful for future projects. In collaboration with HSbooster.eu, the toolkit will be disseminated to a wider audience of projects and experts, facilitating broader feedback and continuous improvement. This collaborative approach will foster harmonized standards implementation across projects that ultimately contribute to the development of a common EHDS2 interoperability framework.</p>
      </abstract>
      <kwd-group>
        <kwd>artificial intelligence</kwd>
        <kwd>European Health Data Space</kwd>
        <kwd>European interoperability framework</kwd>
        <kwd>healthcare standards interoperability</kwd>
        <kwd>secondary use of health data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>During the past years, the European Commission (EC) has aimed to unlock the potential of health data for providing better health care services and advancing research and innovation while upholding ethical and privacy principles. In 2020, the European strategy for data [<xref ref-type="bibr" rid="ref1">1</xref>] proposed to establish common European data spaces to govern access and reuse of data from various sectors across the European Union (EU), starting with the European Health Data Space (EHDS) [<xref ref-type="bibr" rid="ref2">2</xref>] as the first common data space across Europe. The EHDS will mainly empower individuals to take control of their health data across Europe (primary use of data, known as EHDS1 [European Health Data Space for the primary use of data]), in addition to reusing the health data in research, innovation regulatory activities, and policy-making (secondary use of data, known as EHDS2 [European Health Data Space for the secondary use of data]) [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>The EHDS regulation was proposed on May 3, 2022, adopted by the European Parliament on April 24, 2024 [<xref ref-type="bibr" rid="ref4">4</xref>], and is expected to enter into force by Autumn 2024. The EHDS2 obligations will be applied around 2028, except for some data categories, such as clinical trial data and human genetic data, that are expected to be implemented by 2030.</p>
      <p>Meanwhile, the EC is establishing the main infrastructure of the EHDS, namely MyHealth@EU (for EHDS1), based on the lessons learned from the epSOS project cross-border health care services, and building on the xShare initiative for data portability), and HealthData@EU pilot (for EHDS2) [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. Moreover, the Towards the European Health Data Space (TEHDAS) Joint Action (JA) [<xref ref-type="bibr" rid="ref5">5</xref>] was launched to prepare the ground for the harmonized implementation of EHDS2 in the EU member states by developing the guidelines and technical specifications for smooth access to health data.</p>
      <p>The EHDS governance is built on the EU legal frameworks (<xref rid="figure1" ref-type="fig">Figure 1</xref>), mainly, the General Data Protection Regulation (GDPR), the Data Governance Act (DGA), the Medical Devices Regulation (MDR), In Vitro Diagnostics Regulation (IVDR), the Data Act, and the Network &amp; Information Security (NIS2) Directive [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>], in addition to the recently adopted AI (artificial intelligence) Act that shapes the European approach to building trustworthy AI [<xref ref-type="bibr" rid="ref8">8</xref>]. The EHDS complements these regulations and will provide additional tailor-made rules when needed.</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>Timeline of the European Union data regulations and frameworks shaping the European Health Data Space Regulation.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <p>Recently, the HealthData@EU Pilot identified the common elements for health data access and data use within the legal frameworks of the participating nodes [<xref ref-type="bibr" rid="ref9">9</xref>], namely the Biobanking and BioMolecular resources Research Infrastructure (BBMRI; European Research Infrastructure), Health Data Lab (Germany), Danish Health Data Authority (Denmark), Findata (Finland), Health Data Hub (France), Sciensano (Belgium), Norwegian Directorate of eHealth (Norway), and Croatian Institute of Public Health (Croatia). This work aimed to harmonize legal and ethical data access procedures, security requirements, and GDPR citizen access rights compliance for cross-border use of data. The performed analysis reflected that nodes vary to a great extent regarding the scope of available data, the legal basis for making the data available and accessible, and responding to data misuse. There are also major differences in the degree of centralization of the decision on data access.</p>
      <p>To harmonize the EHDS implementation across the member states, the EHDS established a new independent advisory and regulatory body, called the EHDS Board, that facilitates the exchange of information and cooperation among member states and with the EC [<xref ref-type="bibr" rid="ref6">6</xref>], such as: coordinating the practices among Health Data Access Bodies (HDABs) in member states, exchanging best practices with the EC to support the legislation, and sharing information on EHDS2 risks and incidents.</p>
      <p>The EC rolling plan for AI standardization (2024) highlighted the ongoing policy, legislation, ethical, and technical standardization activities [<xref ref-type="bibr" rid="ref10">10</xref>]. The European Committee for Electrotechnical Standardization (CEN-CENELEC) created a Joint Technical Committee (JTC 21) to address AI standardization in Europe, applying both a bottom-up approach (similar to International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) JTC 1 Subcommittees (SC) 42 “ISO/IEC JTC 1/SC 42 Artificial Intelligence”), and a top-down approach concentrating on a long-term plan for European standardization and future AI regulation. Notably, the SC 42 published standards [<xref ref-type="bibr" rid="ref11">11</xref>] on (1) big data overview, vocabulary, reference architecture, and (2) AI covering bias in AI systems and AI-aided decision making, overview of trustworthiness in AI, assessment of the robustness of neural networks, use cases, overview of computational approaches for AI systems. The different workgroups of the SC 42 are still developing the standards on (1) foundational AI standards, (2) big data ecosystem, and (3) AI trustworthiness.</p>
      <p>The EC also established the AI watch as a hub for the Joint Research Centre’s scientific research on AI [<xref ref-type="bibr" rid="ref12">12</xref>]. In 2023, the AI Watch published a report on the state of the art of AI's current and near-future applications in medicine, health care, and well-being [<xref ref-type="bibr" rid="ref13">13</xref>]. At the implementation level, the AI for Health Imaging (AI4HI) [<xref ref-type="bibr" rid="ref14">14</xref>] project network was launched to develop cancer imaging data repositories and AI solutions based on medical imaging to improve clinical practice. The involved projects are PRIMAGE, CHAIMELEON, EuCanImage, INCISIVE, ProCAncer-I, and RadioVal.</p>
      <p>On the other hand, the EC adopted the new European Interoperability Framework (EIF) in 2017 [<xref ref-type="bibr" rid="ref15">15</xref>] to connect public administrations, businesses, and citizens across Europe [<xref ref-type="bibr" rid="ref16">16</xref>]. The EIF conceptual model comprises 4 levels of interoperability namely, legal, organizational, semantic, and technical interoperability, associated with the underlying 12 principles and 47 recommendations for proper implementation. The eHealth Network refined the EIF for the eHealth domain into 6 layers in the Refinement of the eHealth European Interoperability Framework (ReEIF) [<xref ref-type="bibr" rid="ref17">17</xref>]. In 2023, the INCISIVE project [<xref ref-type="bibr" rid="ref18">18</xref>] provided its interoperability framework based on the ReEIF as recommended input for the anticipated interoperability framework for the EHDS [<xref ref-type="bibr" rid="ref19">19</xref>]. <xref rid="figure2" ref-type="fig">Figure 2</xref> depicts the 4 layers of the EIF and its interlinking with the ReEIF 6 layers and the recommended 5 overlapping layers by the INCISIVE project.</p>
      <fig id="figure2" position="float">
        <label>Figure 2</label>
        <caption>
          <p>The interoperability layers of the European Interoperability Framework, Refinement of the eHealth European Interoperability Framework, and the INCISIVE project. EHDS: European Health Data Space; EIF: European Interoperability Framework; ReEIF: Refinement of the eHealth European Interoperability Framework.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec>
      <title>Standards and Interoperability in the European AI-Driven Projects</title>
      <p>Interoperability is the cornerstone of digital medicine, especially in the AI era, which necessitates the availability of various high-quality datasets [<xref ref-type="bibr" rid="ref20">20</xref>]. The lack of proper interoperability implementation hinders AI implementation in the real world, as highlighted by the recent study published by the Scientific Foresight Unit of the European Parliamentary Research Service in 2022 [<xref ref-type="bibr" rid="ref21">21</xref>]. At the industry level, MedTech Europe and COCIR partnered to present a medical technology industry perspective on the standards, levels of interoperability, standards, profiles, and specifications relevant to digital health [<xref ref-type="bibr" rid="ref22">22</xref>]. Furthermore, recent studies addressed the need for an interoperability framework for the EHDS that uses the EIF for managing specifications for interoperability [<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref27">27</xref>] while considering the other aspects of data security, privacy, governance, and quality. The proposed interoperability framework should also be based on approved international interoperability standards for semantics and syntax, for example, the standards described and examined in [<xref ref-type="bibr" rid="ref28">28</xref>-<xref ref-type="bibr" rid="ref30">30</xref>].</p>
      <p>In response to this challenge, we have created a synergy between AI-data projects with cancer use cases based [<xref ref-type="bibr" rid="ref31">31</xref>] in October 2023, through the HSbooster.eu initiative for fostering standards in EU-funded projects. These current projects shape the EHDS implementation, for example, the Integration of Heterogeneous Data and Evidence towards Regulatory and HTA Acceptance (IDERHA), European Federation for Cancer Images (EUCAIM), HealthData@EU pilot, and other projects [<xref ref-type="bibr" rid="ref31">31</xref>]. We started by creating a template for the EHDS2 interoperability framework based on the EIF. Then, we mapped the used standards in 6 projects with the created template [<xref ref-type="bibr" rid="ref32">32</xref>]. We compared the health-standardized models, ontologies, and terminologies used in these projects and mapped their relevance to EHDS2 [<xref ref-type="bibr" rid="ref32">32</xref>]. We also examined the AI tools, techniques, and standards, as well as the federated data infrastructure in these projects.</p>
      <p>In this work, we created an EHDS2 interoperability framework based on the EIF. We used the intensive expertise and lessons learned from the synergy projects to identify the underlying interoperability standards and best practices in implementation. These standards cover health standards and Internet of Medical Things (IoMT) semantic interoperability [<xref ref-type="bibr" rid="ref33">33</xref>] in the context of interoperability standards for health data, knowledge graphs–related technologies, Smart Applications REFerence ontology (SAREF), Data quality framework (DQF), Patient-Generated Health Data (PGHD), AI reasoning, federated approaches, security and privacy. This toolkit aims to support existing and future projects in creating their interoperability framework in compliance with EHDS2 governance and technical requirements.</p>
    </sec>
    <sec>
      <title>Existing Interoperability Framework Tools and Guides</title>
      <p>We investigated the interoperability tools and guides provided by EU-funded projects and international organizations during the past few years. <xref ref-type="table" rid="table1">Table 1</xref> summarizes the key findings and compares these tools in terms of their compliance with the EIF and EHDS2 requirements [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      <p>The listed tools in <xref ref-type="table" rid="table1">Table 1</xref> provide guidance on creating interoperability toolkits in general, while the TEHDAS and INCISIVE projects focus on EHDS2. The IHE integration profiles indicate how to define use cases in any project of clinical data interoperability and promote the coordinated use of established standards such as Digital Imaging and Communications in Medicine (DICOM) and Health Level 7 (HL7). Both IHE and eHAction tools mainly target EHDS1. All tools do not provide concrete guidance on how to select the proper standards for each EIF layer relevant to the EHDS2 recommended standards, for example, standards for data discoverability (meta-data standards), and other related aspects, including data quality, IoMT, PGHD, and others.</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Main recent guides and tools of the interoperability frameworks.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="200"/>
          <col width="200"/>
          <col width="250"/>
          <col width="200"/>
          <col width="150"/>
          <thead>
            <tr valign="top">
              <td>Project/International organization</td>
              <td>Tool/guide (year)</td>
              <td>Scope</td>
              <td>EIF<sup>a</sup> compliance</td>
              <td>EHDS2<sup>b</sup> compliance</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>World Bank Group’s ID4D<sup>c</sup> Initiative [<xref ref-type="bibr" rid="ref34">34</xref>]</td>
              <td>ID4D Practitioner’s Guide (2019)</td>
              <td>To help practitioners design and implement identification systems that are inclusive and trusted—in accordance with the 10 Principles on Identification for Sustainable Development and other international standards and good practices</td>
              <td>Based on the EIF 4 layers</td>
              <td>Not specifically for the health domain</td>
            </tr>
            <tr valign="top">
              <td>eHAction JA<sup>d</sup> [<xref ref-type="bibr" rid="ref35">35</xref>]</td>
              <td>Interoperability Guide (2020)</td>
              <td>To support health care providers in planning and procuring standards-based interoperable solutions</td>
              <td>Based on the ReEIF<sup>e</sup></td>
              <td>Mainly for EHDS1<sup>f</sup></td>
            </tr>
            <tr valign="top">
              <td>TEHDAS JA<sup>g</sup> [<xref ref-type="bibr" rid="ref28">28</xref>]</td>
              <td>EHDS Semantic interoperability framework (2022)</td>
              <td>Providing EHDS2 data life-cycle and recommendations to enhance interoperability within the HealthData@EU</td>
              <td>Based on the EIF</td>
              <td>Target EHDS2</td>
            </tr>
            <tr valign="top">
              <td>INCISIVE<sup>h</sup> project [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]</td>
              <td>Recommendations of interoperability standards (2023) INCISIVE HL7<sup>i</sup> FHIR<sup>j</sup> Implementation Guide (2024)</td>
              <td>To contribute to the EUCAIM<sup>k</sup> interoperability framework, as input for the EHDS interoperability framework</td>
              <td>Based on the ReEIF</td>
              <td>For projects managing clinical data and medical images</td>
            </tr>
            <tr valign="top">
              <td>WHO<sup>l</sup> [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref38">38</xref>]</td>
              <td>Ethics and governance of AI for health (2021 and 2024)</td>
              <td>Recommendations for consideration by governments, technology companies, and health care providers to ensure the appropriate use of AI in health</td>
              <td>Related to the legal interoperability layer of the EIF</td>
              <td>Necessary for EHDS2</td>
            </tr>
            <tr valign="top">
              <td>IHE<sup>m</sup> [<xref ref-type="bibr" rid="ref39">39</xref>]</td>
              <td>IHE profiles for the exchange of documents in European eHDSI<sup>n</sup></td>
              <td>IHE defines Integration Profiles that use existing standards for system integration, providing effective interoperability and efficient workflow</td>
              <td>Related to the organizational/technical interoperability layers of the EIF</td>
              <td>Mainly EHDS1</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>EIF: European Interoperability Framework.</p>
          </fn>
          <fn id="table1fn2">
            <p><sup>b</sup>EHDS2: European Health Data Space for the secondary use of data.</p>
          </fn>
          <fn id="table1fn3">
            <p><sup>c</sup>ID4D: Identification for Development.</p>
          </fn>
          <fn id="table1fn4">
            <p><sup>d</sup>eHAction JA: eHealth Action.</p>
          </fn>
          <fn id="table1fn5">
            <p><sup>e</sup>ReEIF: Refined eHealth European Interoperability Framework.</p>
          </fn>
          <fn id="table1fn6">
            <p><sup>f</sup>EHDS1: European Health Data Space for the primary use of data.</p>
          </fn>
          <fn id="table1fn7">
            <p><sup>g</sup>TEHDAS JA: Towards the European Health Data Space Joint Action.</p>
          </fn>
          <fn id="table1fn8">
            <p><sup>h</sup>INCISIVE: improving cancer diagnosis and prediction with AI and big data.</p>
          </fn>
          <fn id="table1fn9">
            <p><sup>i</sup>HL7: Health Level 7.</p>
          </fn>
          <fn id="table1fn10">
            <p><sup>j</sup>FHIR: Fast Healthcare Interoperability Resources.</p>
          </fn>
          <fn id="table1fn11">
            <p><sup>k</sup>EUCAIM: European Federation for Cancer Images.</p>
          </fn>
          <fn id="table1fn12">
            <p><sup>l</sup>WHO: World Health Organization.</p>
          </fn>
          <fn id="table1fn13">
            <p><sup>m</sup>IHE: Integrating the Healthcare Enterprise.</p>
          </fn>
          <fn id="table1fn14">
            <p><sup>n</sup>eHDSI: eHealth Digital Services Infrastructure.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>In addition, the recent guides of the World Health Organization (WHO) on regulatory considerations on AI for health [<xref ref-type="bibr" rid="ref38">38</xref>], and the ethics and governance of artificial intelligence for health [<xref ref-type="bibr" rid="ref37">37</xref>] can shape the legal, regulatory, and policy layer accompanying the adoption of the AI Act.</p>
    </sec>
    <sec>
      <title>EHDS2 Interoperability Framework Toolkit</title>
      <p>The main concept of creating the toolkit is to incorporate the European guidelines, interoperability standards, and best practices of European projects in real-world implementation for shaping the EHDS2 interoperability framework (<xref rid="figure3" ref-type="fig">Figure 3</xref>).</p>
      <p>Thus, the toolkit aims to provide the existing and future EU projects with an interactive and user-friendly entry interface designing, writing, and printing the interoperability framework in compliance with EHDS2. It facilitates the selection of the standards for each EIF layer and provides more guidance on the proper implementation of these standards by providing best practices from other projects or international organizations (<xref rid="figure4" ref-type="fig">Figure 4</xref>).</p>
      <fig id="figure3" position="float">
        <label>Figure 3</label>
        <caption>
          <p>The European Health Data Space for the secondary use of data interoperability framework: concept and process of creation. AI: artificial intelligence; EHDS2: European Health Data Space for the secondary use of data; IoMT: Internet of Medical Things; PGHD: patient-generated health data.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <fig id="figure4" position="float">
        <label>Figure 4</label>
        <caption>
          <p>The toolkit of European Health Data Space for the secondary use of data interoperability framework: main components and sections. EIF: European Interoperability Framework; FAIR: Findability, Accessibility, Interoperability, and Reusability; IoMT: Internet of Medical Things; PGHD: patient-generated health data.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec>
      <title>Standards and Guidelines Selection Module</title>
      <p>To design the toolkit standards and guideline modules, we first created a template for mapping the interoperability standards between TEHDAS, INCISIVE project, and the created list of implemented standards used in the HSbooster.eu synergy projects (<xref ref-type="table" rid="table2">Table 2</xref>). We did not intend to compare the standards implemented in these projects but rather highlight how these projects fulfill the interoperability goals and share their learned lessons. Thus, <xref ref-type="table" rid="table2">Table 2</xref> highlights the most important standards implemented in these projects, without meaning that the other projects do not implement the proper standards.</p>
      <p>We adopted the TEHDAS recommended categories of EHDS2 interoperability standards, as follows:</p>
      <list list-type="order">
        <list-item>
          <p>Data discoverability: the World Wide Web Consortium (W3C) Data Catalog Vocabulary (DCAT)-Application Profile (AP), as well as the anticipated extension of DCAT-AP for health (HealthDCAT-AP) being developed by the HealthData@EU pilot.</p>
        </list-item>
        <list-item>
          <p>Enabling semantics interoperability: the Observational Medical Outcomes Partnership (OMOP)-Common Data Model (CDM)- developed by the Observational Health Data Sciences and Informatics (OHDSI).</p>
        </list-item>
        <list-item>
          <p>Health data exchange (DICOM for imaging data and the HL7 Fast Healthcare Interoperability Resources (FHIR) for health records).</p>
        </list-item>
      </list>
      <p>Then, we identified the related ISO standards for data quality, PGHD, AI reasoning, federated approaches, security, and privacy.</p>
      <p>The template was refined by adding the INCISIVE standardization suggestions [<xref ref-type="bibr" rid="ref19">19</xref>], on the following:</p>
      <list list-type="bullet">
        <list-item>
          <p>Use cases and health care process definition</p>
        </list-item>
        <list-item>
          <p>Data exchange without losing the semantic meaning with terminologies</p>
        </list-item>
        <list-item>
          <p>Clinical documents exchange</p>
        </list-item>
        <list-item>
          <p>Medical image exchange</p>
        </list-item>
        <list-item>
          <p>Clinical data and events exchange</p>
        </list-item>
        <list-item>
          <p>Common data model to index or group data</p>
        </list-item>
        <list-item>
          <p>Standardize the database with archetypes to present data in the user interface.</p>
        </list-item>
      </list>
      <table-wrap position="float" id="table2">
        <label>Table 2</label>
        <caption>
          <p>Summary of mapping the interoperability standards to the European Health Data Space for the secondary use of data template based on the European Interoperability Framework using the Towards the European Health Data Space and Improving Cancer Diagnosis and Prediction with AI [artificial intelligence] and Big Data Results.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="150"/>
          <col width="250"/>
          <col width="250"/>
          <col width="350"/>
          <thead>
            <tr valign="top">
              <td>EIF<sup>a</sup></td>
              <td>TEHDAS<sup>b</sup> [<xref ref-type="bibr" rid="ref6">6</xref>] Governance model of the EHDS2<sup>c</sup> of the data life-cycle</td>
              <td>INCISIVE<sup>d</sup> [<xref ref-type="bibr" rid="ref19">19</xref>] Recommendations of interoperability standards (managing clinical data and medical images)</td>
              <td>HSbooster.eu synergy projects [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>] (the main health and IoMT<sup>e</sup> standards<sup>f</sup>)</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>Legal</td>
              <td>The EHDS<sup>g</sup> will build on the legal frameworks laid out by the EU<sup>h</sup> regulations (<xref rid="figure1" ref-type="fig">Figure 1</xref>)</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Legal and security standards and FAIRi principles. The detailed explanation is provided in INCISIVE’s Deliverable 7.3 Data donation legal framework</p>
                  </list-item>
                  <list-item>
                    <p>ISOj 14971 Medical Devices Risk Management Assessment</p>
                  </list-item>
                  <list-item>
                    <p>IECk 62304 Medical device software - Software life cycle processes</p>
                  </list-item>
                </list>
              </td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>ISO/IEC 27001:2022-</p>
                  </list-item>
                  <list-item>
                    <p>Information security, cybersecurity, and privacy protection</p>
                  </list-item>
                  <list-item>
                    <p>IEEEl 7000 Series- AI ethical considerations</p>
                  </list-item>
                  <list-item>
                    <p>ISO/IEC 42001_2023 – AI – Management system and requirements</p>
                  </list-item>
                </list>
              </td>
            </tr>
            <tr valign="top">
              <td>Organizational</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Adapting the national policies in compliance with the EHDS regulations</p>
                  </list-item>
                  <list-item>
                    <p>Harmonizing the EU member states health policies and the delivery of health services and medical care</p>
                  </list-item>
                </list>
              </td>
              <td>The IHE<sup>m</sup> integration profiles identified the care process, actors, transactions, and events</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>IHE integration profiles</p>
                  </list-item>
                  <list-item>
                    <p>ISO/IEC 5259-1:2024</p>
                  </list-item>
                  <list-item>
                    <p>Artificial intelligence — Data quality for analytics and machine learning</p>
                  </list-item>
                  <list-item>
                    <p>ISO 9000: Data Quality Management Systems standards</p>
                  </list-item>
                  <list-item>
                    <p>Data quality frameworks</p>
                  </list-item>
                  <list-item>
                    <p>Data FAIRification framework</p>
                  </list-item>
                </list>
              </td>
            </tr>
            <tr valign="top">
              <td>Semantic</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Standards on data discoverability: (DCAT-APn)</p>
                  </list-item>
                  <list-item>
                    <p>Standards that allow semantic interoperability: (OMOP-CDMo)</p>
                  </list-item>
                </list>
              </td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>SNOMED CTp (Clinical data) LOINCq (Lab data)</p>
                  </list-item>
                  <list-item>
                    <p>OHDSIr vocabularies</p>
                  </list-item>
                </list>
              </td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>SNOMED, LOINC, ICDs, RxNorm, etc</p>
                  </list-item>
                  <list-item>
                    <p>ISO 13606-Health Informatics- Electronic Health Record —Parts 1,2,4 (Reference model/ Archetype interchange specification / Security)</p>
                  </list-item>
                  <list-item>
                    <p>ISO 11073-10101 and ISO 11073-10201- Health informatics — Device Interoperability (Point-of-care medical device communication — Domain information model/Nomenclature)</p>
                  </list-item>
                  <list-item>
                    <p>ISO 23903:2021</p>
                  </list-item>
                  <list-item>
                    <p>Health informatics — Interoperability and integration reference architecture — Model and framework</p>
                  </list-item>
                  <list-item>
                    <p>Standards on data discoverability: HealthDCAT-AP</p>
                  </list-item>
                  <list-item>
                    <p>OMOPt for enabling data analysis</p>
                  </list-item>
                  <list-item>
                    <p>ISO/IEC 22989: AI concept and terminology</p>
                  </list-item>
                </list>
              </td>
            </tr>
            <tr valign="top">
              <td>Syntactic</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Standards that facilitate communication: FHIRu (Clinical data)</p>
                  </list-item>
                  <list-item>
                    <p>DICOMv (Imaging data)</p>
                  </list-item>
                </list>
              </td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>FHIR (All data)</p>
                  </list-item>
                  <list-item>
                    <p>DICOM (Imaging data)</p>
                  </list-item>
                </list>
              </td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>HL7, FHIR (Clinical data)</p>
                  </list-item>
                  <list-item>
                    <p>DICOM (Imaging data)</p>
                  </list-item>
                  <list-item>
                    <p>ISO/IEEE 11073-20601 and ISO/IEEE 11073-20701 (PGHD- Device Interoperability and optimized exchange protocol)</p>
                  </list-item>
                  <list-item>
                    <p>EN/ISO 13606: Health Informatics- Electronic Health Record —Parts 3,5(Reference archetypes and term lists/Interface specification)</p>
                  </list-item>
                </list>
              </td>
            </tr>
            <tr valign="top">
              <td>Technical</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Federated peer-to-peer (P2P) network</p>
                  </list-item>
                  <list-item>
                    <p>Secure processing environment</p>
                  </list-item>
                </list>
              </td>
              <td>JSON or XML</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Semantic web languages such as W3Cw RDFx, RDFSy, OWLz, SPARQLaa, JSON-LDab, etc</p>
                  </list-item>
                  <list-item>
                    <p>JSON or XML (medical data)</p>
                  </list-item>
                  <list-item>
                    <p>ISO accreditation for the EHDS2 secure processing environment, for example, ISO/IEC 27001</p>
                  </list-item>
                  <list-item>
                    <p>IEEE 3652.1, Guide for Architectural Framework and Application of Federated Machine Learning</p>
                  </list-item>
                </list>
              </td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table2fn1">
            <p><sup>a</sup>EIF: European Interoperability Framework.</p>
          </fn>
          <fn id="table2fn2">
            <p><sup>b</sup>TEHDAS JA: Towards the European Health Data Space Joint Action.</p>
          </fn>
          <fn id="table2fn3">
            <p><sup>c</sup>EHDS2: European Health Data Space for the secondary use of data.</p>
          </fn>
          <fn id="table2fn4">
            <p><sup>d</sup>INCISIVE: improving cancer diagnosis and prediction with AI and big data.</p>
          </fn>
          <fn id="table2fn5">
            <p><sup>e</sup>IoMT: Internet of Medical Things.</p>
          </fn>
          <fn id="table2fn6">
            <p><sup>f</sup>The complete list of standards is available in the toolkit. The table highlights the main standards used in health and IoMT</p>
          </fn>
          <fn id="table2fn7">
            <p><sup>g</sup>EHDS: European Health Data Space.</p>
          </fn>
          <fn id="table2fn8">
            <p><sup>h</sup>EU: European Union.</p>
          </fn>
          <fn id="table2fn9">
            <p><sup>i</sup>FAIR: Findability, Accessibility, Interoperability, and Reusability.</p>
          </fn>
          <fn id="table2fn10">
            <p><sup>j</sup>ISO: International Standards Organization.</p>
          </fn>
          <fn id="table2fn11">
            <p><sup>k</sup>IEC: Internation Electrochemical Commission.</p>
          </fn>
          <fn id="table2fn12">
            <p><sup>l</sup>IEEE: Institute of Electrical and Electronics Engineers.</p>
          </fn>
          <fn id="table2fn13">
            <p><sup>m</sup>IHE: Integrating the Healthcare Enterprise.</p>
          </fn>
          <fn id="table2fn14">
            <p><sup>n</sup>DCAT-AP: Data Catalogue vocabulary Application Profile for data portals.</p>
          </fn>
          <fn id="table2fn15">
            <p><sup>o</sup>OMOP-CDM: Observational Medical Outcomes Partnership Common Data Model.</p>
          </fn>
          <fn id="table2fn16">
            <p><sup>p</sup>SNOMED CT: Systematized Nomenclature of Medicine – Clinical Terms.</p>
          </fn>
          <fn id="table2fn17">
            <p><sup>q</sup>LOINC: Logical Observation Identifiers Names and Codes.</p>
          </fn>
          <fn id="table2fn18">
            <p><sup>r</sup>OHDSI: Observational Health Data Sciences and Informatics.</p>
          </fn>
          <fn id="table2fn19">
            <p><sup>s</sup>ICD: International Classification of Diseases.</p>
          </fn>
          <fn id="table2fn20">
            <p><sup>t</sup>OMOP mapping (linking the semantic layer with the syntactic layer)</p>
          </fn>
          <fn id="table2fn21">
            <p><sup>u</sup>FHIR mapping (linking the semantic layer with the syntactic layer).</p>
          </fn>
          <fn id="table2fn22">
            <p><sup>v</sup>DICOM: Digital Imaging and Communications in Medicine.</p>
          </fn>
          <fn id="table2fn23">
            <p><sup>w</sup>W3C: World Wide Web Consortium.</p>
          </fn>
          <fn id="table2fn24">
            <p><sup>x</sup>RDF: Resource Description Framework.</p>
          </fn>
          <fn id="table2fn25">
            <p><sup>y</sup>RDFS: Resource Description Framework Schema.</p>
          </fn>
          <fn id="table2fn26">
            <p><sup>z</sup>OWL: Web Ontology Language.</p>
          </fn>
          <fn id="table2fn27">
            <p><sup>aa</sup>SPARQL: SPARQL Protocol and RDF Query Language.</p>
          </fn>
          <fn id="table2fn28">
            <p><sup>ab</sup>JSON-LD: JSON for Linked Data.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>Deciding between the HL7 FHIR and OMOP CDM standards can be complex, as each offers distinct advantages to different needs within health care systems. HL7 FHIR is particularly advantageous due to its flexibility, allowing for personalized profiles, extensions, and the use of local code systems. It enables the exchange of granular clinical data through its resource-based framework and RESTful API. This adaptability, combined with its support for incremental adoption, makes FHIR highly suitable for organizations looking to integrate real-time data exchange into their new or existing infrastructure. Additionally, its alignment with established standards like HL7 v2 and v3 reinforces its utility in a wide range of health care applications.</p>
      <p>Conversely, OMOP CDM shines in facilitating research collaborations, data analysis, and evidence generation through its standardized and harmonized approach to observational health care data. Designed primarily to support observational research, OMOP uses OHDSI vocabularies (for this reason, OMOP is often situated as a semantic layer standard) to semantically code clinical terms instead of using CodeSystems as FHIR does, but both use the same international terminologies. While OMOP is particularly powerful for research purposes and large-scale data consumption, it may be less suitable as a messaging standard, as its implementation often requires extensions to cover all relevant health care domains. As such, it is more appropriate for systems focused on data analytics rather than operational data exchange.</p>
      <p>In determining which standard to adopt, the decision depends on the intended use case. HL7 FHIR is better suited for systems that prioritize flexible, real-time clinical data exchange and customization through extensions and local adaptations. In contrast, OMOP is ideal for those focused on research, standardized data analysis, and evidence generation across multiple health care organizations. Integrating both standards can offer significant benefits, promoting interoperability between clinical and research environments, and leveraging FHIR’s strengths in real-time data sharing and OMOP’s robust framework for data analysis and evidence generation. Fortunately, achieving interoperability between FHIR and OMOP is being carried out by the HL7 and OHDSI communities. For example, the developed semantic Web-based FHIR-Ontop-OMOP system demonstrates great potential in health care AI applications enabled by the interoperability of FHIR and OMOP CDM [<xref ref-type="bibr" rid="ref40">40</xref>] and the FHIR to OMOP FHIR Implementation Guide [<xref ref-type="bibr" rid="ref41">41</xref>]. The relevant FHIR and OMOP mapping resources and implementation guide are also listed in the syntactic standards form of the toolkit to provide a proper linking of the semantic layer with the syntactic layer.</p>
    </sec>
    <sec>
      <title>Interoperability Framework Entry Module</title>
      <p>We also used INCISIVE recommended methodology for the design and implementation of the interoperability framework [<xref ref-type="bibr" rid="ref19">19</xref>], in providing the entry modules of the main components of the main interoperability framework sections: (1) needs analysis, (2) selection of data and information, (3) processes and use cases, (4) interoperability standards and implementation guides, (5) risk analysis, (6) maintenance plan, (7) specification, design and planning of interoperability phases, (8) recommendations and future actions, and (9) implementation guide publication.</p>
      <p>Finally, we used the Fillout platform [<xref ref-type="bibr" rid="ref42">42</xref>] in creating the interactive interface of the toolkit (<xref rid="figure5" ref-type="fig">Figures 5</xref>-<xref rid="figure7" ref-type="fig">7</xref>). The Integration of Heterogeneous Data and Evidence towards Regulatory and HTA Acceptance (IDERHA) project in collaboration with the HSbooster.eu created the first version of the toolkit [<xref ref-type="bibr" rid="ref43">43</xref>]. This is a part of IDERHA’s plan to align with the EHDS2 standards and interoperability requirements [<xref ref-type="bibr" rid="ref44">44</xref>].</p>
      <fig id="figure5" position="float">
        <label>Figure 5</label>
        <caption>
          <p>The interoperability toolkit: a snapshot of the entry module of the interoperability framework and how the projects can share their lessons learned.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <fig id="figure6" position="float">
        <label>Figure 6</label>
        <caption>
          <p>The interoperability toolkit: a snapshot of the module of the standards selection.AI: artificial intelligence; IoMT: Internet of Medical Things.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <fig id="figure7" position="float">
        <label>Figure 7</label>
        <caption>
          <p>The logic for navigating the interoperability toolkit.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec>
      <title>Identifying the AI Risks and Legal Obligations According to the EU AI Act Using the Toolkit</title>
      <p>The AI Act applies to all sectors and it does not identify certain rules for the health care domain. Recently, a study was published to highlight the implications of the AI Act for the health care sector and give a comprehensive overview of the new legal obligations for various health care stakeholders (technical developers, health care professionals, and public health authorities) [<xref ref-type="bibr" rid="ref45">45</xref>]. We adopted this study in the toolkit as a guideline for identifying the AI risk in EU projects as a part of the risk analysis of the interoperability framework (<xref rid="figure8" ref-type="fig">Figure 8</xref>).</p>
      <fig id="figure8" position="float">
        <label>Figure 8</label>
        <caption>
          <p>Identifying the associated artificial intelligence risk and obligations by referring to the guidance. AI: artificial intelligence; EU: European Union.</p>
        </caption>
        <graphic xlink:href="jmir_v27i1e69813_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <p>Now, the toolkit lists the standards and the lessons learned from synergy projects formed through the HSbooster.eu in cancer [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. We also encourage other projects to share their expertise and used standards through the toolkit designated fields for input and uploading files. We enabled the Fillout settings for respondent notifications, including the link to edit submissions, to allow the respondents to revise their answers at any time. Furthermore, the automatic notification email to the respondents will contain a summary of the responses for creating the interoperability framework that can be saved or printed.</p>
      <p>Ultimately, the toolkit can also be used at the international level for creating the EHDS2 interoperability frameworks with countries outside the European region, especially the notable attention as an inspiring model for transatlantic collaborative health data use and AI development [<xref ref-type="bibr" rid="ref46">46</xref>].</p>
    </sec>
    <sec>
      <title>Conclusion</title>
      <p>In preparation for a harmonized implementation of EHDS2, most of the funded European projects applying AI in health are planning for the proper alignment with the EHDS2 requirements in data governance and interoperability [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref44">44</xref>].</p>
      <p>The described toolkit in this work will support the AI-driven project in creating the interoperability framework based on the EHDS2 governance and technical needs. We will share the toolkit with the health standards experts in TEHDAS JA and the HealthData@EU pilot to get their feedback on how to improve and maintain it. We also will share the proposed EHDS2 interoperability framework with IHE Europe to investigate the integration profiles for closing the gaps between EHDS1 and EHDS2. Moreover, we plan to conduct a workshop during the Medical Informatics Europe (MIE2025) to establish a dialogue with the health informatics community on how to use the toolkit as one of the inputs for the EHDS2 interoperability framework. We will also discuss the challenges of keeping the toolkit up to date with the evolving AI standards landscape through hosting the toolkit by the HSbooster. Finally, it will be essential to assess the impact of using the toolkit to ensure that it meets its goal, and delivers the expected benefits to the health data ecosystem. This will also be accompanied by conducting a thorough review of the EHDS2 interoperability achievements and challenges across the member states driven by the real-world implementation of the EHDS.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">AI4HI</term>
          <def>
            <p>AI for Health Imaging</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ASCAPE</term>
          <def>
            <p>Artificial intelligence Supporting Cancer Patients across Europe</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">BBMRI</term>
          <def>
            <p>the Biobanking and BioMolecular resources Research Infrastructure</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">CDM</term>
          <def>
            <p>common data model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">CEN-CENELEC</term>
          <def>
            <p>the European Committee for Electrotechnical Standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">DCAT</term>
          <def>
            <p>data catalog vocabulary</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">DCAT-AP</term>
          <def>
            <p>DCAT Application profile for data portals in Europe</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">DGA</term>
          <def>
            <p>the Data Governance Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">DICOM</term>
          <def>
            <p>Digital Imaging and Communications in Medicine</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">DQF</term>
          <def>
            <p>Data Quality Framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">EC</term>
          <def>
            <p>European Commission</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">EHDS</term>
          <def>
            <p>European Health Data Space</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">EHDS1</term>
          <def>
            <p>European Health Data Space for the primary use of data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">EHDS2</term>
          <def>
            <p>European Health Data Space for the secondary use of data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">EIF</term>
          <def>
            <p>European Interoperability Framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">EU</term>
          <def>
            <p>European Union</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">EUCAIM</term>
          <def>
            <p>European Federation for Cancer Images</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">FHIR</term>
          <def>
            <p>fast healthcare interoperability resource</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb20">GDPR</term>
          <def>
            <p>general data protection regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb21">HDABs</term>
          <def>
            <p>Health Data Access Bodies</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb22">HL7</term>
          <def>
            <p>Health Level 7</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb23">IDERHA</term>
          <def>
            <p>Integration of Heterogeneous Data and Evidence towards Regulatory and HTA Acceptance</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb24">IEC</term>
          <def>
            <p>International Electrotechnical Commission</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb25">iHelp</term>
          <def>
            <p>Personalised Health Monitoring And Decision Support Based On Artificial Intelligence And Holistic Health Records</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb26">IoMT</term>
          <def>
            <p>Internet of Medical Things</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb27">ISO</term>
          <def>
            <p>international organization for standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb28">IVDR</term>
          <def>
            <p>In Vitro Diagnostics Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb29">JA</term>
          <def>
            <p>joint action</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb30">JTC 21</term>
          <def>
            <p>Joint Technical Committee</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb31">MDR</term>
          <def>
            <p>Medical Devices Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb32">NIS2</term>
          <def>
            <p>the Network and Information Security Directive 2</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb33">OHDSI</term>
          <def>
            <p>observational health data sciences and informatics</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb34">OMOP</term>
          <def>
            <p>observational medical outcomes partnership</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb35">PGHD</term>
          <def>
            <p>patient-generated health data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb36">ReEIF</term>
          <def>
            <p>Refinement of the eHealth European Interoperability Framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb37">SAREF</term>
          <def>
            <p>Smart Applications REFerence ontology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb38">TEHDAS</term>
          <def>
            <p>Toward the European Health Data Space</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb39">W3C</term>
          <def>
            <p>World Wide Web Consortium</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb40">WHO</term>
          <def>
            <p>World Health Organization</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>AG declares funding from HSBOOSTER (101058391) and StandICT.eu 2026 (101091933). The IDERHA project is supported by the Innovative Health Initiative (IHI) Joint Undertaking (JU; grant 101112135). The JU receives support from the European Union’s Horizon Europe research and innovation program and life science industries represented by COCIR, EFPIA/Vaccines Europe, EuropaBio and MedTech Europe. The INCISIVE project received funding from the European Union’s Horizon 2020 research and innovation program (grant 952179).</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>RH and AG contributed to conceptualization, methodology, and writing—original draft. SA and SAM assisted with methodology and writing—original draft. SAM and PG contributed to validation and writing—review &amp; editing.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>A European strategy for data</article-title>
          <source>European Commission</source>
          <year>2024</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital-strategy.ec.europa.eu/en/policies/strategy-data">https://digital-strategy.ec.europa.eu/en/policies/strategy-data</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>European health data space regulation (EHDS)</article-title>
          <source>European Commission</source>
          <year>2024</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health.ec.europa.eu/ehealth-digital-health-and-care/european-health-data-space_en">https://health.ec.europa.eu/ehealth-digital-health-and-care/european-health-data-space_en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marcus</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Martens</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Carugati</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bucher</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Godlovitch</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>The European health data space</article-title>
          <source>SSRN</source>
          <year>2022</year>
          <access-date>2024-02-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://papers.ssrn.com/abstract=4300393">https://papers.ssrn.com/abstract=4300393</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Directorate-General for Communication</collab>
          </person-group>
          <article-title>Commission welcomes European parliament's adoption of the European health data space and regulation on substances of human origin</article-title>
          <source>European Commission</source>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/commission/presscorner/detail/en/IP_24_2250">https://ec.europa.eu/commission/presscorner/detail/en/IP_24_2250</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>Project</article-title>
          <source>TEHDAS2</source>
          <access-date>2024-12-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tehdas.eu/project/">https://tehdas.eu/project/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>Options for governance models for the European health data space</article-title>
          <source>TEHDAS</source>
          <year>2023</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tehdas.eu/tehdas1/app/uploads/2023/01/tehdas-options-for-governance-models-for-the-european-health-data-space.pdf">https://tehdas.eu/tehdas1/app/uploads/2023/01/tehdas-options-for-governance-models-for-the-european-health-data-space.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Terzis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Santamaria Echeverria</surname>
              <given-names>OE</given-names>
            </name>
          </person-group>
          <article-title>Interoperability and governance in the European health data space regulation</article-title>
          <source>Med Law Int</source>
          <year>2023</year>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>368</fpage>
          <lpage>376</lpage>
          <pub-id pub-id-type="doi">10.1177/09685332231165692</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <article-title>European approach to artificial intelligence</article-title>
          <source>European Commission</source>
          <year>2024</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital-strategy.ec.europa.eu/en/policies/european-approach-artificial-intelligence">https://digital-strategy.ec.europa.eu/en/policies/european-approach-artificial-intelligence</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <article-title>HealthData@EU pilot identifies common elements for health data access and data use within the legal frameworks of the participating nodes</article-title>
          <source>EHDS</source>
          <access-date>2025-02-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/vz2fwexx">https://tinyurl.com/vz2fwexx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>Artificial intelligence (RP2024)</article-title>
          <source>European Commission</source>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/artificial-intelligence-rp2024">https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/artificial-intelligence-rp2024</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <article-title>ISO/IEC JTC 1/SC 42 artificial intelligence</article-title>
          <source>ISO-IEC Joint Technical Committee</source>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jtc1info.org/sd-2-history/jtc1-subcommittees/sc-42/">https://jtc1info.org/sd-2-history/jtc1-subcommittees/sc-42/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <article-title>AI watch</article-title>
          <source>European Commission</source>
          <year>2024</year>
          <access-date>2024-12-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ai-watch.ec.europa.eu/index_en">https://ai-watch.ec.europa.eu/index_en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <article-title>Artificial intelligence for healthcare and well-being during exceptional times</article-title>
          <source>European Commission</source>
          <year>2023</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://edupharm.pl/wp-content/uploads/2023/11/1699886368490.pdf">https://edupharm.pl/wp-content/uploads/2023/11/1699886368490.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <article-title>Ai for health imaging</article-title>
          <source>AI4HI</source>
          <access-date>2024-12-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ai4hi.net/">https://ai4hi.net/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>The new European interoperability framework</article-title>
          <source>European Commission</source>
          <year>2017</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/isa2/eif_en/">https://ec.europa.eu/isa2/eif_en/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kouroubali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Katehakis</surname>
              <given-names>DG</given-names>
            </name>
          </person-group>
          <article-title>The new European interoperability framework as a facilitator of digital transformation for citizen empowerment</article-title>
          <source>J Biomed Inform</source>
          <year>2019</year>
          <volume>94</volume>
          <fpage>103166</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(19)30084-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2019.103166</pub-id>
          <pub-id pub-id-type="medline">30978512</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(19)30084-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>Refinement of the eHealth European interoperability framework</article-title>
          <source>eHealth Network</source>
          <year>2015</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health.ec.europa.eu/document/download/84839361-c768-4ad5-b7ca-e46b2123fef2_en">https://health.ec.europa.eu/document/download/84839361-c768-4ad5-b7ca-e46b2123fef2_en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lazic</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Agullo</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ausso</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Alves</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Barelle</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Berral</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Bizopoulos</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bunduc</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Chouvarda</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Dominguez</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Filos</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gutierrez-Torre</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hesso</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Jakovljević</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kayyali</surname>
              <given-names>R</given-names>
            </name>
            <collab>et al</collab>
          </person-group>
          <article-title>The holistic perspective of the INCISIVE project—artificial intelligence in screening mammography</article-title>
          <source>Appl Sci</source>
          <year>2022</year>
          <volume>12</volume>
          <issue>17</issue>
          <fpage>8755</fpage>
          <pub-id pub-id-type="doi">10.3390/app12178755</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <article-title>INCISIVE standardization suggestions</article-title>
          <source>INCISIVE</source>
          <year>2023</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://incisive-project.eu/wp-content/uploads/2023/08/INCISIVE_D3.4_StandardizationSuggestions_v1.0_FinalVersion.pdf">https://incisive-project.eu/wp-content/uploads/2023/08/INCISIVE_D3.4_StandardizationSuggestions_v1.0_FinalVersion.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lehne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Essenwanger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schepers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thun</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Why digital medicine depends on interoperability</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <volume>2</volume>
          <fpage>79</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0158-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0158-1</pub-id>
          <pub-id pub-id-type="medline">31453374</pub-id>
          <pub-id pub-id-type="pii">158</pub-id>
          <pub-id pub-id-type="pmcid">PMC6702215</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <article-title>Artificial intelligence in healthcare</article-title>
          <source>European Parliamentary Research Service (EPRS)</source>
          <year>2022</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.europarl.europa.eu/RegData/etudes/STUD/2022/729512/EPRS_STU(2022)729512_EN.pdf">https://www.europarl.europa.eu/RegData/etudes/STUD/2022/729512/EPRS_STU(2022)729512_EN.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Interoperability standards in digital health: a white paper from the medical technology industry</article-title>
          <source>MedTech Europe and COCIR</source>
          <year>2021</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medtecheurope.org/wp-content/uploads/2021/10/mte_interoperability_digital_health_white-paper_06oct21.pdf">https://www.medtecheurope.org/wp-content/uploads/2021/10/mte_interoperability_digital_health_white-paper_06oct21.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stellmach</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Muzoora</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Thun</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Digitalization of health data: interoperability of the proposed European health data space</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <volume>298</volume>
          <fpage>132</fpage>
          <lpage>136</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI220922</pub-id>
          <pub-id pub-id-type="medline">36073471</pub-id>
          <pub-id pub-id-type="pii">SHTI220922</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oemig</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Blobel</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Modeling digital health systems to foster interoperability</article-title>
          <source>Front Med (Lausanne)</source>
          <year>2022</year>
          <volume>9</volume>
          <fpage>896670</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36059825"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fmed.2022.896670</pub-id>
          <pub-id pub-id-type="medline">36059825</pub-id>
          <pub-id pub-id-type="pmcid">PMC9437518</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kouroubali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Katehakis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Policy and strategy for interoperability of digital health in Europe</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <volume>290</volume>
          <fpage>897</fpage>
          <lpage>901</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI220209</pub-id>
          <pub-id pub-id-type="medline">35673148</pub-id>
          <pub-id pub-id-type="pii">SHTI220209</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Katehakis</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Kouroubali</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A framework for eHealth interoperability management</article-title>
          <source>JSIS</source>
          <year>2019</year>
          <volume>14</volume>
          <issue>5</issue>
          <fpage>51</fpage>
          <lpage>61</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://articlegateway.com/index.php/JSIS/article/view/2521"/>
          </comment>
          <pub-id pub-id-type="doi">10.33423/jsis.v14i5.2521</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scheplitz</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Demonstration and evaluation of the digital health innovation interoperability framework</article-title>
          <source>Procedia Comput Sci</source>
          <year>2023</year>
          <volume>219</volume>
          <fpage>1404</fpage>
          <lpage>1411</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2023.01.429</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>EHDS Semantic interoperability framework</article-title>
          <source>TEHDAS</source>
          <year>2022</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tehdas.eu/app/uploads/2023/10/tehdas-recommendations-to-enhance-interoperability.pdf">https://tehdas.eu/app/uploads/2023/10/tehdas-recommendations-to-enhance-interoperability.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ait Abdelouahid</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Debauche</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Mahmoudi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marzak</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Literature review: clinical data interoperability models</article-title>
          <source>Information</source>
          <year>2023</year>
          <volume>14</volume>
          <issue>7</issue>
          <fpage>364</fpage>
          <pub-id pub-id-type="doi">10.3390/info14070364</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>CEN/TC 251</article-title>
          <source>CEN/TC 251 Health Informatics</source>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ehealth-standards.eu">https://www.ehealth-standards.eu</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gyrard</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gribbon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hussein</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Abedian</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bonmati</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cabornero</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Manias</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Danciu</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Dalmiani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Autexier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>van Nuland</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jendrossek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Avramidis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Alvarez</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Synergies among health data projects with cancer use cases based on health standards</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2024</year>
          <volume>316</volume>
          <fpage>1292</fpage>
          <lpage>1296</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI240649</pub-id>
          <pub-id pub-id-type="medline">39176618</pub-id>
          <pub-id pub-id-type="pii">SHTI240649</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gyrard</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Abedian</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gribbon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Manias</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>van Nuland</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zatloukal</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Nicolae</surname>
              <given-names>IE</given-names>
            </name>
            <name name-style="western">
              <surname>Danciu</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Nechifor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marti-Bonmati</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mallol</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dalmiani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Autexier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jendrossek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Avramidis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia Alvarez</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Holub</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Blanquer</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Boden</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hussein</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Lessons learned from European health data projects with cancer use cases: implementation of health standards and internet of things semantic interoperability</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <volume>27</volume>
          <fpage>e66273</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e66273/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/66273</pub-id>
          <pub-id pub-id-type="medline">40126534</pub-id>
          <pub-id pub-id-type="pii">v27i1e66273</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rajab</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Abuhmida</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ward</surname>
              <given-names>RP</given-names>
            </name>
          </person-group>
          <article-title>A review of IoMT security and privacy related frameworks</article-title>
          <source>eccws</source>
          <year>2024</year>
          <conf-name>Proceedings of the 23rd European Conference on Cyber Warfare and Security</conf-name>
          <conf-date>2024 June, 27 - 2024 June, 28</conf-date>
          <conf-loc>Finland</conf-loc>
          <fpage>733</fpage>
          <lpage>743</lpage>
          <pub-id pub-id-type="doi">10.34190/eccws.23.1.2239</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <article-title>ID4D practitioner's guide (English)</article-title>
          <source>World Bank Group</source>
          <access-date>2024-08-22</access-date>
          <publisher-loc>Washington, D.C</publisher-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://documents.worldbank.org/en/publication/documents-reports/documentdetail/248371559325561562/id4d-practitioner-s-guide">https://documents.worldbank.org/en/publication/documents-reports/documentdetail/248371559325561562/id4d-practitioner-s-guide</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <article-title>eHAction Interoperability Guide</article-title>
          <source>eHealth Action</source>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://ehaction.eu/interoperability-guide/">http://ehaction.eu/interoperability-guide/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <article-title>Recommendations of interoperability standards for projects managing clinical data and medical images: the INCISIVE case</article-title>
          <source>INCISIVE</source>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://incisive-project.eu/new/recommendations-of-interoperability-standards-for-projects-managing-clinical-data-and-medical-images-the-incisive-case/">https://incisive-project.eu/new/recommendations-of-interoperability-standards-for-projects-managing-clinical-data-and-medical-images-the-incisive-case/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <article-title>Ethics and governance of artificial intelligence for health, WHO guidance</article-title>
          <source>World Health Organization</source>
          <year>2021</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://iris.who.int/bitstream/handle/10665/341996/9789240029200-eng.pdf?sequence=1">https://iris.who.int/bitstream/handle/10665/341996/9789240029200-eng.pdf?sequence=1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <article-title>Ethics and governance of artificial intelligence for health, guidance on large multi-modal models</article-title>
          <source>World Health Organization</source>
          <year>2024</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://iris.who.int/bitstream/handle/10665/375579/9789240084759-eng.pdf?sequence=1">https://iris.who.int/bitstream/handle/10665/375579/9789240084759-eng.pdf?sequence=1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>IHE IT infrastructure white paper: enabling document sharing health information exchange using IHE profiles</article-title>
          <source>Integrating the Healthcare Enterprise</source>
          <year>2024</year>
          <access-date>2024-08-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://profiles.ihe.net/ITI/HIE-Whitepaper/#3-document-sharing-profiles">https://profiles.ihe.net/ITI/HIE-Whitepaper/#3-document-sharing-profiles</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Pfaff</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Prud'hommeaux</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Huo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ruddy</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Chute</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>FHIR-ontop-OMOP: building clinical knowledge graphs in FHIR RDF with the OMOP common data model</article-title>
          <source>J Biomed Inform</source>
          <year>2022</year>
          <volume>134</volume>
          <fpage>104201</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(22)00206-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2022.104201</pub-id>
          <pub-id pub-id-type="medline">36089199</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(22)00206-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC9561043</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <article-title>Retrieval of Real World Data for Clinical Research</article-title>
          <source>HL7 International</source>
          <access-date>2024-02-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://build.fhir.org/ig/HL7/vulcan-rwd/">https://build.fhir.org/ig/HL7/vulcan-rwd/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
          <article-title>Forms that do it all</article-title>
          <source>Fillout</source>
          <access-date>2024-12-09</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fillout.com">https://www.fillout.com</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <article-title>European Health Data Space (EHDS2) interoperability toolkit</article-title>
          <source>Made with Fillout</source>
          <access-date>2025-04-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://forms.fillout.com/t/juxLYSKmMwus">https://forms.fillout.com/t/juxLYSKmMwus</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hussein</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Balaur</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Burmann</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ćwiek-Kupczyńska</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Gadiya</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ghosh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jayathissa</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Katsch</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kremer</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lähteenmäki</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Meng</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Morasek</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>C Rancourt</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Satagopam</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Sauermann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Scheider</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stamm</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Muehlendyck</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gribbon</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Getting ready for the European health data space (EHDS): IDERHA's plan to align with the latest EHDS requirements for the secondary use of health data</article-title>
          <source>Open Res Eur</source>
          <year>2024</year>
          <volume>4</volume>
          <fpage>160</fpage>
          <pub-id pub-id-type="doi">10.12688/openreseurope.18179.1</pub-id>
          <pub-id pub-id-type="medline">39185338</pub-id>
          <pub-id pub-id-type="pmcid">PMC11342032</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Kolfschooten</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>van Oirschot</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The EU artificial intelligence act (2024): implications for healthcare</article-title>
          <source>Health Policy</source>
          <year>2024</year>
          <volume>149</volume>
          <fpage>105152</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0168-8510(24)00162-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.healthpol.2024.105152</pub-id>
          <pub-id pub-id-type="medline">39244818</pub-id>
          <pub-id pub-id-type="pii">S0168-8510(24)00162-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baumgart</surname>
              <given-names>DC</given-names>
            </name>
          </person-group>
          <article-title>An intriguing vision for transatlantic collaborative health data use and artificial intelligence development</article-title>
          <source>NPJ Digit Med</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>19</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-024-01005-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-024-01005-y</pub-id>
          <pub-id pub-id-type="medline">38263436</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-024-01005-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC10806986</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
