FHIR © HL7.org  |  Server Home  |  XIG Home  |  Server Source  |  FHIR  

FHIR IG Statistics: ValueSet/v3-ActRelationshipSplit

Packagehl7.terminology
TypeValueSet
Idv3-ActRelationshipSplit
FHIR VersionR5
Sourcehttp://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-ActRelationshipSplit.html
URLhttp://terminology.hl7.org/ValueSet/v3-ActRelationshipSplit
Version3.0.0
Statusactive
Date2014-03-26
NameActRelationshipSplit
TitleActRelationshipSplit
Realmuv
Authorityhl7
DescriptionA 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.
CopyrightThis 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

Resources that use this resource

No resources found


Resources that this resource uses

CodeSystem
v3-ActRelationshipSplitActRelationshipSplit
v3-ActRelationshipSplitActRelationshipSplit

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet v3-ActRelationshipSplit

Language: en


Source

{
  "resourceType": "ValueSet",
  "id": "v3-ActRelationshipSplit",
  "language": "en",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "url": "http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplit",
  "identifier": [
    {
      "system": "urn:ietf:rfc:3986",
      "value": "urn:oid:2.16.840.1.113883.1.11.10355"
    }
  ],
  "version": "3.0.0",
  "name": "ActRelationshipSplit",
  "title": "ActRelationshipSplit",
  "status": "active",
  "experimental": false,
  "date": "2014-03-26",
  "publisher": "Health Level Seven International",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://hl7.org"
        },
        {
          "system": "email",
          "value": "hq@HL7.org"
        }
      ]
    }
  ],
  "description": "A code specifying how branches in an action plan are selected among other branches.\r\n\r\n*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.\r\n\r\nIn 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.\r\n\r\nIn 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.",
  "immutable": true,
  "copyright": "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": "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit"
      }
    ]
  }
}