Provenance

The Provenance resource tracks information about the activity that created a version of a resource, including the entities and agents involved in producing a resource. This information can be used to form assessments about its quality, reliability or trustworthiness, or to provide pointers for where to go to further investigate the origins of the resource and the information in it.

Provenance resource is generated for a bundle and it prmarily stores:

  1. Source of the data
  2. Channel of the data
  3. GDPR information if available
  4. References to all resources contained in the bundle
  5. Source requestId of asynchronous ingestion message request

Apps sending data to FHIR using bundles can have two levels of maturity:

  • Entry level, where channel information comes from Bundle Message Header and source will be provided on both Bundle Message Header or DeviceComponent resource. On that case, the FHIR ingestion flow will generate appropriate Provenance resources following described “general rules for provenance generation” described. If this rules are not appropriate for a given application, it must implement the mature level rules.
  • Mature level, where bundle contains one or more provenance resources with the required information. On that case, FHIR ingestion flow only performs “provenance sanity checks”.

Overview

`The below overview shows the elements of the resource, data type and the cardinality of each. Further details like "Binding"/"Fixed values"/"contraints" etc can be found on clicking on each element.

Canonical url - http://roche.com/fhir/rdc/StructureDefinition/provenance

The resource cannot be rendered.

Details

Command 'dict' could not render: File is not a FHIR resource.

Overview

Command 'table' could not render: File is not a FHIR resource.

XML

Command 'xml' could not render: File is not a FHIR resource.

JSON

Command 'json' could not render: File is not a FHIR resource.

Example

NOTE to developer: This is only a sample resource. For the resource structure and valusets always refer the section "Overview" under each profile definition in the Implementation guide. If an element is defined as an array (0..*) in the standard and in RDC profile as an object (0..1), please note that it should still carry the structure of an array with one occurance. The structure for all resources as per the FHIR standard can be found at https://www.hl7.org/fhir/STU3/resourcelist.html

Command 'json' could not render: File not found for 'subject=rdc/example-bgip-provenance'