<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article"><front><journal-meta><journal-id journal-id-type="publisher-id">JBM</journal-id><journal-title-group><journal-title>Journal of Biosciences and Medicines</journal-title></journal-title-group><issn pub-type="epub">2327-5081</issn><publisher><publisher-name>Scientific Research Publishing</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.4236/jbm.2023.1111027</article-id><article-id pub-id-type="publisher-id">JBM-129297</article-id><article-categories><subj-group subj-group-type="heading"><subject>Articles</subject></subj-group><subj-group subj-group-type="Discipline-v2"><subject>Biomedical&amp;Life Sciences</subject></subj-group></article-categories><title-group><article-title>
 
 
  SNOMED CT: A Clinical Terminology but Also a Formal Ontology
 
</article-title></title-group><contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Constant</surname><given-names>Joseph Koné</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Michel</surname><given-names>Babri</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Jean</surname><given-names>Marie Rodrigues</given-names></name><xref ref-type="aff" rid="aff2"><sup>2</sup></xref></contrib></contrib-group><aff id="aff1"><addr-line>Félix Houphou&amp;amp;euml;t-Boigny National Polytechnic Institute, Yamoussoukro, Cote d’Ivoire</addr-line></aff><aff id="aff2"><addr-line>University Jean Monnet, Saint Etienne, France</addr-line></aff><pub-date pub-type="epub"><day>01</day><month>11</month><year>2023</year></pub-date><volume>11</volume><issue>11</issue><fpage>326</fpage><lpage>333</lpage><history><date date-type="received"><day>20,</day>	<month>October</month>	<year>2023</year></date><date date-type="rev-recd"><day>24,</day>	<month>November</month>	<year>2023</year>	</date><date date-type="accepted"><day>27,</day>	<month>November</month>	<year>2023</year></date></history><permissions><copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement><copyright-year>2014</copyright-year><license><license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p></license></permissions><abstract><p>
 
 
  Context and Objective: Over the past few decades, terminologies developed for clinical descriptions have been increasingly used as key resources for knowledge management, data integration, and decision support to the extent that today they have become essential in the biomedical and health field. Among these clinical terminologies, some may possess the characteristics of one or several types of representation. This is the case for the Systematized Nomenclature of Human and Veterinary Medicine—Clinical Terms (SNOMED CT), which is both a clinical medical terminology and a formal ontology based on the principles of semantic web. 
  Methods: We present and discuss, on one hand, the compliance of SNOMED CT with the requirements of a reference clinical terminology and, on the other hand, the specifications of the features and constructions of descriptive of SNOMED CT. 
  Results: We demonstrate the consistency of the reference clinical terminology SNOMED CT with the principles stated in James J. Cimino’s desiderata and we also show that SNOMED CT contains an ontology based on the EL profile of OWL2 with some simplifications. 
  Conclusions: The duality of SNOMED CT shown is crucial for understanding the versatility, depth, and scope in the health field.
 
