Reports Updates

Reports Updates

Video

Video posted at the end of the month.

Enhancements:

1) NFIRS EMS Data Source with NERIS Fields

  • What - The NFIRS EMS data source in Ad Hoc reporting has been enhanced with four new NERIS-specific fields to support expanded data collection and reporting capabilities. These new columns include ePCR Number, Patient Evaluation Status, Patient Status after Intervention, and Transport Outcome, all of which behave consistently with their respective data types and integrate seamlessly with existing Ad Hoc functionality for sorting, filtering, grouping, and analysis.
  • Why - This enhancement was implemented due to customer request to accommodate the transition to the NERIS framework and provide comprehensive reporting capabilities for the expanded data collection requirements introduced with this new system.
  • How - These new fields are automatically available to users with existing access to the NFIRS EMS data source, requiring no additional permission changes or configuration.
    • Navigate to Ad Hoc reporting
    • Select NFIRS EMS as your data source
    • Access the new fields in the Columns tab alongside existing NFIRS EMS fields
    • Use these columns in Criteria, Grouping, and Summary Rows as needed
    • Apply sorting and filtering functions normally
    • List-type fields will display human-readable values automatically
  • Use Case - Emergency medical services departments can now generate comprehensive reports that include patient care record numbers for cross-referencing with ePCR systems, analyze patient evaluation outcomes before and after interventions to measure treatment effectiveness, and track transport decisions and outcomes to optimize resource allocation and improve patient care protocols across their service areas.

2) NFIRS Firefighter Casualty Data Source with NERIS Fields

  • What - The NFIRS Firefighter Casualty data source in Ad Hoc reporting has been significantly expanded with twenty-one new NERIS-specific fields to provide comprehensive data collection and analysis capabilities for firefighter casualty incidents. These new columns include critical incident details such as rescue actions, environmental conditions, personnel information, protective equipment usage, and operational factors like Mayday procedures, RIT activation, and incident command establishment, all fully integrated with Ad Hoc's standard reporting functionality.
  • Why - This enhancement was implemented due to customer request to support the transition to the NERIS framework and enable detailed analysis of firefighter casualty incidents with expanded data fields that provide deeper insights into incident circumstances, response effectiveness, and safety protocols.
  • How - These new fields are automatically available to users with existing access to the NFIRS Firefighter Casualty data source without requiring any permission changes or additional configuration.
    • Navigate to Ad Hoc reporting
    • Select NFIRS Firefighter Casualty as your data source
    • Access all twenty-one new NERIS fields in the Columns tab
    • Utilize these columns in Criteria, Summary Rows, Grouping, Sorting, and Filters
    • List fields will display as dropdown menus with selectable options
    • Boolean fields will appear as checkboxes for true/false selections
    • Comma-separated text fields will display full text strings for comprehensive data analysis
  • Use Case - Fire departments can now generate detailed casualty analysis reports that track rescue operations from initial response through extraction, analyze the effectiveness of safety protocols by examining PPE usage and RIT activation patterns, identify environmental hazards and impediment conditions that contribute to firefighter injuries, and evaluate incident command procedures and company continuity practices to enhance future emergency response safety and operational effectiveness.

3) New Incident Report (NERIS) Data Source

  • What - A new Ad Hoc data source called Incident Report (NERIS) has been introduced to provide optimized reporting capabilities specifically for agencies using the NERIS documentation framework. This streamlined data source features a curated set of NERIS-relevant columns, integrated hazmat fields from neris_hazsit, and enhanced performance through the removal of unnecessary joins and deprecated legacy NFIRS fields, while the existing Incident Report data source has been renamed to Incident Report (NFIRS) for clear differentiation between the two reporting frameworks.
  • Why - This enhancement was implemented due to customer request to provide a cleaner, more performant reporting solution that eliminates confusion from deprecated fields and unused columns while ensuring scalability and maintainability for agencies transitioning to the NERIS framework.
  • How - The new data source is automatically available to NERIS-enabled agencies without requiring any permission changes or manual configuration.
    • Navigate to Ad Hoc reporting
    • NERIS-enabled agencies will automatically see Incident Report (NERIS) as their primary data source option
    • NFIRS agencies will continue to see Incident Report (NFIRS) as their data source
    • Select the appropriate data source based on your agency's framework
    • Access the streamlined column set in the Columns tab with NERIS-specific fields
    • Utilize integrated hazmat fields for comprehensive hazardous situation reporting
    • Existing reports built with the legacy NFIRS data source will continue to function normally
  • Use Case - Fire departments using NERIS can now generate incident reports with significantly improved performance and data clarity, focusing on relevant NERIS fields without navigating through deprecated legacy columns, while hazmat teams can leverage integrated hazardous situation fields to create comprehensive reports that combine incident details with specific hazmat response data, and agencies can confidently build new reports knowing they are working with current, maintained data structures that will scale with future NERIS enhancements.


