09.04.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

In addition, the ReferencedId field may also refer to a Concept when ComponentId refers to an inactive<br />

Description and ReferenceType = 7 (Refers to Concept).This use of the References Table permits a Description<br />

to be made inactive without having to retire its Concept. In such a case, the References Table indicates a<br />

Concept which is correctly described by the Term of the inactive Description.<br />

3.2.7.1.4. Historical relationships<br />

Historical relationships link Inactive Concepts to the overall semantic structure of <strong>SNOMED</strong> CT. These<br />

specialized Relationships should be used to map legacy data into the current subtype hierarchy of <strong>SNOMED</strong><br />

CT :<br />

• An "erroneous" Concept is related to the corrected Concept that replaces it by a | REPLACED BY<br />

|Relationship.<br />

• A "duplicate" Concept is related to the Concept that it was found to duplicate by a | SAME AS |Relationship.<br />

• An "ambiguous" Concept is related to the Concept (s) that represent its possible disambiguated meanings<br />

by one or more | MAY BE A | Relationships.<br />

• A Concept that has the status "Moved Elsewhere" or "Pending Move" is related to a Namespace Concept<br />

by a | MOVED TO |Relationship. This identifies the namespace to which the Concept has been moved<br />

or will be moved.<br />

• A Concept that replaces a Concept moved from another namespace has a | MOVED FROM |Relationship<br />

referring to the original Concept in its original namespace:<br />

• If the Extension from which a Concept originated is not installed the target Concept will not be available.<br />

This is not an error and can be safely ignored. The information in the Relationship is only of interest<br />

to users of the original Concept.<br />

• If the Concept has been moved to the <strong>SNOMED</strong> CT core namespace the | MOVED FROM |Relationship<br />

should be maintained in the originating Extension.<br />

3.2.7.2. Component History Rules<br />

These are the rules used to create the Component History Table when components are added or changed.<br />

components are never removed, but their status may change from active to inactive. Components that have<br />

become inactive may sometimes subsequently have their status restored to active.<br />

Special considerations for the <strong>SNOMED</strong> CT First <strong>Release</strong> are described in the last subsection.<br />

3.2.7.2.1. Adding a Component<br />

A newly added component is distributed as:<br />

1. A row in the Component History Table with:<br />

a. ChangeType value Added;<br />

b. ComponentIdreferring to the new component;<br />

c. Status value for the component (usually Current).<br />

.<br />

2. A row in the appropriate distribution table for the new component.<br />

3.2.7.2.2. Changing the status of a Component<br />

All <strong>SNOMED</strong> CT Components have an active or inactive Status.<br />

When the Status of a component is changed, this is distributed as:<br />

1. A row in the Component History Table with:<br />

a. ChangeType value Status Change;<br />

b. ComponentId referring to the changed component;<br />

<strong>Release</strong> File <strong>Format</strong>s | 125<br />

© 2002-2012 International Health Terminology Standards Development Organisation CVR #: 30363434

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!