<!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>Extracting Medical Information Using Linked Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jakub Koz´ak⋆</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Neˇcasky´</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jaroslav Pokorny´</string-name>
          <email>pokorny@ksi.mff.cuni.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Mathematics and Physics, Charles University in Prague</institution>
          ,
          <addr-line>Malostransk ́e n ́amˇest ́ı 25, 118 00 Prague</addr-line>
          ,
          <country country="CZ">Czech Republic</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Medical documentation is usually represented as a free text. That makes it almost unusable for all other analytical purposes. It would be a great advantage to have at least some information structured in a machine readable form. In this contribution we introduce a system which performs information extraction from partially structured texts such as discharge summaries. It is a rule-based system using ontologies even for rule formulation. We take advantage of Linked Data principles, represent all knowledge as ontologies and make output data available in RDF. We hope this is a right direction for medical information publication and enrichment with other data e.g., from Linked Open Data cloud.</p>
      </abstract>
      <kwd-group>
        <kwd>information extraction</kwd>
        <kwd>discharge summaries</kwd>
        <kwd>Linked Data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Medical documentation offers a rich source of information which has a great
potential for further analysis. It could lead to improvement of the quality of
healthcare. Unfortunately, the documentation is usually represented as a free
text which means the data has to be extracted first.</p>
      <p>Free text representation of medical documentation prevails also in healthcare
in the Czech Republic. In this contribution we will discuss the issue of
information extraction (IE) from partially structured texts such as discharge summaries
written in Czech language, which has its own specifics and special tools for
natural language processing (NLP) has to be used. By partially structured text we
mean text composed of sections with headings which can be recognized with
regular expressions. Discharge summaries usually contain a finite set of sections
e.g., anamnesis, examination and procedures, medication etc.</p>
      <p>
        Information extraction can be performed using basically two methods. It
is either based on rules or on machine learning (ML) or their combination. We
have decided to use a rule-based approach which was also mostly used and among
best performing in The Third i2b2 Workshop on Natural Language Processing
Challenges for Clinical Records which was focused on medication information
extraction [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Recently, a well performing rule-based system for IE from medical
records has also been developed for Polish language which is close to Czech
language [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>Discharge summaries contain various data about patients. Therefore a vast
domain model would be needed for the extraction of all information. There exist
a number of different medical dictionaries, thesauri and ontologies. We can point
out at least some of them. SNOMED CT1 or UMLS2 are well-known controlled
vocabularies. Most of the vocabularies are available in English but not in Czech.
It makes them almost unusable unless translated.</p>
      <p>
        Previous information led us to a decision to build our own domain model. We
have decided to adopt principles of Linked Data which are intended to become
a standard for publishing data on the Web [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This approach is quite beneficial
when thinking about complicated queries with the use of external knowledge
bases e.g., from Linked Open Data3 (LOD) cloud. Enrichment of data using
LOD cloud has been proven to be successful at Mayo Clinic [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>We will present a system which is able to extract information from partially
structured texts. The system uses domain ontologies and rules described in RDF4
(Resource Description Framework). External knowledge can be included e.g.,
from Linked Data cloud. Preliminary application to discharge summaries will be
presented.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Information Extraction System</title>
      <p>We have developed a system that allows IE from partially structured texts using
the advantages of ontologies and Linked Data. Linked Data principles allow
enrichment of data in internal system by linking them to other data and therefore
run more complex queries. The system itself is domain independent because the
knowledge is only contained in configurable ontologies in the underlying data
store.</p>
      <p>The process of extraction can be summarized into a pipeline:
– natural language processing
– section matching using templates
– entity and more complex structures recognition
– RDF output</p>
      <p>Czech language is quite complicated in comparison with English. Therefore at
least basic NLP procedures have to be conducted. Our system performs
tokenization first and then lemmatization using the tool MORCE5 (Czech Morphology
- software for morphological disambiguation (tagging) of Czech text).</p>
      <sec id="sec-2-1">
        <title>1 http://www.ihtsdo.org/snomed-ct/</title>
        <p>2 http://www.nlm.nih.gov/research/umls/
3 http://linkeddata.org
4 http://www.w3.org/RDF/
5 http://ufal.mff.cuni.cz/morce</p>
        <p>For definition of input text structure, i.e. section recognition, a special
template, which should be common for one type of texts, is used. Templates are
implemented using XML and have an XML schema. Each section is represented
with one entity or property in ontology which describes the type of documents
e.g. discharge summaries. The following example shows definition of
pharmacological anamnesis which is preceded by the heading defined with the regular
expression “FA:” and is represented with the range of property
“hasPharmacologicalAnamnesis”:
&lt;def:section def:scope="PARAGRAPH" def:outputElementType=
"...#hasPharmacologicalAnamnesis"&gt;
&lt;def:header&gt;</p>
        <p>&lt;def:expression&gt;FA:&lt;/def:expression&gt;
&lt;/def:header&gt;
&lt;/def:section&gt;</p>
        <p>After matching the section, entities are being extracted based on the rules.
We recognize three types of rules regular expression, taxonomy or complex
structure. The first type seeks for entities described with a regular expression. The
second one looks up a literal property from ontology. Finally, complex structure
combines the previous two approaches.</p>
        <p>If we want to extract basic medication information from the piece of text
“Anopyrin 100 mg 1-0-0” contained in the section describing pharmacological
anamnesis, we need to combine a taxonomy lookup for the name of the
medication, regular expression for the dosage and another complex structure for the
strength (number plus unit). Complex structures are more or less trees and allow
using constructs such as optional, after or close-to, which refer to the position
of previously found part of information. Example of informal model of complex
structure rule for medication extraction is given in Figure 1.</p>
        <p>The system is able to extract quite complex structures using rules described
above. The rules are defined also in RDF and form an ontology of rules, which
is pointing to other ontologies. Schema in Figure 2 shows how the document is
linked to ontologies and extraction rules.
Extracted information is made available as RDF and can be easily inserted
into a triple store. The presented system uses Virtuoso6 for ontology storage.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>The system was originally developed as a universal tool for IE from partially
structured texts which can be used in various domains (job descriptions, CVs,
public contract offers, discharge summaries etc.). The only necessary thing to do
is to connect domain ontology and to define templates and extraction rules.</p>
      <p>We are now trying to use the system on discharge summaries from an internal
clinic, which usually contain these sections: reason for acceptance, anamnesis,
examinations and procedures, therapy, conclusion and recommendation. Each of
these sections can have many subsections annotated with some kind of headings
which we are trying to recognize using our IE tool.</p>
      <p>Application to medication extraction and laboratory results (also free text)
extraction shows promising result. The research is still in progress. It involves a
lot of activities e.g. domain knowledge representation using ontologies.</p>
      <p>We believe that systems based on ontologies and using Linked Data
principles, which allow data enrichment, have a bright future in medicine and we plan
to aim our further efforts this way.</p>
      <sec id="sec-3-1">
        <title>6 http://virtuoso.openlinksw.com</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Uzuner</surname>
            <given-names>O</given-names>
          </string-name>
          ¨.,
          <string-name>
            <surname>Solti</surname>
            <given-names>I.</given-names>
          </string-name>
          , Cadag E.:
          <article-title>Extracting medication information from clinical text</article-title>
          .
          <source>J Am Med Inform Assoc</source>
          <volume>17</volume>
          ,
          <fpage>514</fpage>
          -
          <lpage>518</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Mykowiecka</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marciniak</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kup</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Rule-based information extraction from patients' clinical data</article-title>
          .
          <source>J. of Biomedical Informatics</source>
          <volume>42</volume>
          ,
          <issue>5</issue>
          ,
          <fpage>923</fpage>
          -
          <lpage>936</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bizer</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heath</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked Data - The Story So Far</article-title>
          .
          <source>International Journal on Semantic Web and Information Systems (IJSWIS) 5</source>
          ,
          <issue>3</issue>
          ,
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Pathak</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kiefer</surname>
            <given-names>RC</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chute</surname>
            <given-names>CG</given-names>
          </string-name>
          .:
          <article-title>Applying Linked Data principles to represent patient's electronic health records at Mayo Clinic: A case report</article-title>
          .
          <source>2nd ACM SIGHIT International Health Informatics Symposium (IHI)</source>
          ,
          <fpage>455</fpage>
          -
          <lpage>464</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>