<?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">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</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">v11i1e49301</article-id>
      <article-id pub-id-type="pmid">38133917</article-id>
      <article-id pub-id-type="doi">10.2196/49301</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>The Necessity of Interoperability to Uncover the Full Potential of Digital Health Devices</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Cornet</surname>
            <given-names>Ronald</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Pryss</surname>
            <given-names>Ruediger</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Schobel</surname>
            <given-names>Johannes</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Leuchter</surname>
            <given-names>Richard </given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Schwab</surname>
            <given-names>Julian D</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3050-0618</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Werle</surname>
            <given-names>Silke D</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5153-0269</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Hühne</surname>
            <given-names>Rolf</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4592-1519</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Spohn</surname>
            <given-names>Hannah</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-2666-4136</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Kaisers</surname>
            <given-names>Udo X</given-names>
          </name>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3781-0843</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Kestler</surname>
            <given-names>Hans A</given-names>
          </name>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Ulm University</institution>
            <addr-line>Albert-Einstein-Allee 11</addr-line>
            <addr-line>Ulm, 89081</addr-line>
            <country>Germany</country>
            <fax>49 731 50024502</fax>
            <phone>49 731 500 24500</phone>
            <email>hans.kestler@uni-ulm.de</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4759-5254</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Ulm University</institution>
        <addr-line>Ulm</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>University Hospital Ulm</institution>
        <addr-line>Ulm</addr-line>
        <country>Germany</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Hans A Kestler <email>hans.kestler@uni-ulm.de</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>22</day>
        <month>12</month>
        <year>2023</year>
      </pub-date>
      <volume>11</volume>
      <elocation-id>e49301</elocation-id>
      <history>
        <date date-type="received">
          <day>24</day>
          <month>5</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>7</day>
          <month>8</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>27</day>
          <month>9</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>12</day>
          <month>11</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Julian D Schwab, Silke D Werle, Rolf Hühne, Hannah Spohn, Udo X Kaisers, Hans A Kestler. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 22.12.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2023/1/e49301" xlink:type="simple"/>
      <abstract>
        <p>Personalized health care can be optimized by including patient-reported outcomes. Standardized and disease-specific questionnaires have been developed and are routinely used. These patient-reported outcome questionnaires can be simple paper forms given to the patient to fill out with a pen or embedded in digital devices. Regardless of the format used, they provide a snapshot of the patient’s feelings and indicate when therapies need to be adjusted. The advantage of digitizing these questionnaires is that they can be automatically analyzed, and patients can be monitored independently of doctor visits. Although the questions of most clinical patient-reported outcome questionnaires follow defined standards and are evaluated by clinical trials, these standards do not exist for data processing. Interoperable data formats and structures would benefit multilingual and cross-study data exchange. Linking questionnaires to standardized terminologies such as the Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) and Logical Observation Identifiers, Names, and Codes (LOINC) would improve this interoperability. However, linking clinically validated patient-reported outcome questionnaires to clinical terms available in SNOMED CT or LOINC is not as straightforward as it sounds. Here, we report our approach to link patient-reported outcomes from health applications to SNOMED CT or LOINC codes. We highlight current difficulties in this process and outline ways to minimize them.</p>
      </abstract>
      <kwd-group>
        <kwd>semantic terminology</kwd>
        <kwd>semantic</kwd>
        <kwd>terminology</kwd>
        <kwd>terminologies</kwd>
        <kwd>data linkage</kwd>
        <kwd>interoperability</kwd>
        <kwd>data exchange</kwd>
        <kwd>SNOMED CT</kwd>
        <kwd>LOINC</kwd>
        <kwd>eHealth</kwd>
        <kwd>patient-reported outcome questionnaires</kwd>
        <kwd>requirement for standards</kwd>
        <kwd>standard</kwd>
        <kwd>standards</kwd>
        <kwd>PRO</kwd>
        <kwd>PROM</kwd>
        <kwd>patient reported</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The recording of symptoms and laboratory tests is of paramount importance in clinical practice. In addition to objective, measurable parameters, the patient-reported symptoms and their quality of life have come into focus in modern medicine [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. In this context, patient-reported outcome (PRO) questionnaires have become a standard tool to capture patients’ perspectives on their health status. Depending on the underlying disease, PROs cover topics such as quality of life [<xref ref-type="bibr" rid="ref1">1</xref>], adverse events [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>], or stress [<xref ref-type="bibr" rid="ref5">5</xref>], among others. Although in the past, PROs were typically reported using paper-and-pencil methods, electronic PROs (ePROs) are increasingly used and preferred by patients [<xref ref-type="bibr" rid="ref6">6</xref>]. Because physician and patient perceptions of symptoms can be discrepant [<xref ref-type="bibr" rid="ref7">7</xref>], PROs are essential for identifying conditions requiring a therapy adjustment [<xref ref-type="bibr" rid="ref3">3</xref>]. In addition, ePROs can automate their analysis, and they can be used as an outpatient triage tool to identify those in a cohort who need therapy adjustment or closer support [<xref ref-type="bibr" rid="ref8">8</xref>]. PRO questionnaires can be constructed for different topics and can be more general or tailored to specific diseases [<xref ref-type="bibr" rid="ref9">9</xref>]. In addition, questions can have different recall time resolutions (eg, today or last week) or differ in their detailed description of symptoms [<xref ref-type="bibr" rid="ref3">3</xref>]. Thus, the questions and the corresponding answers can be very specific. As a result, minor adjustments in wording can affect the final result [<xref ref-type="bibr" rid="ref9">9</xref>]. The same is valid for alternative translations. To address these issues, the European Organization for Research and Treatment of Cancer (EORTC), among others, has developed standardized quality-of-life PRO questionnaires [<xref ref-type="bibr" rid="ref1">1</xref>]. These questionnaires were initially developed in 1986 and have been refined, translated into several languages, and validated [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Moreover, the consortium provides a detailed analysis plan to enable comparable results between clinical trials regardless of the geographical region or linguistic and cultural population [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      <p>Like the underlying questionnaires, the outgoing ePRO data should be accurate, standardized, and interoperable to enable sharing, reuse, and international data comparison. Unfortunately, what seems obvious at first glance is far from reality [<xref ref-type="bibr" rid="ref12">12</xref>]. The Fast Healthcare Interoperability Resources (FHIR) specification, developed by Health Level Seven International, is the most widely accepted standard for communicating health care data [<xref ref-type="bibr" rid="ref12">12</xref>]. It aims to provide a comprehensive framework and related standards for exchanging, integrating, sharing, and retrieving electronic health information [<xref ref-type="bibr" rid="ref13">13</xref>]. The FHIR elements required for PRO questionnaires are Questionnaire and QuestionnaireResponse. A Questionnaire defines a structured set of questions to guide the collection of answers. In addition to the questions, it also defines the answer types and possible answers. It provides detailed control over order, presentation, phraseology, and grouping for consistent data collection. Each Questionnaire requires a QuestionnaireResponse as its counterpart for retrieving and organizing the answers. The QuestionnaireResponse provides a structured set of answers for a specific Questionnaire and must match the definitions of the Questionnaire. Terminologies are integrated as CodeSystems by providing a base URL and the term code. This combines the syntactic interoperability (structure and data format) enabled by standards such as FHIR with the semantic interoperability enabled by health terminologies. The Systematized Nomenclature of Medical Clinical Terms (SNOMED CT) is currently the most appropriate and comprehensive clinical health terminology with natural language properties [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. It includes terminologies for medical concepts, descriptions, and relationships, forming a unique component with a specific identifier [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>] (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Another common medical terminology is the Logical Observation Identifiers Names and Codes (LOINC) [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. A LOINC term is defined as the combination of the LOINC code, a unique identifier, and the fully specified name (FSN), which consists of 5 to 6 parts, including the component or analyte, the observed property, the time of the measurement, the type of system, and the scale of the measurement. Where relevant, the measurement method is included as part 6 [<xref ref-type="bibr" rid="ref17">17</xref>] (<xref rid="figure2" ref-type="fig">Figure 2</xref>). Although SNOMED CT seems appropriate as a reference terminology for multilingual semantic interoperability in health care [<xref ref-type="bibr" rid="ref18">18</xref>], LOINC has the advantage of also providing “display text” that can be used to link questions (“SURVEY_QUEST_TEXT”) [<xref ref-type="bibr" rid="ref17">17</xref>]. For these reasons, it may be appropriate to supplement SNOMED CT terminology with LOINC, and several approaches for their mapping have been proposed [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      <p>To improve the international reuse and comparison of PROs in clinical trials, we tested the mapping of standardized and validated questionnaires with their corresponding queries to the SNOMED CT and LOINC terminologies. In the following sections, we introduce these PROs, report on our experience mapping them to SNOMED CT and LOINC, highlight current difficulties, and outline some suggestions for minimizing them.</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>Exemplary composition of SNOMED CT components for nausea. SNOMED CT content consists of concepts, descriptions, and relationships. Each concept is associated with a set of textual descriptions. The descriptions can be grouped into an FSN, which is unique, and several accepted synonyms, allowing users to apply their preferred terms. In addition to the preferred FSN, a synonym can be selected by a language refset. Relationships link concepts within hierarchies. The &#124;Is a&#124; relationship connects concepts within the same hierarchy, whereas the attribute relationship connects relationships in different hierarchies such as finding site, procedure site, or method. SNOMED CT: Systematized Nomenclature of Medicine Clinical Terms.</p>
        </caption>
        <graphic xlink:href="medinform_v11i1e49301_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec>
      <title>Patient-Reported Outcome Questionnaires</title>
      <sec>
        <title>Content of Patient-Reported Outcome Questionnaires</title>
        <p>Various questionnaires focus either on the quality of life and its impact on the underlying disease or on disease- or treatment-related adverse events. Recent approaches have identified conceptual differences between these PRO measures (PROMs) [<xref ref-type="bibr" rid="ref21">21</xref>]. On the basis of these findings, we have limited our approach to a few clinically relevant and widely accepted questionnaires that differ in their representation of the domains assessed. Thus, our content analysis included the following PROMs, which can be accessed at</p>
        <list list-type="bullet">
          <list-item>
            <p>EORTC Quality of Life of Cancer Patients Questionnaire (QLQ-C30) [<xref ref-type="bibr" rid="ref22">22</xref>]</p>
          </list-item>
          <list-item>
            <p>EORTC Quality of Life of Breast Cancer Patients Questionnaire (QLQ-BR23) [<xref ref-type="bibr" rid="ref22">22</xref>]</p>
          </list-item>
          <list-item>
            <p>Patient-Reported Outcomes Measurement Information System (PROMIS-29) [<xref ref-type="bibr" rid="ref23">23</xref>]</p>
          </list-item>
          <list-item>
            <p>Common Terminology Criteria for Adverse Events (CTCAE) [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          </list-item>
        </list>
        <p>In the following, we describe the analyzed PROMs in more detail.</p>
      </sec>
      <sec>
        <title>EORTC QLQ-C30</title>
        <p>The EORTC QLQ-C30 is one of the core validated questionnaires of the EORTC Quality of Life Group. It has been optimized in several revisions since its initial release in 1987 and assesses general aspects and symptoms of patients with cancer based on 30 core items [<xref ref-type="bibr" rid="ref1">1</xref>]. As there is a wide range of tumor diseases, the questionnaire is not considered to be too disease specific. Five questions of the QLQ-C30 do not consider a recall time interval, whereas the remaining questions refer to the recall time interval <italic>last week.</italic> Two different value scales are used for the answers. Most of the questions can be answered with the text <italic>not at all</italic>, <italic>a little</italic>, <italic>quite a bit</italic>, and <italic>very much</italic>, combined with the numerical values 1 to 4. The others have only text for the first and last values (<italic>very poor</italic> and <italic>excellent</italic>), and the numerical values range from 1 to 7. To score the QLQ-C30, the questions are divided into groups to assess functional scales, symptom-related scales, and global health status, using the Likert method of summing scales [<xref ref-type="bibr" rid="ref10">10</xref>]. The QLQ-C30 is currently available in version 3.0 and is recommended for use in any new study [<xref ref-type="bibr" rid="ref10">10</xref>]. The QLQ-C30 core questionnaire can be supplemented by modules containing questions about specific tumor sites, symptoms, or treatments [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. All EORTC questionnaires are available in several languages, but the initial version is in English [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Special care has been taken in their development to ensure that they are universally understandable, regardless of the level of education or cultural background. To ensure these quality standards, each questionnaire undergoes several rounds of revision, including testing with patients from several countries [<xref ref-type="bibr" rid="ref26">26</xref>]. The current versions of all EORTC questionnaires and their development status can be requested at the website in [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>EORTC QLQ-BR23</title>
        <p>The EORTC QLQ-BR23 questionnaire is the validated add-on module to the QLQ-C30 core questionnaire for patients with breast cancer. It is recommended for general use, but its updated version (QLQ-BR45) has already completed phase IV testing [<xref ref-type="bibr" rid="ref10">10</xref>], and a new version will soon be available for newly initiated studies. The QLQ-BR23 questionnaire consists of 23 items that address dealing with symptoms, treatment adverse events, body image, sexual functioning, and future outlook [<xref ref-type="bibr" rid="ref10">10</xref>]. Similar to the QLQ-C30, the items of the QLQ-BR23 can be grouped for scoring based on the available scoring scheme [<xref ref-type="bibr" rid="ref10">10</xref>]. This time, however, all questions can be answered with the text <italic>not at all</italic>, <italic>a little</italic>, <italic>quite a bit,</italic> and <italic>very much</italic> combined with the numerical values 1 to 4, and the questions cover a recall time interval of either the last week or the last 4 weeks.</p>
      </sec>
      <sec>
        <title>PROMIS-29</title>
        <p>The PROMIS is an item bank for constructing patient-reported questionnaires in the context of chronic diseases and conditions. It covers the domains of physical, mental, and social health, which are further subdivided into more precise symptom item banks such as physical function (124 items), pain behavior (39 items), or fatigue (95 items), among others, tailored to a broad population of chronic diseases. This allows comparisons between diseases. The system enables exchanging items or minimizing the number of items within a questionnaire without compromising the reliability [<xref ref-type="bibr" rid="ref27">27</xref>].</p>
        <p>Because of the many possible PROMIS questionnaires, we limited our approach to the PROMIS-29 questionnaire available at the website in [<xref ref-type="bibr" rid="ref23">23</xref>]. It contains 29 questions derived from the 7 PROMIS categories of physical function, anxiety, depression, fatigue, sleep disturbance, ability to participate in social roles and activities, and pain interference, each measured by 4 questions. It also includes a numeric pain intensity scale ranging from 0 (no pain) to 10 (worst pain imaginable). In addition to the pain intensity scale, all other items have a 5-point response scale (eg, 1=never, 2=rarely, 3=sometimes, 4=often, and 5=always). Except for the questions on physical function and ability to participate in social roles and activities, where the time interval is not specified, the requested recall period is the past 7 days.</p>
      </sec>
      <sec>
        <title>CTCAE</title>
        <p>The CTCAE is the classic scoring system physicians use to classify side effects during cancer treatment. It is used to grade patient-reported symptoms and those observed by clinicians or from laboratory tests [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. Unlike the EORTC and PROMIS questionnaires, the CTCAE questions were not originally designed in a pen-and-paper format to be given to patients. Therefore, clinicians do not rate each question. It is a descriptive terminology for adverse events coupled with a descriptive grading of the event that occurred [<xref ref-type="bibr" rid="ref24">24</xref>]. The CTCAE presents scores from 1 to 5 with the associated grading (<italic>mild</italic>, <italic>moderate</italic>, <italic>severe</italic>, <italic>life-threatening</italic>, or <italic>dead</italic>). Each grade has a unique textual clinical description to help to assess the correct grading. Because not all adverse events can be classified into 5 classes, some described adverse events have fewer than 5 grades [<xref ref-type="bibr" rid="ref24">24</xref>]. The current CTCAE scoring (version 5.0) and previous versions are available at the website in [<xref ref-type="bibr" rid="ref29">29</xref>]. We have limited our approach to the current CTCAE version 5.0. However, a CTCAE version 6.0 is already in preparation. Following the idea of the CTCAE, the National Cancer Institute (NCI) has developed a Patient-Reported Outcomes Version of the CTCAE (PRO-CTCAE) scoring system. It contains 78 adverse events from the classic CTCAE, which can be queried based on 124 individual questions [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. The PRO-CTCAE scoring system records adverse events according to attributes such as severity (<italic>none</italic>, <italic>mild</italic>, <italic>moderate</italic>, <italic>severe</italic>, <italic>very severe</italic>), frequency (<italic>never</italic>, <italic>rarely</italic>, <italic>occasionally</italic>, <italic>frequently</italic>, <italic>almost constantly</italic>), or interference (<italic>not at all</italic>, <italic>a little bit</italic>, <italic>somewhat</italic>, <italic>quite a bit</italic>, <italic>very much</italic>) and has a general recall time of the last 7 days [<xref ref-type="bibr" rid="ref30">30</xref>]. Thus, it lacks the detailed textual descriptions of the symptoms that occurred. In contrast, the health application NEMO (German, Nebenwirkungs-Management Onkologie) tried to combine PRO questions with the classic CTCAE scoring descriptions for daily use [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>Workflow—Finding SNOMED CT and LOINC Codes for PRO Questionnaires</title>
      <sec>
        <title>Limitations</title>
        <p>SNOMED CT and LOINC are both optimized for health care and laboratory terminologies. Thus, several approaches have been proposed to map SNOMED CT and LOINC codes [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>] due to their close knowledge representation formalisms (see <xref rid="figure1" ref-type="fig">Figures 1</xref> and <xref rid="figure2" ref-type="fig">2</xref>). However, even applying this mapping to data for which both terminologies are specialized resulted in incomplete results and required significant human effort to complete the task [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].</p>
        <p>Therefore, we also manually mapped the questionnaires with their associated questions and response options to assign them SNOMED CT and LOINC codes. The questionnaires analyzed in our study were obtained from [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]. The workflow used is shown in <xref rid="figure3" ref-type="fig">Figure 3</xref> and is described in more detail below. The results of the manual mapping can be found in Tables S1-S4 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <p>We did not consider the relationship between questions and responses in our analyses of term availability. However, we want to inform the reader that the context between questions and possible responses must also be considered and marked in our workflow for actual use cases.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Exemplary composition of a LOINC term for nausea. A LOINC term is defined as the combination of the LOINC code, a unique identifier, and the FSN, which consists of 5-6 parts, including the component or analyte, the observed property, the time of the measurement, the type of system, the scale of the measurement, and sometimes also the method used. The FSN parts are listed sequentially, separated by “:”. “Nausea [Presence]” is one of the additional names, a long common name, which must be unique. LOINC: Logical Observation Identifiers, Names, and Codes.</p>
          </caption>
          <graphic xlink:href="medinform_v11i1e49301_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Workflow. Depicted is our workflow to match patient-reported outcome questionnaires with the standardized terminologies LOINC and SNOMET CT to enable semantic interoperability. The workflow marked in black depicts the procedure to analyze the current status of terms included in both terminologies. If a term still needs to be included, we suggest the blue workflow to extend the terminologies. The empty box indicates the end of the procedure. LOINC: Logical Observation Identifiers, Names, and Codes; SNOMED CT: Systematized Nomenclature of Medicine Clinical Terms.</p>
          </caption>
          <graphic xlink:href="medinform_v11i1e49301_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>LOINC</title>
        <p>After free registration at the website in [<xref ref-type="bibr" rid="ref31">31</xref>], keywords from our PRO questions and possible answers were queried. If only 1 term was found, it was evaluated if it was a “perfect match.” If multiple terms were found, the most appropriate term was selected and considered a perfect match. If this evaluation resulted in a perfect match, the term was chosen as the terminology term. However, if the match was negative or no term was found, the item was treated as “not found.” For example, for the question <italic>Have you felt nauseated?</italic> there was no match, and a search for the term <italic>nausea</italic> alone returned 12 results, which are listed as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>67232-9 &#124; How often did you have nausea in the past 7 days [PhenX]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>64713-1 &#124; In which months of the pregnancy did you have frequent nausea or vomiting [PhnX]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>81660-3 &#124; Nausea [Presence]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>70406-4 &#124; I have nausea in the past 7 days [FACIT]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>77711-0 &#124; Patient has anorexia, nausea or vomiting in the past week [UPDRS]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>42848-2 &#124; Nausea [CCC]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>77510-6 &#124; Can pronounce nausea [AmNART]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>28391-1 &#124; Nausea [HIV-SSC]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>69711-0 &#124; Did you have nausea or an upset stomach, or the feeling that you were going to have diarrhea [Reported.PHQ]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>69682-3 &#124; Bothered by nausea, gas, or indigestion in last 4 weeks [Reported.PHQ]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>67231-1 &#124; How often did you have pain in the center of the upper stomach in the past 7 days [PhenX]</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>96839-6 &#124; Nauseous or had stomach problems when I thought about or was exposed to information about the coronavirus in past 2 weeks</italic>
            </p>
          </list-item>
        </list>
        <p>All of these are not a perfect match to the original question. Therefore, we considered the term not an ideal match.</p>
      </sec>
      <sec>
        <title>SNOMED CT</title>
        <p>To find SNOMED CT components and the corresponding identifier, we used the SNOMED CT Browser [<xref ref-type="bibr" rid="ref32">32</xref>] and entered keywords from our PRO questions and possible answers into the search field.</p>
        <p>Because full text cannot be entered into SNOMED CT, we searched for relevant parts of the question or answer. For example, for the question <italic>Have you felt nauseated?</italic> the search term <italic>nauseated</italic> or <italic>nausea</italic> returned the following result, which we interpret as a perfect match:</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>422587007 &#124; Nausea (finding) &#124;</italic>
            </p>
          </list-item>
        </list>
        <p>Here, we were interested in a general proof of principle of whether PRO questionnaires can be mapped to semantic terminologies. Therefore, we stopped our analysis after querying the PRO questionnaire terms. However, if the goal is to extend the terminologies, we recommend the following alternatives (marked in blue in Figure 3), which we discuss in more detail below.</p>
        <p>In the case of LOINC, the missing term can either be requested to be added by an extension request proposal, or a semantic description of the term can be searched in the SNOMED CT terminology. The specificity of the term description can be further increased by building a postcoordinated expression.</p>
        <p>In the following sections, we report on the challenges of term mapping to semantic terminologies.</p>
      </sec>
    </sec>
    <sec>
      <title>Challenges in Terminology Binding</title>
      <p>Our attempts to complete the exemplary questionnaires’ terminology binding revealed the following challenges.</p>
      <sec>
        <title>Language</title>
        <p>Although the PRO questionnaires are translated into different languages while preserving the original meaning [<xref ref-type="bibr" rid="ref11">11</xref>], the terminology databases SNOMED CT and LOINC are only available for a limited number of languages [<xref ref-type="bibr" rid="ref18">18</xref>]. This is counterproductive to the goal of digitization and medical terminologies to improve interoperability, especially if automatic mapping is the ultimate goal. In addition to the international edition of SNOMED CT, there are currently 18 other country-specific editions that cover, at least in part, 10 additional languages: Danish, Dutch, Estonian, Finnish, French, German, Māori, Norwegian, Spanish, and Swedish [<xref ref-type="bibr" rid="ref32">32</xref>]. However, several European languages are not yet included [<xref ref-type="bibr" rid="ref18">18</xref>]. On the positive side, at least the same identifiers are used for different languages. However, this should be the case to ensure interoperability. LOINC currently has 20 linguistic variants covering 14 additional languages: Chinese, Dutch, Estonian, French, German, Greek, Italian, Korean, Polish, Portuguese, Russian, Spanish, Turkish, and Ukrainian [<xref ref-type="bibr" rid="ref33">33</xref>]. Because of the various language alternatives, we limited our mapping to the English versions of the PRO questionnaires and terminology databases, as has been done by others [<xref ref-type="bibr" rid="ref34">34</xref>]. The language barrier could be reduced by putting more effort into translating the terminologies into more languages. As mentioned above, FHIR, a standard for health data exchange, enables syntactic interoperability [<xref ref-type="bibr" rid="ref13">13</xref>]. To ensure a correct transition to semantic interoperability, mapping validators, such as the open-source FHIR Validator framework [<xref ref-type="bibr" rid="ref35">35</xref>], check whether the exported textual questionnaire and the specified identifier match. If the language of the PRO questionnaire and, thus, the survey text from the FHIR export differs from the language of the associated terminology, the program generates a warning. However, the fact that it only generates a warning may allow existing tools to continue to be used.</p>
      </sec>
      <sec>
        <title>Concept Availability and Term Selection</title>
        <p>The SNOMED CT and LOINC terminologies are comprehensive, but questionnaire questions are often use-case-specific. We limited our approach to searching for general term matches in the terminologies to provide a proof of concept. However, we recognize and want to emphasize that terminology mapping of PRO questionnaires is more than just finding a match for applied use case scenarios. In addition to the term itself, the context must also match. For example, in SNOMED CT, the term <italic>nausea</italic> is a finding that expects a <italic>yes</italic> or <italic>no</italic> response. In contrast, in LOINC, the code <italic>81660-3 &#124; Nausea [Presence]</italic> expects responses such as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>LA137-2 &#124; None</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>LA6752-5 &#124; Mild</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>LA6751-7 &#124; Moderate</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>LA6750-9 &#124; Severe</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>LA9041-0 &#124; Resolved</italic>
            </p>
          </list-item>
        </list>
        <p>Therefore, the question and the response must be addressed in the correct context for a proper representation using encoding systems. This also includes the evaluation of multiple isosemantic representations.</p>
        <p>In addition to the context, precise wording is paramount for PROs [<xref ref-type="bibr" rid="ref25">25</xref>]. Mapping the PROMIS-29 questionnaire to LOINC version 2.71 was relatively straightforward because it has its own LOINC profile (<italic>62337-1 &#124; PROMIS item bank - 29 profile</italic>), including codes for questions and response scores. However, caution is still required. Although the LOINC code for the PROMIS-29 panel has basic attributes, including first released and last updated, these version numbers do not match the version number of the underlying questionnaire. The PROMIS-29 questionnaire is available in versions 1.0, 2.0, and 2.1 [<xref ref-type="bibr" rid="ref36">36</xref>], with changes to the <italic>abilities to participate in social roles and activities</italic> items in versions 2.0 and later. The available LOINC panel, instead, contains only the 1.0 version items. However, the 4 questions that have changed between these versions can also be found in another LOINC panel (<italic>76731-9 &#124; PROMIS short form - ability to participate in social roles and activities 8a - version 2.0</italic>).</p>
        <p>In contrast to LOINC, none of the complete PROMIS-29 statements could be mapped to SNOMED CT identifiers. Sometimes, the requested symptom finding could be matched, but without having the full statement (eg, SNOMED CT code: <italic>307077003 &#124; feeling hopeless (finding)&#124;</italic> for the PROMIS-29 statement <italic>In the past seven days I felt hopeless</italic>). However, not all descriptive symptoms (eg, <italic>In the past seven days I felt worthless</italic>) could be found in SNOMED CT. The best SNOMED CT match for the PROMIS-29 response options was obtained with the following:</p>
        <list list-type="bullet">
          <list-item>
            <p>The parent concept: <italic>1157335009 &#124; Numeric grade on a scale of 1 to 5 (qualifier)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>Its child concept: <italic>1157337001 &#124; Grade 1 on a scale of 1 to 5 (qualifier value)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>Up to its child concept: <italic>1157341002 &#124; Grade 5 on a scale of 1 to 5 (qualifier value)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>The parent concept: <italic>1157336005 &#124; Numeric grade on a scale of 0 to 10 (qualifier value)&#124;</italic></p>
          </list-item>
        </list>
        <p>Another difficulty is that not all answer options in the PROMIS-29 questionnaire are associated with an ascending scale from 1 to 5. Nevertheless, this scale is sometimes reversed, even though the same text has been assigned. This demonstrates the disadvantage of using only numerical scales alone as terminological concepts for PRO comparison. Instead, it is essential to couple the numerical scales with a semantic representation of their meaning.</p>
        <p>For the EORTC QLQ-C30 and QLQ-BR23 questionnaires, finding LOINC terms that semantically matched the questions was difficult. If at all, we could only find phrases formulated as statements that appeared in questions on the EORTC questionnaires, were taken from other questionnaires, and approximated the flow of words. For example, the QLQ-C30 question <italic>Did you need to rest?</italic> has similarities to the LOINC code</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>70815-6 &#124; I need to rest during the day</italic>
            </p>
          </list-item>
        </list>
        <p>from the Functional Assessment of Chronic Illness Therapy (FACIT) Measurement System questionnaire, which is included in LOINC. Sometimes, we also identified multiple LOINC codes that partially matched the searched item from the EORTC questionnaire. For example, the question <italic>Do you have any trouble taking a long walk?</italic> could be matched to the LOINC code</p>
        <list list-type="bullet">
          <list-item>
            <p><italic>61609-4 &#124; Are you able to go for a walk of at least 15 minutes [PROMIS]</italic> or</p>
          </list-item>
          <list-item>
            <p>
              <italic>79006-3 &#124; Are you able to walk more than a mile [PROMIS]</italic>
            </p>
          </list-item>
        </list>
        <p>Overall, we could not match 2 of 30 questions (7%) from the QLQ-C30 questionnaire and 9 of 23 (39%) from the QLQ-BR23 questionnaire. Similar to LOINC, we did not find a single question in the EORTC PROs that exactly matched the SNOMED CT terminology, but we did find at least 1 or more concepts that described the requested symptoms. For example, the QLQ-C30 question <italic>Have you felt nauseated?</italic> could be mapped to the SNOMED CT concept:</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>422587007 &#124; Nausea (finding)&#124;</italic>
            </p>
          </list-item>
        </list>
        <p>Overall, 29 of 30 questions (96%) of the QLQ-C30 and 18 of 23 (78%) of the QLQ-BR23 could be mapped to SNOMED CT terminologies. However, finding appropriate terminologies for response options in SNOMED CT and LOINC has been difficult. The EORTC Quality of Life Group explicitly states that the coupling of textual descriptions and numerical scores is paramount for using their PRO questionnaire concepts [<xref ref-type="bibr" rid="ref25">25</xref>]. Thus, the simple use of numerical scales such as</p>
        <list list-type="bullet">
          <list-item>
            <p><italic>1157272001 &#124; Numeric grade on a scale of 1 to 4 (qualifier value)&#124;</italic> or</p>
          </list-item>
        </list>
        <p>general adjectival modifiers such as</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>89292003 &#124; Rare (qualifier value)&#124;</italic>
            </p>
          </list-item>
        </list>
        <p>would not be sufficient to match the response options. Although the LOINC terminology includes response list codes that include textual descriptions and numerical scores (eg, <italic>LL5215-0</italic>), we could not find a list that correctly matched all scores and associated text.</p>
        <p>Adverse events associated with CTCAE-scored drugs have been reported using terminologies such as the Medical Dictionary for Regulatory Activities (MedDRA) [<xref ref-type="bibr" rid="ref37">37</xref>]. Thus, the CTCAE scoring incorporates certain elements of the MedDRA terminology [<xref ref-type="bibr" rid="ref24">24</xref>]. In general, there is a mapping between MedDRA and SNOMED CT [<xref ref-type="bibr" rid="ref37">37</xref>], which can also be used for our purposes. However, this mapping is not freely available. A manual test to find corresponding SNOMED CT identifiers for the first 50 CTCAE terms resulted in 6 missing terms. For the CTCAE response options, the parent concept and its child concepts exist in SNOMED CT:</p>
        <list list-type="bullet">
          <list-item>
            <p>Parent concept: <italic>273141005 &#124; Severities (qualifier value)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>Child concept: <italic>255604002 &#124; Mild (qualifier value)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>Child concept: <italic>6736007 &#124; Moderate (severity modifier) (qualifier value)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>Child concept: <italic>2448400 &#124; Severe (severity modifier) (qualifier value)&#124;</italic></p>
          </list-item>
          <list-item>
            <p>Child concept: <italic>442452003 &#124; Life threatening severity (qualifier value)&#124;</italic></p>
          </list-item>
        </list>
        <p>However, the last class <italic>dead</italic> of the CTCAE scores is not included in this severity scoring, and there is no direct relationship to adverse events or the meaning of each score for a specific symptom. We have mainly used the European version of SNOMED CT. Nevertheless, we would like to mention that the US version of SNOMED CT has fully equivalent concepts for the CTCAE scores:</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>46411000124101 &#124; Common terminology criteria for adverse events grade 1 (finding)&#124;</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>446421000124109 &#124; Common terminology criteria for adverse events grade 2 (finding)&#124;</italic>
            </p>
          </list-item>
          <list-item>
            <p>
              <italic>446431000124107 &#124; Common terminology criteria for adverse events grade 3 (finding)&#124;</italic>
            </p>
          </list-item>
        </list>
        <p>However, even with this CTCAE-related scoring, definitions and symptom descriptions are needed for each CTCAE term.</p>
        <p>In summary, it is generally challenging to map the exact wording of questions derived from PRO questionnaires to LOINC or SNOMED CT codes if the specific questionnaire is not included in the terminology. However, linking the response options when text is transformed into numeric scales is easier. However, questionnaires like those of the EORTC consortium declare that more is needed to represent numeric response options with the category descriptions [<xref ref-type="bibr" rid="ref25">25</xref>]. When comparing the 2 ontologies, LOINC was better suited to map PRO questionnaires and their associated response options than SNOMED CT due to its text representation options.</p>
      </sec>
      <sec>
        <title>Questionnaire Licenses</title>
        <p>Standardized questionnaires are often licensed, for example, from EORTC, and can only be used for patient surveys after obtaining permission. For commercial purposes, permission usually requires payment of a fee. This may prevent their questions and response options from being included in the SNOMED CT or LOINC terminologies. However, even if a licensed version is available, it should be noted that this does not mean that it is freely available for use. For example, LOINC indicates the copyright for terms for which copyright licenses must be considered. Thus, some licensed PRO questionnaires can be found in LOINC, such as the FACIT PRO questionnaire [<xref ref-type="bibr" rid="ref38">38</xref>] with its 7 panels, including copyright and reference information. This is possible because the English version of FACIT is freely available [<xref ref-type="bibr" rid="ref38">38</xref>] and can be included in terminology databases. Including at least 1 language version of the PROs in terminology databases would increase the international data exchange and its reusability.</p>
        <p>In recent years, there has been a general movement toward “open access” and “open data,” and Creative Commons licenses as an extension of copyright law are seen as a way to protect the origin of data while making it available [<xref ref-type="bibr" rid="ref39">39</xref>]. In this context, Ehrnsperger and Tietze [<xref ref-type="bibr" rid="ref40">40</xref>] provide a broad collection of applied cases for patent pledges and open IP. These concepts may also be considered for licensed questionnaires in the future. Furthermore, initiatives such as the Medical Data-Models portal attempt to establish an open metadata repository to overcome the licensing problem [<xref ref-type="bibr" rid="ref41">41</xref>].</p>
        <p>Because standardized questionnaires, such as those of the EORTC Quality of Group, are designed to be culturally independent and have been tested for language comparability [<xref ref-type="bibr" rid="ref26">26</xref>], linking the data processing to another language would not change the meaning of the data. Instead, the comparability of the data supports the original intent of the consortia that created each PRO. This reconciliation of different languages would require human effort, but it would be a first step in improving the reusability and comparability of PRO results across studies.</p>
      </sec>
      <sec>
        <title>Terminology Changes</title>
        <p>Terminologies are not static. LOINC is currently updated twice a year. SNOMED CT International Edition will be updated monthly beginning in 2022. As a result, terms and concepts may become inactive, and definitions may change. Although the meaning of an identifier should be stable, we found LOINC codes assigned to FSNs with several different parts when comparing the 2.64 and 2.75 releases. For example, the LOINC code <italic>18682-5</italic> is mapped to the</p>
        <list list-type="bullet">
          <list-item>
            <p>FSN <italic>Ambulance claims attachment:Cmplx:Enctr:^Patient:Set</italic> in the 2.64 release and to the</p>
          </list-item>
          <list-item>
            <p>FSN <italic>Note:Find:Pt:Ambulance:Doc:Emergency medicine</italic> in the 2.75 release.</p>
          </list-item>
        </list>
        <p>So, in the 2.64 release, it was defined as 5 parts. In the current 2.75, it is defined as 6 parts. No part is identical to another.</p>
      </sec>
      <sec>
        <title>Time Resolution</title>
        <p>Many PRO questionnaires have a general recall period of 7 days [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. However, only some questions in the questionnaire are associated with this period. Some questions do not specify the exact recall period; others include it at the top of a panel but do not specify it for each question. Thus, a semantic matching of the PRO text may not correctly match a textual description that includes the time span, even though both may refer to the same thing. Because the recall time can dilute the remembered details [<xref ref-type="bibr" rid="ref3">3</xref>], it is essential to include the period in the semantic terminology or at least include it in one of its compositional parts.</p>
        <p>Another issue is the semantic representation of time. An example is the textual description of the general PRO recall time, which can be <italic>past week</italic> or <italic>past seven days</italic>. This semantic variation could be resolved using relationships that indicate the same meaning. Notably, some LOINC terms also include the time resolution. Thus, another way to address the issue of including time is to extend the questionnaire FHIR specification in combination with omitting the time range from some LOINC terms. LOINC extension requests could also help to enable full terminology binding of a questionnaire. As a workaround, SNOMED CT concepts could be used to describe the subject of questions semantically.</p>
      </sec>
    </sec>
    <sec>
      <title>Opportunities for Improvement</title>
      <sec>
        <title>Extension of Terminologies</title>
        <p>The interoperability requirement aligns with the original idea of standardized PRO questionnaires that can be used in trials worldwide. However, considering their year of origin, it is evident that digitization aspects were not considered in their development, and most versions were designed in the classical pen-and-paper format. To overcome this limitation, the EORTC Quality of Life Group has developed guidelines for coupling available EORTC instruments with electronic devices [<xref ref-type="bibr" rid="ref25">25</xref>]. A desirable next step would be to adapt the existing copyright of the PROs to allow at least 1 language version in the terminology databases, as is the case for the FACIT PRO [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
        <p>If licensing issues are not the limiting problem, new codes can be proposed to extend the current databases. In the case of LOINC, the proposal may include new terms for the entire questionnaire, or if some content matches existing terms, they may be included in the submission form and sent to the Regenstrief Institute [<xref ref-type="bibr" rid="ref17">17</xref>]. Like LOINC, SNOMED CT is also open to requests for additional concepts, coordinated through its members’ National Release Centers [<xref ref-type="bibr" rid="ref16">16</xref>]. Because both terminologies, SNOMED CT and LOINC, are curated databases, it should be expected that not all extension requests will be accepted. In addition, there is a time lag between submitting an extension request and the final release. Special circumstances call for special measures. LOINC allows for advance release of terms for emergency situations (eg, pandemics or new technologies).</p>
        <p>However, these prereleases will be reviewed for the next version release and may disappear again. For SNOMED CT, there are 2 other ways to provide additional data: extensions and reference sets [<xref ref-type="bibr" rid="ref16">16</xref>]. Extensions can be created to support national, local, or organizational needs that may not have international relevance. Instead, reference sets can be made to customize and extend the content for specific needs. However, in addition to the fact that these extensions have limited availability, a disadvantage of these reference sets is that they must be maintained in the future to adapt to new international SNOMED CT releases, which requires more effort than requesting new identifiers.</p>
      </sec>
      <sec>
        <title>Combining LOINC and SNOMED CT</title>
        <p>Manual mapping of PRO questions has shown a better match using question text from LOINC. If the requested terminology extension is denied or there is too much time between the request and the release, another way to handle questions without matching LOINC terms might be to find SNOMED CT concepts that at least describe the topic of the underlying question. This will not be as specific as a matching question, but it will at least semantically describe the topic of the question. SNOMED CT provides so-called postcoordinated expressions to logically combine multiple identifiers logically to represent a clinical idea at a higher level of detail [<xref ref-type="bibr" rid="ref16">16</xref>]. A postcoordinated expression can increase the specificity of the topic description for a question. For example, the question <italic>During the past week, have you vomited?</italic> corresponding to the main concept <italic>300359004 &#124; finding of vomiting</italic> is extended by the attribute <italic>Temporal relationship</italic> and the value <italic>per week</italic>, resulting in the following code:</p>
        <list list-type="bullet">
          <list-item>
            <p>
              <italic>300359004 &#124;Finding of vomiting&#124; : 260863009 &#124;Temporal relationship&#124; : 259038000 &#124;per week&#124;</italic>
            </p>
          </list-item>
        </list>
        <p>In the future, it will be possible to use postcoordinated expressions with concrete values such as integer and decimal numbers as attribute values, which are already included in the compositional grammar specification but are not yet available in the International Edition.</p>
      </sec>
    </sec>
    <sec>
      <title>Distinction From Other International Medical Terminologies</title>
      <p>Here, we have focused on the general applicability of semantic terminologies for PRO questionnaires in the 2 comprehensive terminology systems for clinical settings, SNOMED CT and LOINC, from an international perspective.</p>
      <p>However, we would also like to point out some other interesting terminologies that allow PRO mapping, such as the NCI Thesaurus or the MedDRA. While NCI Thesaurus mainly focuses on cancer and thus includes cross-links to CTCAE [<xref ref-type="bibr" rid="ref43">43</xref>], MedDRA contains a lexicon for adverse events common in clinical trials [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
      <p>A recent study attempted to map free text entries to MedDRA terms manually and found a match for 68% of the terms [<xref ref-type="bibr" rid="ref34">34</xref>]. However, similar to our findings, the authors encountered the problem that the textual description of adverse events could fit several different terminology codes, but they were mutually exclusive.</p>
      <p>Next, we would like to make a small excursion into the general use of these terminologies in the health care sector, where medical documentation is undergoing a paradigm shift. The structured documentation of health data should now facilitate the exchange of patient data and not only be used for statistical and administrative purposes such as billing [<xref ref-type="bibr" rid="ref44">44</xref>]. This puts the patient at the center of attention [<xref ref-type="bibr" rid="ref45">45</xref>]. The International Classification of Disease and Related Health Problems (ICD) code is a globally recognized system of medical terminology that provides uniform names for medical diagnoses [<xref ref-type="bibr" rid="ref46">46</xref>]. Although the semantic terminologies such as SNOMED CT or LOINC are much more fine grained and could, therefore, replace established data collections such as the ICD in health care, they will certainly only be used in the near future in addition to the ICD codes, as the use of ICD codes is legally required [<xref ref-type="bibr" rid="ref44">44</xref>]. This also requires additional SNOMED CT or LOINC codes that map to the currently accepted ICD code versions ICD-10 or, soon, ICD-11. Because the aim of this viewpoint was to find a reasonably accurate mapping of the PRO questionnaires analyzed, we did not map the PROs studied to the latest ICD-11 code. However, automatic mappings have been proposed for this task [<xref ref-type="bibr" rid="ref47">47</xref>].</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>In general, using semantic terminologies is possible to improve the interoperability and reusability of PRO questionnaires and their associated response options. However, this task cannot be automated and requires human effort. In particular, the limited number of available languages limits the general idea of barrier-free interoperability. We have limited our mapping to the English versions of SNOMED CT and LOINC for these reasons. Although this is a limitation of our approach, we believe that this is the most comprehensive version [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>] and that our results would be even lower for other languages. In addition, the exact mapping of the phrasing needs to be revised. Although the PRO questionnaires examined in SNOMED CT could only be mapped by symptom descriptions, some PRO questions with exact wording could be found in LOINC. Recognizing that we analyzed a limited number of PRO questionnaires, we would also like to highlight the positive development that some have already been entered into LOINC. One reason for not including PRO questionnaires is primarily due to licensing and copyright issues, which currently prohibit the inclusion of the PRO questions in terminologies. Including at least 1 language version of a licensed PRO is desirable. In this context, initiatives such as the MDM-Portal should be mentioned again, which try to provide open formats [<xref ref-type="bibr" rid="ref41">41</xref>]. Although SNOMED CT offers a wide range of possible numeric response scales, none of the available scales combine numeric scores with textual descriptions required for PROs. Although such a coupling of scores and text is available in LOINC, none of the available scales perfectly matched the response options of the PROs analyzed. In addition, some questions within a questionnaire may have inverted scales, so care must be taken.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this study, we manually mapped the PRO questionnaires EORTC QLQ-C30 and QLQ-BR23 as well as the PROMIS-29 and a CTCAE-based questionnaire to the 2 widely used standardized terminologies in health care settings, SNOMED CT and LOINC. We showed that among the PRO questionnaires analyzed, only the PROMIS-29 is fully available in LOINC, whereas for the others, between 60.9% and 93.3% of PRO questions could be linked to the LOINC terminology. Although the PROMIS questionnaire is unavailable in SNOMED CT, the American version includes the CTCAE questions, and 78.3%-96.7% of the EORTC questions could be linked to SNOMED CT. Even more critical were our findings concerning the response options. Except for the PROMIS-29 response options in LOINC, which included a score coupled with displayed text, these responses were not available for other questionnaires in any of the terminologies.</p>
        <p>It would be desirable to allow at least 1 language version per licensed questionnaire to be included in the terminologies or to use the open formats for future trials. Moreover, special attention should be paid to linking scores and displayed text in the terminologies, as strongly recommended by the original questionnaire settings.</p>
        <p>On the basis of our analysis, we recommend LOINC for the future inclusion of additional PRO questionnaires due to its ability to include displayed text.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Mapping table for translation of questionnaires to SNOMED CT and LOINC.</p>
        <media xlink:href="medinform_v11i1e49301_app1.xlsx" xlink:title="XLSX File  (Microsoft Excel File), 57 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CTCAE</term>
          <def>
            <p>Common Terminology Criteria for Adverse Events</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EORTC</term>
          <def>
            <p>European Organization for Research and Treatment of Cancer</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ePRO</term>
          <def>
            <p>electronic patient-reported outcome</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FACIT</term>
          <def>
            <p>Functional Assessment of Chronic Illness Therapy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">FHIR</term>
          <def>
            <p>Fast Healthcare Interoperability Resources</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">FSN</term>
          <def>
            <p>fully specified name</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">ICD</term>
          <def>
            <p>International Classification of Disease and Related Health Problems</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">LOINC</term>
          <def>
            <p>Logical Observation Identifiers, Names, and Codes</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">MedDRA</term>
          <def>
            <p>Medical Dictionary for Regulatory Activities</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">NCI</term>
          <def>
            <p>National Cancer Institute</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">NEMO</term>
          <def>
            <p>Nebenwirkungs-Management Onkologie (German)</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">PRO</term>
          <def>
            <p>patient-reported outcome</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">PRO-CTCAE</term>
          <def>
            <p>Patient-Reported Outcomes Version of the CTCAE</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">PROM</term>
          <def>
            <p>patient-reported outcome measure</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">PROMIS</term>
          <def>
            <p>Patient-Reported Outcomes Measurement Information System</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">QLQ-BR23</term>
          <def>
            <p>Quality of Life of Breast Cancer Patients Questionnaire</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">QLQ-BR45</term>
          <def>
            <p>Updated version of the Quality of Life of Breast Cancer Patients Questionnaire</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">QLQ-C30</term>
          <def>
            <p>Quality of Life of Cancer Patients Questionnaire</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">SNOMED CT</term>
          <def>
            <p>Systematized Nomenclature of Medicine Clinical Terms</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>We thank the “Zentrum für Innovative Versorgung” for the fruitful discussion on mapping the analyzed patient-reported outcome questionnaires. HAK acknowledges funding provided by the Ministry of Science and Art Baden-Württemberg (Zentrum für Innovative Versorgung); the German Federal Ministry of Education and Research, as part of the DIFUTURE project (Medical Informatics Initiative, grant 01ZZ1804I); and the Ministry of Social Affairs and Integration Baden-Württemberg as part of the project feelBack (networked, digital, patient-related psycho-oncology feedback).</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>All data generated or analyzed during this study will be included in the published article (and its supplementary information files).</p>
      </sec>
    </notes>
    <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>Aaronson</surname>
              <given-names>NK</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmedzai</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bergman</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Bullinger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cull</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Duez</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Filiberti</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Flechtner</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Fleishman</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>de Haes</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Kaasa</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Klee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Osoba</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Razavi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rofe</surname>
              <given-names>PB</given-names>
            </name>
            <name name-style="western">
              <surname>Schraub</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sneeuw</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Takeda</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>The European Organization for Research and Treatment of Cancer QLQ-C30: a quality-of-life instrument for use in international clinical trials in oncology</article-title>
          <source>J Natl Cancer Inst</source>
          <year>1993</year>
          <volume>85</volume>
          <issue>5</issue>
          <fpage>365</fpage>
          <lpage>376</lpage>
          <pub-id pub-id-type="doi">10.1093/jnci/85.5.365</pub-id>
          <pub-id pub-id-type="medline">8433390</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kluetz</surname>
              <given-names>PG</given-names>
            </name>
            <name name-style="western">
              <surname>Chingos</surname>
              <given-names>DT</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Patient-reported outcomes in cancer clinical trials: measuring symptomatic adverse events with the National Cancer Institute's Patient-Reported Outcomes version of the Common Terminology Criteria for Adverse Events (PRO-CTCAE)</article-title>
          <source>Am Soc Clin Oncol Educ Book</source>
          <year>2016</year>
          <volume>35</volume>
          <fpage>67</fpage>
          <lpage>73</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ascopubs.org/doi/10.1200/EDBK_159514?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1200/EDBK_159514</pub-id>
          <pub-id pub-id-type="medline">27249687</pub-id>
          <pub-id pub-id-type="pii">159514</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>AMR</given-names>
            </name>
            <name name-style="western">
              <surname>Kühlwein</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Kraus</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Schwab</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Szekely</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Thiam</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hühne</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jahn</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Fürstberger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ikonomi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Balig</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schuler</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Steger</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Seufferlein</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>HA</given-names>
            </name>
          </person-group>
          <article-title>Digitalization of adverse event management in oncology to improve treatment outcome—a prospective study protocol</article-title>
          <source>PLoS One</source>
          <year>2021</year>
          <volume>16</volume>
          <issue>6</issue>
          <fpage>e0252493</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0252493"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0252493</pub-id>
          <pub-id pub-id-type="medline">34086740</pub-id>
          <pub-id pub-id-type="pii">PONE-D-20-29066</pub-id>
          <pub-id pub-id-type="pmcid">PMC8177479</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schwab</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Schobel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Werle</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Fürstberger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ikonomi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Szekely</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Thiam</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hühne</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jahn</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schuler</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Holderried</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Steger</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Reichert</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kaisers</surname>
              <given-names>UX</given-names>
            </name>
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>AMR</given-names>
            </name>
            <name name-style="western">
              <surname>Seufferlein</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>HA</given-names>
            </name>
          </person-group>
          <article-title>Perspective on mHealth concepts to ensure users‘ empowerment–from adverse event tracking for COVID-19 vaccinations to oncological treatment</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <volume>9</volume>
          <fpage>83863</fpage>
          <lpage>83875</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9448032/authors#authors"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/access.2021.3087315</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schobel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Volz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hörner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Jobst</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Schwab</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Ikonomi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Werle</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Fürstberger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hoenig</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>HA</given-names>
            </name>
          </person-group>
          <article-title>Supporting medical staff from psycho-oncology with smart mobile devices: insights into the development process and first results</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2021</year>
          <volume>18</volume>
          <issue>10</issue>
          <fpage>5092</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph18105092"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph18105092</pub-id>
          <pub-id pub-id-type="medline">34064987</pub-id>
          <pub-id pub-id-type="pii">ijerph18105092</pub-id>
          <pub-id pub-id-type="pmcid">PMC8150950</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bischoff-Ferrari</surname>
              <given-names>HA</given-names>
            </name>
            <name name-style="western">
              <surname>Vondechend</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bellamy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Theiler</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Validation and patient acceptance of a computer touch screen version of the WOMAC 3.1 osteoarthritis index</article-title>
          <source>Ann Rheum Dis</source>
          <year>2005</year>
          <volume>64</volume>
          <issue>1</issue>
          <fpage>80</fpage>
          <lpage>84</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ard.bmj.com/lookup/pmidlookup?view=long&#38;pmid=15231508"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/ard.2003.019307</pub-id>
          <pub-id pub-id-type="medline">15231508</pub-id>
          <pub-id pub-id-type="pii">ard.2003.019307</pub-id>
          <pub-id pub-id-type="pmcid">PMC1755204</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Polomano</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bruner</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Comparison between patient-reported and clinician-observed symptoms in oncology</article-title>
          <source>Cancer Nurs</source>
          <year>2013</year>
          <volume>36</volume>
          <issue>6</issue>
          <fpage>E1</fpage>
          <lpage>E16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.lww.com/cancernursingonline/fulltext/2013/11000/comparison_between_patient_reported_and.12.aspx"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/NCC.0b013e318269040f</pub-id>
          <pub-id pub-id-type="medline">23047799</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sivanandan</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bullard</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Christian</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digital patient-reported outcome measures for monitoring of patients on cancer treatment: cross-sectional questionnaire study</article-title>
          <source>JMIR Form Res</source>
          <year>2021</year>
          <volume>5</volume>
          <issue>8</issue>
          <fpage>e18502</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2021/8/e18502/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18502</pub-id>
          <pub-id pub-id-type="medline">34398785</pub-id>
          <pub-id pub-id-type="pii">v5i8e18502</pub-id>
          <pub-id pub-id-type="pmcid">PMC8398740</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Malay</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>KC</given-names>
            </name>
          </person-group>
          <article-title>How to use outcomes questionnaires: pearls and pitfalls</article-title>
          <source>Clin Plast Surg</source>
          <year>2013</year>
          <volume>40</volume>
          <issue>2</issue>
          <fpage>261</fpage>
          <lpage>269</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/23506766"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cps.2012.10.002</pub-id>
          <pub-id pub-id-type="medline">23506766</pub-id>
          <pub-id pub-id-type="pii">S0094-1298(12)00149-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC3602914</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fayers</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Aaronson</surname>
              <given-names>NK</given-names>
            </name>
            <name name-style="western">
              <surname>Bjordal</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Groenvold</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Curran</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bottomley</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The EORTC QLQ-C30 scoring manual (3rd edition)</article-title>
          <source>European Organisation for Research and Treatment of Cancer</source>
          <year>2001</year>
          <access-date>2023-12-07</access-date>
          <publisher-loc>Brussels</publisher-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.eortc.org/app/uploads/sites/2/2018/02/SCmanual.pdf">https://www.eortc.org/app/uploads/sites/2/2018/02/SCmanual.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wheelwright</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bjordal</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bottomley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gilberta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Martinelli</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Pe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sztankay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cocks</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Coens</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Darlington</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Fayers</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Giesinger</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Koller</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kulis</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Reijneveld</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Singer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tomaszewski</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Fitzsimmons</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>EORTC quality of life group guidelines for developing questionnaire modules (5th edition)</article-title>
          <source>European Organisation for Research and Treatment of Cancer</source>
          <year>2021</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.eortc.org/app/uploads/sites/2/2022/07/Module-Guidelines-Version-5-FINAL.pdf">https://www.eortc.org/app/uploads/sites/2/2022/07/Module-Guidelines-Version-5-FINAL.pdf</ext-link>
          </comment>
        </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>Lehne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Essenwanger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schepers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thun</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Why digital medicine depends on interoperability</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <volume>2</volume>
          <fpage>79</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0158-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0158-1</pub-id>
          <pub-id pub-id-type="medline">31453374</pub-id>
          <pub-id pub-id-type="pii">158</pub-id>
          <pub-id pub-id-type="pmcid">PMC6702215</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vorisek</surname>
              <given-names>CN</given-names>
            </name>
            <name name-style="western">
              <surname>Lehne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Klopfenstein</surname>
              <given-names>SAI</given-names>
            </name>
            <name name-style="western">
              <surname>Mayer</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bartschke</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Haese</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Thun</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Fast Healthcare Interoperability Resources (FHIR) for interoperability in health research: systematic review</article-title>
          <source>JMIR Med Inform</source>
          <year>2022</year>
          <volume>10</volume>
          <issue>7</issue>
          <fpage>e35724</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2022/7/e35724/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/35724</pub-id>
          <pub-id pub-id-type="medline">35852842</pub-id>
          <pub-id pub-id-type="pii">v10i7e35724</pub-id>
          <pub-id pub-id-type="pmcid">PMC9346559</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>Bodenreider</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Vreeman</surname>
              <given-names>DJ</given-names>
            </name>
          </person-group>
          <article-title>Recent developments in clinical terminologies—SNOMED CT, LOINC, and RxNorm</article-title>
          <source>Yearb Med Inform</source>
          <year>2018</year>
          <volume>27</volume>
          <issue>1</issue>
          <fpage>129</fpage>
          <lpage>139</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0038-1667077"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0038-1667077</pub-id>
          <pub-id pub-id-type="medline">30157516</pub-id>
          <pub-id pub-id-type="pmcid">PMC6115234</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gaudet-Blavignac</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Foufi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Bjelogrlic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lovis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Use of the Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) for processing free text in health care: systematic scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>e24594</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/1/e24594/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24594</pub-id>
          <pub-id pub-id-type="medline">33496673</pub-id>
          <pub-id pub-id-type="pii">v23i1e24594</pub-id>
          <pub-id pub-id-type="pmcid">PMC7872838</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Randorff</surname>
              <given-names>HA</given-names>
            </name>
            <name name-style="western">
              <surname>Kuropatwa</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>SNOMED CT starter guide</article-title>
          <source>International Health Terminology Standards Development Organisation</source>
          <year>2014</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://studylib.net/doc/18128896/snomed-ct-starter-guide">https://studylib.net/doc/18128896/snomed-ct-starter-guide</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>The Logical Observation Identifiers Names and Codes Committee</collab>
          </person-group>
          <article-title>Logical Observation Identifiers Names and Codes LOINC users' guide for LOINC version 2.67</article-title>
          <source>Regenstrief Institute</source>
          <year>2019</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://loinc.org/kb/users-guide/">https://loinc.org/kb/users-guide/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miñarro-Giménez</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jaulent</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Dewenter</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Thun</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gøeg</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Karlsson</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Schulz</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Quantitative analysis of manual annotation of clinical text samples</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <volume>123</volume>
          <fpage>37</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(18)30544-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2018.12.011</pub-id>
          <pub-id pub-id-type="medline">30654902</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30544-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bodenreider</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Issues in mapping LOINC laboratory tests to SNOMED CT</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2008</year>
          <volume>2008</volume>
          <fpage>51</fpage>
          <lpage>55</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/18999311"/>
          </comment>
          <pub-id pub-id-type="medline">18999311</pub-id>
          <pub-id pub-id-type="pmcid">PMC2655945</pub-id>
        </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>Lee</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Groß</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hartung</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liou</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Rahm</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>A multi-part matching strategy for mapping LOINC with laboratory terminologies</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2014</year>
          <volume>21</volume>
          <issue>5</issue>
          <fpage>792</fpage>
          <lpage>800</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/24363318"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2013-002139</pub-id>
          <pub-id pub-id-type="medline">24363318</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2013-002139</pub-id>
          <pub-id pub-id-type="pmcid">PMC4147612</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>Rothmund</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pilz</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Egeter</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lidington</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Piccinin</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Arraras</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Grønvold</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Holzner</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>van Leeuwen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Young</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Giesinger</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Patient-reported outcome measures for emotional functioning in cancer patients: content comparison of the EORTC CAT core, FACT-G, HADS, SF-36, PRO-CTCAE, and PROMIS instruments</article-title>
          <source>Psychooncology</source>
          <year>2023</year>
          <volume>32</volume>
          <issue>4</issue>
          <fpage>628</fpage>
          <lpage>639</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1002/pon.6109"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/pon.6109</pub-id>
          <pub-id pub-id-type="medline">36707461</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Questionnaires</article-title>
          <source>EORTC Quality of Life</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://qol.eortc.org/questionnaires/">https://qol.eortc.org/questionnaires/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>PROMIS-29 profile v2.0</article-title>
          <source>PROMIS Health Organization and PROMIS Cooperative Group</source>
          <year>2016</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.unmc.edu/centric/_documents/PROMIS-29.pdf">https://www.unmc.edu/centric/_documents/PROMIS-29.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>Common Terminology Criteria for Adverse Events (CTCAE) version 5.0</article-title>
          <source>U.S. Department of Health and Human Services</source>
          <year>2017</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ctep.cancer.gov/protocoldevelopment/electronic_applications/docs/ctcae_v5_quick_reference_5x7.pdf">https://ctep.cancer.gov/protocoldevelopment/electronic_applications/docs/ctcae_v5_quick_reference_5x7.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuliś</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Holzner</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Koller</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ruyskart</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Itani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bottomley</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Guidance on the implementation and management of EORTC quality of life instruments in electronic applications</article-title>
          <source>European Organisation for Research and Treatment of Cancer</source>
          <year>2018</year>
          <access-date>2023-12-07</access-date>
          <publisher-loc>Brussels, Belgium</publisher-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.eortc.org/app/uploads/sites/2/2018/03/ePRO-guidelines.pdf">https://www.eortc.org/app/uploads/sites/2/2018/03/ePRO-guidelines.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuliś</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bottomley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Velikova</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Greimel</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Koller</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>EORTC quality of life group translation procedure (4th edition)</article-title>
          <source>European Organisation for Research and Treatment of Cancer</source>
          <year>2017</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.eortc.org/app/uploads/sites/2/2018/02/translation_manual_2017.pdf">https://www.eortc.org/app/uploads/sites/2/2018/02/translation_manual_2017.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cella</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rothrock</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Reeve</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Yount</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Amtmann</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bode</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Buysse</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Devellis</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>DeWalt</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Fries</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Gershon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hahn</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Lai</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Pilkonis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Revicki</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rose</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Weinfurt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hays</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The Patient-Reported Outcomes Measurement Information System (PROMIS) developed and tested its first wave of adult self-reported health outcome item banks: 2005-2008</article-title>
          <source>J Clin Epidemiol</source>
          <year>2010</year>
          <volume>63</volume>
          <issue>11</issue>
          <fpage>1179</fpage>
          <lpage>1194</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/20685078"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jclinepi.2010.04.011</pub-id>
          <pub-id pub-id-type="medline">20685078</pub-id>
          <pub-id pub-id-type="pii">S0895-4356(10)00173-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC2965562</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Di Maio</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bryce</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Perrone</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Patient-reported outcomes in the evaluation of toxicity of anticancer treatments</article-title>
          <source>Nat Rev Clin Oncol</source>
          <year>2016</year>
          <volume>13</volume>
          <issue>5</issue>
          <fpage>319</fpage>
          <lpage>325</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://hdl.handle.net/2318/1603135"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/nrclinonc.2015.222</pub-id>
          <pub-id pub-id-type="medline">26787278</pub-id>
          <pub-id pub-id-type="pii">nrclinonc.2015.222</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <article-title>Cancer Therapy Evaluation Program</article-title>
          <source>National Cancer Institute</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ctep.cancer.gov/protocoldevelopment/electronic_applications/ctc.htm">https://ctep.cancer.gov/protocoldevelopment/electronic_applications/ctc.htm</ext-link>
          </comment>
        </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>Basch</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Reeve</surname>
              <given-names>BB</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Clauser</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Minasian</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Dueck</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Mendoza</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Hay</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Atkinson</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Abernethy</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Bruner</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Cleeland</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Sloan</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Chilukuri</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Baumgartner</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Denicoff</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>St Germain</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>O'Mara</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kelaghan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Sit</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rogak</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Barz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Paul</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Schrag</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Development of the National Cancer Institute's Patient-Reported Outcomes version of the Common Terminology Criteria for Adverse Events (PRO-CTCAE)</article-title>
          <source>J Natl Cancer Inst</source>
          <year>2014</year>
          <volume>106</volume>
          <issue>9</issue>
          <fpage>dju244</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25265940"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jnci/dju244</pub-id>
          <pub-id pub-id-type="medline">25265940</pub-id>
          <pub-id pub-id-type="pii">dju244</pub-id>
          <pub-id pub-id-type="pmcid">PMC4200059</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <article-title>LOINC search</article-title>
          <source>Regenstrief Institute</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://loinc.org/wp-login.php?redirect_to=https%3A%2F%2Floinc.org%2Fsearch%2F&#38;reauth=1">https://loinc.org/wp-login.php?redirect_to=https%3A%2F%2Floinc.org%2Fsearch%2F&#38;reauth=1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>SNOMED CT browser</article-title>
          <source>SNOMED International</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://browser.ihtsdotools.org/?">https://browser.ihtsdotools.org/?</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
          <article-title>International</article-title>
          <source>Regenstrief Institute</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://loinc.org/international/">https://loinc.org/international/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Shoenbill</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Dueck</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Schrag</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bruner</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Minasian</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>St Germain</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>O'Mara</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Baumgartner</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Rogak</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Abernethy</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Griffin</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <article-title>Patient free text reporting of symptomatic adverse events in cancer clinical research using the National Cancer Institute's Patient-Reported Outcomes version of the Common Terminology Criteria for Adverse Events (PRO-CTCAE)</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <volume>26</volume>
          <issue>4</issue>
          <fpage>276</fpage>
          <lpage>285</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30840079"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy169</pub-id>
          <pub-id pub-id-type="medline">30840079</pub-id>
          <pub-id pub-id-type="pii">5320658</pub-id>
          <pub-id pub-id-type="pmcid">PMC6402312</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>team TID</collab>
          </person-group>
          <article-title>FHIR resource validator</article-title>
          <source>GitHub</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/inferno-framework/fhir-validator-app">https://github.com/inferno-framework/fhir-validator-app</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cella</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>SW</given-names>
            </name>
            <name name-style="western">
              <surname>Condon</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Schalet</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hays</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Rothrock</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Yount</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>KF</given-names>
            </name>
            <name name-style="western">
              <surname>Gershon</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Amtmann</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>DeWalt</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Pilkonis</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Weinfurt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Reeve</surname>
              <given-names>BB</given-names>
            </name>
          </person-group>
          <article-title>PROMIS adult health profiles: efficient short-form measures of seven health domains</article-title>
          <source>Value Health</source>
          <year>2019</year>
          <volume>22</volume>
          <issue>5</issue>
          <fpage>537</fpage>
          <lpage>544</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1098-3015(19)30118-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jval.2019.02.004</pub-id>
          <pub-id pub-id-type="medline">31104731</pub-id>
          <pub-id pub-id-type="pii">S1098-3015(19)30118-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC7201383</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>Bodenreider</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Using SNOMED CT in combination with MedDRA for reporting signal detection and adverse drug reactions reporting</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2009</year>
          <volume>2009</volume>
          <fpage>45</fpage>
          <lpage>49</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/20351820"/>
          </comment>
          <pub-id pub-id-type="medline">20351820</pub-id>
          <pub-id pub-id-type="pmcid">PMC2815504</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>Webster</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cella</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yost</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>The Functional Assessment of Chronic Illness Therapy (FACIT) measurement system: properties, applications, and interpretation</article-title>
          <source>Health Qual Life Outcomes</source>
          <year>2003</year>
          <volume>1</volume>
          <fpage>79</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hqlo.biomedcentral.com/articles/10.1186/1477-7525-1-79"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1477-7525-1-79</pub-id>
          <pub-id pub-id-type="medline">14678568</pub-id>
          <pub-id pub-id-type="pii">1477-7525-1-79</pub-id>
          <pub-id pub-id-type="pmcid">PMC317391</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Murray-Rust</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Open data in science</article-title>
          <source>Nat Prec</source>
          <year>2008</year>
          <fpage>1</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nature.com/articles/npre.2008.1526.1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/npre.2008.1526.1</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>Ehrnsperger</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Tietze</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Patent pledges, open IP, or patent pools? Developing taxonomies in the thicket of terminologies</article-title>
          <source>PLoS One</source>
          <year>2019</year>
          <volume>14</volume>
          <issue>8</issue>
          <fpage>e0221411</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0221411"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0221411</pub-id>
          <pub-id pub-id-type="medline">31430349</pub-id>
          <pub-id pub-id-type="pii">PONE-D-19-10154</pub-id>
          <pub-id pub-id-type="pmcid">PMC6701788</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <article-title>Portal for medical data models</article-title>
          <source>Medizinische Fakultät Münster, Universitätsklinikum Münster</source>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medizin.uni-muenster.de/en/imi/research/digital-health/mdm-portal.html">https://www.medizin.uni-muenster.de/en/imi/research/digital-health/mdm-portal.html</ext-link>
          </comment>
        </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>Bennett</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Dueck</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Mendoza</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Reeve</surname>
              <given-names>BB</given-names>
            </name>
            <name name-style="western">
              <surname>Atkinson</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Castro</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Denicoff</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rogak</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Harness</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Bearden</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Bryant</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Siegel</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Schrag</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Mode equivalence and acceptability of tablet computer-, interactive voice response system-, and paper-based administration of the U.S. National Cancer Institute's Patient-Reported Outcomes version of the Common Terminology Criteria for Adverse Events (PRO-CTCAE)</article-title>
          <source>Health Qual Life Outcomes</source>
          <year>2016</year>
          <volume>14</volume>
          <fpage>24</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hqlo.biomedcentral.com/articles/10.1186/s12955-016-0426-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12955-016-0426-6</pub-id>
          <pub-id pub-id-type="medline">26892667</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12955-016-0426-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC4759776</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>de Coronado</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>LW</given-names>
            </name>
            <name name-style="western">
              <surname>Fragoso</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Haber</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Hahn-Dantona</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Hartel</surname>
              <given-names>FW</given-names>
            </name>
            <name name-style="western">
              <surname>Quan</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Safran</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Whiteman</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The NCI thesaurus quality assurance life cycle</article-title>
          <source>J Biomed Inform</source>
          <year>2009</year>
          <volume>42</volume>
          <issue>3</issue>
          <fpage>530</fpage>
          <lpage>539</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(09)00008-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2009.01.003</pub-id>
          <pub-id pub-id-type="medline">19475726</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(09)00008-2</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>Thun</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dewenter</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>ICD-11, ICHI und SNOMED CT—was bedeuten die Systematiken für E‑Health-Anwendungen? [ICD-11, ICHI and SNOMED CT—What do the standards mean for eHealth applications?]</article-title>
          <source>Bundesgesundheitsblatt Gesundheitsforschung Gesundheitsschutz</source>
          <year>2018</year>
          <volume>61</volume>
          <issue>7</issue>
          <fpage>812</fpage>
          <lpage>820</lpage>
          <comment>[in German]</comment>
          <pub-id pub-id-type="doi">10.1007/s00103-018-2759-2</pub-id>
          <pub-id pub-id-type="medline">29846742</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00103-018-2759-2</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>Hamberger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ikonomi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schwab</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Werle</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Fürstberger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Holderried</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kaisers</surname>
              <given-names>UX</given-names>
            </name>
            <name name-style="western">
              <surname>Steger</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kestler</surname>
              <given-names>HA</given-names>
            </name>
          </person-group>
          <article-title>Interaction empowerment in mobile health: concepts, challenges, and perspectives</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2022</year>
          <volume>10</volume>
          <issue>4</issue>
          <fpage>e32696</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2022/4/e32696/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/32696</pub-id>
          <pub-id pub-id-type="medline">35416786</pub-id>
          <pub-id pub-id-type="pii">v10i4e32696</pub-id>
          <pub-id pub-id-type="pmcid">PMC9047725</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <article-title>ICD-11 implementation or transition guide</article-title>
          <source>World Health Organization</source>
          <year>2019</year>
          <access-date>2023-12-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://icd.who.int/en/docs/ICD-11%20Implementation%20or%20Transition%20Guide_v105.pdf">https://icd.who.int/en/docs/ICD-11%20Implementation%20or%20Transition%20Guide_v105.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fung</surname>
              <given-names>KW</given-names>
            </name>
            <name name-style="western">
              <surname>Bodenreider</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Otero</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>SZ</given-names>
            </name>
          </person-group>
          <article-title>Sequential mapping—a novel approach to map from ICD-10-CM to ICD-11</article-title>
          <source>MEDINFO 2021: One World, One Health—Global Partnership for Digital Innovation: Proceedings of the 18th World Congress on Medical and Health Informatics</source>
          <year>2022</year>
          <publisher-loc>Amsterdam</publisher-loc>
          <publisher-name>IOS Press</publisher-name>
          <fpage>96</fpage>
          <lpage>100</lpage>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
