<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The approach of IQVIA to ontologies for healthcare and life sciences</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andrea Splendiani</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Emiliano Reynares</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anthony Reckard</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IQVIA</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kirschgartenstrasse</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Basel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Switzerland</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IQVIA</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Provença</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Barcelona</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Spain</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IQVIA</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mission Street</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>San Francisco</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>United States of America</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>and Life Sciences</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>IQVIA is a healthcare data company that processes yearly over 100B health records from 1M+ distinct data feeds, addressing use cases from clinical development to real world evidence and market access. Ontologies are in use extensively to structure and unify this data space. In this contribution, we intend to present how the company uses ontologies: what standard ontologies are integrated, what gaps exist and what custom solutions need to be developed.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Ontology</kwd>
        <kwd>knowledge graph</kwd>
        <kwd>healthcare</kwd>
        <kwd>life sciences</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1. Introduction</p>
    </sec>
    <sec id="sec-2">
      <title>1.1. Standard ontologies</title>
      <p>
        At the bottom, IQVIA makes use of ontologies that are “standard”: either public or provided by
third parties, these are shared among different actors of the healthcare ecosystem and constitute
the basis for interoperability. The breadth of operations of IQVIA consider ontologies (or
reference data) from many different perspectives. For instance, products may make use of as
diverse resources as ChEBI [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] (research), ATC [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] (therapeutic classification), RxNorm [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
(products) and more.
      </p>
    </sec>
    <sec id="sec-3">
      <title>1.2. Ontologies and reference data in use</title>
      <p>In addition to this, IQVIA collects and integrate reference data from its massive health record
ingestion processes. This results in extended resources, such a regional name variation for
products, or typical references in prescriptions, or even products for which standard
nomenclatures are not present (e.g.: lab supplies).</p>
      <p>It is interesting to note that while ontologies represent the standard “as proposed”, this
extensive collection results in a view of the standard “as used”, including an understanding of
what granularities exist, what is updated when and so on.</p>
    </sec>
    <sec id="sec-4">
      <title>1.3. The last mile</title>
      <p>Finally, as an analytics company, IQVIA goes the “last mile” to complement current ontological
resources to support analytics. This involves developing knowledge graphs that allow for
navigation across ontology versions, even those that are over a decade old, to support the creation
of longitudinal patient data. Additionally, custom ontologies are on development to mine
patientreported outcomes or social media for sentiment analysis.</p>
      <p>This includes for instance the development of knowledge graphs enabling the navigation
across ontology versions (sometimes beyond a decade) to support patient’s longitudinal data
creation, or the development of custom ontologies to, for instance, mine patients reported
outcome or social media for sentiment analysis.</p>
    </sec>
    <sec id="sec-5">
      <title>1.4. Future developments</title>
      <p>With this contribution we intend to present our assets and expertise in the ontology space,
and invite the interested parties to kick off a discussion on how to leverage such resources (e.g.:
extensive observation of ontology use in the field) and advance the current state of the art.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>OHDSI</given-names>
            ,
            <surname>Standardized</surname>
          </string-name>
          <string-name>
            <surname>Data</surname>
          </string-name>
          :
          <article-title>The OMOP Common Data Model. Accessed in December 2023</article-title>
          . URL: https://www.ohdsi.org/data-standardization/.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Clinical</given-names>
            <surname>Data Interchange Standards</surname>
          </string-name>
          <article-title>Consortium (CDISC). Accessed in December 2023</article-title>
          . URL: https://www.cdisc.org/.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>[3] Chemical Entities of Biological Interest (ChEBI)</article-title>
          .
          <source>Accessed in December</source>
          <year>2023</year>
          . URL: https://www.ebi.ac.uk/chebi/.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>World</given-names>
            <surname>Health</surname>
          </string-name>
          <article-title>Organization (WHO): Anatomical Therapeutical Chemical Classification (ATC). Accessed in December 2023</article-title>
          . URL: https://www.who.int/tools/atc-ddd-toolkit/atcclassification.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>[5] National Library of Medicine (NLM): RxNorm. Accessed in December 2023</article-title>
          . URL: https://www.nlm.nih.gov/research/umls/rxnorm/overview.html.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>