Secure, flexible integration with your EPR
The HL7 Bridge enables a secure connection between your hospital network and the EIDO cloud platform, hosted on AWS. It allows HL7 messages containing patient demographic data to be sent from your EPR to EIDO, where they are parsed and added to your organisation’s account.
Each customer has a dedicated HL7 listener instance. This ensures data isolation and security, and allows updates to be deployed to one customer without affecting others.
How it works
- An event in your EPR triggers the Trust Integration Engine (TIE) to send an HL7 message to EIDO.
- The HL7 listener receives the message, extracts the patient demographic data (PID segment), and adds the record to your EIDO account.
- Only the PID segment is required - no episode or patient history data is needed - making this a lightweight and flexible integration.
Event triggers
You choose which events in your EPR or TIE will trigger messages to EIDO. Common examples include:
- Patient admitted
- Added to clinic list
- Attended clinic
The trigger point should align with your clinical workflow and when consent is required.
Demographic updates
If a patient updates their contact details - such as during a clinic visit - this change should be sent to EIDO before the consent discussion. You can choose whether EIDO subscribes to a general update feed or only specific events.
Tailored to your system
Each HL7 listener is bespoke. It doesn’t matter which HL7 version you use (e.g. 2.5.1 or 2.8), or whether you have custom fields. Once your trigger events are defined, you’ll send a sample HL7 message with a PID segment. We’ll map each data point to the EIDO API (for example, PID5.1 → patient_first_name) and create a custom transformation recipe.
Implementation and go-live
During implementation, we’ll work with you in a sandbox environment. This allows both teams to test the integration, review the dashboard and demo the setup to stakeholders. Once everything is signed off, we’ll move to production and apply your final settings and workflows.