<!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>iCAT: A Collaborative Authoring Tool for ICD-11</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tania Tudorache</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>Csongor Nyulas</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>Natalya F. Noy</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>Timothy Redmond</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>Mark A. Musen</string-name>
          <email>museng@stanford.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ICD-11 - Using Semantic Web Technologies</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Stanford Center for Biomedical Informatics Research, Stanford University</institution>
          ,
          <country country="US">US</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We present iCAT-the Collaborative Authoring Tool for the 11th revision of the International Classification of Diseases (ICD-11). ICD is a fundamental health-care resource developed by the World Health Organization (WHO) and applied in all United Nations countries for a variety of uses. A landmark change in this ICD-11 revision compared to previous ones is the use of OWL as a representation language and of Semantic Web technologies for the collaborative authoring of the ICD content. A community of international medical experts develops ICD-11 in a collaborative setting using the Web-based iCAT platform. Besides its extensive collaboration support, iCAT also fosters the interconnectedness of ICD-11 with other biomedical ontologies and terminologies by providing interlinking and reusing capabilities as a fundamental feature of the tool, while also storing the provenance metadata. The generic and extensible infrastructure as well as its declarative user interface allowed us to easily deploy iCAT in a production setting for the development of ICD-11 and two other WHO classifications. The declarative user interface allowed us to custom tailor the platform for domain experts use. iCAT is in production use since October 2009; it was used to author over 105,000 changes in the ICD-11 ontology, to create more than 40,000 cross-links to other biomedical ontologies, and to produce over 19,000 notes and discussions. The software is open source and a demo version of the platform is available at http://icatdemo.stanford.edu.1 The International Classification of Diseases (ICD) is the standard diagnostic classification developed by the World Health Organization (WHO) to encode information relevant for epidemiology, health management, and clinical use. Over the years, ICD has become an essential resource in all United Nations countries, who are applying ICD for a variety of uses, ranging from compiling basic health statistics, to billing, and to informing policy making. To keep up to date with the scientific progress, WHO publishes new revisions of ICD every decade. ICD-10 is the latest revision that is currently in use. Our group has been collaborating with WHO since 2007 to support the development of ICD-11.2 A large community of medical experts around the world are involved in the authoring of ICD11 in a collaborative Web-based platform, called iCAT [2]. The most important change 1 For the OCAS challenge we created a user account: ocas and password: ocas. 2 http://www.who.int/classifications/icd/revision/en/index.html</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>in ICD-11 compared to previous revisions is the decision of WHO to adopt a solid
formalization of ICD-11 and to use Semantic Web technologies for its development.
As a result, the underlying formalization of ICD-11 is OWL, and the platform used for
the collaborative authoring of ICD-11, iCAT, a customization of a generic Web-based
ontology editor, WebProte´ge´.3
2</p>
    </sec>
    <sec id="sec-2">
      <title>The ICD-11 Semantic Web Platform—iCAT</title>
      <p>With the radical change in the ICD-11 revision with respect to the underlying
representation, we needed to develop tools and methods that, on the one hand, are suited for
domain experts and on the other hand support the much richer Semantic Web content of
ICD-11. Some of the main requirements for the platform are: a) support the Web-based
collaboration of experts all around the world, b) provide features to inter-connect and
inter-link ICD-11 with other biomedical ontologies and terminologies, and c) provide
a user interface tailored to the needs of the domain experts that would hide or
sugarcoat complex OWL formalization details.</p>
      <p>As an overall strategy, we decided to implement generic features that can be used
for the development of other Semantic Web applications in the more generic WebProte´ge´
platform, and have only a very small number of plugins that are specific for ICD in iCAT
(which is a customization of WebProte´ge´).</p>
      <p>The development of the ICD-11 core ontology and of the Web platform took place
in parallel, with the former informing the latter. A WHO assigned committee of
ontology experts developed the core ontology in OWL. We defined forms and templates
based on this core ontology that domain experts use to enter the actual ICD-11
content in iCAT. During the last 4 years, the core ontology has evolved significantly, and
we had to make sure that our tools were adaptable enough to support seamlessly such
frequent changes. Our solution was to implement a declarative user interface4 as a
generic feature in WebProte´ge´, and iCAT became mainly a specific UI configuration
of WebProte´ge´. This feature allowed us to re-configure iCAT on-the-fly while the Web
application is running, and also to define user-specific views of the ICD ontology.</p>
      <p>
        Collaboration support: One of the main features of iCAT is its extensive
