Provenance resources document changes in other resource instances
Provenance information is used to record changes to the information resources from the Person information service. The provenance information and services can enable the consumers of person information to keep person information in local software solutions up-to-date with the information recorded in the master person index. All changes to the Person and RelatedPerson resources are documented in it's own Provenance resource.
There is only two noteable changes to the Provenance resource in the gd-Provenance profile:
- The inclusion of a reference-targetElement extension that allows any target reference to also include the possibility to document the actual elements that are changed in the target resource
- The slicing of reason with a required binding to document FREG event types from the valueset GdProvenanceFregEventTypeCodesystem
The provenance process
When the information regarding a person is updated in the register a provenance instance is created to document the change to the person-document:
CREATE: Fundamental operation in an Information System (IS) that results only in the act of bringing an object into existence. A Person document is created. The act of creating the Person-document is documented in the Provenance-1 resource instance.
UPDATE: Fundamental operation in an Information System (IS) that results only in the revision or alteration of an object. When a Person-document is updated a new version (Person v2) is created. Provenance 2 documents the update.
APPEND: Fundamental operation in an Information System (IS) that results only in the addition of information to an object already in existence, works like an update with regards to Provenance.
NULLIFY: Change the status of an object representing an Act to "nullified", i.e., treat as though it never existed. Soft delete, the Person document is nullified, no provenance instances are removed.
DELETE: Fundamental operation in an Information System (IS) that results only in the removal of information about an object from memory or storage. Results in the removal of all information about the Person document and its provenance.
FREG event types
Provenance.reason can contain the event types (change types) registered in FREG (from Skatteetaten), and is described according to the CodeSystem from FREG GdProvenanceFregEventTypeCodesystem. The CodeSystem describes the possible changes FREG can make on an FREG person document instance
This code system http://ehelse.no/fhir/CodeSystem/gd-provenance-freg-eventtype defines the following codes:
Persontjenesten event types
Grunndata uses the element Provenance.activity to document what kind of transaction changed the content of the resource. Only codes identifying Data operation types will be used: http://terminology.hl7.org/CodeSystem/v3-DataOperation The subset of codes used in Persontjenesten is defined in GdProvenanceActivityType
|Published by||Direktoratet for e-Helse|
|Status||Draft (since 2020-04-15T14:00:00+01:00)|
This value set contains representative Activity Type codes, which includes codes from the HL7 DataOperations code system
Website: http://ehelse.noThis value set includes codes from the following code systems: