<!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>Scrutinizing the axiomatic basis of SNOMED CT: How confused is it by the ambiguous terminology paradigm?</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>3Institute for Medical Informatics, Statistics and Documentation, Medical University of Graz</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>INSERM LIMICS UPMC UP 13 Paris</institution>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Jean-Marie Rodrigues</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Manchester</institution>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>University of Saint Etienne</institution>
          ,
          <addr-line>CHU</addr-line>
          ,
          <institution>Department of Public Health and Medical Informatics</institution>
          ,
          <addr-line>Saint Etienne</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>SNOMED CT, the world's largest clinical terminology introduces itself as “a terminological resource which consists of codes representing meanings expressed as terms, with interrelationships between the codes to provide enhanced representation of the meanings.” On the one hand, concepts are linked to lexical entities (terms), including Fully Specified Names, Preferred Terms, and Synonyms. On the other hand, SNOMED CT concepts are described and defined by expressions following a formalism called Compositional Grammar (CG), according to which SNOMED CT might be considered a formal ontology. We investigate whether or not the ambiguity in the terms, which are formulated according to lexical and linguistic principles, is hampering the quality of the formal concept model using DL semantics and propose a more autonomous development process for formal concept definitions.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>SNOMED CT [1], a clinical terminology standard with
about 300,000 representational units, is presented as a
terminological resource linked to description logics
expressions [1]. We can therefore consider SNOMED CT as both</p>
      <p>A terminology – as constituted by concepts (entities of
lexical meaning), related terms of different types (Fully
Specified Names, Preferred Terms, and Synonyms,
obeying several naming conventions).</p>
      <p>A formal ontology constituted by classes, individuals
and formal relations expressed as axioms in
“Compositional Grammar” equivalent to EL++/OWL-EL – what
SNOMED call the “concept model”. As such, the
consistency of the SNOMED CT concept model can be
checked by description logics reasoners.</p>
      <p>It is critical that the concepts referred to by linguistic
expressions used in electronic health records are accurately
aligned with the underlying axiomatic representation of
those concepts. Recent works on the harmonization between
a subset of SNOMED CT and a pre-final version of ICD-11
have highlighted significant modelling issues. In more than
one third of cases, the SNOMED CT axiomatic expressions
did not align well with the intuitive meaning derived from
their Fully Specified Names or synonyms, when lexically
mapped to ICD-11 classes [2].</p>
      <p>This paper will investigate the hypothesis that in the
process of building and maintaining SNOMED CT, the
corshould
addressed:
rectness of the axiomatic expressions is affected when
SNOMED CT curators are led preferentially by language.
We first analyse the external inconsistencies between
axiomatic descriptions and definitions of SNOMED CT
concepts on the one hand and the ICD11 class. Thereafter, we
investigate inconsistencies within SNOMED CT and their
relation to ambiguities in typical clinical interface terms. As
a conclusion, we recommend that the axiomatic
underpinning of SNOMED CT should be developed autonomously
from the lexical entitites/terms, and that the linkage of terms
for concepts to the axiomatic descriptions of those concepts
be done after the axiomatic model of the concepts is
consolidated.
2</p>
    </sec>
    <sec id="sec-2">
      <title>MATERIAL AND METHODS</title>
      <p>SNOMED CT‘s representational units, called concepts are
linked to clinical terms (so called “descriptions”) in several
languages. Terms are of several types including Fully
Specified Names (FSNs), Preferred Terms (PTs), and Synonyms.
SNOMED CT concepts are also formally described by
expressions following a language called Compositional
Grammar (CG) [3], which can be interpreted according to
description logic (DL) semantics. In the following example,
Fracture of tibia, is fully defined as being equivalent to
Injury of tibia and Fracture of lower leg, with Associated
morphology Fracture and Finding site Bone structure of
tibia. Its rendering in CG and the Description Logics
Manchester Syntax is shown below (class symbols are set in
Italics and relation symbols are in Bold):
31978002 |Fracture of tibia(disorder)|
=== 428881005 |Injury of tibia (disorder)| +</p>
      <p>414292006 |Fracture of lower leg (disorder)| :
{ 363698007 |Finding site (attribute)| =</p>
      <p>12611008 |Bone structure of tibia (body structure)|,
116676008 |Associated morphology (attribute)| =</p>
      <p>72704001 |Fracture (morphologic abnormality)| }
