Triggers-Definitions – Vellox Group

Triggers have many items available and some warrant an explanation, you will find them outlined below.

Some of these items are only available starting in 6.9.0.0, If they aren’t available to you that is why.

Events

Add/Edit request turndown - These events will be based on the turndowns tab from a request.

Arrival at pickup - This event is anytime an asset arrives at the waypoint of a patient pickup.

Arrival with patient - This event is anytime an asset arrives at a waypoint with a patient onboard.

Asset approaches location - This event is anytime an asset approaches the location that is defined in the trigger ‘Conditions’.

Assign Asset - This event is when a user clicks OK on the Asset Assignment dialog.

Assign Asset (with overrides) - This event is when a user clicks OK on the Asset Assignment dialog. The queries for this trigger have access to the overrides (if any) that the user set. This will be triggered when the user selects to accept the overrides.

Assign patient to request (patient) -This event occurs when a user assigns a patient to a request from the patient or ‘Record Management’.

Assign patient to request (request) - This event occurs when a patient is assigned to a request from the request itself.

Checklist Completed - This event occurs when a checklist is completed.

Commit Patient - This event occurs when a user clicks ‘OK' or ‘Save and Continue’ on the patient dialog of a patient, whether it is the first time or tenth time.

Commit Patient Initially - This event occurs when a user clicks ‘OK' or ‘Save and Continue’ on the patient dialog of an unsaved patient.

Commit Request - This event occurs when a user clicks 'OK' or 'Save and Continue' on the request dialog of a saved request.

Commit Request Initially - This event occurs when a user clicks OK or Save and Continue on the request dialog of an unsaved request.

Departure with patient - This event occurs when an asset departs any waypoint with a patient onboard.

First departure - This event occurs on the first, initial departure of a request plan for any asset.

Notification created - This event occurs when a new notification (the red messages that appear in the notification window) is created. The queries for the trigger have access to the content of the notification.

OOS Event Advances 1% - This event occurs when an asset is out of service and has advanced 1% in the time that it is scheduled to be out of service.

Patient time added - This event occurs when a new timestamp is set for a patient. In addition to the standard patient fields, the queries for the trigger have access to the time's ID.

Reassign asset - This event occurs when an asset is reassigned from a request.

Request time added - This event occurs when a new timestamp is set for a request.

Set/unset conditional status - This event occurs when a ‘Conditional Status’ is set or unset for an asset.

Update waypoint - This event occurs when a waypoint is modified.

Redact Information

The administrator has the option to indicate that the trigger contains information that should be redacted for applicable users. If the Redacted box is checked for those user groups that have Patient Information set to Hidden in User Group permissions, the information in the trigger will be redacted for that user.

Actions

Add log message - This action will add a message to the log file.

Output Nemsis file - This action will send a NEMSIS file to the designated location.

Output RSQ911 file - This action will send information to RSQ911.

Output run report - This action will output a run report where designated.

Play a sound - This action will play an audio alert when the conditions of the trigger are satisfied. Note: a .wav is the only type of sound file that can be uploaded

Post notification - This action will post a notification with the trigger message in the notification window and on the appropriate ticket. When Post Notification is selected the Recipients, button will appear. The administrator will need to select which user groups the notification will appear for. Prior to selecting the ADD button, the administrator will need to create a message, see below.

Send out page - This action sends a page to the designated recipients. This is done silently, meaning the user will not see the page being sent and requires no action on their part.

Set patient/escort time - This action will set a patient or escort timestamp when the event is triggered.

Set request time - This action will set a request timestamp when the event is triggered.

Show pop up message - This action will display a pop-up window when the event is triggered. Users can set-up one of three pop-up types: Info, Error, or Warning. See examples of the set up below:

Warning Icon: