22.01.2015 Views

Using the HICS Tools in Incident Action Planning - The 2012 ...

Using the HICS Tools in Incident Action Planning - The 2012 ...

Using the HICS Tools in Incident Action Planning - The 2012 ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

HOSPITAL<br />

INCIDENT<br />

COMMAND<br />

INCIDENT OBJECTIVES r:J<br />

1 SYSTEM<br />

1. INC IDENT NAM E<br />

Wll-t­<br />

,<br />

- 6:-wEATHER / r;,NVIRO NMENTAL IMPLICATIONS FOR PERIOD (INCLUDE AS APPROPRIATE: FORECAST. WIND SPEED/DIRECTION, DAYLIGHT)<br />

~ t; 3 tI - 3tJ I /h;~--/f 't1t!+. W~&f­<br />

- --'I~ll --=--;tJ7u --l""'M/;fir-I7JM1th(/o/------2&AJIO~<br />

7. GENERAL SAFETY / STAFF MESSAGES TO BE GIVEN<br />

Examples: pe~on;1 Protective Eq Uipment (PPE!. Precautions, Case Def<strong>in</strong>itions (refer t<br />

<strong>HICS</strong> 261 <strong>Incident</strong> <strong>Action</strong> Plan Safety Analysis)<br />

~aMd -~IlL= - t1TLflj)dIL .~~ ... ~~­<br />

t -~ ()AI /tt;~-4#-fj/Jf-c:itt¢r-11AJtlAIN~<br />

=~)u;JVI___ j7J/V t1rtf;-=-avl1Ct ~~;7 _- U IMlZf:1P·····_---=-_ _<br />

8. ATTACHMENTS (MARK IF ATTACHED)<br />

.~ICS 203 - Organization ASSignment List o <strong>HICS</strong> 206 - Medical Plan 0 Traffic Plan<br />

~ICS 204 - Branch ASSignment List o <strong>HICS</strong> 251 - Facility System Status Report 0 InCident Map<br />

o <strong>HICS</strong> 205 -<strong>Incident</strong> Communications Plan o <strong>HICS</strong> 261 - <strong>Incident</strong> <strong>Action</strong> Plan Safety Analysis 0 O<strong>the</strong>r<br />

9.PRf}AAE~ANNING SECTION CHIEF)<br />

f--- 'J IM<br />

11. FACILITY NAME<br />

J1J /-ft/<br />

PURPOSE: DEFIN E OB,.E CTIVES A \JD ISS UES FOR O P E RAT IONA~ PER IOD ORIGINATION: PLANNING SECTION CHIEF. <br />

COPIES TO: COMMAND STAFF. GENERAL STA FF, AND DOCUM ENTATION UNIT LEADER.<br />

Hies 202

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!