HL7 Terminology (THO)
6.0.2 - Publication International flag

This page is part of the HL7 Terminology (v6.0.2: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: ActRelationshipCheckpoint

Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpoint Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: ActRelationshipCheckpoint
Other Identifiers: OID:2.16.840.1.113883.1.11.10349

Copyright/Legal: 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

A code specifying when in the course of an Act a precondition for the Act is evaluated (e.g., before the Act starts for the first time, before every repetition, after each repetition but not before the first, or throughout the entire time of the Act.)

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. Before each step is executed and has preconditions these conditions are tested and if the test is positive, the Act has clearance for execution. The repeatNumber may indicate that an Act may be repeatedly executed. The checkpointCode is specifies when the precondition is checked and is analogous to the various conditional statements and loop constructs in programming languages “while-do” vs. “do-while” or “repeat-until” vs. “loop-exit”.

For all checkpointCodes, except “end”, preconditions are being checked at the time when the preceding step of the plan has terminated and this step would be next in the sequence established by the sequenceNumber attribute.

When the checkpointCode for a criterion of a repeatable Act is “end”, the criterion is tested only at the end of each repetition of that Act. When the condition holds true, the next repetition is ready for execution.

When the checkpointCode is “entry” the criterion is checked at the beginning of each repetition (if any) whereas “beginning” means the criterion is checked only once before the repetition “loop” starts.

The checkpointCode “through” is special in that it requires the condition to hold throughout the execution of the Act, even throughout a single execution. As soon as the condition turns false, the Act should receive an interrupt event (see interruptibleInd) and will eventually terminate.

The checkpointCode “exit” is only used on a special plan step that represents a loop exit step. This allows an action plan to exit due to a condition tested inside the execution of this plan. Such exit criteria are sequenced with the other plan components using the ActRelationship.sequenceNumber.

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)

Generated Narrative: ValueSet v3-ActRelationshipCheckpoint

Language: en

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActRelationshipCheckpoint v3.0.0 (CodeSystem)

This value set contains 5 concepts

CodeSystemDisplayDefinition
  Bhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointbeginning

Condition is tested every time before execution of the service (WHILE condition DO service).

  Ehttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointend

Condition 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-ActRelationshipCheckpointentry

Condition is tested once before the service is executed (IF condition THEN service).

  Thttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpointthrough

Condition 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-ActRelationshipCheckpointexit

Condition 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

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26