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:
1) Has a single non-duplicative identifier;
2) Assigned at the point of origination by the source EHR/PHR/HIT system;
3) Inseparably bound to the data element instance;
4) Maintained in perpetuity during the lifespan of that data element instance;
5) From source to use (point of origination to each ultimate point of use), including all intermediate stages and lifecycle events (retention, update/amendment, verification/attestation, exchange...).
6) Can be bound together within a correlated set - elements of content bound to elements of related context.
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
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
  • Improving provider experience of care
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.
ONC Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 0 - Data element is not represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 1 - Data element is captured, stored, or accessed in at least one production EHR or HIT module.
Criterion #3
Maturity - Current Exchange		 Level 0 - Data element is electronically exchanged in limited environments, such as connectathons or pilots.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 2 - Use cases apply to most care settings or specialties.
Evaluation Comment Data element does not meet the criteria for either Level 1 or Level 2. With further development of data and exchange standards and implementation, this data element will be reevaluated.

Comment

Log in or register to post comments