<!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>Estimating and Analysing Coordination in Medical Terminologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Cornelia Hedeler</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bijan Parsia</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastian Brandt</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Computer Science, The University of Manchester</institution>
          ,
          <addr-line>Manchester</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Medical vocabulary is complex, expanding, and convoluted not least because of the large numbers of compound terms. Formalized medical terminologies such as SNOMEDCT and ICD-10 take one of two strategies when representing medical language: so-called pre-coordination where valid compound terms are included explicitly in the terminologies and so-called post-coordination where the terminology consists of a basis and a generative function from which the compound terms may be derived. However, these notions are not used with particular precision in the literature. In this paper, we provide a formalization of the notion of coordination, a technique for estimating the degree of coordination in a given system, and an examination, based on our technique, of the coordination level of a number of major existing terminologies.</p>
      </abstract>
      <kwd-group>
        <kwd>pre-coordination</kwd>
        <kwd>post-coordination</kwd>
        <kwd>medical vocabularies</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Controlled medical terminologies have long played an important role in the drive to improve
patient care, e.g., in Electronic Health Records (EHR), decision support and expert systems,
medical literature databases, and data exchange [
        <xref ref-type="bibr" rid="ref17 ref19 ref27">19, 17, 27</xref>
        ]. A large number of medical
terminologies have been developed, including the Systemized Nomenclature of Medical Clinical Terms
(SNOMED CT) [
        <xref ref-type="bibr" rid="ref21 ref6">21, 6</xref>
        ], the International Classi cation of Diseases and Related Health Problems,
9th Revision - ICD-9 and more recently its 10th Revision ICD-10 both with Clinical Modi
cations (CM) and Procedure Coding System (PCS) [
        <xref ref-type="bibr" rid="ref10 ref11 ref39">10, 39, 11</xref>
        ], and the National Cancer Institute
(NCI) thesaurus [
        <xref ref-type="bibr" rid="ref16 ref8">8, 16</xref>
        ].
      </p>
      <p>
        Term composition [24{26] or as it is more recently (in particular in the context of SNOMED
CT) called, (pre-/post-) coordination [
        <xref ref-type="bibr" rid="ref23 ref35">23, 35</xref>
        ] in medical terminologies has been a concern for
developers of standard terminologies [
        <xref ref-type="bibr" rid="ref41">41</xref>
        ] and end-users [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] alike. For example, end users can
struggle with post-coordination [
        <xref ref-type="bibr" rid="ref12 ref22 ref30 ref33">22, 30, 12, 33</xref>
        ], but pre-coordination brings its challenges during
development and maintenance and can lead to an exponential explosion of the terminology size
[
        <xref ref-type="bibr" rid="ref26 ref32">26, 32</xref>
        ], which in turn can make it hard for end-users to determine the appropriate term to use. In
addition, di erent levels of coordination can make data exchange between systems and mapping
of di erent terminologies harder, requiring additional approaches to handle the di erences in
coordination [
        <xref ref-type="bibr" rid="ref42">42</xref>
        ].
      </p>
      <p>
        These discussions have led to repeated suggestions of terminologies to consist of a base of
atomic concepts, with a function, e.g., in form of a grammar or a description logic ontology,
specifying how to compose the atomic terms to form more complex terms [
        <xref ref-type="bibr" rid="ref24 ref26 ref27 ref32 ref38">24, 26, 32, 38, 27</xref>
        ].
Despite the longevity of the discussion on composition of terminologies, there is no consensus
on when a style is to be preferred or even exactly what constitutes a pre- or post- coordinated
vocabulary. There are current exemplars of each style, e.g., the heavily pre-coordinated ICD-10
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and, SNOMED [
        <xref ref-type="bibr" rid="ref32 ref40">40, 32</xref>
        ], the poster child for post-coordination.
      </p>
      <p>Examples of pre-coordinated terms include 'Removal of External Fixation Device from Left
Upper Femur, Open Approach', a procedure in ICD-10-PCS, "Removal of implanted devices from
bone, femur", a procedure from ICD-9 procedures, which contains less detail (no detail on the
location of the femur or the kind of approach used for the removal of the implanted device) than
the procedure in ICD-10, i.e., could be considered to be less coordinated. Similarly, the procedure
'Removal of internal xation device of femur' in SNOMED CT, even though less coordinated
than the procedure in ICD-10, would still be considered to be coordinated as there is potential
for further decomposition, e.g., into the procedure itself, i.e., 'removal', the object that is being
removed, i.e., 'internal xation device', and the location from where it is being removed, i.e.,
'femur'. SNOMED CT also contains atomic terms to be used for post-coordination, for example,
'laterality' along with 'left' and 'right', but also pre-coordinated terms such as 'X-ray of left foot'.</p>
      <p>However, so far no computational method to determine the level of coordination of
terminologies has been available. In this paper, we propose a method for estimating the level of
coordination of a given terminology and determine the coordination level of a number of standard
terminologies.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <p>Consider a simple clinical terminology, T1, that contains a single term, Back Pain, that is:</p>
      <p>While Back Pain is atomic, that is, a single term with no substructure, it is clear from our
perspective that it is a compound term. That is, it is composed of two sub-terms which themselves
are clinically relevant, to wit Back and Pain which gives us an alternative terminology:</p>
      <p>We, of course, can generate T1 from T2 via a suitable function. The simplest correct function
would be a map from a subset of T2 (i.e., fBack; Paing) to the corresponding term in T1 (i.e.,
Back Pain). If we extend T1 and T2 we need to extend our mapping function as well:
T1 = fBack Paing</p>
      <p>T2 = fBack; Paing
T10 = fBack Pain, Heart Pain, Stomach Paing</p>
      <p>T20 = fBack, Heart, Stomach, Paing</p>
      <p>M ap =
