Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions

ValueSet: R3V3ActRelationshipCheckpointForR5

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-v3-ActRelationshipCheckpoint-for-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3V3ActRelationshipCheckpointForR5

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/v3-ActRelationshipCheckpoint|2016-11-11 for use in FHIR R5.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/v3-ActRelationshipCheckpoint|2016-11-11 as defined in FHIR STU3 in FHIR R5.

The source value set is bound to the following FHIR STU3 elements:

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://hl7.org/fhir/ValueSet/v3-ActRelationshipCheckpoint|2016-11-11, defined in FHIR STU3 does not have any mapping to FHIR R5

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://hl7.org/fhir/v3/ActRelationshipCheckpoint version 📍2016-11-11
    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.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/v3/ActRelationshipCheckpoint2016-11-11  BbeginningCondition is tested every time before execution of the service (WHILE condition DO service).
http://hl7.org/fhir/v3/ActRelationshipCheckpoint2016-11-11  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).
http://hl7.org/fhir/v3/ActRelationshipCheckpoint2016-11-11  SentryCondition is tested once before the service is executed (IF condition THEN service).
http://hl7.org/fhir/v3/ActRelationshipCheckpoint2016-11-11  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.
http://hl7.org/fhir/v3/ActRelationshipCheckpoint2016-11-11  XexitCondition 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