<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<!DOCTYPE GmsArticle SYSTEM "http://www.egms.de/dtd/2.0.34/GmsArticle.dtd">
<GmsArticle xmlns:xlink="http://www.w3.org/1999/xlink">
  <MetaData>
    <Identifier>mibe000256</Identifier>
    <IdentifierDoi>10.3205/mibe000256</IdentifierDoi>
    <IdentifierUrn>urn:nbn:de:0183-mibe0002565</IdentifierUrn>
    <ArticleType>Research Article</ArticleType>
    <TitleGroup>
      <Title language="en">Model-driven execution of phenotype algorithms &#8211; introduction of the Terminology- and Ontology-based Phenotyping Framework</Title>
      <TitleTranslated language="de">Modell-getriebene Ausf&#252;hrung von Ph&#228;notyp-Algorithmen &#8211; Einf&#252;hrung des Terminology- and Ontology-based Phenotyping Framework</TitleTranslated>
    </TitleGroup>
    <CreatorList>
      <Creator>
        <PersonNames>
          <Lastname>Beger</Lastname>
          <LastnameHeading>Beger</LastnameHeading>
          <Firstname>Christoph</Firstname>
          <Initials>C</Initials>
        </PersonNames>
        <Address>Universit&#228;t Leipzig, Institut f&#252;r Medizinische Informatik, Statistik und Epidemiologie, H&#228;rtelstra&#223;e 16&#8211;18, 04107 Leipzig, Germany<Affiliation>Institute for Medical Informatics, Statistics and Epidemiology, Leipzig University, Leipzig, Germany</Affiliation><Affiliation>Growth Network CrescNet, Leipzig University, Leipzig, Germany</Affiliation></Address>
        <Email>christoph.beger&#64;imise.uni-leipzig.de</Email>
        <Creatorrole corresponding="yes" presenting="no">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Matthies</Lastname>
          <LastnameHeading>Matthies</LastnameHeading>
          <Firstname>Franz</Firstname>
          <Initials>F</Initials>
        </PersonNames>
        <Address>
          <Affiliation>Institute for Medical Informatics, Statistics and Epidemiology, Leipzig University, Leipzig, Germany</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Sch&#228;fermeier</Lastname>
          <LastnameHeading>Sch&#228;fermeier</LastnameHeading>
          <Firstname>Ralph</Firstname>
          <Initials>R</Initials>
        </PersonNames>
        <Address>
          <Affiliation>Institute for Medical Informatics, Statistics and Epidemiology, Leipzig University, Leipzig, Germany</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Uciteli</Lastname>
          <LastnameHeading>Uciteli</LastnameHeading>
          <Firstname>Alexandr</Firstname>
          <Initials>A</Initials>
        </PersonNames>
        <Address>
          <Affiliation>Institute for Medical Informatics, Statistics and Epidemiology, Leipzig University, Leipzig, Germany</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
    </CreatorList>
    <PublisherList>
      <Publisher>
        <Corporation>
          <Corporatename>German Medical Science GMS Publishing House</Corporatename>
        </Corporation>
        <Address>D&#252;sseldorf</Address>
      </Publisher>
    </PublisherList>
    <SubjectGroup>
      <SubjectheadingDDB>610</SubjectheadingDDB>
      <Keyword language="en">phenotype</Keyword>
      <Keyword language="en">algorithms</Keyword>
      <Keyword language="en">eligibility determination</Keyword>
      <Keyword language="en">health information interoperability</Keyword>
      <Keyword language="en">terminology as topic</Keyword>
    </SubjectGroup>
    <DatePublishedList>
      
    <DatePublished>20231120</DatePublished></DatePublishedList>
    <Language>engl</Language>
    <License license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/">
      <AltText language="en">This is an Open Access article distributed under the terms of the Creative Commons Attribution 4.0 License.</AltText>
      <AltText language="de">Dieser Artikel ist ein Open-Access-Artikel und steht unter den Lizenzbedingungen der Creative Commons Attribution 4.0 License (Namensnennung).</AltText>
    </License>
    <SourceGroup>
      <Journal>
        <ISSN>1860-9171</ISSN>
        <Volume>19</Volume>
        <JournalTitle>GMS Medizinische Informatik, Biometrie und Epidemiologie</JournalTitle>
        <JournalTitleAbbr>GMS Med Inform Biom Epidemiol</JournalTitleAbbr>
      </Journal>
    </SourceGroup>
    <ArticleNo>17</ArticleNo>
    <Fundings>
      <Funding fundId="01ZZ2018">Bundesministerium f&#252;r Bildung und Forschung (BMBF)</Funding>
      <Funding fundId="01ZZ1803A">Bundesministerium f&#252;r Bildung und Forschung (BMBF)</Funding>
    </Fundings>
  </MetaData>
  <OrigData>
    <Abstract language="de" linked="yes"><Pgraph>Die automatisierte Erkennung von Patienten, die bestimmte klinische Kriterien erf&#252;llen oder unerw&#252;nschte Ereignisse aufweisen, spielt eine wichtige Rolle bei der Verbesserung der Patientenversorgung. Regelb<TextGroup><PlainText>a</PlainText></TextGroup>sierte Systeme sind eine M&#246;glichkeit, die standardisierte Modellierung von Algorithmen zur Erkennung von Patienten mit bestimmten beob<TextGroup><PlainText>a</PlainText></TextGroup>chtbaren Merkmalen (Ph&#228;notypen) zu erm&#246;glichen. Ein weiterer wichtiger Aspekt ist der Abruf von Daten aus elektronischen Patientenakten in Krankenhausinformationssystemen und klinischen Forschungsdatenbanksystemen. In dieser Arbeit wird ein neues regelbasiertes System beschrieben, das f&#252;r Fachleute ohne IT-Hintergrund geeignet ist und die automatische Abfrage von Patientendaten bei der Ausf&#252;hrung erm&#246;glicht, indem Suchanfragen in quellenspezifische Abfragesprachen &#252;bersetzt werden.</Pgraph><Pgraph>Als Grundlage f&#252;r regelbasierte strukturierte Ph&#228;notyp-Algorithmen wird ein Modell verwendet, das von der Core Ontology of Phenotypes abgeleitet ist. Das Modell erm&#246;glicht die Definition von Ph&#228;notyp-Algorithmen mit Eigenschaften wie Code-System-Beziehungen zur Verbesserung der Interoperabilit&#228;t. Mit einem relativ einfachen Mapping k&#246;nnen IT-Spezialisten eine Spezifikation erstellen, um diese Modelle mit einem lokalen Krankenhausinformationssystem zu verbinden.</Pgraph><Pgraph>Wir haben eine interaktive Webanwendung, das Terminology- and O<TextGroup><PlainText>ntolog</PlainText></TextGroup>y-based Phenotyping Framework, entwickelt, um Fachleute bei der Modellierung und Ausf&#252;hrung von Ph&#228;notyp-Algorithmen zu unterst&#252;tzen. Je nach dem datenhaltenden Quellsystem wird ein geeigneter Adapter verwendet, der die Abfragen in die quellsystemspezifische Sprache &#252;bersetzt und ausf&#252;hrt. Das Framework wurde mit einer SQL-Datenbank und einem FHIR-Server getestet, die beide mit zuf&#228;llig generierten Daten initialisiert wurden. Die generierten Anfragen ergaben identische Ergebnismengen.</Pgraph><Pgraph>Der vorgeschlagene computergest&#252;tzte Ansatz kann die Erkennung von Krankheiten und die Rekrutierung f&#252;r klinische Studien verbessern und erm&#246;glicht eine klare Aufgabenteilung zwischen Dom&#228;nenexperten und IT-Spezialisten.</Pgraph></Abstract>
    <Abstract language="en" linked="yes"><Pgraph>Automated detection of patients who meet certain clinical criteria or who experience adverse events plays a key role in improving patient care. Rule-based systems are one approach to enable standardised modelling of algorithms to detect patients with certain observable characteristics (phenotypes). Another important aspect is the retrieval of data from electronic health records in hospital information systems and clinical research database systems. In this work, we propose a new rule-based system, suitable for domain experts without IT background that allows automatic retrieval of patient data on execution by translating search queries into source-specific query languages.</Pgraph><Pgraph>As a basis for rule-based structured phenotype algorithms, we use a model derived from the Core Ontology of Phenotypes. The model allows phenotype algorithms to be defined with properties such as code system relationships to improve interoperability. With a relatively simple mapping, IT specialists can provide a specification to connect these models to a local hospital information system.</Pgraph><Pgraph>We developed an interactive web application, the Terminology- and Ontology-based Phenotyping Framework, to support domain experts in modelling and executing phenotype algorithms. Depending on the data-holding source system, an appropriate adapter is used to translate and execute queries in the source system-specific language. The framework was tested against a SQL database and a FHIR server, both initialised with randomly generated data. Generated queries yielded identical result sets.</Pgraph><Pgraph>The proposed computer-assisted approach can improve disease detection and clinical trial recruitment and enables a clear division of tasks between domain experts and IT specialists.</Pgraph></Abstract>
    <TextBlock linked="yes" name="Introduction">
      <MainHeadline>Introduction</MainHeadline><Pgraph>In the Medical Informatics Initiative (MII) innovative IT solutions are developed to support medical research and enhance patient care. An important aspect of this is the automatic detection of diseases, risks for the same and adverse events of medications. For the implementation of such detection, patient data must be extracted from electronic health records (EHR) or research databases and evaluated. This may involve machine-interpretable phenotype algorithms, which use structured filter criteria and rules to detect individuals with specific properties (phenotypes) and derive further properties. With this, computer-assisted algorithms can, among other things, improve clinical trial recruitment <TextLink reference="1"></TextLink>. The National Portal for Medical Research Data (FDPG) was recently developed in the MII <TextLink reference="2"></TextLink>. It provides scientists with federated access to 31 German university hospitals, enabling them to perform feasibility queries and submit data use proposals. The query interface allows relatively simple matching criteria to be defined.</Pgraph><Pgraph>In this work, we want to focus on a more general approach of defining shareable models that can be used to perform complex queries and calculations in order to find matching individuals and infer additional characteristics. For this, we distinguish between three core notions: <Mark2>phenotype</Mark2>, <Mark2>phenotype model</Mark2> and<Mark2> phenotype algorithm</Mark2>.</Pgraph><Pgraph>We use the definition of &#8216;<Mark2>phenotype</Mark2>&#8216; as a &#8216;(combination of) bodily feature(s) of an organism determined by the interaction of its genetic make-up and environment&#8217; by Scheuermann et al. <TextLink reference="3"></TextLink>. And in a broader sense, we also consider all observable human characteristics to be phenotypes.</Pgraph><Pgraph>A <Mark2>phenotype model</Mark2> is a formal representation of phenotypic knowledge. We hereby distinguish between general and specific phenotype models <TextLink reference="4"></TextLink>. The general model provides a basic classification of phenotypes, the required attributes of phenotype classes (e.g., labels, data types, codes, units of measurement, derivation rules&#47;formulas etc.), relation types and rules (axioms), which must be used&#47;followed by developing specific models. A specific phenotype model represents phenotypic knowledge by defining specific phenotype classes (such as &#8216;weight&#8217;, &#8216;height&#8217;, &#8216;BMI&#8217;, &#8216;obesity&#8217;, etc.) according to the general model. This means, all required attributes of the classes (e.g., including the formula for calculating BMI from weight and height, as well as the ranges to classify the BMI value in categories from underweight to obesity) and relations between the classes (e.g., weight and height values are required for calculating BMI) are specified.</Pgraph><Pgraph>A <Mark2>phenotype algorithm</Mark2> is generally understood as an algorithm designed to identify or classify phenotypic traits <TextLink reference="5"></TextLink>, <TextLink reference="6"></TextLink>. Specifically, we consider a phenotype algorithm to be a sequence of instructions to</Pgraph><Pgraph><OrderedList><ListItem level="1" levelPosition="1" numString="1.">query data representing phenotypes,</ListItem><ListItem level="1" levelPosition="2" numString="2.">derive additional properties (derived&#47;composite phenotypes) from other phenotypes,</ListItem><ListItem level="1" levelPosition="3" numString="3.">classify phenotypes into phenotype classes, and</ListItem><ListItem level="1" levelPosition="4" numString="4.">provide results in a machine- and human-readable format.</ListItem></OrderedList></Pgraph><Pgraph>A <Mark2>generic</Mark2> <Mark2>phenotype algorithm</Mark2> is model-driven (i.e., it can be configured by a phenotype model). This means, the algorithm always performs the same (generic) steps (see above) and uses the specific phenotype definitions specified in a phenotype model (e.g., identifying obese patients based on weight and height or identifying patients with acute kidney injury based on creatinine).</Pgraph><Pgraph>The effort required to design algorithms can be very high depending on the complexity <TextLink reference="7"></TextLink> and typically requires a close collaboration between domain and IT experts. To support domain experts in creating phenotype models and executing phenotype algorithms, we developed a framework, the Terminology- and Ontology-based Phenotyping (TOP) Framework, which will be presented in this work. The goal was for the framework to allow domain experts to define phenotypes with respective filters and roles on their own, and to be embeddable by IT experts into the hospital&#8217;s information system, thus allowing the execution of algorithms on patient data from routine patient care and medical research.</Pgraph></TextBlock>
    <TextBlock linked="yes" name="Methods">
      <MainHeadline>Methods</MainHeadline><Pgraph>We use the Core Ontology of Phenotypes (COP) <TextLink reference="8"></TextLink> as the generic phenotype model and as a basis for developing specific models. COP specifies that all phenotypes of organisms are instances of one or more phenotype classes. These classes are distinguished into single and composite phenotype classes. Single phenotypes (e.g., height or weight of a person) are atomic and can be components&#47;parts of composite phenotypes (e.g., BMI). The two described class types can further be subdivided into unrestricted and restricted phenotype classes. A restricted class (e.g., &#8216;height above 150 cm&#8217;) is always a subclass of an unrestricted class (&#8216;height&#8217;) and possess a value restriction so that only a subset of the corresponding unrestricted class instances belongs to the restricted class. For example, the phenotype &#8216;height&#8217; with value 18<TextGroup><PlainText>0 c</PlainText></TextGroup>m of the individual John Doe is an instance of the unrestricted single phenotype class &#8216;height&#8217; and, at the same time, of the restricted single phenotype class &#8216;height above 150 cm&#8217;.</Pgraph><Pgraph>Single phenotype classes must be annotatable with terms of standard terminologies like Logical Observation Identifiers Names and Codes (LOINC) or Systematized Nomenclature of Medicine and Clinical Terms (SNOMED CT). These annotations are used to assign the phenotype classes with corresponding data from the source systems. For instance, the phenotype &#8216;height&#8217; is annotated with code &#8216;LOINC:3137-7&#8217;. With this annotation in place, a mapping can be provided to assign all height values from electronic health records to the phenotype &#8216;height&#8217;, which makes them available for classifications and calculations.</Pgraph><Pgraph>As composite phenotypes result from calculations and compositions of single phenotypes, constants and other composite phenotypes, we developed a generic specification to express these cases. According to the specification, all composite phenotype classes have exactly one expression representing either a phenotype, a constant, or exactly one function with a set of arguments. Expressions can be nested because arguments are also expressions. Functions convert argument sets into a single expression (usually a value), though they are not limited to mathem<TextGroup><PlainText>at</PlainText></TextGroup>ical functions and the available set of functions is exte<TextGroup><PlainText>ns</PlainText></TextGroup>ible. For instance, the expression of the phenotype &#8216;Body Mass Index&#8217; can be expressed as follows: &#8216;quotient(weight, power(height, 2))&#8217;.</Pgraph><Pgraph>The TOP Framework implements a generic phenotype algorithm, which can be executed by selecting a desired phenotype model and defining (single or composite) phenotype classes as in- or exclusion criteria. Composite phenotypes can be traced back to singles from which they are derived. This results in a set of single phenotypes, which all have terminology annotations. For each of them, queries can be inferred that are translated to the respective query language of the source system and executed on the system. We assume that relevant data elements are available in structured form and are retrievable from data-holding systems (source system) with respective query languages. In the MII, Fast Healthcare Interoperability Resources (FHIR, <Hyperlink href="https:&#47;&#47;www.hl7.org&#47;fhir">https:&#47;&#47;www.hl7.org&#47;fhir</Hyperlink>), by the standardisation organisation Health Level 7, is used to make patient data from electronic health records accessible. And also, many research data management systems are using databases based on the Structured Query Language (SQL). We therefore focused on SQL database management systems and FHIR servers with FHIR Search (<Hyperlink href="https:&#47;&#47;www.hl7.org&#47;fhir&#47;search.html">https:&#47;&#47;www.hl7.org&#47;fhir&#47;search.html</Hyperlink>) support. The inference is done by generic or source system-specific adapters. For SQL and FHIR, we provide generic Java-based adapters based on <TextLink reference="4"></TextLink>, which are configurable by a mapping file. The query results are subsequently used to evaluate expressions of composite phenotypes.</Pgraph><Pgraph>The whole process of modelling phenotypes and executing phenotype algorithms is depicted in Figure 1 <ImgLink imgNo="1" imgType="figure"/> and can be carried out by domain experts. Only adapters and an optional source system mapping must be provided by IT specialists. The mapping associates the terminology codes of the phenotype classes in the phenotype model with the corresponding data elements contained in the source system, e.g. FHIR resource types like &#8216;Observation&#8217; and &#8216;Condition&#8217; or SQL database tables and columns. In addition, value ranges contained in the phenotype algorithm can be modified. This is especially helpful to customise an algorithm to facility-specific norm values like laboratory thresholds. If the terminology codes and also value ranges in the phenotype model and in the source system are identical, the mapping can be omitted.</Pgraph></TextBlock>
    <TextBlock linked="yes" name="Results">
      <MainHeadline>Results</MainHeadline><Pgraph>Based on the described methodological blueprint, we have developed an interactive web application, the TOP Framework (see Figure 2 <ImgLink imgNo="2" imgType="figure"/>). The framework is used by domain experts to develop phenotype models and execute phenotype algorithms. It consists of a JavaScript-based frontend, a Java Spring Backend, and a vendor-independent database. The framework can optionally be connected to an Ontology Lookup Service (version 3) <TextLink reference="9"></TextLink>. The main functions provided by the corresponding user interface elements or API are the following:</Pgraph><Pgraph><OrderedList><ListItem level="1" levelPosition="1" numString="1.">Developing phenotype models: Phenotype classes, attributes, relations, ranges, and expressions&#47;formulas can be structurally defined.</ListItem><ListItem level="1" levelPosition="2" numString="2.">Storing and exporting phenotype models: Phenotype models are stored in a relational database and can be exported in different formats (e.g., Ontology Web Language, CSV or Decision Model and Notation).</ListItem><ListItem level="1" levelPosition="3" numString="3.">Execution of phenotype algorithms:  Phenotype algorithms can be initiated by selecting a phenotype model (in-&#47;exclusion criteria) and a source system. Depending on the selected source system, a suitable adapter is used to translate and execute queries in source system-specific language.</ListItem><ListItem level="1" levelPosition="4" numString="4.">Providing results: The number of patients&#47;probands who fulfil all criteria of the phenotype model or also the corresponding data are provided in a machine and human readable format (e.g., CSV).</ListItem></OrderedList></Pgraph><Pgraph>Furthermore, the framework allows search in existing phenotype models and supports, among other things, the creation of expressions for composite phenotypes and thus ensures syntactic correctness. Frontend and backend communicate over an API (the API&#8217;s OpenAPI specification is available in <TextLink reference="10"></TextLink>), which can also be used to integrate backend functionalities into other software applications. </Pgraph><Pgraph>The framework was tested with randomly generated test data consisting of 10,000 patients with about 50,000 visits. We provided the data both in an SQL database and via a FHIR server and created corresponding mapping configurations. Queries to both source systems yielded identical result sets.</Pgraph></TextBlock>
    <TextBlock linked="yes" name="Discussion">
      <MainHeadline>Discussion</MainHeadline><Pgraph>Typically, bioinformaticians, statisticians and comparable groups of people are tasked with implementing algorithms to detect individuals with specific traits. Since domain experts (i.e., medical staff) must provide the knowledge to implement such algorithms, very close collaboration between both groups is required <TextLink reference="11"></TextLink>. Algorithms are often written in programming languages such as R, Python, Clinical Quality Language, which are more powerful and expressive than the TOP Framework but are not familiar to domain experts. As a result, there is no clear separation between modelling and implementation tasks. In addition, access to the source data must be implemented separately, e.g. using libraries such as FHIRcrackr <TextLink reference="12"></TextLink> or FHIR-PYrate <TextLink reference="13"></TextLink>. The TOP Framework can solve these issues by the described separation between phenotype models and phenotype algorithms. Consider phenotype models as different configurations applied to the generic phenotype algorithm described earlier. The framework provides a user interface suitable for domain experts to create such models and use them to compute or infer complex phenotypes for a given set of patient data, and to query patient data management systems for individuals with matching characteristics. Query results can be numbers of individuals or data sets containing selected patient characteristics for further statistical analysis. The approach of separating modelling and implementation tasks has been used previously by Uciteli et al. <TextLink reference="14"></TextLink>, <TextLink reference="15"></TextLink>, where ontological models built by domain experts were used to search text corpora and to identify perioperative risks.</Pgraph><Pgraph>The expressions used in the TOP Framework for modelling composite phenotypes are generic and thus suitable for mapping a large part, but not all, of the calculations and rules that occur in practice in algorithms. Some phenotypes can only be assessed using complex computations (e.g., Python and R scripts) or trained models (e.g., from machine learning). They are therefore not yet supported by the framework. In the future, we would like to integrate such complex calculations into the TOP Framework as external services.</Pgraph><Pgraph>The TOP Framework is a platform for easy definition of reusable phenotype models. All models can be accessed and referenced via URLs. However, the model is only partially standards compliant and introduces a proprietary format. To overcome this, we plan to extend the model with additional audit and metadata, and to enable automated transformation into community standard formats such as RDF with common annotations. This is in line with our commitment to the FAIR data principles <TextLink reference="16"></TextLink>.</Pgraph><Pgraph>The focus of our work was not to provide yet another query tool for patient and trial data, but to enable and encourage domain experts to build machine-readable and richly annotated models of phenotypes that can later be used to build queries. An initial overhead is required to build these models. Therefore, the framework does not support rapid query building as provided by tools such as FDPG <TextLink reference="2"></TextLink>, i2b2 <TextLink reference="17"></TextLink>, or tranSMART <TextLink reference="18"></TextLink>. But there is no need for complex ETL jobs to pre-process patient or trial data. All queries are generated in the source-specific language and can be executed directly on the source system. In this work, we have focused on the query languages FHIR Search and SQL. However, the concept described here can also be used in conjunction with other query languages by implementing appropriate query adapters. Admittedly, the required mapping to source systems may be difficult for some database schemas or APIs &#8211; or even impossible in some cases if essential data is missing (e.g., terminology codes). However, the resulting framework is lightweight and has no requirements for the storage of patient data, and aspects such as data privacy can be handled by the source systems.</Pgraph></TextBlock>
    <TextBlock linked="yes" name="Conclusions">
      <MainHeadline>Conclusions</MainHeadline><Pgraph>We have developed a methodology for modelling phenotypes and retrieving the corresponding data elements from patient data management systems and clinical research systems. The required tasks are clearly divided between domain experts and IT specialists. This computer-assisted approach can improve disease detection and clinical trial recruitment.</Pgraph></TextBlock>
    <TextBlock linked="yes" name="Notes">
      <MainHeadline>Notes</MainHeadline><SubHeadline>Terminology- and Ontology-based Phenotyping (TOP) Framework </SubHeadline><Pgraph>Source code for frontend and backend is available at <Hyperlink href="https:&#47;&#47;github.com&#47;Onto-Med&#47;top-frontend">https:&#47;&#47;github.com&#47;Onto-Med&#47;top-frontend</Hyperlink> and <Hyperlink href="https:&#47;&#47;github.com&#47;Onto-Med&#47;top-backend">https:&#47;&#47;github.com&#47;Onto-Med&#47;top-backend</Hyperlink>. A user manual can be found at <Hyperlink href="https:&#47;&#47;onto-med.github.io&#47;top-deployment">https:&#47;&#47;onto-med.github.io&#47;top-deployment</Hyperlink>.</Pgraph><SubHeadline>Competing interests</SubHeadline><Pgraph>The authors declare that they have no competing interests.</Pgraph><SubHeadline>Funding</SubHeadline><Pgraph>This work was supported by the German Federal Ministry of Education and Research as part of the projects SMITH TOP (reference number: 01ZZ2018) and SMITH (reference number: 01ZZ1803A).</Pgraph></TextBlock>
    <References linked="yes">
      <Reference refNo="1">
        <RefAuthor>Thadani SR</RefAuthor>
        <RefAuthor>Weng C</RefAuthor>
        <RefAuthor>Bigger JT</RefAuthor>
        <RefAuthor>Ennever JF</RefAuthor>
        <RefAuthor>Wajngurt D</RefAuthor>
        <RefTitle>Electronic screening improves efficiency in clinical trial recruitment</RefTitle>
        <RefYear>2009</RefYear>
        <RefJournal>J Am Med Inform Assoc</RefJournal>
        <RefPage>869-73</RefPage>
        <RefTotal>Thadani SR, Weng C, Bigger JT, Ennever JF, Wajngurt D. Electronic screening improves efficiency in clinical trial recruitment. J Am Med Inform Assoc. 2009;16(6):869-73. 
