<!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>Babylon Health's Medical Knowledge Graph: Why, What, and How</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Claudia Schulz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Damir Juric</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jetendr Shamdasani</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Coste</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Szymon Wartak</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aleksandar Savkov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nils Hammerla</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mohammed Khodadadi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Babylon Health</institution>
          ,
          <addr-line>London SW3 3DD, UK https://</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>Babylon Health o ers digital healthcare services through a mobile application. Besides video consultations with doctors, the app is equipped with a chatbot able to provide medical information and perform triage. To realise this digital healthcare experience, various services within Babylon generate, exchange, and consume health data and clinical knowledge. For example, text understanding services process the user's chatbot input and recognise relevant medical terms therein. These terms may need to be matched with prede ned symptoms and risk factors that form the input to the triaging engine, or with past diagnoses stored in user pro les. Furthermore, consultation notes are labelled with clinical codes to allow for easy processing and retrieval. To ensure that a uniform medical terminology is used throughout Babylon's services and to allow reasoning over medical data, a large medical knowledge graph was created [1], realised as the materialisation of an RDF triple store. Building the Babylon Knowledge Graph As illustrated in Figure 1, the Babylon Knowledge Graph was constructed by integrating information from multiple existing medical ontologies. To ensure accurate alignment of these heterogeneous ontologies, we developed a novel iterative approach for ontology integration [3], where SNOMED served as the seed ontology. Our approach tackles the problem of hierarchy incompatibility between ontologies by prioritising the current ontology over the one to be integrated thus minimising the amount of inconsistent mappings being dropped. We furthermore augmented the integrated ontologies with information extracted from biomedical papers. Since SNOMED and other ontologies mainly provide hierarchical relationships between concepts, this information extraction was focused on other types of relationships between medical concepts, e.g. that between diseases and their symptoms or risk factors. Knowledge Graph Validation To ensure the syntactic and semantic validity of the Babylon Knowledge Graph, we apply both automatic [4] and manual evaluation methods. Checking for (undesirable) cycles and investigating average path length are two of the straight-forward automatic syntax analyses performed. An example of ensuring semantic validity is to check that there is no label overlap between concepts. A manual evaluation of a sample of the Babylon Knowledge Graph was performed with the help of doctors, focusing on the correctness of the hierarchy and concept labels.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Schulz et al.</p>
      <p>NCI</p>
    </sec>
    <sec id="sec-2">
      <title>SNOMED CHV</title>
    </sec>
    <sec id="sec-3">
      <title>Alignment</title>
    </sec>
    <sec id="sec-4">
      <title>Information</title>
    </sec>
    <sec id="sec-5">
      <title>Extraction</title>
      <sec id="sec-5-1">
        <title>Babylon Knowledge Graph</title>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Language</title>
    </sec>
    <sec id="sec-7">
      <title>Understanding &amp;</title>
    </sec>
    <sec id="sec-8">
      <title>Entity Linking</title>
    </sec>
    <sec id="sec-9">
      <title>Validation</title>
      <p>I have a
headache</p>
      <sec id="sec-9-1">
        <title>Babylon App</title>
        <p>
          Knowledge Graph Powered Triage To enable the understanding and
processing of user input in a chatbot conversation, we employ various Natural
Language Processing (NLP) techniques: dependency parsing combined with entity
linking identi es medical terms in text and links them to concepts in the
Babylon Knowledge Graph. These concepts are then matched with symptoms and
risk factors represented in Babylon's triage system. However, the combination
of multiple concepts in the user input may correspond to a single concept in the
triage system and triage concepts may be more general than the very speci c
symptoms provided by a user. For example, the concepts `severe pain' and
`forehead' may have been identi ed in the user input, which have to be matched to
the single and more general triage concept `headache'. To realise this advanced
reasoning, we developed a hybrid reasoning method that combines NLP methods
with logic-based subsumption [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ].
        </p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Barisevicius</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Coste</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Geleta</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Juric</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khodadadi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stoilos</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zaihrayeu</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Supporting Digital Healthcare Services Using Semantic Web Technologies</article-title>
          .
          <source>In: ISWC'18</source>
          . pp.
          <volume>291</volume>
          {
          <issue>306</issue>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Juric</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stoilos</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wartak</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khodadadi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Reasoning with Textual Queries: A Case of Medical Text</article-title>
          .
          <source>In: ISWC'18 Poster</source>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Stoilos</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Geleta</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shamdasani</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khodadadi</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A Novel Approach and Practical Algorithms for Ontology Integration</article-title>
          .
          <source>In: ISWC'18</source>
          . pp.
          <volume>458</volume>
          {
          <issue>476</issue>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Stoilos</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Geleta</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wartak</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hall</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khodadadi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alghamdi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmidt</surname>
            ,
            <given-names>R.A.</given-names>
          </string-name>
          :
          <article-title>Methods and Metrics for Knowledge Base Engineering and Integration</article-title>
          .
          <source>In: WOP'18</source>
          . pp.
          <volume>72</volume>
          {
          <issue>86</issue>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>