<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Ontological Representation of CDC Active Bacterial Core Surveillance Case Reports</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Albert Goldfain</string-name>
          <email>albertgoldfain@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lindsay G. Cowell</string-name>
          <email>lindsay.cowell@utsouthwestern.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>(1) Dept. of Eng and Computer Science, Syracuse University, (2) National Center for Ontological Research, (3) Dept. of Clinical Science, UT Southwestern Medical Center</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dept. of Clinical Science UT Southwestern Medical Center Dallas</institution>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Dept. of Eng. and Computer Science Syracuse University Syracuse</institution>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>National Center for Immunization and Respiratory Diseases, Division of Bacterial Diseases</institution>
          , “
          <addr-line>CDC - ABCs: Overview - Background”</addr-line>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>National Center for Ontological Research Buffalo</institution>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2014</year>
      </pub-date>
      <fpage>74</fpage>
      <lpage>77</lpage>
      <abstract>
        <p>The Center for Disease Control and Prevention's Active Bacterial Core Surveillance (CDC ABCs) Program is a collaborative effort betweeen the CDC, state health departments, laboratories, and universities to track invasive bacterial pathogens of particular importance to public health [1]. The year-end surveillance reports produced by this program help to shape public policy and coordinate responses to emerging infectious diseases over time. The ABCs case report form (CRF) data represents an excellent opportunity for data reuse beyond the original surveillance purposes. In this work, we focus on methicillin-resistant Staphylococcus aureus (MRSA), which has been tracked by the ABCs program since 2005. We use the Infectious Disease Ontology (IDO) Staphyloccocus aureus extension ontology (IDO-Staph), along with other ontologies following the principles of the Open Biomedical Ontologies Foundry (OBOF) to represent the entities referenced by the MRSA specific ABCs CRF. The goals of this effort are: (1) to demonstrate that infectious disease case report data can be positioned for reuse and linking to complementary data sources at the point of collection, (2) to identify any coverage gaps or limitations in the OBOF representation, and (3) to extend and reassess previous work in the ontology of infectious diseases [2,3,4].</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
    </sec>
    <sec id="sec-2">
      <title>ONTOLOGICAL REPRESENTATION OF CASE REPORTS</title>
      <p>One of the unique problems for synthesizing surveillance
data relating to any rapidly changing phenomenon of broad
social impact – such as the rise of antibiotic resistance in
bacteria – is that the range of information requires changes
over time. In addition to temporal queries, such data frequently
must be interrogated along several other dimensions: across
pathogens in the ABCs program, across geographical regions
represented by different ABCs surveillance sites and beyond,
across pathogens with different forms of antibiotic resistance
(with our evolving understanding of the mode of action and
genetic basis for this resistance), and across data models /
systems with different case definition criteria and different
semantics for data entry fields.</p>
      <p>The semantic web stack of technologies, when applied towards
metadata representation and resource linking, is a particularly
good fit for this task. The SPARQL query language for such
representations also allows data to be stored in a decentralized
manner. This is of particular importance for an international
problem such as bacterial surveillance.</p>
    </sec>
    <sec id="sec-3">
      <title>We use OBOF ontologies to represent: (1) entities referenced in the CDC ABCs CRF for MRSA, (2) the CDC case definition for MRSA infectious disease, and (3) the CDC inclusion criteria for cases.</title>
    </sec>
    <sec id="sec-4">
      <title>IDO-Staph is an extension of the Infectious Disease Ontology</title>
      <p>(IDO) covering entities specific to Staphylococcus aureus
infectious disease. Classes in IDO-Staph have supertypes in</p>
    </sec>
    <sec id="sec-5">
      <title>IDO, the Ontology for General Medical Science (OGMS), and</title>
    </sec>
    <sec id="sec-6">
      <title>BFO. Within this framework, many of the logical implications</title>
      <p>are inherited by descendant types from their supertypes. In
