The metadata, or extra information about data, regarding who created the data and when it was created.

Data Element
Unique Identifier
Description

Numeric or alphanumeric code that uniquely identifies a document.
Submitted By: Sandi Mitchell / J P Systems, Inc.
Data Element Information
Use Case Description(s)
Use Case Description This will support the traceability of messages. FHIR data exchanges shall have the ability to identify an update to
the original message (e.g., HL7 v2.5 Update Patient Information). The value becomes more important as automatic ingestion of external messages is implemented (i.e., source identifies data entered on wrong patient, and is aware the data was exchanged, then an update can be triggered).
Estimate the breadth of applicability of the use case(s) for this data element Level 0
ONC Priority
  • None of the above
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) N/A
Additional Specifications N/A
Current Use (Level 0) Captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration
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 Standard HIPAA concerns.
Estimate of Overall Burden This data element impacts patient safety to ensure clinicians understand the sender information.
Other Implementation Challenges N/A
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 0 - Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
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 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
Evaluation Comment This data element represents a concept which is a subset or specialized use of the Level 0 data element Element Level GUID https://www.healthit.gov/isa/taxonomy/term/7852/level-0.

Comment

Log in or register to post comments