4) Incident Report Fire Fields (NERIS) Child Data Source

What - A new child data source called "Incident Report Fire Fields" has been added under the Incident Report (NERIS) parent data source to provide specialized fire-related reporting capabilities. This enhancement consolidates twenty-nine comprehensive fire-specific columns that combine legacy NFIRS fields (such as Heat Source, Item First Ignited, Fire Spread, and Cause of Ignition) with new NERIS-specific attributes including:

  • Suppression Appliance
  • Investigation Needed
  • Fire Water Supply
  • Fire Extension
  • Fire Damage
  • Room of Origin
  • Structure Fire Cause / Structure Cause of Ignition
  • Outside Fire Cause of Ignition

All fields are optimized with human-readable lookup values and maintain a strict 1:1 relationship with the parent source to preserve accurate report row counts and prevent data duplication. The data source supports full Ad Hoc functionality including sorting, grouping, criteria filtering, and summary rows, with categorical fields displayed as readable values rather than codes.

Why - This enhancement was implemented to isolate and expand fire-related data fields without bloating the primary Incident Report (NERIS) data source, providing fire departments with specialized reporting capabilities that combine legacy compatibility with enhanced NERIS framework attributes. By consolidating fire-specific data into a dedicated child data source, users can more efficiently analyze fire patterns, causes, suppression methods, and damage assessments without navigating between different datasets or losing data integrity, while ensuring scalability and performance optimization for large-scale clients.

How - The child data source is automatically available to NERIS-enabled agencies when using the Incident Report (NERIS) parent source, requiring no additional permissions or configuration.

  • Navigate to Ad Hoc reporting from the main menu
  • Select Incident Report (NERIS) as your primary data source
  • Click "Add Child Data Source" and choose "Incident Report Fire Fields"
  • Access twenty-nine fire-specific columns in the Columns tab
  • Select specific fire-related columns from both legacy NFIRS fields and new NERIS fields
  • Utilize both legacy NFIRS fields and new NERIS attributes in Criteria, Grouping, and Summary Rows
  • Configure your report using standard Ad Hoc features including criteria filtering, grouping, and sorting
  • NERIS fields will display human-readable values through automatic lookup joins
  • Boolean, list, and comma-separated text fields behave consistently with their data types
  • Export your completed report to CSV, PDF, or XML formats as needed
  • Note that this child data source can only be used when attached to the Incident Report (NERIS) parent dataset

Use Case - Fire departments can now create specialized fire incident reports that analyze suppression effectiveness by examining appliance types and water supply sources, investigate fire causation patterns using both legacy heat source data and enhanced NERIS cause categories, and assess fire spread and damage metrics across multiple story structures to identify prevention opportunities. For example, a fire department analyst can select the Incident Report (NERIS) parent dataset, attach the Incident Report Fire Fields child data source, and include columns for Property Type, Suppression Appliance, Water Supply, Fire Extension, and Fire Damage in a single unified report. They can then group by Property Type and Suppression Appliance to identify patterns in suppression effectiveness, filter for incidents where Investigation Needed is marked as "Yes," and generate comprehensive fire investigation reports that combine room of origin analysis with factors contributing to ignition for improved fire prevention planning, resource allocation strategies, and departmental performance metrics.


5) Custom Questions Integration for ePCR Vital Sign Data Source

  • What - The ePCR Vital Sign Ad Hoc data source has been enhanced to dynamically integrate custom questions defined under the eVitals NEMSIS root, allowing agencies to report on custom data captured at the vital sign level. Custom questions with root field codes beginning with eVitals are automatically surfaced as columns with appropriate data type behavior, including boolean, numeric, datetime, and comma-separated multi-select formats, while maintaining accurate data binding to epcr_vital_sign_id for precise row-level reporting and full functionality across all Ad Hoc capabilities.
  • Why - This enhancement was implemented due to customer request to provide comprehensive reporting capabilities for agency-specific custom data collection at the vital sign level, enabling specialized analysis and documentation requirements that extend beyond standard NEMSIS fields.
  • How - Custom question columns are automatically available to agencies that have configured eVitals custom questions, requiring no additional permissions or manual setup.
    • Navigate to Ad Hoc reporting
    • Select ePCR Vital Sign as your data source
    • Access custom question columns in the Columns tab alongside standard vital sign fields
    • Custom columns will be labeled based on your eVitals question configuration
    • Use these dynamic fields in Criteria, Grouping, Summary Rows, and Sorting functions
    • Multi-select questions will display as comma-separated values
    • Data type behavior matches your question configuration (boolean, numeric, datetime, etc.)
    • Custom columns are visible only to your agency for data security
  • Use Case - Emergency medical services can now generate comprehensive vital sign reports that include agency-specific protocols such as custom pain assessment scales, specialized monitoring equipment readings, or department-specific clinical observations, allowing paramedics to analyze trends in custom vital sign parameters alongside standard measurements, track compliance with local medical protocols, and provide detailed documentation for quality assurance programs that incorporate both NEMSIS-standard and locally-defined clinical data points.

6) NERIS Compliance Reports for Data Quality Assurance

  • What - Two new FDR reports have been added to help Fire/EMS departments identify and resolve data compliance issues before migrating to the National Emergency Response Information System (NERIS) or troubleshoot existing NERIS synchronization errors. The "FDR-NFIRS: Apparatus without Fire Station Assignments" report identifies unassigned apparatus that cannot be properly tracked in NERIS reporting, while the "FDR-NFIRS: Fire Stations with Duplicated Addresses" report detects station address duplications that may cause migration failures or ongoing synchronization problems, with both reports serving as proactive quality assurance tools to ensure seamless data integration with national reporting standards.
  • Why - These reports were implemented due to customer request to provide departments with essential tools for identifying apparatus assignment issues and station address duplications that can cause NERIS migration failures or ongoing synchronization errors, ensuring compliance with NERIS data formatting and completeness standards required for successful reporting to state and federal agencies.
  • How - These reports are automatically available to all active accounts and can be accessed by users with appropriate report viewing permissions.
    • Navigate to Reports from the main dashboard
    • Select Ad-Hoc Reports from available options
    • Open the FDR - NFIRS folder
    • Click FDR-NFIRS: Apparatus without Fire Station Assignments to generate apparatus assignment compliance report
    • Click FDR-NFIRS: Fire Stations with Duplicated Addresses to generate station address duplication report
    • Review results for compliance issues (blank reports indicate no conflicts detected)
    • Export reports as needed for distribution and correction tracking
    • Users need report viewing permissions, Reports module access, station and apparatus data viewing permissions, with administrative access recommended for full oversight
  • Use Case - Fire departments preparing for NERIS migration can proactively identify and resolve apparatus assignment gaps before they cause system integration failures, while departments currently using NERIS can troubleshoot synchronization errors by running these reports after station reorganizations or apparatus transfers to ensure all equipment remains properly tracked, and administrative staff can coordinate with station commanders and dispatch centers to verify correct station addresses and apparatus assignments, maintaining compliance with national reporting standards and preventing critical data synchronization issues that could impact federal and state reporting capabilities.


7) New NERIS Columns to NFIRS Civilian Casualty

  • What - We have expanded the existing NFIRS Civilian Casualty data source in Ad Hoc with additional NERIS framework columns that capture critical details about rescue efforts, impediments, casualty causes, and environmental conditions. The new columns include:
    • Rescue Type (Varchar, List)
    • Occupant Presence Known (Varchar, List)
    • Initial Primary Action (Varchar, List)
    • Primary Rescue Action Taken (Text, Comma Separated List)
    • Impediment Conditions (Text, Comma Separated List)
    • Room Type (Varchar, List)
    • Elevation Type (Varchar, List)
    • Was the Space Isolated from Gas/Heat? (Boolean)
    • Removal Path Type (Varchar, List)
    • Fire Relative Times – Date (Date)
    • Fire Relative Times – Time (Time)
    • Casualty Type (Varchar, List)
    • Cause of Casualty (Varchar, List)

      All new fields support full Ad Hoc functionality including sorting, grouping, criteria filtering, and summary rows, with multi-value fields displaying as comma-separated lists and boolean fields returning clear true/false values.

  • Why - The migration to NERIS requires enhanced casualty documentation that captures more comprehensive rescue operation details and environmental factors affecting civilian casualties. These additional data points enable more thorough analysis of rescue effectiveness, identification of impediments that impact outcomes, and better understanding of casualty causes and circumstances.
  • How - To access the enhanced civilian casualty data:
    • Navigate to Ad Hoc reporting from the main menu
    • Select NFIRS Civilian Casualty as your data source
    • Choose from the expanded list of available columns including the new NERIS fields
    • Apply filters, sorting, grouping, and summary functions to any of the new columns
    • Note that multi-value fields will display as comma-separated lists in your reports
    • Boolean fields will show clear true/false values for easy filtering and analysis
    • Export your completed reports to standard formats (CSV, PDF, XML) with all new field data included
  • Use Case - A fire safety officer analyzing rescue operation effectiveness can now create detailed reports showing the relationship between impediment conditions, rescue actions taken, and casualty outcomes. They can filter for incidents where occupant presence was known, group by rescue type and primary action taken, and analyze whether space isolation from gas/heat correlates with better casualty outcomes, providing actionable insights for improving rescue protocols and training programs.