support for collaboration in the development of Semantic Web content, including change
tracking, contextualized threaded discussions, watches and notifications, an extensible
access policy mechanism, and generation of statistics of the ontology-development
process5 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. We reused the functionalities of Collaborative Prote´ge´ [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], which are
themselves implemented using Semantic Web technologies.
      </p>
      <p>
        Ontology interconnectedness and reuse support: ICD-11, as many other
ontologies, reuses terms from external ontologies and terminologies. We implemented
a generic plugin for WebProte´ge´ that enables simple import of terms from external
ontologies stored in the BioPortal6 ontology repository [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. This plugin allows users to
search for terms in BioPortal ontologies, to browse their details, and then to import
them into the ontology with a single click. All these operations are supported through
      </p>
      <sec id="sec-2-1">
        <title>3 http://protegewiki.stanford.edu/wiki/WebProtege 4 http://protegewiki.stanford.edu/wiki/WebProtegeLayoutConfig 5 http://protegewiki.stanford.edu/wiki/ChangeAnalysisTab 6 http://bioportal.bioontology.org</title>
        <p>REST calls to BioPortal. Several properties in ICD-11 have values coming from
external ontologies, such as body part, morphology, or genomic linkages. Based on the
property range definitions in the ICD ontology, we configured the fields in the UI for
these properties to search specific ontologies, or their subsets, in BioPortal. Some of the
external ontologies and terminologies we have linked to ICD-11 include SNOMED-CT,
The Gene Ontology (GO), the Online Mendelian Inheritance in Men (OMIM), the
International Classification of Functioning, Disability and Health (ICF) and the International
Classification of External Causes of Injuries (ICECI). During the last year, users have
created more than 40,000 links between ICD-11 and terms from external biomedical
ontologies. More than 14,000 of these links are for body part associated to a disease
and take values from the SNOMED CT Anatomy branch. Another use case for
interlinking ICD-11 with its previous revision, ICD-10 (also stored in BioPortal) is to keep
track of the ICD-10 to ICD-11 mappings that are essential for transitioning existing
medical software to the new ICD-11 coding system.</p>
        <p>Infrastructure reuse: We implemented WebProte´ge´ as a pluggable and extensible
architecture that can be customized to the needs of a particular project. As a proof, iCAT
is one particular customization of WebProte´ge´. We reused this generic infrastructure to
deploy similar platforms to support the production development of two other WHO
classifications: the International Classification of Traditional Medicine (ICTM) 7 and
the International Classification of Patient Safety (ICPS). 8 These two platforms required
only a new user interface configuration file and no code changes. Other customizations
of WebProte´ge´ are available on the WebProte´ge´ demo server.9</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Conclusions</title>
      <p>
        We presented iCAT, a customization of the WebProte´ge´ platform for the development
of ICD-11. We discussed the advantages of using Semantic Web technologies for
ICD11 elsewhere [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. iCAT has been in production use since 2009 and other customization
of WebProte´ge´ for real-world Semantic Web applications are available. All software is
open source, pluggable, reusable and under active development.
      </p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgments</title>
      <p>We thank our WHO collaborators for developing the project requirements and for the fruitful
collaboration. The work presented in this paper is supported by the NIGMS Grant 1R01GM086587.</p>
      <sec id="sec-4-1">
        <title>7 http://icatdemo.stanford.edu/ictm/</title>
        <p>8 http://icat-ps.stanford.edu
9 http://webprotege.stanford.edu</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>N.</given-names>
            <surname>Noy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Nyulas</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Musen</surname>
          </string-name>
          .
          <article-title>The Ontology Life Cycle: Integrated Tools for Editing, Publishing, Peer review, and Evolution of ontologies</article-title>
          .
          <source>In AMIA Annual Symposium Proceedings</source>
          , volume
          <year>2010</year>
          , page 552. American Medical Informatics Association,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>T.</given-names>
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Falconer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Nyulas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Noy</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Musen</surname>
          </string-name>
          .
          <article-title>Will Semantic Web Technologies Work for the Development of ICD-11? In The 9th Intl</article-title>
          .
          <source>Semantic Web Conference (ISWC</source>
          <year>2010</year>
          ), pages
          <fpage>257</fpage>
          -
          <lpage>272</lpage>
          . Springer,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>T.</given-names>
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. F.</given-names>
            <surname>Noy</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Musen</surname>
          </string-name>
          .
          <article-title>Supporting Collaborative Ontology Development in Protege</article-title>
          . In Seventh International Semantic Web Conference,
          <string-name>
            <surname>ISWC</surname>
          </string-name>
          <year>2008</year>
          , Karlsruhe, Germany,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>