v5.7.1-rc1 released

A pure-Rust openEHR Clinical Data Repository, with its conformance measured.

openEHR separates clinical knowledge from software: applications store and query structured health records through a vendor-neutral REST API and the Archetype Query Language. FerroEHR implements that standard natively in Rust: headless, API-first, one self-contained binary on PostgreSQL 18.

A server image, a viewer image and a Helm chart on GHCR, built at SLSA Build Level 3, with no JVM and no language runtime, and the openEHR model crates on crates.io.

Conformance

Conformance you can verify.

Veredictum, a separate openEHR conformance instrument, runs its whole catalogue against a live FerroEHR on every push to main. One run against the released specification is committed as the record, and every number below is read from it.

2875rows run
2875passed
0failed or errored
199skipped

The committed record: FerroEHR 5.6.0-rc10, veredictum 0.4.1, released profile, 2026-11-17.

Released specification openEHR BASE · released openEHR OPTIONS · released specification · released veredictum · released
Development specification, never counted toward the record openEHR BASE · development openEHR OPTIONS · development specification · development veredictum · development
The viewer

See what the API serves

ferroehr-viewer is a web UI for any ITS-REST 1.1.0 CDR. It goes through the public API and never the database, so what you see is exactly what the API serves: queries, templates, EHRs, parties, terminology and the audit log.

The viewer's dashboard.
The dashboard. Every page of the viewer.
In the family

The product that stores the record

The FerroHEALTH products reach each other only over published protocols. FerroEHR is where the openEHR record lives.

FerroPIX

The patient index FerroEHR asks for the pseudonym an EHR_STATUS subject carries, so identifying data stays outside the clinical record.

FerroTERM and FerroBRIDGE

Coded text is validated on a FHIR terminology server such as FerroTERM, and FHIR mapping and broker delivery live in FerroBRIDGE, a separate server.

FerroFED

The federation gateway sends each member CDR ordinary AQL scoped to its own EHR ids, and FerroEHR answers as a federation node.

The documentation

Four questions, four parts of the book

Operate

What does running it involve?

Installation and configuration, cluster hardening, security and audit, the viewer, and day-to-day operations.

Contribute

How is the work organised?

The tracker is the worklist, every check is a committed script you can run, and a change cites the specification section it implements.