<!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>Development of a Medication Reconciliation Tool for Norwegian Primary Care EPR Systems: Experiences from a User-initiated Pro ject</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Thomas Brox R st</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Inger Dybdahl S rby</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gry Seland</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Atbrox AS</institution>
          ,
          <addr-line>Trondheim</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Gj vik University College</institution>
          ,
          <addr-line>Gj vik</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Vivit AS</institution>
          ,
          <addr-line>Trondheim</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <fpage>53</fpage>
      <lpage>62</lpage>
      <abstract>
        <p>Medication reconciliation is one of the most important priorities of national and international patient safety e orts, due to the numerous deaths and adverse drug reactions caused by inappropriate medication use. One of the main challenges of general practitioners (GPs) is to get an overview of changes in the patients' medications after transitions between healthcare institutions. This paper presents how Natural Language Processing of free text notes such as discharge summaries is used to automatically extract information about medications and how this can be compared to the patient's existing medication list in an electronic patient record (EPR) system. The functionality has been developed in a user initiated project, as a cooperation between four di erent vendors and with a strong involvement of the end users. The functionality is available for most Norwegian GPs and is seen as a very useful tool in the medication reconciliation process.</p>
      </abstract>
      <kwd-group>
        <kwd>Medication reconciliation</kwd>
        <kwd>natural language processing</kwd>
        <kwd>user centered development</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.1</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <sec id="sec-2-1">
        <title>Medication Reconciliation</title>
        <p>
          Medication reconciliation is the proposed formal, systematic strategy to
