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.

3.2.9.3. relationships tables<br />

Each row in the Relationships Table represents a Relationship between two Concepts.<br />

Note: Most Relationship Types are directional and are therefore regarded as having source concept<br />

and a target concept. Reciprocal relationships are not explicitly represented by rows in the Relationships<br />

Table.<br />

Example: If B is a subtype of A, it follows that A is a supertype of B. The first of these Relationships is<br />

represented by a row in the relationships tables.The reciprocal Relationship is implied and is not restated<br />

by another row in the table<br />

Note:<br />

The Relationship Types supported include the | is a | (subtype) relationship. This is a hierarchical<br />

relationship and only the closest relationships are represented explicitly. Other relationships are subsumed<br />

and are not represented by rows in the Relationships Table.<br />

Example: If C is a subtype of B and B is a subtype of A, it follows that C is a subtype of A. The<br />

Relationship between C and A is not represented by a row in the relationships tables but is subsumed<br />

by the chain of Relationships between C and B and B and A.<br />

Relationships other than | is a | (subtype) relationship are called attribute relationships. These relationships<br />

include the concept (object), relationship type (attribute), and attribute value (another concept). This is<br />

sometimes called the OAV triplet, which stands for Object-Attribute-Value.<br />

Some sets of relationships may have an expected or logical display order (e.g. cranial nerves or cervical<br />

vertebrae). The order is described using the subset mechanism and is not part of the Relationships Table.<br />

In 2003-2004, some relationships were packaged into a separate file called the Historical RelationshipsTable.<br />

These relationships were merged into the Relationships Table starting with the January 2005 release.<br />

To recreate these two tables, use these SQL commands:<br />

Create table historical_relationships as<br />

Select * from relationships<br />

Where characteristic type = "2';<br />

Delete from relationships<br />

Where characteristic type = "2';<br />

Note:<br />

The type of relationship is itself described using a concept.<br />

3.2.9.3.1. Key Fields<br />

Table 81: -<br />

Relationships Table<br />

Key Fields<br />

RelationshipId<br />

Field Type<br />

SCTID<br />

Permitted characters<br />

Digits 0 to 9 only<br />

<strong>Release</strong> File <strong>Format</strong>s | 149<br />

Length<br />

6 to 18<br />

The unique <strong>SNOMED</strong> CT Identifier for this relationship. See Component features - Identifiers (2.1.1.4.2) for<br />

an explanation of the SCTID data type format.<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!