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 | ||
|
documentation:vocabulary:mapping [2019/12/16 10:43] ptalapova |
documentation:vocabulary:mapping [2020/12/09 10:56] (current) ptalapova |
||
|---|---|---|---|
| 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 === | ||
| Line 14: | Line 14: | ||
| * Concepts participating in the “Maps to” mapping are Source (Non-standard) Concepts and Standard Concepts. | * Concepts participating in the “Maps to” mapping are Source (Non-standard) Concepts and Standard Concepts. | ||
| * The mapping always attempts to reflect the semantics of a Source Concept by an Equivalent Standard Concept. | * The mapping always attempts to reflect the semantics of a Source Concept by an Equivalent Standard Concept. | ||
| - | * Equivalent carries the same meaning, covers the same semantic space and, importantly, has the same parents and children in the hierarchy (if there are any) as well. If an equivalent Concept is not available, the mapping matches to a more generic Standard Concept(s). This ensures that a query in the target vocabulary will retrieve the same records as if they were queried in the original source vocabulary. | + | * Equivalent carries the same meaning, covers the same semantic space, and, importantly, has the same parents and children in the hierarchy (if there are any) as well. If an equivalent Concept is not available, the mapping matches to a more generic Standard Concept(s). This ensures that a query in the target vocabulary will retrieve the same records as if they were queried in the original source vocabulary. |
| * Source Concepts are mapped or may be mapped to one or several Standard Concepts. If they are mapped to more than one Standard Concept, in the resulting CDM table, there is more than one record for each record in the source. | * Source Concepts are mapped or may be mapped to one or several Standard Concepts. If they are mapped to more than one Standard Concept, in the resulting CDM table, there is more than one record for each record in the source. | ||
| * Standard Concepts are also mapped to Standard Concepts via "Maps to", this is a mapping to itself. | * Standard Concepts are also mapped to Standard Concepts via "Maps to", this is a mapping to itself. | ||
| + | * If there are 2 or more similar Standard concepts in the OMOP vocabulary, please, report about it at the [[https://forums.ohdsi.org/c/vocabulary-users|OHDSI Forum]] and unless it is fixed, as the first-line choice, use LOINC for Measurements and SNOMED for everything else. | ||
| + | * If there are 2 similar Standard concepts within SNOMED, look at the domain (Morphologic abnormality is an Observation, Clinical finding is a Condition), revise attributes and hierarchy of both concepts (its number, fullness, and correctness). It is not necessary to compare the amount of relationships/children precisely, just verify that all seems appropriate and the hierarchy is rich enough. If it does for both concepts, then choose concepts belonging to SNOMED International (short concept codes) rather than SNOMED US/UK Editions (long concept codes). If the length of concept codes is identical, then choose the one with a smaller number of concept_id. | ||
| //**NB!** Classification Concepts (standard_concept='C') do not have a mapping to a Standard Concept//. | //**NB!** Classification Concepts (standard_concept='C') do not have a mapping to a Standard Concept//. | ||
documentation/vocabulary/mapping.1576493029.txt.gz · Last modified: 2019/12/16 10:43 by ptalapova
Page Tools
