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 |
|
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 |
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. |
||||||||||||
|
Comment