mz-health/OMOP
mz-health
/
OMOP
mirror of https://github.com/OHDSI/CommonDataModel.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Change example for multiple mappings

Anna Ostropolets 2018-07-19 16:56:09 +03:00
parent 777ff6078b
commit 77af61b226
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Background/Data-Model-Conventions.md

@ -68,7 +68,7 @@ When processing your data where source value is a reference to a coding scheme c
- If the source code uses alternative formatting (ex. format has removed decimal point from ICD-9 codes), you will need to perform the formatting transformation within the ETL. In this case, you may wish to store the mappings from original codes to source concept ids in the SOURCE_TO_CONCEPT_MAP table.
- If the source code is not mappable to a vocabulary term, the source_concept_id field is set to 0
- Use the CONCEPT_RELATIONSHIP table to identify the standard concept_id that corresponds to the source_concept_id in the domain.
- Each source_concept_id can have 1 or more Standard concept_id mapped to it. Each Standard concept_id belongs to only one primary domain, but when a source concept_id maps to multiple standard concept_ids, it is possible for that source_concept_id to result in records being produced across multiple domains. For example, HCPCS code for infusion of a drug will map to a concept in the procedure domain of the infusion and a different concept in the drug domain for the product infused. It is also possible for one source_concept_id to map to multiple standard concept_ids within the same domain. For example, ICD-9 for 'viral hepatitis with hepatic coma' maps to SNOMED 'viral hepatitis' and a different concept for 'hepatic coma' in which case multiple condition_occurrence records will be generated for the one source value record.
- Each source_concept_id can have 1 or more Standard concept_id mapped to it. Each Standard concept_id belongs to only one primary domain, but when a source concept_id maps to multiple standard concept_ids, it is possible for that source_concept_id to result in records being produced across multiple domains. For example, ICD10CM Z34.00 'Encounter for supervision of normal first pregnancy, unspecified trimester' will be mapped to the SNOMED concept in the procedure domain 'Routine antenatal care' and the concept in the condition domain 'Primagravida'. It is also possible for one source_concept_id to map to multiple standard concept_ids within the same domain. For example, ICD-9 for 'Viral hepatitis with hepatic coma' maps to SNOMED 'Viral hepatitis' and a different concept for 'hepatic coma' in which case multiple condition_occurrence records will be generated for the one source value record.
- If the source_concept_id is not mappable to any standard concept_id, the concept_id field is set to 0.
- Write the data record into table(s) corresponding to the domain of the standard concept_id(s).
- If the source value is mapped to source_concept_id, but the source_concept_id is not mapped to a standard concept_id, then the domain for the data record, and hence it's table location, is determined by the domain_id field of the CONCEPT record the source_concept_id refers to. The standard concept_id is set to 0.