Search



Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

In SNOMED CT, modules are used to organize content for maintenance purposes. All concepts, descriptions, relationships, and reference set members must be belong to amoduleAccording to the logical design, this association between a component or derivative and its associated module is made using the moduleId attribute. This attribute is common to all components and reference sets.  All components and refset members within a module are maintained by a single organization, which could be local organization, aNational Release Center (NRC), or SNOMED International itself. The moduleId refers to a concept that represents and names the module in which a component or refset is currently maintained.

SNOMED International Modules

The International Edition includes two modules. The core components of SNOMED CT (including clinical concepts, as well as their descriptions and relationships) all belong to the | SNOMED CT core module|The other module is the | SNOMED CT model component module| , which contains metadata components (including attributes, reference set identification concepts and module concepts). Both these modules are maintained by  SNOMED International.

SNOMED International also maintains several other modules that supplement, rather that being part of, the International Edition. These include the | SNOMED CT to ICD-10 rule-based mapping module| and the | LOINC - SNOMED CT Cooperation Project module| .

Modules Maintained by Members and Affiliates

Content and reference sets maintained by Members and Affiliate licensees is also organized into one or more modules. In this case, the modules are represented by concepts that are also created and maintained by the same organization. The module identifier concept, and its associated descriptions and relationships, will usually be part of the module that it identifies1 .

Examples

Examples of Modules

 below lists some examples of modules as well as the organization responsible for maintenance and distribution of the module. Note that the namespace identifier (highlighted in red) forms part of the identifier for the non-International modules because the module concepts were created as part of the extension.

idModule nameMaintained by
449080006SNOMED International
731000124108US National Library of Medicine – Member
22091000087100Canada Health Infoway – Member
999000011000000103NHS Digital (UK) – Member

Examples of Components Assigned to Modules

 includes selected columns and rows from the description file for the the US Edition, 20170301. Note that in the table below the moduleId column includes the preferred synonym for the module as well as the module identifier for improved readability, whereas that column of the release file only includes the identifier.

id

 active

 moduleId

 conceptId

 term

301485011

1

195967001

 Asthma

1563100012411615281000124103Persistent asthma
1811140111116680003Is a
The example above reinforces some key points. Firstly, all components are part of a module which can be seen in the moduleId column. Secondly, components in an edition may belong to modules maintained by seperate organizations.


Footnotes
Ref Notes
1 Alternatively, the module identifier concept, descriptions and relationships may be part of another module maintained by the same organization. In that case, the identified modules necessarily depend upon the module that contains those concepts, descriptions and relationships. Therefore, it is usually simpler to keep the module identifier components in the module they identify.


Feedback
  • No labels