The TransitionTimingConstraint element defines a timing constraint on a transition between structural elements as defined in a workflow. As such, it is a non-blocking constraint. This means that the transition is set on hold as long as the timing condition is not fulfilled, and is executed as soon as the timing condition is fulfilled.

Element NameTransitionTimingConstraint
Parent Element(s)StudyTiming
Element XPath(s)
  • /ODM/Study/MetaDataVersion/Protocol/StudyTimings/StudyTiming/TransitionTimingConstraint
Element Textual ValueNone
AttributesOID, Name, TransitionOID, TimepointTarget, MethodOID, TimepointPreWindow, TimepointPostWindow
Child Elements(Description?)
Usage/Business Rules

AttributeSchema Datatype or EnumerationUsageDefinitionBusiness Rule(s)
OIDoidRequiredUnique identifier.
NamenameRequiredHuman-readable name.
TransitionOIDoidrefRequired

References the workflow Transition on which the timing constraint must be executed.


TimepointTargetdurationDatetime

Conditional


The planned time between the 2 activities defined by the transition in the workflow.
  • Must be expressed as an ISO 8601 duration.
  • Either the TimepointTarget or the MethodOID must be provided - not both.
  • If the value is a "zero time duration" (i.e., "P0D", "PT0H", or "PT0S"), the transition must be executed immediately, or within the provided time window, when provided.
MethodOIDoidrefConditionalReferences a MethodDef that returns a durationDatetime. Use of a method allows timings that depend on other pieces of information, or complex timing calculations.
  • Must match the OID attribute of a MethodDef element in this Study/MetaDataVersion.
  • The MethodSignature for the referenced MethodDef must identify the input parameters and a return value DateType of durationDatetime.
  • If the returned value for the method is a "zero time duration" (i.e., "P0D", "PT0H", or "PT0S"), the transition must be executed immediately, or within the provided time window, when provided.
  • Either the TimepointTarget or the MethodOID  must be provided - not both.
Type(StartToStart, StartToFinish, FinishToStart, FinishToFinish)OptionalDefines how the timing is to be defined between the two activities, starting from the start or the end of the source activity, and ending at the start or the end of the target activity.
  • If not provided, StartToStart is assumed.
TimepointPreWindowdurationDatetimeOptionalSpecifies the amount of time prior to the TimepointTarget, the time between the two activities, may be shortened.
  • Must be expressed as an ISO 8601 duration.
TimepointPostWindowdurationDatetimeOptionalSpecifies the amount of time after the TimepointTarget, the time between the two activities, may be lengthened.
  • Must be expressed as an ISO 8601 duration.

Example: TransitionTimingConstraint

The following is an example of a timing constraint on a transition defined in a workflow.
TransitionTimingConstraint
    <StudyTiming OID="ST.TIMINGS" Name="Study Timings">
        <TransitionTimingConstraint OID="TRTIM.MEAS_1_TO_2" Name="Time between measurement 1 and 2" TransitionOID="TR.MEAS_1_TO_MEAS_2"
            TimepointTarget="PT10M" TimepointPreWindow="PT1M" TimepointPostWindow="PT2M" Type="FinishToStart">
            <Description>
                <TranslatedText xml:lang="en" Type="text/plain">The time between measurement 1 and 2 ideally is 10 minutes, but is allowed to be between 9 and 12 minutes, 
					measured between the end of the first measurement and the start of the second measurement.</TranslatedText>
            </Description>
        </TransitionTimingConstraint>
    </StudyTiming>
    
    <WorkflowDef OID="WF.EXAMPLE" Name="Incomplete workflow example">
        <Transition OID="TR.MEAS_1_TO_MEAS_2" Name="Transition between measurement 1 and 2" SourceOID="IG.MEASUREMENT_1" TargetOID="IG.MEASUREMENT_2" />
    </WorkflowDef>

« RelativeTimingConstraint

DurationTimingConstraint »

  • No labels