7.15.25 Release Notes

These Release Notes are for Firehouse® release 7.15.25, 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.

The following issues were successfully resolved this release.

If you did not have view rights for patient/victim records, and if a NEMESIS validation automatically ran when you saved an incident record, the validation failed.

In the FH installation wizard, on the Select Installation Type screen, the information about installing on the Windows Vista platform was not accurate.

In the FH installation folder, FH created SQL error log files for internal use, but did not delete these files when they are no longer needed.

In the Administrative Options dialog box, on the License tab, there was a typographical error in the heading of the Station Organization section.

If you ran a Department Journal Report for a day that has a incident report including an exposure fire, the total staff hours was incorrect.

If you generated a Combined Activity & Training Summary report, the totals in the Rescue column of the report were not correct.

If you generated an EMS No Patient report, the report did not list the names of the officer in charge and the member making the report below the signature lines.

If you tried to renew permits without selecting which permits to renew with the steps below, the following error message appeared.

Error 107; Operator/operand type mismatch. at line 54 of procedure/method OCC_PREN.RENEW

  1. Choose File → Occupancy Management → Batch Renew Permits.

    The Renew Permits dialog box appears.

  2. Without selecting any permits in the list, click Renew.

    The error message appeared.

In the Account module, if you created a new invoice with the steps below, the Payments tab was blue, indicating that there was at least one payment for the account. Since this was a new invoice, however, no payments had been made yet.

  1. In the main toolbar, click Invoice.

    The Invoice dialog box appears.

  2. Create a new invoice as normal.

    The text of the Print & Payment History tab label is blue, indicating that a payment has been made on the invoice.

If you set up a system rule for Rating Bureau in training classes or a patient refusal signature form as required with the steps below, the label text for the tab the required fields appeared on was not red, indicating that information was required.

For Rating Bureau in training classes: 

    1. Choose Administration → System Rules and Default Values.

      The System Rules and Default Values dialog box appears.

    2. Expand Training, and then select Trn_main.

    3. Click Setup.

      The System Rules and Default Values – Training Classes dialog box appears.

    4. Click the Record-Level Rules tab.

    5. Click Add.

      The Require Child Record for Table dialog box appears.

    6. From Require a record in the following child table, choose TRN_RBUR.
    7. Verify that Require a record always is selected.
    8. Click OK.
    9. In the System Rules and Default Values – Training Classes, click OK.
    10. In the System Rules and Default Values dialog box, click Close.

  2. In the main toolbar, click Training.

    The Training Class dialog box appears, but the text label for the Rating Bureau tab is not red, indicating that you are required to enter information on that tab.

 

For the patient refusal signature form: 

    1. Choose Administration → Signature Form Setup.

      The Signature Form Setup dialog box appears.

    2. Under EMS/Search & Rescue Incident Reporting → EMS/Search & Rescue – Patient/Victim , and then select Patient Refusal.

    3. Click Properties.

      The Signature Form Properties dialog box appears.

    4. Click the Rules tab.
    5. Select Require this Form.
    6. (If a patient refusal signature form is not always required) Under Require Form When, specify an expression that describes when a patient refusal signature form is required.
    7. Click OK.
    8. In the Signature Form Setup dialog box, click Close.

  2. On the main toolbar, click EMS.

    The EMS/Search & Rescue Report dialog box appears, but the text label for the Other tab is not red, indicating that you are not required to enter information (the patient refusal signature form) on it.

If you created a user-defined field that was required in some cases and hidden in others with the steps below, the field was not always hidden later in a dialog box when the hide requirement was met.

    1. Begin creating a user-defined field, as normal.
    2. When the User-Defined Field Properties dialog box appears, on the Field tab, fill out the necessary parameters as normal.

    3. Click the Rules tab.

      A series of sub-tabs appears.

    4. Click the Require sub-tab.
    5. Select Make this a required field.
    6. In Requirement Condition, type the requirement expression you need.
    7. Click the Disable/Hide tab.
    8. In Disable this field when the following condition is true, type the expression you need to hide the field.
    9. Select Remove field from page if above condition is true.
    10. Click OK.
    11. In the EMS/Search & Rescue Patient Procedures Users Fields dialog box, click Save.
    12. In the User-Defined Fields Setup dialog box, click Close.
  2. Open a record in the module where the user-defined field is used.

  3. Verify that the requirements to hide the field are met, and look for the field in the dialog box where it appears is the conditions to display it are met.

    The field may appear in dialog box even when the requirements to hide its display are met.

If you specified a patient’s past medical history and alerts as "none" with the steps below, an item containing the letters none in its description may have been assigned to the history instead.

    1. Open an existing EMS record, or begin a new EMS record as normal.
    2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

    3. In the lower right corner of the tab, click Add.

      The Patient/Victim Information dialog box appears.

    4. Click the Scene tab.

    5. Under Patient Past Medical History & Alerts, select No.

      This selection sets the value to None.

  2. Under Patient Past Medical History & Alerts, now select Yes.

    The Past Medical History/Alerts dialog box appears, with a value whose description contains the letters none instead of simply the value None.

    Example: The description Propafanone contains the letters none, and may be set as the value.

If you edited a user-defined field and changed the length of the field with the steps below, the following error appeared.

Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert the value NULL into column 'User Field Name', table 'FH.dbo.occ_user'; column does not allow nulls.INSERT fails.

  1. Choose Administration → User-Defined Fields Setup.

    The User-Defined Fields Setup dialog box appears.

  2. Expand the category you defined the field in, and then select the user-defined field you created.

  3. Click Setup.

    The EMS/Search & Rescue Patient Procedures Users Fields dialog box appears, with the Users Fields Toolbar over it.

  4. In the EMS/Search & Rescue Patient Procedures Users Fields dialog box, double-click the user-defined field.

    The User-Defined Field Properties dialog box appears.

  5. On the Field tab, in Length, change the value.

    The error message appears.

If you modified a copy of an Occupancies with No Inspections report with the steps below, the following error message appeared.

An error occurred while processing rule condition "!ThisForm.QrySession.ValSQL(0,.F.,.T.)" for Table: Qry_Main

    1. Choose Reports → Occupancy Management Reports.

      The Reports dialog box appears.

    2. Expand Inspection Master Reports.

    3. Click New.

      A confirmation dialog box appears.

    4. Click Yes.

      The Select a Report dialog box appears.

    5. Select Occupancies with No Inspections, and then click Select.

      The Report Designer dialog box appears.

    1. On the Properties tab, click Properties.

      The Query Designer dialog box appears.

    2. Make a change in the dialog box.

      Example: Click the Filter tab, select the row containing Inspection Type in the Target column, and then click Delete.

    3. Click Save.

      The error message appears.

In your computer’s Control Panel, under Regional and Language Options, you can choose the time format (h:mm:ss tt or h:mm:ss) to use on your computer. Depending on your choice of time format in the Control Panel, if you selected the date formatting options in FH with the steps below and then later ran a system report as normal, unexpected date and time formatting problems occurred.

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the General tab.

      Three sub-tabs appear, and the Display tab is selected by default.

    3. Under Formatting, select Use Windows Control Panel date format.

    4. Clear Show Century.

    5. Click OK.

  2. Run a report as normal.

    The minutes and seconds may be filled in on the time, instead of the hours and minutes, and the time can also have a date format on the system report.

If you filled in arson information for a fire or wildland fire and then exported the data for NFIRS with the steps below, the arson transaction information did not export correctly.

    1. Create or open an incident record as normal.

    2. In the NFIRS Incident Report dialog box, fill in the required information as normal for an incident.

      Note: On the Basic tab, in Incident Type, specify an incident type in the lookup code range 100-173.

    3. Click the Additional Reports tab.

    4. Do one of the following.

        1. Click Fire.

          The Fire Report dialog box appears.

        2. Fill in the required information as normal for a fire.

          Note: On the Fire tab, for Cause of Ignition, choose a lookup code of 1, 2, 5, or U.

        1. Click Wildland Fire.

          The Wildland Fire Report dialog box appears.

        2. Fill out the required information as normal for a wildland fire.

          Note: On the Scene tab, for Wildland Fire Cause, choose lookup code 7.

    5. When you finish filling out the information, close the dialog boxes.

    1. Choose File → NFIRS 5 Incident Reporting → Export NFIRS 5 Transaction File.

      The NFIRS 5.0 Export Wizard dialog box appears.

    2. Complete the export of data as normal.

      The arson transaction information is not included in the export file.

