HL7 Terminology (THO)
5.5.0 - Publication
This page is part of the HL7 Terminology (v5.5.0: Release) based on FHIR (HL7® FHIR® Standard) 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
Official URL: http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit | Version: 3.0.0 | |||
Active as of 2019-03-20 | Responsible: Health Level Seven International | Computable Name: ActRelationshipSplit | ||
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.5.13 | ||||
Copyright/Legal: 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 |
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.
This Code system is referenced in the content logical definition of the following value sets:
Properties
This code system defines the following properties for its concepts
Code | URI | Type | Description |
Specializes | Coding | 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. | |
Generalizes | Coding | Inverse of Specializes. Only included as a derived relationship. | |
internalId | http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id | code | The internal identifier for the concept in the HL7 Access database repository. |
status | http://hl7.org/fhir/concept-properties#status | code | Designation of a concept's state. Normally is not populated unless the state is retired. |
Concepts
This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit
defines the following codes in a Is-A heirarchy:
History
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2022-10-18 | revise | TSMG | Marc Duteau | Fixing missing metadata; up-349 |
2022-02-17 00:00:32+1100 | revise | Vocabulary WG | Grahame Grieve | Populate Missing caseSensitive property; UP-286 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |