...
Attributes:
| OID | oid | ||
| Name | name | ||
| (PredecessorStudyEventGroupOID, PredecessorStudyEventOID, PredecessorItemGroupOID, PredecessorItemOID) | oidref | ||
(SuccessorStudyEventGroupOID, SuccessorStudyEventOID, SuccessorItemGroupOID, SuccessorItemOID) | oidref | ||
| Type | (StartToStart, StartToFinish, FinishToStart, FinishToFinish) | (optional) | |
| TimepointRelativeTarget | durationDatetime | ||
| TimepointPreWindow | durationDatetime | (optional) | |
| TimepointPostWindow | durationDatetime | (optional) |
...
The RelativeTimingConstraint element describes a relative timing constraint between two activities or groups of activities, represented by StudyEventGroups, StudyEvents, ItemGroups or Items.
An in time earlier StudyEventGroup, to which the constraint applies, is referenced by the PredecessorStudyEventGroupOID. TODO: describe similar for StudyEvent, ItemGroup and Item (i.e. PredecessorStudyEventOID, PredecessorItemGroupOID, PredecessorItemOID).
ALTERNATIVE: use "PredecessorOID" for all of these.An in time earlier StudyEvent, or Item, to which the constraint applies, is referenced by the PredecessorStudyEventOIDPredecessorOID.
An in time later StudyEventGroup, to which the constraint applies, is referenced by the SuccessorStudyEventGroupOID. An in time later StudyEventStudyEvent, ItemGroup or Item, to which the constraint applies, is referenced by the SuccessorStudyEventOIDSuccessorOID.
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.
...