<!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>UCM at CLEF eHealth 2013 Shared Task1</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Luc a Hervas</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>V ctor Mart nez</string-name>
          <email>victormartinezsimon@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Irene Sanchez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alberto D az</string-name>
          <email>albertodiaz@fdi.ucm.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>NIL Group Universidad Complutense de Madrid C/Profesor Garc a Santesmases</institution>
          ,
          <addr-line>Madrid, 28040</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We are developing a system that analyzes medical reports and extracts a SNOMED-CT based concept representation. The more interesting characteristic of our system is not only that it can detect the concepts. It also takes into account if they appear in an a rmative, negative or speculative context. The system also separates the concept representation according to the structure of the document. Our system takes these steps: automatic orthographic correction, acronyms and abbreviation detection, negation and speculation phrase detection and medical concepts detection. For participating in Task 1 we have adapted our system in order to obtain the mentions that belongs to the Disorder semantic group de ned in the guidelines. The approach is based on using MetaMap to detect the concepts and the spans. Our aim was to identify which was the best way to use MetaMap in our system to solve the Task 1.</p>
      </abstract>
      <kwd-group>
        <kwd>Natural Language Processing</kwd>
        <kwd>medical report</kwd>
        <kwd>concept detection</kwd>
        <kwd>Metamap</kwd>
        <kwd>UMLS</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The goal of Task 1 is to analyze clinical text documents and nd mentions of
