# 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 hardened static binary against external PostgreSQL 18 for. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4950/ferroehr

## Description

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: Helm.

## Health score

64/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 18 days ago)
- Popular: 39 (85 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)

## Links

- Documentation: https://ferroehr.eu/docs/latest/
- Official website: https://ferroehr.eu/
- GitHub: https://github.com/FerroHEALTH/FerroEHR
- Kubernetes (Helm): https://artifacthub.io/packages/helm/ferroehr/ferroehr

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/4950/ferroehr), the self-hosted and open-source app directory.