8) Health and Wellness Exposure Personnel Data Source

  • What - We have added a new child data source called Health and Wellness Exposure Personnel to the parent Health and Wellness Exposure dataset in Ad Hoc reporting. This enhancement enables granular analysis of individual personnel within exposure events, with each row representing a specific person associated with an exposure ID. The data source captures comprehensive personnel attributes across four exposure categories with detailed fields including:
    • Biological: route, equipment, duration, agent type, health effects, MSDS links
    • Chemical: route, equipment, type, toxicity, duration, health effects, MSDS links
    • Physical: environment, equipment, actions taken, work/rest cycles, limitations
    • Traumatic: environment, incident type, years of service, event level, debrief status, duty considerations

      All coded fields are automatically translated into natural language values, and the data source supports child joins to the Personnel dataset for complete individual tracking.

  • Why - Health and wellness officers need the ability to analyze exposure data at the individual personnel level rather than just at the event level, enabling more precise tracking of health impacts, compliance monitoring, and risk pattern identification across different exposure types and individual circumstances.
  • How - To access the personnel-level exposure data:
    • Navigate to Ad Hoc reporting from the main menu
    • Select Health and Wellness Exposure as your parent dataset
    • Click Add Child Data Source and choose Health and Wellness Exposure Personnel
    • Optionally add Personnel as an additional child data source to link exposure records to specific individuals
    • Select the specific exposure category fields you need (biological, chemical, physical, or traumatic)
    • Configure your report using standard Ad Hoc features including criteria filtering, grouping, and sorting
    • Note that all coded values will display as human-readable text rather than raw codes
    • Export your completed reports with individual-level exposure analysis
  • Use Case - A health and wellness officer investigating chemical exposure patterns can select the Health and Wellness Exposure parent dataset, attach both the Health and Wellness Exposure Personnel and Personnel child data sources, then analyze chemical exposure routes, equipment usage, and health effects by individual firefighter demographics such as years of service or department assignment, enabling targeted safety improvements and personalized health monitoring protocols.


9) Custom Questions in ePCR Signature

  • What - We have expanded the ePCR Signature data source in Ad Hoc to include custom questions tied to NEMSIS eOther.SignatureGroup (eOther.12 – eOther.21) as dynamic columns. Each custom question column is mapped to the associated epcr_signature_id and automatically adopts the correct data type including numeric, datetime, boolean, and text formats. Multiple-select questions display as comma-separated values, and columns only appear for custom questions configured in the client's account to ensure security and relevancy. All custom signature question columns support full Ad Hoc functionality including criteria filtering, grouping, sorting, summary rows, and filtering operations.
  • Why - EMS agencies need complete reporting visibility into custom signature-related data captured during the ePCR workflow, as the previous gap in custom question availability limited comprehensive analysis of signature processes and compliance tracking for agency-specific or state-specific requirements.
  • How - To access custom signature questions:
    • Navigate to Ad Hoc reporting from the main menu
    • Select ePCR Signature as your data source
    • Custom questions with NEMSIS roots eOther.12 – eOther.21 will automatically appear as available columns
    • Select the specific custom question columns relevant to your reporting needs
    • Apply standard Ad Hoc functions including filtering, grouping, and sorting to these columns
    • Note that data types will be automatically respected (numeric values, proper datetime formats, Yes/No for boolean fields)
    • Multi-select question responses will display as comma-separated lists
    • Export your reports with complete custom signature question data included
  • Use Case - An EMS compliance officer monitoring adherence to state-specific signature requirements can now create reports that include both standard ePCR signature data and custom questions such as "Supervisor Review Required" or "Special Circumstances Noted," enabling comprehensive tracking of signature compliance across all personnel and identifying patterns in custom question responses that may indicate training needs or process improvements.


