This concept is the supertype for metadata used directly by SNOMED CT components.
Concept Addition Rules
No new subtype children may be added in an extension.
See tables below for concept addition rules for each of the subtypes of .
Characteristic Type
Hierarchy
Purpose
This subhierarchy provides the values for Relationship.characteristicTypeId.
Examples
Concept Addition Rules
No new subtype descendants may be added in an extension.
Definition Status
Hierarchy
Purpose
This subhierarchy provides the values for Concept.definitionStatusId
Examples
Concept Addition Rules
No new subtype descendants may be added in an extension.
Description Type
Hierarchy
Purpose
This subhierarchy provides the values for Description.typeId
Examples
Concept Addition Rules
Additional types permitted provided these are additive and do not replace the synonym or fully specified name values
Concept Addition Uses Cases
Different lengths of text for different purposes
Different formats for text including HTML
Specialized usage of text for a specific purpose
Modifier
Hierarchy
Purpose
This subhierarchy provides the values for Relationship.modifierId
Examples
Concept Addition Rules
No new subtype descendants may be added in an extension.
Module
Hierarchy
Purpose
This subhierarchy provides the concepts used to identify modules
Examples
Concept Addition Rules
The addition of modules that form part of the extension is required. These new module concepts must either be direct children of or descendants of a child of that is owned by the same extension provider. It is not permitted to add modules as subtypes of modules maintained by another extension provider.
Each module concept added within an extension must have an identifier that contains the extension's namespace identifier.
Concept Addition Uses Cases
The addition of at least one module concept is essential for all extensions. More than one module concept may be added to enable content to be organized into separate modules.