search

GoogleCloudPlatform / healthcare-data-harmonization

This is an engine that converts data of one structure to another, based on a configuration file which describes how. There is an accompanying syntax to make writing mappings easier and more robust.
https://cloud.google.com/solutions/healthcare-life-sciences
Apache License 2.0
206 stars 64 forks source link

define mappings between source and OMOP concepts using Concept Maps #14

Open penggaolai opened 3 years ago

penggaolai commented 3 years ago

So from what I understand, you will have to provide FHIR Concept Map(s) to define mapping for the codes from your FHIR resources, such as persons, encounters, conditions, diagnosis, etc to OMOP concept ids and source concept ids. But how many Concept Maps you will have to define? In OMOP vocabulary, there are 7,961,281 codes so far.

suesusususu commented 3 years ago

Hi penggaolai, you'd need to define a concept map to translate code from one value set in FHIR to another in OMOP. For example, we have a concept map for our open sourced fhir omop mappings https://github.com/GoogleCloudPlatform/healthcare-data-harmonization/blob/master/mapping_configs/fhir_omop/code_harmonization/FHIR-OMOP-ConceptMap.harmonization.json

If you want to map all of FHIR to OMOP, then you need all codes in concept maps. But if that's only a subset then it's much more manageable.

Does this answer your question?