overcome medication information communication challenges and reduce unintended
medication discrepancies that occur at transitions in care [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. When conducted
as intended, medication reconciliation is a conscientious, patient-centred,
interprofessional process that supports optimal medication management [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ].
        </p>
        <p>Copyright c 2014 by the paper's authors. Copying permitted for private and academic
purposes.</p>
        <p>The lack of medication reconciliation is seen as a signi cant challenge to
patient safety. Several studies have shown that di erent healthcare
professionals, the patient and the relatives do not have the full overview of the patients'
prescribed medications, particularly after transitions between di erent
healthcare insitutions. Not having the full overview of medication use is one of several
causes of adverse drug reactions [3{5].</p>
        <p>Several ongoing initiatives focus on processes where di erent health care
providers such as physicians, nurses, and pharmacists cooperate with patients
and their relatives to ensure accurate and consistent medication lists across
transitions in care. In Norway, three of eleven focus areas in the Norwegian Patient
Safety Programme: In Safe Hands 1 are related to medications: Medical
reconciliation, drug review in nursing homes and drug review in home care services. Other
programmes have been introduces in other countries. For example, the Institute
for Safe Medication Practices in Canada2 support medication reconciliation at
a provincial, national and international level, and the Agency for Healthcare
Research and Quality3 in the US has developed a toolkit for organizations to
develop medication reconciliation based on knowledge of best practice.</p>
        <p>However, the medication reconciliation process is tedious and time-consuming,
and there has been a lack of electronic systems that facilitate the process of
comparing and adjusting medication lists from di erent sources such as discharge
summaries from hospitals or nursing homes and the "medications in use" list
in the general practitioners (GPs) electronic patient record (EPR) system. In
Norway, this has been done by the GPs, who had to print lists of medications
on paper from their own EPR system as well as lists received in e.g. discharge
letters, and then comparing each medication manually. The result then had to
be entered into the EPR system. If the patient uses many medications the
comparison process becomes complex and sometimes neglected.</p>
        <p>This paper presents how natural language processing of free text notes such as
discharge summaries has been used to automatically extract information about
medications and how this can be compared to the patient's existing medication
list in an EPR system. The functionality has been developed in a user
initiated project, as a cooperation between four di erent vendors and with a strong
involvement of representative end users.
1.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Natural Language Processing</title>
        <p>
          Several studies have shown how information technology and natural language
processing (NLP) is used to facilitate the medication reconciliation process [
          <xref ref-type="bibr" rid="ref6 ref7">6,
7</xref>
          ]. Some of the main challenges are that the medication information is coming
from multiple sources, using di erent controlled terminologies that has to be
consolidated.
1 Norwegian Patient Safety Programme, http://www.pasientsikkerhetsprogrammet.no
2 Institute for Safe Medication Practices Canada,
http://www.ismpcanada.org/medrec/
3 Agency for Healthcare Research and Quality, http://www.ahrq.gov/qual/match/
        </p>
        <p>
          Basic lexical approaches, such as keyword matching, may sometimes be
appropriate for detecting simple concepts from medical free-text [
          <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
          ]. Problems
such as understanding the medical context [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], recognizing negative terms and
ending up with too many false positives [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] may, however, be common. To
achieve higher accuracy, natural language processing techniques are often
employed, at the cost of higher development complexity [
          <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
          ]. The well-de ned
sub-language of the medical domain is often considered suitable for linguistic
processing, given that the vocabulary is more restricted than in general
language and sentences can be terse and to the point [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. On the other hand, this
creates its own set of problems when using e.g. parsers trained on typical
corpora, such as newspaper texts, in particular related to ungrammatical language,
spelling mistakes and non-standard abbreviations.
        </p>
        <p>
          Traditional deep-linguistic grammars can be di cult to implement and are
prone to producing too many and ambiguous results. A simpler approach is to
use partial or shallow parsing [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. With full parsing, the goal is to produce a
complete parse tree of a sentence. A shallow parser will only concern itself with
nding the parts of a sentence that are deemed relevant. While building a full
parser for natural language will be a di cult task for even restricted medical
domains, constructing a shallow parser is a far simpler option. Moreover, in
many cases the problem is to identify the parts of a sentence that are of interest.
With this in mind, shallow parsing can be a viable approach towards identifying
medication administration events.
1.3
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>Project Overview</title>
        <p>The project was initiated in 2011 by the Norwegian College of General Practice
(Norsk forening for allmennmedisin - NFA) Reference Group for EPR. The
members of the reference group are general practitioner specialists who have a special
interest in ICT and EPR systems, and a particular interest in how to obtain
improved systems that can function as useful tools for the GPs in their daily work
with patients. Developing a tool for medication reconciliation was the top
priority of the reference group, and a requirements speci cation for the solution was
developed in cooperation with the Norwegian Centre for Informatics in Health
and Social Care. The suggested solution was to develop a module for extracting
and comparing medication information from di erent sources. During the
period from September 2011 to September 2012, a project plan was developed and
agreed between NFA, Vivit4, and the three major Norwegian general practice
EPR system vendors. Vivit's role in the project was to develop functionality for
recognizing and extracting medication information that could be integrated with
4 Vivit is a small Norwegian company with high competence and experience in the
eld of health informatics. Vivit focus on user-centered design and development,
including empirical methods for user-centered requirements elicitation and analysis,
usability testing and evaluation of clinical information systems, and methods for
search, de-identi cation, and secondary use of electronic patient information. The
company was founded in 2009 by former health informatics researchers from The
Norwegian University of Science and Technology (NTNU).
all the major Norwegian general practice EPR systems. The partners signed the
project agreement in September 2012, and the rst version of the system was
implemented and tested by pilot users in February 2013. In May, 2013, version
1.0 was launched, and from January, 2014, the solution has been available for
the majority of Norwegian GPs.
2</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Objectives and Main Issues</title>
      <p>The main objective of the project was to develop a method for extracting
medication information from unstructured text.</p>
      <p>Several issues had to be resolved to ensure a successful project outcome: The
discharge notes that were to be matched against the medication information in
the primary care EPR system were provided as free-text with no semantic or
structural markup. Input from several di erent hospital and elderly care EPRs
were to be expected, with no standardized ways of structuring the information.
Accordingly, a method for extracting medication information from natural
language had to be devised.</p>
      <p>A prerequisite for the project was that the new medication reconciliation
functionality had to work with three di erent EPR systems developed by
separate, competitive, vendors. Each system had its own approach towards storing
medication information, hence a joint interchange format had to be developed.
3</p>
    </sec>
    <sec id="sec-4">
      <title>Methods</title>
      <p>
        A set of 100 extracts from discharge notes were collected from various general
practice patient records. The source material was discharge notes that were sent
via electronic messaging from the hospital where the patient in question had
undergone treatment. Since we were only interested in medication information,
only the parts of the discharge note that contained such information were used.
This also helped ensure that there was no identifying information in the
extracted text. To evaluate the system, a gold standard was needed. An annotator
was given the task of marking up all relevant medication information
(medication name, dosage and frequency) in the 100 training notes. The annotation was
done independently from the software development. The annotation was
performed by a health informatics researcher. Based on the information available to
us, we created a set of EBNF-like [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] grammars that represented various ways
of describing medication information. The key part of the grammar were the
terminals representing medication names. We made use of the FEST database,
which is a national database containing information about all medications
available on the Norwegian market. In additional to the medication names, FEST
also includes associated ATC (Anatomical Therapeutic Chemical Classi cation
System) codes, information about dosages, frequencies, and various ways of
administering each drug. Much of this information could be imported directly as
grammar terminals, thus simplifying the grammar building process. The
grammars were compiled into a general text matching module, implemented in the
C# language. This module would take two inputs: The unstructured text (e.g.
discharge notes) and a structured list of medications from the primary care
patient record. The key steps of the processing pipeline were as follows: 1) The
text would be split into sentences and tokenized; 2) text matching was applied,
returning a list of extracted medications including their location, dosage and
frequency; 3) the extracted medications were compared with the known
medications, producing a list of matched extracted and known medications. The
reconciliation between known and extracted medications was done by doing a
combined semantic and syntactic comparison between the two medication sets. For
instance, medications would be matched by both name and ATC code, meaning
that two medications with di erent names but the same ATC code were eligible
match candidates. Having found a set of possible match pairs, the additional
information about dosage and frequency, including possible synonyms, would
be included in the comparison. By calculating the Levenshtein string similarity
metric [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] between normalized versions of all possible match candidates, the
matches that resembled each other the most would be returned as match pairs.
The remaining medications where no match was found would be returned as a
single medication item with no corresponding match. Due to the use of string
similarity measures, the match would be slightly fuzzy by nature, meaning that
inexact matches were allowed. In practice, this turned out to be a minor issue,
since the user interface could highlight di erences between the matches. Also,
the output from the extraction module was only intended as a decision support
aid. Each suggested medication match would have to be approved manually with
a conscious decision of whether or not the match was likely to be correct.
4
      </p>
    </sec>
    <sec id="sec-5">
      <title>Results and Findings</title>
      <p>Upon project delivery, the results were evaluated on a sample of 25 notes from
