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.

• One Subset can be used as the basis for another Subset. The defining clauses express differences<br />

between the base Subset and the defined Subset.<br />

Example:<br />

A UK English dialect Subset may be expressed as differences from an International English language<br />

Subset.<br />

• Members can be added to a Subset according to hierarchical Relationships.<br />

Example:<br />

A single defining clause can add all | is a | descendants of the Concept "Musculoskeletal procedure" to<br />

an orthopedic specialist Subset.<br />

Software developers who wish to use subset definition files will need to produce software that will generate<br />

relational subset tables from a subset definition. Please contact the IHTSDO for current information as this<br />

format evolves.<br />

4.4.3.4. Using relational Subset tables<br />

Any Subset Definition can be automatically converted into the relational form. However, the relational form<br />

is release version dependent whereas some Subset Definitions may be applicable to more than one release<br />

of <strong>SNOMED</strong> CT.<br />

An application may use the relational form of a Subset in one of three ways:<br />

1. As part of a run - time query to retrieve, filter or sort members of a Subset.<br />

Example:<br />

An SQL query with a join between the Subsets Table and a core table could be used to:<br />

• Provide a pick list of all members of a Subset;<br />

• Filter a search or hierarchical list so that only members of the Subset are shown;<br />

• Order a search or hierarchical list according to the sequence specified in the Subset.<br />

2. To pre-filter a <strong>SNOMED</strong> CT table when it is imported from a release file.<br />

Example:<br />

You might choose to exclude Descriptions in a language or dialect not required.<br />

Terminology services <strong>Guide</strong> (<strong>RF1</strong>) | 335<br />

• Care should be taken when considering the use of pre-filtering with Concepts. If <strong>SNOMED</strong> CT<br />

data from other systems is received it will not be possible to interpret it unless the relevant Concepts<br />

(including Concepts used directly or indirectly in a definition) are present on the system.<br />

3. To modify the application's internal representation of Concepts or Descriptions to allow efficient application<br />

of the Subset.<br />

• Possible modifications include addition of flags or indexes or some type of pre-sorting of data.<br />

• Objectives of this include:<br />

• Optimizing frequently used Subsets<br />

• Facilitating rapid switching between different Subsets depending on context or user configuration.<br />

Note: The release file formats are tab-delimited files that allow the information to be imported to any<br />

relational database management system.<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!