If you changed the length of automatically generated number values with the steps below, numbers appeared in some fields in exponential format instead of in integer format.

Example: 002.011 E+ 10

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the Database tab.

      A series of sub-tabs appears on the Database tab.

    3. Click the Key Values tab.

    4. In the Key Format column, note that some keys are set to Alpha-Numeric, and others are set to Numeric.

      Note: This issue affects only numeric keys, not alpha-numeric keys.

    5. For any key with a value in the Key Format column of Numeric, change the value to 15.

    6. In the Field Name column, note the field name for the key you changed.

      Example: In the Occupancy Permits row, in the Field Name column, value is Permit No.

    7. Click OK.

  2. Open the dialog box containing the field whose key length you changed.

    Example: To find the Permit No field, you would click Occup, and in the Occupancy dialog box that appears, you would click the Additional Records tab, and then click Permits. The Permits dialog box would appear, and you would click Add in it. The Permit Dialog box would appear, containing the Permit No field.

  3. Type in the permit number you want to use.

    The number appears in exponential form, instead of as an integer.

If you printed a NFIRS report that contained arson and racial/ethnic hate group information in it with the steps below, the resulting report indicated suicide as a motivating factor, instead of your selection for the apparent group involvement.

  1. Create or open an incident record as normal.

  2. In the NFIRS Incident Report dialog box, fill in the required information as normal for an incident.

    Note: On the Basic tab, in Incident Type, specify an incident type in the lookup code range 100-173.

    1. Click the Additional Reports tab.

    2. Click Arson/Investigation.

      The Investigation dialog box appears.

    3. Click the Fire/Arson tab.

    4. Under Apparent Group Involvement, on the right side of the dialog box, click the plus (+) button.

      A new row appears in the list, with the cell in that row’s Code column highlighted and a lookup button in the ? column.

    5. Click the lookup button.

      The Lookup – Apparent Group Involvement dialog box appears.

    6. Select a lookup code, and then click OK.

      The new row in the list updates with the lookup code information.

    7. Click Save, and then click Close.

    1. In the lower right corner of the NFIRS Incident Report dialog box, click Print.

      The Output Report To dialog box appears.

    2. Under Select Output Type, choose how you want the printed report to be displayed or sent.

    3. Click OK.

      The Run Batch or Collated Report dialog box appears.

    4. Click OK.

      The report generates, and section F: Apparent Group Involvement, contains incorrect information.

If you added several violations at once to an inspection record with the steps below, the number of violations did not total correctly.

  1. Create or open an inspection record as normal.
  2. In the Inspection dialog box, click the Violations tab.

  3. Click Add Group.

    The Lookup – Violation Codes (MultiSelect) dialog box appears.

  4. Select the violation codes you want as normal, and then click OK.

    The Violation Detail dialog box appears.

  5. Fill out the necessary information as normal, and then click Save.

    The Violation Detail dialog box closes automatically, and in the Inspection dialog box, the inspection violation total in the lower left corner of the dialog box does not contain the correct number of violations.

If you installed pre-defined (PD) NEMSIS user fields, but you did not specify certain vital information (for example, pain scale, pediatric trauma score, or blood glucose level) before you exported NEMSIS data, the PD fields did not export.

