Page History

...

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

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

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

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

TNote: Once MOVED_TO the NRC we (SNOMED International) have no knowledge of what has happened to B^IntEd

...