v0.4.7 released

A FHIR terminology server for SNOMED CT, LOINC, ICD and every FHIR code system, on ordinary hardware.

FerroTERM serves the HL7 FHIR terminology API on R4, R4B, R5 and the R6 ballot from one binary over an index built once per release and read at startup. No JVM, no search cluster. You bring the release you are licensed for; the build tool turns it into an index; the server answers from it.

A server image and a console image on GHCR and the ferroterm and ferroterm-build binaries for Linux, built at SLSA Build Level 3, and the release readers and the terminology engine on crates.io.

What it answers

One seam, many code systems

Every code system reaches the FHIR operations through the same provider seam, so nothing in an operation is a special case for one system.

SNOMED CT, LOINC, UCUM, BCP 47, BCP 13, ISO 3166-1, ICD-10 (WHO), ICD-10-NL, ICD-10-CM, ICD-11 MMS, ICD-11 ICF, ICD-11 Foundation, ATC/DDD, ICPC-2, RxNorm, the DHD Diagnosethesaurus and Verrichtingenthesaurus, the G-Standaard, the Nederlandse Labcodeset, the NHG ICPC-1 to SNOMED CT map, and any FHIR CodeSystem, ValueSet, and ConceptMap resources. The code systems page lists each with its URI, versions, build command, and licence.

Measured, never typed

What each code system costs to run, and how fast it answers

Every figure below comes from a benchmark record committed to the repository; a check fails when the page and the records disagree. The benchmarks page has every operation, the cold and tail latencies, the method, and how to take a record yourself.

Warm p50 over 200 HTTP round trips on one machine (Apple M2, 17.18 GB, macos/aarch64), FerroTERM 0.1.4 serving FHIR R4B, taken 2026-09-22. Every tile links to its record.

The console

Browse, look up, expand and translate

The console is its own program and image, ferroterm-console, beside the server. It reaches the server over the public FHIR API, so anything it does any FHIR client can do, and it edits the resources your deployment writes.

The console's dashboard: what the deployment serves, its code systems, value sets and concept maps.
The dashboard. Every page of the console.
In the family

The product that serves the code systems

The FerroHEALTH products reach each other only over published protocols, and any FHIR client can use FerroTERM. These are the family's.

FerroEHR

The openEHR CDR validates the coded text of a composition against its terminology bindings through a FHIR terminology server.

FerroBRIDGE

The bridge asks for code systems and value sets through $lookup, $translate and $validate-code while it maps openEHR to FHIR.

FerroPIX

The patient index translates every HL7 v2 table value of its v2 face on a FHIR terminology server.

The documentation

Four questions, four parts of the book

Evaluate

Does it fit my problem?

What it serves and how well, how it compares to the reference servers on the same machine, conformance per FHIR version, and the licence.