Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B - Downloaded Version null See the Directory of published versions

ValueSet: R2V3DataOperationForR4B

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R2-v3-DataOperation-for-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R2V3DataOperationForR4B

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/v3-DataOperation|2015-07-31 for use in FHIR R4B.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/v3-DataOperation|2015-07-31 as defined in FHIR DSTU2 in FHIR R4B.

The source value set is bound to the following FHIR DSTU2 elements:

Across FHIR versions, the value set has been mapped as:

  • http://hl7.org/fhir/ValueSet/v3-DataOperation|2015-07-31
  • http://hl7.org/fhir/ValueSet/v3-DataOperation|2016-11-11
  • http://terminology.hl7.org/ValueSet/v3-DataOperation|2018-08-12

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments: All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (20). All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (20). FHIR ValueSet http://hl7.org/fhir/ValueSet/v3-DataOperation|2015-07-31, defined in FHIR DSTU2 does not have any mapping to FHIR R4B

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://hl7.org/fhir/v3/DataOperation version 📍1.0.2
    CodeDisplayDefinition
    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.
    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.
    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.
    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.
    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.
    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.
    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.
    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.
    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.
    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.
    MODIFYSTATUSmodify statusDescription:Change the status of an object representing an Act.
    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.
    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.
    OPERATEoperateDescription:Act on an object or objects.
    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.
    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.
    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.
    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.
    SUSPENDsuspendDefinition:Change the status of an object representing an Act to suspended, i.e., so it is temporarily not in service.
    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.

 

Expansion

This value set expansion contains 20 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  MODIFYSTATUSmodify statusDescription:Change the status of an object representing an Act.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  OPERATEoperateDescription:Act on an object or objects.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.
http://hl7.org/fhir/v3/DataOperation1.0.2  SUSPENDsuspendDefinition:Change the status of an object representing an Act to suspended, i.e., so it is temporarily not in service.
http://hl7.org/fhir/v3/DataOperation1.0.2  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.

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