Almost everything that happens in Noah will result in an event being sent to all clients.

Noah ES supports two different types of Event Integrations: Real Time Messaging (RTM) and Webhooks.

See an example of the implementation of RTM and Webhooks in the Sample App: https://himsanoah.atlassian.net/wiki/spaces/AD/pages/3200450830

Real-Time Messaging (RTM)

This implementation is based on SignalR, which is making use of different technologies depending on operating systems, firewall setups etc.

Please see more here: https://himsanoah.atlassian.net/wiki/spaces/AD/pages/1275625591

Webhooks

Please see more here: https://himsanoah.atlassian.net/wiki/spaces/AD/pages/1275625605

Selecting the type of event integration

The table below highlights some of the differences between RTM and Webhooks

	Real Time Messaging (RTM)	Webhooks

	Real Time Messaging (RTM)	Webhooks
No changes to firewall setups required	X _{Usually not, since the client initiates the connection}
Low latency (“real time”)	X
No need to deal with skipped events during transient disconnects	_{But SignalR tries to re-connect to some extent}	X
No risk of skipping events during high load	_{Can be an issue in SignalR when queue grows too big}	X
Easy catch up after downtime _{App does not need to be running always}		X
Always encrypted	_{Note that events mostly contains ids, and never patient data.}	X
No HTTPS setup required	X

Subscribing to event types

You can set up events via the API.

Important!:
Your Request URL might receive many events and requests. Consider decoupling your ingestion of events from the processing and reaction to them.