<!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>Analysis and visualization of disease courses in a semantic enabled cancer registry</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Angel Esteban-Gil</string-name>
          <email>angel.esteban@ffis.es</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>J. T. Fernandez-Breis</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Martin Boeker</string-name>
          <email>martin.boeker@uniklinik-freiburg.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Center for Medical Biometry and Medical Informatics, Medical Center - University of Freiburg</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dpto. Informática y Sistemas, Facultad de Informática, Universidad de Murcia, IMIB-Arrixaca</institution>
          ,
          <addr-line>30100 Murcia</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Fundación para la Formación e Investigación Sanitarias de la Región de Murcia, IMIB-Arrixaca</institution>
          ,
          <addr-line>30003 Murcia</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>OBJECTIVE: To develop a platform that incorporates the benefits of semantic Web technologies into traditional cancer registries. BACKGROUND: Cancer registries are important for research and the management of the cancer treatment. Many technological solutions are available to manage data for cancer registries nowadays, however, the lack of a well-defined common semantic model is a problem when customizable analysis and linking of data to external resources are required. METHODS: OWL ontologies and an RDF repository were employed for the transformation of a cancer registry database into a semantic enabled representation. The feasibility of the approach was tested with simulated data. RESULTS: An ontology representing the semantics of an institutional cancer registry was developed. We implemented a platform where the complex timeline of the patient's disease can be clearly represented. Moreover, the semantic structure of the representation renders it easy to analyse key figures on aggregate patient level. CONCLUSION: The presented platform is an example of the parallel development of ontologies and applications that take advantage of semantic web technologies in the medical field.</p>
      </abstract>
      <kwd-group>
        <kwd>Biomedical Informatics</kwd>
        <kwd>Semantic Web</kwd>
        <kwd>Cancer Registry</kwd>
        <kwd>Ontology</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Regional and epidemiological cancer registries are important for cancer research
and the quality management of cancer treatment. Many technological solutions are
available to collect and analyse data for cancer registries nowadays, however, the lack
of a well-defined common semantic model is a problem when user defined analysis
and linking of data to external resources are required.</p>
      <p>
        To solve this problem, we have designed a semantic model for local cancer
registries and implemented it with semantic web technology in a feasibility study. Our
proposal is based on our previous results and experience working with semantic
technologies. We use OWL [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] ontologies and an RDF [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] repository, for transforming a
traditional cancer registry database into a triple store based on the semantic
information derived from the requirements and the database structure. For semantic retrieval
of data we employ SPARQL [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] queries.
      </p>
      <p>Based on the requirements analysis, an OWL ontology has been developed that
models the semantics of an institutional cancer registry in a pragmatic extensible way.
Based on this model, we have implemented a Semantic Web platform that allows to
transform and store data from cancer registries in RDF repositories. With a graphical
user interface of this platform, users can also formulate incremental user-defined
queries. The query results can be displayed in several customizable ways. The complex
timeline of the disease of individual patients can be clearly represented. Different
events, e.g. different therapies and courses of the disease, are presented according to
their temporal and causal relations. Moreover, the semantic structure of the
representation renders it easy to analyse key figures on aggregate patient level.</p>
      <p>We have applied our approach using the requirements of the cancer registry of the
Comprehensive Cancer Center Freiburg (CCCF)1 and used simulated data to generate
a semantic repository. A prototype web platform has been implemented
demonstrating appropriate functionality and performance.
2
2.1</p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <sec id="sec-2-1">
        <title>Cancer registries</title>
        <p>
          Cancer registries are complex structures for the documentation and analysis of data
from patients diagnosed with cancer [
          <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
          ]. Different types of cancer registry are
organized to collect patient data from institutions (institutional), regions (regional) or
countries (epidemiological). Whereas epidemiological registries provide mainly
population based information on morbidity and mortality, institutional and regional
registries can provide fine-grained information on treatment and conditional survival.
        </p>
        <p>Information of regional cancer registries serves different requirements. Besides
others, the quality control of patient care, the comparison of patient-related outcome
parameters and research support are the most prominent ones. Institutional and
regional registries are also the main data source for epidemiological cancer registries.</p>
        <p>
          Regional cancer registries collect information about the diagnosis, therapies and
