FHIR Chat · Athena OHDSI terminology load to HAPI · hapi

Stream: hapi

Topic: Athena OHDSI terminology load to HAPI


view this post on Zulip Craig McClendon (Mar 08 2022 at 18:28):

OHDSI standardizes many common terminologies into an OMOP data model and allows you to download the extracts.
Has anyone attempted to load these extracts to the HAPI JPA server? It would be convenient to be able to load multiple terminologies in one step.
https://www.ohdsi.org/analytic-tools/athena-standardized-vocabularies/

view this post on Zulip Joel Schneider (Mar 09 2022 at 04:48):

This might be a good topic to raise on the #OMOP + FHIR Terminologies stream.

To me, it's not immediately clear how this would look in FHIR. Maybe a new CodeSystem for OMOP concept (concept_id ...), and a ConceptMap for OMOP concept_relationship (concept_id_1, concept_id_2, ...) ... ?

view this post on Zulip Grahame Grieve (Mar 10 2022 at 00:14):

open dsicussion now

view this post on Zulip Craig McClendon (Mar 10 2022 at 00:15):

For more detail, Athena lets you download ~60 different terminologies in a common model (as CSVs) - it has CPT, DRG, 7 or so flavors of ICD, SNOMED, LOINC, NDC, RxNorm, etc.
The HAPI cli tool can process the direct extracts from snomded, loinc, and ICD10 into a HAPI JPA server. I was mostly curious if anyone's tried to extend it to process the Athena extracts - kind of a one-stop shop to get almost everything.

view this post on Zulip Grahame Grieve (Mar 10 2022 at 00:18):

ask on the omop track and tag Michael Lawley


Last updated: Apr 12 2022 at 19:14 UTC