Inactivation Reason | Association Type | Description |
---|---|---|
Erroneous | REPLACED_BY | The inactivation reason “Erroneous Component” explicitly states that the inactivated concept (A) has an FSN which contains an error that when corrected potentially changes the semantic meaning of the concept and that in the judgment of the author/editor the true original meaning is now represented by the “REPLACED_BY” concept (B). Note: this inactivation reason should not be used to correct, punctuation, word order changes, or minor spelling mistakes that do not change the meaning of the FSN - these changes can be made by inactivation and replacement of the FSN. |
Guidance | ||
|
Examples
Inactivated concept:
REPLACED_BY association:
Although superficially some typographical errors can appear insignificant it is safer to inactivate and replace as the spelling differences between organism names can be small
Inactivated concept:
REPLACED_BY association:
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 REPLACED_BY 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) REPLACED_BY (B) and (B) SAME_AS (C) implies (A) REPLACED_BY (C) (A) REPLACED_BY (B) and (B) REPLACED_BY (C) implies (A) REPLACED_BY (C) (AIntEd) REPLACED_BY (BIntEd) and (BIntEd) MOVED_TO (CNRC) implies (AIntEd) MOVED_TO (CNRC) (A) REPLACED_BY (B) and (B) POSSIBLY_EQUIVALENT_TO (C, D) implies (A) POSSIBLY_EQUIVALENT_TO (C, D) (A) REPLACED_BY (B) and (B) WAS_A (C AND D) implies (A) WAS_A (C AND D) |
Note: Once MOVED_TO the NRC, SNOMED International have no knowledge of what has happened to BIntEd