7.6.5 Release Notes

These Release Notes are for Firehouse® release 7.6.5, and provide a listing of the defects resolved and the enhancements implemented during this release. The changes listed in the Release Notes apply to both FH™ Standard and Enterprise editions.

Creating a conditional requirement for the Occupancy/Inspection Signature form, the conditional statement verifies successfully. However, you open when the signature capture form, the following error message appears:

Error evaluating signature form requirement condition "Inspectionrecord.Completed>={^2010/01/21}  Error 13 (Alias 'INSPECTIONRECORD'is not found)”

Pennsylvania requires the Member Making Report field (E23_10) for all incidents. The FIREHOUSE Software EMS Incident design collects the Member Making Report data in the patient record. A user cannot fill out this field on a “No Patient” EMS record. As the incident record is now validated on saving the record, the record fails immediate validation.

The issue has been resolved.

The NEMSIS Patient Export will export -20(Not Recorded) when the value is not populated.

Values in some recently added NEMSIS reporting fields were not being saved when a memorized template was created. The following fields were being omitted: 

  • Weight Kg
  • Drivers License # / Issue State
  • Next of Kin data fields
  • Employment fields
  • Primary Role of Unit
  • Odometer Readings

When saving an EMS Patient record where the patient has a procedure record and assisting staff noted on that procedure, the following error message appears: 

"ThisForm.InciSession.validAssistingStaff("CHECKED and STAFF_ID="' + STAFF_ID + "'and PROC_ID= "'+ PROC_ID +"") for
Table : EMS_PROC
Field : STAFF_ID
Type: Define field error condition
The error was 107 - Operator/operand type mismatch”

When using a system with the Pennsylvania NEMSIS code set installed, the user added values in the lookup table for the Member Making Report user field. Those values were lost when the system updates.

The issue has been resolved.

The lookup category is marked to ‘force merge’ as the NemsisPA2.FHz is installed.

Clients reported the auto-numbering of permit numbers would not number correctly after updating the software. When updating FH software, the Occupancy Permit Numbers key within the database reset to zero. The Next Permit Number for the auto-numbering feature must remain consistent through an update so that the numbers for permits remain sequential.

With an occupancy record open in the Occupancy module, Error 1960: Illegal redefinition of variable CACCT_ID. at line 18 of procedure/method QRY.QRYSESSION.INITPARAMVAR may appear when you click Add under the Account(s) Responsible for Payment section on the Owners & Contacts tab.

In the Inventory module, on the Basic tab, in the Last Maintenance/Test section, the data was not displaying correctly. Information from the top-most record on the Maintenance/Test tab, in the Maintenance section, should be displayed. The Last Meter Reading Date, Mileage, and Hours should come from the most recent Usage or Maintenance record, regardless of the sort order on the grids. The Last Maintenance/Test fields on the Basic tab should similarly come from the most recent maintenance record, regardless of the sort order on the maintenance grid.

An Error 12 “Variable ‘UNIT is not found’” appears when performing a scheduling exchange in the Schedule Module. The error occurs when reassigning a staff member to another station when the unit field is empty. This only occurs if there were previously approved reassignments with empty unit fields.

Invoice numbers were being skipped after completing a batch invoice generation for occupancy inspections.

The issue has been resolved.

New invoice numbers are now only generated during batch invoice generation when one of the following is true:

  • If a pending invoice already exists for the account, add items to that invoice is not checked.
  • If a pending invoice already exists for the account, add items to that invoice is selected and no pending invoices are found.

The ability to edit inspection records synced from FH Mobile has been added to the Administrative Options dialog box.

  1. To find this enhancement, choose Administration → Administrative Options.

    The Administrative Options dialog box appears.

  2. Click Occupancy tab → Inspections tab.

    Additional tabs appear in the Administrative Options dialog box as you click each tab.

    Allow Inspection Data from Mobile to be edited can be checked or cleared to allow inspection data synchronized from FH Mobile to be edited on the desktop after synchronizing the mobile database with the local database.

The ability to run XML validation on each incident has been added to the Administrative Options dialog box. To find this enhancement in FH, do the following:

  1. Choose Administration → Administrative Options.

    The Administrative Options dialog box appears.

  2. Click the Incident tab → EMS/Search & Rescue tab → Nemsis tab.

    Additional tabs appear in the Administrative Options dialog box as you click each tab.

    The Run XML Validation on Each Incident section of the Nemsis tab controls per-incident NEMSIS validation. This section contains the options Always, Until ## Incidents have validated successfully, or Never.

    Tip: While validating each incident can extend the time it takes for the software to save each incident, it is much easier to correct problems if they are found during data entry. XML validation will always be run on the complete NEMSIS export.

    Note: NEMSIS-based administrative options were also moved to this tab from the State Reporting tab.

