This page is part of the FHIR Specification (v1.0.2: DSTU 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

1.25.4.1.1123 HL7 v3 Code System DataOperation

This code system (http://hl7.org/fhir/v3/DataOperation) is defined as part of HL7 v3.

Summary

Defining URL:

http://hl7.org/fhir/ValueSet/v3-DataOperation

Name:

v3 Code System DataOperation

Definition:

**** MISSING DEFINITIONS ****

OID:

(for OID based terminology systems)

System URL:

http://hl7.org/fhir/v3/DataOperation

System OID:

2.16.840.1.113883.5.1123

Source Resource

XML / JSON

This value set is not currently used

1.25.4.1.1123.1 Content Logical Definition

This value set has an inline code system http://hl7.org/fhir/v3/DataOperation, which defines the following codes:

Lvl	Code	Display	Definition
1	OPERATE	operate	Description:Act on an object or objects.
2	CREATE	create	Description: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.
2	DELETE	delete	Description: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.
2	EXECUTE	execute	Description: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.
2	READ	read	Description: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.
2	UPDATE	revise	Definition: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.
3	APPEND	append	Description: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.
3	MODIFYSTATUS	modify status	Description:Change the status of an object representing an Act.
4	ABORT	abort	Description: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.
4	ACTIVATE	activate	Description: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.
4	CANCEL	cancel	Description: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.
4	COMPLETE	complete	Description: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.
4	HOLD	hold	Description: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.
4	JUMP	jump	Description: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.
4	NULLIFY	nullify	Description: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.
4	OBSOLETE	obsolete	Description: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.
4	REACTIVATE	reactivate	Description: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.
4	RELEASE	release	Description: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.
4	RESUME	resume	Description: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.
4	SUSPEND	suspend	Definition:Change the status of an object representing an Act to suspended, i.e., so it is temporarily not in service.