<!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>keyCRF: Using Semantic Metadata Registries to Populate an eCRF with EHR Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gokce B. Laleci Erturkmen</string-name>
          <email>gokce@srdc.com.tr</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Landen Bain</string-name>
          <email>lbain@cdisc.org</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anil Sinaci</string-name>
          <email>anil@srdc.com.tr</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>SRDC Ltd.</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ankara</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Turkey</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>CIDISC</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>The goal of the keyCRF project is the creation of a semantically annotated electronic Case Report Form (eCRF) that can enable the pre-population of the eCRF from data elements in an EHR summary document through the use of semantically linked Common Data Element definitions across care and research domains</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
    </sec>
    <sec id="sec-2">
      <title>Methods and Expected Results</title>
      <p>
        One of the core activities of keyCRF project is to identify a sample set of CDEs in research sites that are often used to
annotate eCRF forms, and the corresponding CDEs at clinical care site, and semantically linking them through a
semantically enabled metadata registry implemented in conformance to ISO/IEC 11179 standard. We will be using the
semantic MDR implementation provided by SALUS project [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] that enables mapping of CDEs managed by different
domains through skos terms such as skos:exactMatch and skos:closeMatch. The activities being carried out can be
summarized as:
• Examine the sample eCRF form provided by CDISC and identify the CDEs at research sites from the common
CDASH and SDTM annotations of eCRF forms, such as “DM.Sex.Char” to indicate gender code in demographics
domain.
• Examine CEDD repository, to find out the corresponding CDEs to the selected research CDEs, for example
“PatientInformation.PatientAdministrativeGender.CE” to “DM.Sex.Char””
• Represent all these CDEs in a 11179 supporting MDR, by also semantically linking them with skos terms
• Define extraction specifications of the selected CEDD CDEs from C-CDA as XPATHS
      </p>
      <p>By making use of these definitions available from a semantic MDR that also supports IHE DEX as a standard
means to retrieve metadata of CDEs, we demonstrate that it is possible to pre-fill an electronic case report form by
reusing the medical history available as follows: A research forms designer becomes able to build a case report form for
a particular research study by referring to an on-line metadata registry of research data elements, and selects the
desired data elements from a set of research friendly elements such as CDASH. He then retrieves the metadata defined
by the metadata registry into an annotated case report form through the use of IHE DEX profile. The metadata
includes the exact specification, using XPath, to find the corresponding data element in the C-CDA. The semantic MDR
creates the metadata by checking the semantic links of CDASH data elements to CEDD data elements, which already
have mappings to C-CDA documents. Using the XPath statements, the research system creates an extraction
specification for all elements to be extracted from the C-CDA. The demonstration will employ the well-known mechanism
of IHE RFD to define the necessary transactions between the EHR and the research system. The extraction
specification could then be used with IHE RFD to pre-populate the case report form.</p>
      <p>This prototype demonstration will show industry the value of the semantic approach to address the challenge of
secondary use of EHR for research purposes.
7. S&amp;I Framework. S&amp;I Clinical Element Data Dictionary (CEDD) WG,
http://wiki.siframework.org/S%26I+Clinical+Element+Data+Dictionary+WG
8. EHR Enabled Research, http://www.phusewiki.org/wiki/index.php?title=EHR_Enabled_Research
9. IHE Data Exchange (DEX) Profile,
http://www.ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_DEX_Rev10_PC_2013-06-03.pdf
10. IHE Retrieve Form for Data Capture Profile,
http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_RFD_Rev22_TI_2011-08-19.pdf</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Sinaci</surname>
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laleci Erturkmen G.B,</surname>
          </string-name>
          <article-title>A federated semantic metadata registry framework for enabling interoperability across clinical research and care domains</article-title>
          .
          <source>J Biomed Inform</source>
          . 2013 Oct;
          <volume>46</volume>
          (
          <issue>5</issue>
          ):
          <fpage>784</fpage>
          -
          <lpage>94</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. CDISC.
          <article-title>Study Data Tabulation Model (SDTM)</article-title>
          , http://www.cdisc.org/sdtm
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. CDISC.
          <article-title>Clinical Data Acquisition Standards Harmonization (CDASH)</article-title>
          ,http://www.cdisc.org/cdash
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>HITSP</surname>
          </string-name>
          . C 154:
          <article-title>HITSP Data Dictionary</article-title>
          , http://www.hitsp.org/ConstructSet_Details.aspx?&amp;
          <source>PrefixAlpha=4&amp;PrefixNumeric =154</source>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>HITSP</surname>
          </string-name>
          . C 32:
          <article-title>HITSP Summary Documents Using HL7 Continuity of Care Document (CCD) Component</article-title>
          , http://www.hitsp.org/ConstructSet_Details.aspx?&amp;
          <source>PrefixAlpha=4&amp;PrefixNumeric=32</source>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>6. HL7 Implementation Guide for CDA® Release 2</article-title>
          :
          <string-name>
            <given-names>IHE</given-names>
            <surname>Health Story</surname>
          </string-name>
          <string-name>
            <surname>Consolidation</surname>
          </string-name>
          ,
          <source>Release</source>
          <volume>1</volume>
          .
          <fpage>1</fpage>
          -
          <string-name>
            <given-names>US</given-names>
            <surname>Realm</surname>
          </string-name>
          , http://www.hl7.org/implement/standards/product_brief.
          <source>cfm?product_id=258</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>