Skip to content
@FerroHEALTH

FerroHEALTH

Pure-Rust health-data servers built on open standards.

FerroHEALTH

Pure-Rust health-data servers built on open standards.

openEHR, HL7 FHIR, SNOMED CT, OMOP and IHE, in small servers with no JVM.
Each one runs on its own and works with the others.

Server What it does
FerroEHR openEHR clinical data repository
FerroTERM FHIR terminology server for SNOMED CT
FerroBRIDGE openEHR to HL7 FHIR and OMOP
FerroFED openEHR federation gateway
FerroPIX Master patient index over IHE PIX and PDQ
FerroSMART SMART App Launch authorization server, being built

Shared by every server
FerroUI console components · FerroAUDIT IHE audit trail

ferrohealth.eu · made by Cadasto B.V.

Pinned Loading

  1. FerroEHR FerroEHR Public

    A pure-Rust openEHR Clinical Data Repository: ITS-REST 1.1.0, AQL 1.1, PostgreSQL 18-native storage.

    Rust 68 5

  2. FerroTERM FerroTERM Public

    a pure-Rust, machine-generated multi-version FHIR terminology server for SNOMED CT. No JVM, no Elasticsearch.

    Rust 4 1

  3. FerroFED FerroFED Public

    A pure-Rust openEHR federation gateway: one AQL query in, standard AQL to every node, one answer out, after the openEHR Federation Tier with AQL proposal.

    Rust 1

  4. FerroBRIDGE FerroBRIDGE Public

    A pure-Rust bridge between openEHR and two interoperability targets: HL7 FHIR via the FHIRconnect specification, and the OMOP Common Data Model via OMOCL, over the openEHR ITS-REST API.

    Rust 1

  5. FerroPIX FerroPIX Public

    A pure-Rust Master Patient Index for the openEHR platform: cross-identifier resolution and record location over IHE PIX and PDQ.

    Rust 1 1

  6. FerroSMART FerroSMART Public

    FerroSMART: the SMART App Launch 2.2 authorization server of the FerroHEALTH products, for any OpenID Connect identity provider, and the ferrohealth-smart, ferrohealth-authz and ferrohealth-session…

    Rust 1

Repositories

Showing 10 of 14 repositories

Top languages

Loading…

Most used topics

Loading…