FHIR DSTU3

[parisni]

Hi there

Have you planned to port your platform compliant with the last FHIR release ? Is there any work on that topic ?

Thanks by advance

[myungchoi]

We are in the process of doing that. We changed our approach on OMOP on FHIR mapping strategy. And, it will make this project whole a lot easier if we start from separate GitHub repo. So, we will be creating a new one sometime within a couple of weeks. As we can't really share non-working code stack, we will not make an announcement. But, you will see a new repo in couple weeks. And, the new repo will be using STU3 with HAPI-FHIR stack.

[singram]

This is a great to hear! Any update on progress or expected availability?

[Rokshan2016]

Hi, @myungchoi Any update on progress or expected availability ?

[myungchoi]

I am now starting to update for STU3. I just created a new branch from master. I will push as I move on. But, those will be broken until I finish updating all. I will try to leave DSTU2 stuff as much as I can. For example, I will see if I can leave MedicationOrder. But, if our JPA model complaints, I will make STU3 only version.

[Rokshan2016]

ok , thanks for the information

[myungchoi]

I found that it requires too many changes. And, having FHIR model to be JPA model of OMOP does not work quite well for some resources. So, I am doing from scratch for STU3 with a new name called "GT-FHIR2". I created a new repo for this.

I separated HAPI FHIR with JPA unlike GT-FHIR version 1. I did a quick test with HAPI's Restful server example for organization resource with care_site in OMOP. I get read() working.

Now I am adding necessary OMOP tables in JPA.

The GT-FHIR2 need lots of work. If anyone wants to participate in developing with me. Please email me. I will create a branch.

[parisni]

I am also interested; but no way to get your email

[myungchoi]

myung.choi@gtri.gatech.edu

[parisni]

hi myung email sent, apparently in spam? thx