Hospital IT departments evaluate FHIR API servers under constraints that look different from those a clinical software vendor faces. The server has to fit an existing operational footprint, integrate with established identity and audit tooling, and survive an environment where the team running it usually owns dozens of other services as well. The six servers below are the ones US hospital IT departments most often run in 2026, with notes on where each one fits. For more, see additional FHIR API notes.
The clinical FHIR server buyer's guide gives the broader selection framing; this article is the hospital-side shortlist.
The 6 FHIR API Servers Hospital IT Departments Most Often Run
The order below reflects deployment frequency in US hospital settings, not feature breadth.
- HAPI FHIR. The Java open-source reference server. Hospital IT teams pick it for the maturity, the deep community knowledge, and the ability to fork and maintain in-house. The trade-off is operational ownership.
- Smile Digital Health. A commercial layer on HAPI that gives hospital IT a support contract and managed terminology, often picked when the team needs an SLA without giving up the HAPI surface.
- Microsoft FHIR Server for Azure. A cloud-native FHIR API tuned for hospital systems already running on Azure, with first-class integration into Azure AD and the rest of the cloud's identity stack.
- Google Cloud Healthcare API. A managed FHIR store with strong BigQuery integration, used in hospitals running research or population-health programs that lean on cloud-side analytics.
- IBM FHIR Server. An enterprise-grade open-source server with strong audit and persistence options, deployed in larger hospital systems where audit-trail completeness is a regulatory requirement.
- Aidbox FHIR server. A developer-oriented server picked by hospital IT teams building internal clinical applications and prioritizing flexible query APIs alongside the standard REST surface.
Other servers that appear in hospital deployments but did not make this shortlist include Firely, Medplum, and several vendor-bundled servers shipped inside EHR or telehealth platforms. The six above cover the bulk of standalone hospital deployments.
What Decides the Fit for Hospital IT
Three factors tend to drive the choice in hospital IT departments.
The first is identity-stack integration. Hospitals already run an SSO and audit infrastructure, and the FHIR server has to plug into that without a separate identity model. Microsoft FHIR Server and Smile have the cleanest stories here; HAPI requires more glue, and IBM brings its own audit framework.
The second is the operational footprint. Hospital IT measures servers on how they survive routine deployment events: patching, rolling restarts, log volume, and observability. Managed offerings like the Google and Microsoft options reduce this footprint at the cost of cloud lock-in.
The third is terminology service coupling. Validation against value sets like LOINC and SNOMED CT requires a working terminology service. Some servers ship one in-process; others expect an external terminology server. The top 5 managed FHIR services for clinical software teams walkthrough covers the managed side of this question.
How Hospital IT Teams Should Pick
The honest evaluation is to run each candidate against a representative hospital workload for a week and measure validation throughput, audit-log volume, and integration friction with the existing identity stack. Hospital teams that pick on feature list often spend the next year unwinding integration choices. The top 5 FHIR servers for clinical software vendors walkthrough covers the vendor-side view, which usually has to be supported by the hospital server too. The server the team is still happy to run a year in is the right one.
Sources
- HAPI Plain Server Introduction - Docs, HAPI FHIR project, 2025
- US Core General Requirements - IG, HL7, 2025
- Bulk Data Access IG v3.0.0 - IG, HL7, 2025
