Submitted by HCapon on
PACIO Comments on Data Elements Under Provenance in V5
- Data Class: Provenance
- Data Elements: Author (Level 2), Signature (Level 0), Author Roles (Level 0), and Purpose of Capture (Level 0)
- Recommendation: Include data element “Author” in USCDI V5 and advance data elements, “Signature,” “Author Roles,” and “Purpose of Capture” to Level 1.
- Rationale: The PACIO (Post-Acute Care Interoperability) Project, established February 2019, is a collaborative effort between industry, government, and other stakeholders, with the goal of establishing a framework for the development of FHIR implementation guides to facilitate health information exchange. The PACIO Community recommends the following data elements that are currently at other levels should be upgraded.
- Author (currently on Level 2) - Author time and organization is not going to have a lot of meaning without the author particularly in non-institutional data sources. As we move to more patient centered care, there will be other contributors of data including patients and non-clinician Caregivers
- Signature (Currently Level 0) – Some documents and other information, such as end of life, like POLST, orders need to be signed in order to trusted and used. Without a signature there is no way to validate the veracity of data that may not be coming from a direct trusted source.
- Author Role(s) (Currently Level 0) – The role in which data is captured is important to more fully understand data. It is important to know not only what organization or author created the data but the capacity in which they were operating under in order to properly understand the data.
- Purpose of Capture (Currently Level 0) – Information is gathered from numerous sources for their own specific purposes. The level of detail, completeness, and quality of the information is going to be highly dependent on the interests of those capturing the information. This is important to understand more about the data and how it can be further used for things such as population and public health.
Submitted by kelly.clarke@j… on
Comment
Recommend adding Unique Identifier as a data element. 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).