DOI: 10.1197&#47;jamia.M3119</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1197&#47;jamia.M3119</RefLink>
      </Reference>
      <Reference refNo="2">
        <RefAuthor>Prokosch HU</RefAuthor>
        <RefAuthor>Gebhardt M</RefAuthor>
        <RefAuthor>Gruendner J</RefAuthor>
        <RefAuthor>Kleinert P</RefAuthor>
        <RefAuthor>Buckow K</RefAuthor>
        <RefAuthor>Rosenau L</RefAuthor>
        <RefAuthor>Semler SC</RefAuthor>
        <RefTitle>Towards a National Portal for Medical Research Data (FDPG): Vision, Status, and Lessons Learned</RefTitle>
        <RefYear>2023</RefYear>
        <RefJournal>Stud Health Technol Inform</RefJournal>
        <RefPage>307-11</RefPage>
        <RefTotal>Prokosch HU, Gebhardt M, Gruendner J, Kleinert P, Buckow K, Rosenau L, Semler SC. Towards a National Portal for Medical Research Data (FDPG): Vision, Status, and Lessons Learned. Stud Health Technol Inform. 2023 May 18;302:307-11. 
DOI: 10.3233&#47;SHTI230124</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.3233&#47;SHTI230124</RefLink>
      </Reference>
      <Reference refNo="3">
        <RefAuthor>Scheuermann RH</RefAuthor>
        <RefAuthor>Ceusters W</RefAuthor>
        <RefAuthor>Smith B</RefAuthor>
        <RefTitle>Toward an ontological treatment of disease and diagnosis</RefTitle>
        <RefYear>2009</RefYear>
        <RefJournal>Summit Transl Bioinform</RefJournal>
        <RefPage>116-20</RefPage>
        <RefTotal>Scheuermann RH, Ceusters W, Smith B. Toward an ontological treatment of disease and diagnosis. Summit Transl Bioinform. 2009 Mar 1;2009:116-20. </RefTotal>
      </Reference>
      <Reference refNo="4">
        <RefAuthor>Beger C</RefAuthor>
        <RefAuthor>Matthies F</RefAuthor>
        <RefAuthor>Sch&#228;fermeier R</RefAuthor>
        <RefAuthor>Kirsten T</RefAuthor>
        <RefAuthor>Herre H</RefAuthor>
        <RefAuthor>Uciteli A</RefAuthor>
        <RefTitle>Towards an Ontology-Based Phenotypic Query Model</RefTitle>
        <RefYear>2022</RefYear>
        <RefJournal>Appl Sci</RefJournal>
        <RefPage>5214</RefPage>
        <RefTotal>Beger C, Matthies F, Sch&#228;fermeier R, Kirsten T, Herre H, Uciteli A. Towards an Ontology-Based Phenotypic Query Model. Appl Sci. 2022 May 21;12(10):5214. DOI: 10.3390&#47;app12105214</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.3390&#47;app12105214</RefLink>
      </Reference>
      <Reference refNo="5">
        <RefAuthor>Wei WQ</RefAuthor>
        <RefAuthor>Denny JC</RefAuthor>
        <RefTitle>Extracting research-quality phenotypes from electronic health records to support precision medicine</RefTitle>
        <RefYear>2015</RefYear>
        <RefJournal>Genome Med</RefJournal>
        <RefPage>41</RefPage>
        <RefTotal>Wei WQ, Denny JC. Extracting research-quality phenotypes from electronic health records to support precision medicine. Genome Med. 2015;7(1):41. DOI: 10.1186&#47;s13073-015-0166-y</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1186&#47;s13073-015-0166-y</RefLink>
      </Reference>
      <Reference refNo="6">
        <RefAuthor>Pathak J</RefAuthor>
        <RefAuthor>Kho AN</RefAuthor>
        <RefAuthor>Denny JC</RefAuthor>
        <RefTitle>Electronic health records-driven phenotyping: challenges, recent advances, and perspectives</RefTitle>
        <RefYear>2013</RefYear>
        <RefJournal>J Am Med Inform Assoc</RefJournal>
        <RefPage>e206-11</RefPage>
        <RefTotal>Pathak J, Kho AN, Denny JC. Electronic health records-driven phenotyping: challenges, recent advances, and perspectives. 