ffBack,Paing ! Back Pain
fHeart,Paing ! Heart Pain
fStomach,Paing ! Stomach Paing
We can also encode M ap by means of a simple grammar:</p>
      <p>M ap2 =</p>
      <p>Term ::= Location; ; Pain
Location ::= Back | Heart | Stomach
(1)
(2)
(3)
(4)</p>
      <p>While M ap2 is rather more illuminating than M ap or T10 and contains more information than
T20 (T20 is not, by itself, su cient to generate exactly T10), it is conceptually more complicated,
i.e., we have to understand a BNF style formalism. While M ap2 is very simple, it is easy to
imagine situations that are inherently more complicated:</p>
      <p>M ap3 =</p>
      <p>Location ::= LocationWithLateralityj Back | Heart | Stomach
LocationWithLaterality ::= Laterality; ; Leg</p>
      <p>Laterality ::= Right | Left</p>
      <p>Whole&amp;terminology
Sanc1onable&amp;terminology
Explicit&amp;terminology</p>
      <p>Base</p>
      <p>
        The more exceptions and irregularities, the more di cult it is to come up with an exact and
yet intelligible description of the mapping, or, for that matter, a terser description. In addition,
ideally the map should only allow the construction of complex terms that are sensible for the
domain. If that is not possible, additional constraints, also known as sanctions, have to be added
to specify which compositions that can be built following the map, are meaningful, and thus are
allowed or sanctioned [
        <xref ref-type="bibr" rid="ref13 ref20 ref37">20, 37, 13</xref>
        ].
      </p>
      <p>If we consider the set of compound terms generated from M ap3, there are only 5. If we include
the \intermediate" terms (e.g., Right Leg), there are only 7, and if we include the base as well,
there are a mere 12. Thus, the enumeration of the terms is shorter than the grammar itself, in this
simple case. However, extending the set of terms with laterality causes the generated terms to
grow more quickly than the base set or the grammar. And it is easy to see that terminologies with
more dimensions can have even more dramatic gaps between the enumerative and the descriptive
presentations of the terminology.</p>
      <p>In general, a terminology (even idealised as complete) will not be fully enumerative or fully
descriptive. Instead, given a set of base terms that are truly atomic, we can project a structure
between the basis and the total terminological space generated from that basis. (Note, that if
we allow for arbitrary iteration of base terms in a compound term, then the full space will be
in nite.) Figure 1 illustrates a slightly idealised structure of a representation of a vocabulary.
The \real" vocabulary, that is the set of terms which are meaningful for a domain, corresponds
to the sanctioned terminology. A terminology might include a degree of pre-coordination in the
form of an explicit set of coordinated terms without fully covering the vocabulary. This might
be because the terminology is incomplete or that there are some compound terms which are so
common or signi cant that the terminology designer wanted to make them more salient. Finally,
there may be terms in the basis or explicit terminology which are not domain signi cant, at least,
in isolation.</p>
      <p>Note that this sort of phenomenon is not limited to terminologies per se. For example, we
might have a hierarchical terminology where the hierarchical relations are themselves aspects of
the coordination. (It is easy to see that we could generate a term plus a list of parent terms via
a mapping function.) Similarly, we might be generating forms from a base \vocabulary" of form
elements, and so on.</p>
      <p>Furthermore, the map could be described in any number of formalisms, for example, by a
description logic ontology.</p>
      <p>With this picture, it is straightforward to articulate the classic trade o s between pre- and
post-coordinated terminologies. A post-coordinated vocabulary has the possibility of 1) being
more \compressed" in size but also 2) it can be expressed in a more perspicuous way. Instead of
having a huge pile of terms, we can isolate important subgroups of terms and characterise them
by their contribution to a mapping function. This can potentially support more e ective review
for correctness and completeness of the terminology itself and of systems that make use of it, as
well as just lowering the cost of maintenance (since we have \fewer things" to look at or connect
to other parts of a system).</p>
      <p>Contrariwise, while we might have fewer things to look at, each thing might be signi cantly
more complex. The correctness of a coordination function with respect to the sanctioned
vocabulary might be quite di cult to determine. Furthermore, the execution of the coordination
function to generate or validate a term might be expensive in computational resources, and it
might not be obvious \how much" of some section of the vocabulary to manifest for a particular
situation.
3
3.1</p>
    </sec>
    <sec id="sec-3">
      <title>Methods</title>
      <sec id="sec-3-1">
        <title>Formalization</title>
        <p>Intuitively, coordination is a process of inductive composition, that is, a coordination of a (base)
terminology is a recursively de ned function over that terminology. Since we can de ne such
functions arbitrarily over any given basis, just identifying coordinations with recursively de ned
sets is not particularly illuminating. In our case, the point of coordination is to capture some
speci c set of terms (i.e., exactly the meaningful ones).</p>
        <p>De nition 1. A vocabulary, V, is a set of terms such that each term is meaningful wrt to a
domain and the set is exhaustive of such terms.</p>
        <p>\Meaningfulness" is domain and application speci c.</p>
        <p>De nition 2. A terminology T is a coordination of another terminology T' just in case there is
a function, f , which is a recursive de nition of T' with the base cases all lying in T and T' V.
We call f the coordinating or coordination function. We call T 0 the basis of the coordination or
the coordinated terminology.</p>
        <p>In the most natural instance, a term is a string and a canonical coordinating function
constructs a new term by concatenating the old ones. For our current purposes, it su ces to be this
narrow.</p>
        <p>Clearly, a coordination can, but does not have to, contain its basis. It may also only contain
