<!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>G-PROV: Provenance Management for Clinical Practice Guidelines</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>James P. McCusker</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Deborah L. M</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Guinn</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>IBM Research</institution>
          ,
          <addr-line>Cambridge, MA</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Rensselaer Polytechnic Institute</institution>
          ,
          <addr-line>Troy, NY 12180</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <fpage>68</fpage>
      <lpage>75</lpage>
      <abstract>
        <p>Providing provenance of treatment suggestions made by clinical decision support systems can enhance transparency and trust in these systems by healthcare practitioners. Provenance can aid in resolving ambiguity and con icts between various guideline sources. We have developed a guideline provenance ontology, G-Prov, by extending existing provenance ontologies, to enable accurate encoding of the source of the reasoning rules that decision support systems rely on to generate diagnosis and treatment suggestions. Our ontology enables provenance representation at di erent granularity levels within guidelines. For instance, G-Prov can be used to annotate rules with citations found in evidence sentences as well as other sources of knowledge, such as gures and tables. Additionally, we have developed an application to show a range of use cases for our ontology. We demonstrate our work annotating recommendations in a CPG for Type-2 Diabetes and discuss how our approach could be used in various medical settings where CPGs are utilized.</p>
      </abstract>
      <kwd-group>
        <kwd>Provenance</kwd>
        <kwd>Clinical Practice Guidelines</kwd>
        <kwd>Clinical Deci- sion Support Systems</kwd>
        <kwd>Ontology</kwd>
        <kwd>Biomedical Knowledge Graphs</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Guideline-based decision support systems aim to assist healthcare practitioners
with patient diagnosis and treatment choices. These systems embody
information present in authoritative clinical practice guidelines (CPGs) as computable
knowledge (e.g. logical rules). However, most of these systems fail to provide the
source of treatment suggestions. Furthermore, the information used to generate
these treatment suggestions might become obsolete, or worse yet, invalidated,
within a newer guideline. Recording the provenance of treatment suggestions
helps address the challenging task of systematically updating a system when new
guidelines or medical literature are published. To concretely tackle the problem
of lack of provenance, there needs to be an easy way to extract information
within the CPG and associate them as provenance.</p>
      <p>
        We attach provenance to SWRL [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] treatment rules of the Diabetes Mellitus
Treatment Ontology (DMTO) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. However since DMTO's rules lack provenance,
we use DMTO as an example usage of our guideline provenance ontology:
GProv and annotate these rules with recommendations from the 2018 version
of the ADA Standards of Medical Care guideline (ADA CPG)3. DMTO is an
ontology that provides treatment suggestions for Type-2 Diabetes. They use
information from several medical guidelines on Diabetes, including the ADA CPG,
Diabetes Canada,4 and the European Association for the study of Diabetes.5 As
stated earlier, DMTO lacks information on the source of each rule within the
ontology, making it di cult to evaluate the accuracy of and the evidence for
each rule. Hence, we address this issue, in our paper.
      </p>
      <p>
        To this end, we develop a guideline provenance ontology, G-Prov, to encode the
provenance details in CPGs. For our ontology, we reused several existing
ontologies, such as, W3C provenance ontology (PROV-O) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], Dublin Core Metadata
Terms (DCT) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], and the Bibliographic Ontology (BIBO) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Further, utilzing
concepts from G-Prov, we modeled the provenance of DMTO rules with content
from the ADA CPGs as Resource Description Framework (RDF) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] Knowledge
Graphs (KGs). We show the diverse use of our ontology-enabled approach by
developing an application for three di erent use cases that cover a variety of
users of guideline documents.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Several general-purpose provenance ontologies currently exist such as the
Provenance Ontology (PROV-O) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], which is an ontology that provides classes and
properties to capture generic provenance terms in various domain. The Dublin
Core Metadata Terms (DCT) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], which is a lightweight vocabulary that aids
in the description of resources and provides a list of terms that can be used to
describe metadata information. DCT can be used to represent articles, gures,
tables on a higher level. On the other hand, The Bibliographic Ontology (BIBO)
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], serves as an enhancement of the DCT ontology and contains a more detailed
description of referenced articles. However, all these provenance ontologies
address the issue of modeling of provenance at a more general level. In G-Prov,
we build o these foundational provenance ontologies to associate provenance of
clinical decisions with their authoritative guideline evidence.
      </p>
      <p>
        The clinical domain have plethora of heterogenous data of varying qualities.
