Difference between revisions of "Data Element Exchange"

Latest revision as of 09:20, 2 August 2017

Data Element Exchange leverages the concept of a metadata registry to add mapping metadata to an annotated data capture form at the point of form design instead of the exchange of data instances.

Data Element Exchange Recording

Summary

To enable clinical research, public health, and quality assessment studies through secondary use of EHR, a mechanism is needed to map EHR data to secondary domain meanings. Integrating patient care and clinical research domains requires a standard-based expressive and scalable interoperability framework for sharing the semantics of the data elements used in patient care and clinical research domains and their mapping to varying data sources. DEX profile enables this through a metadata registry architecture where machine processable definitions of data elements (i.e. metadata) across domains can be shared to address this interoperability challenge to move towards EHR-enabled research. DEX enables retrieving metadata definitions of data elements including “extraction specifications” for a data element defined in a selected domain (like SDTM data elements), from an implementation dependent content model in another domain (like HL7 CCD). As an example, an RFD form Manager can locate the exact mappings of the data elements in the research data set to a pre-population data set provided in HL7 CCD format.

Benefits

Standardized interaction with a metadata registry to search and retrieve metadata definitions
Flexible mapping between clinical research and patient care data elements
Enables dynamic pre-population of clinical research, public health, and quality assessment forms from pre-population data provided by EHR systems as medical summaries

Details

This profile leverages the power of an ISO/IEC 11179 Metadata Registry to search and retrieve data element metadata. The objective is to facilitate creation of annotated data capture form at the point of form design by adding mapping metadata for the data elements in a data capture form to the content models used in clinical care domain. The metadata registry such as CDISC SHARE can serve as the Metadata Source in this profile will define and maintain correspondences between research and healthcare data elements, and will provide an exact map by which an RFD Form Manager can extract data from the pre-population data set.

An electronic data capture system or a research protocol design system would host the Metadata Consumer actor, to query the Metadata Source actor to retrieve the list of data elements hosted and retrieve the metadata of a selected data element including the exact mapping path of the selected data element instance in a content model like HL7 CCD. These mappings would be used to create the annotated data capture forms at the point of form design.

Systems Affected

Metadata Registries may define and maintain metadata of data elements including the correspondences between research and healthcare data elements.

Electronic Data Capture system may query the Metadata Source for a list of Data Elements matching a selection criteria, and may retrieve the metadata of the selected data element.

Metadata Consumer The Metadata Consumer is responsible for the importation of metadata created by the Metadata Source. The Metadata Consumer can optionally query the Metadata Source for a list of Data Elements matching a selection criteria.

Metadata Source The Metadata Source is responsible for creation of the Data Element list matching a selection criteria and the creation of metadata for a selected Data Element per request from the Metadata Consumer. The Metadata Source is associated with a metadata registry.

Specification

Profile Status: Profile Status: Trial Implementation

Documents:

Data Element Exchange (DEX) -Supplement for Trial Implementation- Published 2013-09-13

Underlying Standards:

ISO/IEC 11179: Information Technology – Metadata Registries (MDR) Parts 1–6 (3rd Edition).
IETF RFC2616 HyperText Transfer Protocol HTTP/1.1
Extensible Markup Language (XML) 1.0 (Second Edition). W3C Recommendation 6 October 2000. http://www.w3.org/TR/REC-xml.
Web Services Description Language (WSDL) 1.1. W3C Note 15 March 2001. http://www.w3.org/TR/wsdl.
SOAP 1.2 Second Edition, W3C Recommendation 27 April 2007. http://www.w3.org/TR/soap12-part1
IEEE Std 1003.2 IEEE Standard for Information Technology — Portable Operating System Interface (POSIX®) — Part 2: Shell and Utilities — Amendment 1: Batch Environment -Description

@@ Line 1: / Line 1: @@
 Data Element Exchange leverages the concept of a metadata registry to add mapping metadata to an annotated data capture form at the point of form design instead of the exchange of data instances.
