Extensions Practical Guide

Search

SNOMED CT Document Library

    Loading...

Page tree

Versions Compared

Old Version 5

changes.mady.by.user David Markwell

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.

...

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

Relationship or RelationshipA respective
File TypeProcess
Stated Axiom

Modifying a concept definition involves updating the defining properties of the concept, i.e. making changes to the axioms that represent necessary conditions for the meaning of the concept. 

Once the update has been performed, the concept is classified together with the SNOMED CT content it belongs to, and a new set of relationships are inferred.

To prepare for publication, a new row representing the updated concept definition is added to the OWL axiom reference set.

The attributes of the reference set member representing the stated axiom are set as follows:

  • id is set to the UUID of the reference set member representing the definition of the concept being updated.
  • 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
  • referencedComponentId  is set to the identifier of the concept being updated 
  • owlExpression is set to the text of the OWL expression representing the updated defining properties of the new concept
Relationship



Depending on the nature of the change made, updates to the inferred relationship file will be made to reflect the changes.
This may involve:

  • Inactivating relationships that are no longer valid for the concept
  • Adding new relationships that represent new defining relationships
  • Updating existing relationships, when the change made only impacts mutable attributes for existing relationships, see above
    • in this case, a new row which represents a new version of the modified relationship is added to the
    • relationship file.

The attributes of the new version of the relationship are set as follows:

  • id is set to the relationshipId of the relationship being modified
  • effectiveTime is set to the date the extension will be published
  • active is set to '1' to indicate that the new version of the 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 same as the original version of the relationship
  • destinationId is set to the same as the original version of the relationship
  • relationshipGroup is set to the updated relationship group number (or the original number if no update is required)
  • typeId is set to the same as the original version of the relationship
  • characteristicTypeId is set to the updated value (or the original value if no update is required)
  • modifierId is set to the updated value (or the original value if no update is required)