FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R5.ActRelationshipCheckpoint for use in FHIR R4

Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-v3-ActRelationshipCheckpoint-for-R4 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R5_v3_ActRelationshipCheckpoint_for_R4

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpoint 2.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4.

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 these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpoint version 2.1.1
    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.

 

Expansion

This value set expansion contains 5 concepts.

CodeSystemDisplayDefinition
  Bhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointbeginningCondition is tested every time before execution of the service (WHILE condition DO service).
  Ehttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointendCondition is tested at the end of a repeated service execution. The service is repeated only if the condition is true (DO service WHILE condition).
  Shttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointentryCondition is tested once before the service is executed (IF condition THEN service).
  Thttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointthroughCondition 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.
  Xhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointexitCondition is a loop checkpoint, i.e. it is a step of an activity plan and, if negative causes the containing loop to exit.

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