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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SctId<br />

999999990989121104<br />

2.3.2.9. The Namespace hierarchy<br />

Partition identifier<br />

10= Concept, using long<br />

format<br />

Check digit<br />

4<br />

Notes<br />

The maximum valid SctId<br />

for a Concept in the<br />

0989121 namespace.<br />

<strong>SNOMED</strong> CT core release files include metadata Concepts that represent each of the allocated<br />

namespace-identifiers.The Concepts representing the namespaces are arranged in a single parent hierarchy,<br />

as follows:<br />

• 370136006 | Namespace concept |<br />

• 373872000 | Core Namespace |<br />

• | Extension Namespace A {} |<br />

• | Extension Namespace B {} |<br />

• | Extension Namespace D {} |<br />

• | Extension Namespace E {} |<br />

• | Extension Namespace C {} |<br />

Figure 30: Hierarchy for: Namespace concept (namespace concept)<br />

In the above hierarchy,| Extension Namespace A {} |, | Extension Namespace B {} | and | Extension Namespace<br />

C {} | are all child namespaces of the 373872000 | Core Namespace | (representing the International edition<br />

which does not have a namespace-identifier, and uses short format SCTIDs to identify components). Also, |<br />

Extension Namespace B {} | is the parent namespace of | Extension Namespace D {} | and | Extension<br />

Namespace E {} | .<br />

Each Namespace concept may only have one parent Namespace concept in the 370136006 | Namespace<br />

concept | sub-hierarchy.<br />

The namespace hierarchy is used to constrain which content can be promoted from one Extension to another<br />

without amending the SCTID. Content may be moved (without amendment of SCTID) from an Extension<br />

released by the owner of a child namespace to an Extension released by the owner of a parent (or ancestor)<br />

namespace, as described by the |370136006 | Namespace concept | sub-hierarchy.<br />

Examples:<br />

1. A concept with an SCTID that includes | Extension Namespace D {} | may be moved to the Extension<br />

maintained by the owner of | Extension Namespace B {} | without changing its SCTID, because this<br />

is a parent of the originating namespace.<br />

2. A concept with an SCTID that includes | Extension Namespace D {} | must not be moved to the<br />

Extension maintained by the owner of | Extension Namespace C {} | because this is not parent (or<br />

ancestor) of the originating namespace. Therefore, to make this move the original concept must be<br />

inactivated and replaced by a new component with a new SCTID in target namespace.<br />

3. Any concept may be moved from any Extension to the International <strong>Release</strong> (subject only to formal<br />

acceptance that is a valid addition for international use).<br />

Namespace concepts have the following characteristics:<br />

Structure and Content <strong>Guide</strong> | 67<br />

• They are subtypes (either children or descendants) of 370136006 | Namespace concept |.<br />

• The Fully Specified Name of each Concept has the form “ Extension Namespace {nnnnnnn} (namespace<br />

concept)” – where nnnnnnn is the seven digit Namespace-Identifier.<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!