v0.0.27 released

One bridge from openEHR to HL7 FHIR and to the OMOP Common Data Model.

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.

What it does

One mapping foundation behind every lane

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.

The operator console

See the mapping set a bridge runs, and try a draft

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 console's dashboard: the contexts loaded, the errors of the running load and the upstreams reachable, and the flow from the callers through the faces and the mapping set to the openEHR CDR, the terminology server and the OMOP CDM database.
The dashboard, drawn with synthetic data. Every page of the console, and the operator API behind it.
In the family

The product that maps openEHR outward

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.

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.

FerroTERM

The reference FHIR terminology server, asked for code systems and value sets through $lookup, $translate and $validate-code.

FerroPIX and FerroFED

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 documentation

Four questions, four parts of the book