Your question is impossible to answer without additional information.
Just to give you a rough idea what I am talking about and you might take into consideration:
- Legal constraints
- Technical constraints (deployment, authentication, security etc.)
- Self development / involvement
- Integration with existing infrastructure
- many more
To give you a concrete example. We had to make the decision which server to use some months ago as well. We basically took a look on Azure FHIR API (we are customer there), IBM FHIR Server (which i really like), AWS HealthLake and HAPI.
At the end we made the decision based on the following reasons:
- It’s open source, so we can see what it is doing
- We have to possibility to adopt it to fit our needs. As nobody in my team knows C#/.NET it would be much harder with Azure’s OS Edition
- Data Security and Trust: We are a Munich based company with both hospitals and insurances as customers operating within the EU with a strong footprint in DACH. This made that point most crucial for us. It was clear that we want to host the server ourselves and have no external dependencies.
Don’t get me wrong, I do believe that IBM or Microsoft have good PaaS solutions which are safe, fast and act according to GDPR, however if you followed the political discussions within Germany over the past months you understand the decision against them.
Conclusion is, we went with HAPI with respect to the points above. We are super happy with the support of the community over there and can’t confirm any negative performance leaks which were mentioned in other threads before.
I hope it helps to give u an rough idea how to come up with ur own decision