HL7 Terminology (THO)
6.0.0 - Publication
This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Active as of 2019-03-20 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="v3-DataOperation"/>
<language value="en"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p class="res-header-id"><b>Generated Narrative: CodeSystem v3-DataOperation</b></p><a name="v3-DataOperation"> </a><a name="hcv3-DataOperation"> </a><a name="v3-DataOperation-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Language: en</p></div><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Specializes</td><td>Specializes</td><td/><td>Coding</td><td>The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.</td></tr><tr><td>Generalizes</td><td>Generalizes</td><td/><td>Coding</td><td>Inverse of Specializes. Only included as a derived relationship.</td></tr><tr><td>internalId</td><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>code</td><td>The internal identifier for the concept in the HL7 Access database repository.</td></tr><tr><td>Status</td><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>code</td><td>Designation of a concept's state. Normally is not populated unless the state is retired.</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v3-DataOperation</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td><b>Lvl</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>internalId</b></td><td><b>Status</b></td></tr><tr><td>1</td><td style="white-space:nowrap">OPERATE<a name="v3-DataOperation-OPERATE"> </a></td><td>operate</td><td>Act on an object or objects.</td><td>22873</td><td>active</td></tr><tr><td>2</td><td style="white-space:nowrap"> CREATE<a name="v3-DataOperation-CREATE"> </a></td><td>create</td><td>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.</td><td>22874</td><td>active</td></tr><tr><td>2</td><td style="white-space:nowrap"> DELETE<a name="v3-DataOperation-DELETE"> </a></td><td>delete</td><td>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.</td><td>22891</td><td>active</td></tr><tr><td>2</td><td style="white-space:nowrap"> EXECUTE<a name="v3-DataOperation-EXECUTE"> </a></td><td>execute</td><td>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.</td><td>22892</td><td>active</td></tr><tr><td>2</td><td style="white-space:nowrap"> READ<a name="v3-DataOperation-READ"> </a></td><td>read</td><td>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.</td><td>22875</td><td>active</td></tr><tr><td>2</td><td style="white-space:nowrap"> UPDATE<a name="v3-DataOperation-UPDATE"> </a></td><td>revise</td><td>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.</td><td>22876</td><td>active</td></tr><tr><td>3</td><td style="white-space:nowrap"> APPEND<a name="v3-DataOperation-APPEND"> </a></td><td>append</td><td>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.</td><td>22877</td><td>active</td></tr><tr><td>3</td><td style="white-space:nowrap"> MODIFYSTATUS<a name="v3-DataOperation-MODIFYSTATUS"> </a></td><td>modify status</td><td>Change the status of an object representing an Act.</td><td>22878</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> ABORT<a name="v3-DataOperation-ABORT"> </a></td><td>abort</td><td>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.</td><td>22879</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> ACTIVATE<a name="v3-DataOperation-ACTIVATE"> </a></td><td>activate</td><td>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.</td><td>22880</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> CANCEL<a name="v3-DataOperation-CANCEL"> </a></td><td>cancel</td><td>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.</td><td>22881</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> COMPLETE<a name="v3-DataOperation-COMPLETE"> </a></td><td>complete</td><td>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.</td><td>22882</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> HOLD<a name="v3-DataOperation-HOLD"> </a></td><td>hold</td><td>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.</td><td>22883</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> JUMP<a name="v3-DataOperation-JUMP"> </a></td><td>jump</td><td>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.</td><td>22884</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> NULLIFY<a name="v3-DataOperation-NULLIFY"> </a></td><td>nullify</td><td>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.</td><td>22885</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> OBSOLETE<a name="v3-DataOperation-OBSOLETE"> </a></td><td>obsolete</td><td>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.</td><td>22886</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> DEPRECATE<a name="v3-DataOperation-DEPRECATE"> </a></td><td>deprecate</td><td>Fundamental operation in HL7 Standards Governance that results only in the addition of deprecation information to an object already in existence without changing the status of the object. Operation used internally in the maintenance and recordkeeping of HL7 terminology and standards artifacts.</td><td>722877</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> REACTIVATE<a name="v3-DataOperation-REACTIVATE"> </a></td><td>reactivate</td><td>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.</td><td>22887</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> RELEASE<a name="v3-DataOperation-RELEASE"> </a></td><td>release</td><td>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.</td><td>22888</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> RESUME<a name="v3-DataOperation-RESUME"> </a></td><td>resume</td><td>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.</td><td>22889</td><td>active</td></tr><tr><td>4</td><td style="white-space:nowrap"> SUSPEND<a name="v3-DataOperation-SUSPEND"> </a></td><td>suspend</td><td>Change the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service.</td><td>22890</td><td>active</td></tr></table></div>
</text>
<url value="http://terminology.hl7.org/CodeSystem/v3-DataOperation"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.5.1123"/>
</identifier>
<version value="5.0.0"/>
<name value="DataOperation"/>
<title value="DataOperation"/>
<status value="active"/>
<experimental value="false"/>
<date value="2019-03-20"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description value="**** MISSING DESCRIPTION ****"/>
<copyright
value="This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
<caseSensitive value="true"/>
<hierarchyMeaning value="is-a"/>
<content value="complete"/>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
<valueCode value="antisymmetric"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
<valueCode value="transitive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
<valueCode value="irreflexive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
<valueBoolean value="true"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Specializes"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
<valueString value="Generalizes"/>
</extension>
<code value="Specializes"/>
<description
value="The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric."/>
<type value="Coding"/>
</property>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
<valueCode value="antisymmetric"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
<valueCode value="transitive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
<valueCode value="irreflexive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
<valueBoolean value="true"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Generalizes"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
<valueString value="Specializes"/>
</extension>
<code value="Generalizes"/>
<description
value="Inverse of Specializes. Only included as a derived relationship."/>
<type value="Coding"/>
</property>
<property>
<code value="internalId"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id"/>
<description
value="The internal identifier for the concept in the HL7 Access database repository."/>
<type value="code"/>
</property>
<property>
<code value="status"/>
<uri value="http://hl7.org/fhir/concept-properties#status"/>
<description
value="Designation of a concept's state. Normally is not populated unless the state is retired."/>
<type value="code"/>
</property>
<concept>
<code value="OPERATE"/>
<display value="operate"/>
<definition value="Act on an object or objects."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22873"/>
</property>
<concept>
<code value="CREATE"/>
<display value="create"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22874"/>
</property>
</concept>
<concept>
<code value="DELETE"/>
<display value="delete"/>
<definition
value="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."/>
<designation>
<language value="en"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="remove"/>
</designation>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22891"/>
</property>
</concept>
<concept>
<code value="EXECUTE"/>
<display value="execute"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22892"/>
</property>
</concept>
<concept>
<code value="READ"/>
<display value="read"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22875"/>
</property>
</concept>
<concept>
<code value="UPDATE"/>
<display value="revise"/>
<definition
value="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."/>
<designation>
<language value="en"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="update"/>
</designation>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22876"/>
</property>
<concept>
<code value="APPEND"/>
<display value="append"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22877"/>
</property>
</concept>
<concept>
<code value="MODIFYSTATUS"/>
<display value="modify status"/>
<definition
value="Change the status of an object representing an Act."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22878"/>
</property>
<concept>
<code value="ABORT"/>
<display value="abort"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22879"/>
</property>
</concept>
<concept>
<code value="ACTIVATE"/>
<display value="activate"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22880"/>
</property>
</concept>
<concept>
<code value="CANCEL"/>
<display value="cancel"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22881"/>
</property>
</concept>
<concept>
<code value="COMPLETE"/>
<display value="complete"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22882"/>
</property>
</concept>
<concept>
<code value="HOLD"/>
<display value="hold"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22883"/>
</property>
</concept>
<concept>
<code value="JUMP"/>
<display value="jump"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22884"/>
</property>
</concept>
<concept>
<code value="NULLIFY"/>
<display value="nullify"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22885"/>
</property>
</concept>
<concept>
<code value="OBSOLETE"/>
<display value="obsolete"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22886"/>
</property>
</concept>
<concept>
<code value="DEPRECATE"/>
<display value="deprecate"/>
<definition
value="Fundamental operation in HL7 Standards Governance that results only in the addition of deprecation information to an object already in existence without changing the status of the object. Operation used internally in the maintenance and recordkeeping of HL7 terminology and standards artifacts."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="722877"/>
</property>
</concept>
<concept>
<code value="REACTIVATE"/>
<display value="reactivate"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22887"/>
</property>
</concept>
<concept>
<code value="RELEASE"/>
<display value="release"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22888"/>
</property>
</concept>
<concept>
<code value="RESUME"/>
<display value="resume"/>
<definition
value="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."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22889"/>
</property>
</concept>
<concept>
<code value="SUSPEND"/>
<display value="suspend"/>
<definition
value="Change the status of an object representing an Act to **suspended**, i.e., so it is temporarily not in service."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="22890"/>
</property>
</concept>
</concept>
</concept>
</concept>
</CodeSystem>