J Am Med Inform Assoc. 2013 Dec;20(e2):e206-11. 
DOI: 10.1136&#47;amiajnl-2013-002428</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1136&#47;amiajnl-2013-002428</RefLink>
      </Reference>
      <Reference refNo="7">
        <RefAuthor>Zhang H</RefAuthor>
        <RefAuthor>He Z</RefAuthor>
        <RefAuthor>He X</RefAuthor>
        <RefAuthor>Guo Y</RefAuthor>
        <RefAuthor>Nelson DR</RefAuthor>
        <RefAuthor>Modave F</RefAuthor>
        <RefAuthor>Wu Y</RefAuthor>
        <RefAuthor>Hogan W</RefAuthor>
        <RefAuthor>Prosperi M</RefAuthor>
        <RefAuthor>Bian J</RefAuthor>
        <RefTitle>Computable Eligibility Criteria through Ontology-driven Data Access: A Case Study of Hepatitis C Virus Trials</RefTitle>
        <RefYear>2018</RefYear>
        <RefJournal>AMIA Annu Symp Proc</RefJournal>
        <RefPage>1601-10</RefPage>
        <RefTotal>Zhang H, He Z, He X, Guo Y, Nelson DR, Modave F, Wu Y, Hogan W, Prosperi M, Bian J. Computable Eligibility Criteria through Ontology-driven Data Access: A Case Study of Hepatitis C Virus Trials. AMIA Annu Symp Proc. 2018 Dec 5;2018:1601-10. </RefTotal>
      </Reference>
      <Reference refNo="8">
        <RefAuthor>Uciteli A</RefAuthor>
        <RefAuthor>Beger C</RefAuthor>
        <RefAuthor>Kirsten T</RefAuthor>
        <RefAuthor>Meineke FA</RefAuthor>
        <RefAuthor>Herre H</RefAuthor>
        <RefTitle>Ontological representation, classification and data-driven computing of phenotypes</RefTitle>
        <RefYear>2020</RefYear>
        <RefJournal>J Biomed Semantics</RefJournal>
        <RefPage>15</RefPage>
        <RefTotal>Uciteli A, Beger C, Kirsten T, Meineke FA, Herre H. Ontological representation, classification and data-driven computing of phenotypes. J Biomed Semantics. 2020 Dec;11(1):15. 
