All reference sets require a concept to be created that represents the meaning of the reference set, provides the identification of the reference set, and names the reference set. These reference set concepts are created in the subhierarchy as subtypes of a reference set concept that represents the associated reference set pattern. For more information about creating a reference set concept in an extension, please refer to 5.4.5.1 Create New Reference Set in an Extension.

In this section, we discuss an example reference set concept ( ) from the 20170430 Canadian extension, and explain how this concept and its associated descriptions, relationships and language preferences are represented.

Reference Set Concept

In below, a row from the concept table is shown for the concept .

Extensions Practical Guide > 4.3.2.2 Reference Set Example > image2017-7-5_13-50-46.png

Example reference set concept in the concept table

Please note the following:

The concept id uses a namespace identifier allocated to Canada Health Infoway.
The concept id uses a partition identifier of “10” to indicate that this concept was create in an extension.
The moduleId indicates that this concept belongs to the .
The definitionStatusId indicates that this concept is . Please note that all metadata concepts in SNOMED CT are .

Reference Set Description

In below, a set of rows from the description table are shown. These descriptions provide terms that describe the concept .

Extensions Practical Guide > 4.3.2.2 Reference Set Example > image2017-7-5_13-54-11.png

Example descriptions for the reference set concept

Please note the following:

The description id uses a namespace identifier allocated to Canada Health Infoway.
The description id uses a partition identifier of “11” to indicate that these descriptions were created in an extension.
The moduleId indicates that these descriptions belong to the .
The conceptId links the descriptions to the reference set concept .
A languageCode of "en" indicates that the terms are written in English.
The typeId indicates that the first description is a , while the following two are of type .
The term is used to name the associated reference set.
The caseSignificanceId indicates that the terms is .

Reference Set Relationship

In , a row from the relationship table is shown. This relationship defines the supertype concept of .

Extensions Practical Guide > 4.3.2.2 Reference Set Example > image2017-7-5_13-57-8.png

Example relationships for the reference set concept

Please note the following:

The relationship id uses a namespace identifier allocated to Canada Health Infoway.
The relationship id uses a partition identifier of “12” to indicate that this relationship was originally created in an extension.
The moduleId indicates that these relationships belong to the .
The sourceId indicates that the relationship applies to the concept .
The typeId indicates that the relationship represents an relationship.
The destinationId indicates that is a supertype of .
The characteristicTypeId and modifierId columns have been omitted from this diagram for brevity.

Reference Set Language preferences

In below, a set of rows from the are shown. These rows define the language preferences for the descriptions associated with the concept .

Extensions Practical Guide > 4.3.2.2 Reference Set Example > image2017-7-5_14-0-56.png

Example language preferences for the reference set concept

Please note the following:

The id is a UUID that was generated for the corresponding refset member.
The moduleId indicates that these refset members belong to the .
The refsetId column indicates that these rows are members of the . Note, that if the relevant language reference set does not exist, this must be created using the same process.
The referencedComponentId column refers to the descriptions for which the acceptability is being specified.
The acceptabilityId column indicates the and descriptions in the given language dialect (in this case Canadian English).