Search



  

The Concept File holds the clinical concepts that make up SNOMED CT. A concept is given meaning by its Fully Specified Name, which is held in the Description. A concept may be distinguished from or refined by association with other concepts using relationships, which are held in the Relationship.

Table 4.2.1-1: Concept file - Detailed Specification

Field

Data type

Purpose

Part of Primary Key

id

Uniquely identifies the concept.

NO

YES
(Full/Snapshot) 

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

Note: In distribution files the effectiveTime should follow the short ISO date format (YYYYMMDD) and should not include the hours, minutes, seconds or timezone indicator.

YES

YES (Full)
Optional (Snapshot) 

Specifies whether the concept was active or inactive from the nominal release date specified by the effectiveTime.

YES

NO

Identifies the concept version's module. Set to a descendant of 900000000000443000 | Module| within the metadata hierarchy.

YES

NO

Specifies if the concept version is primitive or defined. Set to a descendant of 900000000000444006 | Definition status| in the metadata hierarchy.

YES

NO

Only one concept record with the same id field is current at any point in time. The current record will be the one with the most recent effectiveTime before or equal to the date under consideration. If the active field of this record is false ('0'), then the concept is inactive at that point in time.

When a concept is made inactive, the following operations take place:

Related Links


Feedback