Information on adding pre-defined user fields is available in the National EMS Information System (NEMSIS) Installation and Implementation Guide, (http://www.firehousesoftware.com/pdf/NEMSIS_Implementation_Checklist.pdf), under Add additional user fields.

    1. Create or open an EMS record as normal.
    2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

    3. Create or open a patient/victims record as normal.

      The Patient/Victim Information dialog box appears.

    4. Click the Assessments & Treatments tab.

    5. On the right side of the dialog box, click Add Vitals/Ax.

      A list of assessments and treatment appears at the top of the tab, and a series of sub-tabs appears below the list.

    6. Click the Other sub-tab.

    7. Click User Fields.

      The EMS/Search & Rescue – Patient Assess/Vit dialog box appears, with any pre-defined (PD) NEMSIS user fields you added when you installed NEMSIS codes in FH.

    8. Specify information for some PD user fields, but not for others.

      Example: Do not enter data for pain scale, pediatric trauma score, or blood glucose level.

    9. Save the information and close all the dialog boxes.

  2. Export your NEMSIS data as normal.

    Information on exporting NEMSIS data is available in the National EMS Information System (NEMSIS) Installation and Implementation Guide, (http://www.firehousesoftware.com/pdf/NEMSIS_Implementation_Checklist.pdf), under Export NEMSIS data for state and national reporting.

    The PD user-defined fields do not export as expected.

If you installed NEMSIS codes and tried to add medication codes, the first medication code updated correctly, but an error message appeared for any additional medication codes you updated.

  1. Add one medication code, as described in the National EMS Information System (NEMSIS) Installation and Implementation Guide, (http://www.firehousesoftware.com/pdf/NEMSIS_Implementation_Checklist.pdf), under Update medication codes.

  2. Repeat the steps as directed to add a second medication code.

    An error message appears.

If you tried to change the system rule for the INV_MLDR table (inventory maintenance ladder testing table) with the steps below, the wrong fields appear in a menu.

  1. Choose Administration → System Rules and Default Values.

    The System Rules and Default Values dialog box appears.

  2. Expand Inventry, and then select Inv_mldr.

  3. Click Setup.

    The System Rules and Default Values – Inventory Maintenance Ladder Testing dialog box appears.

  4. Under Field Name, select L_BM5.

  5. In the lower right corner of the dialog box, click Add.

    The Select Rule Type dialog box appears.

  6. Choose Update the Value of Another Field, and then click OK.

    The Update Value From Field dialog box appears.

  7. Click the Field in MaintenanceRecord_Ldr to Replace menu.

    The options listed in this menu are not the right fields for the INV_MLDR table.

When you filled out phone number information for an inspection with the steps below, the type of phone a phone number was associated with was not required, and should have been.

  1. Create or open an inspection record as normal.
  2. In the Inspection dialog box, click the Responsible Party tab.

  3. Under Phone Numbers, near the right edge of the dialog box, click the plus (+) sign.

    A new row appears in the list, with the cell in that row’s Type column highlighted and a lookup button in the ? column.

    You could click in the new row’s cell in the Phone Number column and enter a number, and you could save the inspection record, without specifying what type of phone (home, office, mobile, fax, and so forth) the phone number was for.

If you printed a default custom report that queried user-defined fields for child records of a module (such as the patient/victim records within an EMS record) with the steps below, the following error message appeared.

Unable to open userfield EMS/Search & Rescue Inciden UserFields in exclusive mode.
Exclusive access to this table is required to make modification to user field definitions

    1. Choose Reports → Incident Reports.

      The Reports dialog box appears.

    2. In the dialog box, navigate to and select your custom report, which queries user-defined fields in child records of a module.
    3. Click Default, and then choose Set as Global Default from the menu that appears.
    4. Click Close.
    1. Open the record containing user-defined fields in the child record, which you want to print.

    2. In the lower right corner of the dialog box, click Print.

      The Output Report To dialog box appears.

    3. Under Select Output Type, choose the option corresponding to where you want the report sent.

    4. Click OK.

      The error messages appear.

If you have two permits for an occupancy, an account linked to the permits for billing, and you batch-generated invoices a second time with the steps below, an invoice for one of the permits was generated a second time, even though an invoice for it already existed.

  1. Choose File → Invoicing and Payments → Batch Generate Invoices.

    The Batch Generate Invoices dialog box appears.

  2. Select options and specify the dates for generating the invoices as normal.

  3. Click Next.

    The next screen of the wizard lists the invoices being created, and one of the permits is listed again, and should not be.

When you specified a date in the Journal module with the steps below, the Calendar dialog box appeared behind another dialog box.

  1. On the main toolbar, click Journal.

    The Department Journal dialog box appears.

  2. In the lower left corner of the dialog box, click Options, and then choose Select Date from the menu that appears.

    The Enter a Value dialog box appears.

  3. Click Calendar.

    The Calendar dialog box appears behind the Enter a Value dialog box, and you must drag it to the side, away from the Enter a Value dialog box, to continue working.

(FH Enterprise) If you updated from Enterprise 6.1.6 to Enterprise 7.5.84, 1781 and 5074 errors appeared in the update log file.

(FH Enterprise) If you selected a database to log into by default with the steps below, the setting was not saved for the next time you logged into FH Enterprise.

  1. Start FH Enterprise as normal.

    The Remote Login dialog box appears.

  2. From Database, select the database that you want to log into by default each time you log into FH.

    This setting is not saved for the next time you log into FH Enterprise.

If you have the NEMSIS code set installed, when you ran an Incomplete EMS Incident report, an incorrect prompt to transfer the fields to a NFIRS incident report appeared.

If you opened a patient record with Device Monitor data attached to it using the steps below, you could not view the attachment in FH.

  1. Open an EMS record that you know has Device Monitor data attached to it.
  2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

  3. Select the name of the patient that has Device Monitor data associated with them, and then click Open.

    The Patient/Victim Information dialog box appears.

  4. Click the Clinical tab.

    A series of sub-tabs appear.

  5. Click the Device Data sub-tab.

  6. Select the device data record you want to view, and then click Open.

    The Medical Device Data dialog box appears.

  7. Click Waveform Graphic.

    The Attachments & Signatures dialog box appears.

  8. Click the Attachments tab.

  9. Select the Device Monitor attachment you want to view, and then click Run It.

    The file cannot be previewed.

If you have a very large database and you changed months in the Journal module with the steps below, it could take a few minutes for FH to refresh the display of the Journal.

  1. On the main toolbar, click Journal.

    The Department Journal dialog box appears.

  2. In the upper left corner of the dialog box, click the left arrow or the right arrow to change the month displayed in the dialog box.

    FH takes a long time to refresh the calendar to show the previous or next month.

If you had detailed audit tracking enabled in FH and you added a new contact with an email address longer than 36 characters to an accounting record with the steps below, an 8152 error message appeared.

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the Database tab.

      A series of sub-tabs appear.

    3. Click the Auditing sub-tab.
    4. Select Enable detailed audit tracking, and then click OK.
    1. Create a new account, or open an existing account, as normal.

    2. In the Account dialog box, click the Contacts tab.

    3. In the right corner of the dialog box, click Add.

      The Contact Detail dialog box appears.

    4. Enter contact information in the fields as normal, specifying an email address longer than 36 characters.

    5. Click Save.

      An 8152 error message appears.

(FH Enterprise) If you have automated tasks set to run on Windows startup and then created an Incomplete NFIRS Incident or Missing/Unused Incident Numbers report with the steps below, error messages appeared.

    1. Choose Tools → Workstation Options.

      The Workstation Options dialog box appears.

    2. Click the Other tab.

      A series of sub-tabs appears.

    3. Click the Automated Tasks sub-tab.
    4. Select Auto-Load on Windows Startup.
    5. Click OK.
  2. Set up an automated task to print an Incomplete NFIRS Incident Report List report or a Missing/Unused Incident Numbers report, as normal.

  3. Exit FH, and reboot the computer.

    When the automated task runs, error messages appear.

If you ran the Invoices (Second Printing) report more than two times, the number of invoice items was incorrect in the report.

If you tried to assign account payment responsibility to a group of departments or agencies with the steps below, a series of error messages appeared.

  1. Create a new account, or open and existing account, as normal.
  2. In the Account dialog box, click the Payment Responsibility tab.

  3. Click Add Group, and then select Department/Agency from the menu that appears.

    The Lookup dialog box appears.

  4. Using the Shift key on your keyboard, select more than one department code in the list, and then click OK.

    The Account Payment Responsibility Link dialog box appears.

  5. For Linked ID, click the lookup button.

    A series of error messages appear.

If you used the Query Designer to build an SQL query that includes fields that can be updated with the steps below, when you ran the query, results for all the fields in the query appeared on the screen, but not all of the results exported to an Excel spreadsheet.

    1. Choose Tools → Queries.

      The Queries dialog box appears.

    2. Click New.

      You are prompted to start with a copy of an existing query.

    3. Click No.

      The Query Designer dialog box appears, displaying the Properties tab.

    4. In Query Name, type a name for the query you are writing.
    5. Under Options, select Define query manually through custom SQL commands.

    6. Under Output, click Customize SQL.

      The Query – Customize SQL dialog box appears.

    7. Enter your custom SQL statement in the dialog box, and then click OK.

      The dialog box closes automatically.

    8. Click Save, and then click Close.

      In the Queries dialog box, your new query is selected by default.

    1. In the Queries dialog box, click Run.

      The Query dialog box appears.

    2. In the lower right corner of the dialog box, click Options, and then choose Print or Output to from the menu that appears.

      The Output Query To dialog box appears.

    3. Under Select Output Type, select Other File Type.
    4. From the menu under Other File Type, choose Spreadsheet (Excel Compatible).

    5. Click File.

      A file browser appears.

    6. Specify the location and name to save the output file with, and then click OK.

      The SQL query runs, but only the fields that can be updated are exported to the .XLS file.

If you tried to set up an automated task to print the department journal or daily reminders report and send it to an email with the steps below, the email file setup screen never appeared.

  1. Choose Administration → Automated Tasks.

    The Automated Task Setup dialog box appears.

  2. Click New.

    The Automated Task Properties dialog box appears.

  3. Under Task to Perform, select Print a Report.

  4. Fill in the name of the automated task and how often to run it, as normal.

  5. Click Setup Task Parameters.

    The Select a Report dialog box appears.

  6. Do one of the following.

    • Expand Department Journal Reports, and then select Department Journal.

    • Expand Daily Reminder Reports, and then select Daily Reminders.

  7. Click Select.

    Depending on the type of report you selected, the Department Journal Report or Daily Reminders Report dialog box appears.

  8. Fill out the fields in the dialog box as normal, and then click OK.

    The Output Report To dialog box appears.

  9. Under Select Output Type, choose PDF.

    The lower half of the dialog box updates to display fields for saving a PDF file.

  10. Click File.

    A file browser appears.

  11. Specify the name and location of the PDF file, and then click Save.

  12. In the Output Report To dialog box, select Send File via Email, and then click OK.

    The Email File Setup dialog box does not appear as it should.

In the EMS module, for patient/victim records, when you filled in any user-defined fields with the steps below, incorrect status messages for the fields appeared in the lower left corner of the EMS/Search & Rescue – Patient/Victim Use dialog box.

  1. Open an existing EMS record as normal.
  2. In the EMS/Search & Rescue Report dialog box, click the Patients and Victims tab.

  3. Select the name of the patient you want to work with, and then click Open.

    The Patient/Victim Information dialog box appears.

  4. Click the Other tab.

  5. Click User Fields.

    The EMS/Search & Rescue dialog box appears.

  6. In the first user-defined field, enter a value.

    In the lower left corner of the dialog box, any status messages specified for other user-defined fields in the dialog box begin displaying, cycling through all of them and then stopping on the status message for the next user-defined field.

    If you start a new patient, when you enter user-defined fields, the status message for the last user field appears, instead of the status message for the first field.

If you created an incident and specified an occupancy ID for it with the steps below, the property ownership information did not propagate to the arson/investigation or EMS/search and rescue child records.

  1. Create a new incident as normal.

  2. In the NFIRS Incident Report dialog box, in the upper right corner, for Occupancy ID, click the lookup button.

    The Query dialog box appears.

  3. Select the occupancy you want to associate the incident with, and then click OK.

    The Transfer Occupancy Owner/Contact Information dialog box appears.

  4. Select the owner/contact names you want to transfer information for, and then click OK.
  5. Click the Additional Reports tab.

    1. Click EMS/Search & Rescue.

      The EMS/Search & Rescue Report dialog box appears. On the Basic tab, the Property Ownership field is blank, when it should have populated from the occupancy information.

    2. Click Arson/Investigation.

      The Investigation – Incident Investigation dialog box appears. On the Fire/Arson tab, the Property Ownership field is blank, when it should have populated from the occupancy information.

If you set the administration requirement that EMS reports are required for certain NFIRS incident types and you saved the EMS report with an informational message with the steps below, the EMS report is incorrectly marked as incomplete, and as a result, the NFIRS report is also marked as incomplete.

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the Incident tab.

      A series of sub-tabs appears.

    3. Click the EMS/Search & Rescue tab.

      Another series of sub-tabs appears, with the General tab displayed.

    4. Under Requirements, select Require EMS report for these NFIRS incident types.

    5. Note the lookup codes listed for the NFIRS incident types, and then click OK.

    1. Choose Administration → System Rules and Default Values.

      The System Rules and Default Values dialog box appears.

    2. Expand EMS, and then select any field in the list.

    3. Click Setup.

      The System Rules and Default Values – EMS/Search & Rescue dialog box appears for the field, set to the Field-Level Rules and Default Values tab.

    4. Under Field Name, select the field in the EMS table that you want to create a system rule for, and then click Add.

      The Select Rule Type dialog box appears.

    5. Select Define Field Error Condition, and then click OK.

      The Error Condition for Field dialog box appears.

    6. Fill in the dialog box as normal, and then click OK.
    7. In the System Rules and Default Values – EMS/Search & Rescue dialog box, click OK.
    8. In the System Rules and Default Values dialog box, click Close.
    1. Create an incident report as normal, specifying one of the incident types that you noted in step 1e.

    2. In the NFIRS Incident Report dialog box, click the Additional Reports tab.

      The EMS/Search & Rescue button label is red, indicating that you must specify EMS information.

    3. Click EMS/Search & Rescue.

      The EMS/Search & Rescue Report dialog box appears.

    4. Fill in the dialog box as normal, except on the Patients/Victims tab, set Number of Patients/Victims Treated or Transported to zero (0).

    5. Click Save.

      The Validation Results dialog box appears, showing an informational message that states: Number of Patients/Victims Treated/Transported is 0.

    6. Click Ignore All.

      The EMS record saves. Even though the only validation message was informational (not required), the EMS record remains marked as incomplete. As a result, the incident record cannot validate as complete, either.

If you synchronized an iPad with FHinspector installed, the following error message occasionally appeared.

1585 update conflict - Procedure APP.DBSESSION.TBLCLOSE

If you filled in an incident report with incident type 100 with the steps below, you were required to indicate whether a detector alerted occupants with the steps below. NFIRS no longer requires this information, and the requirement in FH has been removed.

  1. Create or open an incident record as normal.
  2. In the NFIRS Incident Report dialog box, on the Basic tab, for Incident Type, enter a lookup code of 100.
  3. Click the Response tab.

  4. Under Detector, the Detector Alerted Occupants field is required.

    This field is no longer required for this incident code.

If you exported transaction files from FHnet, date and time fields with a time of 00:00:00 (midnight) exported as 000000. When you imported these transaction files into any legacy edition of FH with the steps below, import errors occurred from the 000000 value.

  1. Do one of the following.

    • Choose File → NFIRS Incident Reporting → Import NFIRS Transaction File.

      The NFIRS Import dialog box appears.

    • Choose File → EMS/Search & Rescue Reporting → Import EMS Transaction File.

      The FH EMS Import dialog box appears.

  2. Fill in this dialog box as normal, and then click OK.

    Error messages appear.

If you disabled the display of the Delete button in module dialog boxes with the steps below, the Delete button still appeared in the Department Journal and Daily Reminders dialog boxes.

    1. Choose Tools → Workstation Options.

      The Workstation Options dialog box appears, set to the General tab and the Startup & Navigation sub-tab.

    2. Click the Data Entry Forms tab.
    3. Under Deleting Records, select Hide the "Delete" button from the bottom of data entry forms (Delete is an option on the Form menu).
    4. Click OK.

  2. On the main toolbar, click Journal.

    The Department Journal dialog box appears, and the Delete button still appears in the lower right corner of the dialog box.

  3. Choose File → Daily Reminders.

    The Daily Reminders dialog box appears, and the Delete button still appears in the lower right corner of the dialog box.

If you enabled the automatic generation feature for EMS reports, when you tried to automatically generate a narrative for an EMS patient record with the steps below, an unnecessary prompt for query custom parameters appeared.

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the Incident tab.

      A series of sub-tabs appears.

    3. Click the EMS/Search & Rescue sub-tab.

      Additional sub-tabs appear.

    4. At the bottom of the General sub-tab, under Auto-Generate Narrative, select Provide option to auto-generate the EMS scene/patient narrative.
    5. Click OK.
    1. Create a new EMS record, or open an existing EMS record, as normal.
    2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

    3. Select the name of the patient you want to generate a narrative for, and then click Open.

      The Patient/Victim Information dialog box appears.

    4. Click the Patient Narrative tab.

    5. In the lower right corner of the tab, click Auto-Generate.

      The Narrative Generation dialog box appears.

    6. In the upper right corner of the dialog box, click Generate Narrative.

      The Query Custom Parameters dialog box appears, and does not need to.

(FH Enterprise) If you ran an Expanded Patient Billing Statement report, the report did not produce any results.

If you ran the Dollar Value Saved & Loss Analysis report over a specific alarm date range, the letter “a” appeared in the heading of the report, at the end of the date range.

If you filtered the department day journal by staff ID and/or shift with the steps below, the activities for all personnel filter was used instead.

    1. Choose Tools → Workstation Options.

      The Workstation Options dialog box appears.

    2. Click the Other tab.

      A series of sub-tabs appears.

    3. Click the Journal & Reminders sub-tab.
    4. Select Use Day Journal instead of Month Journal (May perform better for larger departments).
    5. Click OK.

    1. On the main toolbar, click Journal.

      The Department Journal (Day Mode) dialog box appears.

    2. In the lower left corner of the dialog box, click Filtering.

      The Filtering Options dialog box appears.

    3. For Shift(s) or Staff Member(s), click the lookup button and select a lookup code.

    4. Click Apply Filter.

      The filter is not applied, and activities for all personnel still appear on the calendar.

If you opened a training record and, in a group of attendees, tried to select specific individuals using the Ctrl key with the steps below, the multiple-select function did not work.

  1. Open the training record you want to edit, as normal.

  2. In the Training Class dialog box, click Edit Group.

    The Training Class – Group Update dialog box appears.

  3. Hold down the Ctrl key on your keyboard and, from the list of attendees, try to select multiple names.

    The multiple-select function with this key does not work.

(FH Web) If you started a new inventory maintenance/test record and changed the default vendor with the steps below, the screen blinked, and then FH Web locked up.

  1. Open an existing inventory record that has maintenance/test information saved in it, as normal.
  2. In the Inventory dialog box, click the Maintenance/Test tab.

  3. Under Maintenance, click Add.

    The Maintenance/Test Detail dialog box appears.

  4. For Job, enter a lookup code, or click the lookup button and select a lookup code.
  5. On the Basic tab, for Vendor, enter a lookup code, or click the lookup button and select a lookup code for a different vendor.

  6. Click Save.

    The screen blinks, and then FH Web locks up.

If you created a new incident module and pressed the Tab key after specifying an occupancy ID with the steps below, the following error message appeared.

Error 2012 - Cannot call SetFocus from within a When, Valid, RangeHigh or RangeLow event

  1. Create a new incident record as normal.

  2. In the NFIRS Incident Report dialog box, in the upper right corner, in Occupancy ID, enter the ID number for the occupancy, and then press the Tab key on your keyboard.

    The 2012 error appears.

If your training data is entered for one station, and you ran the Activity & Training Hours/Points Summary report for a different station with the steps below, the report did not generate.

  1. Choose Reports → Staff, Activity, and Training Reports.

    The Reports dialog box appears.

  2. Under Reports → Staff, Activity, and Training Reports, select Activity & Training Hours/Points Summary, and then click Run.

    The Output Report To dialog box appears.

  3. Under Select Output Type, choose the option corresponding to where you want the report sent, and then click OK.

    The Query Parameters dialog box appears.

  4. In the row for Station, in the cell in the Value column, specify which station you want to generate the report for.

  5. Click Run Query.

    If the station you specified in the previous step is not the station the training was entered for, the report does not generate.

In the Report Designer, if you docked the two floating toolbars with the steps below, the user preferences for their position was not saved as part of your user preferences, and the toolbars were floating again in your next Report Designer session.

  1. Choose Reports → Incident Reports.

    The Reports dialog box appears.

  2. Select a report you want to open, and then click Layout.

  3. Answer prompts that appear in a series of dialog boxes as normal.

    The Report Designer appears, displaying the layout of the report. Two of the toolbars that are normally docked at the top of the Report Designer are “floating” over the layout area.

  4. Drag the two toolbars back to the top of the screen and dock them.

  5. Choose File → Save and Close.

    The Report Designer closes.

  6. Repeat steps 2-3.

    The two toolbars are floating again over the layout area, instead of remaining in the docked position you had specified in your last session.

If you copied an existing report and modified it, and then created an .FHz file containing the report components with the steps below, the following error appears.

Error 1: File does not exist. at line 54 of procedure/method
FRMCOPYTO.INSTALL.ADDFILE.

  1. Choose Reports → Incident Reports.

    The Reports dialog box appears.

  2. Select any of the following reports.

    Tip: To select a report quickly, click Find, in the Find in Drilldown List dialog box that appears, type the name of the report, and then click Find. The hierarchy expands as needed, and the name of the name of the report is selected.

    • Hydrants out of Service

    • Staff List By Hire Date

    • Staff List By Name

    • Staff List By Rank w/ Phone Number

    • Staff List By Station

    • Narrative (non-NFIRS)

      Tip: Select Show Hidden to see this report in the list.

    • Arson Narrative (non-NFIRS)

      Tip: Select Show Hidden to see this report in the list.

  3. Click New.

    A dialog box asking whether you want to make a copy of the report appears.

  4. Click Yes.
  5. Respond to any prompts that appear, make the needed changes to the report, as normal.

  6. In the Reports dialog box, click Options, and then choose Copy To in the menu that appears.

    The Copy To dialog box appears.

  7. Click to File, and then use the file browser that appears to specify the location and file name of the .FHz file this process creates.

  8. Click OK.

    The error appears.

If you printed an EMS record to a PDF file with the steps below, you were prompted to cancel the zip file. Depending on your response to the prompt, an error message appeared, or the report was sent to your default printer.

  1. Open the EMS record you want to print, as normal.

  2. In the EMS/Search & Rescue Report dialog box, in the lower right corner of the dialog box, click Print.

    The Output Report To dialog box appears.

  3. Under Select Output Type, select PDF.

    The bottom portion of the dialog box updates to display a field related to saving a PDF file.

  4. Click File, and then use the file browser that appears to navigate to the location and specify the name of the PDF file you want to save the report to.

  5. Click OK.

    The Run Batch or Collated Report dialog box appears.

  6. Select EMS Patient Signatures, and then click OK.

    The report begins generating, but then a prompt to cancel the zip file appears. If you click Yes, an error appears. If you click No, the report is sent to your default printer.

If you opened any module, browsed the list of records, and tried to sort the list by name with the steps below, the following error message appeared.

Error 2199: Error building key for index

  1. On the main toolbar, click any button.

    The dialog box for that module appears.

  2. At the bottom of the dialog box, click Browse.

    The Query dialog box appears.

  3. Double-click the title of the Last or First column, to sort the list by name.

    The error appears.

If you set the number of days in advance for daily reminders to zero (0) with the steps below, birthdays and maintenance items two days in advance still appeared in the reminders list.

  1. Choose File → Daily Reminders.

    The Daily Reminders dialog box appears.

  2. At the bottom of the dialog box, for Show Reminders ____ days in advance, set the value to zero (0).

    Birthdays and maintenance items two days in advance still appear in the reminders list.

If you installed NEMSIS lookup codes and chose to map existing codes during the installation, and then you later changed the export code mapping with the steps below, the export code mapping value was lost.

  1. Choose Tools → Lookup Tables.

    The Lookup Tables dialog box appears.

  2. Expand EMS/Search & Rescue Incident Report Codes → EMS Clinical Codes.

  3. Select Advanced Directive, and then click Setup.

    The Lookup – Advanced Directive dialog box appears.

  4. Select a lookup code, and then click Edit.

    The Code for Advanced Directive dialog box appears.

  5. In Export Code, change the current code value and a different export code.
  6. Click Save.

  7. Select the same code and click Edit.

    The Code for Advanced Directive dialog box reappears.

  8. In Export Code, change the current code value again to a different export code.
  9. Click Save.

  10. Select the same code and click Edit.

    In the dialog box, the value in Export Code is gone.

If you set up an automated task to generate the Detailed Schedule Listing / Sign-In Sheet report, the automated task used the current system time instead of the time specified in the query parameters.

If you ran the Staff Availability Response or Staff Member Participation reports, the resulting report contained discrepancies in the number of calls a staff member was available for, and how many calls they participated in.

If you upsized an existing FH Standard database to an FH Enterprise database, when the database began to update, the following error message appeared.

Error 1734: Property CONFIDENCELEVEL is not found at line 19
of procedure/method CTRBASICMAPPINGINTEGRATIONADDRESS.REFRESH.

Information on upsizing to FH Enterprise is available in the FIREHOUSE Software Enterprise Upsizing Guide.

If you tried to update the new FH Enterprise database again, a 4145 error appears in the update log file.

When you installed FH Web, the first time you launched the program, you are prompted to log out and start a new session so that a registry key is set properly. However, if the path to your user profile is long, you may have been repeatedly prompted to log out and start a new session.

If you do not have administrator permissions in FH and you try to add a default staff activity code to an investigation with the steps below, fields for specifying the incident-related activity are grayed out, when they should be available.

  1. On the main toolbar, click Incident.

    The NFIRS Incident Report dialog box appears.

  2. Open an existing record with an incident type of 111, as normal.
  3. Click the Additional Reports tab.

  4. Click Arson/Investigation.

    The Investigation – Incident Investigation dialog box appears.

  5. Click the Activities tab.

  6. Click Add.

    The Staff Activity dialog box appears.

  7. For Default Activity Code, click the lookup button and then choose the activity code you need.

    Under Incident-Related Activity, the fields do not activate as expected.

If you opened an existing patient/victim record that contained a required phone number and saved it with the steps below, the validation results indicated that the phone number was required, even though the phone number had been supplied.

  1. Open an existing EMS record containing a patient/victim record in it, as normal.
  2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

  3. Select the name of the patient you want to work with, and then click Open.

    The Patient/Victim Information dialog box appears. On the Basic tab, on the lower left corner of the tab, under Phone Numbers, phone number information appears.

  4. Click Save.

    The Validation Results dialog box appears. A critical error message that the phone is a required entry appears in the dialog box, even though a phone number has been entered.

When filling out an Incident report for a fire, if you specified an occupancy ID and started an arson/investigation report for the fire with the steps below, property ownership information from the occupancy record did not transfer into the investigation record as it should have.

  1. Open an existing incident that has an occupancy ID defined and an arson investigation attached to it, as normal.
  2. In the NFIRS Incident Report dialog box, click the Additional Reports tab.

  3. Click Arson/Investigation.

    The Investigation – Incident Investigation dialog box appears.

  4. Click the Fire/Arson tab.

    The Property Ownership field is blank, when it should be populated with information from the occupancy record.

If you deleted the default account status lookup codes with the steps below, problems with linking an occupancy to an account occurred. You should not have been able to delete the default account status lookup codes.

  1. Create a new account, or open an existing account record, as normal.

  2. In the Account dialog box, in the upper right corner of the dialog box, for Status, click the lookup button.

    The Lookup – Account Status dialog box appears.

  3. Select any of the default lookup codes (Active, Inactive, Closed, and Pending).

    The Delete button activates, and you can delete these system codes, even though you should not be able to.

If you tried to save a non-primary query for a report with the steps below, the following error message appeared.

Error creating view Query Temp in database
C:\Docume~1\SPORRAZZ.CO\LOCAL~1\TEMP\FHTEMP.DBC
Error 1 (File 'ems_main_query.dbf' does not exist.)
Press OK to view the text of the SQL statement or CANCEL to continue without saving

  1. Choose Reports → Incident Reports.

    The Reports dialog box appears.

  2. Expand Incident Reports → EMS/Search & Rescue Reports → EMS Patient Reports.

  3. Select EMS Incident Report, and then click Properties.

    A warning dialog box that you are attempting to modify a system report appears.

  4. Click Yes.

    The Report Designer dialog box appears.

  5. On the Properties tab, under Reports to run, select one of the report names.

  6. On the right side of the tab, click Properties.

    The warning dialog box that you are attempting to modify a system report reappears.

  7. Click Yes.

    A second Report Designer dialog box appears.

  8. On the Properties tab, under Query Name, select one of the queries, and then click Properties.

    The warning dialog box that you are attempting to modify a system report reappears.

  9. Click Yes.

    The Query Designer dialog box appears

  10. Click Save.

    The error message appears.

If you set up an automated task for importing data from a station, when the task runs, the following errors appear in the log files.

Unable to update record in Audit Record Save/Delete History - Error 2627 Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'aud_hist_audit_key'. Cannot insert duplicate key in object 'dbo.aud_hist'.

Unable to update record in EMS/Search & Rescue Patient Report Authorizations - Error 2627 Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'ems_auth_auth_key'. Cannot insert duplicate key in object 'dbo.ems_auth'.

If you have installed the NEMSIS code set, and if you created a staff status lookup code that was more than three characters long with the steps below, an error message appeared, stating that “123’ is not a valid lookup entry for category Staff Status Codes.

    1. Choose Tools → Lookup Tables.

      The Lookup Tables dialog box appears.

    2. Expand Staff Activity and Training Codes → Staff Member Codes, and then select Staff Status Codes.

    3. Click Setup.

      The Lookup – Staff Status Codes dialog box appears.

    4. Click New.

      The Code for Staff Status Codes dialog box appears.

    5. In Code, type a four- or five-character code for the status you are creating.
    6. Fill in the rest of the fields in the dialog box as normal, and then click Save.
    7. In the Lookup – Staff and Status Codes and Lookup Tables dialog boxes, click Close.
  2. Create a new staff member, or open an existing staff member record as normal.

  3. In the Staff dialog box, on the Basic tab, on the right side of the tab, for Status, click the lookup button and select the four- or five-character staff member status.

    The error message appears.

If you enabled the administration feature to append to incident narratives, set user security permissions to override append-only notes and narratives, and accessed an incident or EMS record’s narrative with the steps below, the buttons to unlock the narrative and append text did not always activate.

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the Database tab.

      A series of sub-tabs appear.

    3. Click the Data Security sub-tab.
    4. Under Append-Only in Notes & Narratives, expand Incident Records Management.
    5. Select NFIRS Incident Reports and EMS/Search & Rescue Incident Reports.

    6. At the top of the dialog box, click the Incident tab.

      A series of sub-tabs appear, with the All Incidents sub-tab selected by default. A series of sub-tabs appear on the All Incidents sub-tab.

    7. Click the Authorizations & Locking sub-tab.

    8. Select Automatically Lock Incident Reports.

      The options below it activate.

    9. Select Disallow changes __ hours after initial report entry, and then specify the number of hours in the field.
    10. Click OK.

    1. Choose Administration → Users and Security.

      The Users and Security dialog box appears.

      1. Click the Modules tab.
      2. Under Tables, scroll down to NFIRS Incident Report, and then scroll across until you can see the Override Append-Only Notes/Narratives.
      3. Select Override Append-Only Notes/Narratives.
      4. Repeat the previous two steps for EMS/Search & Rescue Incident Reports.
      5. Click Save.

    3. In the Users and Security dialog box, click Close.

  3. Log out of FH, and then log back into FH as a user without administration privileges.

    1. On the main toolbar, click Journal.

      The Department Journal dialog box appears.

    2. Click a date in the calendar that has an incident or EMS icon on it.

      A more detailed listing for the incident or EMS record appears in the right pane.

    3. Double-click the incident or EMS listing in the right pane to open the record.

      The NFIRS Incident Report or EMS/Search & Rescue Report dialog box appears.

    4. Click the Incident Narrative tab.

      At the bottom of the tab, the Unlock Narrative and Append buttons are not active, and should be.

      Note: If you access the NFIRS Incident Report or EMS/Search & Rescue Report dialog box directly from the main toolbar, these buttons are active for the first record you open, but are then not-active for the next records you open.

If you have an incident of type 122 and filled out both equipment involved in the ignition and mobile property, and then generated a report for submission to the state with the steps below, the equipment involved in the ignition was not included in the report.

    1. Create or open an existing NFIRS report of incident type 122, as normal.
    2. In the NFIRS Incident Report dialog box, click the Additional Reports tab.

    3. Click Fire.

      The Fire Report dialog box appears.

    4. Click the Equipt & Mobile Property tab.

    5. Fill in the fields under Equipment Involved in Ignition and Mobile Property Involved, as normal.

    6. Click Save, and then click Close.
    7. In the NFIRS Incident Report dialog box, click Save, and then click Close.

  2. Choose File → NFIRS Incident Reporting → Export NFIRS Transaction File.

    The NFIRS Export Wizard appears.

  3. Use the wizard to export your incident data as normal.

    The data about the equipment involved in the ignition is not included in the report.

If you are using the Active Directory (AD) integration, and you enabled the option for the user to change databases for one of FH Standard/Enterprise or FH Web with the steps below, both editions stopped on the login screen and prompted you to change databases.

  1. Choose Administration → Administrative Options.

    The Administrative Options dialog box appears.

  2. Click the General tab.

    A series of sub-tabs appear.

  3. Click the Active Directory sub-tab.

  4. Under either Standard/Enterprise or WEB, select Attempt login from Active Directory identity.

    The option below it activates.

  5. Select Allow user to be prompted to change database.

  6. Click OK.

    When you next log in, instead of only the FH edition you selected stopping at the login screen so that you can change database, both editions stop on the login screen, regardless of which section you were working in, in the Administrative Options dialog box.

If you are using the Active Directory (AD) integration, the domain of the currently logged-in user was sometimes displayed incorrectly as a combination of the domain the computer is on and the actual user name, instead of the domain of the currently logged-in user.

If you are using the Active Directory (AD) integration, and if you set password complexity rules and not-attempting a login from the network identity with the steps below, FH prompted you to change your password.

  1. Choose Administration → Administrative Options.

    The Administrative Options dialog box appears.

  2. Click the General tab.

    A series of sub-tabs appear.

  3. Click the Security sub-tab.
  4. Under Network, Multi-User, & Internal Messaging, clear Attempt login from network identity.
  5. Under Password Complexity Rules, set parameters as needed.

  6. Click OK.

    The next time you log into FH, you are prompted to change your password, and you should not be.

If you have installed the NEMSIS code set and mapped a cardiac arrest lookup code to a NEMSIS export code with the steps below, the fields for recording who witnessed the arrest did not activate as expected.

  1. Create a new EMS record, or open an existing EMS record as normal.
  2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

  3. Create a new patient/victim record, or select an existing record, and then click Open, as normal.

    The Patient/Victim Information dialog box appears.

  4. Click the Clinical tab.

    A series of sub-tabs appear.

  5. Click the Cardiac Arrest & CPR tab.

    Another series of sub-tabs appears.

  6. On the Basic Cardiac tab, for Cardiac Arrest Type, click the lookup button.

    The Lookup – Cardiac Arrest dialog box appears.

  7. Click New.

    The Code for Cardiac Arrest dialog box appears.

  8. Fill out the Code and Description fields as normal for the lookup code you are creating.
  9. In Export Code, select either NEMSIS codes 2240 or 2245.

  10. Click Save.

    The new code appears in the Lookup – Cardiac Arrest dialog box.

  11. Select the lookup code you create, and then click OK.

    The Arrest Witnessed by area on the tab does not activate as expected.

If you had a future training class with multiple staff members attending the class listed on the department journal, and if you displayed daily reminders with the steps below, the row for the reminder in the dialog box contained a line for each staff member.

  1. Choose File → Daily Reminders.

    The Daily Reminders dialog box appears.

  2. (If necessary) In the lower right corner of the dialog box, click the training class filter icon to display training classes in the dialog box.

    If a training class is listed and there are multiple staff members attending the class, then the row for the reminder in the dialog box contains a line for each staff member, displaying the station, shift, and/or unit information.

    Example: If a training class has 10 staff members attending, the row in the dialog box is 10 lines long.

If you tried to change the incident number for an EMS record to match the incident number of an incident containing a fire report with the steps below, error messages appeared stating that the incident already exists appeared, and the fire report lost the units and personnel data assigned to it.

  1. On the main toolbar, click EMS.

    The EMS/Search & Rescue Report dialog box appears.

  2. Choose Form → Renumber EMS/Search & Rescue Report.

    The Renumber – EMS/Search & Rescue Report dialog box appears.

  3. In New Incident No, type the incident number of the incident record you want the EMS record to be associated with.

  4. Click OK.

    An error message stating that the incident already exists appears, and the fire report loses the units and personnel data assigned to it.

(FH Web) If you are using the Active Directory (AD) integration, and if you enabled attempting a login from the network identity with the steps below, the automatic login did not happen as expected, and you were prompted to enter your password.

  1. Choose Administration → Administrative Options.

    The Administrative Options dialog box appears.

  2. Click the General tab.

    A series of sub-tabs appear.

  3. Click the Security sub-tab.
  4. Under Network, Multi-User, & Internal Messaging, select Attempt login from network identity.

  5. Click OK.

    The next time you log into FH, you are prompted to enter your password, and you should not be.

If you created an EMS record, but did not save it before the security timeout expired and you were logged out by the system, FH discarded the EMS record.

If you specified a specific unit cost for a procedure or medication in the lookup tables and linked an account for payment responsibility for these items, when you created an invoice for the account currently linked to the event, the unit cost for the procedure or medication was not correct on the invoice.

    1. Choose Tools → Lookup Tables.

      The Lookup Tables dialog box appears.

    2. Expand Invoicing and Accounts Receivable Codes, and the select Invoice Items.

    3. Click Setup.

      The Lookup – Invoice Items dialog box appears.

    4. Expand EMS, and the select a medication lookup code.

    5. Click Edit.

      The Code for Invoice Items dialog box appears.

    6. On the Links To tab, under Medication Code(s), verify that the code listed is one you have.
    7. Click the Cost and Class tab.
    8. From Item Cost Calculation, select Use a Specific Unit Cost.
    9. In Specific Unit Cost, enter a cost for the medication.

    10. Click Save.

      The Code for Invoice Items dialog box closes.

    11. Repeat steps d-j for a procedure lookup code.
    12. In the Lookup – Invoice Items and Lookup Tables dialog boxes, click Close.

    1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

    2. Click the Invoicing tab.
    3. Under General Account/Invoicing Options, select Use Account Data for EMS billing Lookup.
    4. Under Require Account Responsibility for Event Types, select EMS Services.
    5. Click OK.
    1. Create a new EMS record, or open an existing EMS record, as normal.
    2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

    3. Click Add.

      The Patient/Victim Information dialog box appears.

    4. In Last Name, type the name of an existing patient/victim that has an existing patient account number, and then press the Tab key on the keyboard.

      The EMS/Search & Rescue Patient/Victim Lookup dialog box appears.

    5. Select the name of the patient with the existing account number, and then click OK.

      The Transfer Patient Details - EMS/Search & Rescue - Patient Past Medical History/Alerts dialog box appears.

    6. Click OK.

      The Patient/Victim Information dialog box populates with information about the patient with the existing account number, and a message prompting you to add this patient record to the responsibility list for the account appears.

    7. Click Yes.
  4. Click the Assessments & Treatments tab.
  5. Add procedure and medication information as normal.
    1. Click the Other tab.

    2. Click Linked Account.

      The Account Link dialog box appears.

    3. Select Create an Invoice to the currently linked account for this event, and then click OK.

      The Invoice dialog box appears and lists the procedure or medication items, but the specific unit costs you defined for the procedure or medication is not correct (the costs are $0).

If you installed the NEMSIS lookup code set, and then required crew member numbers and filled out patient vital information and procedure or medicinal information with steps below, a 2199 error message appears when you tried to specify a staff member’s certification level.

    1. Choose Administration → Administrative Options dialog box.

      The Administrative Options dialog box appears.

    2. Click the Incident tab.

      A series of sub-tabs appear.

    3. Click the EMS/Search & Rescue sub-tab.

      Additional sub-tabs appear.

    4. Click the State Reporting sub-tab.
    5. Under Additional State Reporting Requirements, select Require Crew Member Numbers.
    6. Click OK.
    1. Create a new EMS record, or open an existing EMS record, as normal.
    2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

    3. Add a new patient record, or open an existing patient record, as normal.

      The Patient/Victim Information dialog box appears.

    4. Click the Assessments and Treatments tab.

    5. On the right side of the dialog box, click Add Vitals/Ax.

      The fields in the dialog box update to display fields related to patient vitals.

    6. On the Basic sub-tab, for Staff, click the lookup button and choose the staff member who assessed the patient’s vital signs.
    7. Fill in the fields for the rest of the vital sign information as normal.

    8. On the right side of the dialog box, click either Proc (procedure) or Med (medication), depending on the information you want to enter.

      The fields in the dialog box update to display fields related to patient procedures or medications.

    9. Fill in the fields as normal.
    10. In the lower right corner of the dialog box, click Save, and then click Close.
    1. Click the Other tab.

    2. Click Assign Crew Member Numbers.

      The Assign Crew Member Numbers dialog box appears.

    3. In the row for a crew member, in the ? column next to the Cert Level column, click the lookup button.

      The Lookup - EMS Certification Level dialog box appears.

    4. Select the lookup code for the certification you want, and then click OK.

      The 2199 error appears.

After geocoding locations in FH, only one type of map (road maps) appeared in Google Maps, and ampersands (&) did not display correctly in the information bubbles on the map in Google Earth.

If you launched FH 7.14.19 and logged in, and then launched another session of FH, the following error message appeared when you tried to log in to the second FH session.

Fire access is denied c:docume~1\11057474\locals\temp\fhtemp.dbc

If you have the Ontario 2009 Standard Incident and Injury Report (SIR) recording codes installed, when you enter an incident type of 61 (a type of fire), the arrival date and time fields for the incident become disabled.

Note: Information on updating your Ontario 2009 SIR codes is available in the FIREHOUSE Software Ontario 2009 SIR Update Guide.

  1. Begin a new incident record, as normal.

  2. On the Basic tab, under Incident Type, type or lookup incident type 61.

    Under Times, First Arv Scene and Controlled become grayed out.

If you specified an incident type of 111 (building fire) and selected the option indicating that the fire spread was confined to the object or origin, an incorrect value for the fire spread is set by default, and a validation error appears during the NFIRS validation process at the state and federal level.

  1. Begin an incident record as normal.
  2. In the NFIRS Incident Report dialog box, for Incident Type, specify the lookup code 111 (building fire) as normal.
  3. Fill out the rest of the fields on the Basic tab as normal.
  4. Click the Additional Reports tab.

  5. Click Fire.

    The Fire Report dialog box appears.

  6. Fill out the fields on the Property tab as normal.
  7. Click the Fire tab.
  8. Select Fire spread was confined to the object of origin.
  9. Fill out the rest of the fields on the Fire tab as normal.
  10. Click Save, and then click Close.

  11. Click Structure Fire.

    By default, the Structure Fire Report dialog box appears, open to the Basic tab. Under Fire Origin & Spread, Fire Spread has a value of 1 (confined to the object of origin), and Check if no flame spread OR same as material first ignited OR unable to determined is selected by default.

    As a result, a validation error appears during the NFIRS validation process at the state and federal level.

If you are using the NEMSIS code set and add a second patient to a completed EMS record, and if the NEMSIS validation runs and fails, you are not able to add a second patient to the EMS record.

  1. Open a completed EMS record that contains one patient as normal.
  2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

  3. In the lower right corner of the tab, click Add.

    If the NEMSIS validation runs and fails, you are not able to add a second patient to the EMS record.

If the rule for allowing incomplete reports to be saved is disabled, and you were working on an EMS patient report when you left FH open and idle for a long period of time with the steps below, FH logged you off and the incomplete report was not saved.

  1. Choose Administration → Administrative Options.
  2. Select the Incident → All Incidents → General tab.
  3. Under Rules, clear Allow incomplete reports to be saved.
  4. Click OK.
  5. Begin an EMS record as normal, and enter patient data as normal.

  6. Leave FH open and idle for a long period of time.

    FH automatically logs you off, and the incomplete patient report, and sometimes the entire EMS report, is not saved.

If you had a fire incident with less than one acre burned and exported it to NFIRS with the steps below, the exported report indicated that the acres burned was zero, instead of leaving the value blank.

  1. Begin an incident report as normal.

  2. In the NFIRS Incident Report dialog box, on the Basic tab, for Incident Type, specify any of the 100 incident codes.

    Example: 111, Building fire.

  3. Click the Additional Reports tab.
  4. Click Fire.
  5. For Acres Burned, select Less than One Acre.
  6. Complete all other required fields for the incident, and save it.
  7. Choose File → NFIRS 5 Incident Reporting → Export NFIRS 5 Transaction File.
  8. In the NFIRS 5.0 Export Wizard that appears, select Export Completed Incident Transactions and Department Information, and then click Next >.
  9. In From Date and To Date, specify a date range containing the incident.
  10. Select Export all records in this range as new transaction even if previously exported.
  11. Click Next >.
  12. On the Output Files screen of the wizard, click Next >.
  13. On the Completion screen of the wizard, click Next >.
  14. On the confirmation screen of the wizard, click Finish.
  15. (If prompted to create a directory or overwrite a file) Click Yes.

  16. In the export confirmation dialog box that appears, click Yes.

    The NFIRS export completes successfully, but the file that is created during the export contains a 0 for the number of acres burned, instead of being blank.

The following enhancements were implemented this release.

When an automated task runs across a mapped drive, if the mapping is lost while the task is running, FH now retries the connection until it can connect again with the mapped drive, and then finishes running the task.

In FH, you are able to export queries to Microsoft Excel, but not reports. When you generate a report and the Output Report To dialog box appears, the Other File Type option was active and implied that you could export the report to an Excel spread sheet. This option is now deactivated when you generate a report.

Due to a change in the installation process for FH Web, a CPU-intensive component of the installation (FHWebEditionServerSetup.exe) is no longer used, and has been removed from the installation CD.

FH now uses Microsoft Word 2007 and 2010's shared dictionaries for checking spelling.

In the EMS module, on a patient/victim record, if you gathered vitals data and saved it as a record, you can replicate that data to create another vitals record. You are now also prompted as to whether or not you want to replicate any data entered into pre-defined (PD) user fields in the vitals record.

To comply with NFIRS rule changes, if the alarm date of January 01, 2013 or later, incidents of type 320:

  • Can no longer have a hazardous material report associated with them.
  • Can export EMS module data.

Some validation messages in FH related to civilian causalties and EMS reports have been changed from error messages to informational messages.

The following NEMSIS files have been updated on the FH installation CD in the State directory, and on the Firehouse web site.

  • NemsisAL.FHz
  • NemsisAL2.FHz
  • NemsisGA2.FHz
  • NemsisID.FHz
  • NemsisID2.FHz
  • NemsisIL2.FHz
  • NemsisOH.FHz
  • NemsisOH2.FHz
  • NemsisUT.FHz
  • NemsisUT2.FHz
  • NemsisVA2.FHz
  • NemsisWI2.FHz
  • NemsisPatientExport.FHz

Because a database audit log query on a large database can take anywhere from several minutes to several hours, filtering options have been added to reduce the number of audit records the query must process, and a status bar has been added to indicate the progress of the query through the records.

To find the new features, do the following.

  1. Choose Administration → Database Audit Log.  

    The Database Audit Log dialog box appears.

  2. Click the Data tab.

  3. From Show Detail Changes in Database, choose the record database you want to view audit records for.

    New fields for specifying additional filters on the audit log data activate. The Run Audit Log and Purge Audit Log buttons are also new on this tab.

  4. Select one of All Transactions, Record Created Transactions, Record Modified Transactions or Record Deleted Transactions.
  5. (Optional) For Between and And, specify a data range to further filter the audit log records to examine during the query.

  6. Click Run Audit Log.

    The new status bar appears to indicate the progress of the query through the audit records.

    When the query completes, records that match the criteria appear under the Description of Record.

  7. Select the audit record you want to view detailed information for, and then click Full History for Highlighted Record.

    The Record Modification History dialog box appears, listing additional information.

  8. Click Close.

    1. Click Purge Audit Log.

      The Enter a Value dialog box appears.

    2. In Purge logins prior to, specify the date you want to clear the records before, and then click OK.
  10. Click Close.

FH now supports displaying violation photographs, taken with an iPad running FHinspector and attached to a violation report. The photographs themselves are stored on the FH Cloud, and a link to the photographs is attached to the violation record in FH.

To find and use the new feature, do the following.

  1. On the main toolbar, click Inspect.

    The Inspection dialog box appears.

  2. Open an inspection that was performed on an iPad running FHinspector, which has a violation with a photo attached, as normal.

  3. Click the Violations tab.

  4. Select the violation that has the photo attached, and then click Open.

    The Violation Detail dialog box appears, with the new Attachments button and two accompanying check boxes in the lower left corner of the dialog box.

    If the first checkbox is selected, the attachment of a violation photo is required. If the second checkbox is selected, one or more violation photos are attached, and a number indicating how many photos are attached appears.

  5. Click Attachments.

    The Attachments & Signatures dialog box appears, listing the links to the violation photos taken during the inspection.

  6. Select the link to the violation photo you want to view, and then click Open.

    A web browser opens, and the photo appears in it.

If you have more than one violation code set installed in FH, you can now select lookup codes from the violation code set you defined as the default set, and you can manually enter the lookup codes from the other (non-default) violation code sets.

To find the new feature, do the following.

  1. Choose Reports → Occupancy Management Reports.  

    The Reports dialog box appears.

  2. Expand Occupancy Management Reports → Inspection Master Reports.

  3. Select Inspections Violations by Violation Code, and then click Run.

    The Output Report To dialog box appears.

  4. Under Select Output Type, select the option corresponding to how you want to display the report, and then click OK.

    The Query Parameters dialog box appears.

  5. In the row for Violation Code, in the ? column, click the lookup button.

    The Lookup - Violation Codes dialog box appears, listing the lookup codes in the default violation code set.

You can now create a custom expression that adds a time stamp to the default notes for invoice item lookup codes. This time stamp helps differentiate between invoice items, such as when you have multiple inspections of an occupancy on the same date.

To find the new feature, do the following.

  1. Choose Tools → Lookup Tables.

    The Lookup Tables dialog box appears.

  2. Expand Invoicing and Accounts Receivable Codes, and then select Invoice Items.

  3. Click Setup.

    The Lookup - Invoice Items dialog box appears.

  4. Expand a lookup code group, select an invoice item, and then click Edit.

    The Code for Invoice Items dialog box appears for that invoice item.

  5. Click the Default Notes tab.

    To the right of Enter a custom notes expression to override the notes generated by the system for this billing item, a new lookup button appears.

  6. Click the new lookup button.

    The Invoice Item Custom Notes Expression dialog box appears.

  7. Use the dialog box as normal to create a custom expression that includes a time stamp for the invoice item.
  8. Click OK.
  9. In the Code for Invoice Items dialog box, click Save.
  10. In the Lookup - Invoice Items and Lookup Tables dialog boxes, click Close.

A new advanced function (ListCount) is now available in FH for building system rules. This function returns a count of the number of records in a list, and can use the following optional parameters.

  • expC1: The name of the alias to count records in. If not provided, the current alias is assumed.
  • expC2: Filter to use. If provided, only records for which this expression is true are counted.

To find the new function, do the following.

  1. Choose Administration → System Rules and Default Values.

    The System Rules and Default Values dialog box appears.

  2. Expand any group in the dialog box, and then select a data table.

  3. Click Setup.

    The System Rules and Default Values dialog box appears.

  4. On the Field-Level Rules and Default Values tab, select a field you want to work with.

  5. Click Add.

    The Select Rule Type dialog box appears.

  6. Select any of the rule types in the dialog box, and then click OK.

    A dialog box related to the rule type you selected appears.

  7. On the right side of the dialog box, click the lookup button associated wtih specifying an expression for the rule.

    The System Rule Expression dialog box appears.

  8. Click the Advanced tab.

  9. Under Advanced Functions, scroll down until the ListCount function appears.

When you add a patient to an EMS record, the patient record is now automatically saved, and any validation errors that currently exist are ignored (the validation window does not appear).

Note: If you click Cancel after adding a patient record, only changes made after the patient was added are discarded.

To find the new function, do the following.

  1. Open or begin an EMS record as normal.
  2. In the EMS/Search & Rescue Report dialog box, click the Patients/Victims tab.

  3. In the lower right corner of the tab, click Add.

    The patient record automatically saves.