R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.10 HL7 v3 Value Set ActRelationshipCheckpoint

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This value set (http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpoint) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpoint
Version:2018-08-12
Name:v3.ActRelationshipCheckpoint
Title:v3 Code System ActRelationshipCheckpoint
Definition:

**** MISSING DEFINITIONS ****

OID:2.16.840.1.113883.1.11.10349 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

4.4.2.10.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.4.2.10.2 Expansion

This expansion generated 19 Aug 2018

This value set contains 5 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpoint version 2018-08-12

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpoint

CodeDisplayDefinition
BbeginningCondition is tested every time before execution of the service (WHILE condition DO service).
EendCondition is tested at the end of a repeated service execution. The service is repeated only if the condition is true (DO service WHILE condition).
SentryCondition is tested once before the service is executed (IF condition THEN service).
TthroughCondition must be true throughout the execution and the service is interrupted (asynchronously) as soon as the condition turns false (asynchronous WHILE loop). The service must be interruptible.
XexitCondition is a loop checkpoint, i.e. it is a step of an activity plan and, if negative causes the containing loop to exit.