5.11.12 Release Notes

For the generic ASCII, Tritech XML, Intergraph, and ESO EHR interfaces, FH CAD Monitor now lets you specify a directory where unprocessed data files are sent if they contain invalid data that cause an ODBCOpen Database Connectivity error.

When you specify this directory, FH CAD Monitor can continue processing the rest of the incoming data files instead of completely stopping the import process. You can then examine the file with the invalid data at your convenience and make the appropriate corrections to the data, so the file can be processed and imported.

To find the field for specifying the directory: 

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the Database tab.

   In the Text Files section, the new Unprocessed files directory (files that caused ODBC execution error) appears.

   

 

[FHD-2229, FHD-2233, FHD-2232, FHD-2231, FHD-2230]

For the ESO EHR interface, FH CAD Monitor now lets you specify which fields in FH that you do not want updated if they already contain a value. This prevents overwriting data sent earlier from another CAD system, which has already been imported into FH.

To find the button for specifying which fields to not overwrite:

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the Filters & Data tab.

   In the Don't Overwrite Field section, the new Don't Overwrite button appears.

   

   Information on this button and specifying fields to not-overwrite is available in Specify which fields to not overwrite.

 

[FHD-2216, FHD-2205]

For the Intergraph interface, FH CAD Monitor now lets you determine whether or not only the final closed-call files should update the incident narrative. If you select this option, only files that contain the file name inc_3 update the incident narrative.

To find the option for indicating whether or not to use closed-call files to update the incident narrative:

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the System2 tab.

   The new Allow only incident file containing ‘inc_3’ to update narrative option appears in the upper right corner of the tab.

   

 

[FHD-2175]

For the generic XML interface, FH CAD Monitor now lets you import EMSEmergency Medical Services calls into the fire NFIRSNational Fire Incident Reporting System Incident module and create fire incident records instead of EMS records.

To find the option for creating fire incident records instead of EMS records:

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the System2 tab.

   The new Treat EMS calls as Fire calls during import (Only to NFIRS Incidents) option appears in the middle of the tab.

   

 

[FHD-2088]

For the VisiCAD (TriTech) XML interface, FH CAD Monitor now supports record-level auditing for the Aid Given and Aid Received fields.

 

[FHD-1096]

The FH Net product has been retired from the FIREHOUSE Software product suite, and all FH Net customers have been migrated to software packages that better serve their needs. As part of the FH Net retirement process, FH CAD Monitor no longer supports data import from FH Net, and references to FH Net in the FH CAD Monitor interface have been removed.

 

[FHD-765]

You can now use the notified date and time of the first unit notified as the alarm date and time for the incident, by entering custom SQL expressions as a field mappings for the Alarm Date and Alarm Time fields.

The custom expressions are:

Alarm DateQueryCADCursorFieldValue("TOP 1 UNIT_FLD_9", "CAD_UNITS", "cad_incidents.text_id = text_id", "UNIT_FLD_9, UNIT_FLD_10")

Alarm TimeQueryCADCursorFieldValue("TOP 1 UNIT_FLD_10", "CAD_UNITS", "cad_incidents.text_id =text_id", "UNIT_FLD_9, UNIT_FLD_10")

To implement the expressions:

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the Filters & Data tab.

3. In the Field Mapping section, click Field Mapping.

   The Field Mapping dialog box appears.

4. In the Alarm Date row, in the Maps to CAD Data Element column, click the cell and choose Specify a literal value or expression from the menu that appears.

   The Specify Literal Value or Expression dialog box appears.

5. In the text area of the dialog box, type the following expression to map the first-notified unit's date to the incident alarm date.

   Alarm DateQueryCADCursorFieldValue("TOP 1 UNIT_FLD_9", "CAD_UNITS", "cad_incidents.text_id = text_id", "UNIT_FLD_9, UNIT_FLD_10")

6. Click OK.

7. In the Alarm Time row, in the Maps to CAD Data Element column, click the cell and choose Specify a literal value or expression from the menu that appears.

   The Specify Literal Value or Expression dialog box appears again.

8. In the text area of the dialog box, type the following expression to map the first-notified unit's time to the incident alarm time.

   Alarm TimeQueryCADCursorFieldValue("TOP 1 UNIT_FLD_10", "CAD_UNITS", "cad_incidents.text_id =text_id", "UNIT_FLD_9, UNIT_FLD_10")

9. Click OK.

 

[FHD-597]

When FH CAD Monitor sent data to ESO's EHR module, if the location address was an intersection, only part of the address imported.

 

[FHD-2234]

If the unit codes for different units were very similar (example: two units with the respective codes C33 and C3), FH CAD Monitor did not always differentiate between them correctly, and sometimes overwrote the data from one unit with data from the other unit.

 

[FHD-2174]

If a CAD data file indicated that all units were sent as mutual aid for an incident, when the data was imported into FH, some of the unit records indicated that mutual aid was received instead of given.

 

[FHD-805]

In the FIREHOUSE Software CAD Monitor Options dialog box, on the Filters & Data tab, when you click Code Conversions, a dialog box appears.

For the VisiCAD (TriTech) XML, generic ASCII, generic XML, ESO EHR interfaces, when you clicked the Show Code Conversions for Lookup Category menu, the Street Prefix and Street Suffix options were not available, and should have been.

 

[FHD-490]

In the generic XML XSD file, the node name MutualAid was misspelled as MutialAid.

Note: While the node name is now spelled correctly, FH CAD Monitor will still accept data files with the misspelled node name, to prevent backward-compatibility issues.

 

[FHD- 60]