+'''[https://ihe.webex.com/ihe/lsr.php?RCID=d026bb7ef325f64fec84498eda8c9b87 Data Element Exchange Recording]'''
 __TOC__
@@ Line 16: / Line 18: @@
 This profile leverages the power of an ISO/IEC 11179 Metadata Registry to search and retrieve data element metadata. The objective is to facilitate creation of annotated data capture form at the point of form design by adding mapping metadata for the data elements in a data capture form to the content models used in clinical care domain.
-The metadata registry such as CDISC SHARE can serve as the Metadata Source in this profile will define and maintain correspondences between research and healthcare data elements, and will provide an exact map by which an RFD form Manager can extract data from the pre-population data set.
+The metadata registry such as CDISC SHARE can serve as the Metadata Source in this profile will define and maintain correspondences between research and healthcare data elements, and will provide an exact map by which an RFD Form Manager can extract data from the pre-population data set.
 An electronic data capture system or a  research protocol design system would host the Metadata Consumer actor, to query the Metadata Source actor to retrieve the list of data elements hosted and retrieve the metadata of a selected data element including the exact mapping path of the selected data element instance in a content model like HL7 CCD. These mappings would be used to create the annotated data capture forms at the point of form design.
@@ Line 25: / Line 27: @@
 Electronic Data Capture system may query the Metadata Source for a list of Data Elements matching a selection criteria, and may retrieve the metadata of the selected data element.
-<center>[[Image: ftp:ihe.net/Quality/2014_2015_YR_8/Figure 1 DEX Actor Diagram.jpg]]</center>
+<center>[[Image: Figure-1-DEX_ActorsandTransactions.png]]</center>
+Metadata Consumer
+The Metadata Consumer is responsible for the importation of metadata created by the Metadata Source. The Metadata Consumer can optionally query the Metadata Source for a list of Data Elements matching a selection criteria.
+Metadata Source
+The Metadata Source is responsible for creation of the Data Element list matching a selection criteria and the creation of metadata for a selected Data Element per request from the Metadata Consumer. The Metadata Source is associated with a metadata registry.
+<center>[[Image: TABLE1.png]]</center>
 ==Specification==
-'''Profile Status:''' [[Comments| Final Text]]
+'''Profile Status:''' Profile Status:  Trial Implementation
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 '''Documents:'''
-''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
+[http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_DEX.pdf Data Element Exchange (DEX) -Supplement for Trial Implementation- Published 2013-09-13]
-[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 '''Underlying Standards:'''
-''<list all the standards on which the profile is based; if possible with links to sources>''
+*ISO/IEC 11179: Information Technology – Metadata Registries (MDR) Parts 1–6 (3rd Edition).
-:* [http://dicom.nema.org DICOM]
+*IETF RFC2616 HyperText Transfer Protocol HTTP/1.1
-:* [http://www.hl7.org HL7]
+*Extensible Markup Language (XML) 1.0 (Second Edition). W3C Recommendation 6 October 2000. http://www.w3.org/TR/REC-xml.
-:* ...
+*Web Services Description Language (WSDL) 1.1. W3C Note 15 March 2001. http://www.w3.org/TR/wsdl.
+*SOAP 1.2 Second Edition, W3C Recommendation 27 April 2007. http://www.w3.org/TR/soap12-part1
-==See Also==
+*IEEE Std 1003.2 IEEE Standard for Information Technology — Portable Operating System Interface (POSIX®) — Part 2: Shell and Utilities — Amendment 1: Batch Environment -Description
-''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
-'''Related Profiles'''
-''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
-* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
-* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
-* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
-* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
-* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
-'''Consumer Information'''
-The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
-The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
-'''Implementer Information'''
-The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
-'''Reference Articles'''
-''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract   or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
-This page is based on the [[Profile Overview Template]]
+[[Category:Profiles]]
+[[Category:QRPH Profile]]