CONCEPT_ANCESTOR
Table Description
The CONCEPT_ANCESTOR table is designed to simplify observational
analysis by providing the complete hierarchical relationships between
Concepts. Only direct parent-child relationships between Concepts are
stored in the CONCEPT_RELATIONSHIP table. To determine higher level
ancestry connections, all individual direct relationships would have
to be navigated at analysis time. The CONCEPT_ANCESTOR table includes
records for all parent-child relationships, as well as
grandparent-grandchild relationships and those of any other level of
lineage. Using the CONCEPT_ANCESTOR table allows for querying for all
descendants of a hierarchical concept. For example, drug ingredients
and drug products are all descendants of a drug class ancestor.
This table is entirely derived from the CONCEPT, CONCEPT_RELATIONSHIP
and RELATIONSHIP tables.
CDM Field
|
User Guide
|
ETL Conventions
|
Datatype
|
Required
|
Primary Key
|
Foreign Key
|
FK Table
|
FK Domain
|
ancestor_concept_id
|
The Concept Id for the higher-level concept that forms the
ancestor in the relationship.
|
|
integer
|
Yes
|
No
|
Yes
|
CONCEPT
|
|
descendant_concept_id
|
The Concept Id for the lower-level concept that forms the
descendant in the relationship.
|
|
integer
|
Yes
|
No
|
Yes
|
CONCEPT
|
|
min_levels_of_separation
|
The minimum separation in number of levels of hierarchy between
ancestor and descendant concepts. This is an attribute that is
used to simplify hierarchic analysis.
|
|
integer
|
Yes
|
No
|
No
|
|
|
max_levels_of_separation
|
The maximum separation in number of levels of hierarchy between
ancestor and descendant concepts. This is an attribute that is
used to simplify hierarchic analysis.
|
|
integer
|
Yes
|
No
|
No
|
|
|