The vendor is required to provide for the purchase and implementation of cloud-based programs to help support incident management, including software, hosting, disaster recovery, implementation, training, and maintenance for use by the department.
- This RFP is intended to support five project areas, including:
•  Incident management
•  Volunteer registry and management
• Health alert network (han) operations
• Patient tracking
• Bed availability tracking
1. Incident management
• An electronic incident command system (ICS) that adheres to the national incident management system (NIMS) framework and ICS guidance and is adapted for public health and healthcare use.
2. Volunteer registry and management
• A system for the registry, tracking and deployment of volunteers for the fulfillment of the administration for strategic preparedness and response (ASPR) hospital preparedness program cooperative agreement emergency system for advanced registration of volunteer health professionals (ESAR-VHP) compliance requirements.
3. Health alert network (HAN) operations
• Maintain a statewide delivery system for regional and local messaging of alerts, advisories and updates from center for disease control (CDC), department.
• This allows for the rapid distribution of public health and emergency management information to healthcare and emergency management.
4. Patient tracking
• Electronic system for the tracking and movement of triaged patients in the event of a mass casualty situation.
5. Bed availability tracking
• Electronic system for tracking hospital and healthcare bed types available daily by facility as well as facility situational assessment data.
- Requirements:
• The proposed project components shall be commercially available (beta versions will not be considered) and designed to support disaster and special event management, and daily operations.
• The proposed project components must be web browser based and capable of supporting more than one browser client (edge, chrome, safari, Firefox, etc.) and must be formatted for tablet devices and mobile phones.
• All software shall be designed to work with projectors for information display.
- Security and monitoring requirements:
• The proposed project components must provide complete control to sensitive data via secure password protected methodology
• The web-based project components must support secure internet connectivity.
• The proposed project components shall allow authorized administrators to view currently logged in users of a system and be able to terminate current connections as needed.
- External interfaces and 3rd party products requirements:
• Vendor must identify how interfaces to third party products are handled, including federal agency Interfaces.
- Hosting environment and data access requirements
• The proposed project components must provide a hosting environment with a primary-alternate configuration to ensure reliability.
• The hosting environment must offer ssae-16, soc-2 compliant facilities
• The proposed project component must not require any software to be downloaded onto customer machines to function properly.
• Solutions that require installation of client software will not be considered.
- Incident command system project area features – general requirements:
• Vendors shall describe how the proposed software can be used for each of the following:
a. System can be used to manage disasters, special events, security and day-to-day operations
b. System shall be capable of being used for multiple real world and drill/exercise events simultaneously.
c. System can manage related incidents in a hierarchal incident structure.
d. Describe how customers collaborate regionally.
• The proposed incident management system (IMS) project component shall comply with national incident management system (NIMS) principles and provisions for the incident command system (ICS).
• The proposed IMS project component must support emergency support
• The proposed IMS project component must time and date stamp all actions performed on the system, and preferably include the user’s name of the person performing the action.
• The proposed system must provide spell-check capability.
• The proposed system must provide for all major facets of emergency management without requiring the purchase of additional modules.
- Incident command system project area user tools requirements:
• The proposed system must include automated after-action report functionality.
• The proposed system must have formatting capabilities for standard homeland security exercise and evaluation program (HSEEP) reporting.
• The proposed system must include an integrated joint commission 6 critical element evaluation.
• The proposed system must have the ability to, or the option of, automation of bed availability data reporting from electronic medical record provider.
• Proposal shall identify how users can switch between incidents and authorized roles/positions without logging out of the system.
• The proposed IMS product shall have integrated all hazards checklists, and be adaptable for hospital incident command systems (HICS).
• Proposed solution shall provide the capability for multiple agencies to operate under a common incident.
• Provide the ability to poll the deployment for resource status, operations status, or ask basic questions of the user base.
• Proposed product shall support resource and map sharing features between users based on permissions.
• Proposed system must include mobile app that allows for the initiation of incidents, log entry and enter data, assign to ICS role, and uploading pictures.
• Proposed system must include a mobile app for the triage and tracking of patients.
• Mobile-native applications must use the state’s identity provider.
- Incident command system project area administrative features:
• The proposed IMS software shall provide the ability to create incidents, manage multiple incidents simultaneously, and store, query and view historical data associated with an incident.
• A system administrator must be able to easily add/change/inactivate/remove users. each user much have a distinct access profile that defines that user’s access to data, at a minimum, read or edit access.
• Administration of the proposed project component shall be through a browser.
• Software administration from the server only will not be considered.
• The proposed project component shall be capable of supporting a large number of users from multiple jurisdictions.
• The proposed project component shall support the ability to export reports in xml, csv, pdf, MHTML, excel, tiff and word formats.
• Historical data must follow the agency’s record retention policies on the IMS project component on an incident basis to facilitate post-operational analysis and debriefing.
- Incident command system project area mapping feature requirements:
• The system shall allow authorized users to annotate the map using icons, labels or other symbols.
• Must be capable of viewing live dynamic, multiuser process data on a map.
• Must be capable of combining data with other geographic information system (GIS) or services on a single map.
• Must be capable of saving locations or marking areas as bookmarks.
• The system shall have the ability to display critical infrastructure/key resources (CI/KR) on a map based on the geocode resource location.
- Implementation support requirements
• Describe onsite and offsite training opportunities.
• Software subscription must include all upgrades, including major releases.
- Contract Period/Term: 1 year
- Questions/Inquires Deadline: May 15, 2025