ONC S&I DPROV Use Cases and Requirements
Back to HL7 FHIR Security Topics
FHIR Provenance Resource Use Cases
The Data Provenance Initiative aims to establish a standardized way of capturing provenance (including inbound, system generated, and outbound provenance), retaining and exchanging the provenance of health information. (Provenance Capabilities) Data provenance captures (embodies) data related to the Who, What, When, Where, Why, and Authenticity of a clinical encounter or data capture event for each type of author and supporting system.
3.0 Use Case Scope The scope of Data Provenance is broad and there are differing perspectives surrounding priorities and expectations for provenance capabilities. We will address the initiative goals by discussing the following questions to help us understand the broader scope and applicability of data provenance:
- When healthcare data is first created, what is the provenance information that should be captured (previously created provenance information or newly created provenance information), retained, and conveyed?
- Can a receiving system understand and trust that provenance information?
- Do we need to know who touched it along the way? If so, how do we know?
- In situations where the receiving system combines this information with data received from third parties, how do we persist the provenance from multiple sources?
- When multi-sourced data is assembled and sent to another system, how do we convey the provenance of the multiple data sources as well as for the system doing the assembly?
- Is this considered new data?
- What if the assembling system “cherry picks” from multiple sources, or adds some new health information of its own?
- How do we know if the received provenance information is complete?
