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 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 2014-03-26 |
<ValueSet xmlns="http://hl7.org/fhir">
<id value="v3-ActRelationshipJoin"/>
<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: ValueSet v3-ActRelationshipJoin</b></p><a name="v3-ActRelationshipJoin"> </a><a name="hcv3-ActRelationshipJoin"> </a><a name="v3-ActRelationshipJoin-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><ul><li>Include all codes defined in <a href="CodeSystem-v3-ActRelationshipJoin.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin</code></a></li></ul></div>
</text>
<url value="http://terminology.hl7.org/ValueSet/v3-ActRelationshipJoin"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.1.11.10360"/>
</identifier>
<version value="3.0.0"/>
<name value="ActRelationshipJoin"/>
<title value="ActRelationshipJoin"/>
<status value="active"/>
<experimental value="false"/>
<date value="2014-03-26"/>
<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 concurrent Acts are resynchronized in a parallel branch construct.
*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. Branches are parallel if the splitCode specifies that more than one branch can be executed at the same time. The joinCode then specifies if and how the braches are resynchronized.
The principal re-synchronization actions are (1) the control flow waits for a branch to terminate (wait-branch), (2) the branch that is not yet terminated is aborted (kill-branch), (3) the branch is not re-synchronized at all and continues in parallel (detached branch).
A kill branch is only executed if there is at least one active wait (or exclusive wait) branch. If there is no other wait branch active, a kill branch is not started at all (rather than being aborted shortly after it is started.) Since a detached branch is unrelated to all other branches, active detached branches do not protect a kill-branch from being aborted."/>
<immutable value="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"/>
<compose>
<include>
<system
value="http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin"/>
</include>
</compose>
</ValueSet>