SNOMED Documentation Search


 Other Documents

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The permitted reassignments of responsibility are limited to ensure that the organization responsible for maintaining a

Glossary ref
component
can be determined. Thus the end result of any transfer of responsibility must result in the
Glossary ref
component
being maintained by one of the organization responsible for one of the following:
Anchor
_e5dc0735-3b98-4b11-af98-51e46e16a825__b
_e5dc0735-3b98-4b11-af98-51e46e16a825__b

  • the
    Glossary ref
    Extension
    namespace specified by the
    Glossary ref
    namespace-identifier
    of its
    Glossary ref
    Identifier
    ;
  • an
    Glossary ref
    Extension
    with a
    Glossary ref
    namespace-identifier
    that is a hierarchical ancestor of the
    Glossary ref
    namespace-identifier
    of the originating
    Glossary ref
    Extension
    ;
  • the
    Glossary ref
    International Release
    .

The values of the of the

Glossary ref
partition-identifier
which previously indicated that a
Glossary ref
component
was part of an
Glossary ref
Extension
, continue to indicate that the
Glossary ref
SCTID
contains a
Glossary ref
namespace-identifier
. However, some
Glossary ref
components
with a
Glossary ref
namespace-identifier
may now be maintained as part of the
Glossary ref
International Release
. Therefore, for clarity, the definition of
Glossary ref
partition-identifier
has been revised to indicate that the values determine whether the SCTID (data type) conforms to the long format (with a
Glossary ref
namespace-identifier
) or the short format (without a
Glossary ref
namespace-identifier
). Only the
Glossary ref
IHTSDO
can issue short formatSCTID (data type) (without a namespace), whereas an
Glossary ref
Extension
owner must issue a long formatSCTID (data type) (including a
Glossary ref
namespace-identifier
that is registered as belonging to them).

The moduleId (field) field, introduced in

Glossary ref
Release Format 2
and held against each
Glossary ref
component
, records the organization currently responsible for maintaining the
Glossary ref
component
. The moduleId (field) must refer to a module delivered by the organization maintaining the
Glossary ref
component
and the
Glossary ref
namespace-identifier
of this moduleId (field) must belong to the maintaining organization .

Following the change, migration of

Glossary ref
components
between
Glossary ref
Extensions
would be possible without a change to their SCTID (data type) , according to the following rules:

  • A
    Glossary ref
    component
    can be moved from any
    Glossary ref
    Extension
    to the
    Glossary ref
    International Release
    without a change to its SCTID (data type) .
  • A
    Glossary ref
    component
    can be moved from an
    Glossary ref
    Extension
    to a parent or ancestor
    Glossary ref
    Extension
    without a change to its SCTID (data type) .
  • A
    Glossary ref
    component
    can be moved from the
    Glossary ref
    International Release
    back to its originating
    Glossary ref
    Extension
    without a change to its SCTID (data type) .

In all other cases, the existing rules for moving

Glossary ref
components
between
Glossary ref
Extensions
should be used. These require a change of SCTID (data type) to occur with tracking of inactivation in the appropriate 4.2.2 Component Inactivation Reference Sets and cross-references created in the appropriate 4.2.3 Historical Association Reference Sets (or as historical relationships in
Glossary ref
Release Format 1
).

CAUTION:

Glossary ref
Components
that originated in the
Glossary ref
International Release
must not be moved to any
Glossary ref
Extension
without a change to the SCTID (data type) .

In order to make explicit which

Glossary ref
Extensions
are parents of which other
Glossary ref
Extensions
,
Glossary ref
concepts
under the
Glossary ref
Namespace Concept
may now be rearranged as a nested hierarchy of namespaces. All namespaces at the top level of this hierarchy are considered to have as their parent the
Glossary ref
International release
. The
Glossary ref
Namespace Concept
for an
Glossary ref
Extension
that is dependent on another
Glossary ref
Extension
may be nested as a child (sub-type) of the
Glossary ref
Namespace Concept
for the
Glossary ref
Extension
on which it depends.

CAUTION:

Glossary ref
Components
that originated in an
Glossary ref
Extension
must not be moved to any other
Glossary ref
Extension
unless the
Glossary ref
Namespace Concept
associated with the target
Glossary ref
Extension
is an ancestor of
Glossary ref
Namespace Concept
associated with source
Glossary ref
Extension
. The ancestry of
Glossary ref
Namespace Concepts
is determined by the
Glossary ref
subtype hierarchy
distributed as part of the
Glossary ref
International Release
. Other moves between
Glossary ref
Extensions
require a change of SCTID (data type) .

Guidance has been developed for producers and consumers of SCTID (data type), to help avoid conflicts of ownership and to facilitate identification of owning organizations (see 2.6 Guidance for Producers of SNOMED CT Extensions and 2.5 and Guidance for Consumers of SNOMED CT Extensions ).