...
Concepts can be added to an extension, either to address content gaps or to expand the scope of SNOMED CT to include concepts that are used locally. Concepts in an extension follow the same logical design as concepts in the International Edition. They Extension concepts are distributed in a a concept file, which follows the standard RF2 concept release file format. Additionally, descriptions and relationships associated with extension concepts should be represented in separate description and relationship files. Please refer to the section on authoring for For more details on the principles and processes for authoring components concepts in an extension, please refer to 5.4.2 Authoring Concepts.
Attributes
In the case of concepts, one additional attribute is used with the four common attributesaddition to the four common attributes, extension concepts also have a definitionStatusId.
definitionStatusId
The definitionStatusId attribute definitionStatusId is used to state whether a specifies whether the concept is
| Gloss |
|---|
| t | primitive |
|---|
| GlosTerm | primitive concept |
|---|
|
or
| Gloss |
|---|
| t | fully defined |
|---|
| GlosTerm | Sufficiently defined concept |
|---|
|
.
Initially this is set toIf defining relationships are added, which sufficiently define the concept, then the definitionStatusId should be set to | Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000074008 900000000000073002 |PrimativeDefined| |
|---|
|
because it is not possible for a concept to be. Otherwise, the extension concept is | Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000073002 900000000000074008 |Defined| |
|---|
|
until its defining relationships have been added. If the defining relationships of a concept are found to be sufficient to fully define the concept, the definitionStatusId can then be updated to reflect this.
| Anchor |
|---|
| Concept example |
|---|
| Concept example |
|---|
|
Example
In
| Caption reference |
|---|
| CapRefId | concept-table-20170901-us-edition |
|---|
| CapRefType | Figure |
|---|
|
below, a row from the concept table of the 20170901 US edition is shown, which represents In below, a row associated with the concept
| Concept |
|---|
| t | 5281000124103 |Persistent asthma| |
|---|
|
. from the concept table of the US edition, 2070901 is presented. Note that the attribute values in this row have been set according to the rules previously described.
Image Modified
Key points as follows
| Caption label |
|---|
| CapId | concept-table-20170901-us-edition |
|---|
| CapType | Figure |
|---|
|
A row from the concept table in the 20170901 US Edition |
Please note the following:
- The concept The namespace identifier in the id uses a namespace owned by identifier allocated to the National Library of Medicine which (NLM). This indicates that this concept was originally created by the US NRCNLM.
- The concept id uses a partition identifier is “10” so we know this concept originated of “10”. This indicates that the concept was created in an extension.
- The moduleId indicates that this concept is included in the
| Concept |
|---|
| ShowParts | term |
|---|
| t | 731000124108 |US National Library of Medicine maintained module| |
|---|
|
, which is a module in the US Edition. - The definitionStatusId states that this concept is a
| Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000074008 |PrimativePrimitive| |
|---|
|
concept.