<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">ResProt</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Res Protoc</journal-id>
      <journal-title>JMIR Research Protocols</journal-title>
      <issn pub-type="epub">1929-0748</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
    <article-id pub-id-type="publisher-id">v6i10e196</article-id>
    <article-id pub-id-type="pmid">29021130</article-id>
    <article-id pub-id-type="doi">10.2196/resprot.7904</article-id>
    <article-categories>
      <subj-group subj-group-type="heading">
        <subject>Original Paper</subject>
      </subj-group>
      <subj-group subj-group-type="article-type">
        <subject>Original Paper</subject>
      </subj-group>
    </article-categories>
    <title-group>
      <article-title>Knowledge Management Framework for Emerging Infectious Diseases Preparedness and Response: Design and Development of Public Health Document Ontology</article-title>
    </title-group>
    <contrib-group>
      <contrib contrib-type="editor">
        <name>
          <surname>Sanchez</surname>
          <given-names>Travis</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Fu</surname>
          <given-names>Clementine</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Du</surname>
          <given-names>Jingcheng</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>He</surname>
          <given-names>Zhe</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Lau</surname>
          <given-names>Adela</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="author" id="contrib1">
        <name name-style="western">
          <surname>Zhang</surname>
          <given-names>Zhizun</given-names>
        </name>
        <degrees>MS</degrees>
        <xref rid="aff1" ref-type="aff">1</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-6192-0789</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib2">
        <name name-style="western">
          <surname>Gonzalez</surname>
          <given-names>Mila C</given-names>
        </name>
        <degrees>MPH</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0001-6318-9523</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib3">
        <name name-style="western">
          <surname>Morse</surname>
          <given-names>Stephen S</given-names>
        </name>
        <degrees>PhD</degrees>
        <xref rid="aff2" ref-type="aff">2</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-5434-5683</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib4" corresp="yes">
      <name name-style="western">
        <surname>Venkatasubramanian</surname>
        <given-names>Venkat</given-names>
      </name>
      <degrees>PhD</degrees>
      <xref rid="aff1" ref-type="aff">1</xref>
      <address>
        <institution>Fu Foundation School of Engineering and Applied Science</institution>
        <institution>Department of Chemical Engineering</institution>
        <institution>Columbia University</institution>
        <addr-line>500 W. 120th St., Mudd 801</addr-line>
        <addr-line>New York, NY,</addr-line>
        <country>United States</country>
        <phone>1 212 854 2487</phone>
        <email>venkat@columbia.edu</email>
      </address>  
      <xref rid="aff3" ref-type="aff">3</xref>
      <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-4923-0582</ext-link></contrib>
    </contrib-group>
    <aff id="aff1">
    <sup>1</sup>
    <institution>Fu Foundation School of Engineering and Applied Science</institution>
    <institution>Department of Chemical Engineering</institution>  
    <institution>Columbia University</institution>  
    <addr-line>New York, NY</addr-line>
    <country>United States</country></aff>
    <aff id="aff2">
    <sup>2</sup>
    <institution>Mailman School of Public Health</institution>
    <institution>Department of Epidemiology</institution>  
    <institution>Columbia University</institution>  
    <addr-line>New York, NY</addr-line>
    <country>United States</country></aff>
    <aff id="aff3">
    <sup>3</sup>
    <institution>Center for the Management of Systemic Risk</institution>
    <institution>Columbia University</institution>  
    <addr-line>New York, NY</addr-line>
    <country>United States</country></aff>
    <author-notes>
      <corresp>Corresponding Author: Venkat Venkatasubramanian 
      <email>venkat@columbia.edu</email></corresp>
    </author-notes>
    <pub-date pub-type="collection"><month>10</month><year>2017</year></pub-date>
    <pub-date pub-type="epub">
      <day>11</day>
      <month>10</month>
      <year>2017</year>
    </pub-date>
    <volume>6</volume>
    <issue>10</issue>
    <elocation-id>e196</elocation-id>
    <!--history from ojs - api-xml-->
    <history>
      <date date-type="received">
        <day>5</day>
        <month>5</month>
        <year>2017</year>
      </date>
      <date date-type="rev-request">
        <day>30</day>
        <month>5</month>
        <year>2017</year>
      </date>
      <date date-type="rev-recd">
        <day>19</day>
        <month>7</month>
        <year>2017</year>
      </date>
      <date date-type="accepted">
        <day>11</day>
        <month>9</month>
        <year>2017</year>
      </date>
    </history>
    <!--(c) the authors - correct author names and publication date here if necessary. Date in form ', dd.mm.yyyy' after jmir.org-->
    <copyright-statement>©Zhizun Zhang, Mila C Gonzalez, Stephen S Morse, Venkat Venkatasubramanian. Originally published in JMIR Research Protocols (http://www.researchprotocols.org), 11.10.2017.</copyright-statement>
    <copyright-year>2017</copyright-year>
    <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
      <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Research Protocols, is properly cited. The complete bibliographic information, a link to the original publication on http://www.researchprotocols.org, as well as this copyright and license information must be included.</p>
    </license>  
    <self-uri xlink:href="http://www.researchprotocols.org/2017/10/e196/" xlink:type="simple"/>
    <abstract>
      <sec sec-type="background">
        <title>Background</title>
        <p>There are increasing concerns about our preparedness and timely coordinated response across the globe to cope with emerging infectious diseases (EIDs). This poses practical challenges that require exploiting novel knowledge management approaches effectively.</p>
      </sec>
      <sec sec-type="objective">
        <title>Objective</title>
        <p>This work aims to develop an ontology-driven knowledge management framework that addresses the existing challenges in sharing and reusing public health knowledge.</p>
      </sec>
      <sec sec-type="methods">
        <title>Methods</title>
        <p>We propose a systems engineering-inspired ontology-driven knowledge management approach. It decomposes public health knowledge into concepts and relations and organizes the elements of knowledge based on the teleological functions. Both knowledge and semantic rules are stored in an ontology and retrieved to answer queries regarding EID preparedness and response.</p>
      </sec>
      <sec sec-type="results">
        <title>Results</title>
        <p>A hybrid concept extraction was implemented in this work. The quality of the ontology was evaluated using the formal evaluation method Ontology Quality Evaluation Framework.</p>
      </sec>
      <sec sec-type="conclusions">
        <title>Conclusions</title>
        <p>Our approach is a potentially effective methodology for managing public health knowledge. Accuracy and comprehensiveness of the ontology can be improved as more knowledge is stored. In the future, a survey will be conducted to collect queries from public health practitioners. The reasoning capacity of the ontology will be evaluated using the queries and hypothetical outbreaks. We suggest the importance of developing a knowledge sharing standard like the Gene Ontology for the public health domain.</p>
      </sec>
    </abstract>
    <kwd-group>
      <kwd>EIDs</kwd>
      <kwd>public health</kwd>
      <kwd>systems engineering</kwd>
      <kwd>knowledge representation</kwd>
      <kwd>teleological function</kwd>
      <kwd>knowledge management</kwd>
      <kwd>ontology</kwd>
      <kwd>semantic reasoning</kwd>
    </kwd-group></article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The 2014 Ebola epidemic in West Africa reminded the public health community again of the weaknesses in preparing for and responding to emerging infectious diseases (EIDs). The epidemic directly affected the health and economies of multiple countries in West Africa for 2 years and resulted in 11,299 deaths among 28,599 suspected infections [<xref ref-type="bibr" rid="ref1">1</xref>]. The initial international response was regarded as slow and uncoordinated by many experts [<xref ref-type="bibr" rid="ref2">2</xref>], an indication of the poor application of the lessons learned from prior global pandemics.</p>
      <p>Effective coordination and communication of information among different stakeholders are necessary components of a strong response to an EID outbreak [<xref ref-type="bibr" rid="ref3">3</xref>]. Public health coordination and communication requires not only sharing resources and specialties but also sharing, managing, and using knowledge effectively. This is a recognized challenge in practice [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. Knowledge sharing and management is not a single government task. It needs the collaboration of multiple groups across several sectors. Such effort, however, is usually hindered by geographical, temporal, and political constraints. Lack of a strong public health infrastructure in many countries and the persistent problems in our global health governance structure could exacerbate the crisis and complicate the collaboration [<xref ref-type="bibr" rid="ref4">4</xref>]. The spatial-temporal dynamics of outbreaks further complicate the real-time preparedness and response processes [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. Moreover, how to use the knowledge from prior pandemics to make a prompt decision under current conditions perplexes the public health community.</p>
      <p>Different approaches have been employed to address this challenge. Recent progress includes influenza information management [<xref ref-type="bibr" rid="ref12">12</xref>], public health meta-knowledge analysis [<xref ref-type="bibr" rid="ref13">13</xref>], and public health surveillance [<xref ref-type="bibr" rid="ref14">14</xref>]. Semantic reasoning has been used to address the spatial-temporal difficulties of epidemic management [<xref ref-type="bibr" rid="ref9">9</xref>]. However, advances in the knowledge management of public health have been limited. In this work, we demonstrate how to apply systems engineering concepts to develop a knowledge management framework facilitated by ontology and semantic reasoning.</p>
      <p>The public health system is a complex adaptive system [<xref ref-type="bibr" rid="ref6">6</xref>]. We can tackle its complexity using a systems engineering–based approach [<xref ref-type="bibr" rid="ref15">15</xref>]. Systems engineering, first proposed by Bell Telephone Laboratories in the 1940s [<xref ref-type="bibr" rid="ref16">16</xref>], describes an interdisciplinary engineering methodology that focuses on how to design and manage complex systems. It emphasizes the joint effect of system components, their dynamical interactions, and the environment. Systems engineering promotes the development of risk management in various industries, including aerospace, defense, chemical, and nuclear. Venkatasubramanian [<xref ref-type="bibr" rid="ref17">17</xref>] discusses the necessity of the systems engineering idea for risk management in a complex system. Leveson [<xref ref-type="bibr" rid="ref18">18</xref>] develops a systems engineering–based modeling framework to assess risks of engineered systems. There are other similar efforts in different domains [<xref ref-type="bibr" rid="ref19">19</xref>-<xref ref-type="bibr" rid="ref21">21</xref>]. EID preparedness and response resemble risk management in many engineering disciplines. Recently, systems engineering concepts have gained considerable attention in the public health community. The National Academy of Engineering and the Institute of Medicine have advocated the widespread application of systems engineering tools [<xref ref-type="bibr" rid="ref22">22</xref>]. Systems engineering methods such as Markov models are used to enhance public health preparedness [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      <p>As a result, we propose a novel systems engineering–inspired, ontology-driven knowledge management approach. In this work, we demonstrate how to develop the ontology and semantic rules to manage knowledge and support decision making. This ontology could also serve as a part of other applications, such as a public health training or practice tool. Its flexibility enables the integration with other ontologies.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overall Architecture</title>
        <p>Public health knowledge management aims to systematically manage tasks and support decision making, which view implicit and explicit knowledge as key strategic resources [<xref ref-type="bibr" rid="ref24">24</xref>]. Knowledge management needs storage, retrieval, and utilization of public health knowledge. We propose the ontology-driven knowledge management approach as shown in <xref ref-type="fig" rid="figure1">Figure 1</xref>, which decomposes public health documents to elements of knowledge and stores them in an ontology, namely, the Public Health Document Ontology (OntoPH). OntoPH was developed using ontology competency questions as guidance. Grüninger and Fox [<xref ref-type="bibr" rid="ref25">25</xref>] state that an ontology should answer competency questions proposed based on the motivation of the ontology. Competency questions define the terminology and specify the definitions and constraints of the terminology. Knowledge is modeled using the terminology and retrieved via semantic rules. An inference engine accesses knowledge models and assembles and manipulates elements of knowledge in the ontology to draw conclusions about EID preparedness and response.</p>
        <p>Public health knowledge is mainly preserved in public health documents, which include guidelines, procedures, and academic publications. They are the most important media to share, store, and manage knowledge because they are vetted, high-quality, generated by an authoritative content source, verifiable by a trusted source, and up to date and regularly updated [<xref ref-type="bibr" rid="ref5">5</xref>]. In order to support decision making, OntoPH’s corpus should meet at least 2 requirements: breadth and depth. Breadth means the corpus should cover many, if not all, fields that are involved in public health decision making. Depth means the corpus should contain not only global-level guidelines but also local-level procedures.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Systems engineering inspired ontology-driven knowledge management approach.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig1.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Function-Based Knowledge Representation</title>
        <p>The first task is to represent knowledge preserved in public health documents. Effective knowledge storage and retrieval requires a knowledge representation, which addresses both hierarchical complexity and semantic heterogeneity. The hierarchical complexity of public health knowledge is rooted in the multiple layers of public health activities. Public health practitioners need different chunks of knowledge in various contexts to prepare for and respond to EIDs. Health workers in the clinic, for example, demand knowledge about disease diagnosis, whereas the department of health wants to know how to manage and coordinate. Knowledge always serves some purposes. The health workers’ knowledge leads to accurate diagnoses. The department of health’s knowledge achieves effective emergency response. Multiple layers of public health activities are linked via their purposes. For example, to better respond to emergencies, departments of health require the health workers to diagnose diseases more effectively.</p>
        <p>Semantic heterogeneity, on the other hand, is the result of the cross-reference of public health knowledge, which is a mixture of various fields such as medical science, epidemiology, biology, and engineering [<xref ref-type="bibr" rid="ref8">8</xref>]. For instance, the knowledge of physician training lies in the intersection of medical science (ie, what skills to train) and management science (ie, how to train). Nonetheless, the 2 aspects share the same purpose (ie, training physicians for better EID preparedness). A recent study by Venkatasubramanian and Zhang [<xref ref-type="bibr" rid="ref26">26</xref>] finds that complex system activities usually have 4 common purposes: communication, decision making, processing, and sensing. Training, as part of education, is an important type of implementation activities.</p>
        <p>One can resolve both hierarchical complexity and semantic heterogeneity by identifying the purpose of knowledge, for a piece of knowledge could serve different purposes under different conditions. Venkatasubramanian and Zhang [<xref ref-type="bibr" rid="ref26">26</xref>] identify the importance of means-end relation in complex system risk management and propose a systems engineering framework to explicate the relation. Adopting this idea, our approach models elements of knowledge based on their means-end relations. We use teleological functions to represent the purposes of knowledge elements. Unlike mathematical functions that map a set of inputs onto a set of permissible outputs, teleological functions emphasize the means to realize a goal by indicating the common purpose between 2 connected entities. The 4 common purposes induce 4 types of teleological functions. A function-based knowledge representation has been used in many fields including engineering [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref30">30</xref>] and data science [<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        <p>To develop such a function-based knowledge representation, we first classify public health documents into 2 categories, general documents that contain general public health principles and specific documents that store evidence-based procedures. There exists a gap between the 2 types of documents: general documents are usually too general to implement, whereas specific documents are mostly event-specific thereby limiting their usefulness for new events. We organize knowledge of general documents as a teleological function of that of specific documents: <italic>knowledge</italic><sub>general doc</sub>= <italic>f(knowledge</italic><sub>specific doc1</sub>, <italic>knowledge</italic><sub>specific doc2</sub>,...), where <italic>f</italic> is a teleological function. Specific activities expand a general guideline with specific recommendations. For example, since the 2009 influenza A H1N1 pandemic, many specific documents have discussed vaccination preparedness and distribution [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. The World Health Organization (WHO) also has issued general guidelines for vaccination preparation during the pandemic [<xref ref-type="bibr" rid="ref34">34</xref>]. The function vaccination describes activities related to vaccination preparedness and distribution. Therefore, the equation can be rewritten as <italic>knowledge</italic><sub>[<xref ref-type="bibr" rid="ref34">34</xref>]</sub> = <italic>vaccination</italic> (<italic>knowledge</italic><sub>[<xref ref-type="bibr" rid="ref32">32</xref>]</sub>, <italic>knowledge</italic><sub>[<xref ref-type="bibr" rid="ref33">33</xref>]</sub>), meaning that WHO guidelines about vaccination can be expanded with specific activities and, hence, bridge the gap. The function-based knowledge representation is depicted as a tree structure shown in <xref ref-type="fig" rid="figure2">Figure 2</xref>. The root of the tree is a public health document, and the leaves are the event-based procedures. A general document (eg, g1) contains general knowledge expressions (eg, ge1.1 and ge1.2). A general knowledge expression specifies a teleological function. For instance, the WHO guideline [<xref ref-type="bibr" rid="ref34">34</xref>] points out roles of the health and nonhealth sectors in vaccination sharing and distribution activities. We can label this knowledge expression with a function vaccination (eg, f2). Specific guidelines (eg, s2) elaborate the teleological functions and define many specific knowledge expressions (eg, se1.2). Specific knowledge expressions can further indicate subfunctions (eg, sf1.2), which include detailed procedures and instructions. Unlike specific procedures, teleological functions are event independent. The same functions can apply to different events with similar fundamental lessons. The tree structure demonstrates how general documents and specific documents are linked via teleological functions. The function-based knowledge representation handles the hierarchical complexity through the tree structure of documents and manages the semantic heterogeneity by grouping distinct activities under the same function. Teleological functions define the scope and intention of the specific documents. They let a specific document elaborate a general document by adding actionable items.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>The tree structure of function-based knowledge.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig2.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Ontology Development</title>
        <sec>
          <title>Background</title>
          <p>An ontology is a formal description of entities and their properties, relationships, and constraints [<xref ref-type="bibr" rid="ref25">25</xref>]. It is widely used for the information system and knowledge management. An ontology consists of classes, individuals, and properties. Classes are a collection of concepts in the domain of discourse. Individuals are instances of each class. Properties are relations between classes, values restrictions, or instance descriptions in the domain of discourse. An ontology models knowledge by axiomatizing concepts as well as the relationships between them [<xref ref-type="bibr" rid="ref35">35</xref>]. Knowledge is defined and organized in a layer style (see <xref ref-type="app" rid="app1">Multimedia Appendix 1</xref>). Terms with similar meanings are classified as synonyms. A list of synonyms is defined as a concept. Concepts form a hierarchy and are connected by relations. Concepts and relations constitute general axioms that represent the knowledge of discourse. <xref ref-type="fig" rid="figure3">Figure 3</xref> shows the ontology development process, which consists of 3 steps: (1) concept extraction: extracting knowledge from the corpus; (2) ontology assembly: decomposing knowledge into terms, relations, constraints, and descriptions, integrating these components to form an ontology; and (3) reasoning: creating semantic rules to enable knowledge retrieval.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Ontology development process.</p>
            </caption>
            <graphic xlink:href="resprot_v6i10e196_fig3.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Concept Extraction</title>
          <p>There are 2 concept extraction methods available: manual annotation and natural language processing (NLP) annotation. Manual annotation requires domain experts to review and annotate every term in the corpus per predefined criteria. Manual annotation provides high accuracy but requires tremendous human effort. On the other hand, NLP annotation automatically recognizes and classifies terms into predefined categories [<xref ref-type="bibr" rid="ref36">36</xref>]. NLP annotation is much more efficient than manual annotation but at the cost of accuracy. Usually, an NLP-based information retrieval performs clustering or classification to identify key concepts. The performance is usually measured by precision or recall [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        </sec>
        <sec>
          <title>Ontology Assembly</title>
          <p>OntoPH includes 199 classes, 78 properties, and 1234 axioms (see <xref ref-type="app" rid="app2">Multimedia Appendices 2</xref>-<xref ref-type="app" rid="app8">8</xref>). We developed the general structure of OntoPH based on the Legal Knowledge Interchange Format (LKIF) core ontology. The LKIF core ontology was developed by the European Project for Standardized Transparent Representations to extend a legal accessibility consortium to cater to a continuing need for a standard vocabulary of basic legal terms [<xref ref-type="bibr" rid="ref38">38</xref>]. We expanded this legal term vocabulary to include public health vocabulary.</p>
          <p>OntoPH is structured in a modularized nature. Modularization improves the reusability, scalability, and maintenance of an ontology [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. OntoPH has 7 modules: space-time, agent, action, role, process, document, and event. Inheriting all modules, OntoPH core ontology has 9 main classes (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>). The space class defines spatial concepts such as region and nation. The time class describes temporal concepts such as time point or period. The resource class specifies resources used for public health preparation and response. The action class defines potential actions for an EID event. Actions are categorized regarding the 4 basic teleological functions: communication, control, implementation, and monitoring [<xref ref-type="bibr" rid="ref26">26</xref>]. Subclasses of the action class represent specific functions under the 4 basic functions. The process class describes both continuous and discrete event flows. The agent class lists all the intelligent and nonintelligent agents involved in a process or an action. The description class describes the state and role of any agent, action, or process. The medium class summarizes different types of public health documents, such as legal or nonbinding documents. Last, the expression class represents the knowledge expressions of the documents.</p>
          <boxed-text id="box1" position="float">
            <title>Ontology main classes and subclasses.</title>
            <p>Action</p>
            <list list-type="bullet">
              <list-item>
                <p>Communication</p>
              </list-item>
              <list-item>
                <p>Control</p>
              </list-item>
              <list-item>
                <p>Implementation</p>
              </list-item>
              <list-item>
                <p>Monitoring</p>
              </list-item>
            </list>
            <p>Agent</p>
            <list list-type="bullet">
              <list-item>
                <p>Animal</p>
              </list-item>
              <list-item>
                <p>Human</p>
              </list-item>
              <list-item>
                <p>Organization</p>
              </list-item>
              <list-item>
                <p>Other agent</p>
              </list-item>
              <list-item>
                <p>Pathogen</p>
              </list-item>
            </list>
            <p>Description</p>
            <list list-type="bullet">
              <list-item>
                <p>Attribute</p>
              </list-item>
              <list-item>
                <p>Role</p>
              </list-item>
            </list>
            <p>Expression</p>
            <list list-type="bullet">
              <list-item>
                <p>Argument</p>
              </list-item>
              <list-item>
                <p>Assertion</p>
              </list-item>
              <list-item>
                <p>Assumption</p>
              </list-item>
              <list-item>
                <p>Declaration</p>
              </list-item>
              <list-item>
                <p>Evaluative proposition</p>
              </list-item>
              <list-item>
                <p>Evidence</p>
              </list-item>
              <list-item>
                <p>Fact</p>
              </list-item>
              <list-item>
                <p>Feedback</p>
              </list-item>
              <list-item>
                <p>Intention</p>
              </list-item>
              <list-item>
                <p>Knowledge</p>
              </list-item>
              <list-item>
                <p>Observation</p>
              </list-item>
              <list-item>
                <p>Qualification</p>
              </list-item>
            </list>
            <p>Medium</p>
            <list list-type="bullet">
              <list-item>
                <p>Document</p>
              </list-item>
              <list-item>
                <p>Sample</p>
              </list-item>
            </list>
            <p>Process</p>
            <list list-type="bullet">
              <list-item>
                <p>Continuous process</p>
              </list-item>
              <list-item>
                <p>Discrete process</p>
              </list-item>
            </list>
            <p>Resource</p>
            <list list-type="bullet">
              <list-item>
                <p>Equipment material</p>
              </list-item>
              <list-item>
                <p>Financial</p>
              </list-item>
              <list-item>
                <p>Human resource</p>
              </list-item>
              <list-item>
                <p>Intellectual tool</p>
              </list-item>
            </list>
            <p>Space</p>
            <list list-type="bullet">
              <list-item>
                <p>Area</p>
              </list-item>
              <list-item>
                <p>Space point</p>
              </list-item>
            </list>
            <p>Time</p>
            <list list-type="bullet">
              <list-item>
                <p>Period</p>
              </list-item>
              <list-item>
                <p>Time point</p>
              </list-item>
            </list>
          </boxed-text>
          <p>OntoPH properties (see <xref ref-type="app" rid="app6">Multimedia Appendices 6</xref> and <xref ref-type="app" rid="app7">7</xref>) define the relationships between classes and subclasses. For instance, participate (<xref ref-type="fig" rid="figure4">Figure 4</xref>) has a domain of role and a range of action, indicating that a role participates in some actions. This property has an inverse of participate_by. OntoPH contains individuals extracted from public health documents. For example, legal_role, a subclass of role, has individuals of emergency committee and public health authority (<xref ref-type="fig" rid="figure5">Figure 5</xref>).</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Protégé screenshot for property participate.</p>
            </caption>
            <graphic xlink:href="resprot_v6i10e196_fig4.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Protégé screenshot for individuals of Legal_role.</p>
            </caption>
            <graphic xlink:href="resprot_v6i10e196_fig5.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
        <title>Semantic Rules and Reasoning</title>
        <p>OntoPH is developed using web ontology language (OWL) under the Protégé environment [<xref ref-type="bibr" rid="ref41">41</xref>]. Logic-based semantic rules allow OWL to “exploit the considerable existing body of logical reasoning to fulfill important logical requirements” [<xref ref-type="bibr" rid="ref42">42</xref>]. They imply answers to the competency questions. OntoPH answers 3 types of questions: (1) the relation between actions and roles, (2) the relation between roles and the condition of interest, and (3) the relation between actions and the condition of interest. OntoPH uses time, space, resource, and process classes to describe the conditions of an EID outbreak. Hence, we can construct the following informal competency questions:</p>
        <list list-type="order">
          <list-item>
            <p>What action must a role perform?</p>
          </list-item>
          <list-item>
            <p>What are the roles specified by an action?</p>
          </list-item>
          <list-item>
            <p>What are the actions required under a condition of interest?</p>
          </list-item>
          <list-item>
            <p>What are the roles specified under a condition of interest?</p>
          </list-item>
        </list>
        <p>Informal competency questions should be translated to a formal format so that an ontology can retrieve the elements of knowledge to answer them [<xref ref-type="bibr" rid="ref25">25</xref>]. We denote <italic>T</italic><sub>ontology</sub> as a set of axioms in the ontology, <italic>G</italic><sub>ground</sub> as a set of ground instances, and <italic>Q</italic> as a first-order sentence using only predicates in the language of <italic>T</italic><sub>ontology</sub>. We can formulate the formal translations for the 4 informal competency questions.</p>
        <list list-type="order">
          <list-item>
            <p>Let <italic>Q(action)</italic> denote a sentence that describes some actions. Given a ground formula <italic>G</italic><sub>role</sub> defining instances of a role, determine the possible actions, as shown in <xref ref-type="fig" rid="figure6">Figure 6</xref>.</p>
          </list-item>
          <list-item>
            <p>Let <italic>Q(role)</italic> denote a sentence that describes some roles. Given a ground formula <italic>G</italic><sub>action</sub> defining instances of an action, determine the possible roles, as shown in <xref ref-type="fig" rid="figure7">Figure 7</xref>.</p>
          </list-item>
          <list-item>
            <p>Let <italic>Q(action)</italic> denote a sentence that describes some actions. Given a ground formula <italic>G</italic><sub>condition</sub> defining instances of a condition, determine the possible actions, as shown in <xref ref-type="fig" rid="figure8">Figure 8</xref>.</p>
          </list-item>
          <list-item>
            <p>Let <italic>Q(role)</italic> denote a sentence that describes some roles. Given a ground formula <italic>G</italic><sub>condition</sub> defining instances of a condition, determine the possible roles, as shown in <xref ref-type="fig" rid="figure9">Figure 9</xref>.</p>
          </list-item>
        </list>  
        <p>Semantic rules link axioms <italic>T</italic> with instances <italic>G</italic> and entail a first-order sentence <italic>Q</italic>, which is the answer to the competency question.</p>
        <p>Semantic rules are created using semantic web rule language (SWRL), a rule language for the semantic web. SWRL rules apply unary predicates for describing classes and data types, binary predicates for properties, and some special built-in n-ary predicates [<xref ref-type="bibr" rid="ref43">43</xref>]. An example SWRL rule is shown in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>.</p>
        <boxed-text id="box2" position="float">
          <title>A simple example of semantic web rule language rule.</title>
          <p>(Person(?x), hasParent(?x,?y), hasParent(?x,?z), hasSpouse(?y,?z) → childOfMarriedParents(?x)</p>
        </boxed-text>
        <p>This rule describes the assertion that someone is a child of married parents. Letters with a question mark (eg, <italic>?x</italic>) denote variables. Person(<italic>?x</italic>) indicates that a variable <italic>x</italic> is a person. The binary relation hasParent(<italic>?x</italic>, <italic>?y</italic>) indicates that person <italic>x</italic> has a parent <italic>y</italic>. The formal formula is shown in <xref ref-type="fig" rid="figure10">Figure 10</xref>, which reads: there exists persons <italic>x</italic>, <italic>y</italic>, and <italic>z</italic>. If <italic>x</italic> has parent <italic>y</italic>, and <italic>x</italic> has parent <italic>z</italic>, and <italic>y</italic> and <italic>z</italic> are spouses, then <italic>x</italic> is a child of married parents. SWRL rules translate natural language assertions into computable forms (<xref ref-type="fig" rid="figure10">Figure 10</xref>).</p>
        <p>We create SWRL rules in 3 steps. First, public health experts review documents and identify knowledge expressions. For example, the WHO Technical Advice for Case Management of Influenza A (H1N1) in Air Transport (WHO Advice Air Transport) [<xref ref-type="bibr" rid="ref44">44</xref>] is a WHO-issued guideline for air transportation case management. It specifies the procedures that the pilot in command should follow when a suspicious case is identified. We identify a knowledge expression pilot_in_command_action under the expression class. Second, public health experts create logic expressions for knowledge expressions. This intermediate step translates a procedure into a formal representation. For example, the pilot_in_command_action can be written as logic expressions, as shown in <xref ref-type="fig" rid="figure11">Figure 11</xref>.</p>
        <p>Logic expressions and natural language are interchangeable. The first expression in <xref ref-type="fig" rid="figure11">Figure 11</xref> shows that WHO Advice Air Transport contains specifications about pilot actions. The pilot in command should report any suspicious activities on the flight. The second expression in <xref ref-type="fig" rid="figure11">Figure 11</xref> shows that WHO Advice Air Transport requires communication between agencies. The public health authority should communicate with other agencies. Third, public health experts work with ontology engineers to develop the SWRL rules based on the logic expressions from step 2. <xref ref-type="boxed-text" rid="box3">Textbox 3</xref> shows the SWRL rule created for the same example. The rule first states the knowledge expression and its parent document. Then, it specifies the roles (Pilot and PH_authority) and the expected actions.</p>
        <boxed-text id="box3" position="float">
          <title>Semantic web rule language rule for the pilot_in_command_action example.</title>
          <p>Guideline(Case_management_H1N1_Airtransport_guidance), Knowledge(Pilot_in_command_actions) → contains(Case_management_H1N1_AirTransport_guidance, Pilot_in_command_actions)</p>
          <p>Nonhealth_sector(Pilot), Reporting(?reporting), contains(Case_management_H1N1_AirTransport_guidance, Pilot_in_command_actions) → participate(Pilot, ?reporting)</p>
          <p>Legal_role(PH_authority), Interactive_network(Communication_between_agencies), contains(Case_management_H1N1_AirTransport_guidance, Pilot_in_command_actions) → participate(PH_authority, Communication_between_agencies)</p>
        </boxed-text>
        <p>Logical inference connects documents with knowledge expressions. An inference process is depicted in <xref ref-type="fig" rid="figure12">Figure 12</xref>. WHO Advice Air Transport carries many knowledge expressions. One of them informs the chief pilot’s actions for an EID emergency during a flight mission. This piece of knowledge then implies that pilots and public health authorities should report suspicious cases and communicate with each other in time.</p>
        <p>Reasoning results are presented per individual. <xref ref-type="fig" rid="figure13">Figure 13</xref> shows the reasoning results of Mayor’s Office of Emergency Management under the department class. Given an individual, we obtain a list of sentences, such as “Mayor’s Office of Emergency Management performs delivery strategy.” These sentences in fact are the elements of knowledge.</p>
        <fig id="figure6" position="float">
          <label>Figure 6</label>
          <caption>
            <p>The formal expression of competency question 1.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig6.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure7" position="float">
          <label>Figure 7</label>
          <caption>
            <p>The formal expression of competency question 2.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig7.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure8" position="float">
          <label>Figure 8</label>
          <caption>
            <p>The formal expression of competency question 3.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig8.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure9" position="float">
          <label>Figure 9</label>
          <caption>
            <p>The formal expression of competency question 4.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig9.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure10" position="float">
          <label>Figure 10</label>
          <caption>
            <p>The formal expression of someone is a child of married parents.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig10.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure11" position="float">
          <label>Figure 11</label>
          <caption>
            <p>The formal expression of pilot in command action.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig11.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure12" position="float">
          <label>Figure 12</label>
          <caption>
            <p>An inference process.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig12.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure13" position="float">
          <label>Figure 13</label>
          <caption>
            <p>Reasoning results for Office_of_Emergency_Management.</p>
          </caption>
          <graphic xlink:href="resprot_v6i10e196_fig13.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig></sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Concept Extraction Results</title>
        <p>The corpus, with 135,946 words in total, consists of the US Code [<xref ref-type="bibr" rid="ref45">45</xref>], federal level regulations [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>], international health regulations [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>], and pandemic evaluations of outbreak responses [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. They cover all types of public health documents aforementioned. The US Code is the generic legal document, which ensures that the ontology aligns with laws. The federal regulations and the international health regulations are guidelines regarding surveillance, transportation, and preparedness. The evaluations are chosen per disease. H1N1 and West Nile Virus are 2 specific diseases chosen for illustration. These 2 cases were selected because they are well-studied recent emerging diseases with an impact on health resources both locally and globally. In addition, their impacts on health and geographical coverage are both significant. We wanted to evaluate case examples where the primary infection risk is associated with different infection transmission routes in order to evaluate the potential for having a unified framework for EIDs.</p>
        <p>We implemented a hybrid concept extraction approach. NLP methods are used to preprocess the corpus. By removing stop words and tagging the parts of speech, one can extract meaningful and most frequent terms and relations using text mining tools like KHCoder [<xref ref-type="bibr" rid="ref52">52</xref>]. The classification work is done manually with 2 domain experts reviewing every term and relation and deciding their descriptions and constraints. OntoPH is built upon these terms and relations. Domain experts and ontology engineers work collaboratively to select and annotate documents. Such a team-based method has been used extensively in many scientific studies and applications, such as hazard and operability analysis in chemical engineering [<xref ref-type="bibr" rid="ref53">53</xref>]. Such a team should be as small as possible while maintaining sufficient expertise. In a series of meetings, team members work together to select documents. Conflicts must be resolved before the list of documents is finalized. Each domain expert annotates a part of the corpus and reviews others’ annotations. This practice, therefore, keeps the corpus and annotation as objective as possible.</p>
      </sec>
      <sec>
        <title>Ontology Evaluation</title>
        <p>The quality of ontology is critical. It affects not only the quality of reasoning results but also the effectiveness of the application. Ontology can be evaluated on many aspects, namely, vocabulary, syntax, structure, semantics, representation, and context [<xref ref-type="bibr" rid="ref24">24</xref>]. Extensive research has been conducted to formally evaluate the quality of ontologies [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref54">54</xref>-<xref ref-type="bibr" rid="ref57">57</xref>]. Among these methods, we follow the Ontology Quality Evaluation Framework (OQuaRE) approach [<xref ref-type="bibr" rid="ref55">55</xref>], which adapts the International Organization for Standardization standards for Software Quality Requirements and Evaluation. OQuaRE assesses 6 characteristics and 39 subcharacteristics of an ontology using quality metrics. Quality metrics are composed of primitive and derived measurements. Primitive measurements are metrics that can be measured directly on the ontology, such as number of classes, number of relations, etc. Derived measurements are combinations of some primitive ones [<xref ref-type="bibr" rid="ref55">55</xref>]. With a scale of 1 to 5 (1=not acceptable and 5=exceeds the requirement), it rates every aspect of an ontology. The final score is the arithmetic average of individual scores of all characteristics. The details of this method can be found in Duque-Ramos et al [<xref ref-type="bibr" rid="ref55">55</xref>]. We include 30 out of the 39 subcharacteristics in our evaluation. The other 9 subcharacteristics, which require expert subjective assessment, are excluded. The evaluation results of the OntoPH core ontology are presented in <xref ref-type="table" rid="table1">Table 1</xref>. The evaluation indicates that the OntoPH core ontology is satisfactory, with an average score of 4. Problems have been found on redundancy and controlled vocabulary, mainly due to the relatively small corpus size.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Ontology evaluation results.</p>
          </caption>
          <table width="500" cellpadding="7" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="150"/>
            <col width="240"/>
            <col width="100"/>
            <thead>
              <tr valign="top">
                <td>Characteristics</td>
                <td>Subcharacteristics</td>
                <td>OQuaRE score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td><bold>Structural</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Formalization</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Formal relations support</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Redundancy</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Consistency</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Tangledness</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Cycles</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Cohesion</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Domain coverage</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><bold>Functional adequacy</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Controlled vocabulary</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Schema and value reconciliation</td>
                <td>4.67</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Consistent search and query</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Knowledge acquisition representation</td>
                <td>3.67</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Clustering</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Similarity</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Indexing and linking</td>
                <td>4.5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Results representation</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Text analysis</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Guidance</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Decision trees</td>
                <td>4.5</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Knowledge reuse</td>
                <td>4.28</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Inference</td>
                <td>4.67</td>
              </tr>
              <tr valign="top">
                <td><bold>Compatibility</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Replaceability</td>
                <td>3.5</td>
              </tr>
              <tr valign="top">
                <td><bold>Transferability</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Adaptability</td>
                <td>3.5</td>
              </tr>
              <tr valign="top">
                <td><bold>Operability</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Learnability</td>
                <td>4.17</td>
              </tr>
              <tr valign="top">
                <td><bold>Maintainability</bold></td>
                <td><break/></td>
                <td><break/></td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Modularity</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Reusability</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Analyzability</td>
                <td>3.8</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Changeability</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Modification stability</td>
                <td>4.2</td>
              </tr>
              <tr valign="top">
                <td><break/></td>
                <td>Testability</td>
                <td>3.8</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The possibility of using ontology and semantic reasoning in public health decision making has been recognized in literature [<xref ref-type="bibr" rid="ref58">58</xref>]. In this work, we adapt this idea and our previous experience in knowledge management in the pharmaceutical industry [<xref ref-type="bibr" rid="ref59">59</xref>] to derive a detailed methodology on how to develop such a tool. We introduce the systems engineering–inspired ontology-driven framework for public health knowledge management. We demonstrate how complex and heterogeneous public health knowledge can be modeled and stored in an ontology. Previous work has focused on local activities, such as activities within a health care network [<xref ref-type="bibr" rid="ref60">60</xref>]. OntoPH extends the scope from local level to global/national level by focusing on general documents.</p>
        <p>OntoPH’s strength is threefold. First, it stores public health documents knowledge as classes, relations, and instances. Public health documents, including guidelines, procedures, and academic publications, are important sources of knowledge. Even though medical records, geographic information system data, and disease information have been studied and stored in ontologies [<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref61">61</xref>], to our knowledge, there is no ontology for public health documents. OntoPH provides this missing piece of public health knowledge management. Second, we present a flexible knowledge management framework. OntoPH implements a modularized structure, which ensures its extensibility. For example, the space-time module can be extended using time ontologies [<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref62">62</xref>] and World Wide Web Consortium spatial ontologies [<xref ref-type="bibr" rid="ref63">63</xref>]. It is also possible to add new modules. If disease information is needed, we can create a new disease module, which inherits the disease ontology [<xref ref-type="bibr" rid="ref61">61</xref>]. This modularized structure makes OntoPH a potential generic public health knowledge center. Third, OntoPH can manage the hierarchical complexity and heterogeneity of public health knowledge. Elements of knowledge are effectively organized by the teleological functions that highlight the means-end relations.</p>
        <p>This framework is most useful in low- and middle-income countries (LMICs). Lack of resources and public health experts in LMICs usually makes a knowledge management system difficult to implement. Nonetheless, OntoPH’s general knowledge is widely applicable. By expanding the data sources to include LMIC-specific knowledge [<xref ref-type="bibr" rid="ref64">64</xref>] and connecting with other ontologies [<xref ref-type="bibr" rid="ref61">61</xref>-<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref65">65</xref>], OntoPH would become a useful tool to help LMICs respond to an outbreak quickly, both at the national and local levels.</p>
        <p>Potentially, OntoPH can support decision making by answering user queries. For example, given an outbreak scenario, a user could list questions regarding disease identification, transmission prevention, disease control, and risk mitigation. With enough prestored knowledge, OntoPH could answer the list of questions by producing logical assertions with respect to each question.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>At this stage, however, there are some limitations. First, the training document corpus is relatively small. Only 5 general documents and 7 specific documents are prestored due to the manual annotation constraint. It will require a concerted effort to annotate and develop a more extensive public health knowledge base for widespread application. Nonetheless, the current corpus is comprehensive enough for proof of concept. Second, the selection of documents is subjective. When the corpus size is small, the accuracy of reasoning results is dependent on the document selection rather than the knowledge base. Increasing the size of the corpus and precise query statement will improve reasoning accuracy in general. In addition, rule-based reasoning has its intrinsic limitations—semantic rules are subjective. SWRL rules rarely allow ternary relations, and that limits the power of the SWRL representation. Third, the current framework is restricted to public health documents, which lack information from various data sources, such as geographic information system data, news articles, social media feeds, etc. This limits OntoPH’s real-time usage. Moreover, current knowledge representation would not be able to capture knowledge in research articles that do not fit in the knowledge model. However, the basic and domain ontologies, such as space-time, resource, role, and agent modules, contain fundamental public health knowledge, therefore, making the knowledge framework extendable to cover research articles. This, of course, requires further study of new knowledge representation. Potentially, a research article knowledge expression module could be developed and incorporated into OntoPH.</p>
      </sec>
      <sec>
        <title>Future Work</title>
        <p>Future work will address the limitations and evaluate OntoPH’s reasoning capacity. Adopting artificial intelligence techniques would significantly reduce the human effort, and, thus, get rid of many of the limitations. Specifically, a term extraction module implementing NLP techniques such as topic modeling would enable automated concept classification of public health documents, reducing the amount of work required for annotation. Enriching data sources will improve OntoPH’s ability for real-time response. We plan to expand the corpus incorporating expert opinions. A survey for eliciting expert feedback on what to include in the corpus will be conducted. A systematic literature review on effectiveness of policy and interventions could help us determine what documents to include.</p>
        <p>To evaluate this method, we will collect a list of general queries regarding general EID preparedness and response from public health experts and practitioners. Moreover, we will test OntoPH’s reasoning capacity on hypothetical outbreaks. These full-scale case studies will provide us with valuable information on how to improve the usage and accuracy of OntoPH decision support.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>In recent decades, many EID outbreaks and epidemics have resulted in considerable human disability and mortality, in part due to ineffective coordination or slow response at the start of the outbreak. Responding to EID outbreaks is intrinsically challenging due to the uncertainties associated with EIDs, specifically level of risk and potential for impact of its spread in a population. During an outbreak, evidence-based public health policies developed by public health authorities, legislators, and other government officials facilitate the implementation of a strong public health response. However, there are structural and political forces that prevent decision makers from making evidence-based policies in response to outbreaks. Therefore, it is necessary to have in place a mechanism to easily identify evidence in order to evaluate the consequences of public health or policy actions recommended to address these public health emergencies. An ontology framework for public health outbreak response will cut the time spent aggregating expert opinions during the initial stages of an outbreak. It would also assist public health administrators and government officials on next steps based on individual- and systems-level factors associated with the outbreak.</p>
        <p>Our approach is a potentially effective methodology for EID preparedness and response. It manages complex knowledge via a function-based knowledge representation. It introduces a systematic way of storing, retrieving, and using public health knowledge. Accuracy and comprehensiveness of the ontology can be improved as more knowledge is stored. We advocate the public health community work toward the goal of developing a Gene Ontology-like [<xref ref-type="bibr" rid="ref66">66</xref>] knowledge sharing standard. OntoPH demonstrates the possibility of knowledge management for EID emergency preparedness and response.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <app id="app1">
        <title>Multimedia Appendix 1</title>
        <p>Ontology layer representation (Adapted from Cimiano [<xref ref-type="bibr" rid="ref35">35</xref>]).</p>
        <media xlink:href="resprot_v6i10e196_app1.png" xlink:title="PNG File, 225KB"/>
      </app>
      <app id="app2">
        <title>Multimedia Appendix 2</title>
        <p>Ontology classes part 1.</p>
        <media xlink:href="resprot_v6i10e196_app2.png" xlink:title="PNG File, 34KB"/>
      </app>
      <app id="app3">
        <title>Multimedia Appendix 3</title>
        <p>Ontology classes part 2.</p>
        <media xlink:href="resprot_v6i10e196_app3.png" xlink:title="PNG File, 25KB"/>
      </app>
      <app id="app4">
        <title>Multimedia Appendix 4</title>
        <p>Ontology classes part 3.</p>
        <media xlink:href="resprot_v6i10e196_app4.png" xlink:title="PNG File, 25KB"/>
      </app>
      <app id="app5">
        <title>Multimedia Appendix 5</title>
        <p>Ontology classes part 4.</p>
        <media xlink:href="resprot_v6i10e196_app5.png" xlink:title="PNG File, 26KB"/>
      </app>
      <app id="app6">
        <title>Multimedia Appendix 6</title>
        <p>Ontology properties part 1.</p>
        <media xlink:href="resprot_v6i10e196_app6.png" xlink:title="PNG File, 18KB"/>
      </app>
      <app id="app7">
        <title>Multimedia Appendix 7</title>
        <p>Ontology properties part 2.</p>
        <media xlink:href="resprot_v6i10e196_app7.png" xlink:title="PNG File, 16KB"/>
      </app>
      <app id="app8">
        <title>Multimedia Appendix 8</title>
        <p>Ontology individuals (selected).</p>
        <media xlink:href="resprot_v6i10e196_app8.png" xlink:title="PNG File, 30KB"/>
      </app>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EID</term>
          <def>
            <p>emerging infectious disease</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">LKIF</term>
          <def>
            <p>Legal Knowledge Interchange Format</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">OntoPH</term>
          <def>
            <p>Public Health Document Ontology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">OQuaRE</term>
          <def>
            <p>Ontology Quality Evaluation Framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">OWL</term>
          <def>
            <p>web ontology language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">SWRL</term>
          <def>
            <p>semantic web rule language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">WHO</term>
          <def>
            <p>World Health Organization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">LMIC</term>
          <def>
            <p>low- and middle-income country</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>We would like to thank Dr Yu Luo for his constructive comments on ontology design. ZZ, MG, SM, and VV designed the research; ZZ and MG built the ontology; ZZ and MG developed the semantic rules; and ZZ wrote the manuscript with the input of MG and VV. This work is supported in part by Columbia University and the Center for the Management of Systemic Risk.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>World Health Organization</collab>
        </person-group>
        <source>Ebola Data and Statistics</source>  
        <year>2015</year>  
        <access-date>2016-01-15</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://apps.who.int/gho/data/view.ebola-sitrep.ebola-summary-20151112?lang=en">http://apps.who.int/gho/data/view.ebola-sitrep.ebola-summary-20151112?lang=en</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6dcsyw2bN"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Tomori</surname>
            <given-names>O</given-names>
          </name>
        </person-group>
        <article-title>Will Africa's future epidemic ride on forgotten lessons from the Ebola epidemic?</article-title>
        <source>BMC Med</source>  
        <year>2015</year>  
        <month>05</month>  
        <day>14</day>  
        <volume>13</volume>  
        <fpage>116</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-015-0359-7"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1186/s12916-015-0359-7</pub-id>
        <pub-id pub-id-type="medline">25976420</pub-id>
        <pub-id pub-id-type="pii">10.1186/s12916-015-0359-7</pub-id>
        <pub-id pub-id-type="pmcid">PMC4432500</pub-id></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Stoto</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Nelson</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Higdon</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Kraemer</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Hites</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Singleton</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>Lessons about the state and local public health system response to the 2009 H1N1 pandemic: a workshop summary</article-title>
        <source>J Public Health Manag Pract</source>  
        <year>2013</year>  
        <volume>19</volume>  
        <issue>5</issue>  
        <fpage>428</fpage>  
        <lpage>435</lpage>  
        <pub-id pub-id-type="doi">10.1097/PHH.0b013e3182751d3e</pub-id>
        <pub-id pub-id-type="medline">23892378</pub-id>
        <pub-id pub-id-type="pii">00124784-201309000-00006</pub-id></nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Oshitani</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Kamigaki</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Suzuki</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Major issues and challenges of influenza pandemic preparedness in developing countries</article-title>
        <source>Emerg Infect Dis</source>  
        <year>2008</year>  
        <volume>14</volume>  
        <issue>6</issue>  
        <fpage>0839</fpage> </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Revere</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Turner</surname>
            <given-names>AM</given-names>
          </name>
          <name name-style="western">
            <surname>Madhavan</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rambo</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Bugni</surname>
            <given-names>PF</given-names>
          </name>
          <name name-style="western">
            <surname>Kimball</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Fuller</surname>
            <given-names>SS</given-names>
          </name>
        </person-group>
        <article-title>Understanding the information needs of public health practitioners: a literature review to inform design of an interactive digital knowledge management system</article-title>
        <source>J Biomed Inform</source>  
        <year>2007</year>  
        <month>08</month>  
        <volume>40</volume>  
        <issue>4</issue>  
        <fpage>410</fpage>  
        <lpage>421</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.jbi.2006.12.008"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2006.12.008</pub-id>
        <pub-id pub-id-type="medline">17324632</pub-id>
        <pub-id pub-id-type="pii">S1532-0464(07)00002-0</pub-id></nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bloom</surname>
            <given-names>B</given-names>
          </name>
        </person-group>
        <article-title>Crossing the quality chasm: a new health system for the 21st century</article-title>
        <source>JAMA</source>  
        <year>2002</year>  
        <volume>287</volume>  
        <issue>5</issue>  
        <fpage>646</fpage>  
        <lpage>647</lpage> </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>LaPelle</surname>
            <given-names>NR</given-names>
          </name>
          <name name-style="western">
            <surname>Luckmann</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Simpson</surname>
            <given-names>EH</given-names>
          </name>
          <name name-style="western">
            <surname>Martin</surname>
            <given-names>ER</given-names>
          </name>
        </person-group>
        <article-title>Identifying strategies to improve access to credible and relevant information for public health professionals: a qualitative study</article-title>
        <source>BMC Public Health</source>  
        <year>2006</year>  
        <month>04</month>  
        <day>05</day>  
        <volume>6</volume>  
        <fpage>89</fpage>  
        <pub-id pub-id-type="doi">10.1186/1471-2458-6-89</pub-id>
        <pub-id pub-id-type="medline">16597331</pub-id>
        <pub-id pub-id-type="pii">1471-2458-6-89</pub-id>
        <pub-id pub-id-type="pmcid">PMC1456961</pub-id></nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ho</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Peter</surname>
            <given-names>WWP</given-names>
          </name>
        </person-group>
        <article-title>Harnessing the social web for health and wellness: issues for research and knowledge translation</article-title>
        <source>J Med Internet Res</source>  
        <year>2014</year>  
        <volume>16</volume>  
        <issue>2</issue>  
        <fpage>e34</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.jmir.org/2014/2/e34/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/jmir.2969</pub-id>
        <pub-id pub-id-type="medline">24518432</pub-id>
        <pub-id pub-id-type="pii">v16i2e34</pub-id>
        <pub-id pub-id-type="pmcid">PMC3936299</pub-id></nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Li</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Mackaness</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <article-title>A multi-agent-based, semantic-driven system for decision support in epidemic management</article-title>
        <source>Health Inform J</source>  
        <year>2015</year>  
        <volume>21</volume>  
        <issue>3</issue>  
        <fpage>195</fpage>  
        <lpage>208</lpage>  
        <pub-id pub-id-type="medline">24448277</pub-id></nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ostfeld</surname>
            <given-names>RS</given-names>
          </name>
          <name name-style="western">
            <surname>Glass</surname>
            <given-names>GE</given-names>
          </name>
          <name name-style="western">
            <surname>Keesing</surname>
            <given-names>F</given-names>
          </name>
        </person-group>
        <article-title>Spatial epidemiology: an emerging (or re-emerging) discipline</article-title>
        <source>Trends Ecol Evol</source>  
        <year>2005</year>  
        <month>06</month>  
        <volume>20</volume>  
        <issue>6</issue>  
        <fpage>328</fpage>  
        <lpage>336</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.tree.2005.03.009</pub-id>
        <pub-id pub-id-type="medline">16701389</pub-id>
        <pub-id pub-id-type="pii">S0169-5347(05)00071-6</pub-id></nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Mao</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Bian</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Spatial-temporal transmission of influenza and its health risks in an urbanized area</article-title>
        <source>Comp Environ Urban Syst</source>  
        <year>2010</year>  
        <volume>34</volume>  
        <issue>3</issue>  
        <fpage>204</fpage>  
        <lpage>215</lpage> </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Keselman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rosemblat</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Kilicoglu</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Fiszman</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Jin</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Shin</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Rindflesch</surname>
            <given-names>TC</given-names>
          </name>
        </person-group>
        <article-title>Adapting semantic natural language processing technology to address information overload in influenza epidemic management</article-title>
        <source>J Am Soc Inf Sci Technol</source>  
        <year>2010</year>  
        <month>12</month>  
        <day>01</day>  
        <volume>61</volume>  
        <issue>12</issue>  
        <fpage>2531</fpage>  
        <lpage>2543</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24311971"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1002/asi.21414</pub-id>
        <pub-id pub-id-type="medline">24311971</pub-id>
        <pub-id pub-id-type="pmcid">PMC3847910</pub-id></nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Trinquart</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Galea</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Mapping epidemiology's past to inform its future: metaknowledge analysis of epidemiologic topics in leading journals, 1974-2013</article-title>
        <source>Am J Epidemiol</source>  
        <year>2015</year>  
        <month>07</month>  
        <day>15</day>  
        <volume>182</volume>  
        <issue>2</issue>  
        <fpage>93</fpage>  
        <lpage>104</lpage>  
        <pub-id pub-id-type="doi">10.1093/aje/kwv034</pub-id>
        <pub-id pub-id-type="medline">25977517</pub-id>
        <pub-id pub-id-type="pii">kwv034</pub-id></nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Neill</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>New directions in artificial intelligence for public health surveillance</article-title>
        <source>IEEE Intel Sys</source>  
        <year>2012</year>  
        <volume>27</volume>  
        <issue>1</issue>  
        <fpage>56</fpage>  
        <lpage>59</lpage> </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Trochim</surname>
            <given-names>WM</given-names>
          </name>
          <name name-style="western">
            <surname>Cabrera</surname>
            <given-names>DA</given-names>
          </name>
          <name name-style="western">
            <surname>Milstein</surname>
            <given-names>B</given-names>
          </name>
          <name name-style="western">
            <surname>Gallagher</surname>
            <given-names>RS</given-names>
          </name>
          <name name-style="western">
            <surname>Leischow</surname>
            <given-names>SJ</given-names>
          </name>
        </person-group>
        <article-title>Practical challenges of systems thinking and modeling in public health</article-title>
        <source>Am J Public Health</source>  
        <year>2006</year>  
        <month>03</month>  
        <volume>96</volume>  
        <issue>3</issue>  
        <fpage>538</fpage>  
        <lpage>546</lpage>  
        <pub-id pub-id-type="doi">10.2105/AJPH.2005.066001</pub-id></nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Schlager</surname>
            <given-names>KJ</given-names>
          </name>
        </person-group>
        <article-title>Systems engineering—key to modern development</article-title>
        <source>IRE Tran. Eng Manage</source>  
        <year>1956</year>  
        <month>07</month>  
        <volume>EM-3</volume>  
        <issue>3</issue>  
        <fpage>64</fpage>  
        <lpage>66</lpage>  
        <pub-id pub-id-type="doi">10.1109/IRET-EM.1956.5007383</pub-id></nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Venkatasubramanian</surname>
            <given-names>V</given-names>
          </name>
        </person-group>
        <article-title>Systemic failures: challenges and opportunities in risk management in complex systems</article-title>
        <source>AIChE J</source>  
        <year>2010</year>  
        <month>11</month>  
        <day>30</day>  
        <volume>57</volume>  
        <issue>1</issue>  
        <fpage>2</fpage>  
        <lpage>9</lpage>  
        <pub-id pub-id-type="doi">10.1002/aic.12495</pub-id></nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Leveson</surname>
            <given-names>NG</given-names>
          </name>
          <name name-style="western">
            <surname>Stephanopoulos</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>A system-theoretic, control-inspired view and approach to process safety</article-title>
        <source>AIChE J</source>  
        <year>2013</year>  
        <month>11</month>  
        <day>28</day>  
        <volume>60</volume>  
        <issue>1</issue>  
        <fpage>2</fpage>  
        <lpage>14</lpage>  
        <pub-id pub-id-type="doi">10.1002/aic.14278</pub-id></nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bookstaber</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Glasserman</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Iyengar</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Luo</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Venkatasubramanian</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>Z</given-names>
          </name>
        </person-group>
        <article-title>Process systems engineering as a modeling paradigm for analyzing systemic risk in financial networks</article-title>
        <source>J Invest</source>  
        <year>2015</year>  
        <month>05</month>  
        <volume>24</volume>  
        <issue>2</issue>  
        <fpage>147</fpage>  
        <lpage>162</lpage>  
        <pub-id pub-id-type="doi">10.3905/joi.2015.24.2.147</pub-id></nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Garvey</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <source>Analytical Methods for Risk Management: A Systems Engineering Perspective</source>  
        <year>2008</year>  
        <publisher-loc>Boca Raton</publisher-loc>
        <publisher-name>RC Press</publisher-name></nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Sage</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rouse</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <source>Handbook of Systems Engineering and Management</source>  
        <year>2009</year>  
        <publisher-loc>Hoboken</publisher-loc>
        <publisher-name>John Wiley &#38; Sons</publisher-name></nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kopach-Konrad</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Lawley</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Criswell</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Hasan</surname>
            <given-names>I</given-names>
          </name>
          <name name-style="western">
            <surname>Chakraborty</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Pekny</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Doebbeling</surname>
            <given-names>BN</given-names>
          </name>
        </person-group>
        <article-title>Applying systems engineering principles in improving health care delivery</article-title>
        <source>J Gen Intern Med</source>  
        <year>2007</year>  
        <month>12</month>  
        <volume>22 Suppl 3</volume>  
        <fpage>431</fpage>  
        <lpage>437</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/18026813"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1007/s11606-007-0292-3</pub-id>
        <pub-id pub-id-type="medline">18026813</pub-id>
        <pub-id pub-id-type="pmcid">PMC2150611</pub-id></nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Yaylali</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Ivy</surname>
            <given-names>JS</given-names>
          </name>
          <name name-style="western">
            <surname>Taheri</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Systems engineering methods for enhancing the value stream in public health preparedness: the role of Markov models, simulation, and optimization</article-title>
        <source>Public Health Rep</source>  
        <year>2014</year>  
        <volume>129 Suppl 4</volume>  
        <fpage>145</fpage>  
        <lpage>153</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25355986"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1177/00333549141296S419</pub-id>
        <pub-id pub-id-type="medline">25355986</pub-id>
        <pub-id pub-id-type="pmcid">PMC4187318</pub-id></nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Staab</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Studer</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <source>Handbook on Ontologies, Vol. 1. 2nd Edition</source>  
        <year>2013</year>  
        <publisher-loc>Berlin</publisher-loc>
        <publisher-name>Springer Science &#38; Business Media</publisher-name></nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Grüninger</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Fox</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Methodology for the design and evaluation of ontologies</article-title>
        <year>1995</year>  
        <conf-name>IJCAI'95, Workshop on Basic Ontological Issues in Knowledge Sharing</conf-name>
        <conf-date>1995</conf-date>
        <conf-loc>Montreal</conf-loc></nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Venkatasubramanian</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>Z</given-names>
          </name>
        </person-group>
        <article-title>TeCSMART: a hierarchical framework for modeling and analyzing systemic risk in sociotechnical systems</article-title>
        <source>AIChE J</source>  
        <year>2016</year>  
        <month>05</month>  
        <day>24</day>  
        <volume>62</volume>  
        <issue>9</issue>  
        <fpage>3065</fpage>  
        <lpage>3084</lpage>  
        <pub-id pub-id-type="doi">10.1002/aic.15302</pub-id></nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Heussen</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Lind</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Decomposing objectives and functions in power system operation and control</article-title>
        <year>2009</year>  
        <conf-name>IEEE PES/IAS Conference on Sustainable Alternative Energ</conf-name>
        <conf-date>2009</conf-date>
        <conf-loc>Valencia</conf-loc></nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Lind</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Modeling goals and functions of complex industrial plants</article-title>
        <source>Appl Artif Intell</source>  
        <year>1994</year>  
        <month>04</month>  
        <volume>8</volume>  
        <issue>2</issue>  
        <fpage>259</fpage>  
        <lpage>283</lpage>  
        <pub-id pub-id-type="doi">10.1080/08839519408945442</pub-id></nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chittaro</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Functional diagnosis and prescription of measurements using effort and flow variables</article-title>
        <source>IEE Proc-Control Theory Appl</source>  
        <year>1995</year>  
        <volume>142</volume>  
        <issue>5</issue>  
        <fpage>420</fpage>  
        <lpage>432</lpage>  
        <pub-id pub-id-type="doi">10.1049/ip-cta:19952019</pub-id></nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Chittaro</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Guida</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Tasso</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Toppano</surname>
            <given-names>E</given-names>
          </name>
        </person-group>
        <article-title>Functional and teleological knowledge in the multimodeling approach for reasoning about physical systems: a case study in diagnosis</article-title>
        <source>IEEE Trans Syst Man Cybern</source>  
        <year>1993</year>  
        <volume>23</volume>  
        <issue>6</issue>  
        <fpage>1718</fpage>  
        <lpage>1751</lpage>  
        <pub-id pub-id-type="doi">10.1109/21.257765</pub-id></nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kopena</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Regli</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <article-title>Functional modeling of engineering designs for the semantic Web</article-title>
        <source>IEEE Data Engineer Bull</source>  
        <year>2003</year>  
        <volume>26</volume>  
        <issue>4</issue>  
        <fpage>55</fpage>  
        <lpage>61</lpage> </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>Council of the European Union</collab>
        </person-group>
        <source>Council conclusions on lessons learned from the A/H1N1 pandemic—health security in the European Union</source>  
        <year>2010</year>  
        <access-date>2017-09-25</access-date>
        <publisher-loc>Brussels</publisher-loc>
        <publisher-name>Council of the European Union</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://ec.europa.eu/health//sites/health/files/preparedness_response/docs/council_lessonsh1n1_en.pdf">https://ec.europa.eu/health//sites/health/files/preparedness_response/docs/council_lessonsh1n1_en.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkfOkzFe"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
        <source>Learning the lessons from the H1N1 vaccination campaign for health care workers</source>  
        <year>2010</year>  
        <access-date>2017-09-25</access-date>
        <publisher-loc>London</publisher-loc>
        <publisher-name>UK Department of Health</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/216168/dh_117133.pdf">https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/216168/dh_117133.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkh0fM8U"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>World Health Organization</collab>
        </person-group>
        <source>Pandemic Influenza Preparedness and Response Guide</source>  
        <year>2009</year>  
        <access-date>2017-09-25</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://apps.who.int/iris/bitstream/10665/44123/1/9789241547680_eng.pdf">http://apps.who.int/iris/bitstream/10665/44123/1/9789241547680_eng.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkh6WjOO"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Cimiano</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <source>Ontology Learning and Population From Text: Algorithms, Evaluation and Applications</source>  
        <year>2006</year>  
        <publisher-loc>New York</publisher-loc>
        <publisher-name>Springer</publisher-name></nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Carley</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Columbus</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Landwehr</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <source>Automap User's Guide 2013</source>  
        <year>2013</year>  
        <access-date>2017-09-25</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.dtic.mil/get-tr-doc/pdf?AD=ADA586976">http://www.dtic.mil/get-tr-doc/pdf?AD=ADA586976</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkhpXxaS"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Riloff</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Wiebe</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Learning extraction patterns for subjective expressions</article-title>
        <year>2003</year>  
        <conf-name>Proceedings of the conference on Empirical methods in natural language processing</conf-name>
        <conf-date>2003</conf-date>
        <conf-loc>Stroudsburg</conf-loc>
        <pub-id pub-id-type="doi">10.3115/1119355.1119369</pub-id></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Hoekstra</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Breuker</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Di Bello</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Boer</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>The LKIF Core Ontology of Basic Legal Concepts</article-title>
        <year>2007</year>  
        <conf-name>Proceedings of the Workshop on Legal Ontologies and Artificial Intelligence Techniques (LOAIT )</conf-name>
        <conf-date>2007</conf-date>
        <conf-loc>Stanford</conf-loc></nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>d'Aquin</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Schlicht</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Stuckenschmidt</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Sabou</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>Ontology modularization for knowledge selection: experiments and evaluations</article-title>
        <year>2007</year>  
        <conf-name>International Conference on Database and Expert Systems Applications</conf-name>
        <conf-date>2007</conf-date>
        <conf-loc>Regensburg</conf-loc>
        <pub-id pub-id-type="doi">10.1007/978-3-540-74469-6_85</pub-id></nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Grau</surname>
            <given-names>BC</given-names>
          </name>
          <name name-style="western">
            <surname>Horrocks</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Kazakov</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Sattler</surname>
            <given-names>U</given-names>
          </name>
        </person-group>
        <article-title>A logical framework for modularity of ontologies</article-title>
        <year>2007</year>  
        <conf-name>IJCAI'07 Proceedings of the 20th international joint conference on Artifical intelligence</conf-name>
        <conf-date>2007</conf-date>
        <conf-loc>Hyderabad</conf-loc></nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Musen</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <article-title>The Protege project: A look back and a look forward</article-title>
        <source>AI Matters</source>  
        <year>2015</year>  
        <volume>1</volume>  
        <issue>4</issue>  
        <pub-id pub-id-type="doi">10.1145/2557001.25757003</pub-id></nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Wang</surname>
            <given-names>XH</given-names>
          </name>
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>DQ</given-names>
          </name>
          <name name-style="western">
            <surname>Gu</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Pung</surname>
            <given-names>HK</given-names>
          </name>
        </person-group>
        <article-title>Ontology based context modeling and reasoning using OWL</article-title>
        <year>2004</year>  
        <conf-name>Proceedings of the Second IEEE Annual Conference</conf-name>
        <conf-date>2004</conf-date>
        <conf-loc>Washington</conf-loc></nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kuba</surname>
            <given-names>M</given-names>
          </name>
        </person-group>
        <source>OWL 2 and SWRL tutorial</source>  
        <access-date>2015-12-07</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://dior.ics.muni.cz/~makub/owl/">http://dior.ics.muni.cz/~makub/owl/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6dbdpmnqA"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>World Health Organization</collab>
        </person-group>
        <source>WHO technical advice for case management of Influenza A(H1N1) in air transport</source>  
        <year>2009</year>  
        <access-date>2017-09-25</access-date>
        <publisher-loc>Geneva</publisher-loc>
        <publisher-name>World Health Organization</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.who.int/ihr/travel/A(H1N1)_air_transport_guidance.pdf">http://www.who.int/ihr/travel/A(H1N1)_air_transport_guidance.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkiWa9Ex"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
        <source>US Code: Title 42, Chapter 6A</source>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://uscode.house.gov/view.xhtml?path=/prelim@title42/chapter6A&#38;edition=prelim">http://uscode.house.gov/view.xhtml?path=/prelim@title42/chapter6A&#38;edition=prelim</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6dbdNqIxg"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
        <source>Title 42, Chapter 1</source>  
        <access-date>2015-12-07</access-date>
        <comment>Code of Federal Regulations 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.gpo.gov/fdsys/pkg/CFR-2013-title42-vol1/pdf/CFR-2013-title42-vol1-chapI.pdf">http://www.gpo.gov/fdsys/pkg/CFR-2013-title42-vol1/pdf/CFR-2013-title42-vol1-chapI.pdf</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6dbdWgF6C"/></comment> </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>Department of Health and Human Services</collab>
        </person-group>
        <source>Foreign quarantines: etiological agents, hosts, and vectors</source>  
        <year>2010</year>  
        <access-date>2017-09-25</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.gpo.gov/fdsys/pkg/FR-2011-10-14/pdf/2011-26656.pdf">https://www.gpo.gov/fdsys/pkg/FR-2011-10-14/pdf/2011-26656.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkihBGDH"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>World Health Organization</collab>
        </person-group>
        <source>International Health Regulations</source>  
        <year>2005</year>  
        <access-date>2017-09-25</access-date>
        <publisher-name>World Health Organization</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://apps.who.int/iris/bitstream/10665/246107/1/9789241580496-eng.pdf">http://apps.who.int/iris/bitstream/10665/246107/1/9789241580496-eng.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkjwk3ee"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <collab>World Health Organization</collab>
        </person-group>
        <source>Protocol for assessing national surveillance and response capacities for the international health regulations</source>  
        <year>2010</year>  
        <access-date>2017-09-25</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.who.int/ihr/publications/who_hse_ihr_201007_en.pdf">http://www.who.int/ihr/publications/who_hse_ihr_201007_en.pdf</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tkk4W4FI"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Fineberg</surname>
            <given-names>HV</given-names>
          </name>
        </person-group>
        <article-title>Pandemic preparedness and response—lessons from the H1N1 influenza of 2009</article-title>
        <source>N Engl J Med</source>  
        <year>2014</year>  
        <month>04</month>  
        <day>03</day>  
        <volume>370</volume>  
        <issue>14</issue>  
        <fpage>1335</fpage>  
        <lpage>1342</lpage>  
        <pub-id pub-id-type="doi">10.1056/NEJMra1208802</pub-id>
        <pub-id pub-id-type="medline">24693893</pub-id></nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Asnis</surname>
            <given-names>DS</given-names>
          </name>
          <name name-style="western">
            <surname>Conetta</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Teixeira</surname>
            <given-names>AA</given-names>
          </name>
          <name name-style="western">
            <surname>Waldman</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Sampson</surname>
            <given-names>BA</given-names>
          </name>
        </person-group>
        <article-title>The West Nile Virus outbreak of 1999 in New York: the Flushing Hospital experience</article-title>
        <source>Clin Infect Dis</source>  
        <year>2000</year>  
        <month>03</month>  
        <volume>30</volume>  
        <issue>3</issue>  
        <fpage>413</fpage>  
        <lpage>418</lpage>  
        <pub-id pub-id-type="doi">10.1086/313737</pub-id>
        <pub-id pub-id-type="medline">10722421</pub-id>
        <pub-id pub-id-type="pii">CID994278</pub-id></nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Higuchi</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <source>KH Coder</source>  
        <access-date>2017-09-12</access-date>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://khc.sourceforge.net/en/">http://khc.sourceforge.net/en/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6tQl81dAy"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Venkatasubramanian</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Rengaswamy</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Yin</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Kavuri</surname>
            <given-names>SN</given-names>
          </name>
        </person-group>
        <article-title>A review of process fault detection and diagnosis</article-title>
        <source>Comp Chem Engineer</source>  
        <year>2003</year>  
        <month>3</month>  
        <volume>27</volume>  
        <issue>3</issue>  
        <fpage>293</fpage>  
        <lpage>311</lpage>  
        <pub-id pub-id-type="doi">10.1016/S0098-1354(02)00160-6</pub-id></nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Burton-Jones</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Storey</surname>
            <given-names>VC</given-names>
          </name>
          <name name-style="western">
            <surname>Sugumaran</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Ahluwalia</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>A semiotic metrics suite for assessing the quality of ontologies</article-title>
        <source>Data Knowl Engineer</source>  
        <year>2005</year>  
        <month>10</month>  
        <volume>55</volume>  
        <issue>1</issue>  
        <fpage>84</fpage>  
        <lpage>102</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.datak.2004.11.010</pub-id></nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Duque-Ramos</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Boeker</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Jansen</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Schulz</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Iniesta</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Fernández-Breis</surname>
            <given-names>JT</given-names>
          </name>
        </person-group>
        <article-title>Evaluating the Good Ontology Design Guideline (GoodOD) with the ontology quality requirements and evaluation method and metrics (OQuaRE)</article-title>
        <source>PLoS One</source>  
        <year>2014</year>  
        <month>8</month>  
        <volume>9</volume>  
        <issue>8</issue>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0104463"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1371/journal.pone.0104463</pub-id>
        <pub-id pub-id-type="medline">25148262</pub-id>
        <pub-id pub-id-type="pii">PONE-D-14-20770</pub-id>
        <pub-id pub-id-type="pmcid">PMC4141745</pub-id></nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Brank</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Grobelnik</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Miladenic</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>A survey of ontology evaluation techniques</article-title>
        <year>2005</year>  
        <conf-name>Proceedings of 8th International Multi-Conf Information Society</conf-name>
        <conf-date>2005</conf-date>
        <conf-loc>Lisbon</conf-loc></nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Maedche</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Staab</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>Measuring similarity between ontologies</article-title>
        <year>2002</year>  
        <conf-name>International Conference on Knowledge Engineering and Knowledge Management</conf-name>
        <conf-date>2002</conf-date>
        <conf-loc>London</conf-loc></nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Bures</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Otcenásková</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Cech</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Antos</surname>
            <given-names>K</given-names>
          </name>
        </person-group>
        <article-title>A proposal for a computer-based framework of support for public health in the management of biological incidents: the Czech Republic experience</article-title>
        <source>Perspect Public Health</source>  
        <year>2012</year>  
        <month>11</month>  
        <volume>132</volume>  
        <issue>6</issue>  
        <fpage>292</fpage>  
        <lpage>298</lpage>  
        <pub-id pub-id-type="doi">10.1177/1757913912444260</pub-id>
        <pub-id pub-id-type="medline">23111084</pub-id>
        <pub-id pub-id-type="pii">1757913912444260</pub-id></nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Venkatasubramanian</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Zhao</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Joglekar</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Jain</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Hailemariam</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Suresh</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Akkisetty</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Morris</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Reklaitis</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Ontological informatics infrastructure for pharmaceutical product development and manufacturing</article-title>
        <source>Comput Chem Engineer</source>  
        <year>2006</year>  
        <month>9</month>  
        <volume>30</volume>  
        <issue>10-12</issue>  
        <fpage>1482</fpage>  
        <lpage>1496</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.compchemeng.2006.05.036</pub-id></nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Rao</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Makkithaya</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Gupta</surname>
            <given-names>N</given-names>
          </name>
        </person-group>
        <article-title>Ontology based semantic representation for Public Health data integration</article-title>
        <year>2014</year>  
        <conf-name>International Conference on Contemporary Computing and Informatics</conf-name>
        <conf-date>2014</conf-date>
        <conf-loc>Mysore</conf-loc></nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Schriml</surname>
            <given-names>LM</given-names>
          </name>
          <name name-style="western">
            <surname>Arze</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Nadendla</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Chang</surname>
            <given-names>YW</given-names>
          </name>
          <name name-style="western">
            <surname>Mazaitis</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Felix</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Feng</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Kibbe</surname>
            <given-names>WA</given-names>
          </name>
        </person-group>
        <article-title>Disease ontology: a backbone for disease semantic integration</article-title>
        <source>Nucleic Acids Res</source>  
        <year>2012</year>  
        <month>01</month>  
        <volume>40</volume>  
        <fpage>D940</fpage>  
        <lpage>D946</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22080554"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1093/nar/gkr972</pub-id>
        <pub-id pub-id-type="medline">22080554</pub-id>
        <pub-id pub-id-type="pii">gkr972</pub-id>
        <pub-id pub-id-type="pmcid">PMC3245088</pub-id></nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Hobbs</surname>
            <given-names>JR</given-names>
          </name>
          <name name-style="western">
            <surname>Pan</surname>
            <given-names>F</given-names>
          </name>
        </person-group>
        <article-title>An ontology of time for the semantic web</article-title>
        <year>2004</year>  
        <month>03</month>  
        <day>01</day>  
        <conf-name>ACM Transactions on Asian Language Information Processing (TALIP) - Special Issue on Temporal Information Processing</conf-name>
        <conf-date>2004</conf-date>
        <conf-loc>New York</conf-loc>
        <fpage>66</fpage>  
        <lpage>85</lpage>  
        <pub-id pub-id-type="doi">10.1145/1017068.1017073</pub-id></nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="web">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Lieberman</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Singh</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Goad</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <source>W3C geospatial ontologies</source>  
        <publisher-name>WC3 Organization</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.w3.org/2005/Incubator/geo/XGR-geo-ont/">https://www.w3.org/2005/Incubator/geo/XGR-geo-ont/</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6rDV062jT"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nolen</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Braveman</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Dachs</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Strengthening health information systems to address health equity challenges</article-title>
        <source>B World Health Organ</source>  
        <year>2005</year>  
        <volume>83</volume>  
        <issue>8</issue>  
        <fpage>597</fpage>  
        <lpage>603</lpage>  
        <pub-id pub-id-type="doi">10.1590/S0042-96862005000800013</pub-id></nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <collab>Tao</collab>
          <name name-style="western">
            <surname>Wei</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>Solbrig</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Savova</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Chute</surname>
            <given-names>C</given-names>
          </name>
        </person-group>
        <article-title>CNTRO: a semantic web ontology for temporal relation inferencing in clinical narratives</article-title>
        <year>2010</year>  
        <conf-name>AMIA Annual Symposium Proceedings</conf-name>
        <conf-date>2010</conf-date>
        <conf-loc>Washington</conf-loc></nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Ashburner</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Ball</surname>
            <given-names>CA</given-names>
          </name>
          <name name-style="western">
            <surname>Blake</surname>
            <given-names>JA</given-names>
          </name>
          <name name-style="western">
            <surname>Botstein</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Butler</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Cherry</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Davis</surname>
            <given-names>AP</given-names>
          </name>
          <name name-style="western">
            <surname>Dolinski</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Dwight</surname>
            <given-names>SS</given-names>
          </name>
          <name name-style="western">
            <surname>Eppig</surname>
            <given-names>JT</given-names>
          </name>
          <name name-style="western">
            <surname>Harris</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Hill</surname>
            <given-names>DP</given-names>
          </name>
          <name name-style="western">
            <surname>Issel-Tarver</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Kasarskis</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Lewis</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Matese</surname>
            <given-names>JC</given-names>
          </name>
          <name name-style="western">
            <surname>Richardson</surname>
            <given-names>JE</given-names>
          </name>
          <name name-style="western">
            <surname>Ringwald</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Rubin</surname>
            <given-names>GM</given-names>
          </name>
          <name name-style="western">
            <surname>Sherlock</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Gene ontology: tool for the unification of biology</article-title>
        <source>Nat Genet</source>  
        <year>2000</year>  
        <month>05</month>  
        <volume>25</volume>  
        <issue>1</issue>  
        <fpage>25</fpage>  
        <lpage>29</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/10802651"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1038/75556</pub-id>
        <pub-id pub-id-type="medline">10802651</pub-id>
        <pub-id pub-id-type="pmcid">PMC3037419</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
