Data Outlier Policy

From Standard Operating Guidelines
Revision as of 06:43, 22 January 2026 by Mfrdmanager (talk | contribs) (Created page with "==Section 1 - ADMINISTRATIVE== ==110.40 Data Outlier Policy== ===PURPOSE:=== To ensure consistent and standardized data collection, analysis, and reporting for the Maitland...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Section 1 - ADMINISTRATIVE

110.40 Data Outlier Policy

PURPOSE:

To ensure consistent and standardized data collection, analysis, and reporting for the Maitland Fire Rescue Department (MFRD) in alignment with recognized industry standards and best practices. This policy defines the criteria used to determine which data elements are included or excluded when reporting call processing, turnout, travel, and overall response times. MFRD will apply this policy to support the following reporting and compliance needs: internal statistical reporting; Insurance Services Office (ISO) evaluations; Commission on Fire Accreditation International (CFAI); Commission on Accreditation of Ambulance Services (CAAS); and National Fire Protection Association (NFPA) standards. Based on the requesting agency, additional specific outliers may be excluded from reported datasets to meet applicable reporting standards and requirements.

PROCEDURE:

  • Data sets are compiled and obtained through both CAD and RMS systems. RMS data will serve as the primary data source, with CAD data used for backup and validation.
  • All data will be calculated using the 90th percentile method.
  • All data for each incident category (EMS, Technical Rescue, Hazardous Materials, and Fire) will be used to determine each respective incident category and overall department response times. This standard criterion will be applied to the initial dataset before any additional measures or specific criteria are calculated.
  • The following incident criteria will be excluded when calculating the Maitland Fire Rescue Department’s (MFRD) Effective Response Force (ERF) response data:
    • Non-emergency responses, including downgraded or upgraded incidents
    • Incidents where units staged prior to arrival on scene
    • Incidents canceled prior to arrival on scene
    • Incidents where the location could not be found and no on-scene time was recorded (Good Intent)
    • Incidents occurring outside the City of Maitland jurisdiction
  • All data falling outside of these parameters will remain available and may be used for internal analysis.