Search



Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The first concept to be created in any extension is a module concept. The identifier of this module concept becomes the moduleId to which all extension content is assigned. The moduleId uses the namespace identifier allocated to the extension producer. Additional modules can be created within the same extension, if there is a requirement to maintain or publish sets of components separately. Module concepts must be created as a descendant of 

Concept
t900000000000443000 |Module (core metadata concept)|
 in a subhierarchy that is dedicated to the given extension provider. For more details about creating new concepts in an extension, please refer to  5.4.2.1 Add Concept in an Extension.

The first module concept in an extension, and its associated descriptions, relationships and language reference set members, must all belong to the given module. This means that the id of the new module concept will match the value assigned to moduleId for that row. Subsequent module concepts can either belong to its own module, or to another module owned by the same extension producer on which the given module depends. The module concept must have the definition status

Concept
ShowPartsterm
t900000000000074008 |Primitive|
 as the
Concept
ShowPartsterm
t900000000000441003 |SNOMED CT Model Component (metadata)|
 hierarchy has no concept model attributes. Please see the following page for information about Module Naming Conventions.

Example

The following example uses the module concept

Concept
t45991000052106 |SNOMED CT Sweden NRC maintained module|
 from the Swedish extension. Note that this concept uses the namespace identifier assigned to the Swedish NRC - 1000052. As we can see in
Caption reference
CapRefIdmodule-concept-in-concept-table
CapRefTypeTable
, the module identifier appears in the id column and in the moduleId column of the concept table. A value of
Concept
ShowPartsterm
t900000000000074008 |Primitive|
 is used for the definitionStatusId. 

Footnote Macro

Please note that in the tables above the Preferred Term is shown for some fields of type SCTID to aid the readability of the tables.


Caption label
CapIdmodule-concept-in-concept-table
CapTypeTable
Module concept in concept table


ideffectiveTimeactivemoduleIddefinitionStatusId
45991000052106 20121221145991000052106

Concept
t900000000000074008 |Primitive|

Caption reference
CapRefIddescriptions-for-module-concept
CapRefTypeTable
 shows the two necessary descriptions for the module concept i n the description table. Note that the same namespace identifier is used as part of the description identifiers.

Caption label
CapIddescriptions-for-module-concept
CapTypeTable
Module descriptions in description table


ideffectiveTimeactivemoduleIdconceptIdlanguageCodetypeIdtermcaseSignificanceId
3604311000052110 2012122114599100005210645991000052106en

Concept
t900000000000003001 |Fully specified name|

SNOMED CT Sweden NRC maintained module (core metadata concept)

Concept
t900000000000448009 |Entire term case insensitive|

3604321000052119 2012122114599100005210645991000052106en

Concept
t900000000000013009 |Synonym|

SNOMED CT Sweden NRC maintained module

Concept
t900000000000448009 |Entire term case insensitive|

Caption reference
CapRefIdrelationship-for-module-concept
CapRefTypeTable
 shows the required
Concept
ShowPartsterm
t 116680003 |Is a|
relationship for the module concept in the relationship table. Note that the same namespace identifier is used as part of the relationship identifier.


Caption label
CapIdrelationship-for-module-concept
CapTypeTable
Module relationship in relationship table


ideffectiveTimeactivemoduleIdsourceIddestinationIdrelationshipGrouptypeIdcharacteristicTypeIdmodifierId
8721000052122 2012122114599100005210645991000052106

Concept
t900000000000443000 |Module|

0

Concept
t 116680003 |Is a|
 

Concept
t900000000000451002 |Existential restriction modifier|

Concept
t900000000000011006 |Inferred relationship|

Note that a reference set is also used to specify the language preferences for the module concept. For additional details please refer to  4.3.2.4.1 Language Reference Set.


Display Footnotes Macro