FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R4.v3.DataOperation for use in FHIR R5

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)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-DataOperation version 2018-08-12
    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.
    EXECUTEexecuteFundamental 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.
    READreadFundamental 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.
    APPENDappendFundamental 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.
    ABORTabortChange 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.
    ACTIVATEactivateChange 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.
    CANCELcancelChange 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.
    COMPLETEcompleteChange 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.
    HOLDholdChange 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.
    JUMPjumpChange 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.
    NULLIFYnullifyChange 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.
    OBSOLETEobsoleteChange 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.
    REACTIVATEreactivateChange 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.
    RELEASEreleaseChange 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.
    RESUMEresumeChange 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.
    SUSPENDsuspendChange the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service.
    MODIFYSTATUSmodify statusChange the status of an object representing an Act.
    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.
    OPERATEoperateAct on an object or objects.

 

Expansion

This value set expansion contains 20 concepts.

CodeSystemDisplayDefinition
  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.
  EXECUTEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationexecuteFundamental 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.
  READhttp://terminology.hl7.org/CodeSystem/v3-DataOperationreadFundamental 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.
  APPENDhttp://terminology.hl7.org/CodeSystem/v3-DataOperationappendFundamental 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.
  ABORThttp://terminology.hl7.org/CodeSystem/v3-DataOperationabortChange 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.
  ACTIVATEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationactivateChange 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.
  CANCELhttp://terminology.hl7.org/CodeSystem/v3-DataOperationcancelChange 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.
  COMPLETEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationcompleteChange 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.
  HOLDhttp://terminology.hl7.org/CodeSystem/v3-DataOperationholdChange 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.
  JUMPhttp://terminology.hl7.org/CodeSystem/v3-DataOperationjumpChange 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.
  NULLIFYhttp://terminology.hl7.org/CodeSystem/v3-DataOperationnullifyChange 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.
  OBSOLETEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationobsoleteChange 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.
  REACTIVATEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationreactivateChange 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.
  RELEASEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationreleaseChange 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.
  RESUMEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationresumeChange 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.
  SUSPENDhttp://terminology.hl7.org/CodeSystem/v3-DataOperationsuspendChange the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service.
  MODIFYSTATUShttp://terminology.hl7.org/CodeSystem/v3-DataOperationmodify statusChange the status of an object representing an Act.
  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.
  OPERATEhttp://terminology.hl7.org/CodeSystem/v3-DataOperationoperateAct 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