Hence, there have been several e orts to create ontologies that enable increased
traceability, transparency and trust in clinical data. ProvCaRe [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] is an ontology
      </p>
      <sec id="sec-2-1">
        <title>3 ADA Standards of Medical Care: http://care.Diabetesjournals.org/</title>
      </sec>
      <sec id="sec-2-2">
        <title>4 Diabetes Canada: https://guidelines.Diabetes.ca/cpg</title>
      </sec>
      <sec id="sec-2-3">
        <title>5 EASD: https://www.easd.org/</title>
        <p>
          designed to enhance reproducibility of scienti c research by capturing the
metadata of published articles. Their ontology focuses on the details of the scienti c
study including the design description, the data collection methods, analysis of
the data and overall research methodology. Provenance Context Entity (PaCE)
[
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] is a an ontology that enables provenance tracking in scienti c data. This
ontology has been applied to the Biomedical Knowledge Repository to integrate
biomedical data from various biomedical literature, databases, and vocabulary
lists. Furthermore, in healthcare, there is an ontology for enabling provenance in
healthcare management [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] that enables the e cient integration of patient data
from various clinical sources, and helps in understanding patient outcome as a
result of a clinical process. While these ontologies exist for the clinical domain,
they fail to capture provenance terms necessary for guideline-speci c data. The
authors of [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] have developed a semantic web system that attempts to capture
guideline interactions. Their research has some similarities with our work,
however, they focus on identifying causation which is not within the scope of G-Prov
ontology.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Guideline Provenance Ontology</title>
      <p>We aim to provide an ontology that is compatible with best practice,
