Release 5 Preview #2

This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.1123 HL7 v3 Value Set DataOperation

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This value set (http://terminology.hl7.org/ValueSet/v3-DataOperation) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-DataOperation
Version:2019-07-31
Name:v3.DataOperation
Title:v3 Code System DataOperation
Definition:

**** MISSING DEFINITIONS ****

OID: (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

  • CodeSystem: This value set is the designated 'entire code system' value set for v3.DataOperation

4.4.2.1123.1 Content Logical Definition

 

4.4.2.1123.2 Expansion

This expansion generated 03 May 2020

This value set contains 20 concepts

Expansion based on v3 Code System DataOperation v2019-07-31 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-DataOperation

LvlCodeDisplayLogical Definition (CLD)
0OPERATEoperateDescription:Act on an object or objects.
1  CREATEcreateDescription: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.
1  DELETEdeleteDescription: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.
1  EXECUTEexecuteDescription: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.
1  READreadDescription: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.
1  UPDATEreviseDefinition: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.
2    APPENDappendDescription: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.
2    MODIFYSTATUSmodify statusDescription:Change the status of an object representing an Act.
3      ABORTabortDescription: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.
3      ACTIVATEactivateDescription: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.
3      CANCELcancelDescription: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.
3      COMPLETEcompleteDescription: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.
3      HOLDholdDescription: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.
3      JUMPjumpDescription: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.
3      NULLIFYnullifyDescription: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.
3      OBSOLETEobsoleteDescription: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.
3      REACTIVATEreactivateDescription: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.
3      RELEASEreleaseDescription: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.
3      RESUMEresumeDescription: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.
3      SUSPENDsuspendDefinition:Change the status of an object representing an Act to suspended, i.e., so it is temporarily not in service.