Feed HL7 patient updates to other systems
Goal: patient updates (ADT) from the EHR or RIS reach the PACS and an AI vendor, each edited the way it needs, in order, with nothing lost when a system is down.
1. Receive HL7
Section titled “1. Receive HL7”Turn on the HL7 port (Settings › HL7 and modality worklist), list the sender’s address, and point the EHR’s or interface engine’s ADT feed at the router, as in Build a modality worklist.
2. The destinations
Section titled “2. The destinations”Configuration › HL7 routing › Add HL7 destination, for each system: name, host and port, MLLP over TLS if it supports it, and When it refuses a message (AE): Stop until someone retries or skips it (the default, which keeps patient records in order), or put such messages aside and send the next.
3. The routes
Section titled “3. The routes”ADT to PACS: Message types ADT^A0*, ADT^A40, destination PACS, with edits:
| Path | Action | Value |
|---|---|---|
MSH-5 |
Set | PACS |
MSH-6 |
Set | RADIOLOGY |
ADT to AI vendor: Message types ADT^A08, a condition PV1-2 Equals O (outpatients only), destination
AI vendor, with edits that remove what the vendor must not have:
| Path | Action | Value |
|---|---|---|
PID-11 |
Clear | |
PID-13 |
Clear | |
NK1 |
Remove segment |
4. Test it
Section titled “4. Test it”Paste a real (or sample) message in Configuration › HL7 routing › Test and run it: you see which routes take it, and the exact copy each would send.
Check it
Section titled “Check it”History › HL7 messages shows each message received, and its state at each destination. If a destination refuses one, its queue stops (with an alert): open the message, fix the cause, then Retry now, or Skip it.
See HL7 routing.