</p></abstract><kwd-group><kwd>SNOMED CT</kwd><kwd> Clinical Terminology</kwd><kwd> Ontology</kwd><kwd> OWL2</kwd></kwd-group></article-meta></front><body><sec id="s1"><title>1. Introduction</title><p>There are several types of terminological systems, including thesauruses, terminologies, classifications, taxonomies, vocabularies, nomenclatures, and ontologies [<xref ref-type="bibr" rid="scirp.129297-ref1">1</xref>] . Some terminological resources can possess the characteristics of one or several of these representation artifacts. This is the case with the Systematized Nomenclature of Human and Veterinary Medicine—Clinical Terms (SNOMED CT) [<xref ref-type="bibr" rid="scirp.129297-ref2">2</xref>] , which is both a globally used clinical medical terminology that covers all specialties, disciplines, and clinical requirements and a formal ontology based on the principles of the semantic web, with the Ontology Web Language (OWL) [<xref ref-type="bibr" rid="scirp.129297-ref3">3</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref4">4</xref>] as its reference language.</p><p>OWL2, the current version, is a powerful modeling and explication language for general use in some areas of human knowledge [<xref ref-type="bibr" rid="scirp.129297-ref4">4</xref>] . Humans need knowledge and wisdom to derive implications from their understanding. An essential feature of OWL is that it captures the meaning and significance of the knowledge it can represent, surpassing the simple string of characters of terms or words in a language [<xref ref-type="bibr" rid="scirp.129297-ref5">5</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref6">6</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref7">7</xref>] .</p><p>In this work we present and discuss the compliance of SNOMED CT with the requirements of a clinical reference terminology and with the specifications of the set of features and descriptive logic constructs of SNOMED CT in OWL2 that have an impact on the implementation and maintenance of SNOMED CT.</p></sec><sec id="s2"><title>2. Materials and Methods</title><p>SNOMED CT (Systematized Nomenclature of Medicine Clinical Terms) is the most comprehensive and internationally recognized medical terminology in the world. It provides a coded language for uniformly and systematically representing clinically meaningful information. SNOMED CT facilitates the sharing and analysis of health data across healthcare systems and applications. Used for the electronic coding of medical data, it enhances the quality, safety, and efficiency of healthcare.</p><p>Initially, we discuss the alignment of SNOMED CT with the desiderata articulated by James J. Cimino [<xref ref-type="bibr" rid="scirp.129297-ref8">8</xref>] . After listing Cimino’s 12 desideratas, we search for and present characters of SNOMED CT that relate to each desiderata.</p><p>Subsequently, in a first part, we briefly present the history of ontology and its implication in digital information sciences. We then present and deliberate on the differences between the logical profile implemented in SNOMED CT in EL (Expression Language) and the original version of OWL2. Specifically, we have identified the constructors specific to each system. We then developed a comparison matrix to highlight the similarities and differences between the two systems.</p></sec><sec id="s3"><title>3. Results</title><sec id="s3_1"><title>3.1. SNOMED CT: A Reference Clinical Terminology</title><p>SNOMED CT is built on the design requirements for reference clinical terminology outlined in 1998 and expanded in 2001 in a landmark article—“Desiderata for controlled medical vocabularies in the twenty-first century” by James J. Cimino [<xref ref-type="bibr" rid="scirp.129297-ref6">6</xref>] . These requirements can be summarized as follows: 1) content importance, 2) concept consideration, 3) concept permanence, 4) non-significant concept identifier, 5) poly-hierarchy, 6) formal definitions, 7) rejection of the “not classified elsewhere” notion, 8) multiple granularity, 9) multiple and coherent viewpoints, 10) context representation, 11) capability to evolve, and 12) consideration of redundancy.</p><p>In these Desideratas, James J. Cimino talks about the completeness of vocabulary, that is, domain coverage. In this respect, SNOMED CT can boast a broad coverage of the medical and health field by having about 350,000 concepts that cover anatomy, pathologies, observable variables, organisms, pharmaceutical and biological products, interventions, etc. (Desiderata Cimino 1).</p><p>According to SNOMED, a concept is defined as “a unit of knowledge created by a unique combination of characters”. It has a preferred name and several synonyms in every language available in SNOMED CT, including French (Desiderata Cimino 2 and 3).</p><p>Each concept is associated with a non-significant identifier of a positive 64-bit integer type, having a minimum and maximum authorized length of 6 and 18 digits respectively (Desiderata Cimino 4) [<xref ref-type="bibr" rid="scirp.129297-ref9">9</xref>] .</p><p>The primary hierarchical relation of SNOMED CT is the “is a” relation, forming the base of SNOMED CT hierarchies with a root concept that has no concept above it. A concept with a “is a” relation to a parent concept (more general concept) is called a descendant concept. SNOMED CT allows a concept to have more than one “is a” relation with other concepts, indicating that SNOMED CT has a poly-hierarchical structure (Desiderata Cimino 5).</p><p>Unlike aggregations or classifications where all considered domain objects must be classified in a single exclusive and exhaustive place, SNOMED CT is not bound by these requirements. Domain objects are added as needed and from different viewpoints (Desiderata Cimino 9 and 11). There are no concepts like “others, unspecified or not classified elsewhere” (Desiderata Cimino 7).</p><p>SNOMED CT has evolved by expanding its coverage of the medical and health field at the contextual level. Initially, SNOMED CT representations used only three hierarchies, but now it has 19, allowing the collection of information not only on specific clinical situations but also on the context (Desiderata Cimino 10) [<xref ref-type="bibr" rid="scirp.129297-ref10">10</xref>] .</p><p>We often encounter similar terms or concepts at different levels of SNOMED CT, known as redundancy. This redundancy allows more choices when using SNOMED CT (Desiderata Cimino 12). Various mechanisms within SNOMED CT account for this redundancy, including synonymy, concept hierarchy, and concept equivalence.</p><p>Lastly, for some hierarchies, SNOMED CT provides a formal ontological representation, which we will address in the following chapter (Desiderata Cimino 6).</p></sec><sec id="s3_2"><title>3.2. SNOMED CT: A Formal Ontology</title><p>Ontology is a branch of philosophy that can be defined as the study of what “IS” in the physical world [<xref ref-type="bibr" rid="scirp.129297-ref7">7</xref>] . The application of this approach in digital information sciences, especially in health, began in the 1990s as a representation of information entities used in a knowledge base. The most widely cited definition of formal digital ontology is that of Gruber [<xref ref-type="bibr" rid="scirp.129297-ref11">11</xref>] : “An ontology is an explicit specification of a conceptualization.” By conceptualization, Gruber means an abstract and simplified view of the world’s representation, and by explicit specification, he means that this conceptualization is made unambiguously in a concrete language. Gruber defined five types of components for describing a domain’s knowledge: 1) concepts, 2) relations, 3) functions, 4) axioms, and 5) instances. Later, Gruber’s definition was supplemented by Studer and his colleagues [<xref ref-type="bibr" rid="scirp.129297-ref12">12</xref>] , stating that a formal ontology is a formal and explicit specification of a shared conceptualization. The term “formal” implies that the applied ontology should be machine-readable, meaning machines should be able to interpret the semantics or the meaning of the provided information.</p><p>Formal digital ontology has found its place in the biomedical field, confronted with an explosion of knowledge contained in heterogeneous terminological systems [<xref ref-type="bibr" rid="scirp.129297-ref13">13</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref14">14</xref>] . In this regard, SNOMED CT, for certain hierarchies, provides a formal ontological representation that expresses the formal logic of a “Concept Model” following the rules of “compositional grammar” [<xref ref-type="bibr" rid="scirp.129297-ref3">3</xref>] in a subset or profile of OWL 2 named EL for Expression Language, offering application possibilities [<xref ref-type="bibr" rid="scirp.129297-ref15">15</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref16">16</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref17">17</xref>] [<xref ref-type="bibr" rid="scirp.129297-ref18">18</xref>] . For example, the disease “acute intestinal infection due to Escherichia coli”, represented by the concept 111839008 |Intestinal infection caused by Escherichia coli (disorder)|, is equivalent to the logical expression using the following OWL functional syntax, see <xref ref-type="fig" rid="fig1">Figure 1</xref>.</p><p>However, the OWL2 logical profile of SNOMED CT does not cover all the expressive possibilities of EL OWL2 [<xref ref-type="bibr" rid="scirp.129297-ref15">15</xref>] for several reasons, among which complexity issues are found.</p><p>We provide a comparative table of the constructors and entities of the EL logical profile of SNOMED CT and the OWL2 specification (see <xref ref-type="table" rid="table1">Table 1</xref>).</p><table-wrap id="table1" ><label><xref ref-type="table" rid="table1">Table 1</xref></label><caption><title> Comparison of constructors of SNOMED CT’s EL logical profile and OWL2</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Constructors</th><th align="center" valign="middle" >Logic profile EL SNOMED CT</th><th align="center" valign="middle" >Logic profile EL OWL2</th></tr></thead><tr><td align="center" valign="middle" >Entities, literal and anonymous</td><td align="center" valign="middle" >- Class - ObjectProperty - DataProperty - Datatype - Literal - AnnotationProperty</td><td align="center" valign="middle" >- Class - ObjectProperty - DataProperty - Datatype - Literal - AnnotationProperty - DataRange - Individual - NamedIndividual - AnonymousIndividual</td></tr><tr><td align="center" valign="middle" >Data types</td><td align="center" valign="middle" >- xsd:decimal - xsd:integer - xsd:string - xsd:dateTime</td><td align="center" valign="middle" >- rdf:PlainLiteral - rdf:XMLLiteral - rdfs:Literal - owl:real - owl:rational - xsd:decimal - xsd:integer - xsd:nonNegativeInteger - xsd:string - xsd:normalizedString - xsd:token - xsd:Name - xsd:NCName - xsd:NMTOKEN - xsd:hexBinary - xsd:base64Binary - xsd:anyURI - xsd:dateTime - xsd:dateTimeStamp</td></tr><tr><td align="center" valign="middle" >Class restriction</td><td align="center" valign="middle" >- existential quantification to a class expression (ObjectSomeValuesFrom) - intersection of classes (ObjectIntersectionOf) - existential quantification to a literal (DataHasValue)</td><td align="center" valign="middle" >- existential quantification to a class expression (ObjectSomeValuesFrom) - existential quantification to a data range (DataSomeValuesFrom) - existential quantification to an individual (ObjectHasValue) - existential quantification to a literal (DataHasValue) - universal quantification to a class expression (ObjectAllValuesFrom) - universal quantification to a range of data (DataAllValuesFrom) - cardinality restrictions (ObjectMaxCardinality, ObjectMinCardinality, ObjectExactCardinality, DataMaxCardinality, DataMinCardinality, and DataExactCardinality) - self-restriction (ObjectHasSelf) - enumerations involving a single individual (ObjectOneOf) - enumerations involving a single literal (DataOneOf) - intersection of classes (ObjectIntersectionOf) - intersection of data ranges (DataIntersectionOf)</td></tr><tr><td align="center" valign="middle" >Class expressions</td><td align="center" valign="middle" >- class inclusion (SubClassOf) - class equivalence (EquivalentClasses) - inclusion of object properties (SubObjectPropertyOf) - inclusion of data properties (SubDataPropertyOf) - class disjunction (DisjointClasses) - property equivalence (EquivalentObjectProperties and EquivalentDataProperties) - properties of the transitive object (TransitiveObjectProperty) - reflexive object properties (ReflexiveObjectProperty)</td><td align="center" valign="middle" >- class inclusion (SubClassOf) - class equivalence (EquivalentClasses) - inclusion of object properties (SubObjectPropertyOf) - inclusion of data properties (SubDataPropertyOf) - class disjunction (DisjointClasses) - property equivalence (EquivalentObjectProperties and EquivalentDataProperties) - properties of the transitive object (TransitiveObjectProperty) - reflexive object properties (ReflexiveObjectProperty) - domain restrictions (ObjectPropertyDomain and DataPropertyDomain) - range restrictions (ObjectPropertyRange and DataPropertyRange) - assertions (SameIndividual, DifferentIndividuals, ClassAssertion, ObjectPropertyAssertion, DataPropertyAssertion, NegativeObjectPropertyAssertion and NegativeDataPropertyAssertion) - functional data properties (FunctionalDataProperty) - keys (HasKey) - disjunction (ObjectUnionOf, DisjointUnion, and DataUnionOf) - class negation (ObjectComplementOf) - disjoint properties (DisjointObjectProperties and DisjointDataProperties) - irreflexive object properties (IrreflexiveObjectProperty) - inverse object properties (InverseObjectProperties)</td></tr></tbody></table></table-wrap><p><xref ref-type="table" rid="table2">Table 2</xref> below illustrates the proportion of usage of the constructors of the EL OWL2 logical profile.</p><table-wrap id="table2" ><label><xref ref-type="table" rid="table2">Table 2</xref></label><caption><title> Comparison of the number of constructors and entities of the EL logical profile in SNOMED CT and OWL2</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Types of Constructors and entities</th><th align="center" valign="middle" >Logic profile EL SNOMED CT</th><th align="center" valign="middle" >Logic Profile EL OWL2</th><th align="center" valign="middle" >Percentage of constructors and entities used</th></tr></thead><tr><td align="center" valign="middle" >Anonymous entities, literals and individuals</td><td align="center" valign="middle" >6</td><td align="center" valign="middle" >10</td><td align="center" valign="middle" >60%</td></tr><tr><td align="center" valign="middle" >Data types</td><td align="center" valign="middle" >4</td><td align="center" valign="middle" >19</td><td align="center" valign="middle" >21%</td></tr><tr><td align="center" valign="middle" >Class restrictions</td><td align="center" valign="middle" >3</td><td align="center" valign="middle" >17</td><td align="center" valign="middle" >18%</td></tr><tr><td align="center" valign="middle" >Class expressions</td><td align="center" valign="middle" >9</td><td align="center" valign="middle" >30</td><td align="center" valign="middle" >30%</td></tr></tbody></table></table-wrap></sec></sec><sec id="s4"><title>4. Discussion</title><p>SNOMED CT qualifies as a medical terminology if we adhere to the 12 recommendations by J. J. Cimino. Indeed, these 12 outlined criteria have been thoroughly incorporated in the development of this terminology.</p><p>When looking at the ontological facet of SNOMED CT, on average, 32% of the constructors available in EL OWL2 are used. The lowest utilization rate is associated with class restrictions, with only three out of 17 available constructors being used, accounting for 18%.</p><p>On the other hand, a number of constructors from the EL logical profile of OWL2 are excluded from that of SNOMED CT due to their complexity and/or additional impact on reasoning times with the current hardware and algorithms. The main features excluded from the SNOMED CT EL logical profile are:</p><p>- Universal quantification (ObjectAllValuesFrom);</p><p>- Disjunction (ObjectUnionOf, DisjointUnion, and DataUnionOf);</p><p>- Class negation (ObjectComplementOf);</p><p>- Domain and value constraints which are supported via the SNOMED CT Machine Readable Concept Model;</p><p>- Anonymous entities because SNOMED CT does not see their utility in its context of use.</p><p>There is a natural tension between the desire to use features so that the content can be more expressive and precise and the cost and complexity of these features. In other words, it allows for sufficient expressiveness for the content while remaining manageable for implementation.</p><p>The constructors excluded from the EL profile of SNOMED CT have too high a cost for the implementation of SNOMED CT to be bearable at the moment. For example, in his study, S. Schulz showed that the use of negation is not recommended in SNOMED CT expressions [<xref ref-type="bibr" rid="scirp.129297-ref18">18</xref>] . Extensions of SNOMED CT can choose to implement even more features than the SNOMED CT logical profile offers, with the consequence of not being able to function properly and having reasoning times that increase significantly.</p></sec><sec id="s5"><title>5. Conclusion</title><p>In this text, we highlight the consistency of the reference clinical terminology SNOMED CT with the principles outlined in J. J. Cimino’s desiderata for the 21st-century reference clinical terminologies. A balanced approach that takes into account complexity, cost, and the added value of features is essential to optimize the utility and efficiency of SNOMED CT in the future.</p></sec><sec id="s6"><title>Conflicts of Interest</title><p>The authors declare no conflicts of interest regarding the publication of this paper.</p></sec><sec id="s7"><title>Cite this paper</title><p>Kon&#233;, C.J., Babri, M. and Rodrigues, J.M. (2023) SNOMED CT: A Clinical Terminology but Also a Formal Ontology. Journal of Biosciences and Medicines, 11, 326-333. https://doi.org/10.4236/jbm.2023.1111027</p></sec></body><back><ref-list><title>References</title><ref id="scirp.129297-ref1"><label>1</label><mixed-citation publication-type="book" xlink:type="simple">Duclos, C., et al. (2014) Medical Vocabulary, Terminological Resources and Information Coding in the Health Domain. In: Venot, A., Burgun, A. and Quantin, C., Eds., Medical Informatics, e-Health, Health Informatics, Springer, Paris. https://doi.org/10.1007/978-2-8178-0478-1_2</mixed-citation></ref><ref id="scirp.129297-ref2"><label>2</label><mixed-citation publication-type="other" xlink:type="simple">SNOMED International (2023) SNOMED CT Starter Guide. https://confluence.ihtsdotools.org/display/docstart/snomed+ct+starter+guide</mixed-citation></ref><ref id="scirp.129297-ref3"><label>3</label><mixed-citation publication-type="other" xlink:type="simple">SNOMED Compositional Grammar (2023) Specification and Guide. https://confluence.ihtsdotools.org/display/DOCSCG</mixed-citation></ref><ref id="scirp.129297-ref4"><label>4</label><mixed-citation publication-type="other" xlink:type="simple">Group WCOW (2023) OWL 2 Web Ontology Language Primer (Second Edition). https://www.w3.org/TR/owl2-overview/</mixed-citation></ref><ref id="scirp.129297-ref5"><label>5</label><mixed-citation publication-type="other" xlink:type="simple">Roche, C. (2005) Terminologie et ontologie. Langages, 157, 48-62. https://doi.org/10.3917/lang.157.0048</mixed-citation></ref><ref id="scirp.129297-ref6"><label>6</label><mixed-citation publication-type="other" xlink:type="simple">Geller, J. (2003) John Sowa, Knowledge Representation: Logical, Philosophical, and Computational Foundations, Brooks/Cole, 2000, 512 pp., $70.95 (Cloth), ISBN 0-534-94965-7. Minds and Machines, 13, 441-444. https://doi.org/10.1023/A:1024132024747</mixed-citation></ref><ref id="scirp.129297-ref7"><label>7</label><mixed-citation publication-type="other" xlink:type="simple">Monnin, A. and Félix, E. (2009) Essai de comparaison des ontologies informatiques et philosophiques: Entre être et artefacts: Ontologie et dynamique des systèmes complexes, perspectives interdisciplinaires. Megève, France, p. 14.</mixed-citation></ref><ref id="scirp.129297-ref8"><label>8</label><mixed-citation publication-type="other" xlink:type="simple">Cimino, J.J. (1998) Desiderata for Controlled Medical Vocabularies in the Twenty-First Century. Methods of Information in Medicine, 37, 394-403. https://doi.org/10.1055/s-0038-1634558</mixed-citation></ref><ref id="scirp.129297-ref9"><label>9</label><mixed-citation publication-type="other" xlink:type="simple">SNOMED CT Release File Specifications (2023) SNOMED CT Identifiers. https://confluence.ihtsdotools.org/display/DOCRELFMT/6+SNOMED+CT+Identifiers</mixed-citation></ref><ref id="scirp.129297-ref10"><label>10</label><mixed-citation publication-type="other" xlink:type="simple">SNOMED International, SNOMED (2023) SNOMED CT Concept Model. https://confluence.ihtsdotools.org/display/DOCSTART/6.+SNOMED+CT+Concept+Model</mixed-citation></ref><ref id="scirp.129297-ref11"><label>11</label><mixed-citation publication-type="other" xlink:type="simple">Genesereth, M., Fikes, R., Brachman, R., Gruber, T., Hayes, P., Letsinger, R., et al. (1992) Knowledge Interchange Format Version 3.0 Reference Manual. http://cs.auckland.ac.nz/courses/compsci367s2c/resources/kif.pdf</mixed-citation></ref><ref id="scirp.129297-ref12"><label>12</label><mixed-citation publication-type="other" xlink:type="simple">Studer, R., Benjamins, R. and Fensel, D. (1998) Knowledge Engineering: Principles and Methods. Data &amp; Knowledge Engineering, 25, 161-197. https://doi.org/10.1016/S0169-023X(97)00056-6</mixed-citation></ref><ref id="scirp.129297-ref13"><label>13</label><mixed-citation publication-type="other" xlink:type="simple">Bodenreider, O., Cornet, R. and Vreeman, D.J. (2018) Recent Developments in Clinical Terminologies—SNOMED CT, LOINC, and RxNorm. Yearbook of Medical Informatics, 27, 129-139. https://doi.org/10.1055/s-0038-1667077</mixed-citation></ref><ref id="scirp.129297-ref14"><label>14</label><mixed-citation publication-type="other" xlink:type="simple">Rector, A., Schulz, S., Rodrigues, J.M., Chute, C.G. and Solbrig, H. (2019) On beyond Gruber: “Ontologies” in Today’s Biomedical Information Systems and the Limits of OWL. Journal of Biomedical Informatics, 100, Article ID: 100002. https://doi.org/10.1016/j.yjbinx.2019.100002</mixed-citation></ref><ref id="scirp.129297-ref15"><label>15</label><mixed-citation publication-type="other" xlink:type="simple">W3C Recommendation (2023) OWL2 Web Ontology Language Document Overview (Second Edition). http://www.w3.org/TR/2012/REC-owl2-overview-20121211/</mixed-citation></ref><ref id="scirp.129297-ref16"><label>16</label><mixed-citation publication-type="other" xlink:type="simple">Heiyanthuduwage, S.R., Schwitter, R. and Orgun, M.A. (2016) OWL 2 Learn Profile: An Ontology Sublanguage for the Learning Domain. SpringerPlus, 5, Article No. 291. https://doi.org/10.1186/s40064-016-1826-0</mixed-citation></ref><ref id="scirp.129297-ref17"><label>17</label><mixed-citation publication-type="other" xlink:type="simple">El-Sappagh, S., Franda, F., Ali, F. and Kwak, K.-S. (2018) SNOMED CT Standard Ontology Based on the Ontology for General Medical Science. BMC Medical Informatics and Decision Making, 18, Article No. 76. https://doi.org/10.1186/s12911-018-0651-5</mixed-citation></ref><ref id="scirp.129297-ref18"><label>18</label><mixed-citation publication-type="other" xlink:type="simple">Schulz, S., Markó, K. and Suntisrivaraporn, B. (2008) Formal Representation of Complex SNOMED CT Expressions. BMC Medical Informatics and Decision Making, 8, Article No. S9. https://doi.org/10.1186/1472-6947-8-S1-S9</mixed-citation></ref></ref-list></back></article>