Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Element NameRelativeTimingConstraint
Parent Element(s)StudyTiming
Element XPath(s)
  • /ODM/Study/MetaDataVersion/Protocol/StudyTiming/RelativeTimingConstraint
Element Textual ValueNone
Usage
AttributesOID, Name, PredecessorOID, SuccessorOID, TimepointRelativeTarget, Type, TimepointPreWindow, TimepointPostWindow
Child Elements(Description?)
AttributeSchema Dataype or EnumerationUsageDefinitionBusiness RulesOIDoidRequiredNamenameRequiredPredecessorOIDoidrefRequired

SuccessorOID

oidrefRequiredTimepointRelativeTargetdurationDatetimeRequiredType(StartToStart, StartToFinish, FinishToStart, FinishToFinish)OptionalTimepointPreWindowdurationDatetimeOptionalTimepointPostWindowdurationDatetimeOptional

Contained in:

...

An in time earlier StudyEventGroup, StudyEvent, ItemGroup or Item, to which the constraint applies, is referenced by the PredecessorOID. 
An in time later StudyEventGroup, StudyEvent, ItemGroup or Item, to which the constraint applies, is referenced by the SuccessorOID.

If the two activities are used in a defined workflow, and there is a transition between the two activities in that workflow, then TransitionTimingConstraint must be used to describe the timing, instead of RelativeTimingConstraint.

The Type attribute defines whether the constraint applies to start or to end of the activities. Valid values for the attribute are:

...

If the Type attribute is omitted, "StartToStart" must be assumed.

The TimepointRelativeTarget defines the planned time between the two activities, expressed as a non-negative ISO 8601 duration.

The TimepointPreWindow describes the amount of time, expressed as a non-negative ISO 8601 duration, to which the relative time between the two activities may be shortened with respect to the value in TimepointRelativeTarget.

...

Pagenav2