RelativeTimingConstraint

The RelativeTimingConstraint element describes a relative timing constraint between two activities or groups of activities, represented by StudyEventGroups, StudyEvents, ItemGroups or Items.

Element Name	RelativeTimingConstraint
Parent Element(s)	StudyTiming
Element XPath(s)	/ODM/Study/MetaDataVersion/Protocol/StudyTimings/StudyTiming/RelativeTimingConstraint
Element Textual Value	None
Attributes	OID, Name, PredecessorOID, SuccessorOID, RelativeTimepointTarget, Type, TimepointPreWindow, TimepointPostWindow
Child Elements	(Description?)
Usage/Business Rules	Business Rule(s): If 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.

Attribute	Schema Dataype or Enumeration	Usage	Definition	Business Rules
OID	oid	Required	Unique identifier.	Must be unique within the Study.
Name	name	Required	Human readable name.	Must be unique within the set to timing constraints within the Study.
PredecessorOID	oidref	Required	Identifies a StudyEventGroup, StudyEvent, ItemGroup or Item that occurs immediately before the RelativeTimepointTarget.	Must match an OID for a StudyEventGroupDef,StudyEventDef, ItemGroupDef or ItemDef in the same Study/MetaDataVersion.
SuccessorOID	oidref	Required	Identifies a StudyEventGroup, StudyEvent, ItemGroup or Item tha occurs immediately after the RelativeTimepointTarget.	Must match an OID for a StudyEventGroupDef,StudyEventDef, ItemGroupDef or ItemDef in the same Study/MetaDataVersion.
TimepointRelativeTarget	durationDatetime	Required	The relative timing between two activities or groups of activities.	Must be expressed as an ISO 8601 duration
Type	(StartToStart, StartToFinish, FinishToStart, FinishToFinish)	Optional	Defines 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, Start to Start is assumed.
TimepointPreWindow	durationDatetime	Optional	Adds a lower bound to a time window for the RelativeTimepointTarget.	Must be expressed as an ISO 8601 duration
TimepointPostWindow	durationDatetime	Optional	Adds an upper bound to a time window for the RelativeTimepointTarget.	Must be expressed as an ISO 8601 duration

Example 1:

The following is a simple example of a relative timing constraint between 2 visits.

RelativeTimingConstraint

<RelativeTimingConstraint xmlns="http://www.cdisc.org/ns/odm/v2.0"
    OID="CONSTR.VISIT1_to_VISIT2" 
    Name="Relative Timing Constraint between Visit 1 and Visit 2 of 14 days with a pre-window of 1 day, and a post-window of 3 days"
    PredecessorOID="SE.VISIT1" SuccessorOID="SE.VISIT2" TimepointRelativeTarget="P14D" 
    TimepointPreWindow="P1D" TimepointPostWindow="P3D" Type="StartToStart">
    <Description>
        <TranslatedText xml:lang="en" Type="text/plain">Relative Timing Constraint between Visit 1 and Visit 2 of 14 days with a pre-window of 1 day, and a post-window of 3 days</TranslatedText>
        <TranslatedText xml:lang="nl" Type="text/plain">Visite 2 volgt 14 dagen na Visite 1 met een pre-visite venster van 1 dag en een post-visite venster van 3 dagen</TranslatedText>
    </Description>
</RelativeTimingConstraint>

Page tree

RelativeTimingConstraint