the original 100 note test set. Table 1 summarizes the results. To understand
the results, note that dosage and/or frequency will never be extracted if an
associated medication is not found. If a medication has no dosage, it will still
count as a true positive for MD and MDF if no dosage is extracted. Also note
that no false positives were found for this evaluation. From user feedback we
later learned of (and xed) false positives, but in practice these are fairly rare.</p>
      <p>Match type</p>
      <p>Medication (M)
Medication and dosage</p>
      <p>(MD)
Medication, dosage and
frequency (MDF)</p>
      <sec id="sec-5-1">
        <title>Implementation in EPR Systems</title>
        <p>The module has been implemented by the three EPR vendors that participated
in the project. Figure 1 shows a part of a screenshot from the Infodoc Plenario
EPR system 5.</p>
        <p>The lower left part of the gure shows the incoming text that has been
pasted from a discharge summary. The lower right part of the gure shows
the information that has been recognized by the Vivit module in bold text.
The upper left part of the gure shows the initial medications in use list, and
the upper right part of the gure shows the recognized medications from the
discharge summary. The table is sorted in order to match similar medications
on corresponding lines.</p>
        <p>The physician has to assess every entry in the list in order to accept or reject
the suggested changes of the list. New medications can easily be prescribed as
the new values are automatically transferred to the prescription user interface.
4.2</p>
      </sec>
      <sec id="sec-5-2">
        <title>The system in Use</title>
        <p>All the vendors involved in the project have implemented the solution in their
