Question

When using the OHDSI OMOP Common Data Model, what is the mandatory structural requirement for mapping local source clinical codes to the target standardized vocabulary?

Accepted Answer

The mandatory structural requirement for mapping local source codes in the OMOP Common Data Model is the utilization of the CONCEPT_RELATIONSHIP table to link source concepts to target standardized concepts. In the OMOP model, every piece of clinical data is represented by a concept, which is a unique identifier within the OMOP vocabulary system. Source codes must be mapped to their corresponding standardized concepts, such as SNOMED CT for conditions, LOINC for measurements, or RxNorm for drugs. This is achieved by creating a record in the CONCEPT_RELATIONSHIP table where the concept_id_1 represents the source concept, the concept_id_2 represents the target standard concept, and the relationship_id is set to &#x27;Maps to&#x27;. A &#x27;Maps to&#x27; relationship is the specific structural requirement that confirms a source code has been officially translated into a standardized vocabulary term accepted by the OMOP CDM. If a source code cannot be mapped to a standard concept, it must be mapped to a non-standard &#x27;0&#x27; concept, but the structural integrity of the database depends on this link being documented through the defined relationship structure rather than just matching raw data labels.

Home → All Courses → Engineering and Technology Courses → Digital Health Systems Design → Flashcard

When using the OHDSI OMOP Common Data Model, what is the mandatory structural requirement for mapping local source clinical codes to the target standardized vocabulary?