The following codes were added to the FIPS county list to satisfy the requirement that the user be able to map local county codes to the following NEMSIS null values:

  • -25 Not Applicable
  • -10 Not Known
  • -5 Not Available

The following files have been updated and are in the State folder:

  • NemsisAK2.FHz
  • NemsisAK.FHz
  • NemsisDemographicExport.FHz
  • NemsisMA.FHz
  • NemsisME.FHz
  • NemsisME2.FHz
  • NemsisMI.FHz
  • NemsisMI2.FHz
  • NemsisMO.FHz
  • NemsisNM.FHz
  • NemsisNM2.FHz
  • NemsisPatientExport.FHz
  • NemsisWA.FHz
  • NemsisWI.FHz
  • NemsisWI2.FHz

The MA XSD file (MAEMSDataSet.xsd) has been updated to contain standard code used for NEMSIS export, so that it does not allow for export of Image Trend data.

A Resident option and two new shortcut buttons to the Loss & Value Report or Vehicle Accident/Extrication dialog box were added to the Incident module. To find these new buttons and option in FH, do the following:

  1. Open a record in the Incident module, using the NFIRS Incident Report dialog box.

  2. On the Property & Involvement tab, in the Persons/Entities Involved section, select a record and click Open.

    The Involvement dialog box appears, set to the Basic tab. In the Primary Involvement Type section, the new Resident option and two shortcut buttons (Insurance and Vehicle Info) appear.

  3. (Optional) Click Insurance or Vehicle Info.

    The Loss & Value Report or Vehicle Accident/Extrication dialog box appears.

In the Remote Configuration window, you can now use the Connect Using field to connect to an ODBC data source. When you select ODBC Date Source Name, the name of the default database appears and is not editable. If you select ODBC DSN, you can enter the name of the database. If you enter a database name that is not mapped to the data source, the message Database chosen is not mapped to selected ODBC DSN appears.

The CountAnyMappedInLinkedList() function has been added to FH. This function is similar to CountAnyMappedInList(), but intended to handle NEMSIS rules for linked lists, such as user fields or staff fields on Personnel and/or Units screens. The parameters are:

  • cList
  • cField
  • cCategory
  • cLinkFromField
  • cLinkToTable
  • vVal1, vVal2, ...., vVal24.

Note: The CountAnyMappedInLinkedList() function is identical to the CountAnyMappedInList() function, except that it contains two additional parameters (cFieldand cLinkToTable). The mapping will actually be calculated from (cField) in the (cLinkToTable) instead of from the (cList) alias.

The AtLeastNRecordsHaveLinkedValues() function has been added to FH. This function is available for rules and provides a way to implement some NEMSIS state rules. The parameters for the function are: 

  • cList
  • cLinkFromField
  • cLinkToTable
  • cLinkToField
  • nRecords (nRecords must default to 1 if not passed)

This function returns the following values under the following conditions:

Return Condition

FALSE

There are no records in the alias (cList)

FALSE

There are fewer than (nRecords) in the alias (cList) where the corresponding record in (cLinkToTable) as specified by the (cLinkFromField) have a value in (cLinkToField)

TRUE

At least (nRecords) in the alias (cList) where the corresponding record in (cLinkToTable) as specified by the (cLinkFromField) have a value in (cLinkToField)

The DuplicateMappedDescriptionInList() function has been replaced with the DuplicateMappedInList() function.

This function contains the following parameters:

  • cList = the list to check for duplicates
  • cField = the field to check
  • cCategory = the lookup category to check mappings for cField

This function returns TRUE if there are codes in (cList) that map to the same list.

Example: If we have the following list of symptoms:
  • 1440 Drainage/Discharge
  • 1441 Drainage/Discharge from vital area
  • 1485 Rash/Itching

and if 1441 is mapped to the export code of 1440 and the others are self-mapped, this function should return TRUE.

When setting up an automated task to do a Custom Data Export, if there are no records that currently meet the criteria in the primary query, the Setup wizard now allows you to complete the automated task setup. The message The primary query did not contain any records no longer displays, as the query is not run during setup.

FH Sketch is now fully function with this release. Any issues found during the demonstration period of FH Sketch have been successfully resolved.