200 likes | 317 Views
EMSTAT Case Study. August 2011. Common Terms. 2009 to 2010: The Basics. SILOS. SILOS. EMSTAT Use Case: River Flooding. Threat Description:
E N D
EMSTAT Case Study August 2011
2009 to 2010: The Basics SILOS SILOS
EMSTAT Use Case: River Flooding • Threat Description: • Significant rainfall across the middle Mississippi and Ohio River valleys led to historic, and in some cases record breaking rises on both rivers. As this water moves downriver, significant rises will occur throughout Louisiana along the Mississippi and Atchafalaya Rivers. • Timeline: • Louisiana was in active response (state EOC activated) for approximately 34 days. • The response event was initiated on April 27, 2011 and concluded with de-escalation of the State EOC to a monitoring level on June 1st.
ESF 8 Response • ESF 6 ( Mass Care) and ESF 8 (Health and Medical response) were actively engaged with readiness activities to support: • Search and Rescue • Shelter readiness and strike teams to visit shelters • Water system monitoring, boil water notice distributions as needed • Outreach to at-risk hospitals, nursing homes and assisted living facilities • Included once-daily reporting by hospitals and nursing homes in EMSTAT • Outreach to vulnerable populations located in the at-risk areas
ESF 8 Response • EMSTAT reporting for hospitals started on Saturday, May 14th with messaging that went out on May 13th • Nursing homes were required to start reporting on Wednesday May 17th with messaging that went out on May 16th • Daily reported lasted until Tuesday May 24th
ESF 8 Response • During the period of May 9th to May 24th, there were two full evacuations, two partial evacuations and one closure: • Full Evacuations • 1 Nursing Home (Camelot NH) • 1 Hospital (Promise Hospital) • Partial Evacuations • 2 Nursing Homes (Heritage Manor and Morgan City Health Care Center • Closures • 1 Ambulatory Surgical Center (River Park ASC)
Lessons Learned • Clear messaging in the activation notifications • Need for real-time access to contact data in EMSTAT (being addressed in Stage 1) • Cross-training of personnel in facilities • Weekend staff often unfamiliar with protocols, reporting requirements, and user account codes. • Rapid follow-up with sanctions • Clear and timely feedback to facilities • Push compliance reporting capabilities to facility-level • Being addressed in Stage 2
Origins of EMSTAT • EMSTAT was developed after the storms of 2008 • During the storms we had limited visibility into the operational status of critical healthcare facilities • Anecdotal reports from the associations • Endless phone calls and bad data • We didn’t know what we didn’t know
What We Had in 2008 SILOS SILOS
Our Classroom • Gustav and Ike combined: • 42 hospitals without power, some for several weeks • Faced a potential evacuation of major institutions in the Baton Rouge area • 24 nursing homes without power, some for several weeks • Hundreds of fuel requests, some with as little as 30 minutes notice • “Children will die…” • Requesting un-needed resources • “We thought we could get you to top off our tanks” • “1 surgical suture kit” • “Cans of mosquito repellant and sunscreen”
Problems Identified • Visibility is needed on the following facility conditions: • Operational status • Evacuation status • Power and fuel status • Census by bed type and bed availability • Need easy access to key facility staff and contact information • Need event messaging capability
Problems Addressed • Visibility is needed on the following facility conditions: • Operational status • Evacuation status • Power and fuel status • Census by bed type and bed availability • Need easy access to key facility staff and contact information • Need event messaging capability • Being addressed with Incident Management and Messaging module in Stage 1 Re-design
HIE Opportunities • Primary: • Automate bed availability and census reporting from hospitals • Secondary • Other status indicators as available • Dependent on source data availability