Blaze FHIR Server on Ubuntu 24.04

Blaze is an open source, self contained FHIR R4 server with an embedded CQL evaluation engine. A single Java process exposes a complete FHIR REST API for storing, searching and retrieving clinical resources such as Patient, Observation and Encounter, with all data stored on disk in an embedded RocksDB store rather than a separate database server. The cloudimg image runs the pinned official samply/blaze Docker image (v1.10.1, Apache 2.0, pinned by digest) bound to loopback, and fronts it on port 80 with an nginx reverse proxy that adds a per-VM HTTP Basic Auth gate over the FHIR API. Blaze 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. Blaze RocksDB storage (the index, transaction and resource directories it creates on first start) is persisted on a dedicated 20 GiB Azure data disk captured into the image and re-provisioned on every VM, so your FHIR data survives restarts. Blaze resolves absolute FHIR URLs from the actual host header of each request, so links returned to clients always match however the server is reached. An unauthenticated /healthz endpoint, proxied to Blaze's own /health, is provided for Azure Load Balancer health probes. Blaze is a pure JSON REST API with no browser page of its own; use curl, a FHIR client library, or a tool such as Postman. 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 stronger authentication before using it with real patient data. Backed by 24/7 cloudimg support.