Skip to main content
Skip table of contents

EMS Loop Version 3.0.28 Release Notes

RELEASE NOTES


We are happy to annouce that version 3.0.28 of EMS Loop has been released.  Below is the list of items that have been included in this release.  

 

Version - 3.0.28
 Release Date -
 
 
 

 

New Features

LV-69 Add Ordering Facility to trips

Add the ordering facility from the CAD. The ordering facility entered into the CAD will now be associated with the Trip in EMS Loop, currently the ordering facility information can be located in the trip detail.


LV-2657 Add export to excel on customer dashboard that allows the export of the Call Source Statistics area

The ability to export data from the Call Source Statistics area of the Overview Dashboard has been added. Look for the Excel icon in the upper right hand corner of the Call Source Statistics area.


LV-2660 Add Geo Informatics Reporting section

A new reporting section of Geo Informatics has been added to the reports section.


LV-2661 Add Trip Tracker for Geo Informatics Reporting

A new report “Trip Tracker” has been added to Geo Informatics. This report shows the driven route that was taken from En Route to At Destination overlaid on a map, with trip information.



Improvements

LV-62 Eliminate storing of GPS data when the last GPS data point recorded is the same.

The system now only records incoming GPS data if the device has moved more than 15 meters. If the device sends in data without moving more than 15 meters the last updated time is reset to the current time but the GPS data is not saved.


LV-2634 Add Excel export to Facility Transport Count reports.

The ability to export Facility Transport count reports to Excel has been added.


LV-2650 Calculate and display responses on new dashboard.

On the Overview dashboard, responses have been added as a statistic. Responses are defined as a trip where a vehicle went En Route but did not transport.



Bugs

LV-2630 UHU Calculations on the shift grid are wrong in some cases

Shift UHU numbers were being calculated using all responses instead of calls that were transported. This was calculating the UHU number incorrectly. The UHU number for each shift is now being calculated using the number of trips that were transported ie: completed for the shift.


 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.