We currently have the Microsoft FHIR server provisioned in all our environments. Microsoft's FHIR server offers high availability and throughout...at high cost. We don't need to be able to process large volumes of data in these lower environments, and we also don't need them always-available. For cost savings, we should switch to using the HAPI FHIR server in our lower environments.
Action Requested
Change the dev setup to use the HAPI FHIR server instead of the Microsoft FHIR server.
We may still want some kind of pre-prod environment that is a closer copy of the production environment, but that can be resolved in a later ticket.
Acceptance Criteria
The dev environments deploy a HAPI FHIR server and don't use the Microsoft FHIR server.
Why are we doing this?
We currently have the Microsoft FHIR server provisioned in all our environments. Microsoft's FHIR server offers high availability and throughout...at high cost. We don't need to be able to process large volumes of data in these lower environments, and we also don't need them always-available. For cost savings, we should switch to using the HAPI FHIR server in our lower environments.
Action Requested
Change the
dev
setup to use the HAPI FHIR server instead of the Microsoft FHIR server.We may still want some kind of
pre-prod
environment that is a closer copy of the production environment, but that can be resolved in a later ticket.Acceptance Criteria
The
dev
environments deploy a HAPI FHIR server and don't use the Microsoft FHIR server.Additional Context
Came out of a cloud techtro discussion on 4/18.