Inactivation Reason | Association | Definition |
---|---|---|
Non-Conformance to Editorial Policy | REPLACED_BY ALTERNATIVE No suitable replacement identified | The inactivation reason “Non-conformance to Editorial Policy” explicitly states that the inactivated concept does not comply with a specific Editorial Guideline valid at the point of inactivation. From time to time editorial policy may change, either to revise what is considered to be within scope for the International Edition of SNOMED CT, or to support changes in modeling practice and thereby bring greater consistency to existing content. In the latter scenario, the necessary refactoring or remodeling of content can change the meaning of existing SNOMED CT concept FSN’s or the implied meaning of their logical definitions. |
Guidance | ||
|
Examples:
Non-Conformance to Editorial Policy - content out of scope for SNOMED CT:
ALTERNATIVE:
- No alternative provided
Annotation:
- Briefing note for MF January 2021, Device Hierarchy - Editorial Guidelines for Modeling and Terming v1.0.pdf
Non-Conformance to Editorial Policy:
Update of FSN to comply with Editorial Guidance: The use of "and" which has the implied meaning of "and/or"
Editorial guidance on conjunction and disjunction states that the use of "and" in structural groupers has an implied meaning of "and/or" and therefore the FSN is to be updated to make the inclusive disjunction implicit with the use of "and/or". While this technically represents a change in meaning, as this is both a structural grouper and with the agreement of the community of practice, change of the FSN alone is supported.
Inactivate the FSN as "Non-conformance to Editorial Policy":
- Replace the FSN with: Iron and/or iron compound (substance)
Annotation:
- Briefing note for MF June 2021, Link to Editorial Guidance - Conjunction and Disjunction
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.
(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)
Whenever an already stated ALTERNATIVE 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.
(A) ALTERNATIVE (B) and (B) SAME_AS (C) implies (A) ALTERNATIVE (C)
(A) ALTERNATIVE (B) and (B) REPLACED_BY (C) implies (A) REPLACED_BY (C)
(AIntEd) ALTERNATIVE (BIntEd) and (BIntEd) MOVED_TO (CNRC) implies (AIntEd) MOVED_TO (CNRC)
(A) ALTERNATIVE (B) and (B) POSSIBLY_EQUIVALENT_TO (C, D) implies (A) ALTERNATIVE (C, D)
(A) ALTERNATIVE (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