Emergency Management Services Data Platform

The Vendor is required to provide a subscription-based emergency room data system.
- System shall support agency mission to enhance public health response capabilities by delivering timely, comprehensive, and secure access to Emergency Medical Services (EMS) data, particularly related to overdose surveillance and other priority health indicators.
- The system shall comply with all applicable federal and state data exchange standards and be capable of integrating with existing public health infrastructure.
- Core Data Capabilities
•    Demographic insights: collect age, gender, race/ethnicity, zip code, and insurance status for equity analysis.
•    Clinical information: diagnoses (international classification of diseases, 10th revision (icd-10) codes), procedures, medications, allergies, and discharge status specifically: date, location, run type, emergency medical dispatch (EMD) complaint, primary impression, secondary impression, sign and symptom, possible injury, cardiac arrest, barriers to care, alcohol or drugs, patient pregnancy, narrative, patient zip, scene zip, patient city, scene address.
•    Real-time visit tracking: capture patient arrival (specifically: transport destination, response at destination time to treatment, response call closed time to treatment, response depart scene time to treatment, response transfer of patient care time to treatment, time in seconds from onset to call received, time in seconds from onset to dispatch, time in seconds from onset to on scene, treatment date local offset, treatment date timestamp, triage, diagnosis, treatment (specifically: medication given (code for naloxone), medication administered route, medication dosage, medication administered time, medication complication, medication response, medication name, reason naloxone/ narcan not administered, naloxone/narcan kit left with patient or family member), and discharge data.
•    Outcome tracking: admission, transfer, ambulance patient offload (apot-1) time, patient refusal forms, or discharge data for longitudinal care analysis.
•    Overdose surveillance: flag opioid related visits using icd-10 codes and clinical indicators.
- Privacy and Legal Compliance
•    Health insurance portability and accountability act (HIPAA) compliant data exchange: ensure secure handling of all data exchanges must meet federal privacy and security standards.
•    Consent protocols: systems must support emergency access without explicit patient consent when legally permissible.
•    Substance abuse and mental health services administration (SAMHSA) guidelines: support masking or de-identification of sensitive substance use data.
- Technical Infrastructure
•    Interoperability standards: health level seven (hl7), fast healthcare interoperability resources (FHIR), or storage, analysis, failures, and reclamation (SAFR) model for health information exchange (HIE).
•    Secure application programming interface (APIS) or data feeds: for real-time or batch data transmission.
•    Cloud hosting: most services are software as a services (SaaS)-based and require secure cloud environments.
•    Compatibility with local systems: integrate with ems, hospital electronic health record system (EHRS), and agency epidemiology and surveillance systems.
- Analytics and Reporting Tools
•    Dashboards: visual tools for tracing overdose trends, ER utilization, and demographic patterns.
•    Custom queries: ability to filter by geography, diagnosis, payer source, and time period.
•    Export structed data options: comma separated values (csv), excel, JavaScript object notation (JSON) and integrate with agency systems (API, environmental systems research institute (ESRI), SharePoint, EHRS).

- Contract Period/Term: 1 year
- Pre-Proposal Conference Date: October 21, 2025
- Questions/Inquires Deadline: October 24, 2025