10) Decimals Input for Charts

  • What - We have added a new "Decimals" input field to Ad Hoc Charts that allows users to control the number of digits displayed after the decimal point for computed measure results. This field appears under the existing "Column for Aggregation" dropdown when configuring any chart type and accepts numeric input up to a maximum value of 30. The decimal formatting applies consistently across all chart types including Gauge, Bar, Column, and Line charts, affecting displayed values in gauge charts, tooltip hover pop-ups in interactive charts, and exported chart values. This functionality mirrors the existing decimals control already available in Summary Columns, providing unified numeric formatting throughout Ad Hoc reporting.
  • Why - Charts previously displayed computed measure results with excessive decimal precision (up to 13 digits), creating unsuitable visualizations especially in Gauge charts where decimal-heavy values are prominently displayed, and users had no control over rounding unlike other Ad Hoc features.
  • How - To control decimal precision in charts:
    • Create or edit a chart in Ad Hoc reporting
    • Navigate to the chart configuration section
    • Locate the new "Decimals" field below the "Column for Aggregation" dropdown
    • Enter a numeric value (0-30) to specify the desired number of decimal places
    • The formatting will immediately apply to gauge chart displayed values, hover pop-ups, and tooltips
    • Export your charts to CSV, PDF, or XML with consistent decimal formatting
    • Note that even whole-number measures will display with the specified decimal places (e.g., "2.00" when Decimals = 2)
  • Use Case - An EMS administrator creating a performance dashboard with gauge charts showing average response times can now set the decimals field to 2, ensuring that response times display as clean, readable values like "8.45 minutes" instead of "8.4515151515151 minutes," making the dashboard more professional for executive presentations and improving data clarity for stakeholders reviewing key performance indicators.


11) Minor Updates

  • What - We have added the Patient Destination Odometer Reading of Responding Vehicle (eResponse.21) field to ePCR Reports in Ad Hoc. This NEMSIS-standard field captures the vehicle's odometer reading when arriving at the patient's destination, providing additional vehicle tracking data within existing ePCR reporting capabilities. The field supports standard Ad Hoc functionality including sorting, grouping, criteria filtering, and summary operations.
  • Why - EMS agencies require complete vehicle tracking data for mileage reporting, fleet management, and operational analysis, and the addition of destination odometer readings ensures comprehensive documentation of vehicle usage throughout the entire call cycle.
  • How - To access the new odometer field:
    • Navigate to Ad Hoc reporting from the main menu
    • Select any ePCR Reports data source
    • Locate Patient Destination Odometer Reading of Responding Vehicle (eResponse.21) in the available columns list
    • Include this field in your reports alongside other vehicle or response data
    • Apply standard Ad Hoc functions such as filtering, sorting, and grouping as needed
    • Export reports with complete vehicle odometer tracking data
  • Use Case - A fleet manager analyzing vehicle usage patterns can now create comprehensive mileage reports that include both scene arrival and patient destination odometer readings, enabling accurate calculation of total miles driven per call and supporting vehicle maintenance scheduling, fuel cost analysis, and fleet utilization assessments.




    • Related Articles

    • Reports Module Updates

      Video New Feature What: Multi-Agency Dataset Sharing Tool Why: Agencies with a Parent / Child data relationship want control of what data is being shared. How: Go to the Reports Module > Set Up > Multi-Agency Dataset Sharing Select the Parent Agency ...

    • ePCR Release Notes : June 2025

      Video New Features 1. ePatient.25 Patient's Sex This critical patch implements NEMSIS 3.5.0 compliance requirements by introducing the new ePatient.25 - Patient's Sex field in response to federal regulatory changes. Due to a Presidential Executive ...

    • Reports Module Updates - Sept 2025

      Video Video will be posted by October 3rd. New Feature 1 - New Email Option for Timed-out Ad Hoc Downloads What - A new fallback email delivery system has been implemented for Ad Hoc report downloads that experience timeout errors during file ...

    • Frequently Asked Questions- Reports

      Purpose Statement This article addresses common questions about Ad Hoc reporting functionality in First Due, helping users understand the differences between report types, data source combinations, filtering options, scheduling capabilities, and ...

    • Reports: Create a Custom Folder

      Purpose Statement To demonstrate how to create a new folder in the Report List view for organizing and storing your ad-hoc reports. This feature helps users maintain an organized report structure, making it easier to locate and manage custom reports ...