Stream: implementers
Topic: Setting up a basic FHIR server sandbox env
Rob Whelan (Nov 24 2020 at 16:33):
Hello! I'm working on various projects that wrap a FHIR interface around something else; to help API clients work on integration with our FHIR API (without hitting the real, proxied backend), I'd like to run a multi-tenant read/write FHIR server in our sandbox environment that just serves as the stand-in.
Is HAPI FHIR the best candidate for something like this? I do see the JPA-starter project, and some documentation on a DB-partition-based multi-tenancy option:
https://github.com/hapifhir/hapi-fhir-jpaserver-starter
https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/partitioning.html
This looks fairly possible.
Other suggestions that people have used to fill this kind of role?
Or pitfalls we may run into with hapi-fhir?
Most of my fellow devs don't have deep Java experience, but my expectation is to get this running without 0much customization involved, and we can focus on our core product.
I've been leaning towards OSS (since we'll probably turn off a lot of pieces that we're doing ourselves, like authentication/authorization and message validation).
Thanks in advance for any suggestions!
Yunwei Wang (Nov 24 2020 at 16:36):
There is a #hapi stream where you can get better answers. There are other server implementations. You can find the "incomplete" list here: https://confluence.hl7.org/display/FHIR/Open+Source+Implementations
Paul Church (Nov 24 2020 at 17:08):
I suggest the Google Cloud Healthcare API for as many cheap, scalable, zero-configuration FHIR store instances as you could possibly need. #shamelessplug (perhaps not as customizable as you're looking for though)
Rob Whelan (Nov 25 2020 at 16:10):
Paul Church said:
I suggest the Google Cloud Healthcare API for as many cheap, scalable, zero-configuration FHIR store instances as you could possibly need. #shamelessplug (perhaps not as customizable as you're looking for though)
Thanks — Google does offer quite a bit more than I'd realized! This may not fit with our current need, but we may be able to use it on other upcoming projects.
Last updated: Apr 12 2022 at 19:14 UTC
