Field Data Type Required Description and Notes INTEGER YES A unique identifier for the Clinical Description. CONCEPT_ID INTEGER YES A foreign key to a Concept stored in the Concept table of the Dictionary. DESCRIPTION_NAME VARCHAR(1000) YES The text of the term used to describe the Concept associated with the Description. Example of Loaded Table The following example illustrates the representation of Descriptions associated with a SNOMED-CT Concept The Concept can be described in the following ways: “Chronic Atrial Fibrillation’. Concept Code: 426749004 Concept Fully Specified Name: Chronic atrial fibrillation (disorder) Preferred Term for the Concept: Chronic atrial fibrillation Source Vocabulary: SNOMED_CT Description Status: Current for both Preferred Term and Fully Specified Name If the Fully Specified Name for the Concept is used as the Concept Name in the Concept entity, then the preferred term is stored as a Synonym in the Synonym entity. The particulars for the Synonym being added are as follows: Concept ID: 3409069 Concept Synonym ID: 3351850 Description Name: Chronic atrial fibrillation Concept Synonym ID Concept ID Description Name 3409069 4141360 Chronic atrial fibrillation CONCEPT_REIONSHIP The Concept Relationship entity stores the relationship between two Concepts. The relationships described in the CDM are directional and are intended to include a Source Concept and a Target Concept with an explicit relationship from Source to Target. Concept Relationship includes many different types of relationships between Concepts. The type of relationships described between Concepts includes the following: Hierarchical or relationships), which are used to define a direct ”ISA” Relationships (Subsumes hierarchies between Concepts. Only the hierarchy relationships between two closest Concepts are captured in the Relationship table. All the Ancestor and descendent relationships that are not immediate parent-child relationships are recorded in the Concept Ancestor table. The hierarchical relationships can be between Concepts that are adopted from the same Vocabulary source or between Concepts adopted from difference Vocabulary sources. The Relationship Type attribute is used to identify various types of relationships that are captured in the Concept Relationships table.
Field Data Type Required Description and Notes INTEGER YES A unique identifier for the Clinical Description. CONCEPT_ID INTEGER YES A foreign key to a Concept stored in the Concept table of the Dictionary. DESCRIPTION_NAME VARCHAR(1000) YES The text of the term used to describe the Concept associated with the Description. Example of Loaded Table The following example illustrates the representation of Descriptions associated with a SNOMED-CT Concept “Chronic Atrial Fibrillation’. The Concept can be described in the following ways: Concept Code: 426749004 Concept Fully Specified Name: Chronic atrial fibrillation (disorder) Preferred Term for the Concept: Chronic atrial fibrillation Source Vocabulary: SNOMED_CT Description Status: Current for both Preferred Term and Fully Specified Name If the Fully Specified Name for the Concept is used as the Concept Name in the Concept entity, then the preferred term is stored as a Synonym in the Synonym entity. The particulars for the Synonym being added are as follows: Concept ID: 3409069 Concept Synonym ID: 3351850 Description Name: Chronic atrial fibrillation Concept Synonym ID Concept ID Description Name 3409069 4141360 Chronic atrial fibrillation CONCEPT_REIONSHIP The Concept Relationship entity stores the relationship between two Concepts. The relationships described in the CDM are directional and are intended to include a Source Concept and a Target Concept with an explicit relationship from Source to Target. Concept Relationship includes many different types of relationships between Concepts. The type of relationships described between Concepts includes the following: Hierarchical or ”ISA” Relationships (Subsumes relationships), which are used to define a direct hierarchies between Concepts. Only the hierarchy relationships between two closest Concepts are captured in the Relationship table. All the Ancestor and descendent relationships that are not immediate parent-child relationships are recorded in the Concept Ancestor table. The hierarchical relationships can be between Concepts that are adopted from the same Vocabulary source or between Concepts adopted from difference Vocabulary sources. The Relationship Type attribute is used to identify various types of relationships that are captured in the Concept Relationships table.
4ab62b8893541e0adf6592bc0b362f26a7355e9d.docx