HL7 interface engine
Helping systems that don't speak the same language communicate.
Upsilon receives HL7 messages from hospital systems — admissions and transfers, laboratories, pharmacy and other sources — and distributes them to one or more receiving systems.
It helps organize and track these exchanges according to the interfaces in place.
What Upsilon brings
-
Connect systems
Move HL7 messages between hospital systems and specialized applications.
-
Multiply destinations
A single feed can be distributed to several receiving systems.
-
Keep exchanges running
Queues, checks and recovery mechanisms suited to the configured interfaces.
Hospital message flows
One message received. Several systems informed.
Upsilon acts as an intermediary between the systems that produce information and those that need to receive it.
Incoming HL7 messages can be routed to several receivers, each using an interface and a delivery queue suited to its environment.
Incoming HL7 messages
-
Admissions and transfers (ADT)
-
Laboratories
-
Pharmacy
-
Other HL7 messages
Upsilon
Reception, queuing and routing
Receiving systems
-
Clinical applications
-
Specialized systems
-
Other authorized applications
Each receiver has its own delivery queue, so a single message can feed several systems.
Interoperability
Exchanges suited to your systems.
Hospital environments rely on different technologies to send and receive their information.
Upsilon makes it possible to set up interfaces suited to the systems involved, whether HL7 messages received over a socket, files or other communication mechanisms supported by the integration.
Delivery to receivers can also use different modes, depending on the needs.
Interfaces suited to the HL7 messages and structures of the systems involved.
One message, two delivery modes
Source system
Sends an HL7 message.
Upsilon
Receives the message and routes it to each receiver.
Output over a socket
Forwards the message to a receiving application over a network connection.
Output to a file
Depending on the configured interface, Upsilon can receive an HL7 message over a socket and write a file to a destination server instead of forwarding the data over another socket connection.
Depending on the configured interfaces.
Continuity of exchanges
Monitored flows, even when systems slow down.
Exchanges between systems depend on more than their initial connection.
Upsilon keeps track of messages received, waiting or delivered, as well as of its processes and certain error situations.
Its queuing, monitoring and recovery mechanisms help handle interruptions and slowdowns according to the configurations in place.
The path of a message
-
Message received
The HL7 message is recorded as soon as it arrives.
-
Waiting
It is placed in the queue of each receiver.
-
Delivered
The receiver's response confirms the delivery.
- Email alert when a delivery is delayed, depending on the configuration
- New attempt or reconnection after a failed delivery, depending on the configuration
-
Handling slowdowns
Messages can be queued for each receiver. Depending on the configuration, the sending order can favour the most recent messages when a system falls behind.
-
Monitoring and alerts
Checks can detect some stopped processes, stuck messages or errors and trigger email alerts, depending on the configuration.
-
Recovery mechanisms
Upsilon includes mechanisms for reconnecting, retrying and restarting certain processes.
Monitoring and recovery mechanisms depend on how the services are configured.
Expertise from the field
A technology built around concrete needs.
Upsilon draws on Semiweb's experience in hospital environments and in projects that require exchanges between hospital systems and applications.
This experience led to an interface engine able to meet a wide range of configurations and technical constraints.
A reusable technical foundation for specialized integration projects.