creating our ontological representation to cover the ABCs</p>
    </sec>
    <sec id="sec-7">
      <title>CRF, we use the most specific OBOF term (i.e., the lowest descendent of a BFO term) that is applicable for each relevant entity in the CRF.</title>
    </sec>
    <sec id="sec-8">
      <title>As an illustration of the sorts of entities to which the CRF needs to refer to, we represent the following information from a specific (hypothetical) case report:</title>
      <p>John Doe is a 67 inch, 210 lb, 38 year-old patient at the Mayo
Clinic with a case with a Staphylococcus aureus infectious
disease. Labwork identified MRSA in a sample John’s blood
(MRSA bacteremia) after spa typing the isolate. The isolate
was found to be SCCMec Type IV, tested positive for
toxicshock syndrome toxin, and negative for Panton-Valentin
Leukocidn (PVL). This strain of isolate is known to be resistant
to several antibiotics, including Methicillin. The underlying
condition that led to the initial infectious disorder was
intravenous drug use.</p>
    </sec>
    <sec id="sec-9">
      <title>Our ontological representation of this case report is expressed</title>
      <p>as RDF triples. Relations are drawn from the OBO Relation
Ontology [5]. The appropriate relationship between individuals
referred to by CRF fields and the universals in OBOF
ontologies is made explicit. For example, the following triples
establish relationships between John Doe’s particular disease
and disorder, and the universal types they instantiate:
‘John Doe’s MRSA infectious disease’ instance of
ido-staph:‘staphylococcus aureus infectious disease’
‘John Doe’s MRSA infectious disorder’ instance of
ido-staph:‘staphylococcus aureus infectious disorder’
‘John Doe’s MRSA infectious disease’ has_material_basis
‘John Doe’s MRSA infectious disorder’.</p>
    </sec>
    <sec id="sec-10">
      <title>The material basis of the infectious disease is the infectious</title>
      <p>disorder, which has as proper parts: an organism population of</p>
    </sec>
    <sec id="sec-11">
      <title>MRSA (i.e., the infection) and a portion of John Doe’s blood.</title>
    </sec>
    <sec id="sec-12">
      <title>The MRSA isolate is sampled from a part of John Doe (his</title>
      <p>blood) and placed into culture. The time at which entities exist
is very important here. The material sample isolated from</p>
    </sec>
    <sec id="sec-13">
      <title>John’s disorder is no longer part of John (and thus no longer</title>
      <p>part of the material basis for his disease), but data derived
from this sample can be predictive of the course of John Doe’s
disease, prognosis, and outcome. In culture, only a
subpopulation of MRSA organisms will have ever been a part of</p>
    </sec>
    <sec id="sec-14">
      <title>John, but we have faith in the stability of the predictions it</title>
      <p>allows because the salient properties of John’s MRSA
population are inherited by their immediate descendents.</p>
    </sec>
    <sec id="sec-15">
      <title>Thus, we can make inferences based on SCCmec and spa</title>
      <p>typing, toxin profiles, and other labwork assays performed on
the isolate in culture, for example, the methicillin resistance of</p>
    </sec>
    <sec id="sec-16">
      <title>John’s MRSA:</title>
      <p>‘John Doe’s MRSA isolate’ has_disposition ‘John Doe’s</p>
    </sec>
    <sec id="sec-17">
      <title>MRSA isolate’s antibiotic resistance to methicillin’ ‘John Doe’s MRSA isolate’s antibiotic resistance to methicillin’ instance of ido-staph:‘PBP2a-mediated resistance to beta-lactam antibiotic’</title>
    </sec>
    <sec id="sec-18">
      <title>IDO-Staph provides the ability to subtype specific drug</title>
      <p>resistance dispositions based on their mechanism of action.</p>
    </sec>
    <sec id="sec-19">
      <title>However much broader coverage is needed for the</title>
      <p>mechanisms of action involved for different antibiotics. The</p>
    </sec>
    <sec id="sec-20">
      <title>Comprehensive Antibiotic Resistance Database (CARD) and</title>
      <p>its associated ontology [6] provide a good start along these
