Submitted By: Gary Dickinson / EHR Standards Consulting | |
---|---|
Data Element Information | |
Use Case Description(s) | |
Use Case Description | 1) Allows ready recognition and suppression of duplicate data elements: e.g., from single source through multiple data streams (exchanges) to any single downstream point of use. 2) Allows multiple data elements to be bound together within a correlated set - elements of content bound to elements of related context. |
Estimate the breadth of applicability of the use case(s) for this data element | 1) All stakeholders/systems who originate and retain discrete data elements as well as data elements bound together content/context sets, including source EHR/PHR/HIT systems. 2) All stakeholders/systems who exchange data elements as well as data elements bound together content/context sets, including intermediaries (e.g., HINs). 3) All stakeholders/systems who receive (from external sources) and retain discrete data elements as well as data elements bound together content/context sets, including receiving EHR/PHR/HIT systems. |
Healthcare Aims |
|
Maturity of Use and Technical Specifications for Data Element | |
Applicable Standard(s) | N/A |
Additional Specifications | N/A |
Current Use | In limited use in production environments |
Supporting Artifacts |
Currently used in production systems - typically with common software architecture. Industry standards development still in preliminary stages - HL7 EHR and Security Work Groups. |
Extent of exchange | N/A |
Potential Challenges | |
Restrictions on Standardization (e.g. proprietary code) | None |
Restrictions on Use (e.g. licensing, user fees) | None |
Privacy and Security Concerns | None |
Estimate of Overall Burden | Burden might apply to software developers but is a one-time cost whereas burden reduction to end users (including clinicians) will be ongoing and substantial. This comes as the result of data de-duplication and preservation of correlated set(s) of data content bound to related context. |
Other Implementation Challenges | Immediate challenge is development of common industry standards and uptake of those standards once in place. |
The metadata, or extra information about data, regarding who created the data and when it was created.
Data Element |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Element Level GUID
Description
The Element Level Globally Unique Identifier (GUID) ensures that each data element instance: |
||||||||||||
|
Comment