Extensions Practical Guide

Search

SNOMED CT Document Library

    Loading...

Page tree

Versions Compared

Old Version 6

changes.mady.by.user David Markwell

Saved on

compared with

New Version Current

changes.mady.by.user Ian Spiers

Saved on

Key

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

SNOMED CT content may sometimes need to be moved from one module to another, to enable it to be published in a different edition. Moving SNOMED CT content up the module dependency chain (i.e. from a given module to a module on which it depends) is known as content promotion. This may be required to make the content accessable accessible to a wider audience. Moving SNOMED CT content down the module dependency chain (i.e. from a given module to a module that is dependent on it) is known as content demotion. This may be required to make the content accessable accessible to a narrower audience. In these situations, it is essential to be aware of the principles for promotion and demotion. These principles ensure the integrity and traceability of the content, in both the original module and the module to which it is moved.

...

Updates should also be made to the respective component inactivation reference sets to indicate that the component has been inactivated because 

Concept
ShowPartsterm
t900000000000487009 |Component moved elsewhere|
, and to the 
Concept
ShowPartsterm
t900000000000524003 |MOVED TO association reference set|
 to indicate the module to which the component has been moved. For . For more information on inactivation and historical associated reference sets, see  3.2.6.3. Managing Component Inactivation. 

...

Warning

Some approaches to content demotion that have previously been proposed are considered to be unsafe. The content demotion approaches that should never be used include:

  • Removing every instance of the component from the International Edition (or source edition)
    • This approach will delete the history of the component for users of the International Edition, who do not use the demoted content. The history of each SNOMED CT component should be traceable in the edition in which the component was created.
  • Retaining the component active in the source module, and creating a new version of the component (i.e., with a more recent effectiveTime) in the less more dependent (extension) module
    • This approach will make the component visible and accessible in the source edition, and users of the source edition would not be aware that the component was demoted to a less more dependent (extension) module
    • This approach may lead to inconsistency between the version of the component in the International Edition and the version in the less more dependent (extension) module. 


Display Footnotes Macro

...