You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 17
Next »
| Element Name | ItemGroupDef |
|---|
| Parent Elements | MetaDataVersion |
|---|
| Element XPath(s) | /ODM/Study/MetaDataVersion/ItemGroupDef |
|---|
| Element Textual Value | None |
|---|
| Attributes | OID, Name, Repeating, IsReferenceData, Structure, ArchiveLocationID, DatasetName, Domain, Type, Purpose, StandardOID, IsNonStandard, HasNoData, CommentOID |
|---|
| Child Elements | (Description?, Class?, (ItemGroupRef*, ItemRef*)+, Coding*, WorkflowRef?, Origin*, Alias*, leaf?) |
|---|
| Usage/Business Rules | - Business Rule(s):
- There must be an ItemGroupDef element for each unique ItemGroupOID attribute value in the study.
- Other Information:
- ODM v2.0 introduces nested ItemGroups. ItemGroupRef elements may be added to ItemGroupDef to create hierarchical data structures of arbitrary depth. Nested ItemGroupDefs can be used for enhanced re-usability of ItemGroups. They can also be used to represent semantic relationships between items, items that share common behaviors such as skip logic, or items that are displayed or collected together.
- The Coding child element allows to associate semantics within the group. For example, a LOINC panel code in the case that the ItemGroup represents a laboratory panel.
- The WorkflowRef child element allows to reference a workflow definition (WorkflowDef) for navigation within the ItemGroup, for example, when the ItemGroup represents a form or questionnaire (or part of it) where there is a workflow between the items or groups of items.
|
|---|