FerroEHR

FerroEHR is a pure-Rust, openEHR-conformant clinical data repository that stores and queries health records through ITS-REST 1.1.0 and AQL 1.1, running as a…

  • Databases
  • Development
  • Tools & Utilities
FerroEHR is a pure-Rust, openEHR-conformant clinical data repository that stores and queries health records through ITS-REST 1.1.0 and AQL 1.1, running as a hardened static binary against external PostgreSQL 18 for teams needing a secure, vendor-neutral electronic health record backend.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

64/100 Good

Maintained
100last commit 18 days ago
Popular
3985 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
85
Open issues
51
Last commit
2026-11-03
Latest release
v5.5.0
Activity
rising

Checked 18 days ago - source: GitHub (FerroHEALTH/FerroEHR)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Deployment Deploy the FerroEHR Helm chart, which runs the service non-root with a read-only rootfs; configure an external PostgreSQL 18 database, an unprivileged application role, and a separate schema-preparation credential. source
  • Deployment FerroEHR runs as a hardened static binary with an external PostgreSQL 18 database. It can be deployed with its Helm chart; use the documentation quick start or live sandbox for initial setup. source

Fetched 11 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does FerroEHR require installing a JVM, application server, or OpenSSL?

No. It is a single self-contained binary that links a pure-Rust TLS stack, so it needs no JVM or OpenSSL; you still provide a PostgreSQL 18 database.

Is FerroEHR a headless API service rather than a bundled web UI?

Yes. It is described as a headless, API-first clinical data repository, so it exposes openEHR REST APIs instead of a built-in user interface.

Which openEHR REST and query API versions does it implement?

It implements openEHR ITS-REST 1.1.0 and AQL 1.1.

Is the public demo data persistent?

No. The hosted sandbox uses the demo credentials ferroehr and ferroehr, and its demo data is wiped nightly.

Answers sourced from ferroehr.eu, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads