Historical Type Concepts Do Not have a "Maps To" Relationship

OHDSI / Vocabulary-v5.0

Build process for the OHDSI Standardized Vocabularies. Currently not available as independent release.

The Unlicense

214 stars 74 forks source link

Historical Type Concepts Do Not have a "Maps To" Relationship #614

Open cukarthik opened 2 years ago

cukarthik commented 2 years ago

With the new Type Concept domain old historical type concepts like, Condition Type, became non-standard. However, the deprecated concepts do not have a Maps To relationship. For example, EHR Problem List Entry is an orphan concept when it should most likely be mapped to EHR Problem List.

cgreich commented 2 years ago

Yeah, because neither the historical nor the new ones are external vocabularies. We try to provide mapping if you have source data with codes from a public vocabulary. These are internal. You need to refactor the ETL you have in place for the old one. Shouldn't be a big deal.

Alexdavv commented 2 years ago

Some more background (post 2-3): https://forums.ohdsi.org/t/important-vocabulary-release-type-concept-and-condition-status/11760/3

mik-ohdsi commented 2 years ago

@cukarthik - you okay with refactoring your ETL? Still think we have to implement "replaced by" links of some sort?