Health New Zealand Te Whatu Ora Shared Care FHIR API
0.4.5 - release
Health New Zealand Te Whatu Ora Shared Care FHIR API
0.4.5 - release
Health New Zealand Te Whatu Ora Shared Care FHIR API - Local Development build (v0.4.5) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir-ig.digital.health.nz/shared-care/ValueSet/provenance-reason-type-vs | Version: 0.4.5 | |||
| Active as of 2026-07-06 | Computable Name: ProvenanceReasonTypeVS | |||
Reason type codes for Provenance tracking, combining HL7 v3 DataOperation codes with local DHO reason types
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-DataOperation version 📦5.0.0https://fhir-ig.digital.health.nz/shared-care/CodeSystem/provenance-reason-type-cs version 📦0.4.5
Expansion performed internally based on:
This value set contains 23 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-DataOperation | OPERATE | operate | Act on an object or objects. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | CREATE | create | Fundamental operation in an Information System (IS) that results only in the act of bringing an object into existence. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | DELETE | delete | Fundamental operation in an Information System (IS) that results only in the removal of information about an object from memory or storage. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | EXECUTE | execute | Fundamental operation in an IS that results only in initiating performance of a single or set of programs (i.e., software objects). Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | READ | read | Fundamental operation in an Information System (IS) that results only in the flow of information about an object to a subject. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | UPDATE | revise | Fundamental operation in an Information System (IS) that results only in the revision or alteration of an object. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | APPEND | append | Fundamental operation in an Information System (IS) that results only in the addition of information to an object already in existence. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | MODIFYSTATUS | modify status | Change the status of an object representing an Act. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | ABORT | abort | Change the status of an object representing an Act to "aborted", i.e., terminated prior to the originally intended completion. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | ACTIVATE | activate | Change the status of an object representing an Act to "active", i.e., so it can be performed or is being performed, for the first time. (Contrast with REACTIVATE.) For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | CANCEL | cancel | Change the status of an object representing an Act to "cancelled", i.e., abandoned before activation. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | COMPLETE | complete | Change the status of an object representing an Act to "completed", i.e., terminated normally after all of its constituents have been performed. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | HOLD | hold | Change the status of an object representing an Act to "held", i.e., put aside an Act that is still in preparatory stages. No action can occur until the Act is released. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | JUMP | jump | Change the status of an object representing an Act to a normal state. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | NULLIFY | nullify | Change the status of an object representing an Act to "nullified", i.e., treat as though it never existed. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | OBSOLETE | obsolete | Change the status of an object representing an Act to "obsolete" when it has been replaced by a new instance. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | DEPRECATE | deprecate | Fundamental operation in HL7 Standards Governance that results only in the addition of deprecation information to an object already in existence without changing the status of the object. Operation used internally in the maintenance and recordkeeping of HL7 terminology and standards artifacts. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | REACTIVATE | reactivate | Change the status of a formerly active object representing an Act to "active", i.e., so it can again be performed or is being performed. (Contrast with ACTIVATE.) For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | RELEASE | release | Change the status of an object representing an Act so it is no longer "held", i.e., allow action to occur. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | RESUME | resume | Change the status of a suspended object representing an Act to "active", i.e., so it can be performed or is being performed. For an HL7 Act, the state transitions per the HL7 Reference Information Model. | ||
http://terminology.hl7.org/CodeSystem/v3-DataOperation | SUSPEND | suspend | Change the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service. | ||
https://fhir-ig.digital.health.nz/shared-care/CodeSystem/provenance-reason-type-cs | nhi-merge | NHI Merge | Updated subject NHI logical identifier | ||
https://fhir-ig.digital.health.nz/shared-care/CodeSystem/provenance-reason-type-cs | nhi-unmerge | NHI Unmerge | Updated subject NHI logical identifier |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |