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.

2.1.2.2.1.3. Linking related Concepts of different types<br />

Navigational links can also be used to provide access to connected Concepts even when they are from<br />

different hierarchy branches.<br />

Example:<br />

A navigation links could associate:<br />

• "hypertension" (the disorder) with | blood pressure | (the observation);<br />

• | cataract | (disorder / finding) with "cataract surgery" (the procedure).<br />

2.1.2.2.1.4. Ordering the display of subtypes<br />

Sibling Concepts in a subtype hierarchy are not ordered. However, at the user interface a particular order<br />

may be useful to highlight commonly used Concepts or to mirror a conventional ordering.<br />

Example:<br />

Vertebrae, cranial nerves, disease stages, etc.<br />

Navigational links are ordered and are used to impose order, even when the set of navigational children is<br />

the same as the set of subtype children.<br />

2.1.2.2.1.5. Providing alternative hierarchies<br />

The subtype hierarchy is logically defined and there can only be one such hierarchy. However, as navigation<br />

hierarchies have no definitional consequences, it is possible to have different hierarchies for different groups<br />

of users with differing needs.<br />

Initial releases of <strong>SNOMED</strong> CT will contain a single set of navigation links but those engaged in technical<br />

implementation should be aware that in the future there may be separate sets of navigation links for use in<br />

different environments.<br />

2.1.2.3. Cross Maps<br />

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

<strong>SNOMED</strong> CT specifications and content include resources that support cross mapping to and from other<br />

code systems, classifications and terminologies. These resources support simple mapping, where there is a<br />

one-to-one Relationship between a <strong>SNOMED</strong> CT concept and code in a target scheme, and more complex<br />

maps where these are required.<br />

More complex mapping requirements supported by the <strong>SNOMED</strong> CT cross mapping model include:<br />

• Maps from a single <strong>SNOMED</strong> CT concept to a combination of codes (rather than a single code) in the<br />

target scheme.<br />

• Maps from a single <strong>SNOMED</strong> CT concept to choice of codes in the target scheme. In this case, the<br />

resolution of the choices may involve:<br />

• Manual selection supported by advisory notes.<br />

• Automated selection based on rules that test other relevant characteristics in the source data (e.g. age<br />

and sex of the subject, presence or absence of co-existing conditions, etc).<br />

• A combination of automated processing with manual confirmation or selection where rules are insufficient<br />

to make the necessary decisions.<br />

Note: In <strong>Release</strong> <strong>Format</strong> 1 cross maps are represented using three tables. These tables contains rows<br />

that represent the following types of information:<br />

• Cross Map Set: metadata about a set of maps from <strong>SNOMED</strong> CT to a target scheme;<br />

• Cross Map: a map from a concept to a representation of the concept in the target scheme;<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!