EPR systems, hence the solution is available for practically all Norwegian GPs.
However, the vendors have di erent processes for making the new functionality
known to their customers and not all GPs are aware of the functionality. In
addition, the vendors have implemented the module in di erent ways, and the
user interface solution may a ect how the users perceive the usability of the
medication reconciliation solution. A systematic evaluation of the solution is
currently being carried out, but the results are not yet ready. However, the
responses from many GPs are positive, although there is obviously room for
improvement. Some GPs are enthusiastic and state that
5 http://www.infodoc.no/
The new tool for synchronizing medication lists is really simplifying the
task of comparing and adjusting medication lists between our patient
records and the hospitals. (Specialist General Practitioner, using the
module with InfoDoc EPR system)
and</p>
        <p>The new tool is very useful and makes my daily work easier! (GP, using
the module with WinMed 3.0 EPR system)</p>
        <p>Other users nd the functionality useful, but miss more information about
dosage and frequency, which is important when comparing medications. Further,
the module is able to recognize and correct some spelling mistakes, but not all.
If this could be improved the usability would have been better. At the moment,
medication from unstructured text is better recognized than text in a
semistructured format, which is often used in the Care Sector in the Municipalities.
Finally, some GPs would like the functionality to be more automatic, as it still
may take considerable time to review the patients medications even with the
module. After the di erent lists are compared, the physician must determine
which medications the patient should use or not, and this has to be done for
example by clicking on each individual medication.
5</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Discussion</title>
      <p>The new module does not make the medication reconciliation process automatic,
