Akhester Platform documentation — AJ FHIR (Apache 2.0) + Jam commercial products. Browse all products →
JamMPI v1.0 · Apache 2.0 · Port 8081
Master Patient Index for hospital chains.
JamMPI resolves every patient to a single golden record across all connected facilities. Probabilistic matching at 50M records. IHE PDQm, PIXm, and PMIR conformant. Apache 2.0 — free to use in any environment.
IHE conformant:ITI-78 PDQmITI-83 PIXmITI-93 PMIRITI-119 $match
What JamMPI does
Patient identity resolution at the core of every clinical workflow.
🔍
Probabilistic matching
Jaro-Winkler name + DOB scoring combined with national ID exact match. Three strategies run in combination on every $match call.
🔗
Golden records
One canonical FHIR Patient per person across all facilities. Every branch MRN linked via Patient.link[seealso]. The golden ID follows the patient everywhere.
⚡
Sub-100ms at 50M records
Blocking strategy pre-filters candidates by family name prefix + birth year — O(~500) comparisons, not O(50M). Cached facility resolution adds ~5ms.
🏥
IHE conformant
ITI-78 PDQm, ITI-83 PIXm, ITI-93 PMIR, and ITI-119 PIXm $match. Drop-in replacement for any PMIR-conformant MPI.
🆓
Apache 2.0
Free to use in any environment, commercial or otherwise. Community support via GitHub. Commercial support contracts available from Akhester.
🔄
JamBridge integrated
Every HL7v2 message processed by JamBridge automatically calls $match. No configuration needed — enrichment happens in Stage 2 of the pipeline.
Quick start
JamMPI runs as a Spring Boot service. It requires a PostgreSQL database and exposes a FHIR R4 REST API on port 8081.