Available Ohio Information

FIREHOUSE Software is fully compliant with NEMSIS and the Ohio EMS requirements. You will need to perform multiple items to make your system compliant, and this email provides information on these items.

The Ohio Department of Commerce Division of State Fire Marshal accepts FIREHOUSE Software fire incident records. After you have created your incident file, go to https://www.comapps.ohio.gov/sfm/fire_apps/fmpr/nfirs/login.aspx, and follow the steps below:

  1. Your “User ID” is your 5 digit FDID number with no dashes (89000).
  2. Your “Password” is your 5 digit Zip code with “web” at the end (43068web).
  3. After completing your contact name & email address, press the Select button.
  4. Locate the .INC file you created from the NFIRS Transaction File wizard, click Open (as you would for an email attachment). **You do not need to send your .DEP Department Information File.
  5. Press Upload File(s) then watch for the validation message under Uploaded Files. You should see a ‘Successful’ message.
  6. Log out when completed. A few hours later, return to the web site, log in and select Monthly Totals of All Incidents by FDID. This will display the total number of reports uploaded for each month. For statistics by Fire Department, by County, or by State, choose the Ohio Statistics button.

After discussing the requirements with both NFIRS & ODNR, Ohio has decided to focus on using the Fire Module rather than the Wildland Fire Module.

According to the specification:

If the Incident Type is 140-143 or 160, 170-173 then either the Fire module or the Wildland module is required. One of the two must be completed. If the Incident Type is 561, 631 or 632 the Fire Module is not allowed but the Wildland Module may be optionally completed in addition to the Basic Module for these incidents.

Fire departments should use the Fire Module, especially including the number of acres involved & dollar loss. Ohio reserves Incident Type 140 for mulch fires only.

To indicate Wildland Fires in Ohio a Fire Module incident should be completed for fires occurring in the following fuels:

  • 141 Forest, Woods, or Wildland Fire
  • 142 Brush or Brush and Grass Mixture Fire
  • 143 Grass Fire
  • 170 Cultivated Vegetation, Crop Fire, Other
  • 171 Cultivated Grain, Crop Fire

If an incident is fire related, choose an Incident Type code between 111-173. Incident Type 100 or 110 is not accepted. If a Fire Module report has the Heat Source indicating Equipment Involved (code 10-13), then the Type of Equipment must be listed in the Fire Module.

(Last updated 10/28/2008)

You may have recently received the notice below from the OHIO Division of EMS.

“ATTENTION EMSIRS-1 USERS: The EMS Board voted October 19, 2011 to terminate the use of EMSIRS-1 on December 31, 2012. If your current software is not NEMSIS compliant, you will need to contact your vendor for support. Any incident that begins after January 1, 2013 must be in EMSIRS-2 format.”

FIREHOUSE Software is fully compliant with NEMSIS and the Ohio EMS requirements. You will need to perform multiple items to make your system compliant, and this email provides information on these items.

To ensure your FIREHOUSE Software system is Ohio NEMSIS compliant

  1. Verify you are running FH version 7.9.14 or higher.
    (This is accomplished from inside FH on the Help menu > About FIREHOUSE Software. If you do not have this version or a higher version, contact FH technical support so we may provide you a link to the latest version. If your Annual Maintenance Agreement has expired, please contact your local sales representative to renew your agreement and receive this upgrade.)
  2. Archive your current EMS incident records.
    (We recommend making this change before 1-1-2013 – but you can change at any time. Steps on how to archive your files in FH are available online in a video webcast or using the instructions in the WebHelp topic ” Archive your database.”)
  3. Verify if you have custom system rules and default values presently running in FIREHOUSE Software EMS Module.
    (After you load the new code set your defaults values or system rules will not run until you’ve modified them with the new code set. The codes in the new EMSIRS-2 NEMSIS code set are different from current EMSIR-1 codes.) From the Reports menu > Administrative Reports, run the report User Defined System Rules/Default Values. Run the report for just EMS. Type “EMS” in the Database Name field. (Optional) Copy your existing system rules by selecting the Options button > Copy To. You will need to repeat this for each area of EMS system rules/default values you wish to copy.
  4. Download these items from the FIREHOUSE Software Website.
  • Ohio EMS Components File (1 of 2)
  • Ohio EMS Components File (2 of 2)
  • Ohio NEMSIS Patient Export
  • Ohio NEMSIS Implementation Instructions

(Last updated 12/14/12)

The Ohio Department of Public Safety Emergency Medical Services Division requires FIPS City Codes to be associated with City/State/Zip lookup codes in your FH system.

EMS incident records with non-Ohio County codes will be rejected when processed. Use only the numeric County codes provided and installed with the Ohio State EMS Data Collection code set. If you have alternative County codes, you will need to merge these codes with the Ohio numeric codes.

(Last updated 11/13/08)

Keep In Touch

Wave 2024 featuring ESO Training Academy Agenda is LIVE! Save the date for April 2-5, 2024 and take advantage of our lowest pricing available starting TODAY!