FerroEHR
The reference openEHR CDR. The bridge reaches it over ITS-REST 1.1.0 like any other client, so it runs against a CDR it did not build.
FerroBRIDGE reads FHIRconnect and OMOCL mapping files and runs them against any openEHR CDR it reaches over the ITS-REST API. Mappings are specification-conformant YAML validated against published schemas, so nothing is hand-coded per FHIR resource or per OMOP table.
A server image and an operator console image on GHCR and the
ferrobridge binary for Linux, built at SLSA Build Level
3, and the mapping and FHIR crates on crates.io.
FHIRconnect and OMOCL share a header, a YAML loader, a mapping registry and the openEHR path model. Each language keeps its own parser, validator and interpreter, and every lane below runs the mapping files you load.
A FHIR client sees one FHIR server, and every request becomes CDR operations driven by the mappings: read, vread, create, update, search, transaction and batch. The facade stores no clinical data of its own.
OMOCL 1.0.0 into CDM v5.4A batch job over AQL turns each composition into typed rows of an OMOP CDM v5.4 database, and resolves every concept by SQL over the OHDSI vocabulary you loaded.
Specification-conformant YAML
Model, extension and context files, each checked against its
published schema at load. ferrobridge mapping check
checks a tree without serving it, and the operator API reloads a
running bridge.
The two operations the FHIRconnect specification defines for its engine, as pure transformations: neither reaches a CDR, so a facade, a test harness or a shell can call them.
HL7 v2 over MLLPEach message becomes an R4 Bundle through the ConceptMaps of the HL7 v2-to-FHIR implementation guide and reaches the CDR through the facade's ingest service, acknowledged once the CDR commits or refuses it.
EHDS, Regulation (EU) 2025/327
The eehrxf crate builds and receives the European
exchange format in FHIR R4: prescriptions and dispensations,
laboratory, imaging and discharge reports, mapped from openEHR
through FHIRconnect.
The console is its own server, reached over the bridge's operator API. It shows the loaded mappings and their diagnostics, edits a draft and checks it before the bridge reloads, and runs a mapping against a sample in the playground.
The bridge is one static binary on a distroless base. It needs an openEHR CDR over ITS-REST, a FHIR terminology server and, for the OMOP side, a CDM v5.4 database with the OHDSI vocabulary loaded.
compose.yaml ships with every release. Create the
secret files beside it and docker compose up; the
cdm profiles add PostgreSQL and the
console profile adds the console.
ghcr.io/ferrohealth/ferrobridge and
ghcr.io/ferrohealth/ferrobridge-console, for amd64
and arm64, each with SLSA provenance and an SBOM you verify
before you run it.
The CDR, the terminology server and the CDM database it reaches, the probes an orchestrator reads, and how the bridge behaves when one of them fails.
The FerroHEALTH products reach each other only over published protocols. FerroBRIDGE is where openEHR content becomes FHIR and OMOP, and its parsers and mapping crates serve the others.
The reference openEHR CDR. The bridge reaches it over ITS-REST 1.1.0 like any other client, so it runs against a CDR it did not build.
The reference FHIR terminology server, asked for code systems
and value sets through $lookup,
$translate and $validate-code.
The patient index reads HL7 v2 with the bridge's parser and MLLP
codec, and the federation gateway serves the documents the
eehrxf crate builds.
Building on the mapping languages in Rust? The FHIRconnect
language is the
fhirconnect
crate, and the FHIR model it writes is
fhir-types:
cargo add fhirconnect
The design as decided, the two mapping languages it reads, the version pins and why each one is what it is, and the licence.
A FHIR R4 facade on one side, a batch ETL into the CDM on the other, and the mapping files that drive both.
Every configuration key, the images and compose, the access record, the console, and the failure behaviour you should know before you run it.
The tracker is the worklist, every check is a committed script you can run, and a change cites the specification section it implements.