This Solicitation opportunity from Florida was posted on February 28, 2025. The submission period has ended. Browse the details below for market research, or find similar active opportunities.
Fire-Rescue Records Management System (RMS)
Contract Overview
Solicitation details, issuing organization, response deadlines, documents, and interested companies for this government contract opportunity.
Active Opportunities Like This One
AI Contract Overview
St. Johns County is seeking a comprehensive, fully integrated Fire/EMS/Prevention records management system (RMS) that is cloud-based, scalable, and user-friendly, supporting current and future operational needs for managing a wide range of data including patient care reports, fire incident reports, hydrant management, inspections, and EMS billing. The system must facilitate seamless data entry through a single point of input, with automatic propagation across relevant databases, and support both desktop and mobile users with offline capabilities. It should comply with numerous standards such as NFIRS, NEMSIS, HIPAA, and SOC 2, ensuring data security, role-based access, and encryption, with data stored within the United States. The solution must integrate with existing applications like CAD, billing, scheduling, and communication tools, either through replacement or interface, and accommodate future system upgrades without disrupting interfaces. The scope includes providing a pre-configured, vendor-hosted RMS solution with detailed hardware and software specifications, implementation, and ongoing support, including training, documentation, disaster recovery, and system updates. The platform must support extensive data volumes, real-time analytics, customizable reporting, and advanced features like predictive analytics and GIS integration. Data ownership remains with the County, with clear procedures for migration, retention, and secure data return upon contract termination. The project emphasizes minimal staff disruption, high security standards, and compliance with federal and state regulations, with a contract value estimated between $500,000 and $2 million, and a response deadline of April 3, 2025.
General Info
Place of Performance
FL, USASet-Aside
Documents
0AI Contract Breakdown
Uniform Contract FormatNo documents to break down
The breakdown needs solicitation documents. None were found from this contract's source.
This one is closed. Find the next one like it.
Open contracts like this one, right now:
- Resource Centre Operations & Equipment SupplyOpen now, due in 49 days
- Software Customer Support ServicesOpen now, due in 11 days
Ask CLEATUS
I've read this contract. Ask me anything.
Timeline
Submission Closed
Organization & Contact Information
Full Description
B. CURRENT APPLICATION ENVIRONMENT Below are tables which identify the County’s current inventory of systems and applications, along with the legend for what the County’s intent is related to each system/application.
Legend for Current Applications Legend Code Description R Replacement County intends to replace this application with the selected solution. C Consider County will consider replacing this application with the selected solution, based on the strength of the finalist Proposer offering and cost / benefit of the replacement module. M Maintain County intends to retain the application, not replacing it thru this effort. I Interface County intends to keep the application and interface/integrate it with the selected solution. C/I Consider / Interface County will consider replacing this application with the selected solution based on the strength of the finalist Proposer offering and cost/benefit of the replacement module. In the event the County maintains this application, it would require an interface to the RMS. Therefore, the Proposer must provide interface experience and pricing for these applications.
Current Application Application Notes/Description Likely Future of System? * RescueNet (Zoll) Patient Care Reporting R Fire RMS (Zoll) Fire Incident Reporting/Fire Inspections R FireWorks Reporting C/I FirstDue Building Preplans C/I Handtevy SOP/SOG I X-Series Cardiac Monitors (Zoll) ECG/Vital signs I Pulsara EMS-to-ER communications I Motorola PremierOne CAD Computer Aided Dispatch I PS Trax Work Orders I Teller Cashiering ERP Financial Integration with EMS Billing I UKG TeleStaff Fire Rescue Scheduling I Zoll Billing POS for EMS C/I
C. EXPECTED SCOPE OF SYSTEM SOLUTION The County requires responding Proposers to propose a fully integrated RMS proposer-hosted/cloud solution, including software, hardware specifications, implementation and project management, and other technology services for the entire scope of the project that may or may not include components owned by the proposer. The County recognizes that this project will have a significant impact on their staff and is looking to minimize that impact insofar as possible. Proposer will provide the County with a pre-configured system using its best practices and experience as a model. The County expects to review and test this pre-configured system, requesting minimal changes as required. 1. General Requirements: a. Scalability: The platform must support current and future operational needs, with the ability to handle increasing data volumes and users. [60,000 incidents, 30,000 ePCRs, 25,000 Prevention inspections, 15,000 hydrants, 15,000 occupancies, 500+ users, 20,000 original EMS bills] b. Cloud-Based: Platform must be cloud-based. c. Interoperability: Ability to integrate seamlessly with existing systems (e.g., CAD, RMS, GIS, financial systems). [List of systems in RFP’s “Current Application Environment”] d. Compliance: Adherence to relevant standards (e.g., NFIRS, NERIS, HIPAA, NEMSIS, SOC 2, CMS.gov, EMSTARS, CARES, etc.). e. User Access: Role-based access control to ensure data security. f. User-Friendly Interfaces: Intuitive, easy-to-navigate interfaces for staff at all technical skill levels. g. Training and Support: Comprehensive training programs and ongoing support for staff. 24-hour support for critical functions. h. Documentation: Detailed user manuals and online knowledge bases. 2. Application Requirements a. All Applications: • Secure Login: Login security must use SSO integration with County Azure Active Directory. • HIPPA Compliant: Applications and systems must be kept compliant with applicable HIPAA regulations. b. EMS Reporting: • Incident Tracking: Capture detailed information about EMS incidents, including time stamps, response details, patient care, and outcomes. • NEMSIS Compliance: Ensure the platform is compliant with the latest NEMSIS standards for EMS data reporting. • Data Visualization: Dashboards and visual reports for monitoring response times, patient outcomes, and trends. • Customizable Forms: Ability to customize incident and patient care forms to align with local and state requirements. • Quality Assurance/Quality Improvement (QA/QI): Built-in tools to review and analyze EMS calls for performance improvement. • Health Data Exchange (HDE): Direct integration with Northeast Florida hospital systems [UF Health, Baptist, Mayo, HCA, Ascension St. Vincent’s, AdventHealth to allow SJCFR to directly access patient progress reports and obtain outcomes for SJCFR patient transports. c. Fire Incident Reporting: • NFIRS/NERIS Compliance: Ensure compliance with fire incident reporting standards for fire-related activities. • Incident Tracking: Capture detailed information about EMS incidents, including time stamps, response details, patient care, and outcomes. • Performance Metrics: Tools to analyze key performance indicators (KPIs), such as response times and fire containment success rates. • Operational Insights: Provide insights into apparatus and personnel usage. d. Fire Prevention and Inspection: • Inspection Management: Tools for scheduling, tracking, and documenting fire inspections/preplans for businesses, schools, and other facilities. Mapping ability to plan out inspection routes. • Code Compliance: Integration with local fire codes and standards for compliance checks. Ability to add local codes and standards. Included Access within violation fields to NFPA 1 and 101 Fl Editions. • Mobile Accessibility: Mobile functionality for field inspections, with offline capabilities. Operates on St. Johns County MIS platforms devices/operating systems. Ability to attach photos to reports. • Permit Management: Tools for processing and tracking permits for fire safety systems, events, or hazardous materials. • Violation Tracking: Document, track, and report fire code violations. • Fire Hydrant Management: Track maintenance, testing, mapping of each hydrant. • Records: Ability to import past records for inspections permits and hydrant. e. EMS Billing: • Claims Management: Tools to receive transports from the EPCR software, process EMS bills, submit claims, and track their status. • HIPPA/CMS: Comply with all HIPAA Requirements and CMS Guidelines ( including ability to print CMS 1500 forms. • Import 835 Files: The ability to import 835 files from our clearinghouse and batch post them. • Insurance Verification: Automated insurance eligibility checks for patients. • Payment Processing: Integration with payment gateways for patient and insurance payments. Integrates with SJCFR’s existing billing program (Zoll Billing) as well as Waystar. • Revenue Reporting: Detailed, customizable reports on billing activity, revenue collections, and outstanding balances. • Compliance: Ensure billing is compliant with Medicare, Medicaid, and private insurance regulations as well as having legal and collections components. • Demographics and Insurance: Ability to discover and verify demographics and insurance information. f. Data and Analytics: • Real-Time Reporting: Access to real-time data for operational decisions. • Custom Reports: Ability to create and export customized reports for stakeholders. • Predictive Analytics: Tools to forecast trends and resource needs based on historical data. • AI-Assisted Reporting and Analytics: Predictive insights or intelligent assistance for reporting accuracy and QI/QA analysis. • CAD Integration: Dynamically import CAD data from Motorola PremierOne CAD. See Interface section for more detail. • GIS Integration: Map-based analytics for incident locations, risk assessments, and response coverage. Must support ESRI ArcGIS platform. • Third Party Software Integration: Effectively interfaces with third-party programs (Telestaff, PSTRAX, First Due, Handtevy, etc.). 3. Detailed Requirements: a. Fire: • NFIRS/NERIS: Compliant Fire Incident Report: o Automatically create Fire Incident Report when incident is dispatched in CAD then dynamically update report while incident is in progress. o Automatic flow to mandatory fields as dictated by incident type. o Ability to customize and add user-defined or mandatory fields for special studies and community specific information. o NFIRS/NERIS fields must include written description as well as code numbers. o All free text fields to include automatic spell check. o Tiered security access levels defined by user group. b. EMS: • NEMSIS: Compliant Patient Care Report: o Automatically create Patient Care Report when incident with medical unit is dispatched in CAD then dynamically update report while incident is in progress. o Automatic flow to mandatory fields as dictated by incident type. o All free text fields to include automatic spell check. o Ability to customize and add user-defined or mandatory fields for special studies and community specific information. o Tiered security access levels defined by user group. 4. Other: a. Offline Capability: Clients must have offline capability to maintain operation or minimize data loss if network/internet connection is lost. 5. Interface Requirements/Current Application Environment: a. Interface Compatibility: Must maintain interface compatibility across software changes/upgrades or notify SJC 180 days before any change that will require a third-party vendor to update their side of an interface. b. Rescue/Net (Zoll): • Patient Care Reporting: Replace c. Fire RMS (Zoll): • Fire Incident Reporting/Fire Inspections: Replace d. FireWorks: • Reporting: Consider/Interface e. FirstDue: • Building Preplans: Consider/Interface f. Handtevy: • SOP/SOG: Interface g. X-Series Cardiac Monitors (Zoll) • ECG/Vital signs: Interface h. Pulsara: Interface • EMS-to-ER communications: Interface i. Motorola PremierOne CAD: Interface/Provide requirements for CAD import interface and cooperation with CAD vendor during interface development. • Data Points Required from CAD: o Address (address to be imported in a format to allow for system mapping capabilities upon initial dispatch on MDT/Tablet) o Incident Date o Incident Times (dynamically updates as the following benchmarks are reached: ? Call Received ? Dispatched ? Responding ? Arrived ? Back in Service ? Cleared o Dispatcher o CAD Incident # o Response Priority o Structure o Incident Type/Nature o Known hazards or special instructions that are stored in CAD o CAD notes j. PS Trax: • Work Orders: Interface k. Teller Cashiering: • ERP Financial Systems Integration with EMS Billing: Interface/Ability to integrate with Teller Cashier at minimum by periodic auto-upload of billing transactions data file to SFTP site or ideally via bidirectional communication with billing system API. l. UKG TeleStaff: • Fire Rescue Scheduling: Interface/Ability to integrate with UKG TeleStaff API to retrieve staff schedule/Roster data to automatically populate responding personnel in Fire Reports. m. Zoll Billing: • POS for EMS: Consider Replacing/Interface with Zoll Billing. 6. Additional Vendor Requirements: a. Operating Systems and Hardware: Must maintain compatibility with current supported Microsoft Software including OS, browser, and Microsoft 365. b. Online/Web Services Applications: • Must be compatible with current versions of common browsers including Firefox, Chrome, Edge, and Safari. • Must pass the w3.org validation test (http://www.w3org/QA/Tools) and be compatible with federally regulated accessibility standards (Section 508, http://www.section508.gov). • ADA compliance could be required by the County Legal Department if needed. • Provide mobile and desktop computer hardware and operating system requirements. c. Support: Specified in RFP Section 8 Ongoing Support Services. d. Security: • All data stored at the Cloud provider must be secured in a way which prevents unauthorized access from internal and external parties. • For public safety applications, all data at rest, meaning at the cloud provider must be encrypted and must follow all state and federal regulations. • All data related to the solution provided to the County must be stored in a physical facility within the contiguous forty-eight (48) states of the United States of America. • Software system and hosted environment must be secured against the latest known cybersecurity threats. e. Database: • Must be MS SQL (MS SQL Server 2019 or newer) or other widely supported, commercial relational database. • Must have features that allow for data exports in sql, xls, csv formats of the entire database or specific tables or fields. f. Backups and Disaster Recovery: • Must provide proof of a Business Continuity/Disaster Recovery plan with details on backups and retention periods. • If off-site backups are implemented the data must be encrypted. • Must be able to setup backup systems as well as restore systems in case of any software attacks or system failures. • Ability, in the event of a disaster within our system, to reproduce our environment as a temporary workspace, if we do not have the capability to get back online. g. Data Transmission (Over the Internet): All data transmitted must be encrypted using 128bit (or higher) a minimum of TLS 1.2 for SSL/HTTPS and SSH version 2 for any batch or real-time non-http transfers. SSL certificates must be signed by a trusted third party; no self-signed certificates will be considered. For public safety solutions, encryption is a mandatory requirement. h. Data Ownership: All data (except for system or configurations settings) is exclusively owned by the County and a written agreement is required if the solution provider will use the data for other than the primary purposes of providing all agreed services. All data must be handled and secured as described in this document. i. Data Migration/Retention and Release: • If it is required to migrate the data to a different provider, a description of how data can be transitioned with projected costs must be available. • If there is no strategy/process to migrate data, procedures and documentation including diagrams for a complete extraction of data will be required. • If the SaaS contract is terminated, all data will be returned to the County in a suitable standard format and wiped from the cloud-based provider. • All backup data from any virtual or physical equipment must be erased. • Must provide projected termination costs for data return. j. Historical Data Conversion: Ability to convert and import three years of historical data from Zoll FireRMS, Zoll Billing and Zoll RescueNet ePCR including all NFIRS and all NEMSIS V3 dataset Incidents. • Required Series Incident Types o 100 – Fire o 200 - Overpressure Rupture, Explosion, Overheat (No Ensuing Fire) o 300 - Rescue and Emergency Medical Services (EMS) Incidents o 400 - Hazardous Condition (No Fire) o 500 - Service Call o 600 - Good Intent Call o 700 - False Alarm and False Call o 800 - Severe Weather and Natural Disaster o 900 - Special Incident Type • Lifetime backup for all existing inspections on hydrants and buildings that SJCFR prevention has completed in the current RMS software. k. Systems Updates: Organized system for updates and patches. Must provide release notes with specific descriptions on each update and patch. l. Training and Test Environment: • Continued virtual training as required by updates and patches. • Provide a test environment prior to going live with a full working database kept as up to date as practical. m. ActiveX/Java: Avoid the use of Actiand java clients. If one of these client components are required, the provider must agree in writing to maintain client compatibility and must provide in writing any data that will be transmitted using the client component. n. System Conventions: Describe system conventions and standards followed. Example: Microsoft standards are followed by Windows, Institute of Electrical and Electronic Engineers (IEEE) for data formats, etc.
Find Active Opportunities Like This
Get AI-powered intelligence on the opportunities still open
Every page of the solicitation package shredded into a compliance breakdown
AI-powered matching based on your capabilities and past performance
Competitor and incumbent history on the requirement
Automated alerts on amendments, Q&A deadlines, and award
Join 750+ contractors already using CLEATUS