but it o ers a tool that can be seen as a decision support system that enables
physicians to easily import medication information from various sources into the
EPR system. The EPR systems were developed in the same programming
language (C#), but they used di erent versions of C# and .NET. The developed
functionality had to work with all systems, so a lowest common denominator
approach had to be used when writing the software. This also put some constraints
on the use of third-part libraries.</p>
      <p>There is no standardised way of denoting medication information. As an
example, when denoting medication frequency, the terms x 1 and [1+0+0+0]
both mean the same thing (once a day). To some extent the project had to cope
with such syntactic di erences.</p>
      <p>As with almost all clinical text, spelling errors are common in discharge notes.
It was a strong requirement that minor spelling mistakes should be handled.
We had access to 100 discharge notes as training/example data. This is a fairly
small amount of data, which made the use of machine learning methods di cult.
Moreover, no gold standard was available, meaning that this had to be developed
as part of the project. The annotation was performed by a health informatics
researcher with background in computer science. Using more annotators with
di erent backgrounds (e.g. pharmacists, healthcare professionals) could probably
have increased the validity of the annotation.</p>
      <p>The recall rate for medications is mostly explained by the use of medication
names that were not found in the FEST database (typically colloquial terms)
and major spelling errors that the module was not able to correct. The lower
recall for frequency descriptions can be ascribed to a larger variety of expressions
when describing frequencies than what is the case for dosages. The evaluation
of the module shows that most medications are recognized, while the recall for
dosage and frequency is lower. However, as it is easy to change dosage and
frequency values, the users nd the functionality very helpful as long as most of the
medications are recognized. As more end-users start using the new functionality,
feedback and error reports are basis for continuously improvement of the
grammar. With partial parsing, the grammar strictly de nes the elements that we are
able to extract. This means that every false positive requires adding additional
rules to the grammar. To make this work, the parser developer must take care so
that grammar additions do not break previous functionality. In our experience
this calls for a structured, iterative approach to grammar development. Having
a full set of unit test cases makes grammar development a lot easier and safer. A
positive side-e ect is that with this approach the precision is usually very high,
at the expense of lower recall. Another problem with shallow parsing approach
is that it is not ideal for extracting complex narrative. For simple medication,
dosage and frequency extraction we have seen that this is not a big problem due
to the usually structured notation. However, building a grammar that e.g.
extracts the reasoning behind a prescribed medication will be a lot more di cult,
this because reasons usually are given in natural language. A shortcoming with
the evaluation was that it was performed on the same material as was used for
building the grammars, this due to the relatively small amount of data available
to us.
5.1</p>
      <sec id="sec-6-1">
        <title>User Involvement</title>
        <p>Experiences from several ICT projects in the health care sector show that a lot
of projects do not involve end users in the development. The results are often
systems that can be found annoying and time-consuming, failing to meet the
needs of the end users. The project presented in this paper was initiated by
highly active and engaged users with a real need for improved functionality of
their EPR systems. The involvement of the users and their participation in the
pilot testing and the approvement of the solution was a clear advantage in order
to ensure the success of the project.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Conclusions and Further Work</title>
      <p>The project presented in this paper has shown how joint e orts and
cooperation of end users and vendors have led to the development of new, common
functionality that supports the medication reconciliation process.
6.1</p>
      <sec id="sec-7-1">
        <title>Further Work</title>
        <p>As part of the project follow-up, the medication reconciliation module will be
continuously improved and updated bi-monthly with the latest version of FEST
as well as general quality improvement. This will ensure that the module stays
up to date.</p>
        <p>Repeating the evaluation on a new set of test data will give a clearer view
of real-world precision and recall. Another important aspect is to measure
enduser satisfaction with the medication reconciliation tool and how this a ects
their daily work. For this purpose, a survey is being performed on end users and
results are likely to be ready later this year.</p>
        <p>To improve recall, making use of machine learning technologies is a viable
option. This will, however, require more test data. A bene t of having a
handcrafted extraction module with high precision is that it can probably be used
for automated annotation (i.e. applying the module to new test data) so as to
make the gold standard creation job much easier.</p>
      </sec>
      <sec id="sec-7-2">
        <title>List of Abbreviations Used in the Paper</title>
        <p>ATC
EBNF
EPR/EHR
FEST</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Lo</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kwan</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandes</surname>
            ,
            <given-names>O.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shojania</surname>
            ,
            <given-names>K.G.</given-names>
          </string-name>
          :
          <article-title>Medication reconciliation supported by clinical pharmacists</article-title>
          . In:
          <article-title>Making Health Care Safer II: An Updated Critical Analysis of the Evidence for Patient Safety Practices</article-title>
          . Evidence Reports/Technology Assessments, No.
          <volume>211</volume>
          .
          <string-name>
            <surname>Rockville</surname>
          </string-name>
          (MD):
          <article-title>Agency for Healthcare Research and Quality (US) (</article-title>
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Greenwald</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Halasyamani</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Greene</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , LaCivita,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Stucky</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Benjamin</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          , et al.:
          <article-title>"aking inpatient medication reconciliation patient centered, clinically relevant and implementable: A consensus statement on key principles and necessary rst steps</article-title>
          .
          <source>Journal of Hospital Medicine</source>
          <volume>5</volume>
          (
          <issue>8</issue>
          ) (
          <year>2010</year>
          )
          <volume>477</volume>
          {
          <fpage>85</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. Mjorndal, T.,
          <string-name>
            <surname>Boman</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          , Hagg, S., et al.:
          <article-title>Adverse drug reactions as a cause for admissions to a department of internal medicine</article-title>
          .
          <source>Pharmacoepidemiol Drug Saf</source>
          .
          <volume>11</volume>
          (
          <issue>1</issue>
          )
          <article-title>(Jan-Feb</article-title>
          <year>2002</year>
          )
          <volume>65</volume>
          {
          <fpage>72</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. J, E., I, B.,
          <string-name>
            <surname>J</surname>
          </string-name>
          , E., et al:
          <article-title>Drug-related deaths in a department of internal medicine</article-title>
          .
          <source>Archives of Internal Medicine</source>
          <volume>161</volume>
          (
          <issue>19</issue>
          ) (
          <year>2001</year>
          )
          <volume>2317</volume>
          {
          <fpage>2323</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>DT</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>JD</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>DB</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>RG</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          :
          <article-title>Hospitalization and death associated with potentially inappropriate medication prescriptions among elderly nursing home residents</article-title>
          .
          <source>Archives of Internal Medicine</source>
          <volume>165</volume>
          (
          <issue>1</issue>
          ) (
          <year>2005</year>
          )
          <volume>68</volume>
          {
          <fpage>74</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bassi</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lau</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bardal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Use of information technology in medication reconciliation: a scoping review</article-title>
          .
          <source>Annals of Pharmacotherapy</source>
          <volume>44</volume>
          (
          <issue>5</issue>
          ) (
          <year>2010</year>
          )
          <volume>885</volume>
          {
          <fpage>897</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Cimino</surname>
            ,
            <given-names>J.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bright</surname>
            ,
            <given-names>T.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Medication reconciliation using natural language processing and controlled terminologies</article-title>
          .
          <source>In: Medinfo 2007: Proceedings of the 12th World Congress on Health (Medical) Informatics; Building Sustainable Health Systems</source>
          , IOS Press (
          <year>2007</year>
          )
          <volume>679</volume>
          {
          <fpage>683</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Giuse</surname>
            ,
            <given-names>D.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mickish</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Increasing the availability of the computerized patient record</article-title>
          .
          <source>Proc AMIA Annu Fall Symp</source>
          (
          <year>1996</year>
          )
          <volume>633</volume>
          {
          <fpage>7</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Goldman</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          , et al.:
          <article-title>Term domain distribution analysis: a data mining tool for text databases</article-title>
          .
          <source>Methods Inf Med</source>
          <volume>38</volume>
          (
          <issue>2</issue>
          ) (
          <year>1996</year>
          )
          <volume>96</volume>
          {
          <fpage>101</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Honigman</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , et al.:
          <article-title>A computerized method for identifying incidents associated with adverse drug events in outpatients</article-title>
          .
          <source>Int J Med Inform</source>
          <volume>61</volume>
          (
          <issue>1</issue>
          ) (
          <year>2001</year>
          )
          <volume>21</volume>
          {
          <fpage>32</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Mur</surname>
            ,
            <given-names>H.J.</given-names>
          </string-name>
          , et al.:
          <article-title>Electronically screening discharge summaries for adverse medical events</article-title>
          .
          <source>J Am Med Inform Assoc</source>
          <volume>10</volume>
          (
          <issue>4</issue>
          ) (
          <year>2003</year>
          )
          <volume>339</volume>
          {
          <fpage>50</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Hripcsak</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , et al.:
          <article-title>Unlocking clinical data from narrative reports: A study of natural language processing</article-title>
          .
          <source>Ann Intern Med</source>
          <volume>122</volume>
          (
          <issue>9</issue>
          ) (
          <year>1995</year>
          )
          <volume>681</volume>
          {
          <fpage>688</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Hripcsak</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuperman</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Friedman</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Extracting ndings from narrative reports: software transferability and sources of physician disagreement</article-title>
          .
          <source>Methods of Information in Medicine</source>
          <volume>37</volume>
          (
          <issue>1</issue>
          ) (
          <year>1998</year>
          ) 1{
          <fpage>7</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Spyns</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Natural language processing in medicine: an overview</article-title>
          .
          <source>Methods Inf Med</source>
          <volume>35</volume>
          (
          <issue>4-5</issue>
          ) (
          <year>1996</year>
          )
          <volume>285</volume>
          {
          <fpage>301</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roth</surname>
            .,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Exploring evidence for shallow parsing</article-title>
          .
          <source>Proc of Annual Conference on Computational Natural Language Learning</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Scowen</surname>
            ,
            <given-names>R.S.:</given-names>
          </string-name>
          <article-title>Extended bnf { a generic base standard</article-title>
          .
          <source>Software Engineering Standards Symposium</source>
          (
          <year>1993</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Navarro</surname>
          </string-name>
          , G.:
          <article-title>A guided tour to approximated string matching</article-title>
          .
          <source>ACM Computing Surveys</source>
          <volume>33</volume>
          (
          <issue>1</issue>
          ) (
          <year>2001</year>
          )
          <volume>31</volume>
          {
          <fpage>88</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>