part of its basis. For example, a terminology might not contain left on its own even though
left is part of its basis. For the target application, left might not be meaningful on its own.
Furthermore, we can arrange coordinations in a partial order and there is always the possibility
of exactly capturing V.</p>
        <sec id="sec-3-1-1">
          <title>De nition 3. T is more coordinated than T 0 (T 0 not a coordination of T .</title>
        </sec>
        <sec id="sec-3-1-2">
          <title>T ) if T is a coordination of T 0 and T 0 is</title>
          <p>De nition 4. A coordination, T , is saturated or fully coordinated if T = V.</p>
          <p>A saturated coordination might still be extensible, i.e., there are still desired terms not in the
coordination, but any extension requires an extension to the basis. It is highly likely that few
terminologies are saturated, especially if we allow for all clinically meaningful, i.e., sanctionable
terms.</p>
          <p>De nition 5. The coordination factor (relative to a basis) of T is the size of T / the size of the
basis.</p>
          <p>It might be the case that there are several possible bases or that the true basis is unknown.
In the rst case, a given coordination factor might not be determinate. In the second case, it
might not be precise.</p>
          <p>It is possible that we have the following situation:
1. There is a basis, B
2. a terminology, T , which is what is physically manifested and delivered,
3. another terminology Ttotal, which is the complete set of terms for the application or domain
(i.e., Ttotal, is saturated)
where B T Ttotal. In this case, T is partially pre-coordinated (since it is less coordinated
than its saturation). The pre-coordinated terms might be the most frequently used, or the most
convenient for use, or they might form a more intuitive basis of the full coordination.
Speculatively, we might expect that the coordination factor (relative to B) of Ttotal to be an order of
magnitude greater than that of T in a nicely designed system.
3.2</p>
          <p>
            Approach for estimating level of coordination in medical terminologies
It is not immediate how to determine the amount of coordination in a given terminology,
especially if we are aiming at the inherent amount of coordination. This requires determining the
smallest basis for the terminology and even highly factored systems may not be minimal. In more
typical cases or in highly pre-coordinated terminologies, the basis may never have been made
explicit. Estimates for the size of the basis of medical terminologies have varied widely between
20,000 and 1,000,000 [
            <xref ref-type="bibr" rid="ref24 ref34">24, 34</xref>
            ].
          </p>
          <p>However, we can attempt to estimate the amount of coordination in existing terminologies by
parsing and analysing the terms explicitly present in the terminology. To obtain loose lower and
upper bounds of the size of the basis for each terminology, we have analysed the full descriptions
of the terminologies listed in Table 1 using two di erent approaches, described in the following.
For the purpose of this analysis we were only interested in the level of coordination of the core
terms of each terminology, therefore chose to ignore synonyms that are available for some of the
terminologies analysed.
Approach 1: We have tokenized the descriptions by breaking them up into separate tokens using
the Apache Lucene1 standard tokenizer. On the one hand, this approach results in single tokens
to be considered as part of the basis that domain experts would potentially not consider to be
part of the basis (e.g., stop words, such as 'of', 'the', 'in', and words that do not make sense on
their own in the context of the terminology, e.g., 'due', 'using', or 'object'). On the other hand,
concepts that domain experts might consider to be part of the base, but that consist of multiple
tokens are missed (e.g., 'blood group', 'cardiac arrest', or 'foreign body').</p>
          <p>Approach 2: Some stop words, such as 'of', 'and', 'with', or 'by'2 and punctuations, such as ',',
can be considered as indicators for pre-coordination of a term. Following this intuition, we have
broken up the descriptions into the parts that are separated by any of these stop words and
commas while excluding these words from the basis. Following this approach, for example, the
term 'entire superior segment of left lower lobe of lung', a term specifying a body structure in
SNOMED CT, is broken up into 'entire superior segment', 'left lower lobe', and 'lung'. However,
if laterality, such as 'left' and 'right' is considered to be part of the basis, 'left lower lobe' could
further be broken up into 'left' and 'lower lobe', the latter of which could potentially be further
broken up into 'lower' and 'lobe'. Examples where this approach is successful in identifying what
could be considered atomic concepts include 'fracture of pelvis' (i.e., 'fracture', 'pelvis') in NCIt,
'incision and drainage of perianal abscess' (i.e., 'incision', 'drainage', 'perianal abscess')
procedure in SNOMED CT, or 'removal of drainage device from lower back, percutaneous endoscopic
approach' (i.e., 'removal', 'drainage device', 'lower back', 'percutaneous endoscopic approach')
procedure in ICD-10-PCS.</p>
          <p>For each terminology, we then identi ed the set of unique terms or atomic concepts, i.e., the
basis B of the terminology produced by each of the two approaches. Once we have the size of
the basis, it is easy to determine the coordination factor of the terminology (see De nition 5).</p>
          <p>In addition to the coordination factor itself, there are other measures that can provide
indications of the level of coordination of the terminologies. These include the length of the descriptions
with respect to the number of tokens or atomic concepts of the base, and the usage of the
tokens or atomic concepts of the base, i.e., how many of the concepts in the base are used in the
pre-coordinated terms and how often they are used. In case of the former, longer terms suggest
higher levels of coordination, and for the latter, more frequent usage of a greater number of
concepts of the base also suggest higher levels of coordination. In contrast, in a predominantly
post-coordinated terminology, the average length of the descriptions would be expected to be
fairly short and none or very little re-use of the concepts of the base would be expected.</p>
          <p>To evaluate the length of the descriptions, we have calculated the distribution of terms with a
