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 13 of 41 <br /> <br />discrepancies, and other topics of concern. The purpose of these meetings will be to maintain open and <br />proactive communication, resolve problems, and to provide a forum to discuss patient care performance <br />on the part of the Supplier for EFD. <br />Electronic Healthcare Records (“EHR”) are required to document patient care. The required EHR software <br />is ESO Solutions (“ESO”). The Supplier will assure that each ambulance is equipped with EHR equipment <br />and software to complete ESO records of EFD patients. <br />The Supplier is responsible to assure all Snohomish County ESO requirements are met, including wireless <br />transmission and reception of patient information. <br />The Supplier must ensure all personnel are adequately trained to use ESO and that there are not <br />compatibility issues between EFD and the Supplier’s version of ESO. <br />For each ESO record, the Supplier must enter the transported patient’s Medical Record or Encounter <br />Number into ESO to allow utilization of the ESO Health Data Exchange feature for EFD Patients. The <br />supplier must ensure that recorded destination data is inputted correctly to allow EFD access and export <br />of HDE data. <br />The Supplier must provide access to their ESO database to EFD Medical personnel and others as <br />designated by the EFD Medical Director(s). <br />2.8 RESPONSE TIME PERFORMANCE <br />Exceeding the designated response time by five minutes or more in any category is considered a failed <br />response. Non-response is a failed response. <br />Code responses are made with both lights and sirens in operation. The Supplier must respond to all Code <br />requests which have not been exempted from such time performance standards within fifteen (15:00) <br />minutes. Liquidated damages for late arrival on scene will be assessed per minute for up to five minutes <br />after which liquidated damages for a failed response will be assessed. <br />Non-Code responses are made with neither lights nor sirens in operation. The Supplier shall respond to <br />all non-Code requests which have not been exempted from such time performance standards within <br />20:00 minutes. Liquidated damages for late arrival on scene will be assessed per minute for up to five <br />minutes after which liquidated damages for a failed response will be assessed. <br />Liquidated damages for exceeding the response time standard will be assessed as provided in Section <br />2.20. <br />The Supplier must notify EFD of any occurrences where local assets are dispatched outside of the City to a <br />major disaster or incident of national significance. Response time requirements remain the same, but <br />because the Supplier has opted to remove from service resources dedicated to fulfilling the performance <br />standards in this contract, EFD may need to deploy resources to provide BLS transport. <br />The Supplier must meet or exceed the patient care performance standards set forth in state law and the <br />most current Snohomish County Patient Care Protocols. In the event there are conflicts among these
The URL can be used to link to this page
Your browser does not support the video tag.