<!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>LIMSI @ CLEF eHealth 2015 - task 2</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Eva D'hondt</string-name>
          <email>eva.dhondt@limsi.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Brigitte Grau</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pierre Zweigenbaum</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Laboratoire d'Informatique pour la Mecanique et les Sciences de l'Ingenieur (LIMSI-CNRS 3251)</institution>
          ,
          <addr-line>Rue John von Neumann , 91400 Orsay</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper presents LIMSI's participation in the User-Centered Health Information Retrieval task (task 2) at the CLEF eHealth 2015 workshop[5]. In our contribution we explored two di erent strategies to query expansion, i.e. one based on entity recognition using MetaMap[1] and the UMLS[3], and a second strategy based on disease hypothesis generation using self-constructed external resources such a corpus of Wikipedia pages describing diseases and conditions, and webpages from the MedlinePlus health portal. Our best-scoring run was a weighed UMLS-based run which put emphasis on incorporating signs and symptoms recognized in the topic text by MetaMap. This run achieved a P@10 score of 0.262 and nDCG@10 of 0.196, respectively.</p>
      </abstract>
      <kwd-group>
        <kwd>information retrieval</kwd>
        <kwd>Metamap</kwd>
        <kwd>information extraction</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The 2015 retrieval task in CLEF eHealth competition[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] focused on the retrieval
