You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
| Element Name | StudyEventGroupRef |
|---|
| Parent Elements | Protocol, StudyEventGroupDef |
|---|
| Element XPath(s) | - /ODM/Study/MetaDataVersion/Protocol/StudyEventGroupRef
- /ODM/Study/MetaDataVersion/StudyEventGroupDef/StudyEventGroupRef
|
|---|
| Element Textual Value | None |
|---|
| Attributes | StudyEventGroupOID, OrderNumber, Mandatory, CollectionExceptionConditionOID |
|---|
| Child Elements | (Description?) |
|---|
| Usage/Business Rules | Other Information: - Note that a StudyEvenGroupRef may appear within a StudyEventGroupDef to support recursion.
The OrderNumber attribute provide an ordering on the StudyEventGroupDefs for use whenever a list of StudyEventGroupDefs is presented to a user. They do not imply anything about event scheduling, time ordering, or data correctness. Order of execution and timing between study events and groups of study events must be defined in WorkflowDef elements. Scheduling will be realized in StudyTiming and its child elements that reference StudyEventGroups.
The Mandatory flag indicates that the clinical data for the containing MetaDataVersion would be incomplete without an instance of this type of Study Event Group. ODM clinical data files that are incomplete in this sense may be considered incomplete for study review and analysis purposes.
If the CollectionExceptionConditionOID attribute is provided, it references a ConditionDef that describes the circumstances under which data for this Study Event Group should not be executed.
|
|---|