<?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">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</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">v9i1e63396</article-id>
      <article-id pub-id-type="pmid">39964739</article-id>
      <article-id pub-id-type="doi">10.2196/63396</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Exploring Metadata Catalogs in Health Care Data Ecosystems: Taxonomy Development Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Arayici</surname>
            <given-names>Yusuf</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Gersch</surname>
            <given-names>Martin</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Scheider</surname>
            <given-names>Simon</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Fraunhofer Institute for Software and Systems Engineering</institution>
            <addr-line>Speicherstraße 6</addr-line>
            <addr-line>Dortmund, 44147</addr-line>
            <country>Germany</country>
            <phone>49 231976774</phone>
            <email>simon.scheider@isst.fraunhofer.de</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4704-2833</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Mallick</surname>
            <given-names>Mostafa Kamal</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0009-2572-931X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Fraunhofer Institute for Software and Systems Engineering</institution>
        <addr-line>Dortmund</addr-line>
        <country>Germany</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Simon Scheider <email>simon.scheider@isst.fraunhofer.de</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>18</day>
        <month>2</month>
        <year>2025</year>
      </pub-date>
      <volume>9</volume>
      <elocation-id>e63396</elocation-id>
      <history>
        <date date-type="received">
          <day>19</day>
          <month>6</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>6</day>
          <month>8</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>20</day>
          <month>8</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>12</day>
          <month>12</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Simon Scheider, Mostafa Kamal Mallick. Originally published in JMIR Formative Research (https://formative.jmir.org), 18.02.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 JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2025/1/e63396" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>In the European health care industry, recent years have seen increasing investments in data ecosystems to “FAIRify” and capitalize the ever-rising amount of health data. Within such networks, health metadata catalogs (HMDCs) assume a key function as they enable data allocation, sharing, and use practices. By design, HMDCs orchestrate health information for the purpose of findability, accessibility, interoperability, and reusability (FAIR). However, despite various European initiatives pushing health care data ecosystems forward, actionable design knowledge about HMDCs is scarce. This impedes both their effective development in practice and their scientific exploration, causing huge unused innovation potential of health data.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to explore the structural design elements of HMDCs, classifying them alongside empirically reasonable dimensions and characteristics. In doing so, the development of HMDCs in practice is facilitated while also closing a crucial gap in theory (ie, the literature about actionable HMDC design knowledge).</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We applied a rigorous methodology for taxonomy building following well-known and established guidelines from the domain of information systems. Within this methodological framework, inductive and deductive research methods were applied to iteratively design and evaluate the evolving set of HMDC dimensions and characteristics. Specifically, a systematic literature review was conducted to identify and analyze 38 articles, while a multicase study was conducted to examine 17 HMDCs from practice. These findings were evaluated and refined in 2 extensive focus group sessions by 7 interdisciplinary experts with deep knowledge about HMDCs.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The artifact generated by the study is an iteratively conceptualized and empirically grounded taxonomy with elaborate explanations. It proposes 20 dimensions encompassing 101 characteristics alongside which FAIR HMDCs can be structured and classified. The taxonomy describes basic design characteristics that need to be considered to implement FAIR HMDCs effectively. A major finding was that a particular focus in developing HMDCs is on the design of their published dataset offerings (ie, their metadata assets) as well as on data security and governance. The taxonomy is evaluated against the background of 4 use cases, which were cocreated with experts. These illustrative scenarios add depth and context to the taxonomy as they underline its relevance and applicability in real-world settings.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The findings contribute fundamental, yet actionable, design knowledge for building HMDCs in European health care data ecosystems. They provide guidance for health care practitioners, while allowing both scientists and policy makers to navigate through this evolving research field and anchor their work. Therefore, this study closes the research gap outlined earlier, which has prevailed in theory and practice.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>data catalogs</kwd>
        <kwd>data ecosystems</kwd>
        <kwd>findability, accessibility, interoperability, and reusability</kwd>
        <kwd>FAIR</kwd>
        <kwd>health care</kwd>
        <kwd>metadata</kwd>
        <kwd>taxonomy</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Challenges of Health Care Systems</title>
        <p>In the 21st century, health care systems worldwide are experiencing a tremendous increase in data, driven by advances in medical technology, digital health records, and wearable devices [<xref ref-type="bibr" rid="ref1">1</xref>]. This flood of data holds immense potential for data-driven health innovations, building upon large-scale real-world data (RWD) and real-world evidence (RWE) [<xref ref-type="bibr" rid="ref2">2</xref>]. However, health care systems face multiple challenges that hinder the effective use of RWD to generate RWE and thus data-driven health innovations. One primary issue is the integration of heterogeneous datasets [<xref ref-type="bibr" rid="ref3">3</xref>]. RWD stem from diverse sources, such as electronic health records, imaging, and genomic data, frequently exhibiting incompatible or unknown data formats, which complicates harmonization, particularly across different entities [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Furthermore, finding and accessing suitable RWD represents a hurdle for medical research due to their origins from disparate patient populations, health care systems, and data collection methodologies [<xref ref-type="bibr" rid="ref6">6</xref>]. This impairs the effective discovery of and access to a sufficient number of both available and adequate datasets. Moreover, even if enough RWD are discovered and access is established, another challenge lies in ensuring scientific rigor and reproducibility of generated RWE (ie, medical studies) that becomes increasingly difficult in today’s data-intensive health research [<xref ref-type="bibr" rid="ref7">7</xref>]. Medical studies constantly require larger, high-quality datasets to generate meaningful and reproducible RWE [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. However, unknown RWD management practices threaten study reliability, while making the validation of results (ie, RWE) across studies difficult [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. Besides that, the diversity of national health care systems increases the prevailing differences in health care data infrastructures across countries that, in turn, lead to additional barriers for organizations to share and use RWD at a large scale [<xref ref-type="bibr" rid="ref9">9</xref>]. Moreover, health care systems must navigate complex legal requirements with regard to sharing and processing RWD [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. For instance, the European jurisdiction mandates strict data governance and security standards that, while essential, impair data-driven health innovations in the absence of adequate data-sharing infrastructures [<xref ref-type="bibr" rid="ref9">9</xref>]. As a result, RWD are fragmented and isolated within single organizations, whereby data sharing and use are limited. Because of all these challenges, the rapidly increasing amount of RWD cannot be harnessed to its full potential for producing health care innovations (ie, RWE).</p>
      </sec>
      <sec>
        <title>Metadata Catalogs as a Promising Solution</title>
        <p>Against this background, data ecosystems as technical and organizational infrastructures within the healthcare sector represent auspicious solutions, that is, <italic>health care data ecosystems</italic> (amplified in, eg, the studies by Lovestone and EMIF Consortium [<xref ref-type="bibr" rid="ref10">10</xref>], Manogaran et al [<xref ref-type="bibr" rid="ref11">11</xref>], and Sharon and Lucivero [<xref ref-type="bibr" rid="ref12">12</xref>]). These evolving networks enable legally compliant use of RWD [<xref ref-type="bibr" rid="ref13">13</xref>]. Their key function is market mechanisms instantiated by metadata catalogs [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref14">14</xref>] that define and describe the intricate web of RWD circulating between a potentially arbitrary number of actors in the ecosystem [<xref ref-type="bibr" rid="ref15">15</xref>]. Hence, such <italic>health metadata catalogs</italic> (HMDCs) are crucial components of modern health care data ecosystems, for example, EHDEN (European Health Data and Evidence Network), EHDS2 (European Health Data Space 2), Elixir, EUCAIM (European Federation for Cancer Images), IDERHA (Integration of Heterogeneous Data and Evidence towards Regulatory and Health Technology Assessment Acceptance), and Gaia-X. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> provides a comprehensive overview about the most important European Union (EU) initiatives. For example, EHDS2 aims at creating a European infrastructure for the secure exchange and secondary use of health data across EU member states [<xref ref-type="bibr" rid="ref16">16</xref>]. Therein, HMDCs belong to the core infrastructure services to enable standardized organization of and controlled access to RWD for research. The pilot infrastructure of the EHDS is implemented by the HealthData@EU initiative.</p>
        <p>Since HMDCs provide an effective method for systematically sharing and using RWD within data ecosystems [<xref ref-type="bibr" rid="ref3">3</xref>], they potentially allow harnessing crucial benefits corresponding to the challenges outlined earlier. First, HMDCs facilitate integrating heterogenous datasets across health care systems. They help to transcend diverse data types, which eases the integration, standardization, and harmonization of data within data ecosystems [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. This is essential for medical research that requires huge pools of accessible RWD appropriate for their investigations [<xref ref-type="bibr" rid="ref7">7</xref>]. Second, as finding and accessing adequate RWD effectively is vital for medical research [<xref ref-type="bibr" rid="ref6">6</xref>], HMDCs entail added value by offering a governed data search and access framework embedded into the technical infrastructures of the underlying ecosystems [<xref ref-type="bibr" rid="ref17">17</xref>]. They provide a tool for data discovery to precisely characterize, locate, and filter RWD on the basis of a myriad of factors [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Third, HMDCs support transparent and reproducible research processes by helping scientists in replicating studies and validating their results [<xref ref-type="bibr" rid="ref18">18</xref>]. Such transparency is fundamental for building trust in the reliability and validity of RWE [<xref ref-type="bibr" rid="ref2">2</xref>]. Finally, HMDCs facilitate data-intensive research, generally, as they establish unified health care data infrastructures for allocating, accessing, and using RWD of connected data providers [<xref ref-type="bibr" rid="ref19">19</xref>]. In doing so, they reduce barriers for organizations to integrate their otherwise isolated RWD within data ecosystems. At the same time, HMDCs bridge prevailing differences between national health care systems and retain full control of data providers [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. To this end, they establish robust data security and governance frameworks that are aligned to the applicable jurisdictions [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
        <p>As a result, HMDCs represent an auspicious medium against the fragmentation and isolation of RWD [<xref ref-type="bibr" rid="ref5">5</xref>]. However, since HMDCs are novel constructs, typically in premature phases [<xref ref-type="bibr" rid="ref20">20</xref>], their ascribed benefits are primarily backed by the literature rather than evidence from practice. Nevertheless, HMDCs are likely to provide means for using RWD systematically within and across health care data ecosystems, potentially resulting in more efficient RWE generation.</p>
        <p>In Europe, HMDCs are of particular importance because the EU health care sector exhibits a broad diversity across member states, all with their own health care systems and policies. Consequently, there is a need to focus heavily on standardizing and harmonizing both data and metadata across different countries for facilitating data sharing and legally compliant data use [<xref ref-type="bibr" rid="ref21">21</xref>]. More specifically, the diversity of national health care systems [<xref ref-type="bibr" rid="ref22">22</xref>], the restrictiveness of data protection regulations [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], and the fragmentation and isolation of health data [<xref ref-type="bibr" rid="ref23">23</xref>] make operative health care data ecosystems and HMDCs a paramount concern for the European health care industry. Therefore, this study adopts a European focus.</p>
      </sec>
      <sec>
        <title>Theoretical Background</title>
        <p>Originally, data catalogs are organized collections of datasets that provide descriptive information within an organization [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. They act as centralized repositories, making it easier for data consumers to discover, understand, and access the information they need [<xref ref-type="bibr" rid="ref26">26</xref>]. Enterprise data management platforms often comprise such centralized data catalogs implying storage of data within their peripheries [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. If data are not encapsulated within the organization but integrated into decentral or federated networks [<xref ref-type="bibr" rid="ref28">28</xref>], the literature commonly refers to such environments as data ecosystems with metadata catalogs as key function [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. This study considers metadata catalogs as decentralized or federated constructs that are mutually exclusive to centralized ones. For simplification, only the term decentralized is used.</p>
        <p>Metadata describe dataset attributes, such as source, format, structure, provenance, owner, access, or governance modalities [<xref ref-type="bibr" rid="ref29">29</xref>]. Metadata catalogs act as “catalogues of data catalogues,” dedicated to enhancing discoverability, usability, and management of distributed datasets [<xref ref-type="bibr" rid="ref30">30</xref>]. Within data ecosystems, metadata catalogs are a mechanism that provides a standardized way for recording, disclosing, and making available information about all relevant kinds of phenotypes describing datasets, while ensuring legally compliant access and sharing practices [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. If these datasets are health data, it is henceforth referred to such constructs as <italic>HMDCs</italic>. Consequently, HMDCs manage heterogenous health information integrated into health care data ecosystems [<xref ref-type="bibr" rid="ref5">5</xref>]. They ensure that these diverse and highly sensitive datasets are effectively organized and understood [<xref ref-type="bibr" rid="ref4">4</xref>], while facilitating their systematic use [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. This requires dedicated, yet unknown, design elements to be unveiled by the study.</p>
      </sec>
      <sec>
        <title>Research Gap, Objective, and Questions</title>
        <p>After having clarified the added value of HMDCs, the research gap is demarcated by reviewing related work. Therefrom, the research problem is identified, which leads to the research objectives. These objectives then allow to derive the research questions, required to define a meaningful research methodology.</p>
        <p>To begin with, Labadie et al [<xref ref-type="bibr" rid="ref24">24</xref>] foster the understanding of data catalogs by classifying corresponding initiatives. The authors propose a taxonomy for data catalogs and present 3 case studies. However, similar to Ehrlinger et al [<xref ref-type="bibr" rid="ref26">26</xref>] and Jahnke and Otto [<xref ref-type="bibr" rid="ref25">25</xref>], Labadie et al [<xref ref-type="bibr" rid="ref24">24</xref>] focus on intraorganizational data sharing using centralized catalogs. Moreover, they neglected health use cases. Remy et al [<xref ref-type="bibr" rid="ref3">3</xref>] conducted a design science study to build an integrated catalog for health research metadata. The artifact enables medical scientists to analyze phenomena that require a view across several domains. The authors are among the first who provide design knowledge usable in HMDC contexts. Although, similar to the findings of the previously presented literature sources, Remy et al [<xref ref-type="bibr" rid="ref3">3</xref>] accentuate centralized catalogs. Almeida et al [<xref ref-type="bibr" rid="ref19">19</xref>] present a platform that provides a set of tools, compliant with the findability, accessibility, interoperability, and reusability (FAIR) principles, to help data holders sharing biomedical databases while allowing data consumers to discover and apply for them. However, the authors only consider a narrow use case instead of generating universally applicable design knowledge. Similarly, Oliveira et al [<xref ref-type="bibr" rid="ref15">15</xref>] developed a holistic stakeholder agnostic catalog framework for biomedical datasets. Researchers can explore metadata held decentralized at federated nodes, with distinct levels of granularity being conceivable. Extending this initial design knowledge specific to biomedical data, Swertz et al [<xref ref-type="bibr" rid="ref5">5</xref>] proposed a unified framework for sharing health data across catalogs. It encompasses multiple centralized and decentralized catalogs. The authors offer recommendations to establish an integrated community as an open catalog ecosystem. This theoretical basis for HMDCs builds upon and is enriched by similar research. Specifically, Bergeron et al [<xref ref-type="bibr" rid="ref17">17</xref>] developed a catalog toolkit to support creating comprehensive as well as user- and study-friendly HMDCs. Almeida and Oliveira [<xref ref-type="bibr" rid="ref30">30</xref>] produced a framework to simplify the process of building an HMDC for exposing metadata, while providing analysis capacities. Apparently, there is a tendency from centralized to decentralized data catalogs in health care. However, for HMDCs, a <italic>research gap</italic> prevails concerning (1) empirically grounded and actionable design knowledge that is (2) universally applicable to (3) the broad array of use cases and EU initiatives associated with health care data ecosystems.</p>
        <p>In general, the generation of design knowledge about an artifact is crucial as it provides the intellectual foundation to advance the respective body of scientific knowledge, while facilitating development efforts in practice [<xref ref-type="bibr" rid="ref31">31</xref>]. In particular, HMDC design knowledge can harmonize and sustain the multitude of different EU initiatives by following a systematic approach to problem-solving [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. Therefore, its generation must adhere to a rigor design process [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. This process must ensure empirical grounding for the sake of efficiency, effectiveness, and quality assurance, which inevitably favors quality, adaptiveness, and impact of the generated results [<xref ref-type="bibr" rid="ref35">35</xref>]. Likewise, the prevailing lack of design knowledge causes difficulties concerning the adoption and use of HMDCs in practice and theory, revealing the <italic>research problem</italic>. To remedy this problem, the <italic>research objective</italic> is to provide actionable design knowledge that is universally applicable in real-world HMDC use cases, thus allowing to infer the following <italic>research questions</italic> (RQs):</p>
        <list list-type="bullet">
          <list-item>
            <p>RQ1:</p>
            <p>What are taxonomy elements (ie, dimensions and characteristics) to structure HMDCs from a design science perspective?</p>
          </list-item>
          <list-item>
            <p>RQ2:</p>
            <p>How does the proposed taxonomy effect real-world use cases?</p>
          </list-item>
        </list>
        <p>According to Hevner et al [<xref ref-type="bibr" rid="ref33">33</xref>], a <italic>design science</italic> perspective means to examine and create information system (IS) artifacts to solve practical problems. A taxonomy is a suitable approach to address RQ1 because it provides a set of elementary building blocks and prescriptions for effectively designing such artifacts [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. It targets a broad and diverse audience, including health care IS engineers and architects, health data holders and scientists, health care economists and researchers, as well as legal and ethical regulatory bodies, while accentuating the European health care sector.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>Taxonomies are common approaches in IS research to classify, understand, and examine complex issues [<xref ref-type="bibr" rid="ref38">38</xref>]. For their development, the method of Nickerson et al [<xref ref-type="bibr" rid="ref37">37</xref>] is applied to identify dimensions and characteristics of HMDCs. The authors propose generating knowledge conceptually (eg, from the literature) and empirically (eg, analyzing objects of interest). This approach is referred to as the gold standard to build taxonomies in IS research [<xref ref-type="bibr" rid="ref36">36</xref>]. As refinement, the methodological update of Kundisch et al [<xref ref-type="bibr" rid="ref36">36</xref>] is incorporated, adding an evaluation process by means of focus groups. The authors’ refinement enhances the assessment of value created by the taxonomy [<xref ref-type="bibr" rid="ref39">39</xref>]. Corresponding to these 2 methods, the research design is divided into the 7 steps shown in <xref rid="figure1" ref-type="fig">Figure 1</xref> based on the studies by Nickerson et al [<xref ref-type="bibr" rid="ref37">37</xref>] and Kundisch et al [<xref ref-type="bibr" rid="ref36">36</xref>]. The numbers 1 to 7 represent methodological steps explained in the following sections.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Applied research method of the taxonomy development study based on Nickerson et al [<xref ref-type="bibr" rid="ref37">37</xref>] and Kundisch et al [<xref ref-type="bibr" rid="ref36">36</xref>].</p>
          </caption>
          <graphic xlink:href="formative_v9i1e63396_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>In step 1 in <xref rid="figure1" ref-type="fig">Figure 1</xref>, a <italic>meta-characteristic</italic>  is specified in orientation towards the taxonomy’s purpose so that each subordinated characteristic and dimension follows from it. On the basis of RQ1, the meta-characteristic was defined as “distinguishing key design elements of HMDCs.” It facilitates selecting meta-dimensions as well as inferring characteristics and classifying them to dimensions. To define the meta-dimensions, the FAIR framework was used [<xref ref-type="bibr" rid="ref7">7</xref>]. These well-known data principles postulate an accepted approach to the discoverability and usability of RWD [<xref ref-type="bibr" rid="ref19">19</xref>]. While FAIR emphasizes making data interoperable and reusable, it inherently involves considerations related to data governance and harmonization [<xref ref-type="bibr" rid="ref40">40</xref>].</p>
        <p>In step 2 in <xref rid="figure1" ref-type="fig">Figure 1</xref>, <italic>ending conditions</italic> for the iterative part of the process are defined, determining its termination criteria. The ending conditions were chosen on the basis of Nickerson et al [<xref ref-type="bibr" rid="ref37">37</xref>] and Scheider et al [<xref ref-type="bibr" rid="ref41">41</xref>] in terms of subjective and objective criteria. Ultimately, 6 design iterations were required until all conditions listed in <xref ref-type="table" rid="table1">Table 1</xref> were fulfilled.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Ending conditions for taxonomy development adopted from Nickerson et al [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="490"/>
            <col width="0"/>
            <col width="80"/>
            <col width="0"/>
            <col width="80"/>
            <col width="0"/>
            <col width="80"/>
            <col width="0"/>
            <col width="80"/>
            <col width="0"/>
            <col width="80"/>
            <col width="0"/>
            <col width="80"/>
            <col width="0"/>
            <col width="0"/>
            <col width="0"/>
            <col width="0"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Ending conditions</td>
                <td colspan="13">Design iterations</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <break/>
                </td>
                <td colspan="2">1</td>
                <td colspan="2">2</td>
                <td colspan="2">3</td>
                <td colspan="2">4</td>
                <td colspan="2">5</td>
                <td colspan="2">6</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="17">
                  <bold>Objective</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>All papers were examined.</td>
                <td colspan="2"/>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>No object was merged with another or split.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Each characteristic is classified by one object.</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>No new dimensions or characteristics were added.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Dimensions or characteristics were neither merged nor split.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Each dimension is unique and not duplicated.</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Every characteristic is unique within its dimension.</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Each cell is unique and not repeated.</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="18">
                  <bold>Subjective</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Conciseness: no unnecessary dimensions and characteristics</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Robust: dimensions and characteristics differentiate objects</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Comprehensiveness: all objects can be classified</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Extension: dimensions and characteristics can be added easily</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Explanatory: dimensions and characteristics describe all objects</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
                <td colspan="4">
                  <break/>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In steps 3 to 5 in <xref rid="figure1" ref-type="fig">Figure 1</xref>, we repeatedly chose between either an inductive or a deductive path. The former is a conceptual-to-empirical attempt (step 4a in <xref rid="figure1" ref-type="fig">Figure 1</xref>) to infer dimensions and characteristics from theory. The latter reflects an empirical-to-conceptual procedure (E2C; step 4b in <xref rid="figure1" ref-type="fig">Figure 1</xref>) to derive characteristics from real-world analysis objects and to classify them in dimensions. After each iteration (ie, steps 3 to 5 in <xref rid="figure1" ref-type="fig">Figure 1</xref>), the ending conditions are checked (ie, step 5 in <xref rid="figure1" ref-type="fig">Figure 1</xref>). If all ending conditions are fulfilled, an evaluation step (ie, step 6 in <xref rid="figure1" ref-type="fig">Figure 1</xref>) follows, integrated by focus groups [<xref ref-type="bibr" rid="ref36">36</xref>]. In case the focus group iteration does not imply changes to the taxonomy (ie, step 7 in <xref rid="figure1" ref-type="fig">Figure 1</xref>), the artifact is finished and the methodological process terminates. After 5 design iterations (ie, 4 times of executing steps 4a and 4b and executing step 6 once in <xref rid="figure1" ref-type="fig">Figure 1</xref>), all ending conditions were fulfilled (ie, step 5 in <xref rid="figure1" ref-type="fig">Figure 1</xref>) and the subsequent focus group did not result in any major changes (ie, step 7 in <xref rid="figure1" ref-type="fig">Figure 1</xref>). Thus, the taxonomy was completed [<xref ref-type="bibr" rid="ref36">36</xref>]. Because 6 design iterations were traversed and it was ensured that the focus group experts covered all dimensions relevant for HMDCs, the taxonomy achieved result saturation.</p>
        <p>To ensure transparency of the taxonomy development process, <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> shows intermediary taxonomies after certain iterations. Furthermore, it offers a table linking key references from the inductive (ie, the literature) and deductive iterations (ie, analysis objects) to the dimensions of the final taxonomy [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref78">78</xref>].</p>
      </sec>
      <sec>
        <title>Inductive Design Iterations for Taxonomy Development</title>
        <p>In the first iteration, an initial set of dimensions and characteristics was derived from former research (ie, step 4a in <xref rid="figure1" ref-type="fig">Figure 1</xref>), consolidating the related work addressed in the Introduction section.</p>
        <p>In the second iteration, a structured literature review (SLR) was carried out (ie, step 4a in <xref rid="figure1" ref-type="fig">Figure 1</xref>) [<xref ref-type="bibr" rid="ref36">36</xref>]. The method of Kitchenham et al [<xref ref-type="bibr" rid="ref79">79</xref>] was applied (ie, 1-6), while orienting toward its application in the study by Scheider et al [<xref ref-type="bibr" rid="ref41">41</xref>]. At the outset, RQ1 was adopted as the (1) research question guiding the SLR. The (2) search process comprised HMDC-related conference and journal papers. The search string was defined as (ALL (health AND data AND catalog) OR ALL (health AND metadata AND catalog) AND ALL (data AND catalog AND technologies)). Primarily, Scopus and IEEE Xplore were used, and the operands were deployed on documents’ titles, abstracts, and authors’ keywords. The 2 databanks were leveraged due to their multidisciplinary nature covering research in all fields relevant for HMDCs. Following Scheider et al [<xref ref-type="bibr" rid="ref41">41</xref>], (3) inclusion and exclusion criteria were created to identify and filter papers. First, the literature not available in English was excluded. Second, inaccessible papers were removed. Third, each paper retrieved was reviewed by 2 researchers for whether it covers HMDCs in the broader sense. This means that papers had to address a design perspective, as defined by Hevner et al [<xref ref-type="bibr" rid="ref33">33</xref>]. Articles were emphasized that dealt with “patient-related” data, while ones about aggregated health data (eg, regions and countries) were neglected. The same holds true for catalogs about health-oriented surveys and analysis results (eg, studies). Due to broadly formulated keywords in the search string, initially retrieved literature contained many papers outside the thematical scope. To this end, the third inclusion or exclusion criterion was examined by screening titles and abstracts before reviewing the entire content of the papers. Since 2 researchers constantly worked together in (3), one can argue for reliable objectivity in paper selection.</p>
        <p>Building upon the inclusion and exclusion criteria, the initial (4) data collection resulted in 18 papers in the Scopus and IEEE Xplore search (iteration 4 in <xref rid="figure2" ref-type="fig">Figure 2</xref>). Subsequently, backward (ie, referenced articles) and forward (ie, citing articles) stepping was conducted [<xref ref-type="bibr" rid="ref80">80</xref>], which added 12 articles. <xref rid="figure2" ref-type="fig">Figure 2</xref> shows the SLR statistics expressed by a PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flowchart.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Structured literature review statistics presented in the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flowchart.</p>
          </caption>
          <graphic xlink:href="formative_v9i1e63396_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The SLR was expanded by a search via Google (Google Search) and the AISeL database for extension and verification. The Google search engine served to identify whitepapers using a consolidated search string compared to (2). For AISeL, the same steps executed in Scopus and IEEE Xplore were applied (ie, 2 and 3), except that the research team looked for the search terms in titles only to keep the number of results feasible. Once duplicates were removed, Google and AISeL added 8 papers to the literature collection. To test theoretical saturation [<xref ref-type="bibr" rid="ref81">81</xref>], “quick searches” were carried out in other databases (eg, ACM) checking whether the top results, first, match the inclusion and exclusion criteria and, second, are not already in the collection. Since these quick searches did not add new papers, the literature collection was considered representative [<xref ref-type="bibr" rid="ref41">41</xref>]. Excluding related work of the first iteration, the collection comprised 38 publications, of which the most important items are listed in <xref ref-type="table" rid="table2">Table 2</xref>.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>List of most important literature from the SLR<sup>a</sup> used for taxonomy development.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="310"/>
            <col width="0"/>
            <col width="70"/>
            <col width="0"/>
            <col width="590"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Study</td>
                <td colspan="3">Year</td>
                <td>Title</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="6">
                  <bold>Top 10 academic papers</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Alvarellos et al [<xref ref-type="bibr" rid="ref42">42</xref>]</td>
                <td colspan="2">2023</td>
                <td colspan="2">Democratizing clinical-genomic data: How federated platforms can promote benefits sharing in genomics</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Almeida and Oliveira [<xref ref-type="bibr" rid="ref30">30</xref>]</td>
                <td colspan="2">2024</td>
                <td colspan="2">MONTRA2<sup>b</sup>: A web platform for profiling distributed databases in the health domain</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Almeida et al [<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                <td colspan="2">2023</td>
                <td colspan="2">A FAIR<sup>c</sup> approach to real-world health data management and analysis</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Bergeron et al [<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                <td colspan="2">2018</td>
                <td colspan="2">Fostering population-based cohort data discovery: The Maelstrom Research cataloguing toolkit</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Scheider et al [<xref ref-type="bibr" rid="ref41">41</xref>]</td>
                <td colspan="2">2023</td>
                <td colspan="2">Exploring design elements of personal data markets</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ehrlinger et al [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                <td colspan="2">2021</td>
                <td colspan="2">Data catalogs: a systematic literature review and guidelines to implementation</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Labadie et al [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                <td colspan="2">2020</td>
                <td colspan="2">Fair enough? enhancing the usage of enterprise data with data catalogs</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Lovestone and EMIF Consortium [<xref ref-type="bibr" rid="ref10">10</xref>]</td>
                <td colspan="2">2020</td>
                <td colspan="2">The European medical information framework: a novel ecosystem for sharing health care data across Europe</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Oliveira et al [<xref ref-type="bibr" rid="ref15">15</xref>]</td>
                <td colspan="2">2019</td>
                <td colspan="2">EMIF<sup>d</sup> Catalogue: a collaborative platform for sharing and reusing biomedical data</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Swertz et al [<xref ref-type="bibr" rid="ref5">5</xref>]</td>
                <td colspan="2">2022</td>
                <td colspan="2">Towards an Interoperable Ecosystem of Research Cohort and Real-world Data Catalogues Enabling Multi-center Studies</td>
              </tr>
              <tr valign="top">
                <td colspan="6">
                  <bold>Top 5 nonacademic papers</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="2">European Medicines Agency [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                <td>2022</td>
                <td colspan="2">Good Practice Guide for the use of the Metadata Catalogue of Real-World Sources</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="2">European Medicines Agency [<xref ref-type="bibr" rid="ref44">44</xref>]</td>
                <td>2022</td>
                <td colspan="2">List of metadata for Real World Data catalogues</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="2">Directorate-General for Health and Food Safety [<xref ref-type="bibr" rid="ref82">82</xref>]</td>
                <td>2022</td>
                <td colspan="2">The European Health Data Space</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="2">Jahnke and Otto [<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                <td>2022</td>
                <td colspan="2">Data Catalogs - Implementing Capabilities for Data Curation, Data Enablement and Regulatory Compliance</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="2">TEHDAS<sup>e</sup> [<xref ref-type="bibr" rid="ref16">16</xref>]</td>
                <td>2022</td>
                <td colspan="2">EHDS<sup>f</sup> Semantic interoperability framework</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>SLR: structured literature review.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>MONTRA2: Modular Next-generation Research Analysis.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>FAIR: findability, accessibility, interoperability, and reusability.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>EMIF: European Medical Information Framework Catalogue.</p>
            </fn>
            <fn id="table2fn5">
              <p><sup>e</sup>TEHDAS: Towards European Health Data Space.</p>
            </fn>
            <fn id="table2fn6">
              <p><sup>f</sup>EHDS: European Health Data Space.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Throughout the steps (2) to (4), a (5) quality assessment step was integrated on the basis of the criteria suggested by Kitchenham et al [<xref ref-type="bibr" rid="ref79">79</xref>], that is, inclusion or exclusion criteria, relevant article coverage, literature corpus assessment, and study descriptions.</p>
        <p>For (6) data analysis, phrases (“quotes”) from articles with useful content for HMDC designs were extracted. Following the approaches of Saldana [<xref ref-type="bibr" rid="ref83">83</xref>] and Pratt [<xref ref-type="bibr" rid="ref84">84</xref>], those phrases were coded, inserted in a tabular structure, and iteratively generalized. As in steps (3) and (9), two researchers analyzed the literature to reduce subjectivity biases. <xref rid="figure3" ref-type="fig">Figure 3</xref> shows how quote extractions relating to the dimension of data linking are coded and design implications are derived. Particularly, whenever there was a direct connection to an HMDC context, quotes became design implications immediately, for example, linkage strategy (first quote in <xref rid="figure3" ref-type="fig">Figure 3</xref>). If a direct connection was missing (eg, linkage variable as a new characteristic; third quote in <xref rid="figure3" ref-type="fig">Figure 3</xref>), more evidence was required to transform codes into design implications (ie, second quote in <xref rid="figure3" ref-type="fig">Figure 3</xref>). Finally, considering the influential factors proposed by Mwita [<xref ref-type="bibr" rid="ref81">81</xref>] (eg, study purpose, research design, sample size variability, and analysis approach), data saturation in the SLR is likely.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Examples for literature coding for inductive taxonomy development.</p>
          </caption>
          <graphic xlink:href="formative_v9i1e63396_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Deductive Design Iterations for Taxonomy Development</title>
        <p>Applying the E2C approach (ie, step 4b <xref rid="figure1" ref-type="fig">Figure 1</xref>) in the third and fifth iterations, health data catalogs from practice were initially listed, as identified in the first 2 iterations. This set was extended by a Google search to identify analysis objects not encountered in inductive iterations. The research team searched for analysis objects using the browser’s incognito mode to circumnavigate carryover effects from previous searches [<xref ref-type="bibr" rid="ref85">85</xref>]. The keywords from the SLR were used as an orientation to avoid limiting the results unconsciously [<xref ref-type="bibr" rid="ref41">41</xref>]. Analysis objects were excluded if meaningful information could not be obtained. This characteristic was defined as access to analyzable information describing the analysis object, that is, data retrievable either from websites or demo applications [<xref ref-type="bibr" rid="ref85">85</xref>]. Analysis objects were also excluded if information was meaningful but unavailable in German or English. However, metadata catalogs under construction were not excluded per se [<xref ref-type="bibr" rid="ref41">41</xref>]. The set of analysis objects was created in the first quarter of 2024. The final analysis objects are listed in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Health metadata catalogs from practice used for taxonomy development.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="600"/>
            <col width="200"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td>HMDCs<sup>a</sup></td>
                <td>Classification</td>
                <td>Status</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>BBMRI-ERIC<sup>b</sup> Data Directory [<xref ref-type="bibr" rid="ref45">45</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Catalogue of Mental Health Measures [<xref ref-type="bibr" rid="ref46">46</xref>]</td>
                <td>Central</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Compendium Data Catalog for Healthcare [<xref ref-type="bibr" rid="ref47">47</xref>]</td>
                <td>Central</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>EHDEN<sup>c</sup> Portal [<xref ref-type="bibr" rid="ref48">48</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Elixir (BioSamples [<xref ref-type="bibr" rid="ref86">86</xref>] and FAIRsharing [<xref ref-type="bibr" rid="ref87">87</xref>])</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>EMIF<sup>d</sup> Data Catalogue [<xref ref-type="bibr" rid="ref49">49</xref>]</td>
                <td>Decentral</td>
                <td>In progress</td>
              </tr>
              <tr valign="top">
                <td>EUCAIM<sup>e</sup> Cancer Image Europe [<xref ref-type="bibr" rid="ref50">50</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>European Health Information Portal [<xref ref-type="bibr" rid="ref51">51</xref>]</td>
                <td>Central</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Fjelltopp Data Catalogues for Health [<xref ref-type="bibr" rid="ref52">52</xref>]</td>
                <td>Central</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>HealthRI<sup>f</sup> Data Catalogues [<xref ref-type="bibr" rid="ref53">53</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Helsedata Explore Data Sources [<xref ref-type="bibr" rid="ref54">54</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>IDERHA<sup>g</sup> Metadata Catalogue (no public access)</td>
                <td>Decentral</td>
                <td>In progress</td>
              </tr>
              <tr valign="top">
                <td>IHME<sup>h</sup> Global Health Data Exchange [<xref ref-type="bibr" rid="ref88">88</xref>]</td>
                <td>Central</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>IQVIA<sup>i</sup> Health Data Catalogue [<xref ref-type="bibr" rid="ref55">55</xref>]</td>
                <td>Central</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Kraken Health Data Pilot [<xref ref-type="bibr" rid="ref56">56</xref>]</td>
                <td>Decentral</td>
                <td>In progress</td>
              </tr>
              <tr valign="top">
                <td>Lifebit Precision Medicine Data Catalogue [<xref ref-type="bibr" rid="ref57">57</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>MACH<sup>j</sup> Clinical and Research Data Catalogue [<xref ref-type="bibr" rid="ref89">89</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Maelstrom Research Data Catalogue [<xref ref-type="bibr" rid="ref58">58</xref>]</td>
                <td>Decentral</td>
                <td>Operative</td>
              </tr>
              <tr valign="top">
                <td>Yoda Trials Data Catalogue [<xref ref-type="bibr" rid="ref59">59</xref>]</td>
                <td>Decentral</td>
                <td>In progress</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>HMDC: health metadata catalog.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>BBMRI-ERIC: Biobanking and Biomolecular Resources Research Infrastructure – European Research Infrastructure Consortium.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>EHDEN: European Health Data and Evidence Network.</p>
            </fn>
            <fn id="table3fn4">
              <p><sup>d</sup>EMIF: European Medical Information Framework.</p>
            </fn>
            <fn id="table3fn5">
              <p><sup>e</sup>EUCAIM: European Federation for Cancer Images.</p>
            </fn>
            <fn id="table3fn6">
              <p><sup>f</sup>HealthRI: Health Research Infrastructure.</p>
            </fn>
            <fn id="table3fn7">
              <p><sup>g</sup>IDERHA: Integration of Heterogeneous Data and Evidence towards Regulatory and Health Technology Assessment Acceptance.</p>
            </fn>
            <fn id="table3fn8">
              <p><sup>h</sup>IHME: Institute for Health Metrics and Evaluation.</p>
            </fn>
            <fn id="table3fn9">
              <p><sup>i</sup>IQVIA: Information, Quality, Value, Innovation, and Access.</p>
            </fn>
            <fn id="table3fn10">
              <p><sup>j</sup>MACH: Melbourne Academic Centre for Health.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>The catalogs were examined by classifying them alongside the design elements of the preliminary taxonomy (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). We tried to assign a catalog to a single characteristic in each dimension. This deductive activity was conducted by 2 researchers, whereby three cases could occur [<xref ref-type="bibr" rid="ref41">41</xref>]: (1) on the basis of available information, the analysis object could be assigned to an existing characteristic in a dimension; (2) due to a lack of available information, the analysis object could not be assigned to any characteristic in a dimension; and (3) the analysis object contained information about a dimension but could not be associated with a characteristic defined therein. Evidently, the third case led to modifications of a current set of taxonomy design elements. During the third iteration, the occurrence of this case decreased continuously until only the first and second ones appeared. Because the ending conditions were fulfilled at that time, the taxonomy-building process was terminated and the first focus group session started. Alterations were proposed by focus group members in this session. This led to another E2C approach as the fifth iteration in which specific design elements were emphasized, as addressed by the focus group experts. The corresponding analysis procedure (ie, 1-3) remained the same as in the third iteration, while examining decentral analysis objects only (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
      </sec>
      <sec>
        <title>Evaluative Design Iterations for Taxonomy Development and Use Case Cocreation</title>
        <p>Following <xref rid="figure1" ref-type="fig">Figure 1</xref>, an evaluation by focus groups is needed after the fulfillment of all ending conditions (ie, in step 6). Focus groups help gather more data than individual interviews, since experts respond to the input of others, triggering discussions and idea generation [<xref ref-type="bibr" rid="ref23">23</xref>]. According to Szopinski et al [<xref ref-type="bibr" rid="ref39">39</xref>], focus groups are particularly suitable to assess the comprehensiveness, robustness, understandability, and extensibility of a taxonomy, as well as the shape of dimensions and characteristics. Members were recruited on the basis of the target audience of the taxonomy (see section about Research gap, objective, and questions). We ensured that they have substantial knowledge with regard to HMDCs, stemming from EU initiatives (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Ultimately, the focus group consisted of 7 experts. However, scheduling conflicts affected the organization of meetings. The first focus group had to be split into 2 sessions, involving 5 experts. The second focus group iteration required 3 separate sessions to accommodate all 7 experts. <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> shows the distribution of experts to sessions per iteration. Focus group sessions occurred in the fourth and sixth iteration. Their rough agenda was as follows: (1) the objective of the taxonomy (only fourth iteration) and current version (fourth and sixth iteration) were presented; (2) a dimension with its characteristics was explained; (3) experts shared their expectations about this dimension, especially with regard to real-world use cases; and (4) we triggered discussions by contrasting expectations. Because the focus groups served for evaluation purposes and concrete design elements were discussed in the plenum directly, we dispensed with detailed coding. This lightweight effort is inspired and justified by similar research studies published in high-ranking IS journals [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Therefore, we argue that our approach successfully mitigates any subjectivity biases because specific taxonomy design elements were addressed and discussed in the focus groups directly. This narrow focus led to the derivation of tangible design activities (ie, deletion, addition, alteration, and renaming of design elements and cocreation of use cases).</p>
        <p>In the fourth iteration, the focus group resulted in substantial changes of dimensions and characteristics, particularly regarding taxonomy elements of data accessibility and findability (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). On the contrary, the second session in the sixth iteration caused minor adjustments only (eg, renaming a few characteristics), emphasizing the cocreation of use cases. Finally, the third session of the sixth iteration merely led to refined use case formulations and merging of content. Given these small adjustments, a sufficient saturation in results was considered [<xref ref-type="bibr" rid="ref23">23</xref>] and the taxonomy development was terminated (ie, step 7). <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> lists the focus group members who participated in the evaluation of the taxonomy and the cocreation of use cases during the fourth and sixth iterations. It further states the EU initiatives the experts were recruited from and whether these initiatives have an operative HMDC or one that is still under development.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>In the run-up to the sessions, the experts received an information sheet explaining the study context, the procedure, and the approach to gathering and processing interview data. It was assured that no personal information will be disclosed. Experts were informed about their right to opt out. During the focus group sessions, only anonymous interview data in the form of handwritten notes were collected. Neither a video or voice recording nor the transcription of interview material was used. Experts did not receive any financial compensation. Hence, conducting focus groups did not require the official approval of an ethics review committee.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Taxonomy for FAIR HMDCs</title>
        <sec>
          <title>Overview</title>
          <p><xref ref-type="table" rid="table4">Table 4</xref> shows the taxonomy containing 20 dimensions (<italic>D<sub>n</sub></italic>) and 101 characteristics (<italic>C<sub>nm</sub></italic>) structured alongside the FAIR data principles as meta-dimensions [<xref ref-type="bibr" rid="ref40">40</xref>]. For visualization, morphologies were considered (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>) as they demonstrate the structure and arrangement of taxonomy elements [<xref ref-type="bibr" rid="ref90">90</xref>]. Importantly, the meta-dimension of data accessibility has exclusive dimensions pertaining to the general design of HMDCs. The other meta-dimensions relate to design elements of metadata assets published <italic>within</italic> the HMDC and the data accessibility constraints. On the basis of the study by Nickerson et al [<xref ref-type="bibr" rid="ref37">37</xref>], nonexclusiveness was chosen for some of the dimensions associated with metadata assets. The reason is that they propose structural characteristics, which might be accumulated for creating effective metadata assets in an HMDC. Exclusivity of dimensions allows to categorize design elements into mutually distinct characteristics, ensuring clarity and avoiding overlaps. Nonexclusivity can accommodate complex multidimensional relationships by enabling design elements belonging to multiple characteristics [<xref ref-type="bibr" rid="ref37">37</xref>]. Correspondingly, the difference between OR and XOR in the middle column of <xref ref-type="table" rid="table4">Table 4</xref> is that OR is used for nonexclusive characteristics, while XOR is used for exclusive ones.</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Taxonomy of FAIR<sup>a</sup> HMDCs<sup>b</sup> presented as a morphological box.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="200"/>
              <col width="580"/>
              <col width="0"/>
              <col width="190"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Dimension (D<sub>n</sub>)</td>
                  <td colspan="2">Characteristics (C<sub>nm</sub>)</td>
                  <td>Exclusive or nonexclusive</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Findability</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>1</italic></sub>: data source</td>
                  <td><italic>C</italic><sub><italic>1.1</italic></sub>: patients’ health OR <italic>C</italic><sub><italic>1.2</italic></sub>: medical procedures OR <italic>C</italic><sub><italic>1.3</italic></sub>: medical products OR <italic>C</italic><sub><italic>1.4</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>2</italic></sub>: managerial. details</td>
                  <td><italic>C</italic><sub><italic>2.1</italic></sub>: holder OR <italic>C</italic><sub><italic>2.2</italic></sub>: origin OR <italic>C</italic><sub><italic>2.3</italic></sub>: collection OR <italic>C</italic><sub><italic>2.4</italic></sub>: qualification OR <italic>C</italic><sub><italic>2.5</italic></sub>: financials OR <italic>C</italic><sub><italic>2.6</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>3</italic></sub>: data type</td>
                  <td><italic>C</italic><sub><italic>3.1</italic></sub>: admin XOR <italic>C</italic><sub><italic>3.2</italic></sub>: primary care XOR <italic>C</italic><sub><italic>3.3</italic></sub>: secondary care XOR <italic>C</italic><sub><italic>3.4</italic></sub>: registries XOR <italic>C</italic><sub><italic>3.5</italic></sub>: others</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>4</italic></sub>: population information</td>
                  <td><italic>C</italic><sub><italic>4.1</italic></sub>: disease OR <italic>C</italic><sub><italic>4.2</italic></sub>: family linkages OR <italic>C</italic><sub><italic>4.3</italic></sub>: lifestyle factors OR <italic>C</italic><sub><italic>4.4</italic></sub>: population OR <italic>C</italic><sub><italic>4.5</italic></sub>: sociodemographic OR <italic>C</italic><sub><italic>4.6</italic></sub>: catchment area coverage</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>5</italic></sub>: data sensitivity</td>
                  <td><italic>C</italic><sub><italic>5.1</italic></sub>: synthetic data XOR <italic>C</italic><sub><italic>5.2</italic></sub>: anonymized data XOR <italic>C</italic><sub><italic>5.3</italic></sub>: pseudonymized data XOR <italic>C</italic><sub><italic>5.4</italic></sub>: personal data</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Accessibility</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>6</italic></sub>: catalogue accessibility</td>
                  <td><italic>C</italic><sub><italic>6.1</italic></sub>: public XOR <italic>C</italic><sub><italic>6.2</italic></sub>: hybrid XOR <italic>C</italic><sub><italic>6.3</italic></sub>: private</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>7</italic></sub>: dataset accessibility</td>
                  <td><italic>C</italic><sub><italic>7.1</italic></sub>: free XOR <italic>C</italic><sub><italic>7.2</italic></sub>: formal request XOR <italic>C</italic><sub><italic>7.3</italic></sub>: strictly limited XOR <italic>C</italic><sub><italic>7.4</italic></sub>: others</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>8</italic></sub>: access control</td>
                  <td><italic>C</italic><sub><italic>8.1</italic></sub>: catalog operator OR <italic>C</italic><sub><italic>8.2</italic></sub>: internal DAC<sup>a</sup> OR C<sub><italic>8.3</italic></sub>: external DAC OR C<sub><italic>8.4</italic></sub>: none OR <italic>C</italic><sub><italic>8.5</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Interoperability</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>9</italic></sub>: program discoverability</td>
                  <td><italic>C</italic><sub><italic>9.1</italic></sub>: Beacon OR <italic>C</italic><sub><italic>9.2</italic></sub>: BBMRI-MIABIS<sup>d</sup> OR <italic>C</italic><sub><italic>9.3</italic></sub>: bioimage OR <italic>C</italic><sub><italic>9.4</italic></sub>: CESSDA<sup>e</sup> OR <italic>C</italic><sub><italic>9.5</italic></sub>: DCAT<sup>f</sup> OR <italic>C</italic><sub><italic>9.6</italic></sub>: ECRIN-CRMDR<sup>g</sup> OR C<sub><italic>9.7</italic></sub>: FairShairing OR <italic>C</italic><sub><italic>9.8</italic></sub>: INSPIRE<sup>h</sup> OR <italic>C</italic><sub><italic>9.9</italic></sub>: PHIRI<sup>i</sup> OR <italic>C</italic><sub><italic>9.10</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>10</italic></sub>: semantic interoperability</td>
                  <td><italic>C</italic><sub><italic>10.1</italic></sub>: CDISC-SDTM<sup>j</sup> OR <italic>C</italic><sub><italic>10.2</italic></sub>: LOINC<sup>k</sup> OR <italic>C</italic><sub><italic>10.3</italic></sub>: OMOP<sup>l</sup> OR <italic>C</italic><sub><italic>10.4</italic></sub>: Oorphanet standards OR <italic>C</italic><sub><italic>10.5</italic></sub>: SNOMED<sup>m</sup> OR <italic>C</italic><sub><italic>10.6</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>11</italic></sub>: interoperable communication</td>
                  <td><italic>C</italic><sub><italic>11.1</italic></sub>: DICOM<sup>n</sup> OR <italic>C</italic><sub><italic>11.2</italic></sub>: HL7 FHIR<sup>o</sup> OR <italic>C</italic><sub><italic>11.3</italic></sub>: IDMP<sup>p</sup> OR <italic>C</italic><sub><italic>11.4</italic></sub>: ISO 800-110<sup>q</sup> OR <italic>C</italic><sub><italic>11.5</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>12</italic></sub>: CDM<sup>r</sup></td>
                  <td><italic>C</italic><sub><italic>12.1</italic></sub>: type OR <italic>C</italic><sub><italic>12.2</italic></sub>: reference OR <italic>C</italic><sub><italic>12.3</italic></sub>: release frequency</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>13</italic></sub>: ETL<sup>s</sup> status</td>
                  <td><italic>C</italic><sub><italic>13.1</italic></sub>: planned XOR <italic>C</italic><sub><italic>13.2</italic></sub>: in progress XOR <italic>C</italic><sub><italic>13.3</italic></sub>: completed</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>14</italic></sub>: vocabularies</td>
                  <td><italic>C</italic><sub><italic>14.1</italic></sub>: medicinal product OR <italic>C</italic><sub><italic>14.2</italic></sub>: cause of death OR <italic>C</italic><sub><italic>14.3</italic></sub>: quality of life measurement OR <italic>C</italic><sub><italic>14.4</italic></sub>: prescription OR <italic>C</italic><sub><italic>14.5</italic></sub>: dispensing OR <italic>C</italic><sub><italic>14.6</italic></sub>: indication OR <italic>C</italic><sub><italic>14.7</italic></sub>: procedures OR <italic>C</italic><sub><italic>14.8</italic></sub>: genetic data OR <italic>C</italic><sub><italic>14.9</italic></sub>: biomarker data OR <italic>C</italic><sub><italic>14.10</italic></sub>: medical event</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td colspan="5">
                    <bold>Reusability</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>15</italic></sub>: collection methodology</td>
                  <td><italic>C</italic><sub><italic>15.1</italic></sub>: collection governance OR <italic>C</italic><sub><italic>15.2</italic></sub>: collection process OR <italic>C</italic><sub><italic>15.3</italic></sub>: dataset updates OR <italic>C</italic><sub><italic>15.4</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>16</italic></sub>: collection events</td>
                  <td><italic>C</italic><sub><italic>16.1</italic></sub>: patient encounter OR <italic>C</italic><sub><italic>16.2</italic></sub>: physical examination OR <italic>C</italic><sub><italic>16.3</italic></sub>: diagnostics OR <italic>C</italic><sub><italic>16.4</italic></sub>: treatment OR <italic>C</italic><sub><italic>16.5</italic></sub>: progress note OR <italic>C</italic><sub><italic>16.6</italic></sub>: communication OR <italic>C</italic><sub><italic>16.7</italic></sub>: regulatory OR <italic>C</italic><sub><italic>16.8</italic></sub>: others</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>17</italic></sub>: data linkage</td>
                  <td><italic>C</italic><sub><italic>17.1</italic></sub>: strategy OR <italic>C</italic><sub><italic>17.2</italic></sub>: variable OR <italic>C</italic><sub><italic>17.3</italic></sub>: completeness OR <italic>C</italic><sub><italic>17.4</italic></sub>: cross-reference OR <italic>C</italic><sub><italic>17.5</italic></sub>: none</td>
                  <td colspan="2">Nonexclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>18</italic></sub>: data preservation</td>
                  <td><italic>C</italic><sub><italic>18.1</italic></sub>: definite records XOR <italic>C</italic><sub><italic>18.2</italic></sub>: indefinite records</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>19</italic></sub>: publish</td>
                  <td><italic>C</italic><sub><italic>19.1</italic></sub>: approval needed XOR <italic>C</italic><sub><italic>19.2</italic></sub>: no approval needed</td>
                  <td colspan="2">Exclusive</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td><italic>D</italic><sub><italic>20</italic></sub>: informed consent</td>
                  <td><italic>C</italic><sub><italic>20.1</italic></sub>: not required XOR <italic>C</italic><sub><italic>20.2</italic></sub>: general use XOR <italic>C</italic><sub><italic>20.3</italic></sub>: all studies XOR <italic>C</italic><sub><italic>20.4</italic></sub>: specific studies XOR <italic>C</italic><sub><italic>20.5</italic></sub>: waiver XOR <italic>C</italic><sub><italic>20.6</italic></sub>: others</td>
                  <td colspan="2">Exclusive</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>FAIR: Findability, Accessibility, Interoperability, and Reusability.</p>
              </fn>
              <fn id="table4fn2">
                <p><sup>b</sup>HMDC: health metadata catalog.</p>
              </fn>
              <fn id="table4fn3">
                <p><sup>c</sup>DAC: Data Access Committee.</p>
              </fn>
              <fn id="table4fn4">
                <p><sup>d</sup>BBMRI-MIABIS: Biobanking and Biomolecular Resources Research Infrastructure-Minimum Information About Biobank Data Sharing.</p>
              </fn>
              <fn id="table4fn5">
                <p><sup>e</sup>CESSDA: Consortium of European Social Science Data Archives.</p>
              </fn>
              <fn id="table4fn6">
                <p><sup>f</sup>DCAT: Data Catalog vocabulary.</p>
              </fn>
              <fn id="table4fn7">
                <p><sup>g</sup>ECRIN-CRMDR: European Clinical Research Infrastructure Network – Clinical Research Metadata Repository.</p>
              </fn>
              <fn id="table4fn8">
                <p><sup>h</sup>INSPIRE: Infrastructure for Spatial Information in Europe.</p>
              </fn>
              <fn id="table4fn9">
                <p><sup>i</sup>PHIRI: Population Health Research Infrastructure.</p>
              </fn>
              <fn id="table4fn10">
                <p><sup>j</sup>CDISC-SDTM: Clinical Data Interchange Standards Consortium - Study Data Tabulation Model.</p>
              </fn>
              <fn id="table4fn11">
                <p><sup>k</sup>LOINC: Logical Observation Identifiers Names and Codes.</p>
              </fn>
              <fn id="table4fn12">
                <p><sup>l</sup>OMOP: Observational Medical Outcomes Partnership.</p>
              </fn>
              <fn id="table4fn13">
                <p><sup>m</sup>SNOMED: Systematized Nomenclature of Medicine.</p>
              </fn>
              <fn id="table4fn14">
                <p><sup>n</sup>DICOM: Digital Imaging and Communications in Medicine.</p>
              </fn>
              <fn id="table4fn15">
                <p><sup>o</sup>HL7 FHIR: Health Level 7 Fast Healthcare Interoperability Resources.</p>
              </fn>
              <fn id="table4fn16">
                <p><sup>p</sup>IDMP: Identification for Medicinal Products.</p>
              </fn>
              <fn id="table4fn17">
                <p><sup>q</sup>ISO800-110: International Organization for Standardization 800-110.</p>
              </fn>
              <fn id="table4fn18">
                <p><sup>r</sup>CDM: common data model.</p>
              </fn>
              <fn id="table4fn19">
                <p><sup>s</sup>ETL: extract, transform, load.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Data Findability</title>
          <p>The meta-dimension prescribes that datasets orchestrated by an HMDC must be easily discoverable, requiring metadata assets to describe essential attributes of the decentral datasets [<xref ref-type="bibr" rid="ref40">40</xref>]. The dimension <italic>data source</italic> (<italic>D<sub>1</sub></italic>) refers to abstract categories for data classification in the catalog system. Following European Medicines Agency guidelines [<xref ref-type="bibr" rid="ref43">43</xref>], and implementations in practice [<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>], patients’ health (<italic>C<sub>1.1</sub></italic>) comprises datasets attributable to conditions. Examples are diseases, causes of death, prescriptions and dispensing of medicines, clinical measurements, genetic data, units of health care use, and all other similar patient-generated data, for example, wearables. Medical procedures (<italic>C<sub>1.2</sub></italic>) encompass data describing hospital admission discharges, intensive care admissions, administration of vaccines or other injectables, medical operations, biomarker data, and diagnostic codes [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]. The latter includes, among others, the International Classification of Disease Code, the Major Comorbidity Code, and the Major Diagnostic Code. Medical products (<italic>C<sub>1.3</sub></italic>) span categories like prescribed medicinal products for human use, contraception, indication for use, and medical device data. Others (<italic>C<sub>1.4</sub></italic>) may refer to further data, for example, health care providers delivering diagnosis and treatment services [<xref ref-type="bibr" rid="ref43">43</xref>]. The dimension <italic>managerial details</italic> (<italic>D<sub>2</sub></italic>) captures crucial organizational metadata to be disclosed by the HMDC as part of a dataset’s metadata asset [<xref ref-type="bibr" rid="ref24">24</xref>]. Above all, the data holder (<italic>C<sub>2.1</sub></italic>) must be publicized, including contact details (ie, data steward). This entity sustains the record collection in an underlying dataset [<xref ref-type="bibr" rid="ref60">60</xref>]. The origin (<italic>C<sub>2.2</sub></italic>) of the data refers to the countries or geographical regions of their acquisition [<xref ref-type="bibr" rid="ref60">60</xref>] and the language [<xref ref-type="bibr" rid="ref44">44</xref>]. The characteristic of collection (<italic>C<sub>2.3</sub></italic>) details the acquisition dates as well as all data assemblage information, except collection methodology and events. If the dataset has received a formal qualification (<italic>C<sub>2.4</sub></italic>), this should also be disclosed in the metadata asset [<xref ref-type="bibr" rid="ref43">43</xref>]. The same holds for sources of finance (<italic>C<sub>2.5</sub></italic>) having sponsored the dataset creation [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref61">61</xref>], for example, data holder, public, industry, research, or patient organizations [<xref ref-type="bibr" rid="ref44">44</xref>]. Naturally, other (<italic>C<sub>2.6</sub></italic>) metadata attributes specifying managerial details are conceivable. The dimension <italic>data type</italic> (<italic>D<sub>3</sub></italic>) describes broader content related categories applicable to the dataset. It mainly distinguishes datasets containing administrative (<italic>C<sub>3.1</sub></italic> [<xref ref-type="bibr" rid="ref62">62</xref>]), primary (<italic>C<sub>3.2</sub></italic>) and secondary care (<italic>C<sub>3.3</sub></italic> [<xref ref-type="bibr" rid="ref63">63</xref>]), registry (<italic>C<sub>3.4</sub></italic>), and other (<italic>C<sub>3.5</sub></italic>) data types. Furthermore, <italic>population information</italic> (<italic>D<sub>4</sub></italic>) as metadata attribute refers to the specifics of the records within a dataset [<xref ref-type="bibr" rid="ref17">17</xref>]. The taxonomy narrows the dimension down to collected disease information (<italic>C<sub>4.1</sub></italic>); particular population specifics (<italic>C<sub>4.2</sub></italic>; eg, age groups); family linkages (<italic>C<sub>4.3</sub></italic>; eg, household, parent-child, sibling, and not applicable) lifestyle factors (<italic>C<sub>4.4</sub></italic>; eg, tobacco use, physical exercises, and diet); sociodemographic data (<italic>C<sub>4.5</sub></italic>; eg, gender, ethnicity, education, and deprivation index); and (<italic>C<sub>4.6</sub></italic>) catchment area coverage [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]. <italic>Data sensitivity</italic> (<italic>D<sub>5</sub></italic>) addresses the identifiability of data subjects of whom records were collected. Records can be synthetic (<italic>C<sub>5.1</sub></italic>), anonymized (<italic>C<sub>5.2</sub></italic>), pseudonymized (<italic>C<sub>5.3</sub></italic>), or contain personal data (<italic>C<sub>5.4</sub></italic>) [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref41">41</xref>].</p>
        </sec>
        <sec>
          <title>Data Accessibility</title>
          <p>Once datasets are findable in the HMDC, their accessibility must be facilitated. By their design, HMDCs must ensure legal and ethical compliance of all data access and sharing processes in their health care ecosystems [<xref ref-type="bibr" rid="ref19">19</xref>]. This particularly involves that datasets can be retrieved by authorized users only, implying rigor access control functions [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Accordingly, the dimension <italic>catalogue accessibility</italic> (<italic>D<sub>6</sub></italic>) refers to access modalities for data consumers to use the HMDC. HMDCs can be public (<italic>C<sub>6.1</sub></italic>) allowing anyone to browse metadata assets and discover datasets. Alternatively, HMDCs can be private (<italic>C<sub>6.2</sub></italic>), limited to a certain number of users who have been formally authorized by a dedicated authority. In addition, hybrid (<italic>C<sub>6.3</sub></italic>) forms exist. <italic>Dataset accessibility</italic> (<italic>D<sub>7</sub></italic>) describes the access modalities for data consumers to published datasets [<xref ref-type="bibr" rid="ref30">30</xref>]. The access can be free (<italic>C<sub>7.1</sub></italic>), implying that data must at least be anonymized or synthetic to comply with legal and ethical guidelines [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]. Datasets can also require a formal request (<italic>C<sub>7.2</sub></italic>) with a Data Access Committee (DAC) or a data steward deciding upon access requests [<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref66">66</xref>]. HMDCs frequently require such requests of data consumers to be approved by their ethic committees before processing them within the ecosystem [<xref ref-type="bibr" rid="ref66">66</xref>]. Moreover, data access can be strictly limited (<italic>C<sub>7.3</sub></italic>) to a demarcated group of data consumers. Although, members of such limited groups also need to make formal requests for data access [<xref ref-type="bibr" rid="ref66">66</xref>]. This implies that other (<italic>C<sub>7.4</sub></italic>) data access modalities exist, especially combinations of <italic>C<sub>7.1</sub></italic> to <italic>C<sub>7.3</sub></italic>. <italic>Access control</italic> (<italic>D<sub>8</sub></italic>) refers to the mechanisms implemented by HMDCs that facilitate the aforementioned decision-making by empowered entities [<xref ref-type="bibr" rid="ref30">30</xref>]. The dimension specifies the entities who determine whether data consumers receive the requested datasets and are allowed to perform which kinds of processing activities [<xref ref-type="bibr" rid="ref67">67</xref>]. It distinguishes the catalog operator (<italic>C<sub>8.1</sub></italic>); internal DACs at the sides of the data holders (<italic>C<sub>8.2</sub></italic> [<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref66">66</xref>]); external DACs (<italic>C<sub>8.3</sub></italic>) that are run centrally by an independent third party [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref66">66</xref>]; the absence of access control (<italic>C<sub>8.4</sub></italic>; ie, free data [<italic>C<sub>7.1</sub></italic>]); and any other forms (<italic>C<sub>8.5</sub></italic>). Generally, access control in HMDC designs is crucial for maintaining data security, confidentiality, and compliance with legal and ethical constraints [<xref ref-type="bibr" rid="ref67">67</xref>].</p>
        </sec>
        <sec>
          <title>Data Interoperability</title>
          <p>A core objective of HMDCs is to enable data consumers accumulating datasets across organizations, effectively, to create meaningful connections and analyses [<xref ref-type="bibr" rid="ref7">7</xref>]. This makes data interoperability crucial [<xref ref-type="bibr" rid="ref91">91</xref>]. To that end, HMDCs leverage specific standards described in this meta-dimension. Thereof, <italic>programmatic discoverability</italic> (<italic>D<sub>9</sub></italic>) refers to the ability of data consumers to programmatically query, access, and retrieve metadata assets and search for their attributes. It is defined by the joint action Towards European Health Data Space (TEHDAS) [<xref ref-type="bibr" rid="ref16">16</xref>] as the ability to identify, access, and understand health data by automated means. Associated approaches commonly involve application programming interfaces or similar programmatic methods to access and filter metadata in the HMDC [<xref ref-type="bibr" rid="ref19">19</xref>]. Following the TEHDAS community [<xref ref-type="bibr" rid="ref16">16</xref>], the dimension is narrowed down to the most frequent standards used by HMDCs. These are:</p>
          <list list-type="bullet">
            <list-item>
              <p>Beacon (C<sub>9.1</sub>),</p>
            </list-item>
            <list-item>
              <p>Biobanking and biomolecular resources research infrastructure-minimum information about biobank data sharing (BBMRI-MIABIS; C<sub>9.2</sub>),</p>
            </list-item>
            <list-item>
              <p>Bio-image archive (C<sub>9.3</sub>),</p>
            </list-item>
            <list-item>
              <p>Consortium of European Social Science Data Archives (CESSDA; C9.4),</p>
            </list-item>
            <list-item>
              <p>Data catalog vocabulary (DCAT; C<sub>9.5</sub>),</p>
            </list-item>
            <list-item>
              <p>European Clinical Research Infrastructure Network – clinical research metadata repository (ECRIN-CRMDR; C<sub>9.6</sub>),</p>
            </list-item>
            <list-item>
              <p>FairSharing (C<sub>9.7</sub>),</p>
            </list-item>
            <list-item>
              <p>Infrastructure for Spatial Information in Europe (INSPIRE; C9.8),</p>
            </list-item>
            <list-item>
              <p>Population Health Research Infrastructure (PHIRI; C9.9), and</p>
            </list-item>
            <list-item>
              <p>Others (C<sub>9.10</sub>).</p>
            </list-item>
          </list>
          <p>HMDCs typically adhere to one of those standards to ensure programmatic discoverability of published data offerings (ie, the metadata assets). The dimension <italic>semantic interoperability</italic> (<italic>D<sub>10</sub></italic>) ensures that the precise format and meaning of datasets is preserved and understood, covering both semantic and syntactic aspects [<xref ref-type="bibr" rid="ref68">68</xref>]. Similar to D<sub>9</sub>, the characteristics of this dimension encompass standards commonly applied by HMDCs. These are</p>
          <list list-type="bullet">
            <list-item>
              <p>Clinical Data Interchange Standards Consortium - Study Data Tabulation Model (CDISC-SDTM; C10.),</p>
            </list-item>
            <list-item>
              <p>Logical Observation Identifiers Names and Codes (LOINC; C10.2),</p>
            </list-item>
            <list-item>
              <p>Observational Medical Outcomes Partnership (OMOP; C10.3),</p>
            </list-item>
            <list-item>
              <p>Orphanet (C10.4),</p>
            </list-item>
            <list-item>
              <p>Systematized Nomenclature of Medicine (SNOMED; C10.5 [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>] and</p>
            </list-item>
            <list-item>
              <p>Others (C10.6).</p>
            </list-item>
          </list>
          <p>Subsequently, the dimension <italic>interoperable communication</italic> (<italic>D<sub>11</sub></italic>) comprises approaches implemented by HMDCs to facilitate seamless and effective data sharing between data holders and consumers [<xref ref-type="bibr" rid="ref70">70</xref>]. Approaches typically used for interoperable communication are Digital Imaging and Communications in Medicine (DICOM; <italic>C<sub>11.1</sub></italic>), Health Level 7 Fast Healthcare Interoperability Resources (HL7 FHIR; <italic>C<sub>11.2</sub></italic>), Identification for Medicinal Products (IDMP; <italic>C<sub>11.3</sub></italic>), and International Organization for Standardization (ISO) 800-110 (<italic>C<sub>11.4</sub></italic>) [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]. As for the previous dimensions, other standards (<italic>C<sub>11.5</sub></italic>) are conceivable. For <italic>D<sub>9</sub></italic> to <italic>D<sub>11</sub></italic>, detailed information is easily available in the web.</p>
          <p>The following dimensions deal with “data harmonization<italic>”</italic> as a crucial aspect of data interoperability. They comprise HMDC design elements for standardizing disparate datasets. The purpose is to ensure consistency and coherence of all datasets classifiable to the same data type (<italic>D<sub>3</sub></italic>). Data harmonization aims to create a unified and cohesive view on datasets, enhancing their allocation, sharing, and use [<xref ref-type="bibr" rid="ref7">7</xref>]. The common data model (CDM; <italic>D<sub>12</sub></italic>) describes the specifications relating to the structured representation of data records within datasets [<xref ref-type="bibr" rid="ref5">5</xref>]. The CDM unfolds implications to the relationships between these records, as well as the rules and possibilities for data use. It defines how data consumers can access and process datasets, thus providing the foundation for data consistency, interoperability, and orchestration [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref72">72</xref>]. The taxonomy distinguishes the CDM type (<italic>C<sub>12.1</sub></italic>) [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref72">72</xref>], the CDM references (<italic>C<sub>12.2</sub></italic>), for example, websites or publications, and the release frequency of CDM specification updates (<italic>C<sub>12.3</sub></italic>) [<xref ref-type="bibr" rid="ref43">43</xref>]. Furthermore, information about datasets on their transformation status (extract, transform, load [ETL]) to a CDM should be provided [<xref ref-type="bibr" rid="ref44">44</xref>]. This <italic>ETL status</italic> (<italic>D<sub>13</sub></italic>) can be described as planned (<italic>C<sub>13.1</sub></italic>), in progress (<italic>C<sub>13.2</sub></italic>), or completed (<italic>C<sub>13.3</sub></italic>), indicating the readiness of the dataset for use. Finally, HMDCs leverage <italic>vocabularies</italic> (<italic>D<sub>14</sub></italic>) as sets of fixed terms, labels, or identifiers to describe and categorize the metadata assets [<xref ref-type="bibr" rid="ref63">63</xref>]. Vocabularies facilitate understanding, discovery, and allocation of metadata with a consistently applied language [<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref73">73</xref>]. The dimension distinguishes 10 characteristics for classifying vocabularies on the basis of pertinent literature: medicinal product (<italic>C<sub>14.1</sub></italic>), cause of death (<italic>C<sub>14.2</sub></italic>), quality of life measuring (<italic>C<sub>14.3</sub></italic>), prescription (<italic>C<sub>14.4</sub></italic>), dispensing (<italic>C<sub>14.5</sub></italic>), indication (<italic>C<sub>14.6</sub></italic>), procedures (<italic>C<sub>14.7</sub></italic>), genetic data (<italic>C<sub>14.8</sub></italic>), biomarker data (<italic>C<sub>14.9</sub></italic>), and medical event (<italic>C<sub>14.10</sub></italic>) [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref73">73</xref>].</p>
        </sec>
        <sec>
          <title>Data Reusability</title>
          <p>FAIR datasets must be created and documented in a way that allows reusage for different purposes. For HMDCs, this implies providing contextual information beyond the metadata dimensions associated with data findability [<xref ref-type="bibr" rid="ref40">40</xref>]. <italic>Collection methodology</italic> (<italic>D<sub>15</sub></italic>) encompasses characteristics that are associated with how data records were created [<xref ref-type="bibr" rid="ref74">74</xref>]. Thereof, collection governance (<italic>C<sub>15.1</sub></italic>) addresses information about data capture, demonstrating legal and ethical compliance [<xref ref-type="bibr" rid="ref43">43</xref>]. This includes data quality checks and validation activities [<xref ref-type="bibr" rid="ref75">75</xref>]. The latter may also refer to the question of whether the dataset allows access to the actual records. Furthermore, the collection process (<italic>C<sub>15.2</sub></italic>) outlines how records in the dataset were created [<xref ref-type="bibr" rid="ref74">74</xref>], for example, surveys, questionnaires, or data retrieval from hospital IS. Dataset updates (<italic>C<sub>15.3</sub></italic>) disclose refreshment dates of datasets, for instance, fixed dates around the year [<xref ref-type="bibr" rid="ref43">43</xref>]. Naturally, the collection methodology can contain other (<italic>C<sub>15.4</sub></italic>) use case–specific characteristics as additional metadata attributes. Similar to <italic>D<sub>15</sub></italic>, <italic>collection events</italic> (<italic>D<sub>16</sub></italic>) narrows down the categories of incidents having triggered the creation of a record in the dataset [<xref ref-type="bibr" rid="ref17">17</xref>]. The dimension comprises the characteristics of patient encounter (<italic>C<sub>16.1</sub></italic>; eg, interactions with health care providers); physical examination (<italic>C<sub>16.2</sub></italic>; eg, patient’s health examined by a professional); diagnostics (<italic>C<sub>16.3</sub></italic>; eg, results of medical condition checks); treatment (<italic>C<sub>16.4</sub></italic>; eg, documentation of conditions and treatment plans); progress notes (<italic>C<sub>16.5</sub></italic>; eg, changes in patients’ health status, responses to treatment, or modifications of care plans); communication (<italic>C<sub>16.6</sub></italic>; eg, information exchanged by health care providers); regulatory (<italic>C<sub>16.7</sub></italic>; eg, legally required documentation of patients’ care); and others (<italic>C<sub>16.8</sub></italic>) [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>].</p>
          <p>The dimension <italic>data linkage</italic> (<italic>D<sub>17</sub></italic>) describes whether and how a dataset was created by linking others [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref76">76</xref>]. The metadata should disclose the linkage strategy (<italic>C<sub>17.1</sub></italic>) which could be deterministic, probabilistic, or both. In addition, the used linkage variable (<italic>C<sub>17.2</sub></italic>) should be published, along with the completeness of data linkage (<italic>C<sub>17.3</sub></italic>). Ideally, the linked datasets should be cross-referred (<italic>C<sub>17.4</sub></italic>) and, if applicable, their availability in the HMDC highlighted. In case no data linkage was applied, no corresponding metadata attribute is provided (<italic>C<sub>17.5</sub></italic>). Furthermore, <italic>data preservation</italic> (<italic>D<sub>18</sub></italic>) indicates whether records in the dataset are preserved indefinitely (<italic>C<sub>18.1</sub></italic>) or, if not (<italic>C<sub>18.2</sub></italic>), the time for which they are specified [<xref ref-type="bibr" rid="ref77">77</xref>]. <italic>Publishing constraints</italic> (<italic>D<sub>19</sub></italic>) provides information to data consumers whether an approval of the data holder (<italic>C<sub>19.1</sub></italic>) is needed to publish results obtained from using the dataset or an approval is not needed (<italic>C<sub>19.2</sub></italic>) [<xref ref-type="bibr" rid="ref43">43</xref>]. In the former case, the kind of approval and the approval process should be described. Finally, metadata assets of HMDCs should reveal whether <italic>informed consent</italic> (<italic>D<sub>20</sub></italic>) was obtained or needs to be obtained for data processing [<xref ref-type="bibr" rid="ref78">78</xref>]. Generally, the characteristics not required (<italic>C<sub>20.1</sub></italic>), required for general use (<italic>C<sub>20.2</sub></italic>), required for all studies (<italic>C<sub>20.3</sub></italic>), required for specific studies (<italic>C<sub>20.4</sub></italic>), waiver (<italic>C<sub>20.5</sub></italic>), and other (<italic>C<sub>20.6</sub></italic>) are recommendable [<xref ref-type="bibr" rid="ref43">43</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Cocreated HMDC Use Cases</title>
        <sec>
          <title>Overview</title>
          <p>The usability, effectiveness, and accuracy of the taxonomy are amplified by 4 “illustrative scenarios” for HMDCs that demonstrate how the FAIR dimensions and characteristics are reflected in real-world use cases [<xref ref-type="bibr" rid="ref39">39</xref>]. These use cases facilitate the taxonomy’s tangibility and the ascertainment of its practical implications, while triangulating the results. As such, they add depth and context to the taxonomy [<xref ref-type="bibr" rid="ref39">39</xref>]. Originally, 6 abstract application scenarios were derived from recommendations of EMA [<xref ref-type="bibr" rid="ref43">43</xref>]. Building upon this, we continuously developed and refined those scenarios on the basis of the insights gained during the taxonomy design iterations in general and the focus groups in particular. In the latter, we relied on the experts’ reflections on what they expect from an HMDC and whether our dimensions and characteristics meet their expectations, contradict them, or miss out on certain aspects. In the section about the deductive design iterations, we have already described how the focus groups were conducted. We ensured that the experts possess extensive expertise relevant to HMDC designs, either from a development (ie, technology or legal) or a user perspective (ie, data consumer or provider; <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). Hence, the use cases followed a cocreation approach that was contextualized to the methodological process of the study [<xref ref-type="bibr" rid="ref39">39</xref>]. Moreover, by being refined within multiple design iterations, the cocreated use cases have been triangulated and their relevance for HMDCs ensured. Following, their connection to the taxonomy is highlighted by direct references to dimensions (see <italic>Taxonomy for FAIR HMDCs</italic>). Additionally, I to VII refer to statements of experts who are listed in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. Reference citations of the literature and analysis objects demonstrate further exemplary sources having contributed to the final versions of the cocreated use cases.</p>
        </sec>
        <sec>
          <title>Study Planning</title>
          <p>Use case 1 is as follows: <italic>a data consumer wants to identify suitable datasets for a planned study</italic>.</p>
          <p>The HMDC must enable data consumers to effectively identify datasets for medical research studies [<xref ref-type="bibr" rid="ref15">15</xref>] by implementing the following process: First, a data consumer who wants to access the HMDC, needs to be authorized as a qualified user (<italic>D<sub>6</sub></italic>; #I [<xref ref-type="bibr" rid="ref50">50</xref>]). Second, this authorized user must be able to browse and filter published metadata assets to discover relevant datasets that fulfill specifications of an intended study (#V and VII [<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]). For example, detailed data type [<xref ref-type="bibr" rid="ref63">63</xref>] or population information of the metadata assets should be disclosed to enable verifying the relevance of datasets (<italic>D<sub>3</sub></italic> and <italic>D<sub>4</sub></italic>; #I, II, V, and VII [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref58">58</xref>]). Third, the HMDC must allow to check managerial details concerning information about the data holder, origin, collection, qualification, and financials (<italic>D<sub>2</sub></italic> [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]), including the eligibility to receive synthetic, anonymized, pseudonymized, or personal data (<italic>D<sub>5</sub></italic>; #IV [<xref ref-type="bibr" rid="ref15">15</xref>]). Subsequently, the data consumer must be facilitated to perform a preliminary assessment of datasets regarding their relevance for the planned study (#III and VII). At this stage, a first list of candidates should be possible to be established. Ideally, the data consumer can access links (ie, cross-references) within the metadata assets to identify former studies which were performed with the same dataset, addressing similar research questions (<italic>C<sub>17.4</sub></italic>; #II and VII [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref76">76</xref>]). Such studies are typically accessed outside the contextual boundaries of HMDCs (#IV). Finally, depending on the governance modalities of selected datasets (<italic>D<sub>7</sub></italic>), the HMDC must enable the data consumer to request data access (#I-VII [<xref ref-type="bibr" rid="ref30">30</xref>]). Therefore, an official data order needs to be submitted by the HMDC on behalf of the data consumer, containing specifications about the planned study and required documents, for example, protocols and ethical assessments (#I-III). With respect to the datasets accessibility constraints (<italic>D<sub>7</sub></italic>) and their associated access control (<italic>D<sub>8</sub></italic>) characteristics, the HMDC must forward data orders to the data holders (<italic>C<sub>8.2</sub></italic> [<xref ref-type="bibr" rid="ref66">66</xref>]), external third parties (<italic>C<sub>8.3</sub></italic> [<xref ref-type="bibr" rid="ref23">23</xref>]) or determine request permission or denial decisions itself (<italic>C<sub>8.1</sub></italic> and <italic>C<sub>8.4</sub></italic>; #I, III, and VI).</p>
        </sec>
        <sec>
          <title>Study Assessment</title>
          <p>Use case 2 is as follows: <italic>a dataset is mentioned in a conducted study. The data consumer wants to evaluate this study based on the suitability of the datasets used therein.</italic></p>
          <p>Given that the datasets used in a conducted study are available in the HMDC, data consumers must be enabled to verify, in retrospective, the suitability of these datasets (#I, II, and VII). To support such evaluations, the HMDC must provide different parts of the metadata asset, depending on the nature of the conducted study (#II and VII). For example, to assess the representativeness of the study population, the data consumer needs to examine qualitative metadata attributes (#II and VII), such as population information (<italic>C<sub>4.1</sub></italic>-<italic>C<sub>4.5</sub></italic> [<xref ref-type="bibr" rid="ref17">17</xref>]); data type (<italic>D<sub>3</sub></italic> [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]); collection methodology (<italic>D<sub>15</sub></italic> [<xref ref-type="bibr" rid="ref74">74</xref>]); and collection events (<italic>D<sub>16</sub></italic> [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]). In addition, quantitative metadata such as the percentage of the population covered in the catchment area (<italic>C<sub>4.6</sub></italic>) should be disclosed by the HMDC assets [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Furthermore, the data consumer might want to explore technical details to evaluate a study and its database, respectively (#I, II, and VII). Examples are the vocabularies used to define variables (<italic>D<sub>14</sub></italic> [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]), the CDM according to which the used datasets are structured (<italic>D<sub>12</sub></italic> [<xref ref-type="bibr" rid="ref43">43</xref>]), the ETL status (<italic>D<sub>13</sub></italic> [<xref ref-type="bibr" rid="ref44">44</xref>]) and, if applied, any data linkage strategies (<italic>D<sub>17</sub></italic> [<xref ref-type="bibr" rid="ref76">76</xref>]). Moreover, cross-references should be listed in the metadata assets of the HMDC (<italic>C<sub>17.4</sub></italic>) to allow identifying and obtaining lessons learned from other studies, where the same dataset was leveraged (#VII [<xref ref-type="bibr" rid="ref76">76</xref>]). In doing so, the HMDC facilitates data consumers to identify strengths and limitations of datasets used in conducted studies.</p>
        </sec>
        <sec>
          <title>Study Creation and Data Benchmarking</title>
          <p>Use case 3 is as follows: <italic>a data consumer writes a study protocol that requires to describe the underlying data sets and compare their characteristics.</italic></p>
          <p>An HMDC must enable data consumers to easily access standardized metadata information about datasets that need to be specified and compared in a study protocol to be written (#I-VII). For HMDCs, this requires making attribute values of metadata assets directly and easily retrievable for data consumers to facilitate an efficient description and comparison of datasets (particularly, <italic>D<sub>1</sub></italic>-<italic>D<sub>5</sub></italic>; #VII). As such, when writing a study protocol, the data consumer can simply provide links to the metadata assets available in the HMDC, alongside with all kinds of other information that is interesting in the protocol’s context (#III and VII [<xref ref-type="bibr" rid="ref43">43</xref>]). Providing such links is also beneficial because study readers could, in addition to basic metadata information (<italic>D<sub>1</sub></italic>-<italic>D<sub>5</sub></italic>), be interested in collection methodologies (<italic>D<sub>15</sub></italic> [<xref ref-type="bibr" rid="ref74">74</xref>]) and events (<italic>D<sub>16</sub></italic> [<xref ref-type="bibr" rid="ref17">17</xref>]), data preservation (<italic>D<sub>18</sub></italic> [<xref ref-type="bibr" rid="ref77">77</xref>]), consent requirements (<italic>D<sub>20</sub></italic> [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref78">78</xref>]) as well as technical (<italic>D<sub>9</sub></italic>-<italic>D<sub>14</sub></italic>) and compliance specifics (<italic>D<sub>6</sub></italic>-<italic>D<sub>8</sub></italic>). Thus, HMDCs strengthen transparency and reproducibility of studies by facilitating an effective creation of study protocols (#III and V). At the same time, they support data benchmarking by providing detailed standardized metadata, potentially reaching beyond published datasets (#I-VII).</p>
        </sec>
        <sec>
          <title>Data Analysis</title>
          <p>Use case 4 is as follows: <italic>a data consumer wants to benefit from the experience of others for the creation of a study’s programming script or statistical analysis.</italic></p>
          <p>If a study relies on a CDM, the HMDC should enable the data consumer to identify, for published datasets, the ETL procedure (<italic>D<sub>13</sub></italic>) from the dataset to the CDM (<italic>D<sub>12</sub></italic>) [<xref ref-type="bibr" rid="ref43">43</xref>]. Irrespective of whether data holders have converted their entire datasets, or only an extraction thereof, this information can support the development of the study script (#VII [<xref ref-type="bibr" rid="ref43">43</xref>]). If the HMDC publishes cross-references of datasets (<italic>C<sub>17.4</sub></italic>), the data consumer is also facilitated in finding further studies having investigated the same topic or used a comparable research design (#I, II, and VII [<xref ref-type="bibr" rid="ref76">76</xref>]). These studies may disclose information on how to operationalize data variables, which offers the data consumer additional support in the development of a programming script (#I and VII). After data analysis, the HMDC may require the data consumer to record the developed script in a public repository and provide a link to the study protocol (see use case 3). This allows the HMDC to cross-reference it in the metadata assets of the datasets used (#V [<xref ref-type="bibr" rid="ref43">43</xref>]). In doing so, transparency, reproducibility, and quality of studies are supported. Importantly, before publishing any study results, the HMDC should enable the data consumer to check whether approvals of data holders, of whom datasets were obtained, are required (<italic>D<sub>19</sub></italic>; #IV and V [<xref ref-type="bibr" rid="ref43">43</xref>]).</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The taxonomy detailed in this work provides 20 dimensions and 101 characteristics to develop FAIR HMDCs, representing initial, yet actionable design knowledge to answer RQ1. Comprehensive description is achieved when amplifying the taxonomy in the light of the cocreated use cases that entail real-world requirements (RQ2). The generated design knowledge provides added value because HMDCs facilitate effective and efficient use of RWD for generating RWE. Thereby, the obtained results accentuate the integration of FAIR principles into HMDCs to ensure “findability, accessibility, interoperability, and reusability” of the RWD circulating within the underlying health care data ecosystem [<xref ref-type="bibr" rid="ref40">40</xref>]. The design knowledge can be classified into scientific and managerial contributions, as outlined in the following sections.</p>
      </sec>
      <sec>
        <title>Interpretation of Findings</title>
        <p>The taxonomy’s <italic>scientific contributions</italic> intensify previous work on data catalogs, paying particular attention to, first, their implementation as decentralized components within data ecosystems and, second, their application in health care peripheries. Consequently, some of the design elements conceptualized in this study draw from prior research about metadata catalogs, as shown in the section Research gap, objective, and questions. Concurrently, they further spin the red paths of HMDC developments with respect to European initiatives pushing health care data ecosystems forward, for example, IDERHA, Elixir, HealthData@EU, EUCAIM, TEHDAS, or EHDEN (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Therefore, the taxonomy closes the identified research gap.</p>
        <p>On the one hand, the conceptualized dimensions and characteristics of the taxonomy describe and classify attributes of “HMDC metadata assets.” First, they relate to attributes associated with data findability, such as data source, managerial details, the type of data records contained, data sensitivity, and population information. Second, they state crucial information pertaining to data reusability. This encompasses collection methodologies, data linkage, and preservation as well as consent and possible result publishing constraints. Third, the taxonomy emphasizes the need to specify data interoperability attributes in metadata assets. Among others, data standardization according to a CDM, the prescription of vocabularies, and the technological implementation of programmatic discoverability are important. On the other hand, the taxonomy contains design elements referring to more general data accessibility constraints pertaining to the “overall HMDC design.” They accentuate basic security and governance considerations regarding dataset and catalog accessibility as well as the access control framework. Conclusively, from a scientific viewpoint, the artifact provides fundamental design knowledge [<xref ref-type="bibr" rid="ref31">31</xref>] that unfolds broad implications and a solid starting point for future research.</p>
        <p>Regarding <italic>managerial contributions</italic>, the taxonomy enables health care practitioners (see Introduction section for target audience) to navigate more effectively in the largely unexplored field of HMDCs, particularly focusing on their application in health care data ecosystems across Europe. It helps both researchers and practitioners to anchor and communicate their work [<xref ref-type="bibr" rid="ref41">41</xref>]. The taxonomy also represents a support tool for developing HMDCs, where the illustrative scenarios assume an accentuated role. They showcase how the design elements are reflected in real-world use cases [<xref ref-type="bibr" rid="ref43">43</xref>]. In essence, these use cases amplify that the taxonomy supports common activities for planning, assessing, and conducting medical research studies as well as benchmarking and analyzing the underlying RWD.</p>
        <p>Subsequently, the contributions of the study are discussed in the light of 3 major issues. These are (1) the exclusiveness of taxonomy characteristics; (2) the difference between HMDCs and centralized data catalogs; and (3) the absence of data quality and data-sharing incentives as explicit taxonomy dimensions.</p>
        <p>Depending on the meta-dimension, the taxonomy contains nonexclusive characteristics, which might be accumulated, to facilitate the design of metadata assets, that is, data findability, interoperability, and reusability. Alternatively, the taxonomy has mutual exclusive characteristics to classify and distinguish HMDC designs with respect to their data security and governance approaches, that is, data accessibility. This mixture of exclusive and nonexclusive dimensions can foster the understanding of health care practitioners, while allowing for an easy alteration of the taxonomy [<xref ref-type="bibr" rid="ref37">37</xref>]. Convertibility is vital because HMDCs represent a rapidly evolving and changing field, where new solutions vanish and emerge constantly.</p>
        <p>Furthermore, even though the objective of the taxonomy is not to differentiate between centralized and decentralized data catalogs, as distinguished in the Theoretical Background section, it pinpoints their fundamental design commonalities and differences. The meta-dimensions concerning the design of the metadata assets are conceivable for both approaches in health care contexts (ie, findability, interoperability, and reusability). The reason is that, despite datasets being stored centrally within intraorganizational data catalogs [<xref ref-type="bibr" rid="ref26">26</xref>], meaningful metadata need to be disclosed to their data users by means of the catalog offerings. Naturally, the same holds for decentralized catalogs. However, the taxonomy also shows design differences with respect to its meta-dimension data accessibility. While decentralized catalogs can have various combinations of characteristics in the associated dimensions, centralized health data catalogs exhibit one specific pattern of characteristics. They usually are exclusively private systems (<italic>C<sub>6.1</sub></italic>) as their functionalities are only accessible to members of the operating organization. Similarly, dataset access is strictly limited to this specific group of predefined users (<italic>C<sub>7.3</sub></italic>). Finally, access control lies solely with the organization operating the centralized catalog (<italic>C<sub>8.1</sub></italic>).</p>
        <p>As a last discussion point, the taxonomy contains neither dimensions associated with data quality nor incentives for data sharing. The reason is that these concepts, although important, are broad, multifaceted, and hardly explored, making a systematic categorization difficult. Generally, data quality involves subjective and context-dependent assessments [<xref ref-type="bibr" rid="ref92">92</xref>], while incentives to share data are influenced by external, sociopolitical, and institutional factors [<xref ref-type="bibr" rid="ref28">28</xref>]. Typically, HMDCs do not disclose any data quality metrics as those can barely be quantified and are subject to applied data types, formats, and standards [<xref ref-type="bibr" rid="ref41">41</xref>]. Rather, HMDCs publish test samples consisting of synthetic or fully anonymized data that do not justify a dimension in the taxonomy. Similarly, incentivizing data sharing, for example, via price tags for datasets or mandatory citations, represents an unsolved problem [<xref ref-type="bibr" rid="ref93">93</xref>]. To circumnavigate this issue, HMDCs commonly rely on membership fees and public funding. The former restricts data access to members of the HMDC operating organization. The latter compensates data providers through public funds, usually applied in preliminary stages. Naturally, other business models exist. However, both data quality indicators and data-sharing incentives represent underdeveloped fields requiring future research beyond the study’s design perspective [<xref ref-type="bibr" rid="ref33">33</xref>]. Consequently, these concepts are not a part of the taxonomy, because they cannot be defined in universally applicable dimensions. Arguably, their inclusion would have overcomplicated the taxonomy and undermined its focus on actionable HMDC design knowledge.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The taxonomy is mainly subject to the following limitations. In the inductive iterations, results were derived from a potentially limited number of publications because of the emphasis on 4 main databases. Similarly, in the deductive iterations, the examined analysis objects might merely cover a snapshot of what was available at the time (ie, many analysis objects have been in progress), be outdated quickly, and not be conclusive. As for the SLR, the conclusiveness of analysis objects is particularly questionable because of, first, the focus on European ecosystem initiatives and, second, a possible negligence of many centralized health data catalogs. In the evaluative iterations, the experts might not have captured the full range of relevant perspectives on HMDCs and are limited in number. Furthermore, the research design comprises certain limitations per se. As it is with qualitative research, taxonomy building requires substantial generalizations and simplifications of intricate and interdisciplinary content [<xref ref-type="bibr" rid="ref83">83</xref>]. Although countermeasures were taken (see Methods section), these factors imply interpretative biases inevitably incorporated into the results [<xref ref-type="bibr" rid="ref41">41</xref>], for example, extracting design elements from public data. Moreover, as shown in the Theoretical Background section, new HMDCs must be expected to arise constantly, while others are likely to disappear with a high frequency. Hence, the taxonomy must be altered swiftly. To conclude, the taxonomy provides first actionable design knowledge about HMDCs but requires continuous triangulation of design elements by future research.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Despite the limitations, the scientific and managerial contributions of this study unfold broad implications, which are formulated as recommendations for future research. Generally, HMDCs should be increasingly investigated in practice, for example, by more in-depth case studies. On the one hand, it is of utmost importance to keep track of the rapidly evolving HMDC-related initiatives in Europe. Their conceptual and technical advancements should be analyzed and evaluated constantly against the background of the taxonomy design elements, deriving the need for modifying dimensions and characteristics. On the other hand, by incorporating worldwide efforts toward health care data ecosystems and HMDCs, the scope of the taxonomy can be expanded and design knowledge beyond European jurisdictions can be created. In this regard, it is important to mention that the generated design knowledge about European HMDCs already entails such global implications. The FAIR dimensions of the taxonomy state fundamental characteristics of health data FAIR, making it universally relevant. In other words, the taxonomy conveys generally conceivable options for using catalog functionalities and underlying metadata assets. In addition, it outlines how to design those health metadata assets meaningfully. Therefore, despite the European focus, the taxonomy addresses global challenges with regards to health data sharing and metadata catalog designs, underlining its broad implications. Nevertheless, further research is essential, because HMDCs represent the fulcrum for allocating, exchanging, and using RWD to effectively generate RWE in emerging health care data ecosystems.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Leading European initiatives toward health care data ecosystems.</p>
        <media xlink:href="formative_v9i1e63396_app1.docx" xlink:title="DOCX File , 30 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Intermediary results of the iterative research process and key references.</p>
        <media xlink:href="formative_v9i1e63396_app2.docx" xlink:title="DOCX File , 70 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>List of focus group members and distribution to sessions.</p>
        <media xlink:href="formative_v9i1e63396_app3.docx" xlink:title="DOCX File , 50 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CDM</term>
          <def>
            <p>common data model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">DAC</term>
          <def>
            <p>Data Access Committee</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">E2C</term>
          <def>
            <p>empirical-to-conceptual</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EHDEN</term>
          <def>
            <p>European Health Data and Evidence Network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EHDS</term>
          <def>
            <p>European Health Data Space</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">EHDS2</term>
          <def>
            <p>European Health Data Space 2</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">ETL</term>
          <def>
            <p>extract, transform, load</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">EU</term>
          <def>
            <p>European Union</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">EUCAIM</term>
          <def>
            <p>European Federation for Cancer Images</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">FAIR</term>
          <def>
            <p>findability, accessibility, interoperability, and reusability</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">HMDC</term>
          <def>
            <p>health metadata catalog</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">IDERHA</term>
          <def>
            <p>Integration of Heterogeneous Data and Evidence towards Regulatory and Health Technology Assessment Acceptance</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">IS</term>
          <def>
            <p>information systems</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">RQ</term>
          <def>
            <p>research question</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">RWD</term>
          <def>
            <p>real-world data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">RWE</term>
          <def>
            <p>real-world evidence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">SLR</term>
          <def>
            <p>structured literature review</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">TEHDAS</term>
          <def>
            <p>Towards European Health Data Space</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This research has emerged from the IDERHA (Integration of Heterogeneous Data and Evidence towards Regulatory and Health Technology Assessment Acceptance) project funded by the Innovative Health Initiative of the European Union (GAP-101112135) and the Digital Life Journey project funded by Fraunhofer-Gesellschaft (PN: 051-600000).</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Data sharing is not applicable to this paper as no datasets were generated or analyzed during this study.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>SS conceptualized the study, conducted the investigation, developed the methodology, managed the project, supervised its execution, drafted the original manuscript, and contributed to reviewing and editing the manuscript. MKM contributed to the conceptualization and investigation, validated the findings, and participated in the review and editing of the manuscript.</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="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>GG</given-names>
            </name>
            <name name-style="western">
              <surname>DesRoches</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>The digital transformation of healthcare: current status and the road ahead</article-title>
          <source>Inf Syst Res</source>
          <year>2010</year>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>796</fpage>
          <lpage>809</lpage>
          <pub-id pub-id-type="doi">10.1287/isre.1100.0327</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Schulthess</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Vannieuwenhuyse</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kalra</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Real world big data for clinical research and drug development</article-title>
          <source>Drug Discov Today</source>
          <year>2018</year>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>652</fpage>
          <lpage>60</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1359-6446(17)30595-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.drudis.2017.12.002</pub-id>
          <pub-id pub-id-type="medline">29294362</pub-id>
          <pub-id pub-id-type="pii">S1359-6446(17)30595-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Remy</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ivanović</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Theodoridou</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kritsotaki</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bailo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sbarra</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Jeffery</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Building an integrated enhanced virtual research environment metadata catalogue</article-title>
          <source>Electron Libr</source>
          <year>2019</year>
          <volume>37</volume>
          <issue>6</issue>
          <fpage>929</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1108/el-09-2018-0183</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Feldman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Chawla</surname>
              <given-names>NV</given-names>
            </name>
          </person-group>
          <article-title>The state of data in healthcare: path towards standardization</article-title>
          <source>J Healthc Inform Res</source>
          <year>2018</year>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>248</fpage>
          <lpage>71</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35415409"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s41666-018-0019-8</pub-id>
          <pub-id pub-id-type="medline">35415409</pub-id>
          <pub-id pub-id-type="pii">19</pub-id>
          <pub-id pub-id-type="pmcid">PMC8982788</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Swertz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Enckevort</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Fortier</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Bergeron</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thurin</surname>
              <given-names>NH</given-names>
            </name>
            <name name-style="western">
              <surname>Hyde</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kellmann</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pahoueshnja</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sturkenboom</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cunnington</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nybo Andersen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marcon</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gonçalves</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Gini</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Towards an interoperable ecosystem of research cohort and real-world data catalogues enabling multi-center studies</article-title>
          <source>Yearb Med Inform</source>
          <year>2022</year>
          <volume>31</volume>
          <issue>1</issue>
          <fpage>262</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0042-1742522"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0042-1742522</pub-id>
          <pub-id pub-id-type="medline">36463884</pub-id>
          <pub-id pub-id-type="pmcid">PMC9719789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bietz</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bloss</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Calvert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Godino</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Gregory</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Claffey</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Sheehan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Patrick</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Opportunities and challenges in the use of personal health data for health research</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <volume>23</volume>
          <issue>e1</issue>
          <fpage>42</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26335984"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv118</pub-id>
          <pub-id pub-id-type="medline">26335984</pub-id>
          <pub-id pub-id-type="pii">ocv118</pub-id>
          <pub-id pub-id-type="pmcid">PMC4954630</pub-id>
        </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>Kush</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Warzel</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kush</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Sherman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Navarro</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Fitzmartin</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pétavy</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Galvez</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Becnel</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Harmon</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jauregui</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hudson</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>FAIR data sharing: the roles of common data elements and harmonization</article-title>
          <source>J Biomed Inform</source>
          <year>2020</year>
          <volume>107</volume>
          <fpage>103421</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(20)30049-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2020.103421</pub-id>
          <pub-id pub-id-type="medline">32407878</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(20)30049-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wiertz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Boldt</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Ethical, legal, and practical concerns surrounding the implemention of new forms of consent for health data research: qualitative interview study</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e52180</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e52180/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/52180</pub-id>
          <pub-id pub-id-type="medline">39110970</pub-id>
          <pub-id pub-id-type="pii">v26i1e52180</pub-id>
          <pub-id pub-id-type="pmcid">PMC11339564</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Molnár-Gábor</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Beauvais</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bernier</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jimenez</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Recuero</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Knoppers</surname>
              <given-names>BM</given-names>
            </name>
          </person-group>
          <article-title>Bridging the European data sharing divide in genomic science</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <volume>24</volume>
          <issue>10</issue>
          <fpage>e37236</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/10/e37236/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/37236</pub-id>
          <pub-id pub-id-type="medline">36260387</pub-id>
          <pub-id pub-id-type="pii">v24i10e37236</pub-id>
          <pub-id pub-id-type="pmcid">PMC9631173</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lovestone</surname>
              <given-names>S</given-names>
            </name>
            <collab>EMIF Consortium</collab>
          </person-group>
          <article-title>The European medical information framework: a novel ecosystem for sharing healthcare data across Europe</article-title>
          <source>Learn Health Syst</source>
          <year>2020</year>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e10214</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32313838"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/lrh2.10214</pub-id>
          <pub-id pub-id-type="medline">32313838</pub-id>
          <pub-id pub-id-type="pii">LRH210214</pub-id>
          <pub-id pub-id-type="pmcid">PMC7156868</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Manogaran</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Varatharajan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Sundarasekar</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Thota</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A new architecture of internet of things and big data ecosystem for secured smart healthcare monitoring and alerting system</article-title>
          <source>Future Gener Comput Syst</source>
          <year>2018</year>
          <volume>82</volume>
          <fpage>375</fpage>
          <lpage>87</lpage>
          <pub-id pub-id-type="doi">10.1016/j.future.2017.10.045</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharon</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lucivero</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Introduction to the special theme: the expansion of the health data ecosystem – rethinking data ethics and governance</article-title>
          <source>Big Data Soc</source>
          <year>2019</year>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>205395171985296</fpage>
          <pub-id pub-id-type="doi">10.1177/2053951719852969</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Witte</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>A review on digital healthcare ecosystem structure: identifying elements and characteristics</article-title>
          <source>Proceedings of the 23rd Pacific Asia Conference on Information System</source>
          <year>2020</year>
          <conf-name>PACIS '20</conf-name>
          <conf-date>July 9-12, 2020</conf-date>
          <conf-loc>Dubai, UAE</conf-loc>
          <fpage>226</fpage>
          <lpage>38</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aisel.aisnet.org/pacis2020/228"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/j.1467-8373.2010.01427.x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scheider</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lauf</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Möller</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Otto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A reference system architecture with data sovereignty for human-centric data ecosystems</article-title>
          <source>Bus Inf Syst Eng</source>
          <year>2023</year>
          <volume>65</volume>
          <issue>5</issue>
          <fpage>577</fpage>
          <lpage>95</lpage>
          <pub-id pub-id-type="doi">10.1007/S12599-023-00816-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Trifan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bastião Silva</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>EMIF catalogue: a collaborative platform for sharing and reusing biomedical data</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <volume>126</volume>
          <fpage>35</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.02.006</pub-id>
          <pub-id pub-id-type="medline">31029262</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30830-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <article-title>EHDS semantic interoperability framework 2022</article-title>
          <source>TEHDAS</source>
          <access-date>2024-04-29</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="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bergeron</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Doiron</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Marcon</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ferretti</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Fortier</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Fostering population-based cohort data discovery: the Maelstrom Research cataloguing toolkit</article-title>
          <source>PLoS One</source>
          <year>2018</year>
          <volume>13</volume>
          <issue>7</issue>
          <fpage>e0200926</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0200926"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0200926</pub-id>
          <pub-id pub-id-type="medline">30040866</pub-id>
          <pub-id pub-id-type="pii">PONE-D-18-08049</pub-id>
          <pub-id pub-id-type="pmcid">PMC6057635</pub-id>
        </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>Ulrich</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kock-Schoppenhauer</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Deppenwiese</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gött</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kern</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lablans</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Majeed</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>Stöhr</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Stausberg</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Varghese</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dugas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ingenerf</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Understanding the nature of metadata: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>e25440</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/1/e25440/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25440</pub-id>
          <pub-id pub-id-type="medline">35014967</pub-id>
          <pub-id pub-id-type="pii">v24i1e25440</pub-id>
          <pub-id pub-id-type="pmcid">PMC8790684</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Almeida</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>A FAIR approach to real-world health data management and analysis</article-title>
          <source>Proceedings of the 36th International Symposium on Computer-Based Medical Systems</source>
          <year>2023</year>
          <conf-name>CBMS '23</conf-name>
          <conf-date>June 22-24, 2023</conf-date>
          <conf-loc>L'Aquila, Italy</conf-loc>
          <fpage>892</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/10178764"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/cbms58004.2023.00338</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Derycke</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kesisoglou</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Korsgaard</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Aage Huru</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Catsyne</surname>
              <given-names>CA</given-names>
            </name>
          </person-group>
          <article-title>Report on the landscape analysis of available metadata catalogues and the metadata standards in use</article-title>
          <source>HaDEA &amp; European Union</source>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ehds2pilot.eu/wp-content/uploads/2024/04/HealthData@EU-Pilot_MS6.1_FIN.pdf">https://ehds2pilot.eu/wp-content/uploads/2024/04/HealthData@EU-Pilot_MS6.1_FIN.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Bathelt</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gebler</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gött</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Heidenreich</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Henke</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kadioglu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lorenz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vengadeswaran</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sedlmayr</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Use of metadata-driven approaches for data harmonization in the medical domain: scoping review</article-title>
          <source>JMIR Med Inform</source>
          <year>2024</year>
          <volume>12</volume>
          <fpage>e52967</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2024//e52967/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/52967</pub-id>
          <pub-id pub-id-type="medline">38354027</pub-id>
          <pub-id pub-id-type="pii">v12i1e52967</pub-id>
          <pub-id pub-id-type="pmcid">PMC10902772</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lueschen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>van der Zee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Health Systems in the European Union: Diversity, Convergence, and Integration: A Sociological and Comparative Analysis in Belgium, France, Germany, ... and Spain</source>
          <year>2016</year>
          <publisher-loc>München, Germany</publisher-loc>
          <publisher-name>Walter de Gruyter</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lauf</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Scheider</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Friese</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kilz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Radic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Burmann</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Exploring design characteristics of data trustees in healthcare - taxonomy and archetypes</article-title>
          <source>Proceedings of the 31st European Conference on Information Systems</source>
          <year>2023</year>
          <conf-name>ECIS '23</conf-name>
          <conf-date>June 11-16, 2023</conf-date>
          <conf-loc>Kristiansand, Norway</conf-loc>
          <fpage>33</fpage>
          <lpage>57</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/370060215_Exploring_Design_Characteristics_of_Data_Trustees_in_Healthcare_-_Taxonomy_and_Archetypes"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Labadie</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Legner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Eurich</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fadler</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>FAIR enough? Enhancing the usage of enterprise data with data catalogs</article-title>
          <source>Proceedings of the 2020 IEEE 22nd Conference on Business Informatics</source>
          <year>2020</year>
          <conf-name>CBI '20</conf-name>
          <conf-date>June 22-24, 2020</conf-date>
          <conf-loc>Antwerp, Belgium</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9140254"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/cbi49978.2020.00029</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>Jahnke</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Otto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Data catalogs in the enterprise: applications and integration</article-title>
          <source>Datenbank Spektrum</source>
          <year>2023</year>
          <month>06</month>
          <day>21</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>89</fpage>
          <lpage>96</lpage>
          <pub-id pub-id-type="doi">10.1007/S13222-023-00445-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ehrlinger</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schrott</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Melichar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kirchmayr</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wöß</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Data catalogs: a systematic literature review and guidelines to implementation</article-title>
          <source>Proceedings of the 2021 International Conference on Database and Expert Systems Applications</source>
          <year>2021</year>
          <conf-name>DEXA '21</conf-name>
          <conf-date>September 27-30, 2021</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-030-87101-7_15"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-030-87101-7_15</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>Gröger</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>There is no AI without data</article-title>
          <source>Commun ACM</source>
          <year>2021</year>
          <month>10</month>
          <day>25</day>
          <volume>64</volume>
          <issue>11</issue>
          <fpage>98</fpage>
          <lpage>108</lpage>
          <pub-id pub-id-type="doi">10.1145/3448247</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barros Lima</surname>
              <given-names>GD</given-names>
            </name>
            <name name-style="western">
              <surname>Farias Lóscio</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Investigations into data ecosystems: a systematic mapping study</article-title>
          <source>Knowl Inf Syst</source>
          <year>2019</year>
          <volume>61</volume>
          <issue>2</issue>
          <fpage>589</fpage>
          <lpage>630</lpage>
          <pub-id pub-id-type="doi">10.1007/s10115-018-1323-6</pub-id>
        </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>Sohail</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Bukhsh</surname>
              <given-names>FA</given-names>
            </name>
            <name name-style="western">
              <surname>van Keulen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Multilevel privacy assurance evaluation of healthcare metadata</article-title>
          <source>Appl Sci</source>
          <year>2021</year>
          <volume>11</volume>
          <issue>22</issue>
          <fpage>10686</fpage>
          <pub-id pub-id-type="doi">10.3390/app112210686</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Almeida</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>MONTRA2: a web platform for profiling distributed databases in the health domain</article-title>
          <source>Inform Med Unlocked</source>
          <year>2024</year>
          <volume>45</volume>
          <fpage>101447</fpage>
          <pub-id pub-id-type="doi">10.1016/j.imu.2024.101447</pub-id>
        </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>vom Brocke</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Winter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hevner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Maedche</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Special issue editorial –accumulation and evolution of design knowledge in design science research: a journey through time and space</article-title>
          <source>J Assoc Inf Syst</source>
          <year>2020</year>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>520</fpage>
          <lpage>44</lpage>
          <pub-id pub-id-type="doi">10.17705/1jais.00611</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>van Aken</surname>
              <given-names>JE</given-names>
            </name>
          </person-group>
          <article-title>Valid knowledge for the professional design of large and complex design processes</article-title>
          <source>Des Stud</source>
          <year>2005</year>
          <volume>26</volume>
          <issue>4</issue>
          <fpage>379</fpage>
          <lpage>404</lpage>
          <pub-id pub-id-type="doi">10.1016/j.destud.2004.11.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hevner</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>March</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ram</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Design science in information systems research</article-title>
          <source>MIS Q</source>
          <year>2004</year>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>75</fpage>
          <lpage>105</lpage>
          <pub-id pub-id-type="doi">10.2307/25148625</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>March</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Storey</surname>
              <given-names>VC</given-names>
            </name>
          </person-group>
          <article-title>Design science in the information systems discipline: an introduction to the special issue on design science research</article-title>
          <source>MIS Q</source>
          <year>2008</year>
          <volume>32</volume>
          <issue>4</issue>
          <fpage>725</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.2307/25148869</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cash</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <article-title>Developing theory-driven design research</article-title>
          <source>Des Stud</source>
          <year>2018</year>
          <volume>56</volume>
          <fpage>84</fpage>
          <lpage>119</lpage>
          <pub-id pub-id-type="doi">10.1016/j.destud.2018.03.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kundisch</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Muntermann</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Oberländer</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Rau</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Röglinger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schoormann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Szopinski</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>An update for taxonomy designers</article-title>
          <source>Bus Inf Syst Eng</source>
          <year>2021</year>
          <volume>64</volume>
          <issue>4</issue>
          <fpage>421</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.1007/s12599-021-00723-x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nickerson</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Varshney</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Muntermann</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A method for taxonomy development and its application in information systems</article-title>
          <source>Eur J Inf Syst</source>
          <year>2017</year>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>336</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.1057/ejis.2012.26</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gregor</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The nature of theory in information systems</article-title>
          <source>MIS Q</source>
          <year>2006</year>
          <volume>30</volume>
          <issue>3</issue>
          <fpage>611</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.2307/25148742</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Szopinski</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Schoormann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kundisch</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Because your taxonomy is worth IT: towards a framework for taxonomy evaluation</article-title>
          <source>Proceedings of the 27th European Conference on Information Systems</source>
          <year>2019</year>
          <conf-name>ECIS '19</conf-name>
          <conf-date>June 8-14, 2019</conf-date>
          <conf-loc>Stockholm-Uppsala, Sweden</conf-loc>
          <fpage>25</fpage>
          <lpage>44</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/332711034_Because_your_taxonomy_is_worth_it_Towards_a_framework_for_taxonomy_evaluation"/>
          </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>Wilkinson</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Dumontier</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aalbersberg</surname>
              <given-names>IJ</given-names>
            </name>
            <name name-style="western">
              <surname>Appleton</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Axton</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baak</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Blomberg</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Boiten</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva Santos</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Bourne</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Brookes</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Crosas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dillo</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Dumon</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Edmunds</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Evelo</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Finkers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez-Beltran</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Groth</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Grethe</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Heringa</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>'t Hoen</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Hooft</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lusher</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Martone</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Packer</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Persson</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Rocca-Serra</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Roos</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Schaik</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sansone</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schultes</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sengstag</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Slater</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Strawn</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Swertz</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van der Lei</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>van Mulligen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Velterop</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Waagmeester</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wittenburg</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wolstencroft</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The FAIR guiding principles for scientific data management and stewardship</article-title>
          <source>Sci Data</source>
          <year>2016</year>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/sdata.2016.18"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/sdata.2016.18</pub-id>
          <pub-id pub-id-type="medline">26978244</pub-id>
          <pub-id pub-id-type="pii">sdata201618</pub-id>
          <pub-id pub-id-type="pmcid">PMC4792175</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scheider</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lauf</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Geller</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Möller</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Otto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Exploring design elements of personal data markets</article-title>
          <source>Electron Markets</source>
          <year>2023</year>
          <volume>33</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.1007/S12525-023-00646-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alvarellos</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sheppard</surname>
              <given-names>HE</given-names>
            </name>
            <name name-style="western">
              <surname>Knarston</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Davison</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Raine</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Seeger</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Prieto Barja</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chatzou Dunford</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Democratizing clinical-genomic data: how federated platforms can promote benefits sharing in genomics</article-title>
          <source>Front Genet</source>
          <year>2022</year>
          <month>1</month>
          <day>10</day>
          <volume>13</volume>
          <fpage>1045450</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36704354"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fgene.2022.1045450</pub-id>
          <pub-id pub-id-type="medline">36704354</pub-id>
          <pub-id pub-id-type="pii">1045450</pub-id>
          <pub-id pub-id-type="pmcid">PMC9871385</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <article-title>Good practice guide for the use of the metadata catalogue of real-world data sources</article-title>
          <source>European Medicines Agency</source>
          <year>2022</year>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/good-practice-guide-use-metadata-catalogue-real-world-data-sources_en.pdf">https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/good-practice-guide-use-metadata-catalogue-real-world-data-sources_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <article-title>List of metadata for real world data catalogues</article-title>
          <source>European Medicines Agency</source>
          <year>2022</year>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ema.europa.eu/en/documents/other/list-metadata-real-world-data-catalogues_en.pdf">https://www.ema.europa.eu/en/documents/other/list-metadata-real-world-data-catalogues_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <article-title>Data directory</article-title>
          <source>BBMRI-ERIC</source>
          <access-date>2024-11-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://directory.bbmri-eric.eu/ERIC/directory/#/catalogue">https://directory.bbmri-eric.eu/ERIC/directory/#/catalogue</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <article-title>An interactive catalogue of mental health and wellbeing measures in British cohort and longitudinal studies</article-title>
          <source>Catalogue of Mental Health Measures</source>
          <access-date>2024-10-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cataloguementalhealth.ac.uk/">https://www.cataloguementalhealth.ac.uk/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <article-title>Data catalogue for healthcare</article-title>
          <source>Compendium</source>
          <access-date>2024-10-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://compendiumdatacatalog.com/data-catalog/">https://compendiumdatacatalog.com/data-catalog/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
          <article-title>Findable, standardised data at scale through the EHDEN database catalogue</article-title>
          <source>EHDEN Portal</source>
          <access-date>2024-10-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ehden.eu/ehden-portal/">https://www.ehden.eu/ehden-portal/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <article-title>EMIF catalogue</article-title>
          <source>EMIF</source>
          <access-date>2024-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.emif.eu/emif-catalogue/">https://www.emif.eu/emif-catalogue/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="web">
          <article-title>Cancer image Europe</article-title>
          <source>EUCAIM Catalogue</source>
          <access-date>2024-10-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://catalogue.eucaim.cancerimage.eu/#/">https://catalogue.eucaim.cancerimage.eu/#/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <article-title>Welcome to the one-stop shop that facilitates access to population health and health care data, information and expertise across Europe</article-title>
          <source>European Health Information Portal</source>
          <access-date>2024-10-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthinformationportal.eu/">https://www.healthinformationportal.eu/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
          <article-title>Data catalogues for health</article-title>
          <source>Fjelltopp</source>
          <access-date>2024-10-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fjelltopp.org/service/data-catalogues-for-health/">https://www.fjelltopp.org/service/data-catalogues-for-health/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>Data catalogues</article-title>
          <source>Health RI</source>
          <access-date>2024-10-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://catalogus.healthdata.nl/datasets">https://catalogus.healthdata.nl/datasets</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <article-title>Explore data sources</article-title>
          <source>Helsedata</source>
          <access-date>2024-10-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://helsedata.no/en/">https://helsedata.no/en/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="web">
          <article-title>Health data catalog</article-title>
          <source>IQVIA</source>
          <access-date>2024-09-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iqvia.com/library/fact-sheets/iqvia-health-data-catalog">https://www.iqvia.com/library/fact-sheets/iqvia-health-data-catalog</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="web">
          <article-title>Health pilot</article-title>
          <source>Kraken</source>
          <access-date>2024-11-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.krakenh2020.eu/pilots/health">https://www.krakenh2020.eu/pilots/health</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
          <article-title>Precision medicine data catalog</article-title>
          <source>Lifebit</source>
          <access-date>2024-11-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.lifebit.ai/federated-data-catalogue">https://www.lifebit.ai/federated-data-catalogue</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <article-title>Maelstrom catalogue</article-title>
          <source>Maelstrom Research</source>
          <access-date>2024-11-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.maelstrom-research.org/page/catalogue">https://www.maelstrom-research.org/page/catalogue</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <article-title>Trials data catalogue</article-title>
          <source>Yoda</source>
          <access-date>2024-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://yoda.yale.edu/trials-search/">https://yoda.yale.edu/trials-search/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ge</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>DIR — a semantic information resource for healthcare datasets</article-title>
          <source>Proceedings of the 2017 IEEE International Conference on Bioinformatics and Biomedicine</source>
          <year>2017</year>
          <conf-name>BIBM '17</conf-name>
          <conf-date>November 13-16, 2017</conf-date>
          <conf-loc>Kansas City, MO</conf-loc>
          <fpage>805</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/abstract/document/8217758"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/bibm.2017.8217758</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McCoy</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chand</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sridhar</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Global health funding: how much, where it comes from and where it goes</article-title>
          <source>Health Policy Plan</source>
          <year>2009</year>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>407</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.1093/heapol/czp026</pub-id>
          <pub-id pub-id-type="medline">19570773</pub-id>
          <pub-id pub-id-type="pii">czp026</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yurkovich</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Avina-Zubieta</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gorenchtein</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lacaille</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A systematic review identifies valid comorbidity indices derived from administrative health data</article-title>
          <source>J Clin Epidemiol</source>
          <year>2015</year>
          <volume>68</volume>
          <issue>1</issue>
          <fpage>3</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jclinepi.2014.09.010</pub-id>
          <pub-id pub-id-type="medline">25441702</pub-id>
          <pub-id pub-id-type="pii">S0895-4356(14)00357-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Almeida</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Lopes</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Querying semantic catalogues of biomedical databases</article-title>
          <source>J Biomed Inform</source>
          <year>2023</year>
          <volume>137</volume>
          <fpage>104272</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(22)00277-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2022.104272</pub-id>
          <pub-id pub-id-type="medline">36563828</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(22)00277-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brunswick</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Data privacy, data protection, and the importance of integration for GDPR compliance</article-title>
          <source>Isaca J</source>
          <year>2019</year>
          <volume>1</volume>
          <fpage>14</fpage>
          <lpage>27</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jia</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Ren</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>DAC-MACS: effective data access control for multiauthority cloud storage systems</article-title>
          <source>Proceedings of the 2013 IEEE Conference on Computer Communications Workshops</source>
          <year>2013</year>
          <conf-name>INFOCOM '13</conf-name>
          <conf-date>April 14-19, 2013</conf-date>
          <conf-loc>Turin, Italy</conf-loc>
          <fpage>2895</fpage>
          <lpage>903</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/6567100"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/tifs.2013.2279531</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shabani</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Borry</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>"You want the right amount of oversight": interviews with data access committee members and experts on genomic data access</article-title>
          <source>Genet Med</source>
          <year>2016</year>
          <volume>18</volume>
          <issue>9</issue>
          <fpage>892</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1098-3600(21)04437-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/gim.2015.189</pub-id>
          <pub-id pub-id-type="medline">26795589</pub-id>
          <pub-id pub-id-type="pii">S1098-3600(21)04437-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Munoz-Arcentales</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>López-Pernas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pozo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alonso</surname>
              <given-names>Á</given-names>
            </name>
            <name name-style="western">
              <surname>Salvachúa</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Huecas</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>An architecture for providing data usage and access control in data sharing ecosystems</article-title>
          <source>Procedia Comput Sci</source>
          <year>2019</year>
          <volume>160</volume>
          <fpage>590</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2019.11.042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ngouongo</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Löbe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stausberg</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The ISO/IEC 11179 norm for metadata registries: does it cover healthcare standards in empirical research?</article-title>
          <source>J Biomed Inform</source>
          <year>2013</year>
          <volume>46</volume>
          <issue>2</issue>
          <fpage>318</fpage>
          <lpage>27</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(12)00182-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2012.11.008</pub-id>
          <pub-id pub-id-type="medline">23246614</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(12)00182-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>de Mello</surname>
              <given-names>BH</given-names>
            </name>
            <name name-style="western">
              <surname>Rigo</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>da Costa</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>da Rosa Righi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Donida</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Bez</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Schunke</surname>
              <given-names>LC</given-names>
            </name>
          </person-group>
          <article-title>Semantic interoperability in health records standards: a systematic literature review</article-title>
          <source>Health Technol (Berl)</source>
          <year>2022</year>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>255</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35103230"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12553-022-00639-w</pub-id>
          <pub-id pub-id-type="medline">35103230</pub-id>
          <pub-id pub-id-type="pii">639</pub-id>
          <pub-id pub-id-type="pmcid">PMC8791650</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iroju</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Soriyan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gambo</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Olaleke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Interoperability in healthcare: benefits, challenges and resolutions</article-title>
          <source>Int J Innov Appl Stud</source>
          <year>2013</year>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>262</fpage>
          <lpage>70</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Roehrs</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>da Costa</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>da Rosa Righi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rigo</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wichman</surname>
              <given-names>MH</given-names>
            </name>
          </person-group>
          <article-title>Toward a model for personal health record interoperability</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2019</year>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>867</fpage>
          <lpage>73</lpage>
          <pub-id pub-id-type="doi">10.1109/jbhi.2018.2836138</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kent</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Burn</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Dawoud</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jonsson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Østby</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rijnbeek</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bouvy</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Common problems, common data model solutions: evidence generation for health technology assessment</article-title>
          <source>Pharmacoeconomics</source>
          <year>2021</year>
          <volume>39</volume>
          <issue>3</issue>
          <fpage>275</fpage>
          <lpage>85</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33336320"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40273-020-00981-9</pub-id>
          <pub-id pub-id-type="medline">33336320</pub-id>
          <pub-id pub-id-type="pii">10.1007/s40273-020-00981-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC7746423</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ivanović</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Budimac</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>An overview of ontologies and data resources in medical domains</article-title>
          <source>Expert Syst Appl</source>
          <year>2014</year>
          <volume>41</volume>
          <issue>11</issue>
          <fpage>5158</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1016/j.eswa.2014.02.045</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hentschel</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Contextuality and data collection methods: a framework and application to health service utilisation</article-title>
          <source>J Dev Stud</source>
          <year>1999</year>
          <volume>35</volume>
          <issue>4</issue>
          <fpage>64</fpage>
          <lpage>94</lpage>
          <pub-id pub-id-type="doi">10.1080/00220389908422581</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tijhuis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Finger</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Slobbe</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sund</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Tolonen</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Marieke</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>van Oers</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Data collection</article-title>
          <source>Population Health Monitoring: Climbing the Information Pyramid</source>
          <year>2019</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>59</fpage>
          <lpage>81</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bohensky</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Jolley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sundararajan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pilcher</surname>
              <given-names>DV</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Brand</surname>
              <given-names>CA</given-names>
            </name>
          </person-group>
          <article-title>Data linkage: a powerful research tool with potential problems</article-title>
          <source>BMC Health Serv Res</source>
          <year>2010</year>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>346</fpage>
          <lpage>54</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/1472-6963-10-346"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6963-10-346</pub-id>
          <pub-id pub-id-type="medline">21176171</pub-id>
          <pub-id pub-id-type="pii">1472-6963-10-346</pub-id>
          <pub-id pub-id-type="pmcid">PMC3271236</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rasmussen</surname>
              <given-names>KB</given-names>
            </name>
            <name name-style="western">
              <surname>Blank</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>The data documentation initiative: a preservation standard for research</article-title>
          <source>Arch Sci</source>
          <year>2007</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>55</fpage>
          <lpage>71</lpage>
          <pub-id pub-id-type="doi">10.1007/S10502-006-9036-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Angrist</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Eyes wide open: the personal genome project, citizen science and veracity in informed consent</article-title>
          <source>Per Med</source>
          <year>2009</year>
          <volume>6</volume>
          <issue>6</issue>
          <fpage>691</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/22328898"/>
          </comment>
          <pub-id pub-id-type="doi">10.2217/pme.09.48</pub-id>
          <pub-id pub-id-type="medline">22328898</pub-id>
          <pub-id pub-id-type="pmcid">PMC3275804</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kitchenham</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Pearl Brereton</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Budgen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bailey</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Linkman</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Systematic literature reviews in software engineering – a systematic literature review</article-title>
          <source>Inf Softw Technol</source>
          <year>2009</year>
          <volume>51</volume>
          <issue>1</issue>
          <fpage>7</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1016/j.infsof.2008.09.009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Webster</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Watson</surname>
              <given-names>RT</given-names>
            </name>
          </person-group>
          <article-title>Analyzing the past to prepare for the future: writing a literature review</article-title>
          <source>MIS Q</source>
          <year>2002</year>
          <volume>26</volume>
          <issue>2</issue>
          <fpage>13</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/4132319"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mwita</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Factors influencing data saturation in qualitative studies</article-title>
          <source>Int J Bus Soc</source>
          <year>2022</year>
          <month>06</month>
          <day>05</day>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>414</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.20525/ijrbs.v11i4.1776</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="web">
          <article-title>Proposal for a regulation - the European Health Data Space</article-title>
          <source>Directorate-General for Health and Food Safety</source>
          <year>2022</year>
          <access-date>2024-11-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health.ec.europa.eu/publications/proposal-regulation-european-health-data-space_en#details">https://health.ec.europa.eu/publications/proposal-regulation-european-health-data-space_en#details</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saldana</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>The Coding Manual for Qualitative Researchers</source>
          <year>2021</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pratt</surname>
              <given-names>MG</given-names>
            </name>
          </person-group>
          <article-title>Fitting oval pegs into round holes</article-title>
          <source>Organ Res Methods</source>
          <year>2007</year>
          <volume>11</volume>
          <issue>3</issue>
          <fpage>481</fpage>
          <lpage>509</lpage>
          <pub-id pub-id-type="doi">10.1177/1094428107303349</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fruhwirth</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rachinger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Prlja</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Discovering business models of data marketplaces</article-title>
          <source>Proceedings of the 53rd Hawaii International Conference on System Sciences</source>
          <year>2020</year>
          <conf-name>HICSS '20</conf-name>
          <conf-date>January 7-10, 2020</conf-date>
          <conf-loc>Maui, HI</conf-loc>
          <fpage>5738</fpage>
          <lpage>47</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://scholarspace.manoa.hawaii.edu/server/api/core/bitstreams/cf7bab54-478b-412a-8742-6b02f10dd7ca/content"/>
          </comment>
          <pub-id pub-id-type="doi">10.24251/hicss.2020.704</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="web">
          <article-title>Database (part of Elixir infrastructure)</article-title>
          <source>Elixir BioSamples</source>
          <access-date>2024-12-03</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ebi.ac.uk/biosamples/">https://www.ebi.ac.uk/biosamples/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="web">
          <article-title>A registry of knowledgebases and repositories of data</article-title>
          <source>Elixir FAIRsharing</source>
          <access-date>2024-12-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://fairsharing.org/search?fairsharingRegistry=Database">https://fairsharing.org/search?fairsharingRegistry=Database</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="web">
          <article-title>Global health data exchange</article-title>
          <source>Institute for Health Metrics and Evaluation</source>
          <access-date>2024-10-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ghdx.healthdata.org/">https://ghdx.healthdata.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="web">
          <article-title>MACH clinical and research dataset catalogue</article-title>
          <source>Melbourne Academic Centre for Health</source>
          <access-date>2024-11-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://figshare.unimelb.edu.au/MACH-catalogue?searchMode=1">https://figshare.unimelb.edu.au/MACH-catalogue?searchMode=1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Möller</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Stachon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Azkan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Schoormann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Otto</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Designing business model taxonomies – synthesis and guidance from information systems research</article-title>
          <source>Electron Mark</source>
          <year>2021</year>
          <volume>32</volume>
          <issue>2</issue>
          <fpage>701</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.1007/s12525-021-00507-x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pine</surname>
              <given-names>KH</given-names>
            </name>
          </person-group>
          <article-title>The qualculative dimension of healthcare data interoperability</article-title>
          <source>Health Informatics J</source>
          <year>2019</year>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>536</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/1460458219833095?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1460458219833095</pub-id>
          <pub-id pub-id-type="medline">31002277</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>RY</given-names>
            </name>
            <name name-style="western">
              <surname>Strong</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>Beyond accuracy: what data quality means to data consumers</article-title>
          <source>J Manag Inf Syst</source>
          <year>2015</year>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>5</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1080/07421222.1996.11518099</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Spiekermann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Acquisti</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Böhme</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hui</surname>
              <given-names>KL</given-names>
            </name>
          </person-group>
          <article-title>The challenges of personal data markets and privacy</article-title>
          <source>Electron Markets</source>
          <year>2015</year>
          <volume>25</volume>
          <issue>2</issue>
          <fpage>161</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1007/S12525-015-0191-0</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