course of the disease [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Detailed information on the histo-pathology of the primary
tumor including tumor staging and grading is most important. The longterm follow-up
of the patients' vital status is one of the resource intensive tasks of tumor registries
providing the basis of survival analysis.
        </p>
        <p>Most information is derived from primary documentation aimed at patient care. For
the purpose of structured secondary documentation, tumor documentaries carefully</p>
        <sec id="sec-2-1-1">
          <title>1 http://www.uniklinik-freiburg.de/cccf.html</title>
          <p>
            reprocess primary documentation and code most of the information especially of the
diagnostic and treatment information with clinical coding systems (ICD-10 [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ],
ICDO-3 [
            <xref ref-type="bibr" rid="ref8">8</xref>
            ], TNM [
            <xref ref-type="bibr" rid="ref9">9</xref>
            ], and others). In many countries, a standardized common dataset has
been developed to better support exhaustive data exchange with the epidemiological
cancer registries.
          </p>
          <p>For collection, storage, retrieval and analysis several electronic solutions are
available (e.g. METRIQ2, OncoLog Registry3 or CNEXT4). Proprietary systems have been
developed for large institution. Software for cancer registries has to fulfil a large set
of rapidly changing requirements. Scientific progress and changing legal conditions
complicate the development process and the standardization of cancer registry
software.
2.2</p>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>Standards and Classification Systems</title>
        <p>
          The most important clinical classification system applied in cancer registries is the
ICD-10 (International Statistical Classification of Diseases and Related Health
Problems). This classification system is divided in chapters, with blocks of diseases. For
example, chapter II includes the classification for neoplasms between the blocks C00
and D48. These blocks are subdivided in hierarchies that further specify the diagnosis.
The ICD-O (International Classification of Diseases of Oncology) is a
domainspecific extension of ICD for cancer diseases. The classification system is dual
allowing the coding of topography (tumor site) and morphology of the tumor. This coding
system is of particular interest because SNOMED-CT [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] (Systematized
Nomenclature in Medicine – Clinical Terms) has adopted the ICD-O classification of
morphology.
        </p>
        <p>Several staging systems for cancer have evolved over time and continue to change
with scientific progress. The most important classification system is the TNM
classification for the description of the anatomical extent of the disease. This system is
under constant development of the Union for International Cancer Control (UICC)
and the American Joint Committee on Cancer (AJCC). The TNM stating is based on
the size and/or extent (reach) of the primary tumor (T), the amount of spread to
nearby lymph nodes (N), and the presence of metastasis (M) or secondary tumors formed
by the spread of cancer cells to other parts of the body.</p>
        <p>
          Clinical procedures are coded, e.g., with the ICD10-PCS (Procedure Coding
System) [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. In this system, each code has seven alphanumeric characters. The character
position indicates the clinical classification of the procedure. For example, the first
position is used to define the surgical section; the second position is used to define the
body system.
        </p>
        <sec id="sec-2-2-1">
          <title>2 http://www.elekta.com/healthcare</title>
          <p>professionals/products/elekta-software/cancer-registry.html
3 http://www.oncolog.com/?cid=7
4 http://www.askcnet.org/
2.3</p>
        </sec>
      </sec>
      <sec id="sec-2-3">
        <title>Semantic web technologies</title>
        <p>
          The Semantic Web can be seen as the next-generation web, in which information is
given well-defined meaning, better enabling computers and people to work in
cooperation [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. Ontologies [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] constitute the standard knowledge representation
mechanism for the Semantic Web. Technologies like OWL for the ontology construction
enable a formal representation of the domain.
        </p>
        <p>
          Important international initiatives [
          <xref ref-type="bibr" rid="ref14 ref15">14, 15</xref>
          ] strive to ensure that the Semantic Web
becomes a fundamental system to achieve consistent and meaningful representation,
access, interpretation and exchange of clinical data. The focus of our work lies in the
intersection between the research domains of knowledge management and health
applications, in which there is an increasing use of the semantic web technologies for
managing the knowledge of health information systems. There are a lot of studies that
use semantic web technologies like OWL to represent cancer diseases. To mention
some examples, in [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] an ontology for modeling clinic-genomic trials on cancer has
been developed. In others works [
          <xref ref-type="bibr" rid="ref17 ref18">17, 18</xref>
          ], ontologies that represent a concrete type of
cancer disease have been developed and used in the construction of technical
solutions.
        </p>
        <p>In our approach, we try to take advantage of the best features of the combination of
semantic technologies like OWL and RDF. This means that part of the processing will
be performed using OWL (domain level) and the rest using RDF (data level). For
querying the information we will use SPARQL.
3
3.1</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Methods</title>
      <sec id="sec-3-1">
        <title>Ontology construction</title>
        <p>
          Best practices in ontology engineering recommend to reuse existing and to create
modular ontologies [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. These recommendations are implemented reusing concepts
from different ontologies so that the resulting ontology infrastructure is likely to be a
networked ontology. The OBO Foundry has also developed a series of principles for
ontology construction which propose principles for modularity, orthogonality and
reusability [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ].
        </p>
        <p>Our method for constructing the domain ontology used in this work consisted on
identifying the main entities that should be represented, searching for existing
ontologies containing classes representing these entities, selecting the most appropriate ones
(by our subjective criteria), and extending them when necessary. The final ontology
has been implemented using Protégé5 in OWL-DL, which is the OWL subset based
on Description Logics. By proceeding in this way, the domain knowledge is made
explicit in a set of OWL axioms and therefore ready to be exploited by means of
automated reasoning.</p>
        <sec id="sec-3-1-1">
          <title>5 http://protege.stanford.edu/</title>
          <p>3.2</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>Data transformation and exploitation</title>
        <p>Clinical data are usually stored in relational databases. Different methods and tools
are available for the transformation of relational data into semantic formats like
D2RQ6 or Triplify7. Most approaches perform a syntactical transformation, that is,
they are based on the mappings between the relational and semantic primitives of the
corresponding models resp. languages. Consequently, the meaning of the content is
not really exploited in such transformation processes. In this work, we use a
transformation approach which more likely preserves the meaning of the contents based on
the specification of mappings between the entities of the source relational schema and
the entities of the target domain ontology.</p>
        <p>
          For this purpose, we use SWIT [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ], which is our semantic transformation engine
capable of generating RDF and OWL repositories from both relational and
XMLbased databases. Besides transforming the data, SWIT prevents the generation of
inconsistent semantic data sets with the support of DL reasoners by not transforming
inconsistent source content. The transformation method has three main steps: (1)
definition of the mapping rules between the fields of the database and the ontology; (2)
generation of the OWL data; and (3) importing the OWL data into the semantic data
store. We use Virtuoso8 as data store. Virtuoso has been used in other medical works
as [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. Our semantic data store uses OWL files to save the ontology axioms and an
RDF repository to persist the individuals. This permits separating the semantic model
from the semantic data.
        </p>
        <p>
          SPARQL is used as retrieval language used for expressing and issuing queries over
the data store. We use our ontology-guided input text subsystem called ODS [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] to
facilitate clinicians the exploitation of the data store,. This tool is an editor for
SPARQL queries supported by OWL models. The tool uses the underlying domain
ontologies to show the necessary information to visually define SPARQL queries.
3.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>Generation of simulated data</title>
        <p>In this work, we have generated a set of simulated data of a cancer registry by
using random functions to assign a value of each property of a patient with a diagnosed
cancer. We have ensured that some patients have more than one cancer diagnosis.
Each diagnosis was assigned more than one treatment episode with a maximum
treatment period of twelve months. Plausibility of simulated data was ensured by
rules.
3.4</p>
      </sec>
      <sec id="sec-3-4">
        <title>Semantic profiles</title>
        <p>We define a semantic profile as a set of relations and properties that some
individuals have. Semantic profiles permit to identify groups of patients that share some
6 http://d2rq.org/</p>
        <sec id="sec-3-4-1">
          <title>7 http://triplify.org</title>
        </sec>
        <sec id="sec-3-4-2">
          <title>8 http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/</title>
          <p>properties and are therefore useful for comparing and studying such groups.
Ontologies are of special interest for creating profiles because they allow for aggregation and
selection of individuals from a conceptual perspective.</p>
          <p>In this work, the semantic profiles are built by using the entities defined in a
domain ontology. We have generated two major semantic profiles, namely, timeline
representation of a patient with cancer and aggregated disease timeline representation
of a patient group with some common properties.</p>
        </sec>
      </sec>
      <sec id="sec-3-5">
        <title>Disease timeline of a cancer patient</title>
        <p>In the disease timeline of a patient various health related events occur (e.g.,
diagnosis, patient conditions, therapies and the disease courses). Retrieving these events
of a patient required us to perform some data normalization for representing therapies
by months. Figure 1 shows that every diagnosis has an associated timeline which
includes therapies and the disease course, both ordered by month. E.g., for a breast
cancer patient we can show the timeline with the applied therapies (surgical treatment,
chemotherapy, etc.) for every period. Furthermore, we can show the course of the
disease and its relation with changes in therapy. It also includes the date of the
diagnosis and the date of the last encounter with the patient. At last, the profile contains
the list of all patient diagnoses and a list with the patient conditions, including all its
properties.</p>
      </sec>
      <sec id="sec-3-6">
        <title>Aggregated disease timelines of a group of patients</title>
        <p>The aggregated timelines of a patient group (see Figure 2) include all events of the
selected patients that have the selection criteria in common, for a given period, and
for a concrete diagnosis. An ontology-driven search is performed for the selection of
the patients. This permits to create groups of patients with the same diagnosis,
staging, grading and age range. Second, the semantic profiles of each group member are
obtained. Third, the semantic profiles are globally analyzed to retrieve all data on the
included events. The result is a matrix that contains the disease courses of the
included patients for every month of the disease.</p>
        <p>
          The approach described in the previous section has been applied in an institutional
cancer registry scenario. Based on the requirement analysis [
          <xref ref-type="bibr" rid="ref24 ref25">24, 25</xref>
          ], an ontology was
developed that models the semantics of an institutional cancer registry. We have used
this model and SWIT for transforming and storing simulated data from cancer
registries in a semantic data store. We have implemented a Semantic Web platform that
permits users to formulate incremental user defined queries with a graphical user
interface based in ODS. The query results can be displayed in several customizable
ways, allowing the generation of dashboards on demand. The complex timelines of
the disease of individual and aggregated patients can be clearly represented.
        </p>
        <p>In the last few years, several cancer ontologies have been developed. For the
purposes of this work, we have built a preliminary cancer registry ontology9 based on the
existing ontologies and fulfilling the requirements of a local cancer registry. This first
draft ontology represents some aspects of cancer diseases and their treatment
prag9 http://sele.inf.um.es/ontologies/cancer-registry.owl
matically. The ontology has been defined in OWL-DL. The ontology contains a total
of 335 classes, 18 properties and 29 object properties, with 2.581 logical axioms. The
ontology covers the following classes:
• Patient represents a person with any type of cancer disease. Properties: gender,
birth date, diagnosis, therapies and disease courses.
• Patient condition represents the health condition of a patient at a given time.</p>
        <p>
          Properties: reference date, age, weight, height, Karnofsky index [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ], ASA
index [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] and the menopause status.
• Diagnosis represents the patient diagnosis at a given time. Properties: ICD10
code, grading, staging, therapies, date, pathological structure, anatomical
structure and tumor type.
• Therapy represents the patient therapies of a diagnosis at a given time.
Different kinds of therapy as Chemotherapy, Surgical Treatment, Nuclear Medicine
and others have been modeled in the ontology as subclasses of Therapy class.
        </p>
        <p>
          Properties: medication, start date and end date.
• Disease course represents the patient disease course of a diagnosis at a given
time. Different kinds of course as Complete remission, Progression,
Recurrence and others have been modeled in the ontology as subclasses of Disease
course class. Properties: patient conditions and date.
• The ontology also includes some classes to represent the TNM classification
system of malignant tumors. They include anatomical entities for cancer
grading and staging, e.g. Primary tumor, Regional Lymph Nodes and Distant
Metastasis hierarchies.
• Health Classification System is the superclass of all classes representing
coding artifacts of health related classification systems. To build the taxonomies
of classifications for a cancer registry, we tried to reuse other ontologies. For
the ICD10 code we use the ontology built in [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]. For ICD-O and
ICD10PCS10, we have transformed spreadsheet versions into OWL.
4.2
        </p>
      </sec>
      <sec id="sec-3-7">
        <title>The semantic cancer registry system</title>
        <p>We implemented a prototype system11 based on the methods described in previous
sections. Figure 3 shows the three main parts of this system. The upper part of the
figure shows the data transformation module, which makes use of SWIT to transform
the original data in semantic information stored in the Semantic data store.</p>
        <p>The cancer registry ontology is the core of the system that allows for
computational management of the information related to the cancer patients. All the services
offered by the prototype are implemented on top of this core. The data transformation
requires mapping the source data schema to the cancer registry ontology.</p>
        <p>The lower part of the figure shows the other two modules of the system. The right
one shows the module for the analysis of individual patients, that is, extraction of
profile and timeline analysis. The left one shows the module for the analysis of groups
of patients, which also includes the functionality for graphical access to the disease
10 http://sele.inf.um.es/ontologies/ICD10_PCSv1.owl
11 http://sele.inf.um.es/SECARE/
courses of patient groups. The Ontology Driven Searcher (ODS) permits to create
group of patients with semantic properties in common. The ODS generates charts and
tables with accumulated data of the semantic repository. In this case, the ODS has an
option for adding the concept or property by which to group, so that it can be
considered as a customizable dashboard designer. With this dashboard, the user can select
and aggregate the information on every class of the semantic model. This tool is used
as base for the construction of other services like the graphical representation of the
aggregated timelines of a group of patients or the customizable dashboard.</p>
        <p>The dashboard visualizes the concepts of the model as charted and grouped form. It
is based in the ODS and can generate multiple incremental dashboards on demand.
E.g., the user can generate a pie chart selecting patients by their first therapy. The user
can save any dashboard for querying the results without having to generate it again.</p>
        <p>We have performed an initial evaluation of the system. We have generated a
simulated database with 207.190 patients. The time for the transformation since relational
database to semantic datastore of the simulated data has been thirty-two minutes.
Table 112 shows that the time performance of the semantic datastore is slower than the
relational one for basic queries, without joins. However, when we try to join the data,
the semantic datastore is better than the relational model, even with indexes. The
results obtained when we filter by a property of the class or the table, the semantic
datastore also is faster than the relational one.</p>
      </sec>
      <sec id="sec-3-8">
        <title>Graphical representation of the disease timeline of a patient</title>
        <p>This service permits users to observe the main properties of the timeline of a patient
with a cancer disease. In this view, users can see the details of the diagnosis and of
every applied therapy in each period. Besides, users are provided with two evolution
charts, which are based on the patient course and the Karnofsky index. Figure 4
shows an excerpt of the therapy and course timeline of a patient with pharynx cancer.</p>
      </sec>
      <sec id="sec-3-9">
        <title>Graphical representation of the aggregated disease timeline of a patient group</title>
        <p>12 The test has been realized in a local machine with MySQL 5 as relational database and
Virtuoso 7 as RDF repository.</p>
        <p>Figure 5 shows patient selection and aggregation by the following criteria: male
patients with an age between 50 and 70 diagnosed with colorectal cancer who have
received Chemotherapy.</p>
        <p>After selection and aggregation, the system generates charts that contain the
therapies and the disease courses of the patients. This service can be employed as an
exploratory therapy simulator. Optionally, the entire time matrix can be recalculated by
the selecting a certain therapy. This can help the user to estimate which therapy is
likely to be the most appropriate. Figure 6 shows an excerpt of the first two months of
the therapies analysis panel of a group of 60 patients.</p>
        <p>The main result of this study is the development of a Semantic Web platform that
facilitates the analysis and visualization of data from cancer registries including (1)
the representation of the disease course of a patient, (2) the representation of the
aggregated disease courses of a group of patients, and (3) the definition of customizable
dashboards for patient selection and visualization of the data.</p>
        <p>
          Our approach allows to provide powerful and precise search capabilities assisted
by a customizable dashboard adaptable to the requirements of each user. The query
editor has been developed guided by OWL, providing the user the possibility of
define statements in a more intuitive way than if we used a traditional relational model.
Furthermore, the use of a NoSQL database like an RDF repository allows building a
robust and scalable architecture for big clinical data warehouses [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. Other
important advantage of semantic knowledge modeling is the possibility of sharing
information and comparison of clinical cases and processes.
        </p>
        <p>The use of simulated data has demonstrated the viability of incorporating a local
cancer registry to this model. A comparative performance analysis of relational
databases and semantic repositories demonstrated excellent performance measures for the
semantic repository.</p>
        <p>
          Rule-based systems and logic-based models have been semantic approaches
applied to cancer registries, like analysis of cancer registry processes [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ], quality
assurance [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] and decision support [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]. Our approach innovates by combining traditional
technologies like relational databases and semantic web technologies like OWL and
RDF. We have created an OWL ontology for representing some aspects of an
institutional, local cancer registry. We have developed an RDF repository whose structure is
driven by the OWL ontology and permits to work by exploiting the semantics of the
content, so avoiding the need to care about the relational data structures, which
facilitates the sharing of the content. Our technological infrastructure has permitted us to
develop a semantic searcher for navigating through the complete cancer registry, to
extract semantic profiles of the patients, and to analyze the structure of disease
courses.
        </p>
        <p>One limitation of this work has been to work with a preliminary version of an
ontology of epidemiological cancer data. This ontology needs to be reviewed and
extended, although it has been enough to demonstrate that the semantic exploitation of
this type of clinical data is possible in a robust and scalable way.</p>
        <p>
          Another limitation of this work is the lack of real data to test all the services and
the quality of our domain ontology. The use of real data would enable to (1) test the
performance of the system with a realistic volume of data and (2) evaluate the impact
of missing data in the performance of the system, because cancer registry quality
assurance studies have revealed that they often lack some data [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ]. We plan to
perform a real study with data from a large local cancer registry, which might also
include a clinical validation.
        </p>
        <p>
          Furthermore, we would like to perform term enrichment analyses [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ] to estimate
the use, for instance, of the ICD-10 codes. Finally, we would like to use this model to
generate rules that serve to generate patient groups automatically or for quality
assurance of the data.
6
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>This work demonstrates that the ontologies and the RDF repositories can be
effectively combined for exploiting a local cancer registry. On the one hand, we
constructed an ontology that models the knowledge of local cancer registry. On the other hand,
we have used semantic web technologies for building a platform to analysis the
complex timeline of a patient with cancer. Besides, our semantic structure has allowed
representing the aggregated disease timeline of a patient group.</p>
      <p>The semantic infrastructure has also permitted the generation of graphical
representations of the stored knowledge in the cancer registry with the generation of
customizable dashboards.</p>
      <p>The presented platform is an example of the parallel development of ontologies
and applications that take advantage of semantic web technologies in the medical
field.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This project has been possible thanks to the Spanish Ministry of Science and
Innovation and the FEDER program through grant TIN2010-21388-C02-02 and the
Fundación Séneca through grant 15295/PI/10.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. W3C,
          <article-title>OWL2 web ontology language</article-title>
          . http://www.w3.org/TR/owl2-overview/ (accessed
          <year>September 2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. W3C,
          <article-title>RDF Resource Description Framework</article-title>
          . http://www.w3.org/RDF/ (accessed:
          <year>September 2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. W3C,
          <article-title>SPARQL Query Language for RDF</article-title>
          . http://www.w3.org/TR/rdfsparql-query/ (accesed:
          <year>September 2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Muir</surname>
            <given-names>CS</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nectoux</surname>
            <given-names>J</given-names>
          </string-name>
          .
          <article-title>Role of the cancer registry</article-title>
          .
          <source>Natl Cancer Inst Monogr</source>
          .
          <volume>47</volume>
          :
          <fpage>3</fpage>
          -
          <lpage>6</lpage>
          (
          <year>1977</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Jensen</surname>
            <given-names>OM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whelan</surname>
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Planning</surname>
          </string-name>
          <article-title>a cancer registry</article-title>
          . In
          <string-name>
            <surname>Jensen</surname>
            <given-names>OM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parkin</surname>
            <given-names>DM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maclennan</surname>
            <given-names>R</given-names>
          </string-name>
          et al. eds: Cancer Registration:
          <article-title>Principles and Methods</article-title>
          . Lyon, France: IARC;
          <fpage>22</fpage>
          -
          <lpage>28</lpage>
          (
          <year>1991</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Altmann</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frank</surname>
            <given-names>RK</given-names>
          </string-name>
          .,
          <string-name>
            <surname>Ali</surname>
            <given-names>GT.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Volker</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joachim</surname>
            <given-names>D.</given-names>
          </string-name>
          <article-title>GTDS-a tool for tumor registries to support shared patient care</article-title>
          .
          <source>In Proceedings of the AMIA Annual Fall Symposium</source>
          ,
          <volume>512</volume>
          . American Medical Informatics Association. (
          <year>1996</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>International</given-names>
            <surname>Statistical</surname>
          </string-name>
          <article-title>Classification of Diseases and Related Health Problems 10th Revision (ICD-10)</article-title>
          . http://apps.who.int/classifications/icd10/browse (accessed:
          <year>September 2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>International</surname>
          </string-name>
          <article-title>Classification of Diseases for Oncology, 3rd Edition (ICD-O-3</article-title>
          ). http://www.who.int/classifications/icd/adaptations/oncology/ en/ (accessed:
          <year>July 2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Sobin</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gospodarowicz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wittekind</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>TNM Classification of Malignant Tumors</article-title>
          .
          <source>ISBN: 978-1- 4443-3241-4;</source>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>SNOMED</given-names>
            <surname>Clinical</surname>
          </string-name>
          <article-title>Terms (SNOMED CT)</article-title>
          . http://www.ihtsdo.org/snomedct/ (accessed:
          <year>September 2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <article-title>The 2014 ICD-10-Procedure Coding System (ICD-10-PCS)</article-title>
          . http://www.cms.gov/Medicare/Coding/ICD10/2014-ICD-10- PCS.
          <source>html (accesed: July</source>
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Lassila</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>The semantic web</article-title>
          .
          <source>Scientific American</source>
          ,
          <volume>284</volume>
          ,
          <fpage>34</fpage>
          -
          <lpage>43</lpage>
          (
          <year>2001</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Studer</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Benjamins</surname>
            ,
            <given-names>V. R.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Knowledge engineering: Principles and methods</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          ,
          <volume>25</volume>
          ,
          <fpage>161</fpage>
          -
          <lpage>197</lpage>
          (
          <year>1998</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <given-names>European</given-names>
            <surname>Commission</surname>
          </string-name>
          .
          <article-title>Semantic interoperability for better health and safer healthcare. Deployment and research roadmap for europe</article-title>
          . ISBN-
          <volume>13</volume>
          :
          <fpage>978</fpage>
          -
          <lpage>92</lpage>
          - 79-11139-6; (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. SemanticHealthNet. http://www.semantichealthnet.eu/ (accessed:
          <year>September 2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Brochhausen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spear</surname>
          </string-name>
          , AD.,
          <string-name>
            <surname>Cocos</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , et al.:
          <article-title>The ACGT Master Ontology and its application - Towards an ontology-driven cancer research and management system</article-title>
          .
          <source>Journal of Biomedical Informatics</source>
          ,
          <volume>44</volume>
          ,
          <fpage>8</fpage>
          -
          <lpage>25</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Min</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , Manion,
          <string-name>
            <given-names>FJ.</given-names>
            ,
            <surname>Goralczyk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Wong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Ross</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Beck</surname>
          </string-name>
          , JR.:
          <article-title>Integration of prostate cancer clinical data using an ontology</article-title>
          .
          <source>Journal of Biomedical Informatics</source>
          ,
          <volume>42</volume>
          ,
          <fpage>1035</fpage>
          -
          <lpage>1045</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Abidi</surname>
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Ontology-Based modeling of Breast Cancer follow-up Clinical Practice Guideline for providing Clinical Decision Support. Computer-Based medical systems</article-title>
          , CBMS'
          <volume>07</volume>
          ,
          <fpage>542</fpage>
          -
          <lpage>547</lpage>
          (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Rector</surname>
            <given-names>AL</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brandt</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Drummond</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horridge</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Puleston</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stevens</surname>
            <given-names>R</given-names>
          </string-name>
          .
          <article-title>Engineering use cases for modular development of ontologies in OWL</article-title>
          .
          <source>Applied Ontology</source>
          <year>2012</year>
          ,
          <volume>7</volume>
          (
          <issue>2</issue>
          ):
          <fpage>113</fpage>
          -
          <lpage>132</lpage>
          (
          <year>2002</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ashburner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosse</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bard</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bug</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ceusters</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , ... &amp;
          <string-name>
            <surname>Lewis</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <article-title>The OBO Foundry: coordinated evolution of ontologies to support biomedical data integration</article-title>
          .
          <source>Nature biotechnology</source>
          ,
          <volume>25</volume>
          (
          <issue>11</issue>
          ),
          <fpage>1251</fpage>
          -
          <lpage>1255</lpage>
          (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Miñarro-Giménez</surname>
          </string-name>
          . JA.,
          <string-name>
            <surname>Fernández-Breis</surname>
            <given-names>JT</given-names>
          </string-name>
          .:
          <article-title>Ontology-driven Method for Integrating Biomedical Repositories</article-title>
          , Lecture Notes in Computer Science.
          <volume>7023</volume>
          ,
          <fpage>473</fpage>
          -
          <lpage>482</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Rea</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pathak</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savova</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oniki</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Westberg</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beebe</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tao</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parker</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haug</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huff</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chute</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Building a robust, scalable and standards-driven infrastructure for secondary use of EHR data: The SHARPn project</article-title>
          ,
          <source>Journal of Biomedical Informatics</source>
          .
          <volume>45</volume>
          ,
          <fpage>736</fpage>
          -
          <lpage>771</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Esteban-Gil</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garcia-Sanchez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Valencia-Garcia</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , Fernandez-Breis, JT.:
          <article-title>SocialBROKER: A collaborative social space for gathering semantically-enhanced financial information</article-title>
          ,
          <source>Expert Systems with Applications</source>
          .
          <volume>39</volume>
          ,
          <fpage>9715</fpage>
          -
          <lpage>9722</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Dorn</surname>
            ,
            <given-names>HF.</given-names>
          </string-name>
          <article-title>The Use of Statistics in Cancer Control Programs</article-title>
          .
          <source>American Journal of Public Health and the Nations Health</source>
          <volume>39</volume>
          (
          <issue>5</issue>
          _Pt_1):
          <fpage>602</fpage>
          -
          <lpage>606</lpage>
          (
          <year>1949</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Neitlich</surname>
          </string-name>
          , HW.,
          <string-name>
            <surname>Stephen</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vincent</surname>
            <given-names>J.O.. “</given-names>
          </string-name>
          <article-title>Development of a regional computerized cancer registry and its impact on medical care”</article-title>
          .
          <source>Journal of Medical Systems</source>
          <volume>7</volume>
          (
          <issue>3</issue>
          ):
          <fpage>251</fpage>
          -
          <lpage>255</lpage>
          . (
          <year>1983</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Yates</surname>
            <given-names>JW</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chalmer</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McKegney</surname>
            <given-names>FP</given-names>
          </string-name>
          .
          <article-title>Evaluation of patients with advanced cancer using the Karnofsky performance status</article-title>
          .
          <source>Cancer</source>
          .
          <volume>45</volume>
          ,
          <fpage>2220</fpage>
          -
          <lpage>2224</lpage>
          (
          <year>1980</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <article-title>ASA Physical Status Classification System</article-title>
          . https://www.asahq.org/clinical/physicalstatus.
          <source>htm (accessed: July</source>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Cardillo</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tamilin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eccher</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Serafini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          : ICD-10 Ontology, https://dkm.fbk.eu/technologies/icd-10
          <source>-ontology (accessed: July</source>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Shiki</surname>
          </string-name>
          , Naomi, Yuko Ohno, Ayumi Fujii,
          <source>Taizo Murata und Yasushi Matsumura</source>
          .
          <year>2008</year>
          .
          <article-title>Unified Modeling Language (UML) for hospital-based cancer registration processes</article-title>
          .
          <source>Asian Pacific Journal of Cancer Prevention</source>
          <volume>9</volume>
          :
          <fpage>789</fpage>
          -
          <lpage>796</lpage>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Caldarella</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gianni</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Catia</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Crocetti</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Di Costanzo</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , et al.
          <article-title>Feasibility of evaluating quality cancer care using registry data and electronic health records: a populationbased study”</article-title>
          .
          <source>International Journal for Quality in Health Care: mzs020</source>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Tafazzoli</surname>
            ,
            <given-names>A. G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Altmann</surname>
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wächter</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , Katz, FR.,
          <string-name>
            <surname>Hölzer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dudeck</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Integrated knowledge-based functions in a hospital cancer registry-specific requirements for routine applicability</article-title>
          .
          <source>Proceedings of the AMIA Symposium:</source>
          <fpage>410</fpage>
          -
          <lpage>414</lpage>
          . (
          <year>1999</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Boyle</surname>
          </string-name>
          , EI., et al.:
          <article-title>GO::TermFinder-open source software for accesing Gene Ontology information and finding significantly enriched Gene Ontology terms associated with a list of genes</article-title>
          .
          <source>Bioinformatics</source>
          ,
          <volume>20</volume>
          (
          <issue>18</issue>
          ),
          <fpage>3710</fpage>
          -
          <lpage>3715</lpage>
          (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>