relevant provenance ontologies, and which is focused at directly support clinical,
guideline-based decision support systems. Our initial attempts focus mainly on
annotating SWRL rules de ned within DMTO ontology with the
recommendations found within the ADA CPG. Typically, a CPG comprises of
recommendations for clinical practice, cited publications backing these recommendations
etc. To address the use case of associating provenance with treatment
suggestions encoded as rules, we included classes and properties (described shortly in
section 3.1) in the G-Prov ontology, to link these rules to di erent granularities
of evidence within CPGs.
3.1</p>
      <sec id="sec-3-1">
        <title>Main Classes and Property Associations</title>
        <p>
          Our ontology is represented in OWL-DL and was developed using Protege [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
The G-Prov ontology 6 comprises of terms broadly belonging to three sections.
A broader provenance section that captures metadata associated with the
provenance of a treatment rule in the context of its backing CPG recommendation.
These terms were obtained from the general purpose ontologies described earlier
in section 2, i.e. PROV-O, DCT, and BIBO. The second section is comprised of
more domain speci c terms that are used to associate rules to their guideline
evidence. The third section discusses the guideline speci c classes and properties.
        </p>
        <sec id="sec-3-1-1">
          <title>6 We use the following ontology pre xes: (1) gprov: G-Prov (2) sio: SemanticScience</title>
          <p>Integrated Ontology (3) bibo: The Bibliographic Ontology (4) prov: PROV-O: The
PROV ontology (5) dct: Dublin Core Terms (6) sco: Study Cohort Ontology (7) do:
Disease Ontology (8) ncit: National Cancer Institute Thesaurus</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>Provenance in Guidelines</title>
        <p>Both CPGs (ncit:C28237) and the cited publications within them are speci c
sub-classes of bibo:Document. Additionally, citations within CPGs are
represented by gprov:Citation, and are linked to their reference information using
prov:hasPrimarySource. Further, every published document has at least one
author and, to capture the list of all the authors in a publication, we use the
class bibo:Author, which contains one or more authors. We also capture other
metadata information associated with a document using terms from both BIBO
(bibo:volume, bibo:issue, bibo:pageStart, bibo:pageEnd, bibo:uri) and DCT (dct:creator,
dct:title) ontologies.
3.3</p>
      </sec>
      <sec id="sec-3-3">
        <title>Associating provenance with treatment rules</title>
        <p>Since we are annotating treatment rules, we need a class to model them and we
introduce the gprov:FormalRule class. Additionally, these rules (gprov:FormalRule)
were obtained from guideline recommendations (gprov:Recommendation) and we
use the prov:wasDerivedFrom property to link the two classes. At a more generic
level, we can also link the rules directly to the guideline (ncit:C28237). We use
dct:partOf association to represent the relationship between a recommendation
and its host CPG.
CPGs are developed to manage a speci c health condition. In G-Prov, we link the
guideline class (ncit:C28237) to the health condition (gprov:DiseaseManagement)
it addresses via prov:used property. The gprov:DiseaseManagement class links
to (via prov:used) at least one speci c disease type (do:Disease). Additionally,
some guidelines carry a measure of the quality of each recommendation, and we
capture this information using gprov:Grade. Furthermore, guideline
recommendations are backed by one or more evidence sentences (gprov:EvidenceSentence)
within the guideline. These evidence sentences contain citations, whose modeling
using the existing provenance ontologies is explained in section 3.2.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>ADA Standards of Care Guideline Knowledge Graph</title>
      <p>There are numerous CPGs for e ective diagnosis and treatment of diseases.
Through G-Prov, we support the modeling of recommendations in the ADA
CPG. The ADA CPG is aimed at providing treatment recommendations for
healthcare practitioners to help in the management of Type-1 and Type-2
Diabetes. The ADA CPG is released annually, with updates to recommendations,
recommendation grade, evidence supporting each recommendation, and the
medical literature that backs each piece of evidence.</p>
      <p>To annotate a treatment rule with its ADA CPG recommendation, we rst did
a manual pass on the CPG to understand its structure. Subsequently, we wrote
a web scraping script using BeautifulSoup7 to extract all the contents of the
guideline into a JSON le. The contents of the JSON le included all the
recommendations, their grades, possible evidence sentences, and the citations within
each sentence. Our initial e orts focused on two chapters from the ADA CPG,
namely the \Pharmacologic Approaches to Glycemic Treatment" and
\Cardiovascular Disease and Risk Management" chapters.</p>
      <p>
        To construct the KG, we created a spreadsheet to organize the extracted
guideline data. Further, we manually identi ed applicable guideline recommendations
for DMTO treatment rules and mapped them within the spreadsheet. We had
our medical domain expert (also a co-author) go over these annotations to
conrm both completeness and accuracy. Finally, we wrote a SETLr [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] script to
automatically convert the contents of the spreadsheet to an RDF KG. Fig. 1
highlights the resulting KG from modeling a recommendation within the ADA
CPG using G-Prov ontology.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Applications of G-Prov</title>
      <p>The G-Prov ontology and the ADA KG were used to develop an application and
showcase its various uses for a variety of users. The application evolved out of the
need for healthcare practitioners to identify the sources of treatment suggestions
made by CDS. The various pieces of information that a healthcare practitioner
needed to make clinical decisions were identi ed with the help of our medical
domain expert and we began iteratively building an ontology-enabled system for</p>
      <sec id="sec-5-1">
        <title>7 https://www.crummy.com/software/BeautifulSoup</title>
        <p>our use case. We used a standard ontology engineering process to ensure both
completeness and adaptability into a wide range of applications. Our application
captures three main use cases, described in the next three paragraphs.
Screenshot of the various views of the applications can be viewed on our resources
website 8.</p>
        <p>The rst use case focuses on providing provenance information of treatment
suggestions made by CDS, including the source of the information, other
medical literature that support the article and the date of publication. Thus, when
a treatment suggestion is made by a CDS system, the healthcare practitioner's
view enables the healthcare practitioner to query the system for more
information about its suggestion.</p>
        <p>
          The second use case focuses on a Population Health Manager (PHM). To create
a view for this user, we integrate the Study Cohort Ontology [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], to assist in
visualizing information about citations. Through this view, we aim to help the
PHM identify subgroups (cohorts) of patients who may bene t from the
recommendations. Additionally, the visualizations also help them analyze the research
publications that serve as evidence for recommendations.
        </p>
        <p>The nal use case is focused on a content developer. This view would allow for
developers of CDS systems to enter provenance information while
creating/editing the decision rules. The added advantage of creating a content developers view
in our application, over other editing tools such as Protege, is that this view does
not assume the user has any semantic knowledge whatsoever. This view includes
a form to collect information from the user in a friendly, easy to read manner
and creates a KG of the information entered using the G-Prov ontology.</p>
      </sec>
      <sec id="sec-5-2">
        <title>8 Visit https://tetherless-world.github.io/GProv/</title>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Results and Discussion</title>
      <p>We have developed a guideline provenance ontology, G-Prov, and used it to
enrich DMTO ontology, by associating provenance information with treatment
rules de ned by their ontology. We have reused terminology from relevant
ontologies such as DCT, Prov-O, BIBO. Speci cally, DCT provides concepts that were
relevant to model parts of the reference information, the remaining information
was modeled using BIBO. Further, we represent the unstructured guideline data
as a structured RDF knowledge graph.</p>
      <p>We build an application that comprises of di erent views rendered by results of
SPARQL queries triggered to the ontology and the KG. The di erent views of
the application represent the various use cases that our ontology-enabled system
can be used in. Our application serves as a proof of concept for the development
of systems that can bene t from identifying provenance of CDS treatment
suggestions.</p>
      <p>Through, G-Prov we are taking a step towards enhancing transparency in
healthcare by providing more information to healthcare practitioners regarding the
granularities of guideline evidence behind treatment suggestions. We are focusing
on improving the scalability and automation aspects of our system. Speci cally,
we are exploring the use of NLP techniques to automatically/semi-automatically
identify evidence sentences that support a given guideline recommendation.
Although the G-Prov ontology has currently been used to model the ADA CPG, we
envisage that we can extend upon the ontology and introduce classes to model
guideline provenance from other CPGs.
7</p>
    </sec>
    <sec id="sec-7">
      <title>Conclusion</title>
      <p>In this paper, we have described the guideline provenance ontology: G-Prov,
which is a simple ontology for modeling provenance information of treatment
rules generated by CDS systems. In the ontology design process, we have reused
terms from several widely accepted ontologies to increase interoperability. We
have built a prototype application supported by the G-Prov ontology to show
its various use cases. Currently, we only map provenance of treatment rules to
the ADA 2018 CPG. However, G-Prov can be used to track the provenance
of information in other guidelines. We believe G-Prov is a good complement to
existing provenance ontologies, and thus it is our belief that the our paper will be
a useful contribution to both healthcare practitioners and CDS system designers
who are looking to develop treatment suggestion tools.
8</p>
    </sec>
    <sec id="sec-8">
      <title>Acknowledgements</title>
      <p>This work is partially supported by IBM Research AI through the AI Horizons
Network. We thank our colleagues from IBM (Ching-Hua Chen) and RPI (James
Hendler, John Erickson, Kristen Bennett, Rebecca Cowan) who provided insight
and expertise that greatly assisted the research.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Chari</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Agu</surname>
            ,
            <given-names>N.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seneviratne</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McCusker</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bennett</surname>
            ,
            <given-names>K.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Das</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>Making study populations visible through knowledge graphs</article-title>
          .
          <source>In: International Semantic Web Conference (ISWC)</source>
          . p. to appear. Auckland, New Zealand (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Dabrowski</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Synak</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kruk</surname>
            ,
            <given-names>S.R.</given-names>
          </string-name>
          :
          <article-title>Bibliographic ontology</article-title>
          .
          <source>In: Semantic digital libraries</source>
          , pp.
          <volume>103</volume>
          {
          <fpage>122</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Deora</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Contes</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rana</surname>
            ,
            <given-names>O.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rajbhandari</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wootten</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tamas</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varga</surname>
            ,
            <given-names>L.Z.</given-names>
          </string-name>
          :
          <article-title>Navigating provenance information for distributed healthcare management</article-title>
          .
          <source>In: Proceedings of the 2006 IEEE/WIC/ACM International Conference on Web Intelligence</source>
          . pp.
          <volume>859</volume>
          {
          <fpage>865</fpage>
          . IEEE Computer Society (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>El-Sappagh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kwak</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kwak</surname>
            ,
            <given-names>K.S.:</given-names>
          </string-name>
          <article-title>Dmto: a realistic ontology for standard diabetes mellitus treatment</article-title>
          .
          <source>Journal of biomedical semantics 9(1)</source>
          ,
          <volume>8</volume>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tabet</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grosof</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , et al.:
          <article-title>Swrl: A semantic web rule language combining owl and ruleml</article-title>
          .
          <source>W3C Member submission</source>
          <volume>21</volume>
          (
          <issue>79</issue>
          ) (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Kunze</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baker</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The dublin core metadata element set (</article-title>
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Lebo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belhajjame</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheney</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corsar</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garijo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soiland-Reyes</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zednik</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Prov-o: The prov ontology</article-title>
          .
          <source>W3C recommendation 30</source>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>McCusker</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chastain</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rashid</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Norris</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>Setlr: the semantic extract, transform, and load-r</article-title>
          .
          <source>PeerJ Preprints</source>
          <volume>6</volume>
          ,
          <issue>e26476v1</issue>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>An introduction to the resource description framework</article-title>
          .
          <source>Bulletin of the American Society for Information Science and Technology</source>
          <volume>25</volume>
          (
          <issue>1</issue>
          ),
          <volume>15</volume>
          {
          <fpage>19</fpage>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fergerson</surname>
            ,
            <given-names>R.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Musen</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>The knowledge model of protege-2000: Combining interoperability and exibility</article-title>
          .
          <source>In: International Conference on Knowledge Engineering and Knowledge Management</source>
          . pp.
          <volume>17</volume>
          {
          <fpage>32</fpage>
          . Springer (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bodenreider</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Thirunarayan</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Provenance context entity (pace): Scalable provenance tracking for scienti c rdf data</article-title>
          .
          <source>In: International Conference on Scienti c and Statistical Database Management</source>
          . pp.
          <volume>461</volume>
          {
          <fpage>470</fpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Valdez</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kim</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rueschman</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Socrates</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Redline</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.S.:</given-names>
          </string-name>
          <article-title>Provcare semantic provenance knowledgebase: evaluating scienti c reproducibility of research studies</article-title>
          .
          <source>In: AMIA Annual Symposium Proceedings</source>
          . vol.
          <year>2017</year>
          , p.
          <fpage>1705</fpage>
          . American Medical Informatics Association (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Zamborlini</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoekstra</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Da</given-names>
            <surname>Silveira</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Pruski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>ten Teije</surname>
          </string-name>
          , A.,
          <string-name>
            <surname>van Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , et al.:
          <article-title>Generalizing the detection of internal and external interactions in clinical guidelines</article-title>
          .
          <source>In: HEALTHINF</source>
          . pp.
          <volume>105</volume>
          {
          <issue>116</issue>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>