SAME_AS - Editorial Guide

Current usage:

The purpose of this association type is to indicate that the inactivated concept is semantically equivalent to the SAME_AS target concept. This association type is used with the inactivation reason of "Duplicate component".

This does not imply that the wording of the FSN must be the same for each concept but that the meaning implied by the word string is the same.

While the emphasis on establishing the meaning of the concept is currently based upon the FSN as we move towards completion of the QI work on consistency in modeling we would expect the modeling to accurately reflect the FSN. Where this is not the case and where there is significant difference between the meanings implied by the FSN and logical model, analysis of the siblings, super and sub types may be necessary to confirm the implied meaning of the concept. If after analysis it is confirmed that there is ambiguity between the FSN and its placement within the hierarchy the inactivation reason should be changed to "Ambiguous".

Proposed changes:

There are no proposed changes to the use of this association type.

Combinatorial Logic:

Whenever an already stated SAME_AS target itself also becomes inactive - whether at the same release or later - the combinatorial logic of associations should be:

(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)

(A^IntEd) SAME_AS (B^IntEd) and (B^IntEd) MOVED_TO (C^NRC) implies (A^IntEd) MOVED_TO (C^NRC)

(A) SAME_AS (B) and (C) MOVED_FROM (B) implies (C) MOVED_FROM (A) - work in progress

(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)