FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/4.0/ValueSet/R4-v3-DataOperation-for-R5 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Responsible: HL7 International / Terminology Infrastructure | Computable Name: R4_v3_DataOperation_for_R5 | |
| This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-DataOperation | 2018-08-12 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R4 to R5. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-DataOperation version 2018-08-12| Code | Display | Definition |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| SUSPEND | suspend | Change the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service. |
| MODIFYSTATUS | modify status | Change the status of an object representing an Act. |
| 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. |
| OPERATE | operate | Act on an object or objects. |
This value set expansion contains 20 concepts.
| Code | System | Display | Definition |
| CREATE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| DELETE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| EXECUTE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| READ | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| APPEND | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| ABORT | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| ACTIVATE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| CANCEL | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| COMPLETE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| HOLD | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| JUMP | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| NULLIFY | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| OBSOLETE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| REACTIVATE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| RELEASE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| RESUME | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| SUSPEND | http://terminology.hl7.org/CodeSystem/v3-DataOperation | suspend | Change the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service. |
| MODIFYSTATUS | http://terminology.hl7.org/CodeSystem/v3-DataOperation | modify status | Change the status of an object representing an Act. |
| UPDATE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | 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. |
| OPERATE | http://terminology.hl7.org/CodeSystem/v3-DataOperation | operate | Act on an object or objects. |
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 |