LAC DHV Full-Scale Exercise :: Master Scenario Events List Vers 1 – 2-8-13 page 8
Event # / Event Time / Event Description / From / To / ResponsibleController / Method / Expected outcome / Notes /
1 / February 26 / “Save the date” notice to relevant volunteers / VLA / Unit coordinators / Relevant volunteers / DHV system message
2 / March 26 / “Save the date” reminder to relevant volunteers / VLA / Unit coordinators / Relevant volunteers / DHV system message
Monday, April 22, 2013
3 / 10:00 / Controller/Evaluator briefing
START EXERCISE
4 / 1:00 pm / Healthcare facilities submit resource requests to county / Hospitals and clinics / County DOC / Lead controller / Fax or email / DOC receives resources requests
5 / 1:15 pm / DOC acknowledges receipt of resource requests / County DOC / Requesting hospitals and clinics / Lead controller / Acknowledgement of received resource requests
6 / 1:30 pm / DOC activates relevant sections, positions / Lead controller / DOC activates Logistics section and possibly other positions / Roel: do you want this broken into more steps?
7 / 2:00 pm / DOC initiates response, incident action planning / Lead controller / IAP generated
8 / 3:00 pm / DOC initiates conference calls with requesting facilties / County DOC / Requesting hospitals and clinics / Lead controller / Phone call / Clarification of resource requests; exploration of relevant logistics issues
9 / 4:00 pm / DOC notifies DHV unit coordinators, Mobilization Center staff, other resources / County DOC / DHV, MRC Unit Coordinators, Mobilization Center staff / Lead controller / Relevant resources alerted to begin gearing up for Friday deployment
10 / 4:15 pm / Creation of mission and deployment groups in Mission Manager (DHV system) / County DOC / Lead controller / DHV system / Mission Manager contains relevant mission and deployment groups
11 / 4:30 pm / Notification of volunteers – polling for availability for Friday deployment / Unit Coordinators, County DOC / Disaster Healthcare Volunteers / Lead controller / DHV system / Volunteers receive request for Friday deployment
Tuesday, April 23, 2013
12 / 8:00 am / Monitor volunteer responses; verify license and qualifications for each as they become available / Unit Coordinators, County DOC / Lead controller / DHV system / Growing pool of volunteers with appropriate credentials for resource request
13 / 8:00 am / Respond to volunteers who become available with a confirmation-of-assignment email and “stand by” for more details / Unit Coordinators, County DOC / Lead controller / DHV system / Confirmation email to each volunteer
14 / 10:00 am / Conference calls with all/each requesting facility to finalize logistics details (parking, point of contact, where to report, etc.) / County DOC / Requesting hospitals and clinics / Lead controller / Phone call / Finalize all relevant logistics for Friday deployment / These calls should resolve real-world logistics issues which will be communicated to volunteers: where to report, where to park, etc.
15 / 1:00 pm / Mobilization Center planning conference / County DOC, VLA / Lead controller / Phone call / Completed planning for Mobilization Centers at each of 6 hospitals / This could occur on earlier.
16 / 2:00 pm / DOC conference – updated action planning / County DOC / Lead controller / Updated incident action plan for supporting Friday deployment / This should be updated per DOC protocol
17 / 3:00 pm / Create rosters of available volunteers, for each deployment venue / Unit Coordinators, County DOC / Lead controller / DHV system / Rosters of available volunteers, one roster per deployment venue / Roster creation could occur this day or Wednesday
Wednesday, April 24, 2013
18 / 8:00 am / Finalize rosters of available volunteers / Unit Coordinators, County DOC / Lead controller / DHV system / Final roster of volunteers for each venue
19 / 9:00 am / Confirm rostered volunteers; notify each of their assigned venue / Unit Coordinators, County DOC / Volunteers / Lead controller / DHV system / Confirmation email to each volunteer
20 / 9:00 am / Send release-of-availability email to volunteers who are not rostered / Unit Coordinators, County DOC / Volunteers / Lead controller / DHV system / Email releasing those volunteers who responded but are not being deployed
21 / 10:00 am / Compose and send instructions to rostered volunteers regarding deployment instructions / Unit Coordinators, County DOC / Volunteers / Lead controller / DHV system / All volunteers to be deployed receive detailed instructions regarding where, when to report, and related details
22 / 1:00 pm / Check-in call with VLA regarding Mobilization Center staffing / County DOC / VLA / Lead controller / Phone / Review of preparation to deploy six Mobilization Centers
23 / 2:00 pm / DOC conference – updated action planning / County DOC / Lead controller / Updated incident action plan for supporting Friday deployment / This should be updated per DOC protocol
Thursday, April 25, 2013
24 / 8:30 am / Confirmatory phone call to each rostered volunteer / Unit Coordinators, County DOC / Lead controller / DHV system / Each rostered volunteer receives automated confirmation call
25 / 8:30 am / Send volunteer rosters to each receiving facility / County DOC / Healthcare facility point of contact / Lead controller / Email or fax / Each receiving facility receives roster of expected volunteers
26 / 1:00 pm / Check-in call with VLA regarding Mobilization Center staffing / County DOC / VLA / Lead controller / Phone / Review of preparation to deploy six Mobilization Centers
27 / 2:00 pm / DOC conference – updated action planning / County DOC / Lead controller / Updated incident action plan for supporting Friday deployment / This should be updated per DOC protocol
28 / 3:00 pm / Final QA check on Mobilization Center preparations / County DOC, VLA / Lead controller / Mobilization Centers should have rosters in hardcopy and electronic (USB drive) form for each Center and venue
Friday, April 26, 2013
29 / 7:30 am / Controller and evaluator check-in / Lead facility controllers / Check in at DOC and Mobilization Centers
30 / 7:45 am / Communication check / Lead controller / All controllers and points of contact at healthcare facilities / Lead controller / Comm check / As needed, if using radios. If using cell phones, consider omitting
31 / 8:00 am / Mobilization Centers set up / Mobilization Centers set up at each of 6 hospitals / Consider moving to earlier?
32 / 9:00 am / Volunteers report for duty; commence Mobilization Center check-in process / Lead facility controllers / Volunteer check-in at each Mobilization Center
33 / 9:13 am / Inject 1: Volunteer fails medical screening (see Expanded MSEL #33 for Actor Script) / Lead facility controllers
34 / 9:43 am / Inject 2: Spontaneous unaffiliated volunteer shows up (see Expanded MSEL #35 for Actor Script) / Lead facility controllers
35 / 10:00 am / Hand-off of volunteers from County (Mob Ctr) to receiving facilities / Lead facility controllers / Volunteer check-in completed; volunteers sent to healthcare facilities for duty
36 / 10:00 am / Receiving facilities begin their volunteer intake process / Lead facility controllers / Volunteer intake at each facility
37 / 10:13 am (approx) / Inject 3: Invalid RN license (see Expanded MSEL #37 for Actor Script) / Lead facility controllers
38 / 10:00 am / Transport – from Mob Ctr to clinics / Lead facility controllers / Volunteers serving at clinics need to get from Mob Ctr to clinic
39 / 11:00 am / Begin individual facility activities with volunteers / Lead facility controllers / 4 hours of planned activities with volunteers / Volunteers need to get lunch at some point!
40 / 1:17 pm / Inject 4: Volunteer becomes ill (see Expanded MSEL #40 for Actor Script) / Lead facility controllers
41 / 3:00 pm / Hot wash of volunteers / Lead facility controllers / Hot wash for volunteers, with healthcare facility staff in attendance / Hot wash conducted by lead controller at each facility, scribed by lead evaluator at each facility
42 / 3:30 pm / Demobilization of volunteers / Lead facility controllers / Volunteers checked out at each facility, demobilization completed; volunteers depart
43 / 4:00 pm / Hot wash of non-volunteer players / Lead facility controllers / Hot wash for all non-volunteer players / Hot wash conducted by lead controller at each facility, scribed by lead evaluator at each facility
44 / 4:30 / Tear-down Mobilization Centers / Lead facility controllers
END OF EXERCISE
45 / May 6
1 – 3pm / Controller / Evaluator Debriefing / Conference call / Controllers
Evaluators
Exercise Planning Team
MSEL Questions:
1. Activation of hospital EOC – on Monday, a unified time for everyone? Or a locally/individually timed activity? We most assuredly won’t have evaluators or controllers for each facility available all week to monitor each HCC, but then, we probably don’t need them. There would be value in each facility assigning someone to these roles for local evaluation.
2. DOC activities – should more be reflected in the MSEL, or is the discovery/planning process part of what needs to be figured out during the exercise?
3. Hospital EOP/HCC activities - should more be reflected in the MSEL, or is the discovery/planning process part of what needs to be figured out during the exercise?
LAC DHV Full-Scale Exercise :: Master Scenario Events List Vers 1 – 2-8-13 page 8
Expanded MSEL – Actor Scripts
Event # / 33 / Event Time: / 9:13 amVia: / In person
Who delivers? / Actor /volunteer / Recipient player(s): / Mob Ctr staff
Event Description:
Volunteer fails medical screening
Inject:
When screened by Mobilization Center staff, olunteer actor reports feeling achy, fluish, and alternately chilled and hot. If temperature is taken, volunteer will inform Mob Ctr staff that temperature is > 38C
Expect Actions/Outcomes:
1. Mobilization Center staff identify correctly identify volunteer as not deployable and directs volunteer to return home or seek care as appropriate.
2. Volunteer is deferred from service.
3. Roster is updated to reflect volunteer is not deployed.
4. Hospital is notified that volunteer is not well and will not be serving.
Event # / 34 / Event Time: / 9:27 am
Via: / In person
Who delivers? / Actor /volunteer / Recipient player(s): / Mob Ctr staff
Event Description:
Spontaneous unaffiliated volunteer reports to Mob Ctr
Inject:
Individual reports for service at the Mob Ctr, but is not on the roster.
Expect Actions/Outcomes:
1. Individual is directed to register for DHV on line.
2. Individual is not processed through the Mob Ctr.
Event # / 37 / Event Time: / 10:13 (approx)
Via: / In person
Who delivers? / Actor / Recipient player(s): / Hospital staff
Event Description:
Volunteer presents with invalid RN license number
Inject:
Volunteer presents RN license number to hospital staff that is not currently valid.
Expect Actions/Outcomes:
1. Volunteer is deferred from service.
2. Roster is updated to reflect volunteer is not deployed.
3. Mob Ctr staff is notified of the volunteer’s invalid license.
Event # / 40 / Event Time: / 1:17 pm
Via: / In person
Who delivers? / Actor / volunteer / Recipient player(s): / Hospital staff
Event Description:
Volunteer becomes ill during deployment
Inject:
Volunteer complains to hospital of flu-like symptoms, shortly after lunch
Expect Actions/Outcomes:
1. Hospital staff notify hospital command center staff
2. HCC notifies incident point-of-contact to county
3. Hospital notifies County (or Mobilization Center)
4. Volunteer is demobilized early
5. Volunteer is directed to appropriate care and/or released from service