SNOMED CT Editorial Advisory Group

Page tree

Versions Compared

Old Version 34

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

Saved on

compared with

New Version 35

changes.mady.by.user Paul Amos

Saved on

Key

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

...

Inactivation ReasonAssociationDefinition

Duplicate 

SAME_AS

This combination of inactivation reason and association type explicitly states that the inactivated concept (A) semantically represents exactly the meaning of the remaining active concept (B). Implicitly it also means that (A) SAME_AS (B) always, by definition implies (B) SAME_AS (A).

The definition includes the requirement to ensure any analysis expressed in terms of (A) returns the same subtypes as would have been present had the concept (B) been substituted into the query logic, and vice versa.

Please note that the meaning of the concept is based on the FSN.

Guidance
  • Inactivate non-synonymous synonyms
    If any of the concept’s synonyms are considered to be non-synonymous, these should first be inactivated and re-assigned to either the concept that matches the meaning or if not available a new concept created.
  • Specify target concept
    The target component identifies the active concept that this concept duplicates.
    Note: Where possible consider keeping the concept with the oldest effective date as this is likely to have had the most usage.
  • Annotation
    Provide evidence/reference to support the concepts are duplicates


Panel
borderColor#E6E9EE
titleColor#124F6B
titleBGColor#E6E9EE
titleEquivalent FSNs but different semantic tags

If the pair of semantic tags are within the following permitted pairs then an inactivation reason of "Duplicate" may still be used:

  • Disorder and Finding
  • Procedure and Regime/Therapy
  • Finding and Situation
  • Procedure and Situation
  • Procedure and Observable 
  • Additional notes:
    • The requirement to ensure any analysis expressed in terms of (A) returns the same result as it would if the same logic was applied to (B) is contingent on both concepts being modeled correctly.
    • The choice of which concept should be inactivated may not always be straightforward. To reduce the impact on users/vendors, consider keeping the concept with the oldest effective date as this is likely to have had the most usage. Where the existing FSN for the older concept does not comply with current naming conventions, it may be possible to assign a newer and compliant FSN "in its place" i.e., without inactivating the concept. However, if the newer concept already carries the ideal, compliant FSN then it will not be possible to also assign that same FSN to the older concept, and so there may be no other option than to inactivate the older concept in favor of the newer, with its better FSN.should be based on keeping the concept that has the most compliant FSN, complete and correct modeling, and/or synonyms. 

Examples

Panel
titleSemantic meaning the same but FSN different

Duplicate concepts:

  • Concept
    t235998001 | Perinephric abscess (disorder) |
  • Concept
    t80640009 |Perirenal abscess (disorder)|

Resolution

  • The concept 
    Concept
    t235998001 | Perinephric abscess (disorder) |
         is inactivated with an inactivation reason of 'Duplicate', and a SAME_AS association to:
    • Concept
      t80640009 |Perirenal abscess (disorder)|

Note: Both concepts had an effective date of 2002-01-31 and so the decision was based on current clinical usage and the retained concept already had a synonym of Perinephric abscess.

...