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.

74 | <strong>SNOMED</strong> CT <strong>Release</strong> <strong>Format</strong> 1 (<strong>RF1</strong>) <strong>Guide</strong> July 2012<br />

•<br />

This occurs if a decision is made that some Concepts in the International <strong>Release</strong> are specific to a<br />

Realm or domain or interest for which another organization has been allocated responsibility:<br />

•<br />

For example, this applies to UK specific drugs and UK specific administrative Concepts which are<br />

maintained by the UK NHS.<br />

• From an organization responsible for an Extension to the International <strong>Release</strong>:<br />

• This occurs if an organization recognizes that some of its Extension content belongs in the International<br />

<strong>Release</strong> as it has general applicability;<br />

• It also occurs if an organization hands over responsibility for its entire Extension to the IHTSDO.<br />

• From one organization responsible for an Extension to another organization :<br />

• This occurs if one organization recognizes that some of its Extension content belongs in a domain<br />

managed by another organization ;<br />

• It also occurs if an organization hands over responsibility for its entire Extension to another organization<br />

.<br />

There are three types of transfer of responsibility:<br />

• Transfer of an entire Extension (i.e. all components ever issued with an SCTID in a given Namespace.<br />

from one organization to another organization ):<br />

• This is a straight forward process. All that happens is that another organization assumes responsibility<br />

for the original Namespace-identifier. There is no need for detailed tracking of individual components.<br />

• Transfer of one or more components from an Extension to the International <strong>Release</strong> or to a<br />

"parent"Extension:<br />

• As a result of revision to guidance issued by the IHTSDO in 2011, these transfers can be made without<br />

changing the Identifier of the component provided that the RF2 format moduleId field is used to denote<br />

that the component is now being issued as part of a different module.<br />

• Transfer of one or more components between other Extensions or from the International <strong>Release</strong> to any<br />

Extension:<br />

• In this case, the Namespace is not transferred and thus, to fulfill the roles of the Namespace-Identifier,<br />

the component must be assigned new SCTIDs in the Namespace of the newly responsible organization<br />

:<br />

• The previous instances of these components are withdrawn from current use with the Status value<br />

Moved Elsewhere;<br />

• Appropriate Relationships point to replacement components in the new Namespace.<br />

The transfer of responsibility depends on the release schedules of the organizations involved. Often the<br />

original source organization will be aware of an intended move before the target organization has accepted<br />

responsibility and released the component. To facilitate this, an interim Status value Pending Move is applied<br />

to components that are being moved to another Namespace but are intended for active use until their<br />

replacements are found in the target Namespace.<br />

To provide continuity for a Concept if responsibility is transferred, the Concept Status and history are<br />

coordinated as follows:<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!