<!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>EHR4CR: A semantic web based interoperability approach for reusing electronic healthcare records in protocol feasibility studies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sajjad Hussain</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Ouagne</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eric Sadou</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thierry Dart</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marie-Christine Jaulent</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Boris De Vloed</string-name>
          <email>boris.devloed@agfa.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dirk Colaert</string-name>
          <email>dirk.colaert@agfa.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christel Daniel</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Advanced Clinical Application Group AGFA Healthcare</institution>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>INSERM, UMR_S 872, Eq. 20, Centre de Recherche des Cordeliers</institution>
          ,
          <addr-line>Paris</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A major barrier to repurposing routinely collected data for clinical research is the heterogeneity of healthcare information systems. Electronic Health Record for Clinical Research (EHR4CR) is a European project designed to improve the efficiency of conducting clinical trials. We propose an initial architecture of the EHR4CR Semantic Interoperability Framework using Semantic Web technologies. We used a model-driven engineering approach to build the semantic resources and derived an HL7-based EHR4CR information model. We plan to apply existing ontology modularization techniques for obtaining relevant set of common data elements and clinical terminologies bound to our ERH4CR information model. EHR4CR platform provides semantic interoperability services that facilitate the process of defining eligibility criteria based on standard terminologies and then transforming and executing the user-defined SPARQL queries on RDF triplestore representing local EHRs. We plan to evaluate our semantic interoperability framework for patient eligibility determination in the context of 10 clinical trials running in 11 health institutions.</p>
      </abstract>
      <kwd-group>
        <kwd>Clinical research</kwd>
        <kwd>semantic interoperability</kwd>
        <kwd>electronic health record</kwd>
        <kwd>clinical data warehouses</kwd>
        <kwd>eligibility criteria</kwd>
        <kwd>controlled vocabulary</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        A major barrier to repurposing clinical data directly from Electronic Health Records
