Difference between revisions of "Provenance FHIR Resource Proposal"
| (2 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents | + | This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 34: | Line 34: | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | * [[Security]] | + | *[[Community-Based Collaborative Care]], which has the development of FHIR Provenance Resource within scope of [http://gforge.hl7.org/gf/download/docmanfileversion/8267/12090/HL7%20Project%20Scope%20Statement%20Data%20Provenance%206-18-2014.doc 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 | ||
* [[EHR]] | * [[EHR]] | ||
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| Line 56: | Line 56: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| − | 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. | + | 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) | ||
==RIM scope== | ==RIM scope== | ||
Latest revision as of 17:55, 6 October 2014
This page documents an Approved FHIR Resource Proposal
Contents
- 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
Provenance
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
- EHR
FHIR Resource Development Project Insight ID
pending
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)
RIM scope
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.
Resource appropriateness
Provenance is used by Security, Privacy, Medical Records, Medical Ethics, and good documentation practices.
Expected implementations
The Provenance resource is expected to be used to prove Integrity, Authenticity, and to give credit when sighting a resource content.
Content sources
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.
Example Scenarios
Access Control decisions based on Integrity assertions of the resource Access Control decisions based on the Privacy policy including restricted rules on source of resource Medical Records regulations proof of authorship of a resource Medical Ethics decisions based on proof of authorship and integrity of a resource
Resource Relationships
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.
Timelines
2014
gForge Users
unknown
