<?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 xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v26i1e45209</article-id>
      <article-id pub-id-type="pmid">38289660</article-id>
      <article-id pub-id-type="doi">10.2196/45209</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Electronic Health Record and Semantic Issues Using Fast Healthcare Interoperability Resources: Systematic Mapping Review</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>Kiourtis</surname>
            <given-names>Athanasios</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Knaup-Gregori</surname>
            <given-names>Petra</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Thun</surname>
            <given-names>Sylvia</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hansen</surname>
            <given-names>David</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Amar</surname>
            <given-names>Fouzia</given-names>
          </name>
          <degrees>MEng</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>École de technologie supérieure - ETS</institution>
            <addr-line>1100 Notre Dame Ouest</addr-line>
            <addr-line>Montreal, QC, H3C 1K3</addr-line>
            <country>Canada</country>
            <phone>1 514 396 8800</phone>
            <email>famar2022@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1888-2019</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>April</surname>
            <given-names>Alain</given-names>
          </name>
          <degrees>BSc, MSc, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8675-4329</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Abran</surname>
            <given-names>Alain</given-names>
          </name>
          <degrees>BSc, BA, MASc, MSc MGT, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2670-9061</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>École de technologie supérieure - ETS</institution>
        <addr-line>Montreal, QC</addr-line>
        <country>Canada</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Fouzia Amar <email>famar2022@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>30</day>
        <month>1</month>
        <year>2024</year>
      </pub-date>
      <volume>26</volume>
      <elocation-id>e45209</elocation-id>
      <history>
        <date date-type="received">
          <day>21</day>
          <month>12</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>16</day>
          <month>2</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>7</day>
          <month>3</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>19</day>
          <month>12</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Fouzia Amar, Alain April, Alain Abran. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 30.01.2024.</copyright-statement>
      <copyright-year>2024</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2024/1/e45209" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The increasing use of electronic health records and the Internet of Things has led to interoperability issues at different levels (structural and semantic). Standards are important not only for successfully exchanging data but also for appropriately interpreting them (semantic interoperability). Thus, to facilitate the semantic interoperability of data exchanged in health care, considerable resources have been deployed to improve the quality of shared clinical data by structuring and mapping them to the Fast Healthcare Interoperability Resources (FHIR) standard.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The aims of this study are 2-fold: to inventory the studies on FHIR semantic interoperability resources and terminologies and to identify and classify the approaches and contributions proposed in these studies.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A systematic mapping review (SMR) was conducted using 10 electronic databases as sources of information for inventory and review studies published during 2012 to 2022 on the development and improvement of semantic interoperability using the FHIR standard.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 70 FHIR studies were selected and analyzed to identify FHIR resource types and terminologies from a semantic perspective. The proposed semantic approaches were classified into 6 categories, namely mapping (31/126, 24.6%), terminology services (18/126, 14.3%), resource description framework or web ontology language–based proposals (24/126, 19%), annotation proposals (18/126, 14.3%), machine learning (ML) and natural language processing (NLP) proposals (20/126, 15.9%), and ontology-based proposals (15/126, 11.9%). From 2012 to 2022, there has been continued research in 6 categories of approaches as well as in new and emerging annotations and ML and NLP proposals. This SMR also classifies the contributions of the selected studies into 5 categories: framework or architecture proposals, model proposals, technique proposals, comparison services, and tool proposals. The most frequent type of contribution is the proposal of a framework or architecture to enable semantic interoperability.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This SMR provides a classification of the different solutions proposed to address semantic interoperability using FHIR at different levels: collecting, extracting and annotating data, modeling electronic health record data from legacy systems, and applying transformation and mapping to FHIR models and terminologies. The use of ML and NLP for unstructured data is promising and has been applied to specific use case scenarios. In addition, terminology services are needed to accelerate their use and adoption; furthermore, techniques and tools to automate annotation and ontology comparison should help reduce human interaction.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>electronic health record</kwd>
        <kwd>EHR</kwd>
        <kwd>Health Level Seven International Fast Healthcare Interoperability Resources</kwd>
        <kwd>HL7 FHIR</kwd>
        <kwd>interoperability, web ontology language</kwd>
        <kwd>OWL</kwd>
        <kwd>ontology</kwd>
        <kwd>semantic</kwd>
        <kwd>terminology</kwd>
        <kwd>resource description framework</kwd>
        <kwd>RDF</kwd>
        <kwd>machine learning</kwd>
        <kwd>ML</kwd>
        <kwd>natural language processing</kwd>
        <kwd>NLP</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>The development and deployment of electronic health records (EHRs) worldwide has led to several interoperability challenges, including extracting valuable information from free-text clinical notes, integrating unstructured EHR patient data, and reusing them without ambiguity for clinical research purposes [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>].</p>
        <p>Interoperability is defined by the Institute of Electrical and Electronics Engineers (IEEE) as the “ability of two or more components to exchange information and to use the information that has been exchanged” [<xref ref-type="bibr" rid="ref3">3</xref>]. A total of 4 interoperability levels were proposed by the Healthcare Information and Management Systems Society organization: (1) foundational, (2) structural, (3) semantic, and (4) organizational (<xref rid="figure1" ref-type="fig">Figure 1</xref>) [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Interoperability levels (Healthcare Information and Management Systems Society).</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Important research efforts are underway to develop health care standards, including Fast Healthcare Interoperability Resources (FHIR) standards for the electronic exchange of health care information. This standard was developed by the Health Level Seven International (HL7) organization aiming at the evolution of messaging standards to achieve semantic interoperability [<xref ref-type="bibr" rid="ref5">5</xref>]. FHIR combines the best features of HL7 version 2, version 3, and clinical document architecture, while leveraging the latest web standards.</p>
        <p>FHIR interoperability solutions are designed from a set of modular components called “resources” that have been designed as small reusable components defining a set of properties for the capture of the structure of the domain data acquisition for a particular use. The version 4.3.0 release of FHIR R4B proposes 143 different “resources” classified into five categories to handle health data: (1) foundation resources, (2) base resources, (3) clinical resources, (4) financial resources, and (5) specialized resources (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <p>Many elements in FHIR use coded values and allow the use of external terminologies, such as (1) Systematized Nomenclature of Medicine–clinical terms (SNOMED CT)—comprehensive multilingual clinical terminology used in EHR. Its components include concepts (codes), descriptions (terms), and relationships—and (2) Logical Observation Identifiers Names and Codes (LOINC), a set of universal names and ID codes used to identify laboratory and clinical test results.</p>
        <p>Common terminology aims to address the problem of ambiguity in exchanged data [<xref ref-type="bibr" rid="ref6">6</xref>]. However, most legacy systems do not take advantage of a terminology-based approach to data exchange and still use incompatible terminologies or unstructured data in their exchanges with EHR. Thus, to ensure semantic interoperability with these legacy applications, it is mandatory to perform manual data transformations, mapping, or other alternate solutions to ensure that the exchanged data are interpreted correctly by the information systems involved.</p>
        <p>The FHIR standard is of great interest to researchers and EHR ecosystem developers [<xref ref-type="bibr" rid="ref7">7</xref>], and several technology giants, such as Amazon, Google, IBM, Microsoft, Oracle, and Salesforce, offer ready-to-use cloud services to promote the adoption of FHIR [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
        <p>In this study, we report on a systematic mapping Review (SMR) and propose a classification of the FHIR literature based on FHIR resources, terminologies, research approaches, and innovative contributions. The goal of this SMR was to provide state of the art, trends, and analysis of research related to semantic interoperability using FHIR. This activity specifically aimed to identify the FHIR and terminology used, as well as the different proposed approaches, contribution types, and trends.</p>
      </sec>
      <sec>
        <title>Related Work</title>
        <p>Of the number of literature reviews on the challenges of health information systems interoperability, only 4 specifically address FHIR standard issues [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. This section summarizes the findings of this study.</p>
        <p>The study by Ayaz et al [<xref ref-type="bibr" rid="ref10">10</xref>] reviewed 80 studies published between 2012 and 2019 that identified the opportunities and challenges associated with using FHIR. Another FHIR systematic review by Lehne et al [<xref ref-type="bibr" rid="ref9">9</xref>] identified the main issues to be considered when exchanging data based on only 2 data sources and presented an overview of 131 selected studies up to February 4, 2019. A third systematic literature review by Setyawan et al [<xref ref-type="bibr" rid="ref2">2</xref>] on data interoperability issues and possible solutions selected 39 studies published between 2018 and 2021 from 3 data sources (ie, IEEE Xplore, ScienceDirect, and Scopus). Finally, a systematic review of semantic interoperability in the study by de Mello et al [<xref ref-type="bibr" rid="ref11">11</xref>] selected 28 studies from 2012 to 2020 from 8 different sources.</p>
        <p>An overview of these 4 studies is presented in <xref ref-type="table" rid="table1">Table 1</xref> in terms of their study goal or objective, period covered, number of studies selected and analyzed, source databases, and their respective mapping and research questions (RQs).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Overview of the 4 literature reviews on semantic issues when using Fast Healthcare Interoperability Resources (FHIR).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="50"/>
            <col width="110"/>
            <col width="200"/>
            <col width="100"/>
            <col width="90"/>
            <col width="170"/>
            <col width="280"/>
            <thead>
              <tr valign="top">
                <td>ID</td>
                <td>Study, year</td>
                <td>Goal or objective</td>
                <td>Period covered</td>
                <td>Studies, n</td>
                <td>Source databases</td>
                <td>Mapping and research questions</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>R1</td>
                <td>Ayaz et al [<xref ref-type="bibr" rid="ref10">10</xref>], 2021</td>
                <td>A systematic review of the literature related to FHIR, including the challenges, implementation, opportunities, and future FHIR applications</td>
                <td>January 2012-December 2019</td>
                <td>80</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>ACM</p>
                    </list-item>
                    <list-item>
                      <p>IEEE</p>
                    </list-item>
                    <list-item>
                      <p>Springer</p>
                    </list-item>
                    <list-item>
                      <p>Google Scholar</p>
                    </list-item>
                    <list-item>
                      <p>PubMed</p>
                    </list-item>
                    <list-item>
                      <p>ScienceDirect</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Q1: Types or models of FHIR implementation?</p>
                    </list-item>
                    <list-item>
                      <p>Q2: Common resources used in FHIR implementation?</p>
                    </list-item>
                    <list-item>
                      <p>Q3: Applications that benefit from the use of FHIR?</p>
                    </list-item>
                    <list-item>
                      <p>Q4: Approaches applied to map or migrate data from previous standards to FHIR?</p>
                    </list-item>
                    <list-item>
                      <p>Q5: Goals of FHIR?</p>
                    </list-item>
                    <list-item>
                      <p>Q6: Challenges and open questions related to the FHIR domain?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>R2</td>
                <td>Lehne et al [<xref ref-type="bibr" rid="ref9">9</xref>], 2019</td>
                <td>Screen all FHIR publications and identify the main topics</td>
                <td>February 4, 2019</td>
                <td>131</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Web of science</p>
                    </list-item>
                    <list-item>
                      <p>PubMed</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>N/A<sup>a</sup></p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>R3</td>
                <td>Setyawan et al [<xref ref-type="bibr" rid="ref2">2</xref>], 2021</td>
                <td>Identify integration problems of HL7<sup>b</sup> FHIR implementation and provide technical solutions and nontechnical solutions to these problems</td>
                <td>2018-2021</td>
                <td>39</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>ScienceDirect</p>
                    </list-item>
                    <list-item>
                      <p>IEEE</p>
                    </list-item>
                    <list-item>
                      <p>SCOPUS</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Q1: State of the art of data integration and interoperability in HL7 FHIR implementation?</p>
                    </list-item>
                    <list-item>
                      <p>Q2: Problems the researcher has regarding Data Integration and Interoperability in HL7 FHIR Implementation?</p>
                    </list-item>
                    <list-item>
                      <p>Q3: Potential solutions and future research regarding Data Integration and Interoperability in HL7 FHIR Implementation?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>R4</td>
                <td>de Mello et al [<xref ref-type="bibr" rid="ref11">11</xref>], 2022</td>
                <td>Present a comprehensive systematic literature review of semantic interoperability in electronic health record</td>
                <td>2010-2020</td>
                <td>28</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>ACM</p>
                    </list-item>
                    <list-item>
                      <p>IEEE Xplore</p>
                    </list-item>
                    <list-item>
                      <p>Google scholar</p>
                    </list-item>
                    <list-item>
                      <p>MEDLINE</p>
                    </list-item>
                    <list-item>
                      <p>PubMed</p>
                    </list-item>
                    <list-item>
                      <p>ScienceDirect</p>
                    </list-item>
                    <list-item>
                      <p>SpringerLink</p>
                    </list-item>
                    <list-item>
                      <p>Web of Science</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Q1: State of the art in health standards applied in health records?</p>
                    </list-item>
                    <list-item>
                      <p>Q2: Challenge and open questions to semantic interoperability in health records.</p>
                    </list-item>
                    <list-item>
                      <p>Q3: Health standards adopted in the studies?</p>
                    </list-item>
                    <list-item>
                      <p>Q4: Terminologies or health repositories used?</p>
                    </list-item>
                    <list-item>
                      <p>Q5: Approaches used?</p>
                    </list-item>
                    <list-item>
                      <p>Q6: Main security concerns used?</p>
                    </list-item>
                    <list-item>
                      <p>Q7: Evaluation approaches used?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>N/A: not applicable.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>HL7: Health Level Seven International.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>To the best of our knowledge, no systematic mapping review has been published that specifically addresses the semantic issues raised when using FHIR.</p>
        <p>Some of the lessons learned in these studies and their limitations are presented in <xref ref-type="table" rid="table2">Table 2</xref>. The key findings are summarized as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>Most used FHIR resources from general FHIR implementation up to 2019: Observation, Patient, Practionner, Condition, Medication, AllergyIntolerance, Medication, Device [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
          </list-item>
          <list-item>
            <p>The study by Ayaz at al [<xref ref-type="bibr" rid="ref10">10</xref>] provides a distribution of the different techniques used for the mapping approach (eg, mapping HL7 v2 to FHIR and mapping FHIR to others).</p>
          </list-item>
          <list-item>
            <p>The formula string using FHIR as the keyword is general and allows maximum results [<xref ref-type="bibr" rid="ref9">9</xref>]. This study showed that ontology or terminology approaches were subject to a higher number of studies up to 2018.</p>
          </list-item>
          <list-item>
            <p>One study [<xref ref-type="bibr" rid="ref2">2</xref>] used a limited number of databases (only 3), and the formula string may limit the obtained results.</p>
          </list-item>
          <list-item>
            <p>We learned from the study by de Mello et al [<xref ref-type="bibr" rid="ref11">11</xref>] that the main approaches used are based on ontology and terminology, particularly SNOMED CT, International Classification of Diseases (ICD)-9 or ICD-10.</p>
          </list-item>
        </list>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Lessons learned and limitations of related work.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="60"/>
            <col width="420"/>
            <col width="520"/>
            <thead>
              <tr valign="top">
                <td>ID</td>
                <td>Lessons learned</td>
                <td>Limitations</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>R1</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Interesting mapping framework OR data model into the category of the most selected studies</p>
                    </list-item>
                    <list-item>
                      <p>Common resources used</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>More databases are needed</p>
                    </list-item>
                    <list-item>
                      <p>Formula for search may limit the result to semantic FHIR<sup>a</sup> studies</p>
                    </list-item>
                    <list-item>
                      <p>Are the identified resources still of interest for semantic interoperability?</p>
                    </list-item>
                    <list-item>
                      <p>Mapping to terminologies is not covered</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>R2</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Formula used help to select the maximum number of studies</p>
                    </list-item>
                    <list-item>
                      <p>Topics of interest: ontology, terminology, data models ontology, terminology, data, and information model, mapping</p>
                    </list-item>
                    <list-item>
                      <p>The ontology, terminology, and data models is the subject of a high number of the selected studies</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Limited list of databases</p>
                    </list-item>
                    <list-item>
                      <p>The number of studies continues to increase as of 2018</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>R3</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>N/A<sup>b</sup></p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Limited database sources</p>
                    </list-item>
                    <list-item>
                      <p>The search formula may limit the result as it must have the following: (challenge* OR problem* OR issue* OR trend*)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>R4</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Period: 2010-2020</p>
                    </list-item>
                    <list-item>
                      <p>Different approaches based on ontology and the use of terminology, especially SNOMED CT<sup>c</sup>, ICD<sup>d</sup>-9 or ICD-10</p>
                    </list-item>
                    <list-item>
                      <p>The use of OWL<sup>e</sup> and RDF<sup>f</sup> to solve semantic issues</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>HL7<sup>g</sup> FHIR is not in the list of identified standards based on the selected studies</p>
                    </list-item>
                    <list-item>
                      <p>The search based on semantic interoperability may limit the result as it used: “semantic interoperability” AND (“health record” OR “medical record” OR “patient record” OR “hospital record”) AND standard</p>
                    </list-item>
                    <list-item>
                      <p>A small number of articles selected</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>FHIR: Fast Healthcare Interoperability Resources.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>N/A: not applicable.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>SNOMED CT: Systematized Nomenclature of Medicine–clinical terms.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>ICD: International Classification of Diseases.</p>
            </fn>
            <fn id="table2fn5">
              <p><sup>e</sup>OWL: web ontology language.</p>
            </fn>
            <fn id="table2fn6">
              <p><sup>f</sup>RDF: resource description framework.</p>
            </fn>
            <fn id="table2fn7">
              <p><sup>g</sup>HL7: Health Level Seven International.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>These previous studies do not provide an overview of post-2019 developments related to semantic interoperability approaches and trends using FHIR. An extensive and more recent study is needed using many databases and a search string that includes the most possible semantic keywords.</p>
        <p>In contrast to related works, this SMR focuses on the semantic level of interoperability using FHIR and reports on research directions over the last decade.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>SMRs and systematic literature reviews typically use the same methodology, but their goals differ. The systematic literature review is driven by specific questions and the review aims to respond to these specific questions. In contrast, an SMR targets more high-level questions aimed at a specific topic, with the goal of providing a classification of the research results. An SMR can be helpful to researchers because it provides an overview of the literature at a given time for a specific topic of interest [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>According to the study by Petersen et al [<xref ref-type="bibr" rid="ref13">13</xref>], the mapping review process follows three steps: (1) planning the mapping, (2) conducting the mapping, and (3) reporting the results of the mapping. Furthermore, specific guidelines for a systematic mapping review in the software engineering domain as mentioned in the study by Brereton et al [<xref ref-type="bibr" rid="ref14">14</xref>] suggest more detailed activities at each step (<xref rid="figure2" ref-type="fig">Figure 2</xref>):</p>
        <list list-type="bullet">
          <list-item>
            <p>Planning: identification of the different items used for the research process, including RQs, resources and databases, search terms and formulas, inclusion and exclusion criteria, and questions for quality assessment (QA).</p>
          </list-item>
          <list-item>
            <p>Conducting: initial extraction of the studies was performed in this step. An initial preselection was performed, and both the inclusion and exclusion criteria were applied. The selected studies were then evaluated and filtered using QA questions.</p>
          </list-item>
          <list-item>
            <p>Reporting: during this step, mapping was conducted using the final selection of the studies, and a discussion of the results was presented.</p>
          </list-item>
        </list>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Mapping and review process for this Fast Healthcare Interoperability Resources study.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Research Questions</title>
        <p>A set of 5 questions was defined (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Research questions.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="100"/>
            <col width="900"/>
            <thead>
              <tr valign="bottom">
                <td>RQ<sup>a</sup> ID</td>
                <td>RQ</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>RQ1</td>
                <td>What are the main resources types studied or used in FHIR<sup>b</sup> semantic interoperability studies?</td>
              </tr>
              <tr valign="top">
                <td>RQ2</td>
                <td>Which terminologies are used in FHIR semantic interoperability studies?</td>
              </tr>
              <tr valign="top">
                <td>RQ3</td>
                <td>What are the semantic research approaches most frequently applied to achieve semantic interoperability?</td>
              </tr>
              <tr valign="top">
                <td>RQ4</td>
                <td>What are the main types of contributions within the selected studies?</td>
              </tr>
              <tr valign="top">
                <td>RQ5</td>
                <td>What are the publication sources and types?</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>RQ: research question.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>FHIR: Fast Healthcare Interoperability Resources.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Mapping Search Strategy</title>
        <sec>
          <title>Search String</title>
          <p>The search string was established iteratively: first, by using “FHIR” as a search term in 3 databases and screening the results to look for more keywords dealing with the subject of interest, and second, by identifying additional terms and their synonyms based on the RQs.</p>
          <p>The following is the search string composed using Boolean operators based on the identified terms: FHIR AND (Semantic OR terminology OR vocabulary OR Ontology OR mapping OR classification).</p>
          <p>The Zotero reference management tool [<xref ref-type="bibr" rid="ref15">15</xref>] was used to collect, organize, annotate, and review the abstract and full text to include or exclude studies that met the eligibility criteria. Zotero helps manage the large number of studies extracted for research.</p>
        </sec>
        <sec>
          <title>Search Databases</title>
          <p>The following 10 databases were used to identify and extract studies that satisfied the predefined search string: IEEE Xplore, ScienceDirect, Springer, Scopus, ACM, Web of Science, MEDLINE or PubMed, Compendex, Inspec, and Semantic Scholar.</p>
        </sec>
        <sec>
          <title>Eligibility Criteria</title>
          <p><xref ref-type="boxed-text" rid="box1">Textbox 1</xref> shows the inclusion and exclusion criteria for identified and extracted studies. Articles were excluded based on titles and abstracts as well as full-text reading in some cases.</p>
          <boxed-text id="box1" position="float">
            <title>Inclusion and exclusion criteria for identified or extracted studies.</title>
            <p>
              <bold>Inclusion criteria</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Published between 2012 and 2022 (start date of 2012 was chosen because it was the date of publication of the first draft of the Fast Healthcare Interoperability Resources [FHIR]).</p>
              </list-item>
              <list-item>
                <p>Published in English or French</p>
              </list-item>
            </list>
            <p>
              <bold>Exclusion criteria</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Studies not accessible in full text</p>
              </list-item>
              <list-item>
                <p>Books</p>
              </list-item>
              <list-item>
                <p>Studies reported on 2-3 pages</p>
              </list-item>
              <list-item>
                <p>Duplicate studies: We retained the most recent data</p>
              </list-item>
              <list-item>
                <p>Technical reports or summaries of conferences and editorials</p>
              </list-item>
              <list-item>
                <p>Studies that do not address semantics using FHIR</p>
              </list-item>
              <list-item>
                <p>Studies addressing enhancements to FHIR terminology and comparisons</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
      </sec>
      <sec>
        <title>Quality Assessment</title>
        <p>QA of a research publication is a crucial selection step to ensure that the selected studies have the appropriate impact for mapping reviews and further analysis [<xref ref-type="bibr" rid="ref12">12</xref>]. For this purpose, we defined quality criteria scores based on the following questions.</p>
        <list list-type="bullet">
          <list-item>
            <p>QA1: Are the objectives of the research clearly defined?</p>
          </list-item>
          <list-item>
            <p>QA2: Does the author present results that meet the stated research objectives?</p>
          </list-item>
          <list-item>
            <p>QA3: Is the method or technique used to achieve semantic interoperability clearly described?</p>
          </list-item>
          <list-item>
            <p>QA4: Is a literature review provided?</p>
          </list-item>
          <list-item>
            <p>QA5: Is the author’s contribution clearly stated?</p>
          </list-item>
          <list-item>
            <p>QA6: Is a result validation strategy presented?</p>
          </list-item>
        </list>
        <p>Quality evaluation of the identified and extracted studies was performed by answering each QA question. The selected studies satisfied at least 4 of the 6 QA criteria. Others were rejected.</p>
      </sec>
      <sec>
        <title>Data Extraction and Data Synthesis</title>
        <p>This SMR was conducted in 2022, with publications published from 2012 to 2022. A summary of the data extraction showing the selection filter effect is presented in <xref rid="figure3" ref-type="fig">Figure 3</xref>.</p>
        <list list-type="bullet">
          <list-item>
            <p>2601 results were obtained in the first step</p>
          </list-item>
          <list-item>
            <p>2372 remained after applying the exclusion criteria for studies published out of the range of 2012‑2022</p>
          </list-item>
          <list-item>
            <p>1701 remained after the applying the exclusion criteria on venue type is possible, when available</p>
          </list-item>
          <list-item>
            <p>1692 for studies remained after applying the English or French language restriction</p>
          </list-item>
          <list-item>
            <p>70 studies remained after removing duplicates, applying the additional inclusion, exclusion criteria and QA.</p>
          </list-item>
        </list>
        <p>The 70 studies retained are listed in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref85">85</xref>]. The extracted data are presented in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Search steps and results from databases. QA: quality assessment.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>This section presents findings related to the 5 RQs listed in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
      <sec>
        <title>RQ1: Main FHIR Resources Types Studied or Used</title>
        <p>We reviewed 70 selected studies and identified the types of FHIR resources that were used. <xref ref-type="table" rid="table4">Table 4</xref> lists the 62 types of resources identified in the corresponding studies that have used them. In <xref rid="figure4" ref-type="fig">Figure 4</xref>, the resource types are presented, from most frequently used to least used.</p>
        <p>The 10 most referred or used resource types in these studies were Observation (31/297, 10.4%), Patient (29/297, 9.8%), Medication (19/297, 6.4%), Condition (16/297, 5.4%), CodeSystem (15/297, 5.1%), Encounter (11/297, 3.7%), Procedure (11/297, 3.7%), Medication Request (10/297, 3.4%), Practitionner (10/297, 3.4%), and ValueSet (9/297, 3%).</p>
        <p>The HL7 organization classifies the list of resources into five categories: (1) foundation, (2) base, (3) clinical, (4) financial, and (5) specialized resources. Each of these categories was further divided into 5 subcategories, except for the financial resources category, which was subdivided into 4 subcategories.</p>
        <p>The resources inventoried in the 70 selected studies were mostly in 3 clinical subcategories: summary, medications, and diagnosis (<xref rid="figure5" ref-type="fig">Figure 5</xref> and <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). There is one exception to Patient and Encounter resources, which are in the base category and mainly used for identification purposes. We also noted the terminology subcategory (foundation category) among the top 10 most used resources. Terminology resources were used to map concepts to FHIR terminology (eg, SNOMED CT and LOINC).</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Fast Health Care Interoperability Resources types used and related studies.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="270"/>
            <col width="630"/>
            <col width="100"/>
            <thead>
              <tr valign="top">
                <td>Resource type</td>
                <td>Study ID</td>
                <td>Studies, n</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Observation</td>
                <td>S2, S42, S43, S68, S47, S60, S48, S6, S7, S8, S9, S11, S12, S40, S28, S13, S14, S15, S54, S55, S56, S38, S22, S61, S23, S62, S5, S34, S69, S70</td>
                <td>30</td>
              </tr>
              <tr valign="top">
                <td>Patient</td>
                <td>S1, S42, S43, S68, S65, S46, S47, S60, S48, S50, S39, S9, S11, S13, S14, S15, S16, S54, S55, S30, S56, S38, S22, S23, S5, S34, S52, S69, S70</td>
                <td>29</td>
              </tr>
              <tr valign="top">
                <td>Medication</td>
                <td>S1, S68, S36, S47, S63, S4, S60, S48, S6, S39, S9, S14, S54, S55, S31, S22, S61, S5, S69</td>
                <td>19</td>
              </tr>
              <tr valign="top">
                <td>Condition</td>
                <td>S25, S68, S60, S6, S39, S8, S9, S11, S12, S40, S14, S15, S54, S22, S61, S62</td>
                <td>16</td>
              </tr>
              <tr valign="top">
                <td>CodeSystem</td>
                <td>S37, S9, S29, S10, S40, S41, S17, S18, S20, S61, S33, S14, S15, S21, S28</td>
                <td>15</td>
              </tr>
              <tr valign="top">
                <td>Encounter</td>
                <td>S1, S68, S60, S39, S9, S11, S16, S38, S23, S62, S5</td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>Procedure</td>
                <td>S68, S60, S39, S8, S9, S40, S61, S5, S62, S12, S69</td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>Practitionner</td>
                <td>S68, S47, S60, S50, S9, S15, S16, S34, S23, S70</td>
                <td>10</td>
              </tr>
              <tr valign="top">
                <td>MedicationRequest</td>
                <td>S1, S68, S63, S4, S39, S53, S62, S22, S61, S69</td>
                <td>10</td>
              </tr>
              <tr valign="top">
                <td>ValueSet</td>
                <td>S37, S9, S29, S40, S41, S17, S18, S61, S14</td>
                <td>9</td>
              </tr>
              <tr valign="top">
                <td>MedicationStatement</td>
                <td>S68, S6, S8, S9, S40, S14, S61</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>FamilyMemberHistory</td>
                <td>S68, S60, S39, S8, S15, S54, S61</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>AllergyIntolerance</td>
                <td>S68, S60, S9, S67, S28, S15, S62</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>DiagnosisReport</td>
                <td>S1, S40, S14, S5, S62, S34, S70</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>CarePlan</td>
                <td>S68, S60, S50, S9, S23, S62</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>Device</td>
                <td>S2, S43, S68, S60, S7, S39</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>ServiceRequest</td>
                <td>S60, S39, S9, S38, S34, S69</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>ConceptMap</td>
                <td>S37, S13, S41, S17, S19, S69</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>StructureDefinition</td>
                <td>S44, S38, S53, S40, S69</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>Specimen</td>
                <td>S60, S9, S40, S34</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Questionnaire</td>
                <td>S28, S15, S30, S23</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Organization</td>
                <td>S60, S16, S38, S23</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>MedicationAdministration</td>
                <td>S47, S48, S39, S9</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Appointment</td>
                <td>S60, S9, S28, S69</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Immunization</td>
                <td>S60, S40, S62</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Composition</td>
                <td>S8, S61, S69</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Communication</td>
                <td>S39, S9, S69</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>RiskAssessment</td>
                <td>S60, S28, S69</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>HealthcareService</td>
                <td>S60, S9</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>Goal</td>
                <td>S68, S62</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>EpisodeOfCare</td>
                <td>S68, S23</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>DeviceDefinition</td>
                <td>S2, S7</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>CareTeam</td>
                <td>S68, S60</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>AdverseEvent</td>
                <td>S68, S60</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>ActivityDefinition</td>
                <td>S23, S43</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>RelatedPerson</td>
                <td>S68, S60</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>Coverage</td>
                <td>S9, S16</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>ClinicalImpression</td>
                <td>S12, S23</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>Location</td>
                <td>S68, S69</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>NutritionOrder</td>
                <td>S68, S69</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>PlanDefinition</td>
                <td>S23, S69</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>DocumentReference</td>
                <td>S60</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>MedicationDispense</td>
                <td>S39</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>DeviceUseStatement</td>
                <td>S9</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Consent</td>
                <td>S9</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Person</td>
                <td>S28</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Schedule</td>
                <td>S15</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>PractionnerRole</td>
                <td>S16</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>QuestionnaireResponse</td>
                <td>S23</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>ImagingStudy</td>
                <td>S23</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Substance</td>
                <td>S39</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Account, Library, Claim, DocumentManifest, EnrollmentResponse, CoverageEligibilityRequest, SupplyDelivery, PaymentNotice, OperationDefinition, GuidanceResponse, ImplementationGuide, CapabilityStatement,</td>
                <td>S69</td>
                <td>1</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Distribution of the resources used.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>Distribution of the Fast Healthcare Interoperability Resources types used by category.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>RQ2: Which FHIR Terminologies Were Used</title>
        <p>A total of 9 distinct FHIR terminologies were used in the 70 selected studies (<xref ref-type="table" rid="table5">Table 5</xref>).</p>
        <p>Their distribution and percentage are as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>SNOMED CT (31/98, 32%) and LOINC (25/98, 26%) were the most commonly used.</p>
          </list-item>
          <list-item>
            <p>ICD-9 and ICD-10 (15/98, 15%) and Unified Medical Language System (13/98, 13%)</p>
          </list-item>
          <list-item>
            <p>RxNORM (9/98, 9%)</p>
          </list-item>
          <list-item>
            <p>The remaining terminologies (anatomical therapeutic chemical, quality data model, national drug file–reference terminology, and classification of instructional programs code) accounted for &#60;10%.</p>
          </list-item>
        </list>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>List of terminologies being used.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="180"/>
            <col width="820"/>
            <thead>
              <tr valign="top">
                <td>Terminology</td>
                <td>Study ID</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>SNOMED CT<sup>a</sup></td>
                <td>S2, S34, S3, S35, S4, S48, S5, S49, S7, S8, S9, S29, S10, S11, S12, S40, S28, S53, S14, S16, S41, S31, S38, S18, S66, S22, S61, S23, S13, S25, S64</td>
              </tr>
              <tr valign="top">
                <td>LOINC<sup>b</sup></td>
                <td>S2, S34, S3, S35, S5, S6, S7, S8, S27, S9, S11, S13, S16, S54, S30, S56, S41, S38, S20, S66, S21, S22, S23, S24, S36</td>
              </tr>
              <tr valign="top">
                <td>ICD<sup>c</sup>-9 or ICD-10</td>
                <td>S34, S1, S35, S49, S6, S9, S54, S30, S41, S17, S18, S66, S22, S33, S26</td>
              </tr>
              <tr valign="top">
                <td>UMLS<sup>d</sup></td>
                <td>S34, S43, S37, S5, S27, S14, S19, S66, S21, S61, S64, S25, S8</td>
              </tr>
              <tr valign="top">
                <td>RxNorm<sup>e</sup></td>
                <td>S36, S6, S8, S9, S14, S54, S31, S22, S61</td>
              </tr>
              <tr valign="top">
                <td>ATC<sup>f</sup></td>
                <td>S1, S8</td>
              </tr>
              <tr valign="top">
                <td>QDM<sup>g</sup></td>
                <td>S39</td>
              </tr>
              <tr valign="top">
                <td>NDF-RT<sup>h</sup></td>
                <td>S48</td>
              </tr>
              <tr valign="top">
                <td>CIP<sup>i</sup> Code</td>
                <td>S1</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>SNOMED CT: Systematized Nomenclature of Medicine–clinical terms.</p>
            </fn>
            <fn id="table5fn2">
              <p><sup>b</sup>LOINC: Logical Observation Identifiers Names and Codes.</p>
            </fn>
            <fn id="table5fn3">
              <p><sup>c</sup>ICD: International Classification of Diseases.</p>
            </fn>
            <fn id="table5fn4">
              <p><sup>d</sup>UMLS: Unified Medical Language System.</p>
            </fn>
            <fn id="table5fn5">
              <p><sup>e</sup>RxNORM: medical prescription normalized Medical prescription.</p>
            </fn>
            <fn id="table5fn6">
              <p><sup>f</sup>ATC: anatomical therapeutic chemical.</p>
            </fn>
            <fn id="table5fn7">
              <p><sup>g</sup>QDM: quality data model.</p>
            </fn>
            <fn id="table5fn8">
              <p><sup>h</sup>NDF-RT: national drug file–reference terminology.</p>
            </fn>
            <fn id="table5fn9">
              <p><sup>i</sup>CIP: classification of instructional programs.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>RQ3: Semantic Research Approaches Most Frequently Applied</title>
        <p>A total of six main semantic research approaches were identified from the solutions proposed in the 70 selected studies:</p>
        <list list-type="order">
          <list-item>
            <p>Mapping to FHIR terminology (mapping)</p>
          </list-item>
          <list-item>
            <p>Terminology services (terminology)</p>
          </list-item>
          <list-item>
            <p>Transformation, development, and validation resource description framework (RDF) or web ontology language (OWL)</p>
          </list-item>
          <list-item>
            <p>Machine learning (ML) and natural language processing (NLP)</p>
          </list-item>
          <list-item>
            <p>Semantic annotation (annotation)</p>
          </list-item>
          <list-item>
            <p>Ontology-based approach (ontology)</p>
          </list-item>
        </list>
        <p><xref ref-type="table" rid="table6">Table 6</xref> presents the semantic research approaches used to decrease the frequency of use in the selected studies.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Semantic research approaches and related studies.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="340"/>
            <col width="450"/>
            <col width="210"/>
            <thead>
              <tr valign="top">
                <td>Semantic approach</td>
                <td>Studies IDs</td>
                <td>Distribution (N=126), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Mapping to Fast Healthcare Interoperability Resources terminologies (mapping)</td>
                <td>S1, S2, S4, S5, S6, S7, S8, S9, S10, S11, S13, S14, S15, S16, S17, S18, S20, S21, S22, S23, S24, S25, S27, S28, S29, S30, S31, S32, S33, S38, S41</td>
                <td>31 (24.6)</td>
              </tr>
              <tr valign="top">
                <td>Terminology services (terminology)</td>
                <td>S5, S13, S17, S18, S19, S20, S21, S28, S30, S33, S34, S35, S36, S37, S38, S39, S40, S41</td>
                <td>18 (14.3)</td>
              </tr>
              <tr valign="top">
                <td>Transformation or development or validation resource description framework or web ontology language</td>
                <td>S3, S10, S12, S14, S35, S42, S43, S44, S45, S46, S47, S48, S49, S50, S51, S52, S53, S54, S55, S56, S57, S58, S59, S69</td>
                <td>24 (19)</td>
              </tr>
              <tr valign="top">
                <td>Semantic annotation (annotation)</td>
                <td>S2, S3, S6, S7, S14, S25, S27, S30, S31, S32, S43, S45, S48, S60, S61, S62, S63, S64</td>
                <td>18 (14.3)</td>
              </tr>
              <tr valign="top">
                <td>Machine learning or natural language processing</td>
                <td>S5, S6, S8, S14, S25, S26, S31, S32, S43, S46, S49, S54, S60, S61, S62, S63, S64, S65, S66, S67</td>
                <td>20 (15.9)</td>
              </tr>
              <tr valign="top">
                <td>Ontology-based approach (ontology)</td>
                <td>S3, S11, S12, S13, S26, S40, S44, S46, S47, S49, S50, S55, S66, S68, S70</td>
                <td>15 (11.9)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The distribution of the 6 semantic approaches is as follow: mapping (31/126, 24.6%), RDF or OWL (24/126, 19%), ML and NLP (20/126, 15.9%), annotation (18/126, 14.3%), terminology (18/126, 14.3%), and ontology (15/126, 11.9%).</p>
        <p>The selected studies used at least one of the 6 identified semantic research approaches, and most studies used more than one research approach. For example, 22 of the 31 studies listed in <xref ref-type="table" rid="table6">Table 6</xref> used mapping and other approaches (70%), whereas only 29% (9/31) used mapping alone.</p>
        <p>To better understand the frequency of combinations of more than one semantic research approach, we identified a number of studies using more than one approach. We performed the same exercise for RDF or OWL followed by annotation. <xref ref-type="table" rid="table7">Table 7</xref> shows that most combined semantic approaches are annotation and ML and NLP, mapping and terminology services, mapping and annotation, RDF or OWL, and ontology.</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>Distribution of the combined approaches</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="120"/>
            <col width="140"/>
            <col width="150"/>
            <col width="130"/>
            <col width="140"/>
            <col width="120"/>
            <thead>
              <tr valign="bottom">
                <td>Category</td>
                <td>Mapping</td>
                <td>Terminology</td>
                <td>RDF<sup>a</sup> or OWL<sup>b</sup></td>
                <td>Annotation</td>
                <td>ML<sup>c</sup> and NLP<sup>d</sup></td>
                <td>Ontology</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Mapping</td>
                <td>—<sup>e</sup></td>
                <td>11</td>
                <td>2</td>
                <td>9</td>
                <td>7</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>Terminology</td>
                <td>—</td>
                <td>—</td>
                <td>0</td>
                <td>1</td>
                <td>1</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>RDF and OWL</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>5</td>
                <td>5</td>
                <td>8</td>
              </tr>
              <tr valign="top">
                <td>Annotation</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>11</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>ML and NLP</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Ontology</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
                <td>—</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table7fn1">
              <p><sup>a</sup>RDF: resource description framework.</p>
            </fn>
            <fn id="table7fn2">
              <p><sup>b</sup>OWL: web ontology language.</p>
            </fn>
            <fn id="table7fn3">
              <p><sup>c</sup>ML: machine learning.</p>
            </fn>
            <fn id="table7fn4">
              <p><sup>d</sup>NLP: natural language processing.</p>
            </fn>
            <fn id="table7fn5">
              <p><sup>e</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>The next analysis related to the proposed approach examined how these approaches evolved over time. <xref rid="figure6" ref-type="fig">Figure 6</xref> shows how these approaches were used over time. The main finding are (1) ML and NLP-based proposals emerged in 2018 in FHIR semantic interoperability studies, (2) the other approaches span the full period, and (3) no specific research approach dominates the FHIR semantic interoperability research field.</p>
        <fig id="figure6" position="float">
          <label>Figure 6</label>
          <caption>
            <p>Timeline of semantic research approaches used in the selected studies. ML: machine learning; NLP: natural language processing; RDF: resource description framework.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>RQ4: Main Types of Contributions</title>
        <p>The objective of RQ4 was to identify the contribution types within each of the 70 selected studies. For this purpose, five main contributions were identified: (1) new framework or architecture intended to enable semantic interoperability (framework or architecture proposal), (2) evaluation or comparison of different techniques (eg, comparison of ontologies), (3) new ontology, model or enhancement of an existing one (model proposal), (4) a new technique or improvement of an existing technique (new technique proposal), and (5) a tool proposal through the development of a new tool or an enhancement to existing ones to facilitate achieving semantic interoperability (tool proposal).</p>
        <p><xref ref-type="table" rid="table8">Table 8</xref> presents the distribution of the 70 studies selected according to contribution type.</p>
        <p><xref rid="figure7" ref-type="fig">Figure 7</xref> shows the distribution of studies by contribution type.</p>
        <p>The most frequent contribution type was the proposal of a framework or architecture (26/70, 37%), followed by model proposals (13/70, 19%), new or improved techniques (13/70, 19%), comparison services (10/70, 14%), and tool proposals (8/70, 11%).</p>
        <table-wrap position="float" id="table8">
          <label>Table 8</label>
          <caption>
            <p>Studies by contribution type.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="750"/>
            <thead>
              <tr valign="top">
                <td>Contribution type</td>
                <td>Studies</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Framework or architecture</td>
                <td>S2, S5, S7, S8, S14, S16, S20, S22, S23, S25, S26, S29, S31, S34, S35, S38, S41, S43, S51, S53, S54, S61, S62, S65, S66, S68</td>
              </tr>
              <tr valign="top">
                <td>Comparison</td>
                <td>S4, S15, S17, S32, S33, S46, S56, S58, S59, S67</td>
              </tr>
              <tr valign="top">
                <td>Model</td>
                <td>S1, S3, S6, S30, S39, S40, S45, S48, S49, S50, S55, S60, S63</td>
              </tr>
              <tr valign="top">
                <td>Technique</td>
                <td>S9, S10, S12, S18, S19, S21, S24, S27, S42, S47, S64, S69, S70</td>
              </tr>
              <tr valign="top">
                <td>Tool</td>
                <td>S11, S13, S28, S36, S37, S44, S52, S57</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <fig id="figure7" position="float">
          <label>Figure 7</label>
          <caption>
            <p>Distribution of the studies by contribution type.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e45209_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>RQ5: Publications Sources and Types</title>
        <sec>
          <title>Publication Sources</title>
          <p>The distribution of publication sources and the number of studies is summarized as follows (<xref rid="figure8" ref-type="fig">Figure 8</xref>):</p>
          <list list-type="bullet">
            <list-item>
              <p>The top publication sources were <italic>Studies in Health Technology and Informatics</italic> (8/70, 11%), followed by <italic>CEUR Workshop</italic> and the <italic>Journal of Biomedical Informatics</italic> (6/70, 9%).</p>
            </list-item>
            <list-item>
              <p><italic>JMIR Medical Informatics</italic> and <italic>BMC Medical Informatics and Decision Making</italic> follow with (4/70, 6%).</p>
            </list-item>
            <list-item>
              <p>Approximately (3/70, 4%) of the publications are from 3 sources: <italic>Journal of Biomedical Semantic</italic>, American Medical Informatics Association (AMIA) Joint Summits on Translational Science proceedings, and AMIA Annual Symposium.</p>
            </list-item>
            <list-item>
              <p>Approximately (2/70, 3%) of the publications are from 4 sources: the <italic>Journal of Medical Systems</italic> , IEEE International Conference on Bioinformatics and Biomedicine, International Conference of the IEEE Engineering in Medicine and Biology Society, and the <italic>Journal of the AMIA</italic>.</p>
            </list-item>
            <list-item>
              <p>Each of the remaining 25 publications represented 1%, with 1 study per source.</p>
            </list-item>
          </list>
          <fig id="figure8" position="float">
            <label>Figure 8</label>
            <caption>
              <p>Publication sources and corresponding number of studies.</p>
            </caption>
            <graphic xlink:href="jmir_v26i1e45209_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Publication Types</title>
          <p>The distribution of the selected studies by venue type (<xref ref-type="table" rid="table9">Table 9</xref>) showed that most of selected studies were published in a journal (46/70, 66%), followed by conferences (15/70, 21%), workshops (6/70, 9%), and symposiums (3/70, 4%).</p>
          <table-wrap position="float" id="table9">
            <label>Table 9</label>
            <caption>
              <p>Number of studies per venue type (N=70).</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="500"/>
              <col width="500"/>
              <thead>
                <tr valign="top">
                  <td>Venue type</td>
                  <td>Studies, n (%)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Journal</td>
                  <td>46 (66)</td>
                </tr>
                <tr valign="top">
                  <td>Conference</td>
                  <td>15 (21)</td>
                </tr>
                <tr valign="top">
                  <td>Workshop</td>
                  <td>6 (9)</td>
                </tr>
                <tr valign="top">
                  <td>Symposium</td>
                  <td>3 (4)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Overview</title>
        <p>This section presents a discussion of each of the key findings of the RQs.</p>
        <list list-type="order">
          <list-item>
            <p>Most studies have concentrated on clinical data resources; therefore, the focus has been on patient summaries.</p>
          </list-item>
          <list-item>
            <p>Terminology mapping to SNOMED CT and LOINC was performed in more than half of the selected studies. None of the 5 approaches was dominant in the proposed solutions to semantic interoperability challenges.</p>
          </list-item>
          <list-item>
            <p>Most of the selected studies proposed a framework or architecture as a solution to enable semantic interoperability.</p>
          </list-item>
          <list-item>
            <p>In recent years, research on semantic interoperability has increased since 2018.</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>RQ Results</title>
        <sec>
          <title>RQ1: What Are the Main Resource Types Studied or Used?</title>
          <p>As most studies concentrated on clinical data resources (eg, Observation, Medication, Condition, Procedure, and MedicationRequesL), the focus has been on patient summary including the medical condition, medication, and diagnosis.</p>
          <p>The attributes of these resource-use codes (CodeableConcept) and terminology standards, such as SNOMED CT and LOINC, are already included in the FHIR body. For example, the Observation resource has an attribute code in which the practitioner or user can document the observation type using LOINC code. Similarly, the Medication resource prescribed can be entered either as a code using SNOMED CT or as a textual description.</p>
          <p>In contrast, other types of resources (eg, BodyOfStructure) were not addressed in the selected studies.</p>
        </sec>
        <sec>
          <title>RQ2: Which Terminologies Were Used?</title>
          <p>Terminology mapping to SNOMED CT and LOINC was present in more than half of the selected studies, where SNOMED CT is used mainly for medication, procedure, and condition (problem); SNOMED CT or ICD-10 for diseases and diagnosis; and LOINC for observation and diagnostic report.</p>
          <p>Some countries have attempted to develop a consensus on the terminology to be used at the regional or national level. For example, SNOMED CT was adopted as a single terminology in the United Kingdom by the National Health Service (S12). In Switzerland, the federal initiative of the Swiss Personalized Health Network created a semantic framework available for health communities aiming to use the existing standards instead of building a new one, and the semantics were mapped by domain experts on the existing standards, such as SNOMED CT, LOINC, and ICD. RDF is used to store and transport data. In another regional initiative in Italy, the LOINC vocabulary was used to represent concepts already defined in local and standardized terminologies (S20).</p>
        </sec>
        <sec>
          <title>RQ3: What Are the Most Frequently Applied Research Approaches to Achieve Semantic Interoperability?</title>
          <p>None of the 5 approaches were dominant in the proposed solutions to semantic interoperability challenges. The emerging ML and NLP approach is mostly applied to annotation.</p>
          <p>ML and NLP techniques, which have achieved significant penetration in many other information system or information technology domains, have also been used in FHIR semantic interoperability research. On the one hand, the capability of the ML and NLP techniques for automation and prediction is often required for complex use cases. On the other hand, RDF representation has the specific advantage of containing information about semantic links and dependencies between multiple resources. This could explain why transformation to or from RDF is useful for semantic interoperability.</p>
        </sec>
        <sec>
          <title>RQ4: What Are the Main Types of Contributions Within the Selected Studies?</title>
          <p>Most of the selected studies proposed a framework or architecture as a solution to enable semantic interoperability. Research on achieving semantic interoperability using FHIR has tackled different steps and activities: collecting, extracting, and annotating data; modeling data from legacy systems; and applying transformation and mapping to FHIR models and terminologies. The following research topics were identified.</p>
          <list list-type="bullet">
            <list-item>
              <p>One of the main topics in the selected studies was related to unstructured data because valuable information can be extracted from free text for research and health analytics. The standardization of unstructured clinical notes was the focus of the research for specific use cases in the selected studies. The process of concept extraction and mapping text to standardized terminologies or ontologies requires more automation.</p>
            </list-item>
            <list-item>
              <p>Research on unstructured data using annotation and NLP is a relatively new field for the FHIR community, and challenges related to protecting privacy and security (deidentification and pseudonymization) remain open questions.</p>
            </list-item>
            <list-item>
              <p>The manual mapping of clinical terminology requires significant effort. The use of a tool can reduce the effort required for mapping and increase the adoption of terminology.</p>
            </list-item>
            <list-item>
              <p>Another challenge is related to languages other than English. In S24, a tool was developed to map Russian local terminology to LOINC.</p>
            </list-item>
            <list-item>
              <p>Even though the FHIR standard allows the use of clinical terminologies such as SNOMED CT and LOINC, users still enter information as text or use local terminologies. For example, selecting an appropriate concept from SNOMED CT is not a trivial task. To this end, a proposed solution called Ontoserver (eg, a clinical terminology service) offers a prefix-based search algorithm to help users easily find content and enter coded data. Ontoserver was used in several studies (S5, S10, S11, S17, S18, S40, and S41), and limitations related to its performance were reported.</p>
            </list-item>
            <list-item>
              <p>Comparison and mapping ontologies: detecting similarities and differences is still of interest and may attract more researchers.</p>
            </list-item>
          </list>
        </sec>
        <sec>
          <title>RQ5: What Are the Publication Sources and Types?</title>
          <p>Research on FHIR semantic interoperability emerged in 2015 and has increased since 2018. This probably is linked to the first release HL7 FHIR with a “Normative” status in 2018 indicating that its content has been recognized at the international level as stable for use and has been “locked” for several years. The publication trend in <xref rid="figure9" ref-type="fig">Figure 9</xref> that shows the distribution of the selected studies over time confirms that research on this topic is still active.</p>
          <fig id="figure9" position="float">
            <label>Figure 9</label>
            <caption>
              <p>Number of studies over time.</p>
            </caption>
            <graphic xlink:href="jmir_v26i1e45209_fig9.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Assumptions and Limitations</title>
        <p>This study was limited to semantic studies using only the FHIR standard, and it did not search for other studies related to semantic interoperability in general; therefore, this SMR focused exclusively on studies addressing FHIR implementation.</p>
        <p>Furthermore, only studies from the 10 database sources specified were considered, and commercial solutions were excluded.</p>
        <p>During the classification of the contribution based on 5 categories, 2 studies (S40 and S49) were considered in 2 different categories (model and technique). Both situations were evaluated and the results were only slightly different.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This SMR inventoried and analyzed the findings on semantic interoperability using FHIR over the last decade (2012-2022) in 70 selected studies from 10 databases. It presents a classification of the selected studies according to the semantic approaches used and their contributions. It also provides the frequency of use of FHIR resources and terminologies.</p>
        <p>These findings provide researchers with an inventory of the approaches used to achieve semantic interoperability using the FHIR. The SMR also documented the frequency with which the proposed approaches were used. This may help identify avenues for research on semantic interoperability. It can also be used as a guideline by the FHIR community for the future development of approaches and types of resources that are not well covered in research published to date.</p>
        <p>Indeed, understanding and interpreting the exchanged data in the EHR ecosystem needs to be supported by further research using, for instance, FHIR in mapping, RDF or OWL, and comparing ontologies and terminology services.</p>
        <p>Semantic interoperability is still an active research field, and there is no broad consensus in the health care community on how to achieve full semantic interoperability between information systems. The main issues reported are related to the difficulty associated with the use of different terminologies and the efforts required to successfully map to FHIR terminology. Even worse, when no terminology is used, unstructured data would still need to be extracted and mapped to the appropriate concept code for FHIR terminology.</p>
        <p>This SMR provides a classification of the different solutions proposed to address semantic interoperability using FHIR at different steps: collecting, extracting and annotating data, modeling EHR data from legacy systems, and applying transformation and mapping to FHIR models and terminologies. The use of ML and NLP for unstructured data is promising and has been applied to specific use case scenarios. In addition, terminology services are needed to accelerate their use and adoption; furthermore, techniques and tools to automate annotation and ontology comparison should help reduce human interaction.</p>
        <p>Future work will be devoted to the FHIR-based framework for the semantic interoperability of EHR data.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Targeted resources from a semantic point of view.</p>
        <media xlink:href="jmir_v26i1e45209_app1.png" xlink:title="PNG File , 526 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>List of the selected studies (N=70).</p>
        <media xlink:href="jmir_v26i1e45209_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 152 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Extracted data and searching strategy results.</p>
        <media xlink:href="jmir_v26i1e45209_app3.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 134 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AMIA</term>
          <def>
            <p>American Medical Informatics Association</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">FHIR</term>
          <def>
            <p>Fast Healthcare Interoperability Resources</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HL7</term>
          <def>
            <p>Health Level Seven International</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">ICD</term>
          <def>
            <p>International Classification of Diseases</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">IEEE</term>
          <def>
            <p>Institute of Electrical and Electronics Engineers</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">LOINC</term>
          <def>
            <p>Logical Observation Identifiers Names and Codes</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">ML</term>
          <def>
            <p>machine learning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">OWL</term>
          <def>
            <p>web ontology language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">QA</term>
          <def>
            <p>quality assessment</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">RDF</term>
          <def>
            <p>resource description framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">RQ</term>
          <def>
            <p>research question</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">SMR</term>
          <def>
            <p>systematic mapping review</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">SNOMED CT</term>
          <def>
            <p>Systematized Nomenclature of Medicine–clinical terms</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <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>Nordo</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Levaux</surname>
              <given-names>HP</given-names>
            </name>
            <name name-style="western">
              <surname>Becnel</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Galvez</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rao</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Stem</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Prakash</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kush</surname>
              <given-names>RD</given-names>
            </name>
          </person-group>
          <article-title>Use of EHRs data for clinical research: historical progress and current applications</article-title>
          <source>Learn Health Syst</source>
          <year>2019</year>
          <month>01</month>
          <day>16</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>e10076</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31245598"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/lrh2.10076</pub-id>
          <pub-id pub-id-type="medline">31245598</pub-id>
          <pub-id pub-id-type="pii">LRH210076</pub-id>
          <pub-id pub-id-type="pmcid">PMC6508843</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Setyawan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hidayanto</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Sensuse</surname>
              <given-names>DI</given-names>
            </name>
            <collab>Kautsarina</collab>
            <name name-style="western">
              <surname>Suryono</surname>
              <given-names>RR</given-names>
            </name>
            <name name-style="western">
              <surname>Abilowo</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Data integration and interoperability problems of HL7 FHIR implementation and potential solutions: a systematic literature review</article-title>
          <source>Proceedings of the 5th International Conference on Informatics and Computational Sciences</source>
          <year>2021</year>
          <conf-name>ICICoS '21</conf-name>
          <conf-date>November 24-25, 2021</conf-date>
          <conf-loc>Semarang, Indonesia</conf-loc>
          <fpage>293</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9651762/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/icicos53627.2021.9651762</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>IEEE standard glossary of software engineering terminology</article-title>
          <source>IEEE Std 610.12-1990</source>
          <year>1990</year>
          <month>12</month>
          <day>31</day>
          <access-date>2024-01-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/159342">https://ieeexplore.ieee.org/document/159342</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>Interoperability in healthcare</article-title>
          <source>Healthcare Information and Management Systems Society</source>
          <access-date>2024-01-04</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/resources/interoperability-healthcare">https://www.himss.org/resources/interoperability-healthcare</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bender</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sartipi</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>HL7 FHIR: an agileRESTful approach to healthcare information exchange</article-title>
          <source>Proceedings of the 26th IEEE International Symposium on Computer-Based Medical Systems</source>
          <year>2013</year>
          <conf-name>CBMS '13</conf-name>
          <conf-date>June 20-22, 2013</conf-date>
          <conf-loc>Porto, Portugal</conf-loc>
          <fpage>326</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/6627810"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/cbms.2013.6627810</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Benson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Grieve</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <source>Principles of Health Interoperability: FHIR, HL7 and SNOMED CT</source>
          <year>2021</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </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>Dullabh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hovey</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Heaney-Huls</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rajendran</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
          </person-group>
          <article-title>Application programming interfaces in health care: findings from a current-state sociotechnical assessment</article-title>
          <source>Appl Clin Inform</source>
          <year>2020</year>
          <month>01</month>
          <day>09</day>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>59</fpage>
          <lpage>69</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0039-1701001"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0039-1701001</pub-id>
          <pub-id pub-id-type="medline">31968383</pub-id>
          <pub-id pub-id-type="pii">SHTI190164</pub-id>
          <pub-id pub-id-type="pmcid">PMC6976305</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <article-title>Cloud providers unite for healthcare interoperability</article-title>
          <source>HL7 International</source>
          <access-date>2022-12-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blog.hl7.org/cloud-providers-unite-for-healthcare-interoperability-fhir">https://blog.hl7.org/cloud-providers-unite-for-healthcare-interoperability-fhir</ext-link>
          </comment>
        </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>Lehne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Luijten</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vom Felde Genannt Imbusch</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Thun</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The use of FHIR in digital health - a review of the scientific literature</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <month>09</month>
          <day>03</day>
          <volume>267</volume>
          <fpage>52</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI190805</pub-id>
          <pub-id pub-id-type="medline">31483254</pub-id>
          <pub-id pub-id-type="pii">SHTI190805</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>Ayaz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pasha</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Alzahrani</surname>
              <given-names>MY</given-names>
            </name>
            <name name-style="western">
              <surname>Budiarto</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Stiawan</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The Fast Health Interoperability Resources (FHIR) standard: systematic literature review of implementations, applications, challenges and opportunities</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>07</month>
          <day>30</day>
          <volume>9</volume>
          <issue>7</issue>
          <fpage>e21929</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/7/e21929/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21929</pub-id>
          <pub-id pub-id-type="medline">34328424</pub-id>
          <pub-id pub-id-type="pii">v9i7e21929</pub-id>
          <pub-id pub-id-type="pmcid">PMC8367140</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>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="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kitchenham</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Budgen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pearl Brereton</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Using mapping studies as the basis for further research – a participant-observer case study</article-title>
          <source>Inf Softw Technol</source>
          <year>2011</year>
          <month>6</month>
          <volume>53</volume>
          <issue>6</issue>
          <fpage>638</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0950584910002272"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.infsof.2010.12.011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Vakkalanka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kuzniarz</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Guidelines for conducting systematic mapping studies in software engineering: an update</article-title>
          <source>Inf Softw Technol</source>
          <year>2015</year>
          <month>08</month>
          <volume>64</volume>
          <fpage>1</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0950584915000646"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.infsof.2015.03.007</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>Brereton</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kitchenham</surname>
              <given-names>BA</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>Khalil</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Lessons from applying the systematic literature review process within the software engineering domain</article-title>
          <source>J Syst Softw</source>
          <year>2007</year>
          <month>04</month>
          <volume>80</volume>
          <issue>4</issue>
          <fpage>571</fpage>
          <lpage>83</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S016412120600197X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jss.2006.07.009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>Reference management tool</article-title>
          <source>Zotero</source>
          <access-date>2022-12-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.zotero.org/">https://www.zotero.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Boussadi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zapletal</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>A fast healthcare interoperability resources (FHIR) layer implemented over i2b2</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2017</year>
          <month>08</month>
          <day>14</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>120</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-017-0513-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-017-0513-6</pub-id>
          <pub-id pub-id-type="medline">28806953</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-017-0513-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC5557515</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zampognaro</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Paragliola</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Falanga</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>A FHIR based architecture of a multiprotocol IoT home gateway supporting dynamic plug of new devices within instrumented environments</article-title>
          <source>Proceedings of the 2021 IEEE Symposium on Computers and Communications</source>
          <year>2021</year>
          <conf-name>ISCC '21</conf-name>
          <conf-date>September 5-8, 2021</conf-date>
          <conf-loc>Athens, Greece</conf-loc>
          <fpage>1</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9631446"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/iscc53001.2021.9631446</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kilintzis</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Kosvyra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Beredimas</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Natsiavas</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Maglaveras</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Chouvarda</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>A sustainable HL7 FHIR based ontology for PHR data*</article-title>
          <source>Proceedings of the 41st Annual International Conference of the IEEE Engineering in Medicine and Biology Society</source>
          <year>2019</year>
          <conf-name>EMBC '19</conf-name>
          <conf-date>July 23-27, 2019</conf-date>
          <conf-loc>Berlin, Germany</conf-loc>
          <fpage>5700</fpage>
          <lpage>03</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/8856415/similar"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/embc.2019.8856415</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goeg</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Hummeluhr</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Ugon</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Karlsson</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>GO</given-names>
            </name>
            <name name-style="western">
              <surname>Moen</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>An empirical approach to enhancing terminology binding - an HL7 FHIR SNOMED CT example</article-title>
          <source>Building Continents of Knowledge in Oceans of Data: The Future of Co-Created Ehealth</source>
          <year>2018</year>
          <publisher-loc>Amsterdam, The Netherlands</publisher-loc>
          <publisher-name>IOS Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Banach</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ulrich</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kroll</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kiel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ingenerf</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kock-Schoppenhauer</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>APERITIF - automatic patient recruiting for clinical trials based on HL7 FHIR</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <month>05</month>
          <day>27</day>
          <volume>281</volume>
          <fpage>58</fpage>
          <lpage>62</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210120</pub-id>
          <pub-id pub-id-type="medline">34042705</pub-id>
          <pub-id pub-id-type="pii">SHTI210120</pub-id>
        </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>Daumke</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Heitmann</surname>
              <given-names>KU</given-names>
            </name>
            <name name-style="western">
              <surname>Heckmann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Martínez-Costa</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Schulz</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Clinical text mining on FHIR</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <month>08</month>
          <day>21</day>
          <volume>264</volume>
          <fpage>83</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI190188</pub-id>
          <pub-id pub-id-type="medline">31437890</pub-id>
          <pub-id pub-id-type="pii">SHTI190188</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zampognaro</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Paragliola</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Falanga</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Definition of an FHIR-based multiprotocol IoT home gateway to support the dynamic plug of new devices within instrumented environments</article-title>
          <source>J Reliable Intell Environ</source>
          <year>2021</year>
          <month>12</month>
          <day>07</day>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>319</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/article/10.1007/s40860-021-00161-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40860-021-00161-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tsuji</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kingsbury</surname>
              <given-names>PR</given-names>
            </name>
            <name name-style="western">
              <surname>Rasmussen</surname>
              <given-names>LV</given-names>
            </name>
            <name name-style="western">
              <surname>Pacheco</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Adekkanattu</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Pathak</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Developing a FHIR-based EHR phenotyping framework: a case study for identification of patients with obesity and multiple comorbidities from discharge summaries</article-title>
          <source>J Biomed Inform</source>
          <year>2019</year>
          <month>11</month>
          <volume>99</volume>
          <fpage>103310</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(19)30229-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2019.103310</pub-id>
          <pub-id pub-id-type="medline">31622801</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(19)30229-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC6990976</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shivers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Amlung</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ratanaprayul</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rhodes</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Biondich</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Enhancing narrative clinical guidance with computer-readable artifacts: authoring FHIR implementation guides based on WHO recommendations</article-title>
          <source>J Biomed Inform</source>
          <year>2021</year>
          <month>10</month>
          <volume>122</volume>
          <fpage>103891</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(21)00220-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2021.103891</pub-id>
          <pub-id pub-id-type="medline">34450285</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(21)00220-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC8524423</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>Metke-Jimenez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lawley</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hansen</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>FHIR OWL: transforming OWL ontologies into FHIR terminology resources</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2019</year>
          <volume>2019</volume>
          <fpage>664</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32308861"/>
          </comment>
          <pub-id pub-id-type="medline">32308861</pub-id>
          <pub-id pub-id-type="pmcid">PMC7153051</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metke-Jimenez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hansen</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>FHIRCap: transforming REDCap forms into FHIR resources</article-title>
          <source>AMIA Jt Summits Transl Sci Proc</source>
          <year>2019</year>
          <volume>2019</volume>
          <fpage>54</fpage>
          <lpage>63</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31258956"/>
          </comment>
          <pub-id pub-id-type="medline">31258956</pub-id>
          <pub-id pub-id-type="pmcid">PMC6568121</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arguello-Casteleiro</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez-Costa</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Des-Diz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Maroto</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Fernandez-Prieto</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Stevens</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>From SNOMED CT expressions to an FHIR RDF representation: exploring the benefits of an ontology-based approach</article-title>
          <source>Proceedings of the Joint Ontology Workshops 2019 Episode V: The Styrian Autumn of Ontology</source>
          <year>2019</year>
          <conf-name>CEUR '19</conf-name>
          <conf-date>September 23-25, 2019</conf-date>
          <conf-loc>Graz, Austria</conf-loc>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ceur-ws.org/Vol-2518/paper-ODLS1.pdf"/>
          </comment>
        </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>Paris</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mendis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Daniel</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tannier</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zweigenbaum</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>i2b2 implemented over SMART-on-FHIR</article-title>
          <source>AMIA Jt Summits Transl Sci Proc</source>
          <year>2018</year>
          <volume>2017</volume>
          <fpage>369</fpage>
          <lpage>78</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29888095"/>
          </comment>
          <pub-id pub-id-type="medline">29888095</pub-id>
          <pub-id pub-id-type="pmcid">PMC5961782</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>Hong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sohn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Integrating structured and unstructured EHR data using an FHIR-based type system: a case study with medication data</article-title>
          <source>AMIA Jt Summits Transl Sci Proc</source>
          <year>2018</year>
          <volume>2017</volume>
          <fpage>74</fpage>
          <lpage>83</lpage>
          <pub-id pub-id-type="medline">29888045</pub-id>
          <pub-id pub-id-type="pmcid">PMC5961797</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>Lenivtseva</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kopanitsa</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Investigation of Content Overlap in Proprietary Medical Mappings</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <volume>258</volume>
          <fpage>41</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="medline">30942710</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>Matney</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Heale</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hasley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Decker</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Frederiksen</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Langford</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ramey</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Huff</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Lessons learned in creating interoperable fast healthcare interoperability resources profiles for large-scale public health programs</article-title>
          <source>Appl Clin Inform</source>
          <year>2019</year>
          <month>01</month>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>87</fpage>
          <lpage>95</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30727002"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0038-1677527</pub-id>
          <pub-id pub-id-type="medline">30727002</pub-id>
          <pub-id pub-id-type="pmcid">PMC6365290</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>Rajput</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Drenkhahn</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Perspectives and obstacles for transforming terminologies into FHIR CodeSystems exemplified by Alpha-ID</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <month>05</month>
          <day>27</day>
          <volume>281</volume>
          <fpage>213</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210151</pub-id>
          <pub-id pub-id-type="medline">34042736</pub-id>
          <pub-id pub-id-type="pii">SHTI210151</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>Wiedekopf</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Drenkhahn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ulrich</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kock-Schoppenhauer</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Ingenerf</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Providing ART-DECOR valuesets via FHIR terminology servers - a technical report</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <month>09</month>
          <day>21</day>
          <volume>283</volume>
          <fpage>127</fpage>
          <lpage>35</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210550</pub-id>
          <pub-id pub-id-type="medline">34545828</pub-id>
          <pub-id pub-id-type="pii">SHTI210550</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saripalle</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Representing UMLS knowledge using FHIR terminological resources</article-title>
          <source>Proceedings of the 2019 IEEE International Conference on Bioinformatics and Biomedicine</source>
          <year>2019</year>
          <conf-name>BIBM '19</conf-name>
          <conf-date>November 18-21, 2019</conf-date>
          <conf-loc>San Diego, CA</conf-loc>
          <fpage>1109</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/8983305"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/bibm47256.2019.8983305</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gazzarata</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Maggi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Magnoni</surname>
              <given-names>LD</given-names>
            </name>
            <name name-style="western">
              <surname>Monteverde</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Ruggiero</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Giacomini</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Gazzarata</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Maggi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Magnoni</surname>
              <given-names>LD</given-names>
            </name>
            <name name-style="western">
              <surname>Monteverde</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Ruggiero</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Giacomini</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Semantics management for a regional health information system in Italy by CTS2 and FHIR</article-title>
          <source>Studies in Health Technology and Informatics</source>
          <year>2021</year>
          <publisher-loc>Amsterdam, The Netherlands</publisher-loc>
          <publisher-name>IOS Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rajput</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Gronke</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Johannis</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Semi-automated approach to validate and enrich LOINC codes by FHIR server</article-title>
          <source>Proceedings of the 5th International Conference on Medical and Health Informatics</source>
          <year>2021</year>
          <conf-name>ICMHI '21</conf-name>
          <conf-date>May 14-16, 2021</conf-date>
          <conf-loc>Kyoto, Japan</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/10.1145/3472813.3473207"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/3472813.3473207</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>Wagholikar</surname>
              <given-names>KB</given-names>
            </name>
            <name name-style="western">
              <surname>Mandel</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Klann</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Wattanasin</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mendis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chute</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Mandl</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>SN</given-names>
            </name>
          </person-group>
          <article-title>SMART-on-FHIR implemented over i2b2</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>03</month>
          <day>01</day>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>398</fpage>
          <lpage>402</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27274012"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw079</pub-id>
          <pub-id pub-id-type="medline">27274012</pub-id>
          <pub-id pub-id-type="pii">ocw079</pub-id>
          <pub-id pub-id-type="pmcid">PMC5391721</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>Leroux</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Metke-Jimenez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lawley</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Towards achieving semantic interoperability of clinical study data with FHIR</article-title>
          <source>J Biomed Semantics</source>
          <year>2017</year>
          <month>09</month>
          <day>19</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>41</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jbiomedsem.biomedcentral.com/articles/10.1186/s13326-017-0148-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13326-017-0148-7</pub-id>
          <pub-id pub-id-type="medline">28927443</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13326-017-0148-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC5606031</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>Kopanitsa</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Taranik</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Using semi-automated approach for mapping local Russian laboratory terms to LOINC</article-title>
          <source>Proceedings of the 21st International Conference on Information and Software Technologies</source>
          <year>2015</year>
          <conf-name>ICIST '15</conf-name>
          <conf-date>October 15-16, 2015</conf-date>
          <conf-loc>Druskininkai, Lithuania</conf-loc>
          <fpage>37</fpage>
          <lpage>44</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-319-24770-0_4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-319-24770-0_4</pub-id>
        </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>Peterson</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A corpus-driven standardization framework for encoding clinical problems with HL7 FHIR</article-title>
          <source>J Biomed Inform</source>
          <year>2020</year>
          <month>10</month>
          <volume>110</volume>
          <fpage>103541</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(20)30169-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2020.103541</pub-id>
          <pub-id pub-id-type="medline">32814201</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(20)30169-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7701983</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maga-Nteve</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kontopoulos</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Tsolakis</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Katakis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Mathioudis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mitzias</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Avgerinakis</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Meditskos</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Karakostas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vrochidis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kompatsiaris</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>A semantic technologies toolkit for bridging early diagnosis and treatment in brain diseases: report from the ongoing EU-funded research project ALAMEDA</article-title>
          <source>Proceedings of the 15th International Conference on Metadata and Semantic Research</source>
          <year>2021</year>
          <conf-name>MTSR '21</conf-name>
          <conf-date>November 29-December 3, 2021</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <fpage>349</fpage>
          <lpage>54</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-030-98876-0_30"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-030-98876-0_30</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>Rafee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Riepenhausen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Neuhaus</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Meidt</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dugas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Varghese</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>ELaPro, a LOINC-mapped core dataset for top laboratory procedures of eligibility screening for clinical trials</article-title>
          <source>BMC Med Res Methodol</source>
          <year>2022</year>
          <month>05</month>
          <day>14</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>141</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/s12874-022-01611-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12874-022-01611-y</pub-id>
          <pub-id pub-id-type="medline">35568796</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12874-022-01611-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC9107639</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pahari</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Prinz</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>HL7 FHIR with SNOMED-CT to achieve semantic and structural interoperability in personal health data: a proof-of-concept study</article-title>
          <source>Sensors (Basel)</source>
          <year>2022</year>
          <month>05</month>
          <day>15</day>
          <volume>22</volume>
          <issue>10</issue>
          <fpage>3756</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s22103756"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s22103756</pub-id>
          <pub-id pub-id-type="medline">35632165</pub-id>
          <pub-id pub-id-type="pii">s22103756</pub-id>
          <pub-id pub-id-type="pmcid">PMC9147872</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Odigie</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lacson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Raja</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Osterbur</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ip</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Schneider</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Khorasani</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Fast healthcare interoperability resources, clinical quality language, and systematized nomenclature of medicine-clinical terms in representing clinical evidence logic statements for the use of imaging procedures: descriptive study</article-title>
          <source>JMIR Med Inform</source>
          <year>2019</year>
          <month>05</month>
          <day>13</day>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>e13590</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2019/2/e13590/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13590</pub-id>
          <pub-id pub-id-type="medline">31094359</pub-id>
          <pub-id pub-id-type="pii">v7i2e13590</pub-id>
          <pub-id pub-id-type="pmcid">PMC6535979</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ulrich</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kock</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Duhm-Harbeck</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Habermann</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Ingenerf</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Metadata repository for improved data sharing and reuse based on HL7 FHIR</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2016</year>
          <volume>228</volume>
          <fpage>162</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="medline">27577363</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mathews</surname>
              <given-names>WC</given-names>
            </name>
            <name name-style="western">
              <surname>Pham</surname>
              <given-names>HA</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Opioid2FHIR: a system for extracting FHIR-compatible opioid prescriptions from clinical text</article-title>
          <source>Proceedings of the 2020 IEEE International Conference on Bioinformatics and Biomedicine</source>
          <year>2020</year>
          <conf-name>BIBM '20</conf-name>
          <conf-date>December 16-19, 2020</conf-date>
          <conf-loc>Seoul, Korea</conf-loc>
          <fpage>1748</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9313258"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/bibm49941.2020.9313258</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Seveso</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Campagner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ciucci</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Cabitza</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Ordinal labels in machine learning: a user-centered approach to improve data validity in medical settings</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2020</year>
          <month>08</month>
          <day>20</day>
          <volume>20</volume>
          <issue>Suppl 5</issue>
          <fpage>142</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-020-01152-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-020-01152-8</pub-id>
          <pub-id pub-id-type="medline">32819345</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-020-01152-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC7439656</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wiedekopf</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Drenkhahn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenau</surname>
              <given-names>L</given-names>
            </name>
            <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>Ingenerf</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>TerminoDiff - detecting semantic differences in HL7 FHIR CodeSystems</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <month>05</month>
          <day>25</day>
          <volume>294</volume>
          <fpage>362</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI220475</pub-id>
          <pub-id pub-id-type="medline">35612097</pub-id>
          <pub-id pub-id-type="pii">SHTI220475</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Diomaiuta</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sicuranza</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ciampi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>De Pietro</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>A FHIR-based system for the generation and retrieval of clinical documents</article-title>
          <source>Proceedings of the 3rd International Conference on Information and Communication Technologies for Ageing Well and e-Health</source>
          <year>2017</year>
          <conf-name>ICT4AWE '17</conf-name>
          <conf-date>April 28-29, 2017</conf-date>
          <conf-loc>Porto, Portugal</conf-loc>
          <fpage>135</fpage>
          <lpage>42</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scitepress.org/Link.aspx?doi=10.5220/0006311301350142"/>
          </comment>
          <pub-id pub-id-type="doi">10.5220/0006311301350142</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gaudet-Blavignac</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Raisaro</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Touré</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Österle</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Crameri</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lovis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A national, semantic-driven, three-pillar strategy to enable health data secondary usage interoperability for research within the Swiss personalized health network: methodological study</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>06</month>
          <day>24</day>
          <volume>9</volume>
          <issue>6</issue>
          <fpage>e27591</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/6/e27591/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/27591</pub-id>
          <pub-id pub-id-type="medline">34185008</pub-id>
          <pub-id pub-id-type="pii">v9i6e27591</pub-id>
          <pub-id pub-id-type="pmcid">PMC8277320</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dolin</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Boxwala</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shalaby</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A pharmacogenomics clinical decision support service based on FHIR and CDS hooks</article-title>
          <source>Methods Inf Med</source>
          <year>2018</year>
          <month>12</month>
          <volume>57</volume>
          <issue>S 02</issue>
          <fpage>e115</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0038-1676466"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0038-1676466</pub-id>
          <pub-id pub-id-type="medline">30605914</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saripalle</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sookhak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Haghparast</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>An interoperable UMLS terminology service using FHIR</article-title>
          <source>Future Internet</source>
          <year>2020</year>
          <month>11</month>
          <day>16</day>
          <volume>12</volume>
          <issue>11</issue>
          <fpage>199</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/1999-5903/12/11/199"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/fi12110199</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Semenov</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kopanitsa</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Denisov</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Alexandr</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Osenev</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Andreychuk</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Patients decision aid system based on FHIR profiles</article-title>
          <source>J Med Syst</source>
          <year>2018</year>
          <month>07</month>
          <day>31</day>
          <volume>42</volume>
          <issue>9</issue>
          <fpage>166</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-018-1016-4</pub-id>
          <pub-id pub-id-type="medline">30066031</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-018-1016-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kiefer</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Rasmussen</surname>
              <given-names>LV</given-names>
            </name>
            <name name-style="western">
              <surname>Solbrig</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Mo</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Pacheco</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Montague</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>WK</given-names>
            </name>
            <name name-style="western">
              <surname>Denny</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Chute</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Pathak</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Developing a data element repository to support EHR-driven phenotype algorithm authoring and execution</article-title>
          <source>J Biomed Inform</source>
          <year>2016</year>
          <month>08</month>
          <volume>62</volume>
          <fpage>232</fpage>
          <lpage>42</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(16)30062-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2016.07.008</pub-id>
          <pub-id pub-id-type="medline">27392645</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(16)30062-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC5490836</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rosenau</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Majeed</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>Ingenerf</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kiel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kroll</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Köhler</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Prokosch</surname>
              <given-names>HU</given-names>
            </name>
            <name name-style="western">
              <surname>Gruendner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Generation of a fast healthcare interoperability resources (FHIR)-based ontology for federated feasibility queries in the context of COVID-19: feasibility study</article-title>
          <source>JMIR Med Inform</source>
          <year>2022</year>
          <month>04</month>
          <day>27</day>
          <volume>10</volume>
          <issue>4</issue>
          <fpage>e35789</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2022/4/e35789/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/35789</pub-id>
          <pub-id pub-id-type="medline">35380548</pub-id>
          <pub-id pub-id-type="pii">v10i4e35789</pub-id>
          <pub-id pub-id-type="pmcid">PMC9049646</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metke-Jimenez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Steel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hansen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lawley</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Ontoserver: a syndicated terminology server</article-title>
          <source>J Biomed Semantics</source>
          <year>2018</year>
          <month>09</month>
          <day>17</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>24</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jbiomedsem.biomedcentral.com/articles/10.1186/s13326-018-0191-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13326-018-0191-z</pub-id>
          <pub-id pub-id-type="medline">30223897</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13326-018-0191-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC6142703</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kober</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Paschke</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A FHIR-to-RDF converter</article-title>
          <source>Proceeding of the 12th International Conference on Semantic Web Applications and Tools for Health Care and Life Sciences</source>
          <year>2019</year>
          <conf-name>SWAT4HCLS '19</conf-name>
          <conf-date>December 11-12, 2019</conf-date>
          <conf-loc>Edinburgh, UK</conf-loc>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ceur-ws.org/Vol-2849/paper-03.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dridi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sassi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chbeir</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Faiz</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A flexible semantic integration framework for fully-integrated EHR based on FHIR standard</article-title>
          <source>Proceedings of the 12th International Conference on Agents and Artificial Intelligence</source>
          <year>2020</year>
          <conf-name>ICAART '20</conf-name>
          <conf-date>February 22-24, 2020</conf-date>
          <conf-loc>Valletta, Malta</conf-loc>
          <fpage>684</fpage>
          <lpage>91</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scitepress.org/Papers/2020/89815/89815.pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.5220/0008981506840691</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kilintzis</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Alexandropoulos</surname>
              <given-names>VC</given-names>
            </name>
            <name name-style="western">
              <surname>Beredimas</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Delgado</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Benis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>de Toledo</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gallos</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Giacomini</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Martínez-García</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Salvi</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A methodology for an auto-generated and auto-maintained HL7 FHIR OWL ontology for health data management</article-title>
          <source>Studies in Health Technology and Informatics</source>
          <year>2021</year>
          <publisher-loc>Amsterdam, The Netherlands</publisher-loc>
          <publisher-name>IOS Press</publisher-name>
          <fpage>99</fpage>
          <lpage>103</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beredimas</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kilintzis</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Chouvarda</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Maglaveras</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>A reusable ontology for primitive and complex HL7 FHIR data types</article-title>
          <source>Annu Int Conf IEEE Eng Med Biol Soc</source>
          <year>2015</year>
          <volume>2015</volume>
          <fpage>2547</fpage>
          <lpage>50</lpage>
          <pub-id pub-id-type="doi">10.1109/EMBC.2015.7318911</pub-id>
          <pub-id pub-id-type="medline">26736811</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>Kiourtis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mavrogiorgou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kyriazis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A semantic similarity evaluation for healthcare ontologies matching to HL7 FHIR resources</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2020</year>
          <month>06</month>
          <day>16</day>
          <volume>270</volume>
          <fpage>13</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI200113</pub-id>
          <pub-id pub-id-type="medline">32570337</pub-id>
          <pub-id pub-id-type="pii">SHTI200113</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>Kiourtis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nifakos</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mavrogiorgou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kyriazis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Aggregating the syntactic and semantic similarity of healthcare data towards their transformation to HL7 FHIR through ontology matching</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>12</month>
          <volume>132</volume>
          <fpage>104002</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.104002</pub-id>
          <pub-id pub-id-type="medline">31629311</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30937-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kober</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Annotating FHIR-RDF-graphs with medication knowledge</article-title>
          <source>Proceedings of the Workshop on Automation Experience across Domains, AutomationXP 2020, co-located with the ACM Conference on Human Factors in Computing Systems</source>
          <year>2020</year>
          <conf-name>CEUR '20</conf-name>
          <conf-date>April 26, 2020</conf-date>
          <conf-loc>Honolulu, HI</conf-loc>
          <fpage>1</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ceur-ws.org/Vol-2759/paper5.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kwon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jun</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Pyo</surname>
              <given-names>CS</given-names>
            </name>
          </person-group>
          <article-title>Automatic stroke medical ontology augmentation with standard medical terminology and unstructured textual medical knowledge</article-title>
          <source>Proceedings of the 2021 International Conference on Platform Technology and Service</source>
          <year>2021</year>
          <conf-name>PlatCon '21</conf-name>
          <conf-date>August 23-25, 2021</conf-date>
          <conf-loc>Jeju, Korea</conf-loc>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9680753"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/platcon53246.2021.9680753</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Samavi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglou</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>COC: an ontology for capturing semantics of circle of care</article-title>
          <source>Procedia Comput Sci</source>
          <year>2015</year>
          <volume>63</volume>
          <fpage>589</fpage>
          <lpage>94</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S1877050915025247"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.procs.2015.08.389</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>PrudHommeaux</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Solbrig</surname>
              <given-names>HR</given-names>
            </name>
          </person-group>
          <article-title>Developing a semantic web-based framework for executing the clinical quality language using FHIR</article-title>
          <source>Proceedings of the 10th International Conference on Semantic Web Applications and Tools for Health Care and Life Sciences</source>
          <year>2020</year>
          <conf-name>SWAT4LS '17</conf-name>
          <conf-date>December 4-7, 2017</conf-date>
          <conf-loc>Rome, Italy</conf-loc>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ceur-ws.org/Vol-2042/paper40.pdf"/>
          </comment>
        </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>Prud'hommeaux</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Peterson</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Solbrig</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Development of a FHIR RDF data transformation and validation framework and its evaluation</article-title>
          <source>J Biomed Inform</source>
          <year>2021</year>
          <month>05</month>
          <volume>117</volume>
          <fpage>103755</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(21)00084-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2021.103755</pub-id>
          <pub-id pub-id-type="medline">33781919</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(21)00084-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC8131260</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Prud'Hommeaux</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Peterson</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Solbrig</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Implementing a new FHIR RDF specification for semantic clinical data using a JSONLD- based approach</article-title>
          <source>Proceedings of the 13th International Conference on Semantic Web Applications and Tools for Health Care and Life Sciences</source>
          <year>2022</year>
          <conf-name>SWAT4HCLS '22</conf-name>
          <conf-date>January 10-14, 2022</conf-date>
          <conf-loc>Leiden, The Netherlands</conf-loc>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ceur-ws.org/Vol-3127/paper-10.pdf"/>
          </comment>
        </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>Zong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ngo</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Leveraging genetic reports and electronic health records for the prediction of primary cancers: algorithm development and validation study</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>05</month>
          <day>25</day>
          <volume>9</volume>
          <issue>5</issue>
          <fpage>e23586</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/5/e23586/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23586</pub-id>
          <pub-id pub-id-type="medline">34032581</pub-id>
          <pub-id pub-id-type="pii">v9i5e23586</pub-id>
          <pub-id pub-id-type="pmcid">PMC8188315</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kober</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Paschke</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Medical information-graphs, based on ontologies and FHIR</article-title>
          <source>Proceedings of the 2021 Conference on Digital Curation Technologies</source>
          <year>2021</year>
          <conf-name>Qurator '21</conf-name>
          <conf-date>February 8-12, 2021</conf-date>
          <conf-loc>Berlin, Germany</conf-loc>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ceur-ws.org/Vol-2836/qurator2021_paper_14.pdf"/>
          </comment>
        </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>Kober</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Robaldo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Paschke</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Modeling medical guidelines by Prova and SHACL accessing FHIR/RDF. Use case: the medical ABCDE approach</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <month>05</month>
          <day>16</day>
          <volume>293</volume>
          <fpage>59</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI220348</pub-id>
          <pub-id pub-id-type="medline">35592961</pub-id>
          <pub-id pub-id-type="pii">SHTI220348</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luz</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Nogueira</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Cavalini</surname>
              <given-names>LT</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>TW</given-names>
            </name>
          </person-group>
          <article-title>Providing full semantic interoperability for the fast healthcare interoperability resources schemas with resource description framework</article-title>
          <source>Proceedings of the 2015 International Conference on Healthcare Informatics</source>
          <year>2015</year>
          <conf-name>ICHI '15</conf-name>
          <conf-date>2015</conf-date>
          <conf-loc>Dallas, TX</conf-loc>
          <fpage>463</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/7349736"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/ichi.2015.74</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Szmeja</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Prud’hommeaux</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>ShExMap and IPSM-AF: comparison of RDF transformation technologies</article-title>
          <source>Proceedings of the 6th International Conference on Intelligent Systems, Technologies and Applications</source>
          <year>2021</year>
          <conf-name>ISTA '21</conf-name>
          <conf-date>June 15-17, 2021</conf-date>
          <conf-loc>Chennai, India</conf-loc>
          <fpage>29</fpage>
          <lpage>45</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-981-16-0730-1_3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-981-16-0730-1_3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thornton</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Solbrig</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Stupp</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Gayo</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Mietchen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Prud’hommeaux</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Waagmeester</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Using shape expressions (ShEx) to share RDF data models and to guide curation with rigorous validation</article-title>
          <source>Proceedings of the 16th International Conference on the Semantic Web</source>
          <year>2019</year>
          <conf-name>ESWC '19</conf-name>
          <conf-date>June 2-6, 2019</conf-date>
          <conf-loc>Portorož, Slovenia</conf-loc>
          <fpage>606</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-030-21348-0_39"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-030-21348-0_39</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>De</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yue</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Analyzing patient secure messages using a fast health care interoperability resources (FIHR)-based data model: development and topic modeling study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>07</month>
          <day>30</day>
          <volume>23</volume>
          <issue>7</issue>
          <fpage>e26770</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/7/e26770/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/26770</pub-id>
          <pub-id pub-id-type="medline">34328444</pub-id>
          <pub-id pub-id-type="pii">v23i7e26770</pub-id>
          <pub-id pub-id-type="pmcid">PMC8367168</pub-id>
        </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>Hong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mojarad</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Sohn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Standardizing heterogeneous annotation corpora using HL7 FHIR for facilitating their reuse and integration in clinical NLP</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2018</year>
          <volume>2018</volume>
          <fpage>574</fpage>
          <lpage>83</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30815098"/>
          </comment>
          <pub-id pub-id-type="medline">30815098</pub-id>
          <pub-id pub-id-type="pmcid">PMC6371380</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>Soni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gudala</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>DZ</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Using FHIR to construct a corpus of clinical questions annotated with logical forms and answers</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2019</year>
          <volume>2019</volume>
          <fpage>1207</fpage>
          <lpage>15</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32308918"/>
          </comment>
          <pub-id pub-id-type="medline">32308918</pub-id>
          <pub-id pub-id-type="pmcid">PMC7153115</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>Aberdeen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bayer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Keybl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tresner-Kirsch</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>An annotation and modeling schema for prescription regimens</article-title>
          <source>J Biomed Semantics</source>
          <year>2019</year>
          <month>05</month>
          <day>31</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>10</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jbiomedsem.biomedcentral.com/articles/10.1186/s13326-019-0201-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13326-019-0201-9</pub-id>
          <pub-id pub-id-type="medline">31151407</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13326-019-0201-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC6544933</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>Hong</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Davoudi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mowery</surname>
              <given-names>DL</given-names>
            </name>
          </person-group>
          <article-title>Annotation and extraction of age and temporally-related events from clinical histories</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2020</year>
          <month>12</month>
          <day>30</day>
          <volume>20</volume>
          <issue>Suppl 11</issue>
          <fpage>338</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-020-01333-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-020-01333-5</pub-id>
          <pub-id pub-id-type="medline">33380319</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-020-01333-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7772895</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>Ciampi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sicuranza</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Silvestri</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A privacy-preserving and standard-based architecture for secondary use of clinical data</article-title>
          <source>Information</source>
          <year>2022</year>
          <month>02</month>
          <day>13</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>87</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/2078-2489/13/2/87"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/info13020087</pub-id>
        </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>Wu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Toti</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Morley</surname>
              <given-names>KI</given-names>
            </name>
            <name name-style="western">
              <surname>Ibrahim</surname>
              <given-names>ZM</given-names>
            </name>
            <name name-style="western">
              <surname>Folarin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kartoglu</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Agrawal</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stringer</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gale</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gorrell</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Broadbent</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dobson</surname>
              <given-names>RJ</given-names>
            </name>
          </person-group>
          <article-title>SemEHR: a general-purpose semantic search system to surface semantic data from clinical notes for tailored care, trial recruitment, and clinical research</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>05</month>
          <day>01</day>
          <volume>25</volume>
          <issue>5</issue>
          <fpage>530</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29361077"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocx160</pub-id>
          <pub-id pub-id-type="medline">29361077</pub-id>
          <pub-id pub-id-type="pii">4817428</pub-id>
          <pub-id pub-id-type="pmcid">PMC6019046</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lenivtceva</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Slasten</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kashina</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kopanitsa</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Applicability of machine learning methods to multi-label medical text classification</article-title>
          <source>Proceedings of the 20th International Conference on Computational Science</source>
          <year>2020</year>
          <conf-name>ICCS '20</conf-name>
          <conf-date>June 3-5, 2020</conf-date>
          <conf-loc>Amsterdam, The Netherland</conf-loc>
          <fpage>509</fpage>
          <lpage>22</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-030-50423-6_38#:~:text=Medical%20text%20classification%20task%20facilitates,manually%20labeled%20Russian%20medical%20notes"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-030-50423-6_38</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El-Sappagh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Hendawi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jang</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Kwak</surname>
              <given-names>KS</given-names>
            </name>
          </person-group>
          <article-title>A mobile health monitoring-and-treatment system based on integration of the SSN sensor ontology and the HL7 FHIR standard</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <month>05</month>
          <day>10</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>97</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-019-0806-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-019-0806-z</pub-id>
          <pub-id pub-id-type="medline">31077222</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-019-0806-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC6511155</pub-id>
        </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>Solbrig</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Prud'hommeaux</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Grieve</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>McKenzie</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mandel</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Modeling and validating HL7 FHIR profiles using semantic web shape expressions (ShEx)</article-title>
          <source>J Biomed Inform</source>
          <year>2017</year>
          <month>03</month>
          <volume>67</volume>
          <fpage>90</fpage>
          <lpage>100</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(17)30034-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2017.02.009</pub-id>
          <pub-id pub-id-type="medline">28213144</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(17)30034-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC5502481</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kiourtis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mavrogiorgou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Menychtas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Maglogiannis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kyriazis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Structurally mapping healthcare data to HL7 FHIR through ontology alignment</article-title>
          <source>J Med Syst</source>
          <year>2019</year>
          <month>02</month>
          <day>05</day>
          <volume>43</volume>
          <issue>3</issue>
          <fpage>62</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-019-1183-y</pub-id>
          <pub-id pub-id-type="medline">30721349</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-019-1183-y</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