DOI: 10.1186&#47;s13326-020-00230-0</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1186&#47;s13326-020-00230-0</RefLink>
      </Reference>
      <Reference refNo="9">
        <RefAuthor>Jupp S</RefAuthor>
        <RefAuthor>Burdett T</RefAuthor>
        <RefAuthor>Leroy C</RefAuthor>
        <RefAuthor>Parkinson HE</RefAuthor>
        <RefTitle>A new Ontology Lookup Service at EMBL-EBI</RefTitle>
        <RefYear></RefYear>
        <RefBookTitle>Proceedings of the 8th International Conference on Semantic Web Applications and Tools for Life Sciences (SWAT4LS 2015); 2015 Dec 7-10; Cambridge, UK</RefBookTitle>
        <RefPage>118-9</RefPage>
        <RefTotal>Jupp S, Burdett T, Leroy C, Parkinson HE. A new Ontology Lookup Service at EMBL-EBI. In: Malone J, Stevens R, Forsberg K, Splendiani A, editors. Proceedings of the 8th International Conference on Semantic Web Applications and Tools for Life Sciences (SWAT4LS 2015); 2015 Dec 7-10; Cambridge, UK. 
p. 118-9. URN: urn:nbn:de:0074-1546-1</RefTotal>
        <RefLink>https:&#47;&#47;nbn-resolving.org&#47;urn:nbn:de:0074-1546-1</RefLink>
      </Reference>
      <Reference refNo="10">
        <RefAuthor>Beger C</RefAuthor>
        <RefAuthor>Matthies F</RefAuthor>
        <RefTitle></RefTitle>
        <RefYear>2023</RefYear>
        <RefBookTitle>Onto-Med&#47;top-api</RefBookTitle>
        <RefPage></RefPage>
        <RefTotal>Beger C, Matthies F. Onto-Med&#47;top-api. Version v0.7.6. Zenodo; 2023 May 5.  DOI: 10.5281&#47;zenodo.7900530</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.5281&#47;zenodo.7900530</RefLink>
      </Reference>
      <Reference refNo="11">
        <RefAuthor>Hruby GW</RefAuthor>
        <RefAuthor>Boland MR</RefAuthor>
        <RefAuthor>Cimino JJ</RefAuthor>
        <RefAuthor>Gao J</RefAuthor>
        <RefAuthor>Wilcox AB</RefAuthor>
        <RefAuthor>Hirschberg J</RefAuthor>
        <RefAuthor>Weng C</RefAuthor>
        <RefTitle>Characterization of the biomedical query mediation process</RefTitle>
        <RefYear>2013</RefYear>
        <RefJournal>AMIA Jt Summits Transl Sci Proc</RefJournal>
        <RefPage>89-93</RefPage>
        <RefTotal>Hruby GW, Boland MR, Cimino JJ, Gao J, Wilcox AB, Hirschberg J, Weng C. Characterization of the biomedical query mediation process. AMIA Jt Summits Transl Sci Proc. 2013 Mar 18;2013:89-93. </RefTotal>
      </Reference>
      <Reference refNo="12">
        <RefAuthor>Palm J</RefAuthor>
        <RefAuthor>Meineke FA</RefAuthor>
        <RefAuthor>Przybilla J</RefAuthor>
        <RefAuthor>Peschel T</RefAuthor>
        <RefTitle>&#8220;fhircrackr&#8221;: An R Package Unlocking Fast Healthcare Interoperability Resources for Statistical Analysis</RefTitle>
        <RefYear>2023</RefYear>
        <RefJournal>Appl Clin Inform</RefJournal>
        <RefPage>54-64</RefPage>
        <RefTotal>Palm J, Meineke FA, Przybilla J, Peschel T. &#8220;fhircrackr&#8221;: An R Package Unlocking Fast Healthcare Interoperability Resources for Statistical Analysis. Appl Clin Inform. 2023 Jan;14(1):54-64. DOI: 10.1055&#47;s-0042-1760436</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1055&#47;s-0042-1760436</RefLink>
      </Reference>
      <Reference refNo="13">
        <RefAuthor>Hosch R</RefAuthor>
        <RefAuthor>Baldini G</RefAuthor>
        <RefAuthor>Parmar V</RefAuthor>
        <RefAuthor>Borys K</RefAuthor>
        <RefAuthor>Koitka S</RefAuthor>
        <RefAuthor>Engelke M</RefAuthor>
        <RefAuthor>Arzideh K</RefAuthor>
        <RefAuthor>Ulrich M</RefAuthor>
        <RefAuthor>Nensa F</RefAuthor>
        <RefTitle>FHIR-PYrate: a data science friendly Python package to query FHIR servers</RefTitle>
        <RefYear>2023</RefYear>
        <RefJournal>BMC Health Serv Res</RefJournal>
        <RefPage>734</RefPage>
        <RefTotal>Hosch R, Baldini G, Parmar V, Borys K, Koitka S, Engelke M, Arzideh K, Ulrich M, Nensa F. FHIR-PYrate: a data science friendly Python package to query FHIR servers. BMC Health Serv Res. 2023 Jul;23(1):734. DOI: 10.1186&#47;s12913-023-09498-1</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1186&#47;s12913-023-09498-1</RefLink>
      </Reference>
      <Reference refNo="14">
        <RefAuthor>Uciteli A</RefAuthor>
        <RefAuthor>Kropf S</RefAuthor>
        <RefAuthor>Weiland T</RefAuthor>
        <RefAuthor>Meese S</RefAuthor>
        <RefAuthor>Graef K</RefAuthor>
        <RefAuthor>Rohrer S</RefAuthor>
        <RefAuthor>Schurr MO</RefAuthor>
        <RefAuthor>Bartussek W</RefAuthor>
        <RefAuthor>Goller C</RefAuthor>
        <RefAuthor>Blohm P</RefAuthor>
        <RefAuthor>Seidel R</RefAuthor>
        <RefAuthor>Bayer C</RefAuthor>
        <RefAuthor>Kernenbach M</RefAuthor>
        <RefAuthor>Pfeiffer K</RefAuthor>
        <RefAuthor>Lauer W</RefAuthor>
        <RefAuthor>Meyer JU</RefAuthor>
        <RefAuthor>Witte M</RefAuthor>
        <RefAuthor>Herre H</RefAuthor>
        <RefTitle>Ontology-based specification and generation of search queries for post-market surveillance</RefTitle>
        <RefYear>2019</RefYear>
        <RefJournal>J Biomed Semantics</RefJournal>
        <RefPage>9</RefPage>
        <RefTotal>Uciteli A, Kropf S, Weiland T, Meese S, Graef K, Rohrer S, Schurr MO, Bartussek W, Goller C, Blohm P, Seidel R, Bayer C, Kernenbach M, Pfeiffer K, Lauer W, Meyer JU, Witte M, Herre H. Ontology-based specification and generation of search queries for post-market surveillance. J Biomed Semantics. 2019 May;10(1):9. DOI: 10.1186&#47;s13326-019-0203-7</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1186&#47;s13326-019-0203-7</RefLink>
      </Reference>
      <Reference refNo="15">
        <RefAuthor>Uciteli A</RefAuthor>
        <RefAuthor>Neumann J</RefAuthor>
        <RefAuthor>Tahar K</RefAuthor>
        <RefAuthor>Saleh K</RefAuthor>
        <RefAuthor>Stucke S</RefAuthor>
        <RefAuthor>Faulbr&#252;ck-R&#246;hr S</RefAuthor>
        <RefAuthor>Kaeding A</RefAuthor>
        <RefAuthor>Specht M</RefAuthor>
        <RefAuthor>Schmidt T</RefAuthor>
        <RefAuthor>Neumuth T</RefAuthor>
        <RefAuthor>Besting A</RefAuthor>
        <RefAuthor>Stegemann D</RefAuthor>
        <RefAuthor>Portheine F</RefAuthor>
        <RefAuthor>Herre H</RefAuthor>
        <RefTitle>Ontology-based specification, identification and analysis of perioperative risks</RefTitle>
        <RefYear>2017</RefYear>
        <RefJournal>J Biomed Semantics</RefJournal>
        <RefPage>36</RefPage>
        <RefTotal>Uciteli A, Neumann J, Tahar K, Saleh K, Stucke S, Faulbr&#252;ck-R&#246;hr S, Kaeding A, Specht M, Schmidt T, Neumuth T, Besting A, Stegemann D, Portheine F, Herre H. Ontology-based specification, identification and analysis of perioperative risks. J Biomed Semantics. 2017 Sep;8(1):36. DOI: 10.1186&#47;s13326-017-0147-8</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1186&#47;s13326-017-0147-8</RefLink>
      </Reference>
      <Reference refNo="16">
        <RefAuthor>Wilkinson MD</RefAuthor>
        <RefAuthor>Dumontier M</RefAuthor>
        <RefAuthor>Aalbersberg IJ</RefAuthor>
        <RefAuthor>Appleton G</RefAuthor>
        <RefAuthor>Axton M</RefAuthor>
        <RefAuthor>Baak A</RefAuthor>
        <RefAuthor>Blomberg N</RefAuthor>
        <RefAuthor>Boiten JW</RefAuthor>
        <RefAuthor>da Silva Santos LB</RefAuthor>
        <RefAuthor>Bourne PE</RefAuthor>
        <RefAuthor>Bouwman J</RefAuthor>
        <RefAuthor>Brookes AJ</RefAuthor>
        <RefAuthor>Clark T</RefAuthor>
        <RefAuthor>Crosas M</RefAuthor>
        <RefAuthor>Dillo I</RefAuthor>
        <RefAuthor>Dumon O</RefAuthor>
        <RefAuthor>Edmunds S</RefAuthor>
        <RefAuthor>Evelo CT</RefAuthor>
        <RefAuthor>Finkers R</RefAuthor>
        <RefAuthor>Gonzalez-Beltran A</RefAuthor>
        <RefAuthor>Gray AJ</RefAuthor>
        <RefAuthor>Groth P</RefAuthor>
        <RefAuthor>Goble C</RefAuthor>
        <RefAuthor>Grethe JS</RefAuthor>
        <RefAuthor>Heringa J</RefAuthor>
        <RefAuthor>&#39;t Hoen PA</RefAuthor>
        <RefAuthor>Hooft R</RefAuthor>
        <RefAuthor>Kuhn T</RefAuthor>
        <RefAuthor>Kok R</RefAuthor>
        <RefAuthor>Kok J</RefAuthor>
        <RefAuthor>Lusher SJ</RefAuthor>
        <RefAuthor>Martone ME</RefAuthor>
        <RefAuthor>Mons A</RefAuthor>
        <RefAuthor>Packer AL</RefAuthor>
        <RefAuthor>Persson B</RefAuthor>
        <RefAuthor>Rocca-Serra P</RefAuthor>
        <RefAuthor>Roos M</RefAuthor>
        <RefAuthor>van Schaik R</RefAuthor>
        <RefAuthor>Sansone SA</RefAuthor>
        <RefAuthor>Schultes E</RefAuthor>
        <RefAuthor>Sengstag T</RefAuthor>
        <RefAuthor>Slater T</RefAuthor>
        <RefAuthor>Strawn G</RefAuthor>
        <RefAuthor>Swertz MA</RefAuthor>
        <RefAuthor>Thompson M</RefAuthor>
        <RefAuthor>van der Lei J</RefAuthor>
        <RefAuthor>van Mulligen E</RefAuthor>
        <RefAuthor>Velterop J</RefAuthor>
        <RefAuthor>Waagmeester A</RefAuthor>
        <RefAuthor>Wittenburg P</RefAuthor>
        <RefAuthor>Wolstencroft K</RefAuthor>
        <RefAuthor>Zhao J</RefAuthor>
        <RefAuthor>Mons B</RefAuthor>
        <RefTitle>The FAIR Guiding Principles for scientific data management and stewardship</RefTitle>
        <RefYear>2016</RefYear>
        <RefJournal>Sci Data</RefJournal>
        <RefPage>160018</RefPage>
        <RefTotal>Wilkinson MD, Dumontier M, Aalbersberg IJ, Appleton G, Axton M, Baak A, Blomberg N, Boiten JW, da Silva Santos LB, Bourne PE, Bouwman J, Brookes AJ, Clark T, Crosas M, Dillo I, Dumon O, Edmunds S, Evelo CT, Finkers R, Gonzalez-Beltran A, Gray AJ, Groth P, Goble C, Grethe JS, Heringa J, &#39;t Hoen PA, Hooft R, Kuhn T, Kok R, Kok J, Lusher SJ, Martone ME, Mons A, Packer AL, Persson B, Rocca-Serra P, Roos M, van Schaik R, Sansone SA, Schultes E, Sengstag T, Slater T, Strawn G, Swertz MA, Thompson M, van der Lei J, van Mulligen E, Velterop J, Waagmeester A, Wittenburg P, Wolstencroft K, Zhao J, Mons B. The FAIR Guiding Principles for scientific data management and stewardship. Sci Data. 2016 Mar 15;3:160018. DOI: 10.1038&#47;sdata.2016.18</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1038&#47;sdata.2016.18</RefLink>
      </Reference>
      <Reference refNo="17">
        <RefAuthor>Murphy SN</RefAuthor>
        <RefAuthor>Weber G</RefAuthor>
        <RefAuthor>Mendis M</RefAuthor>
        <RefAuthor>Gainer V</RefAuthor>
        <RefAuthor>Chueh HC</RefAuthor>
        <RefAuthor>Churchill S</RefAuthor>
        <RefAuthor>Kohane I</RefAuthor>
        <RefTitle>Serving the enterprise and beyond with informatics for integrating biology and the bedside (i2b2)</RefTitle>
        <RefYear>2010</RefYear>
        <RefJournal>J Am Med Inform Assoc</RefJournal>
        <RefPage>124-30</RefPage>
        <RefTotal>Murphy SN, Weber G, Mendis M, Gainer V, Chueh HC, Churchill S, Kohane I. Serving the enterprise and beyond with informatics for integrating biology and the bedside (i2b2). J Am Med Inform Assoc. 2010;17(2):124-30. DOI: 10.1136&#47;jamia.2009.000893</RefTotal>
        <RefLink>https:&#47;&#47;doi.org&#47;10.1136&#47;jamia.2009.000893</RefLink>
      </Reference>
      <Reference refNo="18">
        <RefAuthor>Athey BD</RefAuthor>
        <RefAuthor>Braxenthaler M</RefAuthor>
        <RefAuthor>Haas M</RefAuthor>
        <RefAuthor>Guo Y</RefAuthor>
        <RefTitle>tranSMART: An Open Source and Community-Driven Informatics and Data Sharing Platform for Clinical and Translational Research</RefTitle>
        <RefYear>2013</RefYear>
        <RefJournal>AMIA Jt Summits Transl Sci Proc</RefJournal>
        <RefPage>6-8</RefPage>
        <RefTotal>Athey BD, Braxenthaler M, Haas M, Guo Y. tranSMART: An Open Source and Community-Driven Informatics and Data Sharing Platform for Clinical and Translational Research. AMIA Jt Summits Transl Sci Proc. 2013 Mar 18;2013:6-8. </RefTotal>
      </Reference>
    </References>
    <Media>
      <Tables>
        <NoOfTables>0</NoOfTables>
      </Tables>
      <Figures>
        <Figure format="png" height="583" width="1140">
          <MediaNo>1</MediaNo>
          <MediaID>1</MediaID>
          <Caption><Pgraph><Mark1>Figure 1: Overview of the TOP Framework. Domain experts use the graphical user interface to browse existing phenotype classes, create new ones and execute algorithms based on them. IT specialists provide data source adapters and mappings that enable generating source system-specific queries. External terminology servers can be incorporated.</Mark1></Pgraph></Caption>
        </Figure>
        <Figure format="png" height="734" width="1163">
          <MediaNo>2</MediaNo>
          <MediaID>2</MediaID>
          <Caption><Pgraph><Mark1>Figure 2: Screenshot of the TOP Framework web application. Shown is the repository &#8216;BMI Example&#8217; that contains a simple phenotype model of the body mass index (BMI). On the left side, all phenotype definitions contained in the repository are displayed in a tree structure. And on the right side, a form to edit the definition of the phenotype &#8216;BMI&#8217; is shown.</Mark1></Pgraph></Caption>
        </Figure>
        <NoOfPictures>2</NoOfPictures>
      </Figures>
      <InlineFigures>
        <NoOfPictures>0</NoOfPictures>
      </InlineFigures>
      <Attachments>
        <NoOfAttachments>0</NoOfAttachments>
      </Attachments>
    </Media>
  </OrigData>
</GmsArticle>