lines. To be brought fully into alignment with OBOF, CARD
data would have to be linked to a suitable drug ontology such
as DrON [7].</p>
      <p>In virtue of its physical makeup, John Doe’s MRSA infection
(i.e., the population of MRSA organisms) has a particular
antibiotic resistance towards methicillin. Moreover, resistance
to methicillin can (and will) vary in degree across isolated
samples. Laboratory personnel measure the degree of
resistance by performing a minimal inhibitory concentration
assay to produce a certain measurement datum.</p>
    </sec>
    <sec id="sec-21">
      <title>We have elsewhere discussed the detailed representation of</title>
    </sec>
    <sec id="sec-22">
      <title>SCCmec types and toxin profiles for PVL and TSST in the</title>
      <p>context of the NARSA isolate repository, as well as the
representational units for the lab processes and assays
involved in classifying Staphylococcus aureus [4]. These
representations are readily combined with the data from the</p>
    </sec>
    <sec id="sec-23">
      <title>CRF to enrich the clinical picture of John Doe’s disease. The entities and relationships required for the ontological representation of SCCmec type IV (as in this case) are presented.</title>
      <p>The infection type in this case is bacteremia, which is
differentiated from other types of infection solely by
anatomical location of the isolate (i.e., the bloodstream). The
underlying condition listed for the MRSA infectious disease is
intravenous drug use. Ontologically, this can be modeled as a
disposition towards certain behaviors that would be
explanatory for the how the MRSA came to be in John’s
bloodstream. Depending on the modeling needs, John’s
intravenous drug use can be associated with many other pieces
of information (e.g., relating to the injection site bearing the
portal of entry role for Staphylococcus aureus).</p>
    </sec>
    <sec id="sec-24">
      <title>The final portion of the CRF is the classification of MRSA</title>
      <p>type. Absent any information that John Doe acquired MRSA
while meeting the criteria for either HACO or HA, John’s case
would be classified as community-associated MRSA. Lists of
criteria such as this are well suited for OWL/RDF since the
task is determining if an instance satisfies a description.</p>
      <p>III.</p>
    </sec>
    <sec id="sec-25">
      <title>A WEB-BASED MRSA CASE REPORTING SYSTEM</title>
    </sec>
    <sec id="sec-26">
      <title>We have implemented a large part of the ABCs CRF for</title>
      <p>MRSA as a standards-compliant (HTML5/CSS3) web-based
form.1 The current version of the web-form is intended as a
proof-of-concept for annotating CRF data at the point of
collection. The web form is a custom solution rather than one
built around a particular web framework. This allows for
maximal flexibility in exporting to other data formats that are
specifically required by external resources. The ultimate goal
would be to implement such a system with direct EMR
integration.</p>
      <p>IV.</p>
    </sec>
    <sec id="sec-27">
      <title>CONCLUSION</title>
    </sec>
    <sec id="sec-28">
      <title>Our annotation of such data with OBOF types and relations</title>
      <p>can provide several advantages, including: (1) precise
semantics and definitions can be enforced during data entry,
(2) linkage to other infectious disease resources, such as the</p>
    </sec>
    <sec id="sec-29">
      <title>CARD, to enable broader queries, (3) harmonization and</title>
      <p>comparability of multi-year CRF data (e.g., for a longitudinal
study), (4) the possibility for retrospective application of new
inclusion criteria, and (5) an OWL/RDF data model with which
to build web applications around CRF data.</p>
    </sec>
    <sec id="sec-30">
      <title>Most of the resources necessary to build an ontological</title>
      <p>representation of the entities referred to by the ABCs CRF are
already part of ontologies conformant to OBOF principles.</p>
    </sec>
    <sec id="sec-31">
      <title>Some of the gaps in coverage include: (1) an ontological</title>
      <p>resource specifically for pathogen genes and gene products, (2)
a drug ontology that classifies methods of action for different
antibiotics, and (3) a good ontological relation template for
how information about isolates in culture can lead to inferences
about the disorders these bacteria are sampled from.</p>
    </sec>
    <sec id="sec-32">
      <title>If case report data is properly represented and linked to other resources, this data can lead to insights beyond the original scope of CDC ABCs surveillance.</title>
    </sec>
    <sec id="sec-33">
      <title>ACKNOWLEDGMENT</title>
    </sec>
    <sec id="sec-34">
      <title>The authors would like to thank Dr. Vance Fowler and Dr.</title>
    </sec>
    <sec id="sec-35">
      <title>Alan Lesee for productive discussions on Staphylococcus aureus case report requirements.</title>
      <p>1 See http://www.awqbi.com/ido/abccrf/</p>
      <sec id="sec-35-1">
        <title>IDO STAPH AND THE OBO FOUNDRY</title>
      </sec>
      <sec id="sec-35-2">
        <title>PROOF OF CONCEPT IMPLEMENTATION ABSTRACT</title>
        <p>We propose an ontological representation to support the annotation of a CDC Active Bacterial Core
surveillance (ABCs) case report form, specifically the form used for Methicillin-Resistant Staphylococcus
aureus surveillance. The ontological representation is developed using source ontologies from the Open
Biomedical Ontology Foundry. A prototype web-based case report form is implemented to demonstrate
how the proposed ontology resource can support the automatic annotation of case report data. The
prototype implementation can be found at http://www.awqbi.com/ido/abccrf/. We argue that the annotated
data will enable reuse of the surveillance data beyond the original scope and purpose of its collection.
Design considerations, benefits, and limitations of the ontological representation are described.
GOALS:
•
•
•</p>
        <p>Demonstrate that infectious disease case report data can be positioned for reuse and linking to
complementary data sources at the point of collection
Identify any coverage gaps or limitations in the OBOF representation, and
Extend and reassess previous work in the ontology of infectious diseases.</p>
      </sec>
      <sec id="sec-35-3">
        <title>CDC ABCs SURVEILLANCE PROGRAM</title>
        <p>CDC Active Bacterial Core Surveillance (ABCs) program is a collaborative effort between the CDC, state
health departments, laboratories, and universities to track invasive bacterial pathogens of particular
importance to public health.</p>
        <p>Case reports produced for six emergent pathogens: group A and group B Streptococcus, Haemophilus
influenzae, Neisseria meningitis, Streptococcus pneumoniae, and methicillin-resistant Staphylococcus
aureus (MRSA). The primary output of the ABCs program is a yearly epidemiological report on each of
the pathogens covered.
1. To evaluate changes in rates of hospital-onset (HO), healthcare-associated community onset (HACO),
and community-associated (CA) invasive [MRSA] disease over time and across different geographic
areas
2. To identify populations at risk for invasive MRSA disease,
3. To describe the molecular and microbiologic characteristics of [HA], [HACO], and [CA] MRSA”
Achieving these goals also requires linking case report data to relevant molecular and
microbiological information.</p>
        <p>In addition to querying case report data across time, the data may need to be queried across several other
dimensions:
•
•
•
•</p>
        <p>Across pathogens in the ABCs program
Across geographical regions represented by different ABCs surveillance sites and beyond.
Across pathogens with different forms of antibiotic resistance (with our evolving understanding of the
mode of action and genetic basis for this resistance).</p>
        <p>Across data models / systems with different case definition criteria and different semantics for data
entry fields.</p>
        <p>RESEARCHPOSTERPRESENTATIONDESIGN©2012
www.PosterPresentations.com
IDO-Staph is an extension of the Infectious Disease Ontology (IDO) covering entities specific to
Staphylococcus aureus infectious disease. Classes in IDO-Staph have supertypes in IDO, the Ontology for
General Medical Science (OGMS), and BFO. For example, the taxonomy leading to Staphylococcus
aureus infectious disease is as follows:
ogms:disease
John Doe is a 67 inch, 210 lb, 38 year-old patient at the Mayo Clinic with a case with a
Staphylococcus aureus infectious disease. Labwork identified MRSA in a sample John’s blood
(MRSA bacteremia) after spa typing the isolate. The isolate was found to be SCCMec Type IV,
tested positive for toxic-shock syndrome toxin, and negative for Panton-Valentin Leukocidn (PVL).
This strain of isolate is known to be resistant to several antibiotics, including Methicillin. The
underlying condition that led to the initial infectious disorder was intravenous drug use.
‘John Doe’s MRSA isolate’ has_disposition
‘John Doe’s MRSA isolate’s antibiotic resistance to methicillin’
‘methicillin minimal inhibitory concentration measurement datum of John Doe’s MRSA isolate’
instance of obi:‘minimal inhibitory concentration’
There are several immediate benefits of migrating the ABCs CRF from a paper form to an
electronic web form. A web form would allow for form validation (on the client and server side),
allow certain fields to be labeled as required input, and help to prevent data entry errors.
We have implemented a large part of the ABCs CRF (see http://www.awqbi.com/ido/abccrf/ )
Web form implementation
Standards compliant (HTML5/CSS3)
Follow-up questions as needed (jQuery)
Client side logical constraints / required fields enforced
RDF/XML output suitable for
•
•
•</p>
        <p>Storage in a triplestore
SPARQL query
Input to a reasoner</p>
      </sec>
      <sec id="sec-35-4">
        <title>CONCLUSIONS</title>
        <p>An ontological representation can also facilitate the extension, specialization, and linking of the
CRF with different resources. Our annotation of such data with OBOF types and relations can
provide several advantages, including:</p>
        <p>Precise semantics and definitions can be enforced during data entry.</p>
        <p>Linkage to other infectious disease resources, such as the Comprehensive Antibiotic Resistance
Database, to enable broader queries.</p>
        <p>Harmonization and comparability of multi-year CRF data (e.g., for a longitudinal study).
The possibility for retrospective application of new inclusion criteria.An OWL/RDF data
model with which to build web applications around CRF data.</p>
        <p>As we have seen, most of the resources necessary to build an ontological representation of the
entities referred to by the ABCs CRF are already part of ontologies conformant to OBOF
principles. Some of the gaps in coverage include:
1. An ontological resource specifically for pathogen genes and gene products,
2. A drug ontology that classifies methods of action for different antibiotics,
3. A good ontological relation template for how information about isolates in culture can lead to
inferences about the disorders these bacteria are sampled from.</p>
      </sec>
      <sec id="sec-35-5">
        <title>ACKNOWLEDGEMENTS AND CONTACT</title>
        <p>This work was funded by the National Institutes of Health through Grant R01 AI 77706-01.
The authors would like to thank Dr. Vance Fowler and Dr. Alan Lesee for productive discussions
on Staphylococcus aureus case report requirements.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <given-names>Biomedical</given-names>
            <surname>Informatics</surname>
          </string-name>
          , vol.
          <volume>44</volume>
          (
          <issue>1</issue>
          ), pp.
          <fpage>35</fpage>
          -
          <lpage>41</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>Conference on Formal Ontology in Information Systems</source>
          , pp.
          <fpage>400</fpage>
          -
          <lpage>413</lpage>
          ,
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>Biomedical</given-names>
            <surname>Ontology</surname>
          </string-name>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <source>biomedical ontologies”</source>
          ,
          <source>Genome Biology</source>
          , vol
          <volume>6</volume>
          :
          <fpage>R46</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Database</surname>
            <given-names>”</given-names>
          </string-name>
          ,
          <source>Antimicrobial Agents and Chemotherapy</source>
          , vol.
          <volume>57</volume>
          , pp.
          <fpage>3348</fpage>
          -
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <source>the Fourth International Conference on Biomedical Ontology</source>
          ,
          <year>2013</year>
          .
          <volume>1 2 3</volume>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <article-title>ido-staph:'PBP2a-mediated resistance to beta-lactam antibiotic'</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>