- 1 Provenance
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
Owning committee name
Contributing or Reviewing Work Groups
- Community-Based Collaborative Care, which has the development of FHIR Provenance Resource within scope of Project ID: 1093 â€œProvenance for Clinical Document Architecture (CDA R2) Implementation Guideâ€�
- Security, which is a co-sponsor of Project 1093
- Structured Documents, which is a co-sponsor of Project 1093
FHIR Resource Development Project Insight ID
Scope of coverage
Provenance refers to the sources of information, such as entities and processes, involved in producing or delivering an artifact. The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.
In some scenarios the provenance resource is unnecessary as the resource itself contains the required 'background' information - such as author, time of recording etc. However, any resource can be associated with a provenance if required (though note that the relation is from the provenance to the resource and not the other way around 0 except in the case of the DocumentRoot resource)
The provenance resource is based on known practices in the HL7 implementation space, particularly those found in the v2 EVN segment, the v3 ControlAct Wrapper, and the CDA header.
Provenance is used by Security, Privacy, Medical Records, Medical Ethics, and good documentation practices.
The Provenance resource is expected to be used to prove Integrity, Authenticity, and to give credit when sighting a resource content.
The conceptual model underlying the design is the W3C Provenance Specification. Though the content and format of the resource is designed to meet specific requirements for FHIR, all the parts of the resource are formally mapped to the PROV-O specification, and FHIR resources can be transformed to their W3C PROV equivalent.
All resources may/should/shall have a Provenance resource
Note that there is no link from a provenance resource to the resource/s it describes. They need to be queried separately.