My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2023/08/09 Council Agenda Packet
>
Council Agenda Packets
>
2023
>
2023/08/09 Council Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/17/2023 9:22:40 AM
Creation date
8/9/2023 6:07:50 PM
Metadata
Fields
Template:
Council Agenda Packet
Date
8/9/2023
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
216
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />Page 12 of 41 <br /> <br />seconds and shall be timed-stamped by the Supplier’s CAD system. See definition of response time in <br />Section 5. <br />By the fifth business day of each month the Supplier must provide EFD a download of CAD data in an <br />editable format. Also, a report summarizing patient care performance and other factors of contractual <br />compliance during the preceding month entitled “Monthly Performance and Compliance Report.” <br />The Monthly Performance and Compliance Report must include the following elements, at minimum. <br />1. Report Title: Monthly Performance and Compliance Report, and <br />2. Issues of concern pertaining to patient care, including a Quality Improvement Plan if needed, and all <br />QAR responses submitted to the MPD for EFD incidents, and <br />3. Prior month response data export in XLSX format (or other as mutually agreed) for all requests for <br />transport provided under the contract, including supplier CAD timestamps and pertinent incident data <br />within the City of Everett; and <br />4. Summary of Response Performance, including the subset of responses out of compliance and the <br />associated CAD information for all requests for service. To include: <br />a. Median, mean and 90th percentile total response time, code responses <br />b. Median, mean and 90th percentile total response time, non-code responses <br />c. Count of direct dispatches to medical facilities <br />d. Median, mean, and 90th percentile total response time to medical facilities <br />e. Table of instances the supplier reported “no ambulances available” to the PSAP, to include <br />date, time and CAD incident number. <br />f. Summary of transports, to include destinations. <br />g. Other pertinent incident data as requested by the City. <br />5. Table of instances where supplier units fell below minimum levels as defined in Section 2.9. This table <br />must include date(s), start time(s), and end time(s) for all instances where minimum unit <br />requirements were not met. <br />6. Itemized list of requests for exemption from liquidated damages as per Section 2.19. <br />7. Summary of customer complaints and supplier responses. <br />8. Summary of vehicle collisions. <br />9. Summary of fleet inventory with verification that available inventory remains greater than or equal to <br />125% of peak ambulance coverage requirements. If fleet inventory drops below 125%, a written plan <br />for remedying back to 125% including a timeline should be included. <br />The Monthly Performance and Compliance Report is due to the City Contract Administrator on or before <br />the 5th business day of each calendar month. See Section 2.21 for processing of any fees or liquidated <br />damages. <br />The Supplier and EFD may meet up to monthly to discuss matters of concern and to review adherence to <br />patient care performance standards and transport protocols. A joint meeting must occur at least <br />quarterly. Dispatch personnel may also be included in this meeting to review dispatch protocols,
The URL can be used to link to this page
Your browser does not support the video tag.