Bidirectional FHIR ETL

[parisni]

Hi

AFAIK your platform is able to produce FHIR resources throught HAPI FHIR from data that is stored into OMOP.

Do you plan to be able to ingest FHIR data into OMOP thought HAPI FHIR too ?

Am I missing something ?

Thanks,

[myungchoi]

Current version (Release 1) does bidirectional mapping. But, the mapping is very primitive (easy mapping or obvious mapping). So, you can POST FHIR, which will create OMOP entries in the table.

For our release 2 (which we are trying to set up a separate repo), we are trying to handle more (or better) mapping. In OMOP, there are other tables that need to be driven from another table. We are trying to get that process integrated when we do FHIR to OMOP direction. So, we have asymmetric bidirectional transaction. For OMOP to FHIR, it will be based on FHIR-views from OMOP tables.

[parisni]

@myungchoi thanks for the details. A couple of new questions:

we are trying to handle more (or better) mapping

what about local FHIR profiles & extensions ? Are they in your mind for the mapping ?

it will be based on FHIR-views from OMOP tables

does it mean SQL VIEWS ? relational -> Json ?

Thanks