‘Fracture of tibia’ equivalentTo
‘Injury of tibia (disorder)’ and
‘Fracture of lower leg (disorder)’ and
RoleGroup some
((‘Finding site (attribute)’ some
‘Bone structure of tibia (body structure)’) and
(‘Associated morphology (attribute)’ some</p>
      <p>‘Fracture (morphologic abnormality)’))
Table 1. SNOMED CT definitions in Conceptual Grammar
(above) and OWL Manchester Syntax (below)
CG supports logic-based compositional expressions in order
to maximise the coverage of utterances in clinical records,
without requiring the terminology to attend the users’
demand by continuous creation of new concepts. The latter is
known as pre-coordination. An example for a
precoordinated concept is “right hand”, which has the code
78791008 |Structure of right hand (body structure). In
contrast, there is no code for “right thumb”, but the meaning of
this is expressible by post-co-ordination, viz. by the CG
expression 76505004 |Thumb structure (body structure)|:
272741003 |Laterality (attribute)| = 24028007 |Right
(qualifier value), corresponding to the OWL expression:
‘Thumb structure (body structure)’ and
‘Laterality (attribute)’ some ‘Right (qualifier value)’.
ICD – the International Classification of Diseases and
Related Health Problems – is promoted by WHO as “the
standard diagnostic tool for causes of death, epidemiology,
health management and clinical purposes”. However, it is
particularly focused on the analysis of the health of
population groups, and is used to monitor the incidence and
prevalence of diseases and other health problems. The ongoing
11th (ICD-11) revision, named ICD-11-MMS (Mortality,
Morbidity and Standard) is planned to be finalized in 2018.
ICD has recently been characterized as an “aggregation
terminology” [2]. This terminology genre typically contains
rules that enforce the principle of single hierarchies and
disjoint classes. Partitioning ICD-11 into non-overlapping
chapters requires exclusion rules at all hierarchical levels.
E.g., the chapter “circulatory system” excludes infections,
neoplasms, endocrine and congenital diseases called
“developmental”, which have their own chapters. Making ICD
exhaustive requires residual classes (“other specified”,
“other unspecified”), indicated by codes ending in “Y” or “Z”.
named residuals which have no meaning outside the ICD
hierarchy.</p>
      <p>The current study is limited to 428 classes from ICD-11, as
displayed by the WHO browser [5], covering the circulatory
system, and 522 classes covering the digestive system. We
exclude ICD-11 residuals because they are meaningless
outside ICD. The resulting totals are 206 in the circulatory
chapter and 250 in the digestive chapter (see Table 4).
In a first step, we compared the Compositional Grammar
(CG) expressions of lexically mapped ICD11 classes and
SNOMED CT concepts using WHO and
IHTSDO/SNOMED Browsers [4][5]. As explained in [6],
the lexical map is based on ICD 11 class names and
SNOMED CT FSNs or synonyms. In a second step, we
checked if the CG expressions of SNOMED CT concepts
lexically mapped to a single ICD 11 class constituted a fully
equivalent representation of the ICD11 class.</p>
      <p>The details are developed below and summarized in Figure
1 and Table 2.</p>
      <p>We introduce the following symbols for the mapping types:
M (refined by M1 and M2), A (refined by A1 and A2), P
and Z. We consider the mapping of a SNOMED CT
Concept SCi, described by terms STi{1…n} to an ICD class ICi,
described by a name ITi.</p>
      <p>Lexical map


</p>
      <p>The following rules apply for the lexical maps
