<!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 Semantic-enabled Framework for Drug Recommendations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Charalampos Doulaverakis</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>George Nikolaidis</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Athanasios Kleontas</string-name>
          <email>kleontasg@ergobyte.gr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ioannis Kompatsiaris</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>AHEPA, University General Hospital of Thessaloniki</institution>
          ,
          <country country="GR">Greece</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Information Technologies Institute, Centre for Research and Technology Hellas</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>The paper presents Panacea, a semantic-enabled framework capable of o®ering drug-drug and drug-diseases interaction discovery. For enabling this kind of service, medical information and terminology had to be translated to ontological terms and be appropriately coupled with medical knowledge of the ¯eld. International standards for diseases and dug classi¯cations provide the backbone of the common representation of medical data while the medical knowledge of drug interactions is represented by a rule base which makes use of the aforementioned standards. The framework provides an e±cient drug recommendations service where Semantic Web technologies are coupled with traditional business rule engines.</p>
      </abstract>
      <kwd-group>
        <kwd>ontologies</kwd>
        <kwd>medical information modelling</kwd>
        <kwd>rule-based reasoning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        One of the health sectors where intelligent information management and
information sharing compose valuable preconditions for the delivery of top quality
services is personalized drug prescription. This is more evident in cases where
more than one drug is required to be prescribed, a situation which is not
uncommon, as drug interactions may appear. The problem is magni¯ed by the wide
range of available drug substances in combination with the various excipients
in which the former are present. Semantic Web technologies can play an
important role in the structural organization of the available medical information
in a manner which will enable e±cient discovery and access. Research projects
funded for enabling Semantic Web technologies in the diagnosis and therapeutic
procedures exist such as REMINE (http://www.remine-project.eu/) and PSIP
(http://www.psip-project.eu/) or works such as [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], but they don't fully address
the problem of automated drug prescription using drug-drug and drug-disease
interactions.
      </p>
      <p>
        In this work Panacea, a semantic-enabled system for discovering drug
recommendations and interactions, is presented. Panacea is based on experiences and
lessons drawn from the development of GalenOWL [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], a similar system which
had Semantic Web technologies in its core. As such, Panacea can be considered
the evolution of GalenOWL in terms of design and scalability. The paper is
organized with Section 2 giving details of the framework's architecture, the semantic
modelling and reasoning approaches, while Section 3 evaluates the framework,
discusses the results and concludes the paper.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Architecture, semantic modelling and reasoning</title>
      <p>In order to demonstrate the bene¯ts of the proposed drug recommendation
system, a use case is described: An elder man visits his family doctor complaining
for pain in his abdominal region which is accompanied with fever and he is
diagnosed with right pyelonephritis. The patient is already receiving clopidogrel
for chronic atrial ¯brillation, and candesartan and amlodipine for high arterial
blood pressure. For treating the patient, the doctor has to prescribe drugs in
order to treat the resulting in°ammation and fever, the cause of the
in°ammation (the pyelonephritis) and the abdominal pain. However, there should be
checks for interactions of the drugs that the patient is already prescribed with
the new condition and also verify that the new prescription will not have adverse
e®ects or interactions with the patient's current medication and medical history.
It is clear that the task for the doctor is hard and using an automated drug
recommendation system can minimize this risk of wrong prescriptions.</p>
      <p>
        The purpose of Panacea is to provide drug prescription recommendations
based on a patient's medical record and drug prescription rules. For details
regarding the initial medical and pharmaceutical data that were available, the
reader is encouraged to read [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>Panacea follows a layered reasoning process. During initialization, standard
medical terminologies and custom encodings are transformed to semantic
entities, using an appropriate vocabulary, and the initial ontology is constructed. A
reasoner binds to the ontology to infer relations such as inheritance, unions and
equivalences. In order to get recommendations in Panacea, a patient instance
with the appropriate medical record data is created and is fed to the knowledge
base. The reasoning process enriches the patient instance with inferred
knowledge, thus making that knowledge explicit. On this enriched instance, and by
utilizing a di®erent reasoning process, the set of medical rules is applied upon.
The result of this ¯nal stage of rule-based reasoning is the recommendations list
which can be retrieved through querying.</p>
      <p>Semantic transformations Panacea is built on top of international standards
of medical terminology in order to represent medical and pharmaceutical
information. The standard terminologies that are used are ICD-10 (International
Classi¯cation of Diseases), ATC (Anatomical Therapeutic Chemical
classi¯cation), UNII (Unique Ingredient Identi¯er) and IVT (International Virus
Taxonomy). Besides these international standards, a number of domain classi¯cations
have been declared in order to enhance the usability of the system or to
represent data that are not included in the standards. These are a) a Substance
classi¯cation which represent human-readable names for drug active substances
and correspond to ATC codes, b) Custom Concepts where they represent
diseases or drugs that are not present in the international standards, and c) Custom
Collections where they represent \groups" of substances and diseases that are
frequently present in drug interactions.</p>
      <p>SKOS vocabulary : The medical classi¯cations were expressed using the SKOS4
