Every connector carries its own audit trail: what was sent, when, to which destination, and with which payload mapping. Exportable on request.
ConneX Bridge
Validated results, delivered to every system that needs them.
Your results are validated in Core. Getting them into DHIS2, your LIS, your data warehouse: that is what Bridge does. One connector per destination, licensed individually, configured to your specific protocols. Tell us where the data has to go. We build the path.
What Bridge is
An integration layer, licensed one connector at a time.
Each connector targets a destination category and is licensed individually. Adding a destination becomes a configuration task, not a software project.
How Bridge works
From validated data to your destination.
Core validates and normalises the data. Bridge takes it from there. Each connector transforms the payload to match the destination's specific protocol and schema, routes it, and keeps a per-pipeline audit trail of everything sent, when, and to which system.
The connector is configured once by BAO Systems, mapped precisely to your protocols and destinations. Add a new destination later and the same process applies. There is no bespoke development cycle each time.
Destinations
- DHIS2 — DataSets and Tracker programs, segregated by country.
- EMR and EHR — FHIR-compliant endpoints, OpenMRS, Bahmni.
- LIS — HL7 v2 and v3, ASTM.
- Data warehouses — BigQuery, Redshift, Snowflake, Postgres.
- Custom APIs — REST and JSON over HTTPS.
Built in
Same portal as Link and Core. SSO, single permissions, single view.