Due to the perceived challenges of building, maintaining and coordinating access to a Vulnerable Needs Database, many state and local governments are ill-equipped to support their vulnerable citizens in an emergency. Yet solutions exist to overcome these challenges - solutions that can save many thousands of lives.
In 1993, a year after Hurricane Andrew revealed an elderly population grossly underprepared for a disaster, Florida became the first state to enact legislation requiring local emergency management agencies to maintain a vulnerable needs database or registry. The registry was populated by data available through the state's Department of Health and Rehabilitative Services, and reminders for registered citizens to update their information are sent once a year by utility companies.
In subsequent years, several state and local governments have followed Florida's lead. Delaware, Utah, New Jersey and North Dakota are among ten states that now maintain state-wide vulnerable needs registries; while multiple counties and cities throughout the United States operate smaller-scale registries. Some jurisdictions also have vulnerability-specific registries. For example, the Division of Deafness in Maine maintains a registry for citizens who are hard of hearing.
Defining a Vulnerable Needs Registry
To best understand the challenges of building, maintaining and coordinating access to a vulnerable needs registry, it is necessary to first define what a register for vulnerable citizens is - not necessarily to answer the question “What is a Vulnerable Needs Registry?”, but rather to explain what it consists of, the options for populating and maintaining it, and its objectives. There are also eligibility questions to answer, such as what is the eligibility for inclusion in the registry?
Most definitions of a vulnerable needs registry describe it as a database of citizens who would need specific support before, during or after an emergency. The database identifies the number, location, and needs of registered citizens in order to allocate resources during emergency response planning and to deliver assistance when and where it is required. The database does not necessarily have to be computerized. Some localized, vulnerability-specific registries are maintained on paper.
There are several options for populating and maintaining registries. Whereas Florida's vulnerable needs register was populated by existing Department of Health data, many subsequent registries required eligible citizens (or their representatives) to self-register and self-update records in order to overcome consent and privacy issues.
Compliance with privacy regulations is one of the major challenges to state and local governments considering the implementation of a Vulnerable Needs Register.
The objectives of a vulnerable needs registry are to make sure the right resources are in the right place at the right time. For example, appropriate modes of transport and shelter may need to be in place prior to an emergency to facilitate an evacuation; backup power sources may be needed during an emergency by individuals who have electrically-powered medical equipment; and unique communication channels may need to be established with vulnerable citizens following an emergency.
What constitutes a vulnerable citizen can also be challenging to state and local governments. During an emergency, there are only limited resources available. To open a registry for individuals who have relatively minor vulnerabilities could compromise the ability of emergency response teams to deliver assistance to those in the greatest need. Therefore each government authority has to balance eligibility criteria against the resources it has available to assist citizens registered in its database.
In the case of many state and local governments, the perception is that building, maintaining and coordinating access to a registry is too expensive for the potential benefits. There are also the costs of equipment and training to consider and compliance with security and privacy regulations. But what if the cost issues could be overcome? What if there was a way in which a database of vulnerable citizens could be built and maintained, and access coordinated within a reasonable budget?
Build vs. Buy - How to Overcome the Cost Issues
The perception that vulnerable needs registries are too expensive for the potential benefits has evolved from the experiences of state and local governments that implemented databases in the 1990s. These registries were built on Records Management Systems and SQL Databases that - at the time - were high maintenance technologies. Today the story would be different due to technological advances. So, is it time to change the perception of how much vulnerable needs registries cost?
The Case for Building a Database
Undoubtedly the costs of building and maintaining a database are much less than they were twenty years ago. The development of cloud computing has substantially reduced the cost of hosting a database and resolves many of the security issues associated with data protection. Furthermore, twenty years on from the early days of SQL Databases, more people are familiar with database management, so the cost of training system administrators would also be negligible.
There are however as many challenges - if not more - than twenty years ago. For example, the passage of the Healthcare Insurance Portability and Accountability Act (HIPAA) in 1996 means that healthcare facilities such as nursing homes and assisted living residences (which between them accommodate 2.3 million vulnerable citizens) would have to seek the authorization of their residents in order to “disclose” their health information to a local authority.
In order to add the disclosed health information to a vulnerable needs registry, the local authority would have to sign a “Data Use Agreement” that effectively commits it to comply with the technical, physical and administrative safeguards of the HIPAA Security Rule.
Other challenges include how independent citizens register for inclusion in the database and how their information is updated. One of the criticisms of the vulnerable needs registries operating in Massachusetts and Vermont is that vulnerable citizens have to complete a paper registration form and email it to the database coordinator. From there the data and any subsequent amendments are entered manually onto the registry, increasing the cost of database maintenance.
In its defense, Vermont is one of the few states in which inclusion on its vulnerability needs registry is subject to an annual renewal. The state's system is also E911 compatible so the location of a vulnerable citizen can be traced via their mobile phone signal. However, the data recorded is limited to the options provided on its registration form, which are evacuation-orientated and not of any great benefit once a disaster has occurred. More options have to be provided to cover all eventualities.
Factors to consider before making a final decision
While the cost of building and hosting a database is less, these potential roadblocks should be taken into consideration:
- There are more compliance issues to overcome
- The costs of administering a database remain an issue
- Few authorities ensure data is renewed or kept up-to-date
- Limited data capacity limits the effectiveness of emergency response
- Many systems are landline-based and lack compatibility with E911
- There is no portability between Vulnerable Needs Registries in different locations
The Case for Buying a Database
What is meant by “buying a database system” is the purchase of an emergency management platform that is integrated with an existing citizen-populated database to create a vulnerability needs registry with the click of a mouse. Provided the existing database complies with privacy and data security regulations, is self-administered, has vast data capacity, E911 compatibility and portability, the only challenges for state and local governments are the cost of the platform and education.
The cost of the platform is easy to justify. According to the International Association of Chief of Police's “Voluntary Registry Programs for Vulnerable Populations” report, the cost of one search and rescue effort is $13,500. With a greater amount of data available to 911 dispatchers and first responders - and E911 compatibility - search and rescue times can be significantly reduced, and search and rescue efforts more likely to result in a positive outcome. The platform not only saves money but saves lives.
Using pre-built vulnerable population databases during a disaster, emergency managers easily identify residents in need of assistance, communicate with them, and assign resources to send help. Some databases have an interactive web-based map interface that allows emergency managers to create queries by demographics or location to single out any group or segment in need of assistance.
Factors to consider before making a final decision
While the cost of a platform might come into question, here are a few reasons why it should be considered:
- The cost of the purchase is easy to justify
- There are no privacy or data security issues
- Zero costs related to database administration
- Data is reviewed regularly by those who know their needs best
- Vast data capacity allows for extensive information to be entered
- E911 compatibility and registry portability results in more positive outcomes
An emergency management platform with a web-based, citizen-provided vulnerable needs registry gives emergency planners accurate information about the number of vulnerable citizens, the nature of their vulnerabilities, and the assistance they would need in the event of an emergency. With this information, emergency planners can prioritize their resources to ensure they are in the right place at the right time to provide assistance to their community's most vulnerable members.
you may also like
How California's Disaster Communication Plan Failed Residents During Deadly Wildfires
March 28, 2018
“People didn’t die from the smoke. People didn’t die from the fire. People died because they didn’t know something was coming.”
-Joseph Solis, former 911 dispatcher employee...