of health information by lay people. This is an interesting research problem
which has gathered a lot of interest from the research community over the last
ve years. A survey conducted by [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] shows that 80% of internet users in the
U.S. look online for health information, most frequently for information about
a speci c disease or medical problem. General purpose search engines are
illequipped to deal with this particular type of search[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], however, which may lead
to erroneous self-diagnosis and self-treatment[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>The main problem lies in a vocabulary mismatch between the user and the
writers in the corpus: Lay people generally do not know the terminology to
accurately name or describe the symptoms or conditions they want to get information
on. Instead they use long, descriptive and often highly ambiguous queries, in the
hope of nding a relevant website that may show them additional keywords which
can be used to further re ne the search. Even if such information is found,
however, the user does not necessarily recognize its importance. He or she may also
add erroneous terms which will lead to inaccurate retrieval results. An additional
problem is that of the `informativeness' of the retrieved documents: A retrieval
system may return medical documents that are highly pertinent to the user's
information need but since he does not master the medical vocabulary, they are
nevertheless useless to him in practice. A retrieval system that is adapted to this
task should have the following properties: (a) resolve ambiguities in the
circumlocutory queries, (b) bridge the terminology gap between query and documents
and (c) incorporate a user-centric mesure of informativeness when presenting
the retrieved documents to the user.</p>
      <p>In this paper we present our participation to the 2015 health information
retrieval track. As this is our rst contribution to this type of track, we only
explored baseline approaches for content retrieval and did not incorporate a
user-centric measure in our retrieval system.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Task and Corpus Description of CLEF eHealth Task 2</title>
      <p>
        As part of the CLEF eHealth 2015 track [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] task 2 focused on retrieval of web
pages containing health information by non-expert users, i.e. lay man. The
organizer made a corpus of 1.102.120 web pages of medical and health-related
websites available to the participants. These pages were crawled on the web as
part of the khresmoi project1. The types of web pages in the corpus are quite
varied: They include forum threads from health fora, pages from web shops for
health-related products as well as high-quality health information sites such as
MedlinePlus, ... . The crawled documents were provided in their raw HTML
(Hyper Text Markup Language) format along with their uniform resource locators
(URL).
      </p>
      <p>
        Given a circumlocutory query, i.e. long, ambiguous topic query written by
a lay person, the retrieval system had to return a maximum of 1000 web pages
that were relevant to the users information need. Topics have been created using
the process described in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]: Lay people were asked to write a descriptive query
of a sign and/or symptom of a medical condition that was shown in a picture or
video. Participants were provided with 5 training topics and 66 topics for test
phase. The queries were available in multiple languages, such as Arabic, Czech,
French, German, Farsi and Portuguese. We opted to use only the English queries.
3
3.1
      </p>
    </sec>
    <sec id="sec-3">
      <title>System Components</title>
      <sec id="sec-3-1">
        <title>Preprocessing</title>
        <p>
          As the web pages in the corpus came from various sources, their quality varied
greatly. We built our own HTML parser to extract the following information
from a given web page:
{ title: We extracted the title from the title tag in the head block of the web
page. Even though this is a required element (according to the W3C rules),
a small subset of web pages in the corpus had no titles.
1 http://www.khresmoi.eu/
{ description: We extracted the description from the description meta tag
(&lt;meta name="description" content="..."&gt;) in the head block of the
web page. The description of a website is the little text excerpt which is
shown to users in search engine rankings. While it is an optional element in
a web page, good quality websites will always have a short description text.
{ keywords: Like the description tag, the content of this meta tag is useful
for search engine rankings and may list a few keywords to summarize the
content of a page. It is now generally considered obsolete and mostly used
to detect spam so this eld is often left un lled.
{ content: We also extracted the body of the web page and performed
boilerplate and duplicate removal using the Justext Python package developed
by [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. The resulting strings contains free running text as well as title strings
and the contents of tables from the original web page.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2 Indexing</title>
        <p>After preprocessing the corpus was indexed using the Apache Solr toolkit2. We
indexed the following elds separately:
{ title: Text extracted from corresponding tag
{ description: Text extracted from corresponding tag
{ keywords: Words extracted from corresponding tag
{ content: Text extracted from body of the web page
{ text: A catchall eld that combines the information in the four previous
elds.
{ URL: URL of the web page, both in full form and its base name
{ UID: Unique identi er of the web page which serves as the primary key in
the index</p>
        <p>The text in the title, description and content elds was indexed with
a customized Solr eldType which incorporated intermediary steps such as
tokenization, stopword removal, normalization of English possesives and stemming
using the Hunspell stemmer 3. The latter was to English, and we did not employ
stemmers for di erent languages.
3.3</p>
      </sec>
      <sec id="sec-3-3">
        <title>Annotating with MetaMap</title>
        <p>
          Our rst strategy was to experiment with direct translations of circumlocutory
terms into their medical variants in order to have a well-controlled query
expansion based on the UMLS. By allowing both medical terms, e.g. `Epidermis' and
their common language counterparts, e.g. `skin' we aim to increase the coverage
of the query in the corpus. Recognition of the medical terms and entities was
2 http://lucene.apache.org/solr/
3 Can be found at
https://www.elastic.co/guide/en/elasticsearch/guide/master/hunspell.html
done using MetaMap [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], a state-of-the-art Named Entity Recognizer for medical
English. After visual inspection of the training data, we con gured MetaMap to
return only entities from a limited set of Semantic Types (such as body part,
age group, etc.). This ltering set was constructed manually after analysis of the
entities found for the training queries.
        </p>
        <p>The identi ed entities are likely to be more important for the retrieval
process than other information in the topic query. We experimented with several
weighing schemes in Solr in which information from MetaMap was combined
with the original query terms in di erent set-ups. We used the two weighing
schemes that scored the highest on training data for the o cial runs, i.e. Run2
and Run3. Table 1 shows the di erent query construction schemes for the nal
runs.
3.4</p>
      </sec>
      <sec id="sec-3-4">
        <title>Generation of Disease Hypotheses</title>
        <p>For our second strategy we aimed to go directly from the circumlocutory query
to the name of the disease or condition that the user wanted to nd, and use
these terms to expand the original query to search in the Khresmoi corpus.
The rationale behind this strategy was to search for diseases or conditions in
a smaller, more controlled and consistent corpus (rather than the more varied
Khresmoi web corpus). To this end we gathered two small corpora of (web)
pages describing the most frequent diseases in clear and common language (so
as to match the language use in the query topics). We selected a corpus of 2496
articles from Wikipedia, and another corpus of 1796 web pages from
MedlinePlus4. Each document describes exactly one disease or condition, and the two
corpora overlapped, i.e. all diseases in the MedlinePlus corpus has a
corresponding page in the Wikipedia corpus. These two corpora were chosen with an eye
on their language use: The webpages in MedlinePlus are written in a very
accessible style and contain a lot of descriptions of signs and symptoms. Wikipedia
articles are more varied in style and are more likely to contain medical terms
with (additional) explanations in lay language.</p>
        <p>For each corpus we built a separate index in Solr, and then used the topics
to query the wikipedia index (run 4) and both the wikipedia and MedlinePlus
indices (run5). For each topic we extracted the top 3 documents, and used their
title i.e. disease name as query expansion terms for the original query with which
we then searched the Khresmoi corpus. Table 1 shows how the original query
terms and the terms for the disease hypotheses were combined.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Submitted Runs</title>
      <p>We submitted the following 5 runs for o cial evaluation. Table 1 summarizes
the query construction methods and resources used for each run.
4 http://www.nlm.nih.gov/medlineplus/
{ LIMSI EN Run1: A baseline bag-of-words run. In this run the processed
words of the query are searched for in the title, description. keywords and
content elds of the documents in the Khresmoi corpus. All elds have equal
weight.
{ LIMSI EN Run2: A weighed run with emphasis on terms that have been
recognized as agegroup and bodypart Semantic Types. The topics were
processed with MetaMap to identify a body part terms (UMLS Semantic Types
`bdsy', `blor', `bpoc', `bsoj') and agegroup terms (UMLS Semantic Type
`aggp') in the topic query texts. If terms with these Semantic Types were
recognized, the recognized string and preferredString (from UMLS) were
added to the query and given extra weight (^1.5) in the keyword eld.
{ LIMSI EN Run3: A weighed run with emphasis on terms of agegroup,
body parts, symptoms and diseases. The topics were processed with MetaMap
to identify a body part terms (UMLS Semantic Types `bdsy', `blor', `bpoc',
`bsoj'), terms that denote an age group (UMLS Semantic Type `aggp') and
terms that denote symptoms (UMLS Semantic Type `sosy') and disorders
(UMLS Semantic Type `dsyn'). For the recognized body part and age group
terms, the recognized string and preferredString (extracted from UMLS) are
added to the query and given extra weight (^1.5) in the keywords eld. The
recognized string and preferredStrings from recognized signs and disorders
were also added to the query and given a higher weight in the keywords eld
(^1.5) and title eld (^2).
{ LIMSI EN Run4: In this run we used the Wikipedia corpus as an external
source to generate disease hypotheses for a given topic. These disease names
were then added to the query with a weight relative to their retrieval score.
The terms were added to all elds but given extra weight (^2) when found
in the keywords, description and/or title elds.
{ LIMSI EN Run5: This run is similar to run 4 but the disease hypotheses
were retrieved on a corpus that consisted of 2496 Wikipedia pages and 1796
MedlinePlus webpages.</p>
      <p>The terminology in Table 1 is as follows: `origQuery' refers to the (processed)
words in the original query; `bodypartEntities', `agegroupEntities', ... refer to
the recognized strings and preferredNames of UMLS concepts that were
recognized by MetaMap (per UMLS Semantic Type); `diseaseHypotheses' refers to
the strings of the diseases and conditions that were retrieved in the Wikipedia
(and MedlinePlus) corpora.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Results</title>
      <p>Table 2 shows the o cial results we achieved for the ve di erent runs on the
test set. Please note that only the top 10 retrieved documents from the run 1 to
3 were used in the evaluation pool. Overall, we nd that the best-scoring system
was that of run3, which combined term weighing and query expansion based
on MetaMap and the UMLS. Run 4 and 5 which both used external sources to
title:forigQueryg +
content:forigQueryg +
description:forigQueryg +
keywords:forigQueryg +
title:fdiseaseHypotheses^retrievalScoreg +
content:fdiseaseHypotheses^retrievalScoreg +
description:fdiseaseHypotheses^retrievalScoreg +
keywords^2:fdiseaseHypotheses^retrievalScoreg +
title^2:fdiseaseHypotheses^retrievalScoreg +
description^2:fdiseaseHypotheses^retrievalScoreg
The scores presented in table 2 are generally quite low: Of all submitted runs,
only Run 3 outperformed the baseline (Run 1). Overall, we see that the
UMLSbased runs did better than those that incorporated disease hypotheses. Close
analysis of the disease hypotheses runs shows that the submitted runs contained
a bug in the query construction process which lead to lower performance. We
reran Runs 4 and 5 and evaluated them with the relevance assessments released
by the track organizers. While these scores are higher, they remain well below
the scores attained by Run3.</p>
      <p>The scores for both disease hypotheses runs are very similar. Analysis of
the disease hypotheses that were generated by retrieval in the Wikipedia corpus
versus the combination of the Wikipedia and the MedlinePlus corpora, showed
that the di erence between the lists of retrieved diseases from both corpora were
very small. In fact, di erent hypotheses were retrieved for only 19 out of the 66
queries. These queries did achieve higher scores in run 5 which shows that the
added information from the MedlinePlus corpus leads to better hypotheses. As
a follow-up to this task, it would be interesting to compare our hypotheses with
those that were used to generate the test queries.</p>
      <p>When we turn our attention to the UMLS-based runs we see that these
remain fairly close to the baseline scores. We believe that the relatively small
impact of additional elds could be attributed to uneven distribution of
information in the corpus: We found that around 57.4% and 59.2% of documents in
the corpus had empty elds for the description and keywords elds, respectively.
The other elds were better lled: Only around 1% of the documents had an
empty title eld, but we do see that about 11% of the pages in the corpus did
not have any information in the content eld. The latter is mostly due to the
di erent ( le) formats that were included in the crawl. Our parser could only
deal with HTML documents and did not process other le types such as PDF or
PowerPoint les. In total, however, only 7,949 les were completely empty (i.e.
no text information in either title, description, keywords and content elds, and
therefore unretrievable for any of the topics). None of these les featured in the
list of reference les though.</p>
      <p>The decreased score for Run2 shows that terms for recognized age group
and body part are not informative query expansion terms and including them
actually harms performance. We believe that certain age group terms (such as
`child', `toddler', ... ) are too general and their relative higher importance in the
query leads to the retrieval of non-relevant articles.</p>
      <p>Recognized symptoms and disorders seem much more informative (Run3)
query expansion terms, especially in the title eld. Intuitively this makes sense:
If a (correctly recognized) disease or symptom is referenced in the title of the
web page, it will be topically relevant.
7</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>In this paper we presented our participation to the User-Centered Health
Information Retrieval task (task 2) at the CLEF eHealth 2015 workshop. We explored
two di erent baseline strategies to query expansion: One based on Entity
Recognition of concepts in the UMLS, and another based on disease hypothesis
generation using external sources such as Wikipedia and MedlinePlus. We found that
the disease hypotheses approach was not adequate and lead to a serious decrease
in performance, which is most likely caused by the relatively small coverage of the
corpora. For the UMLS-based runs, we found that performing query expansion
with terms describing recognized Disease and Symptom entities, lead to
improvements over our baseline. Our best-scoring run was a weighed UMLS-based run
which put emphasis on nding terms for signs and symptoms recognized in the
topic text in the title and keywords eld (with relative weights of 2 and 1.5,
respectively). This run achieved a P@10 score of 0.262 and nDCG@10 of 0.196.
In this year's participation we limited our systems to a baseline content-based
retrieval. In a future participation, we would like to incorporate a method of
reranking based on readability, and pro t from the multilingual topics that were
o ered in this years track.
This work was supported by the French National Agency for Research under
grant Accordys5 ANR-12-CORD-0007.
5 Agregation de Contenus et de COnnaissances pour Raisonner a partir de cas dans
la DYSmorphologie foetale</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aronson</surname>
            ,
            <given-names>A. R.</given-names>
          </string-name>
          (
          <year>2001</year>
          ).
          <article-title>E ective Mapping of Biomedical Text to the UMLS Metathesaurus: the MetaMap program</article-title>
          .
          <source>In Proceedings of the AMIA Symposium</source>
          , p.
          <fpage>17</fpage>
          . American Medical Informatics Association.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Benigeri</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Pluye</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          (
          <year>2003</year>
          ).
          <article-title>Shortcomings of Health Information on the Internet</article-title>
          . Health promotion international,
          <volume>18</volume>
          (
          <issue>4</issue>
          ),
          <fpage>381</fpage>
          -
          <lpage>386</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bodenreider</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          (
          <year>2004</year>
          ).
          <article-title>The Uni ed Medical Language System (UMLS): Integrating Biomedical Terminology</article-title>
          .
          <source>Nucleic acids research</source>
          32, no.
          <issue>suppl 1</issue>
          :
          <fpage>D267</fpage>
          -
          <lpage>D270</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Fox</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <article-title>Health topics: 80% of Internet Users look for Health Information online</article-title>
          .
          <source>Pew Internet &amp; American</source>
          Life Project.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Goeuriot</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kelly</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suominen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hanlen</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neveol</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grouin</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palotti</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <given-names>G.</given-names>
            <surname>Zuccon</surname>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>Overview of the CLEF eHealth Evaluation Lab 2015"</article-title>
          <source>in CLEF 2015 - 6th Conference and Labs of the Evaluation Forum, Lecture Notes in Computer Science (LNCS)</source>
          , Springer.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Pomikalek</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <article-title>Removing boilerplate and duplicate content from web corpora. Disertacn prace, Masarykova univerzita, Fakulta informatiky</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Stanton</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ieong</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Mishra</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Circumlocution in Diagnostic Medical Queries</article-title>
          .
          <source>In Proceedings of the 37th international ACM SIGIR conference on Research &amp; development in information retrieval</source>
          , pp.
          <fpage>133</fpage>
          -
          <lpage>142</lpage>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Zuccon</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koopman</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Palotti</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>Diagnose this if you can: On the e ectiveness of search Engines in nding medical self-diagnosis information</article-title>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>