v0.0.34 released

Who the patient is, across every system that knows them.

FerroPIX is the Master Patient Index of the FerroHEALTH family, in pure Rust. Each hospital, practice and national register issues its own identifier for the same person. FerroPIX holds the cross-reference between them in PostgreSQL, answers for it over the IHE profiles your systems already speak, and mints the pseudonyms a clinical store names a patient by, so identifying data stays outside the clinical record.

A server image, an operator console image and a Helm chart on GHCR, built at SLSA Build Level 3, and the two identity crates on crates.io.

What it answers

One cross-reference behind every face

A feed over FHIR and a feed over HL7 v2 of the same patient land in one person, and every query reads the same store. Each transaction follows the IHE ITI Technical Framework and its implementation guide, on HL7 FHIR R4, and the book cites the section behind every answer.

The operator console

A data steward decides what the scorer is unsure of

An identifier in an authoritative domain links two records on its own, a probabilistic scorer grades the rest, and the pairs it is unsure of wait in a review queue. The console is where a steward compares them, links, merges and unmerges with a reason, and every reveal of an identifier is an audited disclosure.

The console's dashboard: the open review queue, the share of records linked automatically, the versions fed today, the subscriptions in error, and the queue depth and feeds per hour as charts.
The dashboard, drawn with synthetic data. Every page of the console, and how a pair is scored.
In the family

The one product that owns patient identity

The FerroHEALTH products reach each other only over published protocols. FerroPIX is where they ask who a patient is.

FerroEHR

With its PIXm subject index, the openEHR clinical data repository finds a patient's EHR through FerroPIX: the EHR_STATUS names the patient by the pseudonym FerroPIX minted for the clinical domain.

FerroFED

The federation gateway resolves the patients of a cross-site query through a PIXm Manager, and takes both identity crates from crates.io.

FerroBRIDGE and FerroTERM

The HL7 v2 face reads messages with FerroBRIDGE's parser and MLLP codec, and translates every v2 table value on a FHIR terminology server such as FerroTERM.

Building a client in Rust? Each IHE profile is a feature of ihe-iti, and each Dutch Generic Function a feature of nl-generic-functions, none on by default:

cargo add ihe-iti --no-default-features -F pixm
The documentation

Four questions, four parts of the book