HL7.TERMINOLOGY\ActRelationshipSplit

HL7 Terminology (THO)
5.2.0 - Publication International flag

This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. 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

ValueSet: ActRelationshipSplit

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplit		Version: 2.0.0
Active as of 2014-03-26	Computable Name: ActRelationshipSplit
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.10355

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.

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 all codes defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit

Expansion

This value set contains 4 concepts

Expansion based on ActRelationshipSplit v2.1.1 (CodeSystem)

Code	System	Display	Definition
E1	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit	exclusive try once	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.
EW	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit	exclusive wait	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.
I1	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit	inclusive try once	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.
IW	http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit	inclusive wait	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).

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

History

Date

Action

Author

Custodian

Comment

2022-10-18

revise