Extensions Practical Guide

Search

SNOMED CT Document Library

    Loading...

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Anne Randorff Højen

Saved on

compared with

New Version Current

changes.mady.by.user Anne Randorff Højen

Saved on

Key

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

...

  • Destination Concept: The target of the relationship may belong to the extension module, or any module on which the extension module depends (including an international module). However, care should be taken to avoid intermediate concepts as described in 5.4.2.1 Add Concept in an Extension). Additionally, it is important to ensure that the added relationships do not induce any cycles, i.e. it should be ensured that the added relationships retain the SNOMED CT hierarchy as a Directed Acyclic Graph.  
Cyclic GraphDirected Acyclic Graph

NOT ALLOWED

Image Modified

ALLOWED

Image Modified

Process

The table below provides a summary of the process to follow when adding a new relationship to an extension.

File TypeProcess
Stated
Relationship
AxiomA
new row representing a new relationship is added to the stated relationship file.

A new relationship identifier is allocated within the extension namespace.

The attributes of the new relationship are set as follows:

  • id is set to the new relationship identifier allocated within the extension namespace.
  • effectiveTime is set to the date the extension will be published
  • active is set to '1' to indicate that the new relationship will be active at the time of publication
  • moduleId is set to identify a module concept from the extension
  • sourceId is usually set to a concept from an extension module.
    • Concepts from other modules upon which the extension is dependent may be used if necessary to meet legitimate clinical needs or to correct identified clinical issues.
  • destinationId is set to a concept that represents the value of the relationship attribute
  • relationshipGroup is set to a number that indicates which relationships with the same sourceId are logically grouped together
  • typeId is set to an attribute concept that represents the type of the relationship
  • characteristicTypeId is usually set to 900000000000010007 |Stated relationship|
    • modifierId is usually set to 900000000000451002 |Existential restriction modifier|
    prerequisite for generating the relationships in the relationship file is that concepts have been authored and the defining properties stated and classified together with the SNOMED CT content it belongs to. Please see 5.4.2.1 Add Concept in an Extension.
    Relationship

    Once authoring is complete, the contents of the extension modules, together with every module on which these depend, are classified.

    The resulting set of inferred relationships (i.e. the output of the classification process) is added to the Relationship file.

    A new row is added to the Relationship file for every inferred relationship that results from the classification process.

    The attributes of the inferred relationships are set as follows:

    • id is set to a new relationship identifier allocated within the extension namespace.
    • effectiveTime is set to the date the extension will be published
    • active is set to '1' to indicate that the new relationship will be active at the time of publication
    • moduleId is set to identify a module concept from the extension
    • sourceId is set to the source concept in the relationship. This will usually belong to the extension module.
    • destinationId is set to the destination concept in the relationship
    • relationshipGroup is set to a number that indicates which relationships with the same sourceId are logically grouped together
    • typeId is set to an attribute concept that represents the type of the relationship
    • characteristicTypeId is usually set to 900000000000011006 |Inferred relationship|
    • modifierId is usually set to 900000000000451002 |Existential restriction modifier|