This concept enumeration represents a value that can be applied to the description.caseSignificanceId field. This is used to indicate whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa). The Table below shows the current set of values for this concept enumeration.
Case significance (core metadata concept) (900000000000447004)
The text of the description.term must be presented in the case in which it is specified.
The initial character of the description.term is case insensitive and can be changed from upper to lower case (or vice-versa) if appropriate to the context in which it is used. This applies only to the first character of the term as a whole, not to the initial character of other words in the term.
The entire description.term is case insensitive and can be can be changed from upper to lower case (or vice-versa) if appropriate to the context in which it is used.
This concept enumeration represents a value that can be applied to the relationship.typeId field. This is used to identify the concept model attribute that determines the type of relationship between two concepts. Exhibit E.7-1 shows the full range of values of values that can be applied to the relationship.typeId field.
Exhibit E.7-1: Subtype and Concept Model Attributes
/* subtype relationship to a supertype concept */
This concept enumeration applies to the field which is present in all released SNOMED CT components (RF2). The value applied to a particular component indicates the development module within which that component was created and is being maintained.
Each of the values in Exhibit E.1-1 represents a SNOMED CT module. The range of permitted values is extensible by addition of branches to the hierarchy shown in modules managed by other organizations (i.e. in an extensions namespace) and to add specific module identifiers within each branch.
Exhibit E.1-1: Hierarchy of SNOMED CT moduleId values
Subtypes of the 900000000001073010 | Attribute value| provide sets of values for use in specific attributes of specific types of reference sets. Exhibit E.8-1 shows some of the values in this part of the metadata hierarchy. Additionally branches of the hierarchy can be added to support new requirements for specific reference set types.
Exhibit E.8-1: Reference Set Attribute Values
This concept enumeration represents a value that can be applied to the description.typeId field. This is used to indicate whether the description represents a fully specified name, a synonym a definition or some other symbolic or textual representation of the associated concept. The Table below shows the current set of values for this concept enumeration.
Description type (core metadata concept) (900000000000446008)
Concept
Comment
The description.term represents the fully specified name of the associated concept in the language indicated by the description.languageCode.
The description.term represents a term that is used to represent the associated concept in the language indicated by the description.languageCode.
Note: The preferred term used in a given language or dialect is a synonym. Preference and acceptability of a particular synonyms is indicated by a .
The description.term represents a textual definition of the associated concept in the language indicated by description.languageCode.
This concept enumeration enumeration represents a value that can be applied to the relationship.characteristicTypeId field. This is used to indicate that a relationship forms part of the definition of the source concept. The Table below shows the current set of values for this concept enumeration.
Characteristic type (core metadata concept) (900000000000449001)
Concept
Comment
A general value which is a supertype of and .
This value is not applied to any released relationships.
Indicates that this defining relationship was inferred by a description logic classifier from the stated view of the concept definition.
Since 2018 the characteristicTypeId of all released relationships has this value. This is because, stated view definitions are now represented by OWL axioms rather than relationships.
Obsolete values that are no longer used
Indicates that this defining relationship was stated by a terminology author.
Not used since 2018 as stated views of concept definitions are now represented using OWL axioms rather than relationships.
The relationship is not part of the definition of the concept but indicates a possible qualification that may be applied to refine a postcoordinated expression that refers to the source concept.
Note used since 2012 when Release Format 2 was introduced.
The relationship is not part of the definition of the concept but is used to convey some additional information about the concept . This additional information may only be applicable to a particular jurisdiction or use case.
Note used since 2012 when Release Format 2 was introduced.
This concept enumeration represents a value that can be applied to the concept.definitionStatusId field. This is used to indicate whether the current set of relationships applied to a concept are sufficient to define it relative to its supertypes. The Table below shows the current set of values for this concept enumeration.
Definition status (core metadata concept) (900000000000444006)
Concept
Comment
The set of defining relationships applied to the concept are asserted to fully define the concept.
Any concept or expression for which all these defining relationships are true is either equivalent to or subsumed by this concept.
Any concept or expression for which any of these defining relationships is not true is neither equivalent to nor subsumed by this concept.
The set of defining relationships applied to the concept are asserted to be incompletely define the concept. The concept is currently considered to be primitive.
A concept or expression for which all these defining relationships are true may be equivalent to or subsumed by this concept. However, it is not possible to compute this from the definition - because the missing element in the definition may or may not apply to the other concept or expression.
Any concept or expression for which any of these defining relationships is not true is neither equivalent to nor subsumed by this concept.
This concept enumeration represents a value that can be applied to the relationship. modifierId field. This is used to indicate the type of Description Logic (DL) restriction (some, all, etc.) that applies to the relationship. The Table below shows the current set of values for this concept enumeration.
Modifier (core metadata concept) (900000000000450001)
Concept
Comment
Indicates that description logic restriction represented by this defining relationship applies to some aspect of the concept.
Indicates that description logic restriction represented by this defining relationship applies to all aspects of the concept.
This value is not used for any concepts.
SNOMED CT core components have some fields that have values represented by concepts in specific parts of the SNOMED CT hierarchy. These are referred to as concept enumerations.
The range of permitted values for each of the concept enumerations is the set of subtypes of a specified concept which is itself a subtype of 900000000000442005 |Core metadata concept (core metadata concept). The current set of concept enumeration types is shown in Table Appendix E:-1. The values of each of these and the ways they should be used in implemented systems are described in the following subsections.
Core metadata concept (core metadata concept) (900000000000442005)
Each subtype of this concept represents a development module. These concepts provide values to the field that is present in all component release files. The value indicates the module within which a component was created and is being maintained.
Each subtype of this concept represents a value that can be applied to the concept.definitionStatusId field. This is used to indicate whether the current set of defining relationships applied to a concept are sufficient to define it relative to its supertypes.
Each subtype of this concept represents a value that can be applied to the description.typeId field. This is used to indicate whether the description represents a fully specified name, a synonym, a text definition or some other symbolic or textual representation of the associated concept.
Each subtype of this concept represents a value that can be applied to the description.caseSignificanceId field. This is used to indicate whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa).
Each subtype of this concept represents a value that can be applied to the relationship.characteristicTypeId field. This is used to indicate whether a relationship forms part of the definition of the source concept.
Each subtype of this concept represents a value that can be applied to the relationship.modifierId field. This is used to indicate the type of description logic (DL) restriction (some, all, etc.) that applies to the relationship.
Each subtype of this concept represents a value that can be applied to the identifier.identifierSchemeId field. This is used to indicate the scheme to which the identifier value belongs.