(EHRs) or from Clinical Data Warehouses (CDWs) during clinical trial design and
execution is that information systems in both domains – patient care and clinical
research – use different information representations and terminology systems [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The
collective efforts of multiple organizations (such as ISO, HL7, CDISC, etc) are
currently focused on defining various standards required to achieve semantic
interoperability and bridge the gap between clinical research and patient care by defining
mappings between their data schemes [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. However, the current scope of published
mappings is limited. In the context of patient eligibility, due to the emerging requirements
for representing new eligibility criteria from different domain areas, new mappings
are needed [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. We argue that integrating patient care and clinical research domains
requires a standard-based and scalable semantic interoperability framework, allowing
dynamic mappings between data structures and semantics of varying data sources.
      </p>
      <p>
        The EHR4CR (Electronic Health Records for Clinical Research) project aims to
improve the efficiency and reduce the cost of conducting clinical trials, through better
leveraging of routinely collected clinical data in the trial design and execution
lifecycle [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In this paper, we propose an initial architecture of the EHR4CR Semantic
Interoperability Framework using Semantic Web technologies. EHR4CR platform
provides semantic interoperability services that facilitate the process of defining
eligibility criteria based on standard terminologies and then transforming and executing
the user-defined SPARQL queries on RDF triplestore representing local EHR/CDWs.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work: Bridging standards and semantic interoperability approaches</title>
      <p>
        There have been various attempts in establishing semantic interoperability,
developing different approaches for bridging clinical care and clinical research [
        <xref ref-type="bibr" rid="ref5 ref6 ref7 ref8">5-8</xref>
        ]. In this
regard, one of the prominent attempts is the Shared Health Research Information
Network (SHRINE), offering the SHRINE Ontology Mapping Tool (SHRIMP) for
creating association mappings between local and standard vocabularies, and allowing
researchers to define distributed queries over a federated network of i2b2 systems
across multiple institutions [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The PONTE project focuses on developing advanced
tools for semantic interoperability between clinical research and EHR data, which
takes into consideration all widely used standards, such as coding systems,
terminologies, vocabularies as well as health messaging standards such as HL7 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The
Linked2Safety project aims, similar objectives being targeted in EHR4CR, to advance
clinical practice and accelerate medical research, by providing pharmaceutical
companies, healthcare professionals and patients an innovative semantic interoperability
framework facilitating the efficient and homogenized access to distributed EHRs [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
A recently launched EURECA project aims to enable seamless, secure, scalable and
consistent linkage of healthcare information residing in EHR systems with
information in clinical research information systems [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>
        Current interoperability efforts in both patient care and clinical research include
defining metadata and vocabulary standards and using these to define Common Data
Elements (CDEs) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. The CDISC SHARE project aims at building a metadata
repository of CDEs based on the BRIDG model and its underlying mapping to the HL7
RIM. Another initiative is the Ontology of Clinical Research (OCRe), which provides
methods for binding external information standards (e.g. BRIDG) and clinical
terminologies (e.g. SNOMED CT) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. A recently launched initiative, Fast Health
Interoperability Resources (FHIR) [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], offers the use of RDF-modeled core FHIR resources,
and provides a semantic harmonization framework for establishing semantic
interoperability between clinical research and patient care domains. To demonstrate the value
of Semantic Web (SW) specifications in bridging patient care and clinical research, a
W3C task on Clinical Observations Interoperability was established [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. As a use
case for secondary use of EHRs for clinical research, checking clinical trial eligibility
for patient recruitment was chosen and a prototype implementation was achieved. In
line with this approach, we propose EHR4CR semantic interoperability framework
based on SW technologies, where in our case, we define the mappings between
standard clinical terminologies and local EHR terminologies, and use an HL7 based
information model as a standard interface for querying heterogeneous CDWs.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>EHR4CR Semantic Interoperability Framework</title>
      <p>
        We propose the EHR4CR Semantic Interoperability Framework for consistent
interpretation of clinical data accessed from varying sources (see Figure 1). A
templatebased query interface at the User Workbench allows clinical researchers to define
eligibility criteria based on standard terminologies, data elements and value sets using
the EHR4CR Terminology Services. The defined set of eligibility criteria are
represented as SPARQL queries. For querying heterogeneous CDWs through a standard
interface, we adopted the «A_SupportingClinicalStatementUniversal» model,
component of the StudyDesign, proposed by the HL7 Regulated Clinical Research
Information Model (RCRIM) Work Group [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Structures and Value Sets of Common
Data Elements (CDEs) are defined in order to specify additional constraints on the
high-level EHR4CR information model and to represent the fine-grained clinical
information included in eligibility criteria constructs. Based on the pre-defined
terminology mappings in the terminology server, we expand and transform the initial
SPARQL queries based on the local CDW schemas, and execute them across different
CDWs. We transform the query results based on the standardized terminologies, and
then display them at the User Workbench. The key elements are discussed as follows.
Standard clinical terminologies – such as SNOMED CT, LOINC, ICD-10, PathLex,
ATC, etc – contain numerous clinical concepts usually organized in a hierarchy and
interconnected by domain specific relations, provides a comprehensive medical
knowledgebase. However, in particular use-cases and applications only a small
fraction of these terminologies are required. Therefore, there have been efforts towards
modularizing and extracting disease-specific ontology modules [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. In addition, Del
Vescovo et. al. demonstrated a large scale investigation into the modular structure of
state-of-the-art biomedical ontologies, by using their proposed notion of atomic
decomposition, and extracting relevant and “logically complete” fragments from source
ontologies [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. In order to incorporate the use of standard clinical terminologies in
EHR4CR, we plan to investigate the state-of-the art modularization approaches and
utilize them for extracting modules that represents those terminology fragments that
cover only our domains of interest – i.e. Patient Care and Clinical Research. The
extracted terminology modules will be uploaded into EHR4CR terminology server.
3.2
      </p>
      <sec id="sec-3-1">
        <title>Building SPARQL Query Endpoint based on heterogeneous CDW Models</title>
        <p>
          For building a SPARQL endpoint, Mate et. al. demonstrated the use of SW standards
in populating i2b2-based CDWs from heterogeneous EHRs [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. In EHR4CR, we
query patient data from heterogeneous CDWs using SPARQL endpoints that directly
expose the CDW schema as RDF. Immediately formalizing the relational database
(RDB) model of EHR into a CDW represented as RDF triplestore creates the
possibility to use SW technologies – such as defining rules for reasoning and performing
        </p>
        <sec id="sec-3-1-1">
          <title>Query Result Transformation and Aggregation. The RDB-to-RDF mapping [16] en</title>
          <p>
            sures the same semantics between the SPARQL endpoints and the RDB, and in this
case provides a one-to-one mapping, where: (i) a database table is mapped to an
RDFS class (rdfs:Class), (ii) a database table column is mapped to an RDF property
(rdf:Property), and (iii) the database data type of a field is mapped to the XSD data
type range class of the property; with an exception: if a field is a foreign key, its range
is the class that the foreign key points to. Consequently the process of creating an
ontology that describes the CDW model can be automated as discussed in [
            <xref ref-type="bibr" rid="ref17">17</xref>
            ].
3.3
          </p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>EHR4CR Semantic Interoperability Services</title>
        <p>In order to establish semantic interoperability between data elements describing
eligibility criteria and patient data, we are currently developing the following services.</p>
        <sec id="sec-3-2-1">
          <title>3.3.1. Terminology Services</title>
          <p>For constructing the user-defined eligibility criteria at the Workbench, we build
terminology services for selecting preferred medical terminologies and value sets:
 Terminology Management Service incorporates extracted modules from standard
clinical terminologies (LOINC, SNOMED CT, ICD-10, HL7 vocabulary, PathLex,
ATC) by loading their schema models through standard protocols.
 Terminology Selection Service allows users to select the preferred terminology in
which the user wants to define the eligibility criteria.
 Terminology Browsing Service allows users to browse the appropriate terminology
concepts and attached value sets for defining eligibility criteria.
 Terminology Mapping Service manages and provides concept mappings between</p>
          <p>EHR4CR terminology and local EHR/CDW terminologies.</p>
        </sec>
        <sec id="sec-3-2-2">
          <title>3.3.2. Query Expansion &amp; Transformation Service</title>
          <p>
            In different clinical terminologies, medical concepts are organized with varied
granularities, therefore while querying based on heterogeneous clinical terminologies,
query expansion becomes a crucial task [
            <xref ref-type="bibr" rid="ref18">18</xref>
            ]. In our work, using the EHR4CR
terminology services, we perform query expansion on the user-defined SPARQL
queries by walking through terminology hierarchies for a specific terminology
concept to incorporate its narrower concepts (i.e. sub-concepts) into the query set. By
using the Query Expansion &amp; Transformation Service, we transform the expanded
SPARQL queries based on local CDWs terminology, which can then be executed
across different CDWs to obtain more comprehensive query results.
          </p>
        </sec>
        <sec id="sec-3-2-3">
          <title>3.3.3. Result Transformation and Aggregation Service</title>
          <p>This service is designed to translate back the query-results obtained from various
CDWs into an integrated result format based on the standardized medical vocabulary
representing the initially given eligibility criteria. It invokes Terminology Mapping
Services to retrieve mappings from local to central terminology codes, and also
performs necessary unit and measurement conversions among query results.
4</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Discussion &amp; Conclusion</title>
      <p>
        In this paper, we present EHR4CR semantic interoperability approach for bridging the
clinical care and clinical research domains. In course of developing this framework,
we face several challenges: (i) formally defining patient eligibility criteria including
temporal constraints [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], (ii) dealing with heterogeneity between different EHRs,
(iii) defining mappings between data elements from eligibility criteria and patient
data, and (iv) investigating standard query interfaces for retrieving patient information
from heterogeneous EHRs. We also need to continue our efforts at harmonizing the
EHR4CR Information Model, common data elements and terminology to other
standard-based semantic resources including FHIR, BRIDG, CDISC SHARE (and other
meta data repository initiatives such as caDSR, openMDR, eMERGE) and the
Ontology of Clinical Research (OCRe) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>Our preliminary investigations of 11 hospital EHR systems across Europe suggest
variable quality in the collection of data items most frequently used as eligibility
criteria. However, taken together, queries across multiple eligibility criteria are expected
to result in a significant improvement in the accuracy of patient number estimations
than present approaches. We will be conducting these and other evaluations more
formally later in the project, and will report the results in later publications.
Acknowledgements. The research leading to these results has received support from
the Innovative Medicines Initiative Joint Undertaking under grant agreement n° [No
115189], resources of which are composed of financial contribution from the
European Union's Seventh Framework Programme (FP7/2007-2013) and EFPIA companies’
in kind contribution.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Prokosch</surname>
            <given-names>HU</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganslandt</surname>
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Perspectives for medical informatics. Reusing the electronic medical record for clinical research</article-title>
          .
          <source>Methods Inf Med</source>
          .
          <volume>48</volume>
          (
          <issue>1</issue>
          ):
          <fpage>38</fpage>
          -
          <lpage>44</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Fridsma</surname>
            <given-names>DB.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Evans</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hastak</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mead</surname>
            <given-names>CN</given-names>
          </string-name>
          .:
          <article-title>The BRIDG project: a technical report</article-title>
          .
          <source>J Am Med Inform Assoc</source>
          .
          <volume>15</volume>
          (
          <issue>2</issue>
          ):
          <fpage>130</fpage>
          -
          <lpage>7</lpage>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>El</given-names>
            <surname>Fadly</surname>
          </string-name>
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Rance</surname>
          </string-name>
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Lucas</surname>
          </string-name>
          <string-name>
            <given-names>N.</given-names>
            ,
            <surname>Mead</surname>
          </string-name>
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Chatellier</surname>
          </string-name>
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Lastic</surname>
          </string-name>
          <string-name>
            <given-names>P.Y.</given-names>
            ,
            <surname>Jaulent</surname>
          </string-name>
          <string-name>
            <given-names>M.C.</given-names>
            ,
            <surname>Daniel</surname>
          </string-name>
          <string-name>
            <surname>C.</surname>
          </string-name>
          :
          <article-title>Integrating clinical research with the Healthcare Enterprise: From the RE-USE project to the EHR4CR platform</article-title>
          .
          <source>J Biomed Inform. Dec;44 Suppl</source>
          <volume>1</volume>
          :
          <fpage>S94</fpage>
          -
          <lpage>S102</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Electronic</given-names>
            <surname>Healthcare</surname>
          </string-name>
          <article-title>Record for Clinical Research (EHR4CR) [Online]</article-title>
          . Available: http://www.ehr4cr.eu/
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Weber</surname>
            <given-names>GM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Murphy</surname>
            <given-names>SN</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McMurry</surname>
            <given-names>AJ</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Macfadden</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nigrin</surname>
            <given-names>DJ</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Churchill</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kohane</surname>
            <given-names>IS</given-names>
          </string-name>
          .:
          <article-title>The Shared Health Research Information Network (SHRINE): a prototype federated query tool for clinical data repositories</article-title>
          .
          <source>J Am Med Inform Assoc</source>
          .
          <volume>16</volume>
          (
          <issue>5</issue>
          ):
          <fpage>624</fpage>
          -
          <lpage>30</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>PONTE</given-names>
            <surname>Project</surname>
          </string-name>
          [Online]. Available: http://www.ponte-project.eu/
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Antoniades</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Georgousopoulos</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Forgo</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aristodimou</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tozzi</surname>
            <given-names>F</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hasapis</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perakis</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bouras</surname>
            <given-names>T</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alexandrou</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kamateri</surname>
            <given-names>E</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panopoulou</surname>
            <given-names>E</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tarabanis</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pattichis</surname>
            <given-names>C.</given-names>
          </string-name>
          <article-title>Linked2Safety: A secure linked data medical information space for semanticallyinterconnecting EHRs advancing patients' safety in medical research</article-title>
          , International Conference on Bioinformatics and Bioengineering, Larnaka, Cyprus,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>EURECA</given-names>
            <surname>Project</surname>
          </string-name>
          [Online]. Available: http://eurecaproject.eu/
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Sim</surname>
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carini</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tu</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wynden</surname>
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pollock</surname>
            <given-names>B.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mollah</surname>
            <given-names>S.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gabriel</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hagler</surname>
            <given-names>H.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scheuermann</surname>
            <given-names>R.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
            <given-names>H.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wittkowski</surname>
            <given-names>K.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nahm</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bakken</surname>
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The human studies database project: federating human studies design data using the ontology of clinical research</article-title>
          .
          <source>AMIA Summits Transl Sci Proc. Mar</source>
          <volume>1</volume>
          ;
          <year>2010</year>
          :
          <fpage>51</fpage>
          -
          <lpage>5</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>Fast Health Interoperability Resources (FHIR)</article-title>
          . [Online]. Available: http://www.hl7.org/implement/standards/fhir/fhir-book.htm
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <article-title>W3C task on Clinical Observations Interoperability (COI) [Online]</article-title>
          . Available: http://esw.w3.org/HCLS/ClinicalObservationsInteroperability http://www.w3.org/blog/hcls/
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>HL7 Regulated Clinical Research Information Model (RCRIM) Work</surname>
            <given-names>Group</given-names>
          </string-name>
          [Online]. http://wiki.hl7.org/index.php?title=Regulated_Clinical_Research_Information_Management
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Milian</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Aleksovski</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Vdovjak</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Teije</surname>
          </string-name>
          , A. ten ; and
          <string-name>
            <surname>Harmelen</surname>
          </string-name>
          , F. van 2.:
          <article-title>Identifying disease-centric subdomains in very large medical ontologies</article-title>
          .
          <source>Or: finding 2500 out of 300.000. workshop on Knowledge Representation for Healthcare</source>
          , Springer Verlag (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Del Vescovo</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gessler</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klinov</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sattler</surname>
            <given-names>U</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schneider</surname>
            <given-names>T</given-names>
          </string-name>
          , and
          <article-title>Winget A. Decomposition and Modular Structure of BioPortal Ontologies</article-title>
          .
          <source>International Semantic Web Conference (1)</source>
          :
          <fpage>130</fpage>
          -
          <lpage>145</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Mate</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bürkle</surname>
            <given-names>T</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Köpcke</surname>
            <given-names>F</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breil</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wullich</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dugas</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prokosch</surname>
            <given-names>HU</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganslandt</surname>
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Populating the i2b2 database with heterogeneous EMR data: a semantic network approach</article-title>
          .
          <source>Stud Health Technol Inform</source>
          .
          <volume>169</volume>
          :
          <fpage>502</fpage>
          -
          <lpage>6</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. R2RML:
          <article-title>RDB to RDF Mapping Language</article-title>
          . http://www.w3.org/TR/r2rml/
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Sun</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Depraetere</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Roo</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Vloed</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mels</surname>
            <given-names>G</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Colaert</surname>
            <given-names>D.</given-names>
          </string-name>
          <article-title>Semantic integration and analysis of clinical data</article-title>
          .
          <source>eprint arXiv:1210.4405</source>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Bettembourg</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Diot</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burgun</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dameron</surname>
            <given-names>O.:</given-names>
          </string-name>
          <article-title>GO2PUB: Querying PubMed with semantic expansion of gene ontology terms</article-title>
          .
          <source>Journal of Biomedical Semantics</source>
          <volume>3</volume>
          :
          <issue>7</issue>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Boland</surname>
            <given-names>MR.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tu</surname>
            <given-names>SW</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carini</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sim</surname>
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weng</surname>
            <given-names>C.</given-names>
          </string-name>
          :
          <string-name>
            <surname>EliXR-TIME</surname>
          </string-name>
          :
          <article-title>A Temporal Knowledge Representation for Clinical Research Eligibility Criteria</article-title>
          ,
          <source>Proc of AMIA 2012 Clinical Research Informatics Summit</source>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>