You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 16
Next »
Element Name | StudyEventGroupDef |
---|
Parent Elements | MetaDataVersion |
---|
Element XPath(s) | /ODM/Study/MetaDataVersion/StudyEventGroupDef |
---|
Element Textual Value | None |
---|
Attributes | OID, Name, ArmOID, EpochOID, CommentOID |
---|
Child Elements | (Description?, (StudyEventGroupRef?, StudyEventRef?)+, WorkflowRef?, Coding*) |
---|
Usage/Business Rules | - Business Rule(s):
- The lowest level building block will always be a StudyEvent, which cannot be nested.
- The ArmOID and EpochOID attributes may only be present when the StudyEventGroupDef represents an upper-level study design building block; that is, describing a study cell (the crossing of an arm with an epoch, as defined in the SDTMIG). In such a case, the value of ArmOID must be equal to the value of the OID of an Arm (child element of StudyStructure). The value of EpochOID must be equal to the value of the OID of an Epoch (child element of StudyStructure).
- The ArmOID and EpochOID must be absent when the StudyEventGroupDef is referenced from another StudyEventGroupDef.
- Other Information:
- Whereas StudyEventGroupDefs having both the ArmOID and EpochOID populated represent a study design study cell (as defined in the SDTMIG), StudyEventGroupDefs without ArmOID and EpochOID being populated but which are referenced by a StudyEventGroupDef that has both ArmOID and EpochOID populated will typically represent study elements (as defined in the SDTMIG). Subelements can then be defined by creating additional StudyEventGroupDefs that are referenced by StudyEventGroupDefs representing study elements.
- StudyEventGroupDef can also be used to group other types of planned events that are not described by the study diagram.
|
---|
Attribute | Schema Datatype or Enumeration | Usage | Definition | Business Rule(s) |
---|
OID | oid | Required | Unique identifier for the StudyEventGroupDef element. | - The OID attribute for the StudyEventGroupDef must be unique within the study.
|
Name | name | Required | Human readable identifier for the StudyEventGroupDef element. | - The Name must be unique within the set of StudyEventGroupDef elements for the study.
|
ArmOID | oidref | Optional | Reference to an Arm element defined in the study. | - The ArmOID must match the OID attribute for an Arm element contained in the Study/MetaDataVersion.
|
EpochOID | oidref | Optional | Reference to an Epoch element defined in the study. | - The EpochOID must match the OID attribute for an Epoch element contained in the Study/MetaDataVersion.
|
CommentOID | oidref | Optional | Reference to a CommentDef element defined in the study. | - The CommentOID must match the OID attribute for a CommentDef element contained in the Study/MetaDataVersion.
|
A StudyEventGroup is a study building block that groups a number of smaller building blocks, which can themselves be StudyEventGroups or StudyEvents. It thus allows nesting of building blocks.
The lowest level building block will always be a StudyEvent, which cannot be nested.
The ArmOID and EpochOID attributes may only be present when the StudyEventGroupDef is en upper-level study design building block, describing a "study cell", which is the crossing of anarm with an epoch. The value of ArmOID must be equal to the value of the OID of an Arm (element in StudyDesign). The value of EpochOID must be equal to the value of the OID of an Epoch (element in StudyStructure). The ArmOID and EpochOID must be absent when the StudyEventGroupDef is referenced from another StudyEventGroupDef.
The WorkflowRef references a workflow definition, a WorkFlowDef
ODM2DEV-60
-
Getting issue details...
STATUS
.