Terminology servers should provide efficient access to the Identifiers that represent concepts with structurally significant Roles within the terminology. Table 5.1-1 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 or 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 for the terminology server to extend similar functionality to all direct subtypes of the root concept ( 138875005 | SNOMED CT Concept| ) and to subtype descendants of 410662002 | concept model attribute| .
Table 5.1-1: Essential concept Identifiers
Id | Significance |
|---|---|
The root concept. All other active concepts are subtypes of this concept. | |
All enumerated values applicable to core components are subtypes of this concept. See Appendix E: Concept Enumerations for information about these metadata data concepts. | |
All reference sets and all reference set related metadata concept are subtypes of this concept. | |
All reference sets are subtypes of this concept. | |
The Attribute used to specify the subtype Relationship between concepts. | |
All Attribute ( relationship type) concepts are subtypes of this concept. | |
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. | |
Each subtype of this concept represents an extension namespaces allocated by the SNOMED International. | |
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. |
Feedback
Overview
Content Tools
Apps