disorders. There are two subtasks: (1a) discovering the mention boundaries and
(1b) mapping each mention to a UMLS CUI. Normalization/mapping is limited
to UMLS CUIs of SNOMED codes. Participants are free to use any UMLS
resources [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>For participating in this Task we have adapted a system that analyzes medical
reports in order to obtain the mentions that belongs to the Disorder semantic
group de ned in the guidelines. The approach is based on using MetaMap to
detect the concepts and the spans.</p>
      <p>Our system extracts a SNOMED-CT based concept representation from a
medical report. Before the analysis we have other phases: a language corrector
and an acronyms expander. The more interesting characteristic of our system
is that not only detect the concepts, it also take into account if they appear in
an a rmative, negative or speculative context. The system also separates the
concept representation according to the structure of the document, that is, there
is a di erent representation for each section of the document.</p>
      <p>
        During our research, we discover the ShARe/CLEF eHealth 2013 Shared
Tasks [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. As the these tasks were very close of what we are developing, we decide
to participate to increase our knowing and the performance of our system. Our
aim was to identify which was the best way to use MetaMap in our system to
solve the Task1.
      </p>
      <p>We have submitted runs with no external annotations, two for task 1a and
two for task 1b. The di erence between the runs is only the DB used. We used
the 2012AA USAbase strict model for the rst run and the 2011AA USAbase
strict model for the second run. Our best results for task 1a show 0.504 F1
score with strict evaluation, and 0.660 F1 score with relaxed evaluation. Our
best results for task 1b show 0.362 Accuracy with strict evaluation and 0.870
Accuracy with relaxed evaluation.
2</p>
    </sec>
    <sec id="sec-2">
      <title>MetaMap</title>
      <p>
        MetaMap maps biomedical text to concepts in the UMLS Metathesaurus.
Several types of lexical/syntatic analysis are performed on the input text to perform
this mapping: tokenization, part-of-speech tagging, lexical lookup in the
SPECIALIST lexicon and shallow parsing. Per each noun phrase obtained is applied
the next processes: variant generation, candidate identi cation, mapping
construction and word sense disambiguation. Final scores are computed per each
candidate mapping combining di erent measures [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>MetaMap has di erent parameters that in uences its performance: data
options, output options and processing options. The data options allow to choose
the level of ltering and the UMLS data. The default setting is the Strict model,
where all types of ltering are applied. The Relaxed model only includes manual
and lexical lterings.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Processing</title>
      <p>We use the default setting of MetaMap to detect the di erent concepts and to
know their CUI. MetaMap retrieves some concepts, so to reduce the noise, we
only take the concepts with the greater score. We also use the MedPost/SKR
server included in MetaMap to perform word sense disambiguation. Finally, we
con gure the system to accept only the next semantic types that corresponds to
the Disorder semantic group de ned in the guidelines.</p>
      <p>{ Congenital Abnormality
{ Acquired Abnormality
{ Injury or Poisoning
{ Pathologic Function
{ Disease or Syndrome
{ Mental or Behavioral Dysfunction
{ Cell or Molecular Dysfunction
{ Experimental Model of Disease
{ Anatomical Abnormality
{ Neoplastic Process
{ Signs and Symptoms
4</p>
    </sec>
    <sec id="sec-4">
      <title>Framework evaluation</title>
      <p>Participants will be provided training and test datasets. The evaluation for all
tasks will be conducted using the withheld test data. Teams are allowed to use
any outside resources in their algorithms.
4.1</p>
      <p>Evaluation Measures
In subtask 1a, boundary detection of disorders, the evaluation measures are
F1score, Recall and Precision, where a TP is considered when the span obtained
is the same that the gold standard span, a FP when it is a spurious span, and
a FN when it is a missing span. There are two variants: Strict and Relaxed,
depending if the span is identical to the reference standard span, or if the span
overlaps the standard span.</p>
      <p>In subtask 1b, identify the boundaries of disorders and map them to a
SNOMED-CT code, the evaluation measure is Accuracy, where Correct is
considered as the number of disorder named entities with strictly correct span and
correctly generated code and Total is considered as the number of disorder named
entities. There are also two variants: Strict and Relaxed, depending if Total is
considered as the number of reference standard named entities, or if Total is
considered as the number of named entities with strictly correct span generated
by the system. In the rst case, the system is penalized for incorrect code
assignment for annotations that were not detected by the system. In the second case,
the system is only evaluated on annotations that were detected by the system.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Results</title>
      <p>We have submitted runs with no external annotations, two for task 1a and two
for task 1b. The di erence between the runs is only the DB used. We used the
2012AA USAbase strict model for the rst run and the 2011AA USAbase strict
model for the second run.</p>
      <p>Our best results for task 1a shown a 0.504 F1 score with strict evaluation,
and a 0.660 F1 score with relaxed evaluation. Our best results for task 1b shown
a 0.362 Accuracy with strict evaluation, and a 0.871 Accuracy with relaxed
evaluation.</p>
    </sec>
    <sec id="sec-6">
      <title>Discussion</title>
      <p>The detection of boundaries of disorders o ers bad results mainly due to the
limit of MetaMap in the discovering of the spans: the best Recall obtained is
around 0.42. Of course, the main problem is related with the discontinuous spans
that MetaMap is not able to process. With respect to the di erence between our
systems, the second version o ers slightly better results, as expected, because
it uses the 2011AA USAbase database. With respect to the type of evaluation,
higher scores are obtained with relaxed evaluation, mainly on Precision, but
Recall only increase to 0.558.</p>
      <p>With respect to the mapping of CUIs, the results are low in the strict
evaluation, but high in relaxed evaluation. That is due to the penalization for incorrect
code assignment for annotations not detected by the system.</p>
      <p>Our results show the baseline that can be obtained using MetaMap with the
strict model con guration. Then, we can conclude that MetaMap is not enough
to solve this task.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgements</title>
      <p>We want to acknowledge the support given by the Shared Annotated Resources
(ShARe) project, funded by the United States National Institutes of Health with
grant number R01GM090187.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aronson</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lang</surname>
            ,
            <given-names>F.M.:</given-names>
          </string-name>
          <article-title>An overview of MetaMap: historical perspective and recent advances</article-title>
          ,
          <source>Journal of the American Medical Informatics Association</source>
          , vol.
          <volume>17</volume>
          , no.
          <issue>3</issue>
          , pp.
          <fpage>229236</fpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Suominen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Salantera</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Velupillai</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Three Shared Tasks on Clinical Natural Language Processing. Proceedings of CLEF 2013</source>
          . To appear
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>