Here are 7 project requirements that can affect your choice of FHIR server vendor.
With 20+ server providers to choose from, it’s important to understand how significant the differences between them are.
1. Data location
- Spin up a new Azure FHIR server in Europe, chances are it will be in Sweden
- And so will your patient’s data
- Is your organization ok with that?
2. Multi-tenancy
- There is no “best practice” for implementing multi-tenancy in FHIR
- EVERY vendor handles this differently or not at all
- Work this out before you sign a contract
3. FHIR Subscriptions
- Do you or your users need FHIR Subscriptions?
- Many of the big name vendors don’t support them
- Building this yourselves is a HUGE project
4. Smart-on-FHIR
- Smart-on-FHIR v2 is not supported by all vendors
- “We’re working on it” is not an answer
5. Analytical Queries
- Will you need to run big queries against your FHIR data?
- Some vendors have built-in analytical abilities, most do not
- Building this yourselves is a HUGE project
6. Cross border
- Different countries, different Implementation Guides
- How does each vendor handle this?
- Managing multiple IGs yourselves is not for the faint-hearted
7. Extending FHIR
- Custom operations, proxies, interceptors, custom search parameters…
- Every vendor does them differently or not at all
- Pick one that your technical team can work with
The lesson here is “do your homework.”
The harder to swallow lesson is “you need a POC.” Even if you have to pay for it.
Understand your own requirements first, then insist that every vendor on your shortlist can meet those requirements.
If they can’t, take them off the list.
---