Go-live timeline
A typical 5-branch hospital chain deployment from contract to production monitoring takes 9–12 weeks.
Phase overview
| Phase | Weeks | Deliverable |
|---|---|---|
| Infrastructure & config | 1–2 | Kubernetes, firewall rules, BridgeConfig |
| First branch pilot | 3–4 | Branch 01 connected, ADT smoke tests |
| ORU + pharmacy | 5–6 | Lab results, LOINC mapping, JamGuard |
| Remaining branches | 7–8 | Branches 02–05, cross-branch IPS testing |
| Production + monitoring | 9+ | Grafana, Prometheus, DHIS2 |
Week-by-week
Weeks 1–2: Infrastructure
- Kubernetes cluster provisioned (or Docker Compose for single-server)
- JamBridge Helm chart deployed
- HAPI FHIR, JamMPI, AJ Consent, PostgreSQL running
- MLLP port firewall rules opened per branch
BridgeConfig.yamlconfigured with facility codes- JamMPI national ID field mapping confirmed for target country
Weeks 3–4: Branch 01 pilot
- Branch 01 HIS configured to send MLLP to JamBridge :2575
- ADT A01/A03/A08 message smoke tests with real patient data (synthetic)
- Golden record validation — confirm correct matching grade for national ID
- ATNA audit trail reviewed — confirm all events present
- Consent policy seeded in AJ Consent Manager
Weeks 5–6: ORU + pharmacy
- Branch 01 ORU^R01 lab results on :2576
- Local lab code → LOINC mapping configured in JamTS
- JamGuard DDI rule configuration and NLM API key
- Branch 01 RDE^O11 pharmacy prescriptions on :2580
- Cross-branch DDI smoke test (requires Branch 03 data)
Weeks 7–8: Remaining branches
- Branches 02–05 MLLP connections
- HIS vendor-specific HL7v2 edge cases resolved
- Cross-branch IPS tested: clinician sees combined record from all branches
- Clinician portal SMART App Launch tested
- JamReferral cross-branch referral tested BR01 → BR05
Week 9+: Production and monitoring
- Grafana dashboard: transaction volume, pipeline stage durations, error rates
- Prometheus alerting: circuit breaker state, queue depth, consent failure rate
- DHIS2 surveillance pipeline validated (if applicable)
- JamDHIW population health dashboards seeded
- Runbook documented for on-call team
HIS vendor-specific notes
| HIS | Known edge cases |
|---|---|
| Epic | PID-3 may carry multiple identifiers — confirm national ID CX.4 domain |
| Cerner | ADT A28/A31 (pre-admit update) needs mapping to A08 |
| MEDITECH | MSH-9.3 MessageStructure field sometimes missing — JamBridge handles this |
| Bahmni | OpenMRS HL7 MLLP module required; PV1-3 location format differs |