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.

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

There are some underlying subtleties to this table however.<br />

The LinkedID field is only valid for:<br />

• Navigation Subsets, where it specifies the navigational children of the subset member;<br />

• Duplicate Terms Subsets, where it refers to the Description which is most highly prioritized.<br />

The field MemberStatus has a different significance depending on the type of subset specified in the Subset<br />

Table.<br />

A brief description of the significance of the MemberStatus in each type of subset is given below.<br />

4.4.3.2.1. Significance of MemberStatus in a Language or Realm Description Subset<br />

The MemberStatus specifies the role of the reference Description in this Language or Realm.There are three<br />

roles.<br />

1 = Preferred Term<br />

2 = Synonym<br />

3 = Fully Specified Name<br />

Note that the following rules apply to each Subset:<br />

• A Description cannot be assigned the role Fully Specified Name unless its DescriptionType is also "Fully<br />

Specified Name.";<br />

• Only one Description of each Concept may be assigned as the Fully Specified Name;<br />

• If no Description of a Concept is assigned the role Fully Specified Name, the FullySpecifiedName in the<br />

Concepts Table assumes this role;<br />

• A Description cannot be assigned the role Preferred Term or Synonym if its DescriptionType is "Fully<br />

Specified Name.";<br />

• One and only one Description of each Concept must be assigned the role "Preferred Term.";<br />

• Any number of Descriptions of a Concept may be assigned the role "Synonym.".<br />

4.4.3.2.2. Significance of MemberStatus in a Realm Concept or Context Concept Subset<br />

The MemberStatusspecifies the priority of the Concept within the Subset, with lower numbers denoting higher<br />

priority. The priority may be used to determine order of display. Concepts with priority status of "0" would<br />

appear at the top of the list.<br />

4.4.3.2.3. Significance of a MemberStatus in a navigational Subset<br />

The MemberStatus specifies the order of the child concepts within the navigational hierarchy. This may be<br />

used to determine the display order of children when displaying a navigational Subset.<br />

4.4.3.2.4. Significance of MemberStatus in a Realm Relationship (for future use) or Context Description<br />

Subset<br />

The MemberStatus has no particular significance in these types of subsets, and will be set to the value of<br />

"1,"meaning include this table row in the subset.<br />

4.4.3.3. Using subset definition files (future use)<br />

Subset definition files are the preferred way of specifying the content of subsets. The subset definition file is<br />

a series of logical clauses, expressed as XML mark-up, which defines what should be included in the subset.<br />

While all subsets released by the IHTSDO are currently distributed in the relational file format, there are plans<br />

to provide these subsets as XML definition files. This method of specifying subsets has several advantages:<br />

• It is less verbose as many members can be included by a single clause.<br />

• It is likely to be resilient to the effects of applying updates and Extensions.<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!