SNOMED CT® Release Format 1 (RF1) Guide - ihtsdo

126 | SNOMED CT Release Format 1 (RF1) Guide July 2012
c. Status value of the component (usually one of the non-current status values).
.
2. If the component is a Concept or Description, a row in the appropriate distribution table for the component
with its updated Status (usually one of the non-current status values).
Components other than Concepts and Descriptions are only distributed when they are "current". Therefore,
there is no status field in the distributed Relationships, Subsets, Cross Map Sets or Cross Map Targets Tables.
Note that the Relationships table contains Relationship Types that describe Relationships between inactive
and active Concepts.
Inactive Concepts and Descriptions are included in the distributed tables to support data recorded when these
components were active. Therefore, the status of these components is represented explicitly in the
ConceptStatus and DescriptionStatus fields of the distributed tables. The reason for inactivation of a Concept
or Description may vary and is represented by a range of status values.
3.2.7.2.3. Making minor changes to Component
Most changes to a component require it to be inactivated and replaced by a new component with a new
SNOMED CT identifier. However, a specified set of minor changes is permitted without inactivating the
component.
A minor change to a component is distributed as:
1. A row in the Component History Table with:
a. ChangeType value Minor Change;
b. ComponentIdreferring to the changed component;
c. Status value for the component (usually Current).
.
2. A row in the appropriate distribution table for the changed component.
Minor changes to components are tabulated below:
Table 47: Permitted minor changes to components
Table
Concepts
Descriptions
Field
FullySpecifiedName
Term
Permitted minor changes
Changes in presentation such as changed
capitalization, punctuation, spelling or revision due to
changes in agreed presentation style are permitted,
without retiring the ConceptId, as long as the minor
changes in FSN do not change the specified meaning
of the Concept. Some changes to the semantic type
shown in parentheses at the end of the
FullySpecifiedName may also be considered minor
changes if the change in hierarchy does not alter the
Concept's meaning. NOTE: This rule indicates that
the ConceptId does not need to be retired in cases
where the FSN undergoes minor changes. See below
regarding required changes in DescriptionId.
If DescriptionType is FullySpecifiedName then no
changes are allowed; any change to any character of
the FSN Term string requires a new DescriptionId.
(NOTE: this is a new policy as of October 2011).
© 2002-2012 International Health Terminology Standards Development Organisation CVR #: 30363434