If there is a full lexical map between the ICD-11 class
name ITi and one SNOMED CT description STi{1…n,
considered as pre-coordinated in SNOMED CT it is
classified as M (for lexical Map) type .</p>
      <p>If there is no lexical map between any ITi and STik , but
if mapping can be achieved to the post-coordination of
two or more descriptions STi{1…n, of SCk , it is
classified as A (for Addition map) type.</p>
      <p>If only a part of ITi of ICi can be lexically mapped to
any STik it is classified as P (for Partial) type.</p>
      <p>Finally, if not even a partial lexical mapping between
any ITi o of ICi and STik is possible, it is classified as Z
(for Zero) type.</p>
      <p>Match of meaning
Subsequently, the defining and constraining axioms of one
or more than one SCi CG expressions were analysed to
check whether they correspond to the totality of the textual
definition and to the hierarchy inheritance of ICi . The
following cases are distinguished:
 M (lexical map) type:
1. This expression fully represents the meaning of ICi,
a complete match meaning is assumed: the
classification is refined to M1.
2. This expression does not fully represent the
meaning of ICi, a new expression is produced according
to CG: the classification is refined to M2.
 A (addition map) type:
1. These expressions fully represent the meaning of
ICi, a complete match meaning is assumed: the
classification is refined to A1.
2. These expressions do not fully represent the
meaning of ICi, a new expression is produced according
to CG: the classification is refined to A2.
 P type:</p>
      <p>For ICi it is then necessary to create a logical
representation based on one existing CG expression plus an
extended de novo CG expression.
 Z type:</p>
      <p>For this ICi it is necessary to create a logical expression
in accordance with SNOMED CT CG .</p>
      <p>In the following, only M and A types will be analysed.
We did not consider the current pre-final version of ICD-11
as a gold standard. Therefore, the total or partial omission
of a SNOMED CT concept that seemed necessary to ICD 11
was not considered an issue, and these cases were omitted.
Neither did we assess the clinical consistency of ICD 11’s
textual definitions. We assessed only the existing CG
expression(s) as to how well they represented the ICD-11 class
textual definitions when the IC11 class names have been
lexically mapped to SNOMED terms or to a minimally
adapted SNOMED CT concept terms. We were conforming
to the assumptions, rules, and standards of the SNOMED
CT concept model when we have to extend the
representation (Types M2 and A2). Two knowledge engineering
master students did the work, one each for the circulatory and
digestive chapters. The same senior ICD-11 and SNOMED
CT expert supervised both.</p>
      <p>Map and meaning
match types</p>
      <p>ICD11
Circ.
count</p>
      <p>Rate
(%)</p>
      <p>ICD11
Digestive
count</p>
      <p>Rate
(%)
Table 3 provides an overview of the results. The two most
frequent lexical map types are M (M1 plus M2) for full
lexical map with a pre-coordinated SNOMED CT concept
and A (A1 plus A2) full lexical map with more than one
post-coordinated SNOMED CT concepts: 78 % for the
circulatory chapter and 89% for the digestive chapter. The
most frequent type is M1 for both. The less frequent types
are Z for no possible lexical map for the circulatory chapter
(1%) and for the digestive chapter (2%). These differences
can be explained by inter-ratter differences (the work was
done by two different knowledge engineering master
students supervised by the same senior terminology expert) or
quality differences between these two chapters either in
WHO ICD 11 or in SNOMED CT or in both.</p>
      <p>Map and ICD11 ICD11 ICD11 ICD11
meaning Circ. Circ. Digestive Digestive
match types system system system system
primitotal primitives total tives
M 1 209 44 (21%) 251 58 (23 %)
To address the quality of the formal descriptions of
SNOMED CT, it is interesting to compare the rate of
primitive SNOMED CT concepts in the different Map and
Meaning match types as shown in Table 4. The types with full
map and meaning match (M1 and A1) have a lower rate of
SNOMED CT primitive concepts (from 21 % to 47%) and
the types with no full match (M2 and A2) have a higher rate
of SNOMED CT primitive concepts (from 52% to 91%).
Nevertheless the primitive concepts rate of full Map and
Meaning match types (M1 and A1) is high when it is
considered that the lexical map was complete between the
ICD11 class name and the SNOMED CT FSN or synonym. On
the contrary, when the lexical map is incomplete we should
have expected a rate nearer from 100 % which is nearly
true for M2 but less for A2.</p>
      <p>It is necessary to go further by taking some examples of
mismatches regarding primitive and fully defined SNOMED
CT concepts.</p>
      <p>As an example for the type M1, the ICD ICD-11 class DA
40.4 Perforation of esophagus is defined by: “Perforation of
esophagus is a penetration or hole of the wall of the
esophagus, resulting in luminal contents in esophagus flowing
into the mediastinum and/or thoracic cavity”. The full
lexical map is with the fully defined SNOMED CT concept
23387001,
Perforation of esophagus (disorder), which is equivalent to
the following (inferred) pre-coordinated SNOMED CT
inferred expression:</p>
      <p>RoleGroup some
((‘Finding site (attribute)’ some</p>
      <p>‘Esophageal structure (body structure)’) and
(‘Associated morphology (attribute)’ some</p>
      <p>‘Perforation (morphologic abnormality)’))
As an example for the type M2, the ICD-11 class BB67.3
Macro re-entrant atrial tachycardia is defined as “An atrial
arrhythmia in which there is intra-atrial re-entry or circus
movement around a fixed or functional central obstacle. The
central obstacle may consist normal (e.g. valves) or
abnormal (e.g., scar) structures. Conduction to the ventricles is
not necessary for the tachycardia to continue. All that is
required is an organised atrial rhythm with a rate typically
between 250 and 350 bpm, including tachycardia using a
variety of re-entry circuits that often occupy large areas of
the atrium (‘‘macro-re-entrant’’). Here the arrhythmia
involves the cavo-tricuspid isthmus”.</p>
      <p>The full lexical map is with the SNOMED CT concept
233893007 Re-entrant atrial tachycardia (disorder), a
primitive concept with the following pre-coordinated SNOMED
CT inferred expression:</p>
      <p>RoleGroup some
((‘Finding site (attribute)’ some
‘Cardiac conducting system structure (body structure.)’)and
(‘Clinical course (attribute))’ some
‘Sudden onset AND/OR short duration (qualif. value)’) and
(‘Has definitional manifestation (attribute)’ some
‘Tachycardia (finding)’) )
This representation lacks the localization of the arrhythmia
at the atrium and the formalization allows representing it as
the following one. The modification to the original
expression is underlined.</p>
      <p>RoleGroup some
((‘Finding site (attribute)’ some
‘Preferential interatrial pathway (body structure)’)and
(‘Clinical course (attribute))’ some
‘Sudden onset AND/OR short duration (qualif. value)’) and
(‘Has definitional manifestation (attribute)’ some
‘Tachycardia (finding)’) )
An example for the type A1 is BA04.3 is Secondary
hypertension associated with renal tubular disorders This ICD-11
class has no definition in most recent version (Jan 2017). A
full lexical map can be done with the SNOMED CT concept
31992008, Secondary hypertension(disorder), a primitive
concept, together with 95568003, Renal tubular disorder
(disorder), a fully defined one, using the following
postcoordinated SNOMED CT inferred expressions, which
introduces the aetiology using the relation DueTo:
Has definitional manifestation (attribute) some</p>
      <p>Finding of increased blood pressure (finding) and
