The possibility of a large-scale event threatening the health and safety of a large number of residents in Connecticut is sizable. Emergency response plans (ERPs) need to be in place to address concerns including epidemic/pandemic disease, the intentional or accidental release of a hazardous material, contamination of the food and/or water supply, and other incidents that might threaten the 3.4 million residents and could result in mass casualties. For this reason, the State of Connecticut Department of Public Health (DPH; 2005) has developed an ERP to guide the department in the event of a catastrophic threat the lives and safety of the residents of Connecticut. Additionally, the State of Connecticut has developed a State Response Framework, much like the National Response Framework, in order to allow for a modulation of an incident from a local level to a state or federal level (State of Connecticut, Department of Homeland Security, 2010; U.S. Department of Homeland Security, 2008). The ability of an incident response to grow and shrink as an incident dictates follows the natural progression of incidents starting and ending locally, whether involving state or local responses at any time during the response (Walsh et al., 2012).
The ERP (DPH, 2005) that guides the DPH allows for representation in the state EOC while forming a modular incident management team (IMT) to staff the DPH emergency command center. The DPH IMT is designed not only to support the state EOC when activated, but also supports the various local incident commands as a public health and medical service resource. In keeping with the modular aspects of the incident command philosophies and the state and national response framework, the DPS ERP becomes a valuable resource for both initiating a response to a significant threat to the public health and safety and allows for an expert resource when other incidents of magnitude, but not necessarily public health in nature, require or benefit from the availability of public health experts.
One criticism I do have, however, is that the plan (DPH, 2005) does not address the provision of emergency medical services (EMS). For some time, there has been much confusion as to where EMS falls in the realm of emergency service functions. EMS, for many jurisdictions, is a function of the fire department and may fall under the direction of ESF #4, firefighting, especially as many EMTs and paramedics are cross-trained to fight fire. However, ambulances are not firefighting apparatus. As ambulances do transport the ill and injured, perhaps EMS falls to ESF #1, transportation. This is unlikely, though, as the primary need is not the transportation provided but the care rendered. Public health and medical services, ESF #8, seems to me to be the logical category for EMS to fall under, but EMS has an expanded role that also fits ESFs #9, #10 & #13 (search & rescue, oil & hazmat response, and public safety & security, respectively), as well as the aforementioned ESFs #1 and 4. This lack of initial categorization may allow flexibility in the deployment of EMS personnel and equipment, but it could also lead to ineffective deployment strategies resulting in a shortage of EMS in one area and overutilization in another.
State of Connecticut, Department of Homeland Security. (2010, October). State response framework. Retrieved from http://www.ct.gov/demhs/lib/demhs/telecommunications/ct_state_response_framework_v1_oct_10.pdf
State of Connecticut, Department of Public Health. (2005, September). Public health emergency response plan: Emergency Support Function #8 Public health and medical services. Retrieved from http://www.ct.gov/ctfluwatch/lib/ctfluwatch/pherp.pdf
U.S. Department of Homeland Security. (2008, January). National response framework. Retrieved from http://www.fema.gov/pdf/emergency/nrf/nrf-core.pdf
Walsh, D. W., Christen, H. T., Callsen, C. E., Miller, G. T., Maniscalco, P. M., Lord, G. C., & Dolan, N. J. (2012). National Incident Management System: principles and practice (2nd ed.). Sudbury, MA: Jones & Bartlett.