<!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>A Methodology for Encoding Problem Lists with SNOMED CT in General Practice</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Francis Lau</institution>
          ,
          <addr-line>Ph.D., Ray Simkus, M.D., Dennis Lee</addr-line>
          ,
          <institution>M.Sc. School of Health Information Science, University of Victoria</institution>
          ,
          <addr-line>Victoria, B.C.</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2008</year>
      </pub-date>
      <fpage>97</fpage>
      <lpage>103</lpage>
      <abstract>
        <p>This paper describes a methodology for encoding problem lists used in general practice with SNOMED CT. Our intent is to help general practitioners to incorporate SNOMED CT into their existing Electronic Medical Record (EMR) systems with minimal disruption as a first step, thus allowing them to assess its impact prior to full-scale conversion. We started with 1,713 original unique terms that made up the problem lists from the general practice EMR used in the study. We ended with 1,468 unique concepts after two cycles of matching and revisions that led to 1,347 or ~92% successful matches. The remaining terms were revised to tease out modifiers or secondary concepts that could be used to provide equivalency through post-coordination. While skeptics of reference terminology systems often balk at their unwieldy size and complexity for local adoption, this study has demonstrated that, using our methodology, it is possible to create a manageable subset of SNOMED concepts for problem lists used in general practice with immediate tangible value.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>The problem list is the keystone of the medical
record. In general practice settings, the type of
problems presented by patients can be quite diverse.
Examples range from non-specific symptoms such as
headaches with unknown cause, to a diagnosis of
coronary disease that can be expressed in different
ways such as heart attack and myocardial infarction.
The choice of terms used in problem lists becomes an
important design issue for the electronic medical
record (EMR), since the level of granularity selected
for defining the problems and the actual terms
entered into the system can affect one’s ability to
retrieve the information afterwards, thus impacting
the overall quality of the EMR system.</p>
      <p>
        There have been many studies on the design and use
of controlled terminology to encode the problem lists
in EMR systems and their impact on practice [
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref5 ref6 ref7 ref8">1-8</xref>
        ].
