From 70bb971165a07ffd66f83d573199138d21c3c02c Mon Sep 17 00:00:00 2001 From: clairblacketer Date: Tue, 20 Jun 2017 13:43:34 -0400 Subject: [PATCH] Updated SOURCE_TO_CONCEPT_MAP (markdown) --- StandardizedVocabularies/SOURCE_TO_CONCEPT_MAP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/StandardizedVocabularies/SOURCE_TO_CONCEPT_MAP.md b/StandardizedVocabularies/SOURCE_TO_CONCEPT_MAP.md index 4cd6287..f25faf2 100644 --- a/StandardizedVocabularies/SOURCE_TO_CONCEPT_MAP.md +++ b/StandardizedVocabularies/SOURCE_TO_CONCEPT_MAP.md @@ -1,7 +1,7 @@ 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. Field|Required|Type|Description -:----|:----|:----|:----- +:-------------------------|:--------|:-----|:--------------------------------------------- |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.|