particular number of tokens as identi ed using the rst approach as well as the maximum, median
and average number of atomic concepts in terms as determined by approach 2. To determine
the usage of the concepts in the basis, we have calculated the maximum, median and average
occurrence of tokens and atomic concepts determined by both approaches, as well as the number
and percentage of tokens that appear only in a single term, along with the average length of those
terms with respect to its number of tokens. We expect that not all members of the base contribute
equally to the pre-coordination of a terminology, i.e., some tokens might appear more frequently
than others and a number of them might only be used once. In the case of terminologies that
support post-coordination, some of the tokens that appear only once might be atomic concepts
to be used for post-coordination, but others might be tokens that are only used very rarely. To
1 http://lucene.apache.org
2 complete list: f"and", "at", "by", "for", "from", "in", "into", "no", "not", "non", "of", "on", "or",
"with", "within", "without"g
gain an insight into the change in level of coordination of a terminology during its life cycle, we
have analysed the coordination factor and the sizes of the base (using approach 1) and the whole
explicit terminology of 115 versions of the NCI thesaurus released almost every month between
late 2003 and July 2013.</p>
          <p>
            Unfortunately, determining the saturated coordination is not possible without out of band
knowledge of the coordinating function. This might be given by a set of rules or by examining
the pattern of use in a large application. It is not clear whether we can give an interesting loose
estimation: If we allow arbitrary repetition of base terms in coordinated terms, then we have
an in nite number of possible terms. If we disallow repetition, the total possible set of terms is
exponential in the size of the basis. It is highly unlikely that the true saturated coordination is
remotely close in size to the potential term space, as most combinations of terms from the basis
will be clinically nonsensical [
            <xref ref-type="bibr" rid="ref34 ref36">36, 34</xref>
            ].
3.3
          </p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>Source Data</title>
        <p>
          Where available, we collected the OWL representation of ontologies (SNOMED CT, NCIt, FMA,
and Gene Ontology), in all other cases we collected the source les from the terminologies listed
in Table 1. The terminologies are grouped according to their contents, with the rst group
containing SNOMED CT and NCI thesaurus (NCIt) representing general terminologies. The second
group covers diagnosis descriptions and contains ICD-9-CM, ICD-10-CM and the corresponding
subsets disorder and ndings of SNOMED CT as well as the Clinical Observations Recording
and Encoding (CORE) subset [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ] of SNOMED CT, which contains terms frequently used in
problem lists and was placed into this group based on the analysis of its content in comparison to
ICD carried out in [
          <xref ref-type="bibr" rid="ref40">40</xref>
          ]. The third group covers procedures and contains the ICD-9 procedures,
ICD-10-PCS and the corresponding subset of SNOMED CT and SNOMED CT CORE describing
procedures. The fourth group covers anatomy and contains the Foundational Model of Anatomy
ontology and the corresponding body structure subset of SNOMED CT. The remaining groups
are LOINC along with its subsets of the top 2000 most frequently used lab results and the top
300 most frequently used lab orders, and the whole of the Gene Ontology (GO) along with its
separate parts covering biological processes, cellular components and molecular functions.
Subsets of the most frequently used terms, i.e., CORE problem subset of SNOMED CT and the
subsets of LOINC, were analysed separately in addition to the whole terminology to evaluate
whether a di erence in coordination level of the most frequently used terms in comparison to
the whole terminology can be observed.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Results</title>
      <p>The distributions of terms with a certain number of tokens as determined using approach 1 are
shown in Figure 2. The increase in the length of the terms in ICD suggest an increase in the
level of coordination in both cases, ICD procedure and diagnosis between the last release of
ICD-9 in 2012 and the most recent release of ICD-10. Di erences can also be observed between
the CORE subset of SNOMED CT and the corresponding whole set of terms as illustrated in
the case of SNOMED CT and CORE SNOMED CT, as well as the corresponding subsets for
disorder and nding, with the terms in the CORE subset tending to be shorter, and potentially
less coordinated. A comparison of the distributions of tokens of a particular length between
SNOMED CT in Figure 2 and NCIt in Figure 4, NCIt appears to be less coordinated.</p>
      <p>The results of the analysis of the size of each terminology as well as the size of the
corresponding basis, the median and maximum length of the terms and the coordination factor with
respect to the basis determined using both approaches 1 and 2 are shown in Table 2. Table 3
presents the results of the usage analysis of the terminologies, i.e., how many members of the
base occur in how many terms and how many members of the basis occur only once.</p>
      <p>
        Considering that SNOMED CT supports and encourages post-coordination, its
coordination factor is perhaps higher than expected, in particular when compared to pre-coordinated
terminologies such as LOINC. However, evaluations of SNOMED CT suggest that it contains a
mixture of pre-coordinated terms and atomic terms that can be post-coordinated (e.g., [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]). The
analysis of various of the categories of SNOMED CT covering, e.g., disorder, nding, procedure,
and body structure, to mention only those included here, shows signi cant di erences in their
coordination factors, e.g., 6.33 for body structure and 2.97 for nding (for approach 1). Similar
di erences have been observed for other categories not included here. This would suggest that
the coordination factor of the whole of SNOMED CT might not be representative and further
analyses would best be carried out on the subsets covering individual categories. Similar di
erences between the whole terminology and its speci c subsets can also be observed for the Gene
Ontology.
      </p>
      <p>SNOMED  CT  disorder  
CORE  SNOMED  CT  disorder  </p>
      <p>ICD-­‐9  2012  diagnosis  
ICD-­‐10-­‐CD  2014  diagnosis  
SNOMED  CT  </p>
      <p>CORE  SNOMED  CT  </p>
      <p>SNOMED  CT  finding  
CORE  SNOMED  CT  finding  
ICD-­‐9  2012  procedure  
ICD-­‐10-­‐PCS  2014  procedure  
25.00%  
20.00%  
15.00%  
10.00%  
5.00%  
0.00%  
30.00%  
25.00%  
20.00%  
15.00%  
10.00%  
5.00%  
0.00%  
14.00%  
12.00%  
10.00%  
8.00%  
6.00%  
4.00%  
2.00%  
18.00%  
16.00%  
14.00%  
12.00%  
10.00%  
8.00%  
6.00%  
4.00%  
2.00%  
0.00%  
25.00%  
20.00%  
15.00%  
10.00%  
5.00%  
0.00%  
1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23  
1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23  
Fig. 2. Distribution of terms with a certain number of tokens, x-axis: number of tokens, y-axis: percentage
of terms in the terminology with number of tokens
1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26  </p>
      <p>1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24  
SNOMED  CT  disorder  </p>
      <p>SNOMED  CT  finding  
1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24  </p>
      <p>ICD  diagnosis  
Terminology</p>
      <p>An observation that applies to both terminologies for which subsets of frequently used terms
could be obtained (SNOMED CT and LOINC) is that the coordination factor of the frequently
used terms are signi cantly lower than those of the whole terminology, even when the
corresponding subsets for the categories in SNOMED (disorder and nding) are considered. In the
case of SNOMED this could suggest that the most frequently used terms are atomic concepts
that are being post-coordinated, however, as LOINC does not support post-coordination, this
does not apply to LOINC.</p>
      <p>
        A signi cant increase in the coordination factor can be observed for both, the diagnosis and
the procedure codes between ICD-9 and ICD-10, with the former increasing from 2.48 to 12.79
and the latter from 1.80 to 53.51 (for approach 1) with the base decreasing in size in the case
of the latter. ICD-10 aims to contain an as complete as possible list of variations of diagnoses
and procedures, with, in particular the procedures being descriptions of the procedures rather
than their names [
        <xref ref-type="bibr" rid="ref39">39</xref>
        ], which could explain the high coordination factors. The observation of a
high level of pre-coordination is further supported by the low percentage of tokens of the base
obtained using approach 1 that are not re-used in multiple terms, i.e., that occur only once. As
can be seen in Table 3, the percentages for ICD-10 are lower than the percentages observed for
the other terminologies, with a signi cantly lower percentage of tokens not used multiple times
for the procedures in ICD-10 (only about 5%), which means that 95% of the basis of ICD-10 is
used multiple times.
      </p>
      <p>In contrast, the percentage of those that occur only in a single term is surprisingly high across
the majority of the other terminologies (around 50%) with the median length of the terms in
which these rarely used tokens appear suggesting that these are not only atomic concepts to be
used for post-coordination, which is only supported by SNOMED CT.
25,000"
20,000"
15,000"
10,000"
5,000"</p>
      <p>Number'of'terms'with''
a'given'length'of''
numbers'of'tokens'</p>
      <p>The results of the analysis of the NCI thesaurus, namely the observed change in coordination
factor, increase in size of the base as well as the whole terminology and the changes in the
distribution of terms with a particular number of tokens are shown in Figures 3 and 4. In comparison
to the change in coordination factor observed between ICD-9 and ICD-10, the coordination
factor of NCIt does not change signi cantly over time. However, the plot of the coordination factor
over time on the left hand side of Figure 3 suggests that e orts are being undertaken to reduce
the level of coordination of NCIt, which is followed by an increase of the co-ordination factor,
most likely due to new terms being added to the NCI thesaurus. The reductions in the level of
coordination do not correlate with signi cant reductions in the size of the terminology or the
length of the terms, as can be seen by the steady increase of both (see on the right hand side of
Figure 3 and Figure 4).
5</p>
    </sec>
    <sec id="sec-5">
      <title>Discussion</title>
      <p>
        The key advantage of our technique for determining the coordination factor along with
supporting measures providing indications for the level of coordination is that it is done completely
analytically and computationally. No domain expertise or manual inspection of a sample of
terms (a la [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]) is required. Furthermore, we do not need access to the often implicit, inchoate,
or incomplete actual coordination function in order to gain some insight into the coordination
strategy of the terminology. The price of these conveniences is that we currently have no method
for estimating the saturated variant (and thus estimate the amount of post-coordination needed)
and the process generates no material level insight into the structure of the terminology (for the
simple reason that it does not examine the content per se). While the lack of content insight is
inherent in any analytical approach, the inability to estimate the true term space is unfortunate
and can a ect the actual coordination factor, as can be seen by the results produced using the
two di erent approaches (see Table 2). We hope to address this lack with extrapolation methods
based on 1) the distribution pattern of terms, 2) a semantic and frequency based categorization
of the basis, and 3) token combination pattern learning, and more domain aware approaches.
      </p>
      <p>
        The coordination level has previously been suggested as a quality measure for terminologies
[
        <xref ref-type="bibr" rid="ref31">31</xref>
        ]. For example, it is easy to see the dramatic increase in pre-coordination between ICD-9
and ICD-10. Perhaps more surprising is the relatively high coordination factor for
SNOMEDCT, although it is well known that while SNOMED-CT is geared toward post-coordination in
general, it contains a substantial number of pre-coordinated terms (e.g., [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]). We intend to
extend such analyses to other aspects of terminologies, such as hierarchical relations.
      </p>
      <p>
        Di erent levels of coordination in di erent terminologies have also been shown to cause issues
or require additional work when mapping between terminologies (e.g., [
        <xref ref-type="bibr" rid="ref15 ref42">15, 42</xref>
        ]). Having an easily
computable measure of the level of coordination can help assess the e ort required to map
between di erent terminologies. Further analysis, such as overlap of the bases could further help
with the assessment of the e ort required.
      </p>
      <p>In case of terminologies that are being adapted from pre-coordinated to post-coordinated
terminologies, the measures presented here enable a continuous assessment of the progress made
in the conversion process.</p>
      <p>As the analysis presented here suggests that most commonly used terms have a lower
coordination factor than the terminology, highly coordinated terms might deserve some analysis
to determine the reasons for their limited usage and whether they could be removed from the
terminology or whether they are pre-coordinated terms of post-coordinated most commonly used
terms.</p>
      <p>
        In addition to having a measure for assessing the level of coordination in terminologies, the
basis that is obtained as part of the process presented here, can also be utilised further. The
analysis of the usage of the basis can highlight tokens or atomic concepts that are rarely used,
and perhaps deserve further analysis to decide whether they should be included in the basis, or
whether some pre-coordinated terms have been missed. The basis itself could prove useful for
the maintenance and development of the terminology. For example, an agreed canonical basis
of the preferred names for the atomic concepts to be used with synonyms could be utilised to
ensure that the preferred term is used, and not one of the multiple synonyms. For example,
inconsistencies in term usage, such as in the ndings in SNOMED CT 'Amputated big toe' and
'Cock-up deformity of great toe' where the big toe is called big toe in one nding and great toe in
the other nding. The same inconsistency can be observed in FMA, e.g., 'Dorsal surface of great
toe' and 'Eponychium of big toe'. Other examples include the representation of ordinal numbers,
which are written out in some terms and written as numbers in other terms within the same
terminology. This inconsistent usage could be one reason for the observed high percentage of
rarely used tokens in the basis. In NCIt, the following terms can be found: 'Cardiac Arrest' and
'CTCAE Grade 5 Asystole'. Using the Uni ed Medical Language System (UMLS) [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] to lookup
synonyms for 'cardiac arrest' suggests that 'asystole' is a synonym. Ideally, the same name for
a concept would be used consistently throughout the whole terminology. This, however, is very
hard to ensure without the knowledge of the basis of the terminology.
      </p>
      <p>In addition to the basis, a coordination function could furthermore help to ensure that the
