Terminology Change Set Exchange
1.0.0 - STU1 International flag

Terminology Change Set Exchange, published by HL7 International / Terminology Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/termchangeset-ig/ and changes regularly. See the Directory of published versions

ValueSet: Change Type Value Set

Official URL: http://hl7.org/fhir/uv/termchangeset/ValueSet/changetype-vs Version: 1.0.0
Standards status: Draft Maturity Level: 0 Computable Name: ChangeTypeVS

Codes representing the type of change to an element for a concept. The value set includes the terms CREATE, DELETE, UPDATE, and DEPRECATE from the following CodeSystem: https://terminology.hl7.org/CodeSystem-v3-DataOperation.html.

References

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-DataOperation
    CodeDisplayDefinition
    CREATEcreateFundamental 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.
    DELETEdeleteFundamental 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.
    UPDATEreviseFundamental 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.
    DEPRECATEdeprecateFundamental 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.

 

Expansion

Expansion performed internally based on codesystem DataOperation v5.0.0 (CodeSystem)

This value set contains 4 concepts

CodeSystemDisplay (en-US)Definition
  CREATEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationcreateFundamental 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.
  DELETEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationdeleteFundamental 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.
  UPDATEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationreviseFundamental 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.
  DEPRECATEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationdeprecateFundamental 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.

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