RoleGroup some
(‘Finding site (attribute)’ some
‘Systemic circulatory system structure (body structure)’) and
‘Due to (attribute)’ some Renal tubular disorder (disorder)
As an example for the type A2, let us analyse the ICD-11
class DB02.31 Ig-E mediated allergic enteritis of small
intestine, defined as “Immediate type (IgE-mediated)
enteric hypersensitivity due to exposure to an allergen in
individuals previously sensitized. The symptoms are acute
abdominal pain and diarrhoea and can be combined to other
symptoms in cases of anaphylaxis”. A full lexical map is
possible with the fully defined SNOMED CT concepts
22231002 Allergic enteritis (disorder) and 422076005
Immunoglobulin E-mediated allergic disorder (disorder),
constructing the following expression (addition underlined):
‘Pathological process (attribute)’ equivalentTo
‘Allergic process (qualifier value)’ and
RoleGroup some
((‘Associated morphology (attribute)’ some
‘Inflammation (morphologic abnormality)’) and
(‘Finding site (attribute)’ some
‘Intestinal structure (body structure)’)) and
‘Due to (attribute)’ some</p>
      <p>‘Type 1 hypersensitivity response (disorder)’ and
‘Causative agent (attribute)’ some
‘Immunoglobulin E (substance)’
4</p>
    </sec>
    <sec id="sec-3">
      <title>DISCUSSION</title>
      <p>The study makes the attempt to propose semantically
