<?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">Comparing the representation of medicinal products in RxNorm and SNOMED CT -Consequences on interoperability</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Jean</forename><forename type="middle">Noel</forename><surname>Nikiema</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">ERIAS</orgName>
								<orgName type="laboratory" key="lab1">Bordeaux Population Health Research Center</orgName>
								<orgName type="laboratory" key="lab2">UMR 1219</orgName>
								<orgName type="institution" key="instit1">Univ. Bordeaux</orgName>
								<orgName type="institution" key="instit2">Inserm</orgName>
								<address>
									<postCode>F-33000</postCode>
									<settlement>Bordeaux</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Olivier</forename><surname>Bodenreider</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">U.S. National Library of Medicine National Institutes of Health Bethesda</orgName>
								<address>
									<settlement>Maryland</settlement>
									<country key="US">USA</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Comparing the representation of medicinal products in RxNorm and SNOMED CT -Consequences on interoperability</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">A20EA317DA8B05E8C34E13B8EA353D2C</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T00:48+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>RxNorm</term>
					<term>SNOMED CT</term>
					<term>medicinal products</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Objectives: To compare the representation of medicinal products in RxNorm and SNOMED CT and assess the consequences on interoperability. Methods: To compare the two models, we manually establish equivalences between the types and definitional features of medicinal products entities in RxNorm and SNOMED CT. We highlight their similarities and differences. Results: Both models share major definitional features including ingredient (or substance), strength and dose form. SNOMED CT is more rigorous and better aligned with international standards. In contrast, RxNorm contains implicit knowledge, simplifications and ambiguities, but its model is simpler. Conclusions: Since their models are largely compatible, medicinal products from RxNorm and SNOMED CT are expected to be interoperable. However, specific aspects of the alignment between the two models require particular attention.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Background</head><p>Drug terminologies, such as RxNorm and the medicinal product hierarchy of SNOMED CT (Systematized Nomenclature of Medicine-Clinical Terms), support multiple use cases, including electronic prescription, drug information exchange, medication reconciliation, and analytics (including pharmacovigilance) <ref type="bibr" target="#b0">(1,</ref><ref type="bibr" target="#b1">2)</ref>. A formal representation of medicinal products is needed for the principled development and maintenance of such drug terminologies, as well as for precisely aligning existing drug terminologies <ref type="bibr" target="#b2">(3)</ref>. Many definitional characteristics of medicinal products are similar among drug terminologies. For example, clinical drugs are generally defined in terms of ingredient, strength and dose form. However, the level of formality and the formalism used for representing medicinal products may differ among terminologies. Some attributes may also be specific to some terminologies (especially for country-dependent attributes, such as packaging information). In addition to existing drug terminologies, international standards have been developed for the representation of medicinal products, such as IDMP (Identification of Medicinal Products). IDMP (4), a collection of recommendations from the International Standards Organization (ISO).</p><p>Interoperability among drug terminologies is especially important for exchanging drug information internationally. For example, a medication list established with RxNorm in the U.S. could be made available to any electronic health record (EHR) system in the world, in which drugs are represented using SNOMED CT. To fully support this use case, however, the models of medicinal products in RxNorm and SNOMED CT must be compatible, such that one can be accurately translated into the other. We focus on RxNorm and SNOMED CT, because RxNorm is the standard drug terminology in the U.S. and SNOMED CT is the largest clinical terminology in the world, supported by a consortium of over 40 countries. While the RxNorm model has been analyzed <ref type="bibr" target="#b4">(5,</ref><ref type="bibr" target="#b5">6)</ref>, and reused to create others standards <ref type="bibr" target="#b6">(7,</ref><ref type="bibr" target="#b7">8)</ref> and to integrate drug terminologies worldwide (8), there has not been a detailed comparison between RxNorm and SNOMED CT. Moreover, the SNOMED CT model for medicinal products is particularly interesting, because it was recently updated, in part to comply with IDMP requirements <ref type="bibr" target="#b8">(9)</ref>. In this investigation, we compare the representation of medicinal products in RxNorm and SNOMED CT. The objective of our work is to analyze their similarities and differences and the consequences of these differences on interoperability between the two terminologies.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Methods and results</head><p>In this section, we describe the models of RxNorm and SNOMED CT with focus on their definitional characteristics. Then we identify similarities and differences between the two models.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>The SNOMED CT model for medicinal products</head><p>The SNOMED CT, the largest clinical terminology in the world, is an international clinical terminology based on a formal concept model <ref type="bibr" target="#b9">(10)</ref>. SNOMED CT recently published a new model for the representation of medicinal products integrating requirements from IDMP <ref type="bibr" target="#b8">(9)</ref>. The model was developed to support international usage. Therefore, it is restricted to generic drugs and does not represent packaging information or branded drugs, which tend to be country-specific. In accordance with requirements from IDMP, clinical drugs are represented in a closed worldview. This means that characteristics used to define clinical drugs must be sufficient and what is not stated is false. In contrast, in the open worldview, what is not</p><p>Copyright © 2019 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0). stated is potentially true. For example, the representation of a clinical drug containing Atorvastatin must clearly state that this product only contains the substance Atorvastatin as its active ingredient (i.e., without any other active ingredient). In the open worldview, products containing Atorvastatin could also contain other active ingredients, e.g., Amlodipine. As shown in Figure <ref type="figure" target="#fig_1">1</ref>, the representation of medicinal products in SNOMED CT is based on a model with six <ref type="bibr" target="#b5">(6)</ref>     </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Closed-world entities</head><p>Closed-worldview are "closed" with respect to their active ingredient(s). More specifically, medicinal product and medicinal product form entities are closed with respect to their active ingredient(s), while medicinal product precisely and clinical drug entities are closed with respect to their precise active ingredient(s). There are no hierarchical relations among substances. However, there is a "modification of" relation between a modified substance (e.g., ester or salt) and the corresponding base substance (e.g., between Atorvastatin calcium and Atorvastatin). Modified substances can be further modified. IDMP requires that dose forms be defined in reference to a list of dose forms from the European Directorate for Quality in Medicines (EDQM). EDQM distinguishes between dose forms and units of presentation. Units of presentation are used to express the strength and quantity in countable entities, while dose forms correspond to the physical structure of the medicinal product.</p><p>In accordance with requirements from IDMP, strength units in SNOMED CT are aligned with the international standard for units of measure, UCUM (Unified Code for Units of Measure). Finally, depending on the unit of presentation, strength can be represented as concentration strength, presentation strength or both.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>The RxNorm model</head><p>in 1992, RxNorm is a normalized terminology for clinical drugs in the U.S. RxNorm represents both generic drugs and branded drugs, as well as packs <ref type="bibr" target="#b10">(11)</ref>. The full model of RxNorm contains ten entities, five for generic drug entities and five for branded drugs entities. For comparison with SNOMED CT, we only present RxNorm generic drug entities and also omit packs. The simplified RxNorm model for generic drug entities includes four entities (Figure <ref type="figure" target="#fig_3">2</ref> qualitative distinction (QD) Strength in RxNorm is normalized. In its units of measure (e.g., for volume, weight, surface), RxNorm uses one unit for each type quantity (e.g., milligram for weight rather than gram or microgram). The representation of dose forms in RxNorm is not based on a specific standard <ref type="bibr" target="#b11">(12)</ref>. It is also important to note that the SCDs and SCDCs refer to the basis of strength substance (e.g., cetirizine hydrochloride), while SCDFs refer to the base ingredient (e.g., cetirizine). Of note, ingredients in RxNorm can (purposely) be understood as either the substance contained in a medicinal product as active ingredient (e.g., "cetirizine the substance") or the class of all medicinal products containing this substance as active ingredient. Precise ingredients (PINs) generally correspond to modified forms of the corresponding base ingredients (INs). PINs cannot be further modified. In addition, RxNorm does not explicitly have a notion of "worldview" (i.e., open or closed worldview) for its entities. While clinical drugs implicitly refer to a closed worldview, ingredients, clinical drug components and clinical drug forms can be understood in both open and closed worldview, leaving it to queries to distinguish between the two. Finally, the Quantity Factor (QF) is a number followed by a unit of measure corresponding to vial sizes or patch durations (e.g., "12H"). RxNorm does not explicitly state whether strength is expressed as presentation strength or concentration strength. Presentation strength can be derived from concentration strength by multiplying the concentration strength by the quantity factor. (For example, if the concentration strength is 1MG/ML and the QF is 2ML, the presentation strength is 2MG/2ML). The Qualitative Distinction (QD) corresponds to some qualitative characteristic of a drug outside the main definitional features (e.g., "sugar free" and "abuse-deterrent"). QD and QF are optional modifiers used in RxNorm to define medicinal products when it is clinically relevant to identify such distinctions <ref type="bibr" target="#b11">(12)</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Comparison of the RxNorm and SNOMED CT models</head><p>To compare the two models, we manually establish equivalences between their entities and between their definitional features, based on our analysis of the two models. First, we need to disambiguate the notion of ingredient in RxNorm (IN,PIN, MIN), because, as mentioned earlier, it can be understood as either a substance or a class of medicinal products. Therefore, as shown in Figure <ref type="figure" target="#fig_4">3</ref>, ingredients in RxNorm correspond to SNOMED CT medicinal products (in open and closed worldview) or to SNOMED CT substances, which are active ingredients of SNOMED CT medicinal products. In practice, RxNorm ingredients are often associated with multiple SNOMED CT entities, typically with one substance entity and one medicinal product entity. Disambiguation consists in identifying which SNOMED CT entity comes from the substance hierarchy (and treating it as a value for the definitional feature "active ingredient"), while the SNOMED CT entity corresponding to an entity from the medicinal product hierarchy is marked as an asserted equivalence for the RxNorm medicinal product entity. RxNorm does not formally have the notion of "unit of presentation". Units of presentation are implicitly represented through dose forms in RxNorm, whereas the two notions are represented separately in SNOMED CT. For example, in SNOMED CT, tablet is the logical "unit of presentation" of the conventional release oral tablet, while the two are conflated in the RxNorm dose form "Oral Tablet". Therefore, RxNorm dose forms generally correspond to pairs of a pharmaceutical dose form and a unit of presentation in SNOMED CT. In addition, there are no materialized entities for SCDCs in SNOMED CT. Instead, strength and basis of strength substance are associated as part of the definition of a clinical drug in  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Discussion</head><p>Findings. Not surprisingly, the models used by RxNorm and SNOMED CT for representing medicinal products are fairly similar and essentially compatible. Both models share major definitional features including ingredient (or substance), strength and dose form. Only the qualitative distinction feature of RxNorm has no correspondence at all in SNOMED CT. SNOMED CT is more rigorous and better aligned with international standards. In SNOMED CT, differences tend to be made explicit, e.g., between a substance and the class of medicinal products containing this substance as an ingredient, or between the class of all medicinal products containing only a given active ingredient and the class of all medicinal products containing at least this active ingredient . SNOMED CT also offers more flexibility with relations among substances, as opposed to a fixed precise ingredient to base ingredient relationship in RxNorm. This precision comes at the price of a more complex model, and possibly a steeper learning curve. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Conclusion</head><p>In this investigation, we examined the similarities and differences between the representation of medicinal products in RxNorm and SNOMED CT. We established that both models share major definitional features including ingredient (or substance), strength and dose form. Because of subtle differences between the two models, specific aspects of their alignment require particular attention.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>Substance is the type of values for the active ingredient, precise active ingredient and basis of strength roles, for example 372523007 | Cetirizine (substance) and 108656004 | Cetirizine hydrochloride (substance). (The basis of strength is the substance in reference to which strength is defined.)Unitof measure is the type of values for the strength unit roles, for example, 258684004 | milligram (qualifier value). Number is the type of values for the strength value roles, for example, 3445001 | 10 (qualifier value). Pharmaceutical dose form is the type of values for the manufactured dose form role, for example, 421026006 | Conventional release oral tablet (dose form). Unit of presentation is the type of values for the unit of presentation role, for example, 732936001 | Tablet (unit of presentation).</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 1 -</head><label>1</label><figDesc>Figure 1-SNOMED CT model for the representation of medicinal products showing the six types of entities defined in the model, along with their definitional features and examples from the SNOMED CT terminology</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>): Ingredient, including base ingredient (IN), precise ingredient (PIN), and multi-ingredient (MIN) (e.g., IN: Cetirizine [RxCUI = 20610], PIN: cetirizine hydrochloride [RxCUI = 203150], MIN: Cetirizine / Pseudoephedrine [RxCUI = 352367]) Clinical drugs component (SCDC), combining ingredient and strength (e.g., cetirizine hydrochloride 10 MG [RxCUI = 1011480]) Clinical drugs form (SCDF), combining ingredient and dose form (e.g., Cetirizine Oral Tablet [RxCUI = 371364]) Clinical drug (SCD), combining ingredient, strength and dose form (e.g., cetirizine hydrochloride 10 MG Oral Tablet [RxCUI = 1014678]) The representation of these entities relies on three mandatory and two optional definitional features: Mandatory definitional features: ingredient (IN/PIN/MIN) (e.g., IN: Cetirizine [RxCUI = 20610], PIN: cetirizine hydrochloride [RxCUI = 203150], MIN: Cetirizine / Pseudoephedrine [RxCUI = 352367]) dose form (DF) (e.g., Oral Tablet [RxCUI = 317541]) strength (e.g., 10 MG) Optional definitional features (see below for examples): quantity factor (QF)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 2 -</head><label>2</label><figDesc>Figure 2-Simplified RxNorm model for the representation of generic medicinal products showing the four types of entities defined in the model, along with their definitional features and examples from the RxNorm terminology</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 3 -</head><label>3</label><figDesc>Figure 3-Correspondence between the RxNorm and SNOMED CT models</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head></head><label></label><figDesc>SNOMED CT. Therefore, SCDCs cannot be related to entities in SNOMED CT, but their defining features are represented as part of clinical drug entities. SCDs in RxNorm are equivalent to clinical drugs in SNOMED CT as they essentially share the same definitional features. The quantity factor in RxNorm has no direct equivalent in SNOMED CT, but QF information is implicitly represented in the presentation strength. In contrast, qualitative distinctions are absent from the SNOMED CT model.</figDesc><table><row><cell cols="2">Definitional features RxNorm SNOMED CT</cell><cell>RxNorm entities</cell><cell></cell><cell>SNOMED CT entities</cell></row><row><cell>Substance</cell><cell>IN/PIN (Substance)</cell><cell>Ingredient (IN)/ Precise ingredient (PIN)</cell><cell>IN/PIN (Medicinal product)</cell><cell>Medicinal product</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="2">Medicinal product</cell></row><row><cell cols="3">Dose Form (DF) While RxNorm only represents one level of modification (be-Pharmaceutical Dose Form tween PIN and IN), SNOMED CT can represent arbitrary levels Clinical drug Form (SCDF) of modification among substances.</cell><cell></cell><cell>Medicinal product form</cell><cell>only</cell></row><row><cell cols="3">Unit of Both RxNorm and SNOMED CT have the notion of concentration</cell><cell></cell><cell></cell></row><row><cell cols="3">presentation strength and presentation strength. However, RxNorm empha-</cell><cell></cell><cell></cell></row><row><cell cols="3">sizes concentration strength (from which presentation strength</cell><cell></cell><cell>Medicinal product</cell></row><row><cell cols="3">can be calculated using the quantity factor), whereas SNOMED</cell><cell></cell><cell>form only</cell></row><row><cell cols="3">Strength Unit CT explicitly represent both presentation strength and concentra-Unit of measure tion strength when necessary.</cell><cell></cell><cell></cell></row><row><cell cols="3">Clinical drug (SCD) Finally, RxNorm normalizes all quantities to one unit (per type of</cell><cell></cell><cell>Clinical drug</cell></row><row><cell cols="3">Strength Value quantity), whereas SNOMED CT uses units that are most clini-Number</cell><cell></cell><cell></cell></row><row><cell cols="3">cally appropriate (following IDMP requirements). For example,</cell><cell></cell><cell></cell></row><row><cell cols="3">RxNorm uses 0.001 milligram and SNOMED CT 1 microgram.</cell><cell></cell><cell></cell></row><row><cell cols="3">Legend This difference merely reflects differences in editorial guidelines, Correspondence between definitional features Definitional feature as conversion between the two is trivial.</cell><cell>Correspondence between entities</cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head></head><label></label><figDesc>Strength entities require minimal attention, specifically for converting RxNorm "fixed unit" into the clinically appropriate unit used in SNOMED CT. Simple arithmetic is also required to convert concentration strength and quantity factor in RxNorm to presentation strength in SNOMED CT wherever appropriate. In contrast, aligning dose forms requires more analysis, as RxNorm dose forms generally correspond to pairs of a pharmaceutical dose form and a unit of presentation in SNOMED CT. The absence of correspondence for qualitative distinction in SNOMED CT may lead to multiple clinical drugs in RxNorm mapping to a single clinical drug in SNOMED CT. For example, the distinction between Cholestyramine Resin 4000 MG Powder for Oral Suspension [RxCUI = 848943] and its sugar-free form Sugar-Free Cholestyramine Resin 4000 MG Powder for Oral Suspension[RxCUI = 1801279]  in RxNorm is lost in SNOMED CT. This issue is unlikely to result in clinically significant alignment errors. The absence of materialization of the clinical drug component (SCDC) entity in SNOMED CT does not create an alignment issue, because SCDCs are essentially navigational entities in RxNorm. They are not crucial to any of the main use cases for RxNorm or SNOMED CT. Future work. In future work, we plan to translate RxNorm into the SNOMED CT model for medicinal products. The resulting alignment would make RxNorm entities directly compatible with SNOMED CT's. One benefit of this alignment would be to assess interoperability between RxNorm and SNOMED CT, potentially enriching SNOMED CT with clinical drugs currently specific to RxNorm. Additionally, this alignment would offer an opportunity for quality assurance by identifying cases where alignment is expected, but cannot be inferred (e.g., because of a difference in basis of strength substance for a given clinical drug between RxNorm and SNOMED CT).</figDesc><table><row><cell>In contrast, RxNorm contains im-</cell></row><row><cell>plicit knowledge, simplifications and ambiguities, but its model</cell></row><row><cell>is simpler.</cell></row><row><cell>With features, such as explicit closed worldview for clinical drug</cell></row><row><cell>entities, use of standard dose forms from EDQM, use of UCUM</cell></row><row><cell>units, and use of clinically appropriate strength values, SNOMED</cell></row><row><cell>CT shows better compliance with international standards (namely</cell></row><row><cell>IDMP) than RxNorm does.</cell></row><row><cell>Consequences on alignment. Since their models are largely com-</cell></row><row><cell>patible, medicinal products from RxNorm and SNOMED CT are</cell></row><row><cell>expected to be interoperable. However, specific aspects of the</cell></row><row><cell>alignment between the two models require particular attention.</cell></row></table><note>The values of ingredient can be aligned rather trivially (after disambiguation between the two meanings of RxNorm ingredients, substance and class of medicinal products containing this substance as an ingredient).</note></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgment</head><p>This work was supported by the Intramural Research Program of the NIH, National Library of Medicine. The authors would like to thank the developers of RxNorm and the contributors to the SNOMED International Drug Model Working Group for useful discussion We are particularly grateful to Tammy Powell and Chris Hui (RxNorm), and Julie James, Jim Case, Yongsheng Gao, Emma Melhuish, Toni Morrison, Guillermo Reynoso, Farzaneh Ashrafi and Phuong Skovgaard (SNOMED CT). We also thank NLM colleagues, Lee Peters, Robert Wynne and Phill Wolf, for useful discussion.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Address for correspondence</head><p>Jean.nikiema@u-bordeaux.fr Olivier.bodenreider@nih.gov</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Harnessing Ontologies to Improve Prescription in Pediatric Medicine</title>
		<author>
			<persName><forename type="first">O-S</forename><surname>Lupse</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C-B</forename><surname>Chirila</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Stoicu-Tivadar</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Studies in Health Technology and Informatics</title>
		<imprint>
			<biblScope unit="page" from="97" to="101" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Ontological approach to reduce complexity in polypharmacy</title>
		<author>
			<persName><forename type="first">S</forename><surname>Farrish</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Grando</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">AMIA Annu Symp Proc</title>
		<imprint>
			<biblScope unit="volume">2013</biblScope>
			<biblScope unit="page" from="398" to="407" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Applying a common data model to Asian databases for multinational pharmacoepidemiologic studies: opportunities and challenges</title>
		<author>
			<persName><forename type="first">Ec-C</forename><surname>Lai</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Ryan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schuemie</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">C</forename><surname>Hardy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Kamijima</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Clinical Epidemiology</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="page" from="875" to="885" />
			<date type="published" when="2018-07">2018 Jul</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<ptr target="https://www.ema.europa.eu/docu-ments/other/introduction-iso-identification-medicinal-prod-ucts-spor-programme_en.pdf" />
		<title level="m">Introduction to ISO Identification of Medicinal Products, SPOR programme</title>
				<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
		<respStmt>
			<orgName>European Medicines Agency</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Evaluating the implementation of RxNorm in ambulatory electronic prescriptions</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Dhavle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Ward-Charlerie</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">T</forename><surname>Rupp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Kilbourne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">P</forename><surname>Amin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Ruiz</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of the American Medical Informatics Association</title>
		<imprint>
			<biblScope unit="volume">23</biblScope>
			<biblScope unit="issue">e1</biblScope>
			<biblScope unit="page" from="e99" to="107" />
			<date type="published" when="2016-04">2016 Apr</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">RxNorm: prescription for electronic drug information exchange</title>
		<author>
			<persName><forename type="first">S</forename><surname>Liu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Wei</forename><surname>Ma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Moore</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Ganesan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Nelson</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IT Professional</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">5</biblScope>
			<biblScope unit="page" from="17" to="23" />
			<date type="published" when="2005-09">2005 Sep</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Toward a normalized clinical drug knowledge base in China-applying the RxNorm model to Chinese clinical drugs</title>
		<author>
			<persName><forename type="first">L</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Jiang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Dong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Liu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of the American Medical Informatics Association</title>
		<imprint>
			<biblScope unit="volume">25</biblScope>
			<biblScope unit="issue">7</biblScope>
			<biblScope unit="page" from="809" to="818" />
			<date type="published" when="2018-07-01">2018 Jul 1</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Building a drug ontology based on RxNorm and other sources</title>
		<author>
			<persName><forename type="first">J</forename><surname>Hanna</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Joseph</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Brochhausen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">R</forename><surname>Hogan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Biomedical Semantics</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">44</biblScope>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">The New SNOMED CT International Medicinal Product Model</title>
		<author>
			<persName><forename type="first">O</forename><surname>Bodenreider</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>James</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the International Conference on Biological Ontology (ICBO 2018)</title>
				<meeting>the International Conference on Biological Ontology (ICBO 2018)<address><addrLine>Oregon, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Ontological analysis of SNOMED CT</title>
		<author>
			<persName><forename type="first">G</forename><surname>Héja</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Surján</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Varga</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">BMC Medical Informatics and Decision Making</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">S8</biblScope>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
	<note>Suppl</note>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Normalized names for clinical drugs: RxNorm at 6 years. Journal</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J</forename><surname>Nelson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Zeng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Kilbourne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Powell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Moore</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">of the American Medical Informatics Association</title>
		<imprint>
			<biblScope unit="volume">18</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="441" to="448" />
			<date type="published" when="2011-07">2011 Jul</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Recent Developments in Clinical Terminologies -SNOMED CT, LOINC, and RxNorm</title>
		<author>
			<persName><forename type="first">O</forename><surname>Bodenreider</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cornet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Vreeman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Yearbook of Medical Informatics</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="issue">01</biblScope>
			<biblScope unit="page" from="129" to="139" />
			<date type="published" when="2018-08">2018 Aug</date>
		</imprint>
	</monogr>
</biblStruct>

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