EHRbase on Ubuntu 24.04

Azure Applications

EHRbase, the open source openEHR Clinical Data Repository, storing and querying standards based structured health data through the openEHR REST API, secured on first boot.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

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 integrations write and read vendor neutral, semantically rich health data over HTTP and JSON.

It suits digital health teams, health data platforms and research projects that need a conformant openEHR persistence layer without building one: a headless REST API server for compositions, EHRs, templates and AQL queries, backed by standard PostgreSQL, that plugs into clinical front ends, integration engines and analytics pipelines. It is an API server with no rich web UI, designed to sit behind your own applications and identity provider.

Why the cloudimg image

cloudimg delivers EHRbase fully installed on a hardened, fully patched base on the Java 25 runtime it requires, with a local standard PostgreSQL database already bootstrapped with the roles, schemas and extension EHRbase needs, so the openEHR REST API answers the moment the instance boots and applies its own schema migrations on first start. The image is secure by default: EHRbase ships documented default Basic auth credentials, so on the first boot of each instance the built in admin and user passwords are both rotated to unique per instance values and the database role passwords are rotated in lockstep, before the API accepts traffic, with the insecure default profile disabled and the credentials written to a root only file. The database starts empty on first boot, and the image ships with a paired step by step deploy guide and 24/7 cloudimg support.

Common uses

  • A conformant openEHR persistence layer for clinical applications, storing compositions against operational templates over the openEHR REST API
  • Vendor neutral structured health data storage with Archetype Query Language querying for analytics and research pipelines
  • A standards based clinical data backend behind an integration engine or identity provider in a digital health platform