FHIR Cross-Version Extensions package for FHIR R5 from FHIR R2 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/1.0/ValueSet/R2-v3-ActRelationshipSplit-for-R5 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Computable Name: R2_v3_ActRelationshipSplit_for_R5 | ||
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/v3-ActRelationshipSplit | 2015-07-31 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R2 to R5. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/v3/ActRelationshipSplit version 1.0.2| Code | Display | Definition |
| E1 | 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 | 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 | 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 | 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). |
This value set expansion contains 4 concepts.
| Code | System | Display | Definition |
| E1 | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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 |