User Tools

Site Tools


documentation:cdm:concept_relationship

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
documentation:cdm:concept_relationship [2014/12/06 17:25]
cgreich
documentation:cdm:concept_relationship [2017/08/17 15:19]
clairblacketer
Line 1: Line 1:
 ===== CONCEPT_RELATIONSHIP table ===== ===== CONCEPT_RELATIONSHIP table =====
 +**The CDM documentation is now being housed on [[https://​github.com/​OHDSI/​CommonDataModel/​wiki|github]]. The most recent release is [[https://​github.com/​OHDSI/​CommonDataModel/​releases/​tag/​v5.2.-bugfix.1|v5.2]]**
  
-The CONCEPT_RELATIONSHIP table contains records that define direct relationships between any two Concepts and the nature or type of the relationship. Each type of a relationship is defined in the RELATIONSHIP table.+The CONCEPT_RELATIONSHIP table contains records that define direct relationships between any two Concepts and the nature or type of the relationship. Each type of a relationship is defined in the [[documentation:​cdm:​relationship|RELATIONSHIP]] table.
  
 ^Field^Required^Type^Description^ ^Field^Required^Type^Description^
-|concept_id_1|Yes|integer|A foreign key to a Concept in the CONCEPT table associated with the relationship. Relationships are directional,​ and this field represents the source concept designation.| +|concept_id_1|Yes|integer|A foreign key to a Concept in the [[documentation:​cdm:​concept|CONCEPT]] table associated with the relationship. Relationships are directional,​ and this field represents the source concept designation.| 
-|concept_id_2|Yes|integer|A foreign key to a Concept in the CONCEPT table associated with the relationship. Relationships are directional,​ and this field represents the destination concept designation.| +|concept_id_2|Yes|integer|A foreign key to a Concept in the [[documentation:​cdm:​concept|CONCEPT]] table associated with the relationship. Relationships are directional,​ and this field represents the destination concept designation.| 
-|relationship_id|Yes|varchar(20)|A unique identifier to the type or nature of the Relationship as defined in the RELATIONSHIP table.|+|relationship_id|Yes|varchar(20)|A unique identifier to the type or nature of the Relationship as defined in the [[documentation:​cdm:​relationship|RELATIONSHIP]] table.|
 |valid_start_date|Yes|date|The date when the instance of the Concept Relationship is first recorded.| |valid_start_date|Yes|date|The date when the instance of the Concept Relationship is first recorded.|
 |valid_end_date|Yes|date|The date when the Concept Relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.| |valid_end_date|Yes|date|The date when the Concept Relationship became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.|
Line 13: Line 14:
 ==== Conventions ==== ==== Conventions ====
   * Relationships can generally be classified as hierarchical (parent-child) or non-hierarchical (lateral). ​   * Relationships can generally be classified as hierarchical (parent-child) or non-hierarchical (lateral). ​
-  * All Relationships are directional,​ and each Concept Relationship is represented twice symmetrically within the CONCEPT_RELATIONSHIP table. For example, the two SNOMED concepts of ‘Acute myocardial infarction of the anterior wall’ and ‘Acute myocardial infarction’ have two Concept Relationships:​ 1- ‘Acute myocardial infarction of the anterior wall’ ‘Is a’ ‘Acute myocardial infarction’,​ and 2- ‘Acute myocardial infarction’ ‘Subsumes’ ‘Acute myocardial infarction of the anterior wall’.+  * All Relationships are directional,​ and each Concept Relationship is represented twice symmetrically within the [[documentation:​cdm:​concept_relationship|CONCEPT_RELATIONSHIP]] table. For example, the two SNOMED concepts of ‘Acute myocardial infarction of the anterior wall’ and ‘Acute myocardial infarction’ have two Concept Relationships:​ 1- ‘Acute myocardial infarction of the anterior wall’ ‘Is a’ ‘Acute myocardial infarction’,​ and 2- ‘Acute myocardial infarction’ ‘Subsumes’ ‘Acute myocardial infarction of the anterior wall’.
   * There is one record for each Concept Relationship connecting the same Concepts with the same relationship_id.   * There is one record for each Concept Relationship connecting the same Concepts with the same relationship_id.
   * Since all Concept Relationships exist with their mirror image (concept_id_1 and concept_id_2 swapped, and the relationship_id replaced by the reverse_relationship_id from the [[documentation:​cdm:​relationship|RELATIONSHIP]] table), it is not necessary to query for the existence of a relationship both in the concept_id_1 and concept_id_2 fields.   * Since all Concept Relationships exist with their mirror image (concept_id_1 and concept_id_2 swapped, and the relationship_id replaced by the reverse_relationship_id from the [[documentation:​cdm:​relationship|RELATIONSHIP]] table), it is not necessary to query for the existence of a relationship both in the concept_id_1 and concept_id_2 fields.
documentation/cdm/concept_relationship.txt · Last modified: 2017/09/25 14:58 by clairblacketer