search

jembi / hearth

A fast FHIR-compliant server focused on longitudinal data stores.
BSD 3-Clause "New" or "Revised" License
26 stars 20 forks source link

R4 Updates #176

Open korada opened 4 years ago

korada commented 4 years ago

When can we expect to see R4 definitions in Hearth? I did add the R4 definitions to my fork, but wasn't sure if that is right.

https://github.com/korada/hearth/tree/feature/r4-updates/lib/fhir/definitions

BMartinos commented 4 years ago

Hi @korada

Thank you for your query.

Jembi has scheduled in time to upgrade Hearth to make use of FHIR R4 from the beginning of next year. Unfortunately due to other constraints and deadlines we have had to push this out a little bit but have planned the work for the beginning of next year.

Having a quick look at your forked changes, it seems to be in line with what needs to be changed, there are however a few issues that still need to be dealt with. The FHIR validation module in use only supports FHIR DSTU2 and STU3. The newer version of that module doesnt support DSTU2 validations we either need to cater for or drop support for.

Out of interest sake, it would be great to find out how you are using Hearth and what kind of problem you are trying to solve? This will help us to keep the product moving forward and adding improvements for the community

korada commented 4 years ago

Hi @BMartinos

Looking forward to R4 release. I am planning to use this as our primary Fhir Server to store Patients, Patient encounters and if possible the results from the ECQM calculations.

We process around 2 million patients/hr. After trying HAPI Fhir, we felt Hearth could be a better choice to handle that throughput.