precise mappings between two independent representation
artefacts (ICD-11 and SNOMED CT), based on OWL-DL,
using the axioms in the SNOMED Composition Grammar
“concept model” (and OWL-EL equivalent to from it),
which are intended to fine what is universally true in a
domain, [7-8].</p>
      <p>The findings are summarised in Table 3: 138 (123 M2 plus
15 A2 )out of 364 SNOMED CT concepts (38%) in the
circulatory chapter and 150 (125 M2 plus 25 A2) out of 424
SNOMED CT concepts (35%) in the digestive chapter from
the Clinical finding hierarchy that were lexically mapped to
ICD-11 classes show modelling issues resulting in
misalignments between the meaning of the ICD-11 MMS classes
(as given by their name, hierarchic context and text
definition) and formal axioms that characterise SNOMED CT
concepts. We equally found misalignments within
SNOMED CT, i.e. between Fully Specified Names and
formal axioms. As shown in Table 4, in most of the cases
this is related to the high number of primitives, i.e. not fully
defined SNOMED CT concepts but as well with some fully
defined concepts.
4.1</p>
      <p>Misalignment between SNOMED CT concept
FSN and primitive representation
There were higher rates of primitive in lexical and meaning
match types M2 vs M1, viz. 91% vs 21% in the Circulatory
chapter and 84% vs 23% in the Digestive chapter; and in A2
vs A1 53% vs 35% in the Circulatory chapter and 52% vs
47% in the Digestive chapter.</p>
      <p>What is challenging is that the OWL axioms allow a fully
defined representation. For example, Essential hypertension
(ICD-11 class BA 00), lexically matched to the SNOMED
CT concept 59621000 Essential hypertension (disorder) is
the most frequent arterial disease. SNOMED CT does not
represent the lack of secondary cause, which is the meaning
of “essential” or “idiopathic”. SNOMED CT CG provides
the possibility to represent the lack of secondary cause by
adding the following expression:
‘Pathological process (attribute)’ some</p>
      <p>‘spontaneous (qualifier value)’
Apart from some other cases of SNOMED CT concepts
with the wording “of unknown etiology” there are
numerous cases of “real” qualifying adjectives that are not
reflected in the definition, such as 85598007, Constrictive
pericarditis (disorder) with no representation of “constrictive”,
373945007 Pericardial effusion (disorder) with no
representation of “effusion” and 706882009 Hypertensive crisis
(disorder) with no representation of “crisis”.
4.2</p>
      <p>Misalignment between SNOMED CT concept
FSN and full definitions
The ICD-11 class DA52.51 Allergic gastritis due to
IgEmediated hypersensitivity can be fully represented by the
SNOMED CT concepts 1824008 Allergic gastritis
(disorder) and 422076005 Immunoglobulin E-mediated allergic
disorder (disorder), both of which are fully defined. The
role of Immunoglobulin E is not represented in the present
version.
4.3</p>
      <p>Inconsistencies across SNOMED CT concept
definitions
It is interesting to try to understand why they are so many
issues: let us take the example of hypertension. In clinical
settings, most healthcare professionals who use
“hypertension” in their daily patient monitoring practice this means
exclusively systemic arterial hypertension, which is a
frequent disease. However, the SNOMED CT concept
59621000 Essential hypertension (disorder) is described by
the expression:</p>
      <p>Has definitional manifestation (attribute) some
Finding of increased blood pressure (finding) and
RoleGroup some (‘Finding site (attribute)’ some</p>
      <p>‘Systemic circulatory system structure (body structure)’)
