Overview

Relationships are added in an extension to link a new concept to one of its supertypes, or to specify defining attribute relationships. Note that at least one hierarchical ( ) relationship is required for each new extension concept. Extension relationships are distributed in a relationship file, which follows the standard RF2 release file format. For more details on the principles and processes for authoring relationships in an extension, please refer to  5.4.4 Authoring Relationships.

Attributes

In addition to the four  common attributes, relationships also have a sourceId, destinationId, relationshipGroup, typeId, characteristicTypeId and modifierId.

sourceId

The sourceId identifies the concept being defined by the relationship. In the case of a hierarchical ( ) relationship, the sourceId refers to the subtype/child concept.

destinationId

The destinationId represents the value of the defining relationship. In the case of a hierarchical ( ) relationship, the destinationId refers to the supertype/parent concept. The destinationId may refer to a concept in the same extension module as the source concept, or any module on which this extension module depends.

relationshipGroup

The relationshipGroup is an integer that indicates whether or not the relationship is grouped together with other relationships associated with the same source concept. Any relationships with the same sourceId and relationshipGroup integer (other than zero) are considered to belong to the same relationship group. A relationshipGroup of zero (i.e. "0") indicates that the relationship was not grouped with other relationships by the terminology author. For more information on relationship groups, please refer to Relationship groups in SNOMED CT.

typeId

The typeId is a SCTID that specifies the attribute type of the relationship. In the case of a hierarchical relationship, the value of this attribute is . Attribute relationships use a typeId value that refers to a subtype of . Common examples of attribute types include  and .

In most cases, the typeId will refer to an international concept. However, additional attribute concepts may be added in an extension if there is a legitimate clinical need, and clear rules and guidance is provided. For more information, please refer to 5.4.4.1 Add Relationship in an Extension.

characteristicTypeId

The characteristicTypeId is a SCTID, which specifies whether this relationship was stated by an author or was inferred by a description logic classifier. For more information, please refer to 5.6.1.1 Classifying an Edition.

modifierId

The modifierId attribute is a SCTID which specifies the type of description logic that applies to the given relationship - existential restriction (i.e. 'there exists some') or universal restriction (i.e. 'there exists only'). All relationships in the International Edition use the value  . This value is also recommended for extension relationships, as the value   can significantly affect the speed of classification.

Example

In   two rows from the relationship table of the 20170901 US edition are shown. Note that these relationships are used to define the extension concept from the earlier example.

Rows from the relationship table in the 20170901 US Edition

Please note the following:

• The relationship ids use a namespace identifier allocated to the National Library of Medicine (NLM). This indicates that these relationships were originally created by the NLM.
• The relationship ids use a partition identifier of “12”. This indicates that the relationships were created in an extension.
• The moduleId indicates that these relationships are included in the . This is the same module as the source concept belongs to.
• The sourceId indicates that the relationship defines the concept .
• The typeId indicates that the first relationship is an   relationship, while the second relationship specifies the   of the source concept.
• The destinationId indicates that  is a supertype of , and that the   of   is  .