Pure-Rust health-data servers built on open standards.
FerroCHART · FerroEHR · FerroTERM · FerroBRIDGE · FerroFED
Pure-Rust health-data servers built on open standards.
FerroCHART · FerroEHR · FerroTERM · FerroBRIDGE · FerroFED
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.
A pure-Rust openEHR Clinical Data Repository: ITS-REST 1.1.0, AQL 1.1, PostgreSQL 18-native storage.
a pure-Rust, machine-generated multi-version FHIR terminology server for SNOMED CT. No JVM, no Elasticsearch.
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.
The shared SMART and OAuth 2.0 resource-server crate for every FerroHEALTH product: token validation against the authorization server's keys, SMART v2 scopes and the patient compartment, Basic and client-credentials machine auth, and the audit line.
The shared UI component library of the FerroHEALTH consoles: Leptos components, role tokens and one table model, used by FerroBRIDGE, FerroFED, FerroEHR and FerroTERM.
A pure-Rust openEHR form builder and renderer: operational templates in, forms out, validated compositions into any openEHR CDR
A pure-Rust Master Patient Index for the openEHR platform: cross-identifier resolution and record location over IHE PIX and PDQ.
A pure-Rust control plane for the FerroHEALTH family: health, telemetry, the event log, notification subscriptions, configuration and deployment.
This organization has no public members. You must be a member to see who’s a part of this organization.
Loading…
Loading…