Emergency Medical Dispatch Software System

The vendor required to provide emergency medical dispatch software system for include:
- Functional requirements
•    Scripted case entry questions for gathering vital information, including address, telephone number, chief complaint, age, sex, conscious or unconscious, breathing or not breathing and the number of victims.
•    Scripted key questions for each separate chief complaint. 
•    Patient condition codes for categorizing patients according to acuity, mechanism of injury and scene circumstance.
•    The system must have customer configurable guide questions and responses to account for airport specific scenarios. 
•    Scripted pre-arrival instructions, using a color- coded, panel logic script that emphasizes key action and decision pathways. 
•    The system must have the ability to interface with Motorola vesta next generation 9-1-1 system. 
•    The system must be able to receive data (number and location information) from the ani link. 
•    The system shall have the ability to recommend appropriate unit response based on incident nature. 
•    The system shall include a bi-directional cad interface. 
•    The interface must currently exist and be used by another agency. 
•    The PSCC currently uses Motorola premier one cad version 4.6.x
•    Process EMD questions and then exports as a call type and modifying circumstance, phone number, location, and treatment instructions to Motorola p1 cad for event entry. 
•    The system shall include an automated quality assurance case review software program capable of providing case histories of each incident and comparative histories providing individual dispatcher case statistics. 
•    The system must also be capable of providing reports that reflect any period of time or data field requested such as current week, month or year-to-date statistics. 
•    The system shall provide guide cards or card sets (flip-file protocol system) with pre-arrival instructions at each operator station as a backup to computer software.
- Technical requirements
1. System requirements
•    The solution must operate on the latest modern web browsers (google chrome, microsoft edge, safari). 
•    Data stored and/or transmitted over the networks must be encrypted using industry standard encryption best practices (i.e., transport layer security (TLS) 1.2 or greater, advanced encryption standard (AES) 256 or greater).
2. Application administration
•    The solution shall support role-based access control (RBAC) role-based user access. 
•    Applications must have the capability to define custom roles based on a user’s job function and access requirements. 
•    Support single-sign on (SSO) via SAML 2.0 or the use of azure active directory (AAD) or key cloak.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: January 29, 2026