order in which the pre-coordinated complex terms are created is consistent, e.g., in ICD-10, a
diagnosis called 'Abrasion, left great toe' can be found, with the laterality associated with the
great toe, without the explicit mention of the foot to which the great toe belongs. In contrast, the
diagnosis called 'Fused toes, left foot' lists the corresponding foot and assigned the laterality to
the foot rather than the toes. These inconsistencies make maintenance and usage of terminologies
harder, and could be avoided with the identi cation and then usage of coordination functions.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>1. FMA, http://sig.biostr.washington.edu/projects/fm/</mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>2. GO, http://www.geneontology.org</mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. ICD-10
          <string-name>
            <surname>-CM</surname>
          </string-name>
          , http://www.cms.gov/Medicare/Coding/ICD10/2014-ICD-10
          <string-name>
            <surname>-</surname>
            <given-names>CM</given-names>
          </string-name>
          <string-name>
            <surname>-</surname>
          </string-name>
          and
          <string-name>
            <surname>-GEMs</surname>
          </string-name>
          .html
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>4. ICD-10-PCS, http://www.cms.gov/Medicare/Coding/ICD10/2014-ICD-10-PCS.html</mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>5. ICD-9, http://www.cms.gov/Medicare/Coding/ICD9ProviderDiagnosticCodes/codes.html</mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>International</given-names>
            <surname>Health Terminology Standards Development Organisation</surname>
          </string-name>
          (IHTSDO), http://www. ihtsdo.org/
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>7. LOINC, http://loinc.org</mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>8. NCIthesaurus, http://ncit.nci.nih.gov</mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>9. SNOMED, http://www.nlm.nih.gov/research/umls/Snomed/core_subset.html</mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. WHO |
          <article-title>International Classi cation of Diseases (ICD)</article-title>
          , http://www.who.int/classifications/ icd/en/
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Averill</surname>
            ,
            <given-names>R.F.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mullin</surname>
            ,
            <given-names>R.L.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steinbeck</surname>
            ,
            <given-names>B.A.B.</given-names>
          </string-name>
          , Gold eld,
          <string-name>
            <given-names>N.I.N.</given-names>
            ,
            <surname>Grant</surname>
          </string-name>
          ,
          <string-name>
            <surname>T.M.T.</surname>
          </string-name>
          :
          <article-title>Development of the ICD-10 Procedure Coding System (ICD-10-PCS)</article-title>
          .
          <source>Journal of AHIMA / American Health Information Management Association</source>
          <volume>69</volume>
          (
          <issue>5</issue>
          ),
          <volume>65</volume>
          {72 (Apr
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Bakhshi-Raiez</surname>
            ,
            <given-names>F.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>de Keizer</surname>
            ,
            <given-names>N.F.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cornet</surname>
            ,
            <given-names>R.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dorrepaal</surname>
            ,
            <given-names>M.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dongelmans</surname>
            ,
            <given-names>D.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jaspers</surname>
            ,
            <given-names>M.W.M.M.:</given-names>
          </string-name>
          <article-title>A usability evaluation of a SNOMED CT based compositional interface terminology for intensive care</article-title>
          .
          <source>International Journal of Medical Informatics</source>
          <volume>81</volume>
          (
          <issue>5</issue>
          ),
          <volume>351</volume>
          {362 (Apr
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stevens</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ng</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jacoby</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goble</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Guiding the user: an ontology driven interface</article-title>
          .
          <source>In: Proceedings User Interfaces to Data Intensive Systems</source>
          . pp.
          <volume>158</volume>
          {
          <fpage>161</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Bodenreider</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>The Uni ed Medical Language System (UMLS): integrating biomedical terminology</article-title>
          .
          <source>Nucleic Acicds Research</source>
          <volume>32</volume>
          (
          <issue>Database issue</issue>
          ),
          <source>D267{70 (Jan</source>
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Bodenreider</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Issues in mapping LOINC laboratory tests to SNOMED CT</article-title>
          . AMIA ...
          <source>Annual Symposium proceedings / AMIA Symposium. AMIA Symposium</source>
          pp.
          <volume>51</volume>
          {
          <issue>55</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Ceusters</surname>
            ,
            <given-names>W.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>B.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goldberg</surname>
            ,
            <given-names>L.L.:</given-names>
          </string-name>
          <article-title>A terminological and ontological analysis of the NCI Thesaurus</article-title>
          .
          <source>Methods of information in medicine 44(4)</source>
          ,
          <volume>498</volume>
          {507 (Jan
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Chute</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cohn</surname>
            ,
            <given-names>S.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Campbell</surname>
            ,
            <given-names>J.R.</given-names>
          </string-name>
          <article-title>, for the ANSI Healthcare Informatics Standards Board Vocabulary Working Group and the Computer-based Patient Records Institute Working Group on Codes and Structures: A Framework for Comprehensive Health Terminology Systems in the United States: Development Guidelines, Criteria for Selection, and Public Policy Implications</article-title>
          .
          <source>Journal of the American Medical Informatics Association</source>
          <volume>5</volume>
          (
          <issue>6</issue>
          ),
          <volume>503</volume>
          {510 (Nov
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Chute</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cohn</surname>
            ,
            <given-names>S.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Campbell</surname>
            ,
            <given-names>K.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oliver</surname>
          </string-name>
          , D.E.,
          <string-name>
            <surname>Campbell</surname>
            ,
            <given-names>J.R.:</given-names>
          </string-name>
          <article-title>The Content Coverage of Clinical classi cations</article-title>
          .
          <source>Journal of the American Medical Informatics Association</source>
          (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Cimino</surname>
            ,
            <given-names>J.J.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clayton</surname>
            ,
            <given-names>P.D.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hripcsak</surname>
            ,
            <given-names>G.G.</given-names>
          </string-name>
          , Johnson,
          <string-name>
            <surname>S.B.S.</surname>
          </string-name>
          :
          <article-title>Knowledge-based approaches to the maintenance of a large controlled medical terminology</article-title>
          .
          <source>Journal of the American Medical Informatics Association : JAMIA</source>
          <volume>1</volume>
          (
          <issue>1</issue>
          ),
          <volume>35</volume>
          {50 (Jan
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Cornet</surname>
          </string-name>
          , R.:
          <article-title>De nitions and quali ers in SNOMED CT</article-title>
          .
          <source>Methods of information in medicine 48(2)</source>
          ,
          <volume>178</volume>
          {183 (Jan
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Cornet</surname>
          </string-name>
          , R., de Keizer, N.:
          <article-title>Forty years of SNOMED: a literature review</article-title>
          .
          <source>BMC Medical Informatics and Decision Making</source>
          <volume>8</volume>
          (
          <issue>Suppl 1</issue>
          ),
          <source>S2</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Cornet</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , Nystrom,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Karlsson</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.:</surname>
          </string-name>
          <article-title>User-Directed Coordination in SNOMED CT</article-title>
          .
          <article-title>Studies in health technology</article-title>
          and
          <source>informatics 192</source>
          ,
          <volume>72</volume>
          {
          <fpage>76</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>De Silva</surname>
            ,
            <given-names>T.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>MacDonald</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paterson</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sikdar</surname>
            ,
            <given-names>K.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cochrane</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Systematized nomenclature of medicine clinical terms (SNOMED CT) to represent computed tomography procedures</article-title>
          .
          <source>Computer methods and programs in biomedicine 101(3), 6{6 (Mar</source>
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Elkin</surname>
            ,
            <given-names>P.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bailey</surname>
            ,
            <given-names>K.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chute</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          :
          <article-title>A randomized controlled trial of automated term composition</article-title>
          .
          <source>In: Proceedings of the AMIA Symposium</source>
          . p.
          <fpage>765</fpage>
          . American Medical Informatics Association (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Elkin</surname>
            ,
            <given-names>P.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brown</surname>
          </string-name>
          , S.H.:
          <article-title>Compositionality: An Implementation Guide</article-title>
          .
          <source>In: Terminology and Terminological Systems</source>
          , pp.
          <volume>71</volume>
          {
          <fpage>94</fpage>
          . Springer London, London (
          <year>Mar 2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Elkin</surname>
            ,
            <given-names>P.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brown</surname>
            ,
            <given-names>S.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lincoln</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hogarth</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rector</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A formal representation for messages containing compositional expressions</article-title>
          .
          <source>International Journal of Medical Informatics</source>
          <volume>71</volume>
          (
          <issue>2-3</issue>
          ),
          <volume>89</volume>
          {102 (Sep
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Evans</surname>
            ,
            <given-names>D.A.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cimino</surname>
            ,
            <given-names>J.J.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hersh</surname>
            ,
            <given-names>W.R.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>S.M.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bell</surname>
            ,
            <given-names>D.S.D.</given-names>
          </string-name>
          :
          <article-title>Toward a medical-concept representation language</article-title>
          .
          <source>The Canon Group. Journal of the American Medical Informatics Association : JAMIA</source>
          <volume>1</volume>
          (
          <issue>3</issue>
          ),
          <volume>207</volume>
          {217 (Apr
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Fung</surname>
            ,
            <given-names>K.W.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McDonald</surname>
            ,
            <given-names>C.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Srinivasan</surname>
            ,
            <given-names>S.S.:</given-names>
          </string-name>
          <article-title>The UMLS-CORE project: a study of the problem list terminologies used in large healthcare institutions</article-title>
          .
          <source>Journal of the American Medical Informatics Association : JAMIA</source>
          <volume>17</volume>
          (
          <issue>6</issue>
          ),
          <volume>675</volume>
          {680 (Nov
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Goss</surname>
            ,
            <given-names>F.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhou</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plasek</surname>
            ,
            <given-names>J.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Broverman</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robinson</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Middleton</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rocha</surname>
            ,
            <given-names>R.A.</given-names>
          </string-name>
          :
          <article-title>Evaluating standard terminologies for encoding allergy information</article-title>
          .
          <source>Journal of the American</source>
          Medical Informatics Association : JAMIA pp.
          <source>{ (Feb</source>
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30. de Keizer,
          <string-name>
            <given-names>N.F.</given-names>
            ,
            <surname>Bakhshi-Raiez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>de Jonge</surname>
          </string-name>
          , E.,
          <string-name>
            <surname>Cornet</surname>
          </string-name>
          , R.:
          <article-title>Post-coordination in practice: evaluating compositional terminological system-based registration of ICU reasons for admission</article-title>
          .
          <source>International Journal of Medical Informatics</source>
          <volume>77</volume>
          (
          <issue>12</issue>
          ),
          <volume>828</volume>
          {835 (Dec
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Kless</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Milton</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Towards quality measures for evaluating thesauri</article-title>
          .
          <source>Metadata and Semantic</source>
          Research pp.
          <volume>312</volume>
          {
          <issue>319</issue>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>MacIsaac</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Walker</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Essential</surname>
            <given-names>SNOMED</given-names>
          </string-name>
          :
          <article-title>Simplifying SNOMED CT and Supporting Integration with Health Information Models</article-title>
          .
          <source>In: Proceedings of KR-MED</source>
          <year>2008</year>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>McKnight</surname>
            ,
            <given-names>L.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elkin</surname>
            ,
            <given-names>P.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ogren</surname>
            ,
            <given-names>P.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chute</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          :
          <article-title>Barriers to the clinical implementation of compositionality</article-title>
          .
          <source>Proceedings / AMIA ... Annual Symposium. AMIA Symposium</source>
          pp.
          <volume>320</volume>
          {
          <issue>324</issue>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          34.
          <string-name>
            <surname>Rassinoux</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>R.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baud</surname>
            ,
            <given-names>R.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scherrer</surname>
            ,
            <given-names>J.R.</given-names>
          </string-name>
          :
          <article-title>Modeling Just the Important and Relevant Concepts in Medicine for Medical Language Understanding: A Survey of the Issues</article-title>
          .
          <source>In: Proceedings of the IMIA WG6 Working Conference</source>
          , Jacksonville, FL (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          35.
          <string-name>
            <surname>Rector</surname>
          </string-name>
          , Iannone: Lexically suggest, logically de ne:
          <article-title>Quality assurance of the use of quali ers and expected results of post-coordination in SNOMED CT</article-title>
          .
          <source>Journal of Biomedical Informatics</source>
          <volume>45</volume>
          (
          <issue>2</issue>
          ),
          <volume>11</volume>
          {11 (Mar
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          36.
          <string-name>
            <surname>Rector</surname>
            ,
            <given-names>A.L.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goble</surname>
            ,
            <given-names>C.A.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nowlan</surname>
            ,
            <given-names>W.A.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solomon</surname>
          </string-name>
          , W.D.W.:
          <article-title>The GRAIL concept modelling language for medical terminology</article-title>
          .
          <source>Arti cial Intelligence in Medicine</source>
          <volume>9</volume>
          (
          <issue>2</issue>
          ),
          <volume>139</volume>
          {171 (Feb
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          37.
          <string-name>
            <surname>Rogers</surname>
            ,
            <given-names>J.E.</given-names>
          </string-name>
          :
          <article-title>Development of a methodology and an ontological schema for medical terminology</article-title>
          .
          <source>Ph.D. thesis</source>
          , School of Computer Science (May
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          38.
          <string-name>
            <surname>Spackman</surname>
            ,
            <given-names>K.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Campbell</surname>
            ,
            <given-names>K.E.</given-names>
          </string-name>
          :
          <article-title>Compositional concept representation using SNOMED: towards further convergence of clinical terminologies</article-title>
          .
          <source>Proceedings / AMIA ... Annual Symposium. AMIA Symposium</source>
          pp.
          <volume>740</volume>
          {
          <issue>744</issue>
          (Jan
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          39.
          <string-name>
            <surname>Steindel</surname>
          </string-name>
          , S.J.:
          <article-title>International classi cation of diseases, 10th edition, clinical modi cation and procedure coding system: descriptive overview of the next generation HIPAA code sets</article-title>
          .
          <source>Journal of the American Medical Informatics Association : JAMIA</source>
          <volume>17</volume>
          (
          <issue>3</issue>
          ),
          <volume>274</volume>
          {282 (Apr
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          40.
          <string-name>
            <surname>Steindel</surname>
            ,
            <given-names>S.J.S.:</given-names>
          </string-name>
          <article-title>A comparison between a SNOMED CT problem list and the ICD-10-CM/PCS HIPAA code sets</article-title>
          .
          <source>Perspectives in Health Information Management / AHIMA, American Health Information Management Association</source>
          <volume>9</volume>
          ,
          <source>1b{1b (Jan</source>
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          41.
          <string-name>
            <surname>Wade</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosenbloom</surname>
          </string-name>
          , S.T.:
          <article-title>The impact of SNOMED CT revisions on a mapped interface terminology: Terminology development and implementation issues</article-title>
          .
          <source>Journal of Biomedical Informatics</source>
          <volume>42</volume>
          (
          <issue>3</issue>
          ), 4{4 (May
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          42.
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patrick</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>O</given-names>
            <surname>'Hallaran</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.:</surname>
          </string-name>
          <article-title>A computational linguistics motivated mapping of ICPC-2 PLUS to SNOMED CT. BMC Medical Informatics and Decision Making 8 Suppl 1(suppl 1), S5{S5 (Jan</article-title>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>