vocabulary. Each of the classi¯cations is placed under the skos:ConceptScheme
class and each entry is placed under the skos:Concept class. Classi¯cations
hierarchies are expressed with the skos:broaderTransitive and skos:narrowerTransitive
properties while Custom Collections are represented with the skos:member
property. Equivalences, e.g. between ATC codes and Substances, are expressed with
the skos:closeMatch property. A total of 64; 658 de¯nitions of classi¯cation codes
have been expressed using SKOS.</p>
      <p>Medical reasoning When querying the system for recommendations, a patient
instance is created with the initial patient data and is loaded in the knowledge
base. The reasoner, using RDFS inference and a small number of additional rules,
infers all the implicit patient data. As an example, a patient who su®ers from
a form of thrombocytopenia (icd:D69.6 ) will be inferred as also su®ering from
icd:D69, icd:D65-D69, icd:D50-D89 (through skos:broaderTransitive) and from
pnc-cc:de¯ciency-bone-marrow (through skos:member from the Custom
Collection de¯nition).</p>
      <p>Rule-based reasoning Drug recommendations in Panacea are generated using
a rule-based approach. The rules express the indications and contraindications
of drug substances while their premises are the medical de¯nitions and the
patients' age and sex group. The rules use the logical operators and (&amp;) and or
(j) and parentheses. An example of a rule is for the substance \ lisuride" which
is expressed as \lisuride = icd:E22.0 j (icd:E22.1 &amp; (icd:N91.0 j icd:N97)),
ageGroup=adult or elder ".The rule reads that: substance \lisuride" is
recommended for adult and elder patients who su®er from E22.0, OR su®er from E22.1
AND one of the N91.0 OR N97.</p>
      <p>
        The rule base consists of 1,342 rules whose validity has already been assessed
in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. These rules have to be properly parsed and transformed in order to match
the knowledge base and the, enriched with implicit knowledge, patient instance.
Any rule reasoner can be utilized to use the rule base. To demonstrate this
concept, two separate rule engine integrations, the Jena5 and Drools6 rule engines,
have been developed. While the Drools integration only required to translate the
rule base to the Drools Rule Language and develop an additional layer for Drools
to interface with the Patient instance, the Jena integration proved more complex
as the rule base is quite large to be handled e±ciently and certain optimizations
had to be implemented. These optimizations involve the introduction of coarse
rule selection phase where a subset A of candidate rules is created from the
4 SKOS vocabulary, http://www.w3.org/2009/08/skos-reference/skos.html
5 Apache Jena, http://jena.apache.org/
6 Drools { Business logic integration platform, http://www.jboss.org/drools/
Panacea-Jena
      </p>
      <p>Panacea-Drools
Initialization time
Memory consumption
Query response time
32.0 s
169 MB
47 ms
initial rule base that match the patient's sex and age group, and a ¯ne selection
phase where rules from A that contain at least one of the patient's data, i.e. a
skos term, in their premises are singled out and a ¯ne set R µ A is created from
them. R is loaded in Jena and can contain as little as 50 rules.</p>
    </sec>
    <sec id="sec-3">
      <title>Evaluation and Conclusion</title>
      <p>
        For evaluating the framework, a comparison was made between the two
approaches for the rule-based reasoning and GalenOWL. The comparison was
focused on the usability of the framework in a production environment. Three
parameters were measured: initialization time, memory consumption after
initialization, and query response time, i.e. the time needed to retrieve the
recommendations. Results are shown in Table 1, where values for GalenOWL are from
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The results show that both Panacea approaches exhibit satisfactory results
on all three parameters with Jena appearing to consume less memory as the rule
base is loaded during query time and with Drools being optimized to handle
large rule bases e±ciently.
      </p>
      <p>The paper presented Panacea, a framework for semantic-enabled drug
recommendations discovery. The framework utilizes a layered reasoning approach
were the medical ontology and the patient data instances are fed to a RDF(S)
reasoner and drug recommendations are generated using the second, rule-based
reasoning layer where any rule engine can be employed. Concerning future work,
the possibility to add probabilistic reasoning will be investigated and an
evaluation of the framework on real world data will be carried out.</p>
      <p>Acknowledgments This work has been supported by the national project
\Panacea", funded by GSRT Hellas under the \Support for SMEs" programme.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Adnan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Warren</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orr</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Ontology based semantic recommendations for discharge summary medication information for patients</article-title>
          .
          <source>In: Computer-Based Medical Systems (CBMS)</source>
          ,
          <source>2010 IEEE 23rd International Symposium on. (oct</source>
          .
          <year>2010</year>
          )
          <volume>456</volume>
          {
          <fpage>461</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Doulaverakis</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolaidis</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kleontas</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kompatsiaris</surname>
          </string-name>
          , I.:
          <article-title>GalenOWL: Ontology based drug recommendations discovery</article-title>
          .
          <source>Journal of Biomedical Semantics</source>
          <volume>3</volume>
          (
          <issue>14</issue>
          ) (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>