documentation:cdm:cdm:relationship
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
documentation:cdm:cdm:relationship [2014/11/14 17:23] cgreich |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== RELATIONSHIP table ===== | ||
| - | |||
| - | The RELATIONSHIP table provides a reference list of all types of relationships that can be used to associate any two concepts in the CONCEPT_RELATIONSHP table. Relationships are classified as hierarchical (parent-child) or non-hierarchical (lateral), and are used to determine which concept relationship records should be included in the computation of the CONCEPT_ANCESTOR table. | ||
| - | |||
| - | ^Field^Required^Type^Description^ | ||
| - | |relationship_id|Yes|varchar(20)| The type of relationship captured by the relationship record.| | ||
| - | |relationship_name|Yes|varchar(255)| The text that describes the relationship type.| | ||
| - | |is_hierarchical|Yes|varchar(1)|Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.| | ||
| - | |defines_ancestry|Yes|varchar(1)|Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0.| | ||
| - | |reverse_relationship_id|Yes|varchar(20)|The identifier for the relationship used to define the reverse relationship between two concepts.| | ||
| - | |relationship_concept_id|Yes|integer|A foreign key that refers to an identifier in the CONCEPT table for the unique relationship concept.| | ||
| - | |||
| - | ==== Conventions ==== | ||
| - | |||
| - | * There is one record for each Relationship. | ||
| - | The relationship_id field contains an alphanumerical identifier, that can also be used as the abbreviation of the Relationship. | ||
| - | * The relationship_name field contains the unabbreviated names of the Relationship. | ||
| - | * Relationships all exist symmetrically, i.e. in both direction. The relationship_id of the opposite Relationship is provided in the reverse_relationship_id field. | ||
| - | * Each Relationship also has an equivalent entry in the Concept table, which is recorded in the relationship_concept_id field. This is for purposes of creating a closed Information Model, where all entities in the OMOP CDM are covered by unique Concepts. | ||
| - | * Hierarchical Relationships are used to define a hierarchical tree between Concepts. For example, "has_ingredient" is a Relationship between Concepst of the Concept Class 'Clinical Drug' and those of 'Ingredient', and all Ingredients can be classified as the "parental" hierarchical Concepts for the Drugs they are part of. All 'Is a' Relationships are hierarchical. Relationships, also hierarchical, can be between Concepts within the same Vocabulary or those adopted from different Vocabulary sources. | ||
| - | * Non-hierarchical Relationships are all remaining non-inclusive relationships, for example between Clinical Drugs and Branded Drugs. These Relationships are not utilized to create Ancestor relationships. | ||
| - | Past versions of the OMOP CDM did not have a separate reference table for all Concept Classes. Also, the content of the old concept_class and the new concept_class_id fields are not always identical. A conversion talbe can be found here: | ||
documentation/cdm/cdm/relationship.1415985802.txt.gz ยท Last modified: 2014/11/14 17:23 by cgreich
Page Tools
