Release File Specification

Search

SNOMED CT Document Library

    Loading...

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The Relationship file holds oneper row. Eachis of a particular type, and has a sourceand a destinationAn example of ais given below: |Outpatient procedure| |Is a| |Procedure| where:

Field

Data type

Immutable

Purpose

Part of Primary Key

id

SCTID

Y

Uniquely identifies the

YES (Full/ Snapshot) 

effectiveTime

Time

N

Specifies the inclusive date at which the component version's state became the then current valid state of the component

YES (Full)

Optional (Snapshot) 

active

Boolean

N

Specifies whether the state of thewasorfrom the nominal release date specified by the effectiveTime field.

NO

moduleId

SCTID

N

Identifies theversion's module. Set to aof |Module| within the metadata

NO

sourceId

SCTID

Y

Identifies the sourceof theversion. That is thedefined by thisSet to theof ain the Concept File.

NO

destinationId

SCTID

Y

Identifies thethat is the destination of theversion.

That is therepresenting the value of the attribute represented by the typeId column.

Set to theof ain the Concept File.

Note that the values that can be applied to particular attributes are formally defined by the   SNOMED CT Machine Readable Concept Model .

NO

relationshipGroup

Integer

N

Groups togetherversions that are part of a logically associated relationshipGroup. Allrecords with the same relationshipGroup number and sourceId are grouped in this way.

NO

typeId

SCTID

Y

Identifies thethat represent the defining attribute (or relationship type) represented by thisversion.

That is therepresenting the value of the attribute represented by the typeId column.

Set to theof ain the Concept File. The concept identified must be either |Is a| or a subtype of 410662002 |Concept model attribute| . The concepts that can be used as in the typeId column are formally defined as follows:

Note that the attributes that can be applied to particular concepts are formally defined by the SNOMED CT Machine Readable Concept Model.

NO

characteristicTypeId

SCTID

N

Aenumeration value that identifies the characteristic type of theversion (i.e. whether theversion is defining, qualifying, etc.) This field is set to aof |Characteristic type| in the metadata.

NO

modifierId

SCTID

N

Aenumeration value that identifies the type of(DL) restriction (some, all, etc.). Set to aof |Modifier| in the metadata

Currently the only value used in this column is |Some| and thus in practical terms this column can be ignored. For further clarification please see notes on modifierId .

NO

 

Only onerecord with the same id field will be current at any point in time. The current record will be the one with the most recent effectiveTime before or equal to the point in time under consideration.
If thefield of this record is false ('0'), then theisat that point in time. If thefield is true ('1'), then there is abetween theidentified by sourceId and destinationId .
The sourceId, destinationId, relationshipGroup, typeId, characteristicTypeIdand modifierId will not change between two rows with the same id, in other words they are immutable. Where a change is required to one of these fields, then the current row will be de-activated (by appending a row with the same id and thefield set to false) and a new row with a new id will be appended.
The relationshipGroup field is used to groupwith the same sourceId field into one or more logical sets. Awith a relationshipGroup field value of '0' is considered not to be grouped. Allwith the same sourceId and non-zero relationshipGroup are considered to be logically grouped.
The relationshipGroup field will be an unsigned Integer, and will not be limited to a single digit value. There is no guarantee that they will be assigned sequentially, and the values will not be unique across

Related Links

Feedback