JamBridge
v1.0 · Spring Boot 3.3 · Apache Camel 4 · Java 21 · Commercial
JamBridge is the HL7v2-to-FHIR R4 integration gateway at the centre of the Jam clinical data platform. It sits between your existing hospital information systems — Epic, Cerner, MEDITECH, or any HIS that speaks HL7v2 — and a FHIR R4 data store, translating decades of HL7v2 message traffic into modern, queryable, consent-governed FHIR resources in real time.
It runs on port 8443 and opens eight MLLP listeners on ports :2575–:2582.
What it does
Hospital HIS JamBridge :8443 HAPI FHIR :8080
│ │ │
│── ADT^A01 ──── MLLP :2575 ──►│ │
│ │ 1. RECEIVE (parse+dedup) │
│ │ 2. ENRICH ──► JamMPI │
│ │ 3. TRANSFORM ──► JamTS │
│ │ 4. GOVERN ──► AJ Consent │
│ │ 5. PERSIST ─────────────►│
│ │ 6. DISPATCH ──► JamConnect │
│◄── MSA|AA ────────────────────│ 7. ACK + ATNA audit │
Every message enters the same 7-stage pipeline. The stages are sequential and non-configurable — see Why non-configurable? below.
What it is not
JamBridge does not route arbitrary messages between systems. It does not have a drag-and-drop route builder. It does not accept arbitrary mediator plugins. It is a clinical integration engine — it understands the semantics of HL7v2 messages and applies a fixed, ordered pipeline that cannot be rearranged.
If your integration needs are primarily routing HL7v2 messages between systems without FHIR transformation, see JamBridge vs OpenHIM and JamBridge vs Mirth for an honest assessment of when those tools are the right choice.
Why non-configurable?
The pipeline stages are in a specific order because clinical safety requires it:
- Consent must be checked before data is written. A configurable pipeline is one where an operator could accidentally place PERSIST before GOVERN, writing patient data without a consent check.
- Identity must be resolved before transformation. The FHIR Patient resource cannot carry a golden record link until the MPI has matched the patient.
- Terminology must be translated before persistence. An Observation with a local lab code instead of LOINC is not queryable by any downstream FHIR consumer.
A configurable pipeline is a pipeline where someone can make a clinically unsafe configuration.
Open source foundation
Every component JamBridge depends on is open source. You can audit the entire infrastructure before signing a commercial contract.
| Component | Licence | Role |
|---|---|---|
| HAPI FHIR JPA | Apache 2.0 | FHIR R4 data store |
| JamMPI (AJ MPI) | Apache 2.0 | Master patient index |
| AJ Auth Server | Apache 2.0 | SMART App Launch v2.2 |
| AJ Consent Manager | Apache 2.0 | FHIR Consent lifecycle |
| JamFR | Apache 2.0 | Facility registry |
| JamReferral | Apache 2.0 | Cross-branch referrals |
| JamBridge | Commercial | Integration engine |
| JamTS | Commercial | Terminology service |
| JamGuard | Commercial | Clinical safety rules |
Full open source platform: open.akhester.com
Who it is for
- Hospital chains connecting 3–50 branches through a central HIE
- National health programmes replacing OpenHIM or Mirth Connect mediator stacks
- Digital health integrators needing production-grade HL7v2-to-FHIR transformation with consent and audit already in the pipeline
Next steps
- Quick Start → — get JamBridge running in 10 minutes
- Architecture overview → — how it all fits together
- The 7-stage pipeline → — deep dive into what happens to each message