<!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>
      <journal-title-group>
        <journal-title>Link Type AML
Phenotype-to-Phenotype</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>On adopting Ontology Alignment techniques within the Phenotype Acquisition Process?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>E. Jime´nez-Ruiz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>D. Hovland</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>L. Slaughter</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>T. Ha˚ndstad</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>A. Waaler</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Informatics, University of Oslo</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Oslo University Hospital</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <volume>6</volume>
      <issue>344</issue>
      <abstract>
        <p>The work presented in this paper is framed within the context of the BigMed project, a project funded by the Norwegian Research Council. One of the objectives of BigMed is to enhance the phenotype acquisition process in newborns with a monogenetic disorder, one of the four patient groups studied in the project. The use of the Human Phenotype Ontology (HPO) [1] to tag phenotypes and systems like PhenoTips have substantially contributed to the overall phenotype acquisition workflow. PhenoTips [2] is a system for the acquisition of phenotypic information in patients with a genetic disease. PhenoTips also suggests, given a selected set of HPO terms, candidate diagnoses using OMIM (Online Mendelian Inheritance in Man) codes, and related genes for a subsequent genetic test. Although PhenoTips represents a fantastic effort, we believe it could be extended with suitable Semantic Web solutions. In this paper, we present the first steps to adopt ontology alignment techniques to contribute to the diagnostic process.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1 Introduction
2
In order to obtain phenotype-to-disease links between HPO and OMIM terms, as in the
reference datasets presented above, we exploited the semantic information in OMIM
and the computed mappings. We extracted the associated OMIM disease terms for a
given OMIM phenotype term using the ontology properties manifestation of and
inheritance type of. The second row in Table 1 shows the number of phenotype-to-disease
links derived from the phenotype-to-phenotype mappings.</p>
      <p>Results and Discussion. Table 2 shows the coverage of the links derived from the
automatically computed alignments.4 The results in terms of Recall are not impressive and
only when considering all alignment sets we get near to 50% Recall. Giving a closer
look at the results, we noticed that a few OMIM ids present in the annotation files were
missing in the OMIM ontology.5 However, the missing OMIM ids are not significant
enough to explain the low Recall values. We also observed that a large number (i.e.,
&gt;1,000) of HPO terms occurring in the links extracted from the annotation files were
not aligned to OMIM terms by any of the ontology alignment systems. There may be
three possible explanations: (i) the alignment systems fail to discover relevant
correspondences, (ii) the OMIM ontology does not cover all phenotype terms from the HPO
ontology, and/or (iii) the description of related diseases to a phenotype in the OMIM
ontology is limited. Future work aims at clarifying these possible limitations.</p>
      <p>Although the results regarding Recall are not encouraging, the results with respect
to Precision may be considered promising since there are links derived by the
automatically computed correspondences that are not present in the annotation files. These new
links, however, require manual curation to assess their validity.
4 The coverage has been calculated in terms of Precision and Recall with respect to the
(reference) link sets extracted from the hpo-annotations and phenotips-annotations files.
5 OMIM v.2016AB: https://bioportal.bioontology.org/ontologies/OMIM</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Ko¨hler, S., et al.:
          <article-title>The human phenotype ontology in 2017</article-title>
          .
          <source>Nucleic Acids Res</source>
          .
          <volume>45</volume>
          (
          <issue>D1</issue>
          ) (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Girdea</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , et al.:
          <source>PhenoTips: Patient Phenotyping Software for Clinical and Research Use. Human Mutation</source>
          <volume>34</volume>
          (
          <issue>8</issue>
          ) (
          <year>2013</year>
          )
          <fpage>1057</fpage>
          -
          <lpage>1065</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Harrow</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jimenez-Ruiz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , et al.:
          <article-title>Matching disease and phenotype ontologies in the ontology alignment evaluation initiative</article-title>
          .
          <source>Journal of Biomedical</source>
          Semantics (in press) (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Achichi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , et al.:
          <article-title>Results of the Ontology Alignment Evaluation Initiative 2017</article-title>
          .
          <source>In: 12th International Workshop on Ontology Matching (OM)</source>
          .
          <article-title>(</article-title>
          <year>2017</year>
          ) http://oaei.ontologymatching.org/.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>