This is an old revision of the document!
The source to concept map table is a legacy data structure within the OMOP Common Data Model, recommended for use in ETL processes to maintain local source codes which are not available as Concepts in the Standardized Vocabularies, and to establish mappings for each source code into a Standard Concept as target_concept_ids that can be used to populate the Common Data Model tables. The SOURCE_TO_CONCEPT_MAP table is no longer populated with content within the Standardized Vocabularies published to the OMOP community.
|source_code||Yes||varchar(50)||The source code being translated into a Standard Concept.|
|source_concept_id||Yes||integer||A foreign key to the Source Concept that is being translated into a Standard Concept.|
|source_vocabulary_id||No||varchar(20)||A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept.|
|source_code_description||Yes||varchar(255)||An optional description for the source code. This is included as a convenience to compare the description of the source code to the name of the concept.|
|target_concept_id||Yes||integer||A foreign key to the target Concept to which the source code is being mapped.|
|target_vocabulary_id||Yes||varchar(20)||A foreign key to the VOCABULARY table defining the vocabulary of the target Concept.|
|valid_start_date||Yes||date||The date when the mapping instance was first recorded.|
|valid_end_date||Yes||date||The date when the mapping instance became invalid because it was deleted or superseded (updated) by a new relationship. Default value is 31-Dec-2099.|
|invalid_reason||No||varchar(1)||Reason the mapping instance was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.|