Most of these studies are focused on large institutions
involving a substantive number of clinical terms in
order to accommodate the needs of a wide range of
clinicians in the institution. For example in their
study of diagnosis and problem lists in a
computerized physician order entry system,
Wasserman [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] reported that 88.4% of their 8,378
clinical terms were found in SNOMED CT. With the
addition of 145 site-specific terms they were able to
achieve 98.5% overall content coverage. With the
formation of the International Health Terminology
Standards Organization (IHTSDO), the historical
barriers to SNOMED CT related to cost and the
proprietary nature of the product have now been
removed, and national initiatives related to EMR’s
are emerging to use SNOMED CT as a clinical
terminology in several countries around the world.
Despite such impressive development, the effort to
adopt SNOMED CT in Canada has been minimal to
date. There continues to be a concern especially in
the primary care setting where most general practices
are made up of small groups of practitioners, of
whom few are equipped with an EMR. Critics often
balk at the enormous size and complexity of
SNOMED CT, considering it as too unwieldy and
costly for local adoption and use. But a review of
data collected from several sites by one author
showed the number of codes needed to cover
disorders of at least 1:100,000 occurrence would be
under 5,000 [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Work is underway with IHTSDO
and the WICC group of WONCA to finalize this list
as a potential primary care SNOMED subset [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
In this paper, we describe a methodology that we
have developed based on an ongoing study to encode
problem lists using SNOMED CT (July 2007 release)
for a local general practice in Canada. The intent of
this methodology is to enable general practitioners to
incorporate SNOMED CT into their existing EMR
systems within minimal disruption as a first step, thus
allowing them to assess its potential impact prior to
full-scale conversion.
      </p>
    </sec>
    <sec id="sec-2">
      <title>METHODS</title>
    </sec>
    <sec id="sec-3">
      <title>Design and Setting</title>
      <p>For this study, we included all the problem list (PL)
terms from the commercial EMR system used by a
local general practice in British Columbia, Canada.
This setting is typical of many general practices
across the country, which are made up of small
groups of general practitioners working in a private
medical office, mostly on a fee-for-service basis. The
medical office in this study has four general
practitioners who have worked as a group for 30
years in a township with a population of 100,000
located east of Vancouver, British Columbia. The
practice has had 8 years of experience using an EMR.
At least two of the practitioners record all of the
information on their patients on a daily basis at the
time of encounter or shortly thereafter. Laboratory
and imaging results and consult reports from external
sources – both electronic and on paper – are entered
into the EMR either by the practitioners themselves
or the medical office assistant.</p>
    </sec>
    <sec id="sec-4">
      <title>Matching Algorithms</title>
      <p>
        We applied four matching algorithms used in an
earlier SNOMED CT to ICD-10 mapping project to
find matching SNOMED concepts for each of the PL
terms [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Three are lexical techniques for
exactmatch, match-all and partial-match. The fourth is
semantic matching that involves retrieving the
current concepts based on historical relationships if
the initial SNOMED concepts found were inactive.
These algorithms are summarized in Table 1.
Algorithm Explanation
1. Exact match Exact string match where all words are
same and in same sequence, including
punctuation
2. Match all String match where all words are same but
not necessary in same order; additional
words allowed
3. Partial match String match where one or more words is
found
4. Semantic match For inactive concepts use historical
relationships Was-A, Same-As, May-Be-A,
      </p>
      <p>Replaced-By to find current concepts
5. Unmatched Assigned when no match is found</p>
      <p>Table 1. Matching algorithms used in this study</p>
    </sec>
    <sec id="sec-5">
      <title>Normalization Steps</title>
      <p>
        In addition to applying the matching algorithms to
the original PL terms, we reran the algorithms after
we normalized the PL and SNOMED terms to
remove “noise” using the Unified Medical Language
System (UMLS 2007 version) normalization steps,
shown in Table 2a [
        <xref ref-type="bibr" rid="ref13 ref14">13,14</xref>
        ]. To improve matching, we
expanded step-2 to remove both “stop words” and
“exclude words” and SNOMED prefixes, shown in
Table 2b. For step-5 we included the lookup and
stemming methods to uninflect the phrase. The
lookup method uses the UMLS SPECIALIST
Lexicon’s inflection table with ~1 million entries,
whereas the stemming method is a computational
technique that reduces word variants to a single
canonical form [
        <xref ref-type="bibr" rid="ref15 ref16">15,16</xref>
        ].
      </p>
      <p>No
1
2
3
4
5
6</p>
      <p>Step Example
Remove Hodgkin’s disease, NOS o Hodgkin
genitive diseases, NOS
Remove stop Hodgkin diseases, NOS o Hodgkin
words diseases,
Convert to Hodgkin diseases, o hodgkin diseases,
lowercase
Strip hodgkin diseases, o hodgkin diseases
punctuation
Uninflect hodgkin diseases o hodgkin disease
phrase
Sort hodgkin disease o disease hodgkin
words</p>
      <p>Table 2a. UMLS normalization steps [8, slide20]</p>
    </sec>
    <sec id="sec-6">
      <title>Matching PL Terms</title>
      <p>The process of matching the PL terms involved
cycling through the matching algorithms one at a
time to find the best candidate SNOMED CT
concepts. For each algorithm we always began with
the original terms, then the UMLS normalized terms,
followed by the stemmed terms. During each cycle,
we would review the candidate concepts found to
determine if it was a match, and if so, what type of
match it was based on the algorithm applied. When
no matching concepts were found, we would label
the term as unmatched. Our experience with the
matching algorithms had been that, the sooner we
could find a match in the cycle, the greater
confidence we would have that the candidate concept
is appropriate. The preferred order of matching
selected is always exact first, then all, followed by
partial. For exact-match and match-all if only
inactive concepts are found then a semantic-match is
done to find their corresponding current concepts
through the historical relationships.</p>
      <p>SNOMED
Prefixes
Step-5
Stop
words
Exclude
words</p>
      <p>Explanation
Frequent short words that do not affect the phrase:
and, by, for, in, of, on, the, to, with, no, (nos)
Words that may change meaning of the word but if
ignored help to find a term otherwise missed: about,
alongside, an, anything, around, as, at, because,
before, being, both, cannot, chronically, consists,
covered, does, during, every, find, from, instead,
into, more, must, no, not, only, or, properly, side,
sided, some, something, specific, than, that, things,
this, throughout, up, using, usually, when, while
[X] – concepts with ICD-10 codes not in ICD-9
[D] - concepts in ICD-9 XVI and ICD-10 SVII
[M] – morphology of neoplasm concepts in ICD-O
[SO] – concepts in OPCS-4 chapter Z in CTV3
[Q] – temporary qualifying terms from CTV3
[V] – concepts in ICD-9 and ICD-10 on factors
influencing health status and contact with health
services (V-codes and Z-codes)</p>
      <p>Table 2b. Expanded UMLS normalization step-2</p>
    </sec>
    <sec id="sec-7">
      <title>Encoding the Problem Lists</title>
      <p>The process of encoding the problem lists extracted
from the EMR followed these steps: (a) tabulating the
frequency of occurrences for all of the original PL
terms; (b) cataloguing all of the unique words across
the PL terms present; (c) examining all unique words
and PL terms to identify and revise for acronyms,
abbreviations, spelling variants and errors; (d)
matching the PL terms to SNOMED CT concepts
using matching algorithms described earlier; (e)
producing detailed and summary outputs to show the
type of matches found; (f) reviewing/verifying the
matched concepts one term at a time for accuracy; (g)
repeating steps (c-f) until no further matches could be
found; (h) examine remaining partial-matches for
post-coordination; (i) create an index table of all PL
and matched SNOMED terms. As part of this study,
we also explored navigating within the SNOMED
hierarchy to examine how the super-types and
relations could be used to improve the quality of
recall using the matched SNOMED concepts.</p>
    </sec>
    <sec id="sec-8">
      <title>RESULTS</title>
    </sec>
    <sec id="sec-9">
      <title>Summary of PL Terms and Matches</title>
      <p>A total of 7,833 PL entries were extracted from the
EMR for this study. The majority of these entries
were recorded by one practitioner over a 7-year
period. Of these entries, there were 1,713 unique PL
terms present. Based on the frequency distribution of
the entries, the top 10 PL terms were hypertension,
hypercholesterolemia, diabetes mellitus, hypothyroid,
asthma, atrial fibrillation, gastroesophageal reflux,
depression, congestive heart failure and chronic
kidney disease. After the second cycle we had 1,296
(88.23%) exact-matches where the PL terms are
exactly the same as the SNOMED terms found.
There were 51 (3.47%) match-all where all the words
in the PL terms are present in the SNOMED terms
but not necessarily in the same sequence. There were
120 (8.17%) partial-matches where one or more
words matched the SNOMED terms. Another 20
(1.42%) SNOMED terms were found with semantic
matches. Between the two cycles partially-matched
terms were revised to tease out qualifiers and
secondary concepts if present in order to explore
post-coordination. A summary of the PL terms and
the SNOMED matches found is shown in Table 3.</p>
    </sec>
    <sec id="sec-10">
      <title>Characteristics of Encoded PL Terms</title>
      <p>In Table 4 we have examples of the frequently used
PL terms with their SNOMED terms found by exact,
all and semantic matches. Also shown are the
matches after revision and post-coordination of the
original and partially-matched PL terms. For most
exact-matches we selected the preferred terms from
SNOMED CT as they are identical or closest to the
original PL terms, such as Atrial fibrillation. In some
cases we chose the synonym terms, such as
Hypertension instead of the preferred term which is
Hypertensive disorder. For match-all and some
partial-matches we selected the SNOMED terms that
were closest to the PL concept involved, such as
GERD gastro-esophageal reflux disease. For
semantic matches we looked up the current concepts
of the matched but inactive SNOMED terms through
their historical relationships, such as Cirrhosis. For
post-coordination we added qualifier and refinement
terms to SNOMED concepts or combined those that
are lexically closest to the original PL terms, such as
Atrial fibrillation+Chronic, Kidney disease+Chronic,
and Headache+Migraine. After the second cycle any
remaining partial-matches were treated as
unmatched. Initially there were eight PL terms not
found in SNOMED CT. Five were spelling errors
and were revised for the second cycle (e.g.
hepatomegally o hepatomegaly); three were
legitimate missing terms – vasculopath, pyocystitis
and hypotestosteronemia, where we had to modify
the PL term or tag as local extensions. Using these
outputs we created an index table to link the PL
terms to their matched SNOMED terms, shown in
Table 5. Each row contains the PL-termId, conceptId,
descriptionId, relationship-typeId match-type, and
post-coordination-sequenceId.</p>
      <p>Description Frequency
No. of patients 2,894
Total PL entries 7,833
Total words in PL terms 16,455
Unique words 1,764
Longest word Hypercholesterolemia, 20 characters
Median length 8 characters
Most common word Hypertension, 585 times
Matching Initial Cycle 2nd Cycle
Algorithm Frequency (%) Frequency (%)
Exact-Match 905 (52.83%) 1,296 (88.23%)
Match-All 167 (9.75%) 52 (3.47%)
Partial-Match 633 (36.95%) 120 (8.17%)
Semantic-Match 49 (2.86%) 20 (1.42%)
Unmatched 8 (0.47%) 2 (0.14%)
Post-coordination Not done In-progress
Total unique PL terms 1,713 1,468
Table 3. Summary of PL terms and matches. For
frequency %, once a match has been found it is not
included as part of the next matching algorithm</p>
    </sec>
    <sec id="sec-11">
      <title>Revision of PL Terms</title>
      <p>
        Manual revisions were done on the 1,713 unique PL
terms after the initial cycle. By selecting the PL terms
that were not matched in SNOMED CT, we were
able to identify entries that were misspelled,
idiosyncratic local terms or ambiguous concepts. A
number of spelling mistakes were corrected. The
CliniClue Browser [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] was used to find matches for
each term. A few terms were found in our problem
lists but not in SNOMED CT. Some were local terms
that needed to be reconsidered but there were also
terms that would be submitted for inclusion in
SNOMED CT. One example is “chronic kidney
disease” which seems to be the preferred term in
common usage. Yet the closest SNOMED term is
“chronic renal failure.” In this revision we also noted
parts of some PL terms could be removed as
qualifiers or modifiers, thus increasing the number of
exact matches found. Examples include left, right,
lower, midline, chronic, recurring, active, query and
multiple. These modifiers seemed to be clustered
around the concepts of time course, number, location
and severity. We found 313 such instances in our PL
terms. In another 89 instances we found
postcoordination of two SNOMED concepts produced a
good match.
      </p>
    </sec>
    <sec id="sec-12">
      <title>Navigating the SNOMED Hierarchy</title>
      <p>As part of this study, we explored ways to navigate
the SNOMED hierarchy to determine if it could
improve one’s ability to retrieve related concepts. Of
the 1,296 exact matches found for the 1,468 unique
PL terms present, we selected a subset of 32 PL
terms related to cardiovascular disorders for this
analysis. First, we did frequency counts of these PL
terms to show how often they were present in the
EMR system. For each PL term present, we
navigated up the hierarchy until we reached the
super-type “49601007|Disorder of cardiovascular
system.” We then pruned the tree to include only
those concepts with a positive frequency count, but
left their immediate super-types intact. This
partlyinstantiated cardiovascular disorder hierarchy is
shown in Figure 1. The value of this tree is that it
shows the SNOMED concepts that are actually
present in the EMR and how often they occur via the
frequency counts based on the PL terms recorded.
This tree can aide in the retrieval of relevant concepts
recorded using different PL terms. For instance, by
specifying the concept “56265001|Heart disease” in
the query, one should expect to retrieve all sub-types
under “5754005|Acute myocardial infarction” and
“12026006|Paroxysmal tachycardia.” On the other
hand, by specifying the concept “57054005|Acute
myocardial infarction” in the query, the sibling
concept “12026006|Paroxysmal tachycardia” should
automatically be excluded.</p>
    </sec>
    <sec id="sec-13">
      <title>DISCUSSION</title>
    </sec>
    <sec id="sec-14">
      <title>A proposed Methodology</title>
      <p>Drawing on the lessons learned from this study, we
propose the following steps for general practitioners
to encode problem lists from their EMR in SNOMED
as a first step for review before full-scale conversion:
1. Extract all PL entries from the EMR and tabulate
the frequency of the PL terms present;
2. Catalogue all unique words across the PL terms;
3. Examine all unique words and PL terms to
identify and revise for acronyms, abbreviations,
spelling variants and errors;
4. Match the PL terms to SNOMED concepts using
the matching algorithms outlined in this paper
(contact authors for copies of the algorithms);
5. Create detailed and summary outputs to show the
exact, all, partial and semantic matches found;
6. Review matched SNOMED terms for accuracy;
remove successful exact-match and match-all
terms from further matching cycles;
7. Repeat steps 3 through 6 for remaining partial
matches until no further matches found;
8. Post-coordinate remaining PL terms with
qualifier, refinement and combined concepts;
9. Create a pruned PL hierarchy tree showing all
concepts with positive frequency counts and
immediate super-type concepts;
10. Create index table containing unique identifiers
for the PL and matched SNOMED terms.</p>
    </sec>
    <sec id="sec-15">
      <title>Implications</title>
      <p>Post-coordination is thought to be a feature that is
difficult to implement. Yet based on the small
number of SNOMED concepts used in this study to
post-coordinate our PL terms, it seems feasible to
achieve. We did note the use of pre-coordination in
SNOMED CT is unpredictable, and it seems common
to include acronyms within SNOMED descriptions.
Careful use of modifiers such as laterality, chronicity
and severity should be considered. Further studies are
needed.</p>
      <p>Critics often balk at the unwieldy size and
complexity of SNOMED CT as too impractical for
local use. In Canada the vendor and general practice
communities, which are often small in size, are
reluctant to adopt SNOMED CT, questioning their
return on value for the effort required. From this
study, we have shown it is feasible to incorporate
SNOMED CT into EMR in the general practice
setting. The methodology we have outlined is
practical even for small medical offices with an EMR
in place. We have also shown the potential use of
SNOMED CT to improve the quality of recall from
its hierarchy. The ability to demonstrate return on
value, as in our encoding of problem lists with
SNOMED CT to improve recall, is an important first
step for practitioners to consider before full-scale
conversion of their EMR.</p>
    </sec>
    <sec id="sec-16">
      <title>Limitations</title>
      <p>There are several limitations to this study. First, the
PL terms used have been established over the years
mainly by one practitioner from a single setting,
which are likely to vary between practices. Second,
our current matching algorithms do not take into
account subtype hierarchy to limit searches, which
could otherwise restrict unlikely choices such as
Physical Object and Substance. Third, the evaluation
of this methodology is incomplete to date; the full
extent of the post-coordination effort required to
encode the entire set of PL terms in this EMR should
be further examined and reported. Fourth, the use of
our partly instantiated hierarchy tree to improve
recall quality, while promising, requires more
thorough investigation into its utility with more
complex real-life cases. Its design should also be
aligned with the existing SNOMED navigation
hierarchy feature that is already in place as part of the
new RefSet release.</p>
    </sec>
    <sec id="sec-17">
      <title>Next Steps</title>
      <p>We are developing a Web-based mapping tool made
up of the matching algorithms described earlier to
allow the matching of clinical terms to SNOMED CT
in an interactive or batch mode. With our focus
continued to be on general practice EMR systems,
there are several steps ahead to be considered. For
instance, we need to expand the use of SNOMED
terms to other parts of the EMR such as procedures,
medications and billing. We also need to refine our
encoding methodology to take into account specific
contexts such as past/family history and health risks,
and to use subtype hierarchy to improve search
precision. The inclusion of frequency statistics on the
distribution of matched SNOMED CT terms across
the hierarchies would be useful to validate the results.
These efforts should aid in the eventual creation of a
primary care SNOMED subset, and eventually a
concept model in the primary care domain. But most
important, we should continue to exploit ways by
which the use of SNOMED CT in the EMR can
actually enhance patient care.</p>
    </sec>
    <sec id="sec-18">
      <title>ACKNOWLEDGMENTS</title>
      <p>Funding support for this project has been provided
by the Canadian Institutes for Health Research
Strategic Training Initiative.
Two sets of post-coordinated terms shown above</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Chute</surname>
            <given-names>CG</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elkin</surname>
            <given-names>PL</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fenton</surname>
            <given-names>SH</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Atkin</surname>
            <given-names>GE</given-names>
          </string-name>
          .
          <article-title>A clinical terminology in the post modern era: pragmatic problem list development</article-title>
          .
          <source>Proceedings AMIA Ann Symposium</source>
          <year>1998</year>
          ;
          <fpage>795</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Warren</surname>
            <given-names>JJ</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Collins</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sorrentino</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Campbell</surname>
            <given-names>JR</given-names>
          </string-name>
          .
          <article-title>Just-in-time coding of the problem list in a clinical environment</article-title>
          .
          <source>Proceedings AMIA Annual Symposium</source>
          <year>1998</year>
          ;
          <fpage>280</fpage>
          -
          <lpage>4</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Petersson</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gunnar</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strender</surname>
            <given-names>LE</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahlfeldt</surname>
            <given-names>H.</given-names>
          </string-name>
          <article-title>The connection between terms used in medical records and coding system: a study on Swedish primary health care data</article-title>
          .
          <source>Medical Informatics</source>
          <year>2001</year>
          ;
          <volume>26</volume>
          (
          <issue>2</issue>
          ):
          <fpage>87</fpage>
          -
          <lpage>99</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Wang</surname>
            <given-names>SJ</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bates</surname>
            <given-names>DW</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chueh</surname>
            <given-names>HC</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karson</surname>
            <given-names>AS</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maviglia</surname>
            <given-names>SM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Greim</surname>
            <given-names>JA</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frost</surname>
            <given-names>JP</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuperman</surname>
            <given-names>GJ</given-names>
          </string-name>
          .
          <article-title>Automated coded ambulatory problem lists: evaluation of a vocabulary and a data entry tool</article-title>
          .
          <source>International Journal of Medical Informatics</source>
          <year>2003</year>
          ;
          <volume>72</volume>
          ,
          <fpage>17</fpage>
          -
          <lpage>28</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Fabry</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baud</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruch</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Despont-Gros</surname>
            <given-names>C</given-names>
          </string-name>
          , Lovis C.
          <article-title>Methodology to ease the construction of a terminology of problems</article-title>
          .
          <source>International Journal of Medical Informatics</source>
          <year>2006</year>
          ;
          <volume>75</volume>
          :
          <fpage>624</fpage>
          -
          <lpage>32</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Meystre</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haug</surname>
            <given-names>PJ</given-names>
          </string-name>
          .
          <article-title>Automation of a problem list using natural language processing</article-title>
          .
          <source>BMC Medical Informatics and Decision Making</source>
          <year>2005</year>
          ;
          <volume>5</volume>
          (
          <issue>30</issue>
          ):
          <fpage>1472</fpage>
          -
          <lpage>6947</lpage>
          /5/30.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Elkin</surname>
            <given-names>PL</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brown</surname>
            <given-names>SH</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Husser</surname>
            <given-names>CS</given-names>
          </string-name>
          , et al.
          <article-title>Evaluation of the content coverage of SNOMED CT: ability of SNOMED clinical terms to represent clinical problem lists</article-title>
          .
          <source>Mayo Clinic Proceedings</source>
          <year>2006</year>
          ;
          <volume>81</volume>
          (
          <issue>6</issue>
          ):
          <fpage>741</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>O</given-names>
            <surname>'Halloran</surname>
          </string-name>
          <string-name>
            <given-names>J</given-names>
            ,
            <surname>Miller</surname>
          </string-name>
          <string-name>
            <given-names>GC</given-names>
            ,
            <surname>Britt</surname>
          </string-name>
          <string-name>
            <surname>H</surname>
          </string-name>
          .
          <article-title>Defining chronic conditions for primary care with ICPC2</article-title>
          .
          <source>Family Practice</source>
          <year>2004</year>
          ;
          <volume>21</volume>
          (
          <issue>4</issue>
          ):
          <fpage>381</fpage>
          -
          <lpage>6</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Wasserman</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            <given-names>J</given-names>
          </string-name>
          .
          <article-title>An applied evaluation of SNOMED CT as a clinical vocabulary for the computerized diagnosis and problem list</article-title>
          .
          <source>Proceedings AMIA Symposium</source>
          <year>2003</year>
          ,
          <fpage>699</fpage>
          -
          <lpage>703</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Comment</surname>
          </string-name>
          <article-title>: one author reviewed datasets provided by colleagues from hospitals in Buenos Aires in Argentina, Kaiser Permanente in United States, and Sherbrooke in Canada during Fall</article-title>
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <article-title>Comment: WONCA is the World Organization of Family Doctors, and WICC is the WONCA International Classification Committee</article-title>
          . URL http://www.globalfamilydoctor.com/; Jan20/08.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Lee DHK. Reverse Mapping</surname>
            <given-names>ICD</given-names>
          </string-name>
          -10-CA to SNOMED CT.
          <source>UVic Master of Science research project report, Oct</source>
          <year>2007</year>
          . Unpublished.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <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>
            <surname>O'Halleran.</surname>
          </string-name>
          <article-title>Linguistic mapping of terminologies to SNOMED CT</article-title>
          .
          <source>Semantic Mining Conference on SNOMED CT Oct</source>
          <year>2006</year>
          , Copenhagen, Denmark.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Kleinsorge</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willis</surname>
            <given-names>J</given-names>
          </string-name>
          , et al.
          <source>UMLS Overview - Tutorial T12. AMIA Annual Symposium</source>
          <year>2006</year>
          . http://165.112.6.70/research/umls/pdf/AMIA_T1 2
          <article-title>_2006_UMLS.pdf</article-title>
          .
          <source>Jan15/08.</source>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. National Library of Medicine.
          <source>The SPECIALIST Lexicon</source>
          . http://lexsr3.nlm.nih.gov/LexSysGroup/Projects/ Summary/lexicon.html. Jan15/
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Goldsmith</surname>
            <given-names>JA</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Higgins</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soglasnova</surname>
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Automatic</surname>
          </string-name>
          Language-specific
          <source>Stemming in Information Retrieval</source>
          . Springer-Verlag Berlin Heidelberg
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>CliniClue. The Clinical Information Consultancy</surname>
          </string-name>
          , Ltd., UK. http://www.cliniclue.com/software. available for download.
          <source>Jan22/08.</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>