Skip to end of metadata
Go to start of metadata

Current Version - Under Revision

Terminology servers should provide efficient access to the Identifiers that represent concepts with structurally significant Roles within the terminology. lists the concepts that have the most clear-cut structurally significant Roles . A terminology server should enable access to these Identifiers by an easy to use name of enumeration. In addition a terminology server should provide a service that rapidly determines whether a given concept is a subtype of any of these concepts . It is also useful to for the terminology server to extend similar functionality to all direct subtypes of the root concept ( |SNOMED CT Concept| ) and to subtype descendants of |concept model attribute| .

Table 30. Essential concept Identifiers




Preferred Term



|SNOMED CT Concept|

The root concept . All other active concepts are subtypes of this concept .


|SNOMED CT Model Component|

All active metadata concepts are subtypes of this concept .


|core metadata concept|

All enumerated values applicable to core components are subtypes of this concept .


|foundation metadata concept|

All reference sets and all reference set related metadata concept are subtypes of this concept .


|reference set|

All reference sets are subtypes of this concept .


|is a|

The Attribute used to specify the subtype Relationship between concepts .



All Attribute ( relationship type ) concepts are subtypes of this concept .


|concept model attribute|

With the exception of the subtype Relationship (see above) all relationship types that are used in the SNOMED CT Concept Model are subtypes of this concept .


|namespace concept|

Each subtype of this concept represents an extension namespaces allocated by the IHTSDO .


|navigational concept|

Subtypes of this concept to provide nodes in navigation hierarchies . They act as grouper categories that do not have any semantic meaning and thus do not appear elsewhere in the SNOMED CT hierarchy.