American Falls School District No. 381 NONINSTRUCTIONAL OPERATIONS

8310F(3)

Automated External Defibrillators

AMERICAN FALLS SCHOOL DISTRICT #381 AUTOMATED EXTERNAL DEFIBRILLATOR (AED) INCIDENT REPORT

Date of Incident:

Time of Incident:

Location of Incident (which building, where in building, etc.):

Patient’s Age:

Patient’s Sex:

CPR prior to defibrillation: Cardiac Arrest:

Male

Attempted Not Witnessed Witnessed by AED person

Female Not Attempted

Witnessed by Bystander

Estimated time (in minutes) from arrest to CPR: Shock:

Indicated

Not Indicated

Estimated time (in minutes) from arrest to 1st AED shock: Number of shocks: Additional Comments:

8310F(3)-1

(ISBA 4/06 UPDATE)

Patient Outcome at Incident Site:   

Return of pulse and breathing Return of pulse with no breathing Return of pulse, then loss of pulse

  

No return of pulse or breathing Became responsive Remained unresponsive

Name of AED Operator: Transporting Ambulance: Name of Facility Patient was Transported To: Name of Emergency Health Care Provider:

Signature of Health Care Provider

Date of Report

This report is to be completed by the Emergency Health Care Provider or AED User within 5 business days of use of an AED. The completed report must be mailed/returned to:

Cross Reference: Legal Reference: I.C. § 5-337

Immunity for Use of Automated External Defibrillator (AED)

Policy History: Adopted on: 11/18/2014 Revised on:

8310F(3)-2

(ISBA 4/06 UPDATE)

Automated External Defibrillators – Incident Report Form 8310F3.pdf ...

Automated External Defibrillators – Incident Report Form 8310F3.pdf. Automated External Defibrillators – Incident Report Form 8310F3.pdf. Open. Extract.

117KB Sizes 1 Downloads 44 Views

Recommend Documents

RMU Incident Investigation and Report Form
Unsafe Acts. Unsafe Conditions. Management Deficiencies. Improper work technique. Poor workstation design or layout. Lack of written procedures or policies. Safety rule violation. Congested work area. Safety rules not enforced. Improper PPE or PPE no

Google Apps Incident Report
Mar 17, 2014 - Issue Summary. From 8:35 AM to 12:10 PM PT, Google Talk, Google Hangouts (including Chat and Video), Google. Voice, and the Google App ...

Google Apps Incident Report
Apr 17, 2013 - The following is the incident report for the Google services access ... Talk, Google Sync, the Admin panel, and the Cloud Console, and to a ...

Google Apps Incident Report
Mar 19, 2013 - Applications using the Google Drive and Docs APIs also returned errors. ... We thank you for your business and continued support. Sincerely,.

Google Apps Incident Report
Feb 27, 2011 - Google Engineering reverted the storage software update, and halted further deployment. Restoration Process. While analyzing the issue and its root cause, Google Engineering also worked on the process to restore users' accounts. At 6:0

Google Apps Incident Report
Apr 17, 2012 - Prepared for Google Apps for Business customers. The following is the ... Enhance internal documentation for configuration management.

Google Apps Incident Report
This misconfiguration prevented changes to existing customer data for upgraded users. ... Eliminate the need for server restarts to recover from this type of error.

Google Apps Incident Report
At 7:50 AM PT | 16:00 UTC November 15, Google Calendar Engineering brought a system of servers ... your business and continued support during this time.

Incident Report
Feb 24, 2009 - The root cause of the problem was a software bug that caused an ... we monitor our systems 24 x 7, we have engineers available to analyze.

Google Apps Incident Report
Nov 15, 2010 - Prepared for Google Apps Customers ... Apps customers on November 15, 2010. ... your business and continued support during this time.

Google Apps Incident Report
Feb 27, 2011 - Google Engineering reverted the storage software update, and halted ... better identify this class of bug during the software development cycle.

Google Apps Incident Report
We understand this service issue has impacted our valued customers and users, and we apologize to everyone ... At 6:12 AM PDT, a bug in a thirdparty software update caused a partial failure of a Google network router in ... escalated the software iss

Google Apps Incident Report
Mar 18, 2013 - service disruption was an issue in the network control software. Actions and Root Cause Analysis. At 6:09 AM PT, a portion of Google's network ...

Google Apps Incident Report
Google Drive list. Applications using ... The Google Engineering team conducted an internal review and analysis of the March 21 event. They ... Modify the Drive software to more reliably serve user requests during short periods where overall.

Google Apps Incident Report
Dec 10, 2012 - Actions and Root Cause Analysis. Background: The load balancing software routes the millions of users' requests to Google data centers.

Google Apps Incident Report
Google Apps Incident Report. Google Docs Outage - September 7, 2011. Prepared for Google Apps for Business customers. The following is the incident report ...

Google Apps Incident Report
Google Apps Incident Report. Gmail Outage - September 23, 2011. Prepared for Google Apps for Business customers. The following is the incident report for the ...

2016-2017 Incident Report Form (CPTSB Form 139-16).pdf ...
Whoops! There was a problem loading more pages. 2016-2017 Incident Report Form (CPTSB Form 139-16).pdf. 2016-2017 Incident Report Form (CPTSB Form ...

Google Apps Incident Report - PDFKUL.COM
Apr 17, 2013 - The following is the incident report for the Google services access disruption that occurred on. April 17 ... Talk, Google Sync, the Admin panel, and the Cloud Console, and to a lesser extent Groups,. Sites, and ... misconfiguration oc

2016-2017 Incident Report Form (CPTSB Form 139-16).pdf ...
CPTSB OFFICE (303) 894-7785. Office: Cell: Location: Larry Smith (303) 894-7786 (303) 929-3494 Arvada. Joyce Young (303) 894-7781 (720) 331-8985 Denver. 2016-2017. Passenger Tramway Safety Board. PASSENGER TRAMWAY. INCIDENTS. Page 2 of 2. 2016-2017 I

Google Apps Incident Report - PDFKUL.COM
Google Docs Outage - September 7, 2011. Prepared for Google Apps for Business customers. The following is the incident report for the Google Docs access ...

Postini Services Incident Report
May 7, 2013 - Prepared for Postini and Google Apps customers. The following is the ... We thank you for your business and continued support. Sincerely,.

Incident Summary Report -
Offense Class Code. Offense Class Description. Count. 320. ROBBERY - STRONG-ARM. 1. 450. ASSAULT AND BATTERY. 6. 460. INTIMIDATION / THREAT. 1. 510. BURGLARY - HOME INVASION - 1ST DEGREE. 1. 1410. MDOP - MALICIOUS DESTRUCTION OF PROPERTY. 3. Grand To

BULLYING INCIDENT REPORT FORM.pdf
Submission of a good faith complaint. or report of bullying or harassment will not affect the complainant or reporter's future employment, grades,. learning, or working environment. A complainant that falsely accuses someone will be subject to. disci