Alert Integrations

Minimum CorEMR Version: 6.0

CorEMR is capable of a bi-directional alert interface with a JMS system if both systems have been configured correctly to produce and consume alert messages. Alternatively, a JMS vendor can use the web service to add/update/remove alerts.

Each system, CorEMR & JMS need to agree on a pre-defined alert code map.

Alert Message Format

The message is in CSV format with seven elements.

Column	Field	Datatype	Required	Notes
1	Jacket Number / Permanent Number	String(50)	R
2	Booking Number	String(32)	R
3	Date Added	Datetime	R
4	Date Removed	Datetime
5	Alert Code	String(32)	R
6	Added User Id	Integer		If not provided, we will use CorEMR System.
7	Removed User Id	Integer		If not provided, we will use CorEMR System.

---

For example, each system has agreed that HIGHCAL is the High Calorie Diet.

The following examples contain messages to add, and then to remove the coded alert.

1234,202009181020,2020-09-01T10:00:00,,HIGHCAL,,

1234,202009181020,2020-09-01T10:00:00,2020-09-14T10:00:00,HIGHCAL,,

If users are not mapped and we're processing an incoming message, the system will default to use the CorEMR System user.