On the other hand, the SNOMED CT 11399002, Pulmonary
hypertensive arterial disease (disorder) is described with
RoleGroup some (‘Finding site (attribute)’ some</p>
      <p>‘Pulmonary artery structure (body structure)’)
Both are primitive concepts, and since 24184005. Finding
of increased blood pressure (finding) is clinically
understood as a finding measuring only for systemic arterial
hypertension it cannot be applied to Pulmonary hypertensive
arterial disease.</p>
      <p>On the other hand, the CG formalism would allow the
following representations:
‘Pulmonary hypertensive arterial disease (disorder)’
subclassOf
RoleGroup some (‘Finding site (attribute)’ some</p>
      <p>‘Pulmonary artery structure (body structure)’) and
‘Has interpretation (attribute)’ some</p>
      <p>‘Abnormally high (qualifier value)’ and
‘Interprets (attribute)’ some</p>
      <p>‘Blood pressure (observable entity)’
‘Essential hypertension (disorder)’
subclassOf
RoleGroup some (‘Finding site (attribute)’ some
‘Systemic circulatory system structure (body structure)’) and
‘Has interpretation (attribute)’ some</p>
      <p>‘Abnormally high (qualifier value)’ and
‘Interprets (attribute)’ some</p>
      <p>‘Blood pressure (observable entity)’ and
‘Pathological process (attribute)’ some
‘Spontaneous (origin) (qualifier value)’
If the clinical vocabulary (interface terminology) and the
logic-based descriptions were defined independently, this
would reduce the problem. However, there would still be
issues where the full meaning of the natural language
expression would not be captured in the formal logical
expression.</p>
      <p>The difference between flexible human language and
machine-required logic is apparent in the SNOMED CT
Editorial guide [1]. What is an inappropriate synonym when a
synonym is defined by SNOMED as “a term other than the
FSN that is an acceptable way to express the meaning of a
SNOMED CT concept in a particular language”? This
synonym is anchored to a FSN which shall be aligned on the
FSN concept model instance. An inappropriate synonym
must therefore be “an acceptable (or unacceptable) way to
express the meaning of a SNOMED CT concept” and
aligned or not aligned on the FSN concept model instance.
The dimension of this issue is summarized by 24,782 shared
terms between pairs of active concepts either in one
hierarchy or across hierarchies. In the Clinical findings disorder
hierarchy there are 1394 instances of duplicate terms
(around 3%). Across hierarchies, most of duplicate terms
are between Product and Substance, e.g. 53009005
Analgesic (product) and 373265006 Analgesic (substance). Such
definitions (a drug name replaced by the name of the active
ingredient) are acceptable for interface terminologies but
inappropriate for ontological standards. This therefore
suggests a principled reworking of the relations between FSN,
concept model instances and synonyms.</p>
      <p>Another example is related to negation as in Non traumatic
tear of meniscus. The formal SNOMED CT expression is
based on their Compositional Grammar (equivalent to
OWL-EL and EL++ without disjointness), which does not
support any form of negation. Here the question arises
whether the negative expression might be rather restricted to
a common interface term feature or represented in CG. Such
an interface term, in our example, could point to a fully
specified name Degenerative tear of meniscus. But on a
logic basis as there are developmental, inflammatory, or
other non-traumatic non-degenerative tears it does not
appear correct to equate non-traumatic and degenerative
cartilage tears. The issue is that even if negation is
understandable at the clinical interface terminology level it cannot be
represented with the SNOMED formalism. The logical
alternative is to point the negated concept at the alternative
concepts – developmental, degenerative, etc.</p>
      <p>This is the base of the solution we recommend to represent
such concepts or classes clinical names. For example, it is
possible to represent the closely related notion “tears of
meniscus excluding traumatic tears” as a query on the
representation (codes) for “ tears of meniscus” which is an
axiomatized expression minus the representations (codes) or
“traumatic tears of meniscus” as recommended in [8].
5</p>
    </sec>
    <sec id="sec-4">
      <title>CONCLUSION</title>
      <p>To answer the main question of this paper, viz. whether the
