OHDSI Home | Forums | Wiki | Github

Proposal for Creating an OHDSI FHIR Workgroup

Dear Colleagues,

This is a gentle reminder that we will have our monthly FHIR WG meeting at 12:00pm (Central Time) on May 18, 2017. The draft agenda is as follows.

  1. New member introduction (5 minutes)
  2. Action Items review (10 minutes)
  3. Presentation by Mitra Rocca: FDA CDM Harmonization project overview (20 minutes presentation, 10 minutes Q & A)
  4. WG task discussion (15minutes)
  5. Other items (Please add)

Please see the WebEx Info posted on the WG wiki page.

For those who would like to join the WG monthly meetings but have not put your email on the wiki page, could you do so or send email directly to me at jiang.guoqian at mayo.edu so that I can add you in the distribution list?




I d’like to be part of this group. I have been working on FHIR in multiple ways, and definitively think something can be done in this field

Is it still alive?
I see the latest notes
OHDSI FHIR WG Monthly Meeting on December 20 2017


Has any work been done on distribution of OHDSI data and research findings through FHIR based APIs? Additionally does OHDSI currently have tools that transform FHIR based EHR extracts into the CDM format?



I am working on reading/writing/searching within OMOP thought a R4 FHIR API.
The method is quite different from the GT-FHIR one, since there is no staging area.
The OMOP table are extended a bit to deliver some FHIR elements that are not present.

In interested, please contact

Hi Nicolas, I am interested if you can share more details. Thanks. Damien

Hi @DamienC . Sure. Some part of the source code is available there : https://framagit.org/interchu/omop-spark/tree/master/omop-solr-sync

The rest of the source code (based on spring boot jpa and hapi fhir) will be released and the whole will be packaged together.

As said, this is FHIR R4 on top of OMOP v6 and covers patient, encounter, condition, procedure, practitioner, practitionerRole, claim, composition, documentReference, group resources.

The architecture is based on postgresql, apache spark and apache solr. This may look quite complex to use 3 layers, but they combine greatly. Yet this FHIR API is used internally for data of 12M patients, 40M discharge summaries, 20m condition, claims, procedure and 2bilion labs with sub second responses.

The next steps include the FHIR concept/valueset/conceptmap resources to deliver the concept aspects of OMOP thought the FHIR API as referenced in this this issue. We think that FHIR value-set is an abstraction compatible with OMOP and d’like to adapt a bit the concept model to store them efficiently.

Friends: Please come on Wednesday.