documentation:vocabulary:mapping
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
documentation:vocabulary:mapping [2019/12/16 10:43] ptalapova |
documentation:vocabulary:mapping [2020/12/09 09:34] ptalapova [Table] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Mapping of Concepts ===== | ===== Mapping of Concepts ===== | ||
| + | * **Mapping**, also known as **a map**, is an association between a particular concept in one code system or | ||
| + | * dataset and code in another, rarely the same, code system that has the same (or similar) meaning. | ||
| + | * Also, **Mapping** is the process to transform one concept into a Standard one. The Standardized Clinical Data Tables allow only Standard Concepts, thus all other codes used in the source databases have to be translated to Standard Concepts. | ||
| + | * Mapping is done through records in the CONCEPT_RELATIONSHIP table. They connect each Concept to a Standard Concept through a number of special relationship_id: | ||
| - | **Mapping** is the process to transform one Concept to another. The clinical data tables of the CDM allow only Standard Concepts. All other codes used in the source databases have to be translated to Standard Concepts. | + | ^ Relationship ID ^ Purpose ^ Features ^ |
| - | + | | **Maps to** | Mapping a Source Concept to a Standard Concept to be placed into the following fields of :[[https://github.com/OHDSI/CommonDataModel/wiki/Standardized-Clinical-Data-Tables|Standardized Clinical Data Tables]]:\\ • **condition_concept_id**\\ • **observation_concept_id**\\ • **measurement_concept_id**\\ • **drug_concept_id**\\ • **procedure_concept_id**\\ • **device_concept_id** etc. \\ \\ Note, that this relationship is also used for mapping of concepts to populate **value_as_concept_id**. | • stands for either a full equivalence or an “uphill” mapping (mapping to a more general semantic category)\\ \\ • can be single or multiple for each Source Concept | | |
| - | Mapping is done through records in the CONCEPT_RELATIONSHIP table. They connect each Concept to a Standard Concept through a number of special relationship_id: | + | | **Maps to value** | A special mapping between a Source Concept and a Standard Concept to be placed into the **value_as_concept_id** field of the MEASUREMENT and OBSERVATION tables | • points to a concept, indicating the value of Measurements or content of Observations\\ \\ • is used only in combination with a single “Maps to” | |
| - | + | ||
| - | ^ Relationship ID ^ Purpose ^ Features ^ | + | |
| - | | **Maps to** | Mapping a Source Concept to a Standard Concept to be placed into the following fields of :[[https://github.com/OHDSI/CommonDataModel/wiki/Standardized-Clinical-Data-Tables|Standardized Clinical Data Tables]]:\\ • **condition_concept_id**\\ • **observation_concept_id**\\ • **measurement_concept_id**\\ • **drug_concept_id**\\ • **procedure_concept_id**\\ • **device_concept_id** | • stands for either a full equivalence or an “uphill” mapping (mapping to a more general semantic category)\\ \\ • can be single or multiple for each Source Concept | | + | |
| - | | **Maps to value** | A special mapping between a Source Concept and a Standard Concept to be placed into the **value_as_concept_id** field of the MEASUREMENT and OBSERVATION tables | • points to a concept, indicating the value of Measurements or content of Observations\\ \\ • is used only in combination with a single “Maps to” | | + | |
| === "Maps to" Relationships === | === "Maps to" Relationships === | ||
documentation/vocabulary/mapping.txt · Last modified: 2020/12/09 10:56 by ptalapova
Page Tools
