documentation:vocabulary:data_etl
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
documentation:vocabulary:data_etl [2015/01/24 13:05] cgreich |
documentation:vocabulary:data_etl [2015/01/24 13:09] cgreich |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| * If there is more than one potential destination table the ETL needs to identify the context in which a Standard Concept is used, and select the right table from this table. | * If there is more than one potential destination table the ETL needs to identify the context in which a Standard Concept is used, and select the right table from this table. | ||
| - | * For some Source Concepts there is **no mapping to a Standard Concept** (there is no record in the CONCEPT_RELATIONSHIP or SOURCE_TO_CONCEPT_MAP tables), usually because the Source Concept is too generic or otherwise ill-defined. In these cases, the domain_id field of the Source Concept itself should be used to place the record in the right table. Some Source Concepts have combination Domains, such as "Device/Procedure". In these cases, write a record into each of the combination Domain table (in this case to the DEVICE_OCCURRENCE and PROCEDURE_OCCURRENCE tables). As the Standard Concept write Concept 0 (concept_id=0) into the respective *_concept_id field. | + | * For some Source Concepts there is **no mapping to a Standard Concept** (there is no record in the CONCEPT_RELATIONSHIP or SOURCE_TO_CONCEPT_MAP tables), usually because the Source Concept is too generic or otherwise ill-defined. In these cases, the domain_id field of the Source Concept itself should be used to place the record in the right table. Some Source Concepts have combination Domains, such as "Device/Procedure". In these cases, write a record into each of the combination Domain table (in this case to the DEVICE_OCCURRENCE and PROCEDURE_OCCURRENCE tables). As the Standard Concept write Concept 0 (concept_id=0) into the respective <domain>_concept_id field. |
| If in the mapping process a Concept of the "Domain" or "Metadata" Domains are retrieved, an error has snuck into the mapping table. Please report those cases in the [[http://forums.ohdsi.org/c/cdm-builders/l/latest|CDM-Builder]]. | If in the mapping process a Concept of the "Domain" or "Metadata" Domains are retrieved, an error has snuck into the mapping table. Please report those cases in the [[http://forums.ohdsi.org/c/cdm-builders/l/latest|CDM-Builder]]. | ||
| - | The same is true if a Type Concept Domain, like "Obs Period Type", "Death Type", "Visit Type", "Procedure Type", etc. is produced. Though these Type Concepts are valid concepts and have to be placed into the <domain>_type_concept_id field of the respective CDM tables, they cannot be the result of the mapping process. They denote the origin of the record and the selection of Type Concepts have to be hard-wired in the ETL process. | + | The same is true if a Type Concept Domain, like "Obs Period Type", "Death Type", "Visit Type", "Procedure Type", etc. is produced. Though these Type Concepts are valid concepts and have to be placed into the <domain>_type_concept_id field of the respective CDM tables, they cannot be the result of the mapping process. They denote the origin of the record and the selection of Type Concepts should be hard-wired into the ETL process. |
documentation/vocabulary/data_etl.txt ยท Last modified: 2015/01/24 14:23 by cgreich
Page Tools
