...
Whenever an already stated POSSIBLY_EQUIVALENT_TO target itself also becomes inactive - whether at the same release or later - the combinatorial logic of associations should be:, identifying the replacement for the original concept, should follow the combinatorial logic stated below.
| Code Block | ||||
|---|---|---|---|---|
| ||||
(A) POSSIBLY_EQUIVALENT_TO (B OR C) and (B) SAME_AS (D) implies A POSSIBLY_EQUIVALENT_TO (C OR D) |
...
(A) POSSIBLY_EQUIVALENT_TO (B OR C) and (B) REPLACED_BY (D) implies (A) POSSIBLY_EQUIVALENT_TO (C OR D) |
...
(AIntEd) POSSIBLY_EQUIVALENT_TO (BIntEd OR CIntEd) and (BIntEd) MOVED_TO (DNRC) implies (AIntEd) POSSIBLY_EQUIVALENT_TO (CIntEd) |
...
(A) POSSIBLY_EQUIVALENT_TO (B OR C) and (B) POSSIBLY_EQUIVALENT_TO (D OR E) implies A POSSIBLY_EQUIVALENT_TO (C OR D OR E) |
...
(A) POSSIBLY_EQUIVALENT_TO (B OR C) and (B) WAS_A (D AND E) implies ((A) POSSIBLY_EQUIVALENT_TO (C) OR (A) WAS_A (D AND E)) |
Note: Once MOVED_TO the NRC we (SNOMED International) have no knowledge of what has happened to BIntEd