BridgeConfig YAML guide
BridgeConfig.yaml is the single configuration file for JamBridge. It is country-agnostic — the same structure works for a single hospital or a 50-branch national HIE.
Facility code mapping
The facility-code in BridgeConfig.yaml is the fallback used when JamBridge cannot resolve an MSH-4 code from the JamFR facility registry. In most deployments, auto-provision: true handles unknown facility codes automatically by creating a new FHIR Organization on first message.
Multi-branch example
For a hospital chain deployment, each branch typically runs its own HIS pointing to the central JamBridge. JamBridge uses the MSH-4 field to identify the source:
MSH|^~\&|HHIMS|BRANCH-01|JAMBRIDGE|CHAIN|...
JamFR resolves BRANCH-01 to Organization/org-br01-001. No per-branch config change is needed in JamBridge — the facility registry handles the mapping.
National ID field mapping
The MPI match quality depends on providing a national identity number when available. Configure which PID field carries the national ID:
mpi:
national-id-field: PID-3.1 # default
national-id-system: urn:national.nic
| Country | Common field | System URI |
|---|---|---|
| India | PID-3 (Aadhaar) | urn:in.aadhaar |
| Sri Lanka | PID-3 (NIC) | urn:lk.nic |
| UK | PID-3 (NHS) | https://fhir.nhs.uk/Id/nhs-number |
| Kenya | PID-3 (National ID) | urn:ke.nationalid |
DHIS2 surveillance mapping
When a notifiable LOINC code appears in an ORU message, JamBridge pushes a data value to DHIS2. The program and data element mapping is defined in a separate file:
dhis2:
mapping-file: dhis2-loinc-map.yaml
mappings:
- loinc: "80823-7"
dhis2-program: DENGUE_SURVEILLANCE
dhis2-data-element: DE_DENGUE_NS1
- loinc: "32700-2"
dhis2-program: MALARIA_SURVEILLANCE
dhis2-data-element: DE_MALARIA_RDT