GroupAlarm can connect to various interfaces via different flow triggers, e.g. websocket connections, IMAP mailboxes, WDX-3 of the ISE Cobra and more. If several flows access the same resources for different tasks, the connection data previously had to be entered multiple times. Furthermore, there was no monitoring of the connection status. With the introduction of the connection manager, we are solving these problems.

Connections can now be created via ‘Admin -> Connections’ – starting with the WDX3 interface – which can then be evaluated using flows. At least one flow trigger is available for each connection. This means that the connections only need to be created once and, for a better overview, they also have a corresponding status and can be paused.

The live view of the incoming data provides additional control over the transferred values and makes it easier to create the subsequent flows.

We will migrate existing interfaces from the flow to the connections in the future as well as adding further protocols.

Trigger ‘Connection Status’

The new flow trigger ‘Connection status change’ makes it possible to monitor the connections and, if necessary, generate messages/alarms if a connection unexpectedly changes status and, for example, alarms can no longer be triggered via the interface. This monitoring reports problems independently of missing alarms and ensures more secure connections.

WDX3 Connection

Further improvements have also been incorporated for the WDX3 interface. The Operation service bundles the data from the resource and patient service so that all data is available for an alarm. This makes it possible to alert a list of the involved resource IDs directly via the external IDs in GroupAlarm. Furthermore, the resource trigger can be used to set position and status.