Jam ecosystem
JamBridge is one component in a coordinated platform of 10+ products. Each is independently deployable — you can add components progressively as your needs grow.
Platform map
| Product | Port | Licence | Role |
|---|---|---|---|
| JamBridge | 8443 / 2575–2582 | Commercial | HL7v2-to-FHIR integration engine |
| JamConnect | 8091 | Commercial | Clinical intelligence facade + CDS |
| JamMPI | 8081 | Apache 2.0 | Master patient index (golden records) |
| JamFR | 8089 | Apache 2.0 | Facility registry (mCSD ITI-90) |
| AJ Consent Manager | 8082 | Apache 2.0 | FHIR R4 Consent enforcement |
| AJ Auth Server | 9000 | Apache 2.0 | SMART App Launch v2.2 |
| JamSHR | 8084 | Commercial | Shared health record (IPS) |
| JamTS | 8085 | Commercial | Terminology service (LOINC, SNOMED) |
| JamGuard | 8094 | Commercial | Cross-branch clinical safety |
| JamReferral | 8093 | Apache 2.0 | Cross-branch referral state machine |
| JamDHIW | 8086 | Commercial | Analytics + DHIS2 surveillance |
| JamPHR | 8087 | Commercial | Patient-facing health record portal |
Integration points
All integration between Jam components uses standard FHIR R4 operations or documented REST APIs — nothing proprietary. You can replace any component with a standards-conformant alternative.
For example: if you already have an ITI-119 conformant MPI, point mpi.url in BridgeConfig.yaml at it. JamBridge will use your MPI instead of JamMPI.