HL7 Terminology (THO)
6.1.0 - Publication
HL7 Terminology (THO)
6.1.0 - Publication
This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. 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-ActRelationshipSplit"/>
<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-ActRelationshipSplit</b></p><a name="v3-ActRelationshipSplit"> </a><a name="hcv3-ActRelationshipSplit"> </a><a name="v3-ActRelationshipSplit-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-ActRelationshipSplit</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><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 style="white-space:nowrap">E1<a name="v3-ActRelationshipSplit-E1"> </a></td><td>exclusive try once</td><td>The pre-condition associated with the branch is evaluated once and if true the branch may be entered. All other exclusive branches compete with each other and only one will be selected. This implements a COND, IF and CASE conditionals, or "XOR-split." The order in which the branches are considered may be specified in the priorityNumber attribute.</td><td>10356</td><td>active</td></tr><tr><td style="white-space:nowrap">EW<a name="v3-ActRelationshipSplit-EW"> </a></td><td>exclusive wait</td><td>A branch is selected as soon as the pre-condition associated with the branch evaluates to true. If the condition is false, the branch may be entered later, when the condition turns true. All other exclusive branches compete with each other and only one will be selected. Each waiting branch executes in parallel with the default join code wait (see below). The order in which the branches are considered may be specified in the Service\_relationship.priority\_nmb.</td><td>10357</td><td>active</td></tr><tr><td style="white-space:nowrap">I1<a name="v3-ActRelationshipSplit-I1"> </a></td><td>inclusive try once</td><td>A branch is executed if its associated preconditions permit. If associated preconditions do not permit, the branch is dropped. Inclusive branches are not suppressed and do not suppress other branches.</td><td>10358</td><td>active</td></tr><tr><td style="white-space:nowrap">IW<a name="v3-ActRelationshipSplit-IW"> </a></td><td>inclusive wait</td><td>A branch is executed as soon as its associated conditions permit. If the condition is false, the branch may be entered later, when the condition turns true. Inclusive branches are not suppressed and do not suppress other branches. Each waiting branch executes in parallel with the default join code wait (see below).</td><td>10359</td><td>active</td></tr></table></div>
</text>
<url value="http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.5.13"/>
</identifier>
<version value="3.0.0"/>
<name value="ActRelationshipSplit"/>
<title value="ActRelationshipSplit"/>
<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="A code specifying how branches in an action plan are selected among other branches.
*Discussion:* This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches.
In addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as "guard conditions" on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true.
In exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true."/>
<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="E1"/>
<display value="exclusive try once"/>
<definition
value="The pre-condition associated with the branch is evaluated once and if true the branch may be entered. All other exclusive branches compete with each other and only one will be selected. This implements a COND, IF and CASE conditionals, or "XOR-split." The order in which the branches are considered may be specified in the priorityNumber attribute."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10356"/>
</property>
</concept>
<concept>
<code value="EW"/>
<display value="exclusive wait"/>
<definition
value="A branch is selected as soon as the pre-condition associated with the branch evaluates to true. If the condition is false, the branch may be entered later, when the condition turns true. All other exclusive branches compete with each other and only one will be selected. Each waiting branch executes in parallel with the default join code wait (see below). The order in which the branches are considered may be specified in the Service\_relationship.priority\_nmb."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10357"/>
</property>
</concept>
<concept>
<code value="I1"/>
<display value="inclusive try once"/>
<definition
value="A branch is executed if its associated preconditions permit. If associated preconditions do not permit, the branch is dropped. Inclusive branches are not suppressed and do not suppress other branches."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10358"/>
</property>
</concept>
<concept>
<code value="IW"/>
<display value="inclusive wait"/>
<definition
value="A branch is executed as soon as its associated conditions permit. If the condition is false, the branch may be entered later, when the condition turns true. Inclusive branches are not suppressed and do not suppress other branches. Each waiting branch executes in parallel with the default join code wait (see below)."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="10359"/>
</property>
</concept>
</CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#6.1.0 based on FHIR 5.0.0. Generated 2024-11-17
Links: Table of Contents |
QA Report
| Version History 
|
|
Propose a change