SNOMED CT Editorial Advisory Group

Page tree

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

Compare with Current View Page History

« Previous Version 35 Next »

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


Equivalent 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 should be based on keeping the concept that has the most compliant FSN, complete and correct modeling, and/or synonyms. 

Examples

Semantic meaning the same but FSN different

Duplicate concepts:

Resolution

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.

Identical FSN but different semantic tag

Duplicate concepts:

Resolution

Managing Incoming Historical Associations

The intention is that this functionality will be seamlessly integrated into the tooling so as to present to the user the appropriate updated historically association to be allocated.

Whenever an already stated “SAME_AS” target itself also becomes inactive - whether at the same release or later, identifying the replacement for the original concept, should follow the combinatorial logic stated below.

Combinatorial Logic

(A) SAME_AS (B) and (B) SAME_AS (C) implies (A) SAME_AS (C)

(A) SAME_AS (B) and (B) REPLACED_BY (C) implies (A) REPLACED_BY (C)

(AIntEd) SAME_AS (BIntEd) and (BIntEd) MOVED_TO (CNRC) implies (AIntEd) MOVED_TO (CNRC)

(A) SAME_AS (B) and (B) POSSIBLY_EQUIVALENT_TO (C OR D) implies (A) POSSIBLY_EQUIVALENT_TO (C OR D)

(A) SAME_AS (B) and (B) WAS_A (C AND D) implies (A) WAS_A (C AND D)

Note: Once MOVED_TO the NRC we (SNOMED International) have no knowledge of what has happened to BIntEd

  • No labels