<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">The approach of IQVIA to ontologies for healthcare and life sciences</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Andrea</forename><surname>Splendiani</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">IQVIA</orgName>
								<address>
									<addrLine>Kirschgartenstrasse 14</addrLine>
									<settlement>Basel</settlement>
									<country key="CH">Switzerland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Emiliano</forename><surname>Reynares</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">IQVIA</orgName>
								<address>
									<addrLine>Provença 392</addrLine>
									<settlement>Barcelona</settlement>
									<country key="ES">Spain</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Anthony</forename><surname>Reckard</surname></persName>
							<affiliation key="aff2">
								<orgName type="institution">IQVIA</orgName>
								<address>
									<addrLine>Mission Street 123</addrLine>
									<settlement>San Francisco</settlement>
									<region>CA</region>
									<country>United States of America</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">The approach of IQVIA to ontologies for healthcare and life sciences</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">9D711974276831E71A20DC85BD5B27C3</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:40+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Ontology</term>
					<term>knowledge graph</term>
					<term>healthcare</term>
					<term>life sciences</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><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></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Ontologies are broadly used across healthcare and life sciences. As a healthcare data company covering pharma, from early clinical development to market access as well as healthcare delivery, IQVIA makes an extensive usage of ontologies: for data harmonization (e.g.: OMOP <ref type="bibr" target="#b0">[1]</ref>), regulatory submission support (e.g.: CDISC <ref type="bibr" target="#b1">[2]</ref>), to structure data through NLP pipelines and to drive analytics (e.g.: population definitions).</p><p>The "ontology architecture" of IQVIA can be considered made of three parts, as illustrated below (for a sample of geographies and domains). andrea.splendiani@iqvia.com (A. Splendiani); emiliano.reynares@iqvia.com (E. Reynares); anthony.reckard@iqvia.com (A. Reckard) 0000-0002-3201-9617 (A. Splendiani); 0000-0002-5109-3716 (E. Reynares)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.1.">Standard ontologies</head><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 <ref type="bibr" target="#b2">[3]</ref> (research), ATC <ref type="bibr" target="#b3">[4]</ref> (therapeutic classification), RxNorm <ref type="bibr" target="#b4">[5]</ref> (products) and more.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.2.">Ontologies and reference data in use</head><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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.3.">The last mile</head><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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.4.">Future developments</head><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></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Examples of types of IQVIA ontology assets for selected resources and domains</figDesc><graphic coords="1,79.78,441.26,435.42,183.40" type="bitmap" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Standardized Data: The OMOP Common Data Model</title>
		<author>
			<persName><surname>Ohdsi</surname></persName>
		</author>
		<ptr target="https://www.ohdsi.org/data-standardization/" />
		<imprint>
			<date type="published" when="2023-12">December 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Clinical Data Interchange Standards Consortium (CDISC)</title>
		<ptr target="https://www.cdisc.org/" />
		<imprint>
			<date type="published" when="2023-12">December 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<ptr target="https://www.ebi.ac.uk/chebi/" />
		<title level="m">Chemical Entities of Biological Interest</title>
				<imprint>
			<publisher>ChEBI</publisher>
			<date type="published" when="2023-12">December 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<ptr target="https://www.who.int/tools/atc-ddd-toolkit/atc-classification" />
		<title level="m">World Health Organization (WHO): Anatomical Therapeutical Chemical Classification (ATC)</title>
				<imprint>
			<date type="published" when="2023-12">December 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">): RxNorm</title>
		<ptr target="https://www.nlm.nih.gov/research/umls/rxnorm/overview.html" />
		<imprint>
			<date type="published" when="2023-12">December 2023</date>
			<publisher>NLM</publisher>
		</imprint>
		<respStmt>
			<orgName>National Library of Medicine</orgName>
		</respStmt>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