logic based expressions in SNOMED CT are blurred by a
primarily language-driven modelling approach, we can state
the following points as a route to an answer:
SNOMED CT currently integrates two aspects, a reference
clinical terminology and a formal ontology.</p>
      <p>It is necessary to distinguish clearly the part of SNOMED
CT natural language definition to be used as the basis of a
formal representation in the Composition
Grammar/Description Logic from the part used for the
management of the clinical interface vocabularies used by clinicians
in electronic health records. Clinical language is
characterised by lexical ambiguities due to brevity and assumed
context. The words used by clinicians often hide widely
understood conventions that, if taken literally, give rise to
incorrect formal representations.</p>
      <p>Given the conflict between clinical usage and formal
representation, errors in the axiomatized formal content arise
easily. External validation of the axiomatic content in
SNOMED CT is critical to reach validated DL-based (or
any other logic-based) model medical knowledge and
concept descriptions. The harmonization of SNOMED CT with
ICD-11 provides one example of such an external
validation.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>SNOMED CT® Editorial Guide January 2017 International Release (US English</surname>
          </string-name>
          <article-title>) chapter 2.1. snomed.org/eg last access 15 may 2017 Rodrigues JM</article-title>
          ,
          <string-name>
            <surname>Robinson</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Della Mea</surname>
            <given-names>V</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Campbell</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rector</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schulz</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brear</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Üstün</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spackman</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chute</surname>
            <given-names>CG</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Millar</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solbrig</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brand Persson K. Semantic</surname>
          </string-name>
          <article-title>Alignment between ICD-11 and SNOMED CT</article-title>
          .
          <article-title>Studies in health technology and informatics</article-title>
          .
          <year>2015</year>
          ;
          <volume>216</volume>
          :
          <fpage>790</fpage>
          -
          <lpage>794</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>SNOMED CT Compositional Grammar. Version 2.3</source>
          .1 may
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          http://snomed.org/scg last access 15 may
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <given-names>IHTSDO</given-names>
            <surname>Browser</surname>
          </string-name>
          . http://browser.ihtsdotools.org/ last access 30 may 2017 WHO Browser. http://who.int/classifications/icd11/browse/f/en. Last access 08 may 2017 Mamou M,
          <string-name>
            <surname>Rector</surname>
            <given-names>AL</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schulz</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Campbell</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solbrig</surname>
            <given-names>H</given-names>
          </string-name>
          , Rodrigues.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Representing</surname>
            <given-names>ICD</given-names>
          </string-name>
          <article-title>-11 JLMMS Using IHTSDO Representation Formalisms</article-title>
          .
          <source>Studies in Health Technology and Informatics</source>
          .
          <year>2016</year>
          ;
          <volume>228</volume>
          :
          <fpage>431</fpage>
          -
          <lpage>435</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Reiter R.</surname>
          </string-name>
          <article-title>On closed world data bases</article-title>
          . In H. Gallaire and J. Minker, editors,
          <source>Logic and Data Bases</source>
          , Plenum, New York.
          <year>1978</year>
          ,
          <fpage>55</fpage>
          -
          <lpage>76</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Schulz</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodrigues</surname>
            <given-names>JM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rector</surname>
            <given-names>AL</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chute</surname>
            <given-names>CG</given-names>
          </string-name>
          .
          <article-title>Interface Terminologies, Reference Terminologies and Aggregation Terminologies: A Strategy for Better Integration</article-title>
          .
          <source>Studies in Health Technology and Informatics</source>
          .
          <year>2017</year>
          : accepted for publication de Matos,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Alcántara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Dekker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Ennis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Hastings</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Haug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Spiteri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Turner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            , and
            <surname>Steinbeck</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          (
          <year>2010</year>
          ).
          <article-title>Chemical Entities of Biological Interest: an update</article-title>
          .
          <source>Nucl. Acids Res</source>
          .,
          <volume>38</volume>
          ,
          <fpage>D249</fpage>
          -
          <lpage>D254</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>