Slot: mandatory
Is this element required?
URI: dds:slot/mandatory Alias: mandatory
Applicable Classes
| Name | Description | Modifies Slot |
|---|---|---|
| SiteOrSponsorComment | A feedback element that contains comments from a site or sponsor, distinct from the general Comment class | no |
| Analysis | Analysis extends Method to capture analysis-specific metadata including the reason for analysis, its purpose, and data traceability for the results used. Expressions and parameters from Method can be generic or implementation-specific. |
no |
| Measure | A data cube property that describes a measurable quantity or value | no |
| Check | A reusable validation check included in the metadata package, such as a published CORE rule. Linked many-to-many by reference to the metadata and/or data elements it applies to, and optionally citing an external published rule so checks stay reusable and loosely coupled. Distinct from RangeCheck, which is an inline executable comparison; a RangeCheck may implement a Check. | no |
| ItemGroup | A collection element that groups related items or subgroups within a specific context, used for tables, FHIR resource profiles, biomedical concept specializations, or form sections | no |
| ConceptProperty | A reified property concept that exists within the context of its containing topic concept | no |
| Dimension | A data cube property that describes a categorical or hierarchical dimension | no |
| Display | A rendered output of an analysis result. | no |
| DataStructureDefinition | A structural element that defines the organization of a data cube for analysis, including dimensions, attributes, and measures | no |
| Query | A reified query (discrepancy, request for clarification, or annotation) raised against one or more metadata and/or data elements. Modelled as an intermediate relationship node so a single query can relate to many elements (many-to-many) and be referenced rather than embedded. Internal queries originate within the organization; external queries (e.g. site or sponsor) carry their source. | no |
| CubeComponent | An abstract data field that represents a component in a data structure definition, referencing an Item for its definition | no |
| ProvisionAgreement | An agreement element that describes the contractual relationship between a Data Provider and a Data Consumer regarding data provision | no |
| Concept | An abstract concept that can be referenced and specialised by data implementations. Holds ConceptProperties describing the concept's expected data shape. Multiple ItemGroups or Items can implement the same Concept, allowing standard biomedical concepts to be implemented differently across studies while remaining semantically aligned. | no |
| Method | A reusable computational procedure that describes how to derive values and can be referenced by Items. Analysis and Derivation concepts can be implemented by a Method. Properties can be referenced by Parameters in its expressions. |
no |
| DataProduct | A governed collection that represents a purpose-driven assembly of datasets and services with an owning team and lifecycle. The DataProduct defines the boundary of accountability between data producers and consumers. | no |
| LogicalPredicate | A reusable, composable, and nestable logical expression resolving to a boolean. Used for applicability conditions, validation rules, eligibility criteria, and skip logic. This is a data-model predicate — not a clinical condition (diagnosis). Implements usdm:Condition (the study-design predicate, distinct from the clinical FHIR Condition resource). | no |
| Dataflow | An abstract representation that defines data provision for different reference periods, where a Distribution and its Dataset are instances | no |
| CodeList | A value set that defines a discrete collection of permissible values for an item, corresponding to the ODM CodeList construct | no |
| Policy | A set of usage and access rules (ODRL) governing data. For a DTA this is typically an ODRL Agreement between an assigner (provider) and assignee (consumer), composed of permissions, prohibitions and obligations. | no |
| Specification | The root specification container: a versioned, governed definition of the data model for a study or data product. Links items, item groups, methods, code lists, concepts, and study design references. Projects to Define-XML MetaDataVersion, FHIR ImplementationGuide, and OMOP CDM metadata. ODMSerializationMetadata is applied by the ODM output generator, not here. | no |
| GovernedElement | no | |
| DataAttribute | A data cube property that describes additional characteristics or metadata about observations | no |
| Comment | A descriptive element that contains explanatory text provided by a data or metadata handler | no |
| Item | A data element that represents a specific piece of information within a defined context, with data type, constraints, and derivation methods | no |
| ApplicabilityCondition | A reusable, named applicability condition describing the circumstances under which a containing context applies. References one or more LogicalPredicates combined with AND. Distinct from LogicalPredicate (the expression itself): ApplicabilityCondition is the named, governed wrapper referenced from Items, ItemGroups, Parameters, and Analyses. | no |
| Governed | A mixin that provides slots for audit trail and standards governance, including mandatory status, comments, and attribution | no |
Properties
- Range: Boolean
Identifier and Mapping Information
Schema Source
- from schema: https://w3id.org/dds
Mappings
| Mapping Type | Mapped Value |
|---|---|
| self | dds:mandatory |
| native | dds:mandatory |
LinkML Source
name: mandatory
description: Is this element required?
from_schema: https://w3id.org/dds
rank: 1000
alias: mandatory
owner: Governed
domain_of:
- Governed
range: boolean