1. Department Information:
- NERIS introduces new ID numbers, including fields for the old FDID, enabling seamless transition and data tracking.
- It supports single-system, multi-agency setups, accommodating sub-departments and parent-child indicators.
- NERIS organizes information hierarchically: Department → Station(s) → Unit(s), although adjustments may be needed for existing data structures.
- More detailed information is required, such as NERIS-specific fields like neris_id and GIS polygon coordinates for response areas.
2. Dispatch/CAD Schema:
- While similar to existing data, NERIS proposes additional fields, necessitating considerations for system compatibility and customization.
- Standardized NERIS call types may require alignment with client-specific call type codes for submission.
3. Incident Schema:
- Similar to NFIRS, but with expanded fields, especially for specific incident categories like FIRE and EMS.
- Many fields overlap with NEMSIS specifications, potentially leveraging existing tables for lookup.
- Adjustments are required for fields with variable numbers of items, such as Actions Taken.
- Inclusion of GIS data, like incident scene outlines and coordinates, adds complexity to data collection.
1. Data Transfer Requirements:
Clarification is needed regarding the method of data submission, whether through REST endpoints, SOAP, or other protocols.
2. Approval and Submission Process:
Procedures for approval, submission statuses, and vendor verification processes require definition to ensure smooth operations.
3. System Integration:
Integrating NERIS-compliant data fields into existing systems, such as RedNMX, may necessitate updates and customization.
4. Training and Familiarization:
Fire department personnel will require training to familiarize themselves with the new reporting protocols and systems.
5. Technical Considerations:
Ensuring compatibility with existing CAD systems and addressing any discrepancies in data formatting are essential for seamless transition.
