HAPI FHIR Server (FHIR R4/R5) on Ubuntu 24.04 LTS by cloudimg. The de-facto open source FHIR server for healthcare interoperability: a full FHIR REST API at /fhir plus a built-in web tester UI, served behind nginx on port 80 with a per-instance HTTP Basic Auth password generated on first boot. The bundled H2 database persists to a dedicated Azure data disk. Apache 2.0 licensed. Ships as infrastructure; you own all HIPAA and PHI controls.
HAPI FHIR is the de-facto open source FHIR server for healthcare interoperability. It exposes a complete FHIR REST API (FHIR R4/R5) for storing, searching and retrieving clinical resources such as Patient, Observation and Encounter, alongside a built-in web tester UI for browsing the server, reading its CapabilityStatement and running requests interactively. The cloudimg image runs the pinned official HAPI FHIR JPA Server Starter container (hapiproject/hapi v8.10.0-2, Apache 2.0) bound to loopback, and fronts it on port 80 with an nginx reverse proxy that adds a per-VM HTTP Basic Auth gate over both the tester UI and the FHIR API. HAPI's server itself ships open by design, so the nginx Basic Auth credential is the access gate, and a unique password is generated on the first boot of every VM (user admin) and written to a root only file. The bundled H2 database is switched to file backed persistence on a dedicated 20 GiB Azure data disk captured into the image and re-provisioned on every VM, so your FHIR data survives restarts. An unauthenticated /healthz endpoint is provided for Azure Load Balancer health probes. Compliance note: this image ships as infrastructure and is not a certified or HIPAA compliant healthcare product. If you store, process or transmit protected health information you are responsible for the required controls, including TLS, FHIR level authentication and authorization, audit logging and backups. Add a real domain, TLS and FHIR level authorization before using it with real patient data. Backed by 24/7 cloudimg support.