EHRbase on Ubuntu 24.04 LTS by cloudimg

EHRbase is an open source openEHR Clinical Data Repository: a standards-based backend for storing and querying structured electronic health record data. It implements the openEHR Reference Model, stores clinical compositions against uploaded operational templates, and exposes the official openEHR REST API together with the Archetype Query Language query endpoint, so clinical applications and integration engines write and read vendor-neutral, semantically rich health data over HTTP and JSON. This image delivers EHRbase 2.34 fully installed and configured on Ubuntu 24.04 LTS, hardened and fully patched, so a conformant openEHR API is answering within a minute or two of launch.

Application stack: EHRbase runs as a dedicated non-root systemd service on the Eclipse Temurin Java 25 runtime it requires, backed by a local standard PostgreSQL 16 database that has been bootstrapped with the two roles, the ehr and ext schemas and the uuid-ossp extension EHRbase expects. EHRbase manages its own database schema with Flyway and applies all migrations automatically on first start. Its embedded server serves the openEHR REST API over HTTP on port 8080 under the /ehrbase context path. EHRbase is a headless API server with no rich web UI, designed to sit behind your own applications, reverse proxy and identity provider.

Secure by default: EHRbase ships with documented default Basic-auth credentials, so this image is secure by default. On the first boot of your instance a one-shot service rotates both the built-in admin and user passwords to unique per-instance values, rotates the two PostgreSQL role passwords in lockstep, disables EHRbase's insecure default profile, and recreates the database empty, all before the API port accepts traffic. The default credentials are neutralised and the per-instance passwords are written to a root-only credentials file. The database starts empty on first boot with no prior data.

Key capabilities: a conformant openEHR persistence layer for EHRs, compositions and operational templates; the official openEHR REST API for clinical applications and integrations; Archetype Query Language querying for analytics and research; and standard PostgreSQL storage you can back up and operate with familiar tools.

Get started: retrieve the per-instance Basic-auth credentials from the root-only credentials file, upload an operational template, then create EHRs and store compositions through the openEHR REST API. Put EHRbase behind your own TLS-terminating reverse proxy and identity provider for production. cloudimg engineers can help with template and archetype modelling, AQL query design, reverse-proxy and TLS options, PostgreSQL tuning and version upgrades after purchase.

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.