# Patent

## Title
System and method for providing centralized management and distribution of information to remote users

## Abstract

The invention includes systems, methods, and software applications for centrally maintaining information and automatically distributing relevant portions of the information to remote users. In one embodiment, a central server stores the information, which is maintained on the central server. Periodically, or each time the server information is updated, the server identifies the portion of the information that is relevant to each user and downloads the relevant portion of information to each user, for example to a mobile device such as a BlackberryTM. The invention may be used to maintain and timely distribute information related to emergency response procedures, sales or servicing schedules, and delivery schedules, among other things.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
The present application is a continuation and claims the priority benefit of U.S. patent application Ser. No. 10/953,449 filed Sep. 30, 2004, now U.S. Pat. No. 8,601,049 issued on Dec. 3, 2013, which claims the priority benefit of U.S. provisional application No. 60/549,528 filed Mar. 4, 2004, the disclosures of which are incorporated herein by reference.


BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates generally to centralized management and distribution of an organization's information, and, in particular, information regarding emergency response plans, procedures, and contact information, delivery information, and customer service information.
2. Description of the Related Art
Today, businesses and other organizations strive to improve their preparedness for the unexpected. Organizations recognize the importance of continuing their business operations, communicating with personnel, and maintaining the safety of personnel during times of crisis. To do so, businesses and other organizations typically design and maintain a set of rules and procedures to follow in case of an emergency, such as a fire, earthquake, terrorist attack, or other disaster. In the event a disaster strikes, companies, organizations, and institutions expect their personnel to follow the organization's emergency response procedures.
Effective emergency response procedures must be updated periodically. To facilitate personnel's awareness of the updated emergency response procedures and to ensure that all required measures are followed accurately, an organization typically collects and organizes pertinent information for the entire organization and distributes it to a selected group of individuals. Conventionally, emergency response procedures, tracking and reporting information, contact lists, and other information related to emergency response are organized, printed, and compiled in a loose-leaf, paper-based binder or other type of hard-copy manual, and the organization distributes the three-ring binders, and any periodically updated portions, to the personnel responsible for following and implementing the emergency response procedures.
To implement such a system, a number of employees in an organization have to spend time creating, updating, compiling, and distributing manuals and their updated portions to the relevant employees within the organization. Distribution may be especially difficult if the relevant employee is located offsite in a remote office, if the employee travels frequently or for extended periods, or if the employee's job requires being out of the office or away from their desk, such as delivery or sales job that requires visiting customer sites or help desk personnel that visit the offices of IT system users to fix their computer problems. By the time the emergency-response-related information is entered, organized, compiled and distributed, some of the information may be outdated or obsolete.
In addition, the employees responsible for following and implementing the emergency response procedures have to spend time on a regular basis checking to ensure that their binders or manuals contain the most up-to-date versions of documents, contact lists, etc. The relevant employees may neglect to timely update the information that pertains to them, especially if they are busy, travel frequently, or spend little time in an office. This conventional process of collecting and disseminating information is time consuming, costly, and incapable of providing the most up-to-date information on a timely basis. It is therefore desirable to provide an automated system capable of delivering in a timely manner the most current and accurate information, such as emergency response information, directly to the individuals responsible for using the information, such as the employees responsible for following and implementing an organization's emergency response procedures.
Similarly, timely delivery of up-to-date information maintained at a central location is desirable for other aspects of an organization's operations as well. For example, the schedules and tasks for personnel that travel to customer locations, such as service persons, repair persons, or delivery persons, may be created and maintained at a central location, such as a call center. Distributing and maintaining daily printed travel schedules to such personnel suffer the same drawbacks described above for emergency response procedures, perhaps even more so because these travel schedules and tasks can change frequently and with no notice, as customers call in with new requests, cancel previous requests, change the desired visit time of previous requests, request new tasks or services to be performed, or change the particulars of a task or location. Thus, it is desirable to provide a system capable of centrally maintaining yet timely delivering the most up-to-date and accurate scheduling, tasking, and other information to the personnel responsible for implementing the scheduled activities.
SUMMARY OF THE PRESENTLY CLAIMED INVENTION
Embodiments of systems, methods, and software applications consistent with the invention collect and update information, such as emergency response information, in a centralized location and automatically distribute at least a portion of the information to relevant individuals via storage-capable wireless devices, such as a BlackBerryTM handheld device. In one embodiment, the centralized location includes a networked server and network site containing information needed by the offsite individuals. The information on the server is kept up-to-date by staff at the centralized location or through the network. The server sends the latest information pertaining to each individual to that individual's wireless device soon after the information is updated at the central location, and the wireless device stores the information so that the individual can access it on demand.
In accordance with the invention, a system for providing centralized management and distribution of information comprises a central data processing apparatus for maintaining a set of information for an organization and for dividing the set of information into a plurality of subsets of information based on relevance to each of a plurality of users; a network, communicatively connected to the central data processing apparatus, for communicating each subset of information to the user to which the subset is relevant; and a user device, communicatively connected to the network, for receiving, storing, and presenting the subset of information relevant to a user of the user device.
In accordance with another aspect of the invention, a method, system, and software product for providing centralized management and distribution of information, comprises the operations of storing information regarding an organization in a central apparatus; accepting an update to the information; determining a portion of the information that is relevant to a user; communicating the portion of the information to a device associated with the user; and storing the portion of the information on the device.
In accordance with yet another aspect of the invention, a system for providing centralized management and distribution of emergency response procedures, comprises a server containing the emergency response procedures; at least one wireless device for receiving and storing information; and a wireless communication network for connecting the wireless device and the server, wherein the server sends a portion of the emergency response procedures to the wireless device when the emergency response procedures are updated; and the wireless device receives and stores the portion of the emergency response procedures.
In accordance with yet another aspect of the invention, a system for providing centralized management and distribution of item delivery information, comprises a server containing the item delivery information; at least one wireless device for receiving and storing information; and a wireless communication network for connecting the wireless device and the server, wherein the server sends a portion of the item delivery information to the wireless device when the item delivery information is updated; and the wireless device receives and stores the portion of the item delivery information.
Additional objects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.



BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is an exemplary generic wireless mobile device;
FIG. 2 depicts an exemplary system that connects a database server and a mobile device having wireless access;
FIG. 3 depicts another exemplary system connecting a database server with mobile devices;
FIG. 4 is an exemplary Access Rights Privilege and Security Matrix identifying groups of access rights for different groups of the employees;
FIG. 5 is a flowchart of an exemplary process consistent with the present invention; and
FIG. 6 is a flowchart of another exemplary process consistent with the present invention.



DETAILED DESCRIPTION
An organization, such as a company, business, partnership, business division, department, or section, may maintain all of its emergency-response-related information in one database, for example, as an Electronic Continuity of Operations Plan (eCOOP). Such a database may reside in a memory device, such as a semiconductor storage device, magnetic storage device, or optical storage device, among others, on a main central server supported, for example, by Oracle PL/SQL database application. The system may include a redundant backup server at a separate location, mirroring the information on the primary server and available to perform its functions if needed.
The eCOOP may contain emergency response information, for example, procedures, instructions, tasks, contact lists, emergency planning information, and other emergency-response-related documentation. The eCOOP may also contain a list of the employees authorized by an organization to receive emergency-response-related information.
To enable an organization's employees to remotely receive downloaded emergency-response-related information from the eCOOP server, an organization may provide each designated employee with a mobile device having wireless access to e-mail or other wireless or remote data-download capability, for example, a BlackBerryTM device. FIG. 1 depicts an exemplary generic mobile handheld device, such as a BlackBerryTM 108. Each such BlackBerryTM 108 may be wirelessly connected to a server where the eCOOP resides. Using his or her BlackBerryTM 108, an employee may remotely receive emergency-response-related information directly from the eCOOP via e-mail or other data-download technique. Other wireless mobile devices, such as a laptop PC with a wireless card or a Palm PilotTM, among others, may be used.
FIG. 2 depicts an exemplary system 200 that connects a database server 202 and a mobile device 208 having wireless access to e-mail or other download techniques, which are well known in the art. In the embodiment shown, database server 202 may send a new or updated set of information, such as emergency-response-related information from an eCOOP, to a network server, such as a BlackBerry Enterprise Server (BES) 204. In the embodiment illustrated, once the network server 204 receives new or updated information from the database server 202, it forwards this information to each individual mobile device 208 via the organization's firewall 206, a network (such as the internet 210), and a wireless network 212.
In one embodiment consistent with the invention, the database server 202 determines the portion of the organizational information that pertains to each user of a mobile device 208, and sends just that portion of the information to the device 208 of each user. Thus, a user's mobile device 208 receives only the information relevant to that user. In the eCOOP example, a user's mobile device 208 may receive and store emergency response checklists for that particular user to implement, contact lists for employees that report to that user and whom the user must call in case of an emergency, or the address of an alternate work or meeting site that the user should report to in case of a disaster. Server 202 may make this determination using a software application that considers, among other things, the user's title within the organization (e.g., department manager), the user's designation within the system framework (e.g., regional emergency response coordinator), the user's primary work site, an access control list, or other information regarding the user maintained in server 202.
Although several of the described embodiments of the invention utilize a database to store information, those of ordinary skill in the art will recognize that organizing the information in a database is not critical to the invention. The information may be stored in any way that allows it to be accessed, modified, and sent out to users, without departing from the principles of the invention. For example, the information may be contained in a word processor file that may be the basis for a hardcopy manual, such as an emergency response procedures manual, or it may be contained in a calendar file, such as Lotus NotesTM file.
Further, although many embodiments are described in the context of emergency response information, one of ordinary skill will recognize that the invention encompasses other applications such as outside service or sales call applications, inside service call applications (help desk), or item delivery applications. Many organizations may employ one or more of these and other applications, such as, for example, the United States Postal Services (USPS), Federal Express, United Parcel Service, and other delivery businesses.
FIG. 3 depicts an exemplary system connecting a database server 302 with mobile devices 306. In the embodiment shown, an organization may use a software application, such as a “push” application, to forward, for example via e-mail, new or updated information, such as emergency-response-related information in an eCOOP system, to designated mobile devices. In one embodiment, the push is done automatically, without a specific request from the mobile device user.
More specifically, when a new or updated set of information, such as eCOOP emergency-response-related information, is ready for forwarding to the mobile devices 306.sub.1 through 306.sub.x, the push application server 302 sends a request to a software application residing on a mobile device server, such as the Mobile Data Service feature of the BlackberryTM Enterprise Server (BES) 304, which were developed by the Research In Motion Ltd. Company. In response, the Mobile Data Service acknowledges that it received the request, converts the contents of the request, and passes it to BES 304. BES 304 compresses, encrypts, and forwards the converted contents of the request to the appropriate mobile devices among 306.sub.1 through 306.sub.x. As shown, each mobile device 306.sub.1 through 306.sub.x, such as a handheld BlackBerryTM device, receives the compressed and encrypted contents of the request via a wireless network 308. Once the pushed information is received, each mobile device 306 may send an acknowledgement of receipt to the Mobile Data Service.
In one embodiment consistent with the invention, an organization may use the push application to download a new or updated set of emergency-response-related information to its personnel's mobile devices 306 every time new or updated information is entered into the database on server 302. In another embodiment, an organization may push emergency-response-related information to mobile devices 306.sub.1 through 306.sub.x on a regular basis, for example, every seven days, regardless of whether or not new information was entered into the database on server 302. Once a mobile device 306 receives information, such as eCOOP emergency-response-related information, it may locally store such information indefinitely or until overwritten by a subsequent download of updated information. Thus, personnel with a mobile device 306 have continuous access to up-to-date information even if the connection between the mobile device 306 and the wireless network 308 is disrupted, the servers 302 or 304 malfunction, or the connection between server 304 and the network 308 is disrupted. Periodically pushing information, such as emergency-response-related information, into mobile devices 306, helps ensure that all personnel responsible for implementing or acting on the information, such as performing emergency response procedures, automatically and consistently receive up-to-date and accurate information that is relevant to them.
FIG. 4 is an exemplary Access Rights Privilege and Security Matrix 400 identifying groups of access rights for different groups of employees. To control access to a central database of organization-wide information that needs to be disseminated to certain employees, and maintain its security, an organization may assign certain access privileges to designated employees, for example, rights to view, enter, update, and modify the contents of an eCOOP information database, or a delivery information database, or a service call information database. In one embodiment, an organization may have a tier system identifying different combinations of access rights for different groups of employees within an organization. For example, as shown in row 402, an organization may grant all employees designated as active users of the system a right to view the information related to all users in general, such as the complete set of emergency response procedures stored in an eCOOP database. In one embodiment, active users may also have a right to download such information on demand. In another embodiment, an organization may restrict the viewing and downloading privileges of certain groups of its employees, effectively blocking certain areas of the database from access by specified groups of employees. For example, in an eCOOP-type embodiment, an organization may block from viewing and downloading a portion of the contact list for all the users located outside of the geographical area related to that portion of the list.
In one embodiment consistent with the invention, users have write access to portions of the information in the main central database. For example, as shown in row 402, an organization may allow all the users of the system to change their own user profile, including information such as contact information, name, phone number, and address of their BlackBerryTM, laptop computer, home computer, or other device that may receive and store information for them. In another embodiment, an organization may prevent certain users from modifying their own information, or have users submit a change request to the personnel maintaining the central database, who then make the requested changes to the database.
As shown in row 404, system administrators may have the right to view, enter, delete, modify, and update any data contained in the information database. That right may include the right to add or delete users of the system and their contact information, such as their BlackBerryTM or other mobile device address.
As shown in row 406, headquarters administrators may have a right to view and modify data related to the headquarters. They also may have a right to add users and their contact information. An organization may also grant headquarters administrators a right to modify contact information of the existing users.
As shown in row 408, area administrators may have a privilege to view and modify data related to their area contained in the information database. That privilege may include the right to add users of the system and their information distribution contact information, such as their BlackBerryTM address or home computer address. Area administrators may also have a right to modify contact information of the existing users of the system.
As shown in row 410, organization administrators may have a right to view and modify data related to the organization. They also may have a right to view and modify a user's level of access and add new users and their contact information. In one embodiment consistent with the invention, additional levels of administrators with different combinations of access rights may be added by the organization. For example, an organization may designate department administrators as having rights to view, modify, and add information for new users from their department.
In one embodiment consistent with the invention, to enhance the information content and usefulness for each user, an organization may offer users the option of customizing their own user information and presentation in the central server database, so that it appears among the organization's information. For example, in an emergency response system embodiment such as eCOOP, a user may add a task of picking up children at school to the emergency response task list maintained in the eCOOP database; or the user may be allowed to modify their local copy of the task list that was downloaded to their mobile device or home computer. As another example, a user may add names and contact information of friends and relatives to the contact list maintained as part of the eCOOP information.
One skilled in the art will recognize that many alternative embodiments of the scheme shown in FIG. 4 are possible within the scope of the invention. For example, an organization may restrict the information that certain groups of users may view and download. As another example, an organization may limit access for certain groups of users to various partitioned areas of the information database, such as an eCOOP database.
FIG. 5 is a flowchart of an exemplary process consistent with the present invention. Such a process may be implemented as a software application(s) running on conventional data processing system, such as a central server, on a hardwired system, or as a combination of the two. In the embodiment shown, the process begins by receiving information on a central server (step 510). The information may pertain to any of several categories, such as emergency-response-related information, continuation-of-operation-plan-related information, delivery-schedule-related information, customer-service-call-related information, sales-call-related information, help-desk-request-related information or other centrally maintained information that needs to be provided to remote users in a timely manner. The system implementing the process may receive information manually from personnel that maintain the information or automatically from other systems that maintain or contribute to the information. The exact manner in which the information is received and maintained is not critical to the invention. The information may be stored as a database, spreadsheet, word processing file, organized data collection, or some other data-storing entity. The exact data-storing entity is not critical to the invention.
Next, the process determines a subset of information that is relevant to each remote user (step 515). For example, in the case of continuation-of-operations plan information, if the remote user is the manager of a department, the subset of information may include the emergency response procedures for the department, a contact list for the department employees who report to the manager, and an alternative work site where the department would meet and organize in case of an emergency. It would not include information from other departments other than the one that the user manages. As another example, in the case of customer service call information, if the remote user is a service technician the subset of information may include a schedule of appointments for the day for the remote user, addresses of each customer to be visited by the remote user, a description of the service to be performed for each customer, and driving directions from one customer location to the next. Similar subsets of information may be relevant to an inside service person, such as help desk personnel. As yet another example, in the case of delivery information, if the remote user is a delivery person, the subset of information may include a schedule of deliveries for the day for the remote user, addresses of each delivery, a description of the item to be delivered to each customer, and driving directions from one delivery location to the next.
The process then downloads to remote users (preferably, each remote user) the subset of information relevant to that user (step 520). This may be accomplished by downloading to a mobile device associated with the user, such as a BlackberryTM, Palm PilotTM, cellular telephone, laptop computer with a wireless network card, laptop computer connected to a designated website, specialized receiving system in a delivery vehicle, satellite radio, GPS device, or other mobile device associated with the user that is capable of receiving and storing data.
In step 525, the process determines whether the information on the central server has been updated. The information may be updated by personnel or systems dedicated to maintaining the information so that it remains accurate and up-to-date. The information may be updated for many reasons. For example, in the case of continuation-of-operation-plan information, the information may be updated if emergency response procedures change, if the personnel involved with the emergency response procedures change, if the personnel contact information changes, or other reasons. As another example, in the case of customer service call information including both outside customer services, such as telephone repair, and inside customer services, such as an IT help desk, the information may be updated if a new trouble ticket comes in, a customer calls and cancels a service call, if a new service call is added, if a customer availability time changes, if another service person phones in sick and their calls for the day must be reassigned, or other reasons. As yet another example, in the case of delivery information, the information may be updated if a delivery address changes, if a new delivery is added to the schedule, if an item does not arrive from a prior location in time to be delivered as scheduled, if another delivery person calls in sick, if additional delivery persons become available to assist with the day's deliveries, or for other reasons.
If the information on the central server has been updated (step 525, Yes), then the process returns to steps 515 and 520 to determine a subset of information for each user from the updated information, and download the relevant updated subset to each user. If, on the other hand, the information on the central server has not been updated (step 525, No), then the process loops to receive updated information on the central server as needed (step 530). As noted above, there are numerous reasons that may cause the central server information to be updated.
One of ordinary skill will recognize that steps may be added to, deleted from, or modified in the process depicted in FIG. 5 without departing from the principles of the invention. For example, steps could be added to check whether the updated information received in step 530 came from a person authorized to update the information, and if not, to reject the information and prevent it from being downloaded to remote users.
FIG. 6 is a flowchart of an exemplary process consistent with the present invention. Such a process may be implemented as a software application(s) running on a conventional mobile data processing device, such as a BlackberryTM or laptop computer, as a dedicated hardwired mobile device, or as a combination of the two. In the embodiment shown, the process first receives information tailored to a user (step 604), such as the subset of information determined in step 515 of FIG. 5. In the embodiment shown, the received information is tailored such that it consists largely or wholly of information relevant to the user from among a greater set of information that is relevant to several users or an entire organization. For example, if the user is a delivery person, the information may include only the delivery schedule that must be run by that delivery person, and exclude information concerning the delivery schedules of other delivery persons in the same organization. In another example, if the user is a department employee, the information may include the specific emergency response procedures to be followed by that employee in case of a disaster, excluding the emergency response procedures of other departments and other employees. In another embodiment consistent with the invention, the received information is not narrowly tailored to the user and contains information beyond the minimum that the user needs to know.
Next, the system running the process stores the information (step 610). In one embodiment, the stored information is retrievable on demand by the user. For example, if the receiving device is a BlackberryTM, it may run a custom software application that stores the received information and allows the user to access it by selecting an icon associated with the application on the Blackberry's touch screen. Next, the process may occasionally receive updated information tailored to the user of the receiving device (step 615). As noted above with respect to FIG. 5, the information may be updated and sent to the user for many different reasons independent of the user and without the user's knowledge or input.
The next step of the process stores the updated information (step 620). In one embodiment, the stored updated information is retrievable on demand by the user.
In the embodiment shown, the process then determines whether it has received a triggering notification (step 625). For example, in the context of a continuation-of-operations plan system, the triggering notification may be an email, phone call, fax, or other communication of the occurrence of a disaster that requires implementation of emergency response procedures. In another example, in the context of a delivery or service call system, whether inside or outside, the triggering notification may be an email, phone call, fax, or other communication of the occurrence of a change in delivery or service schedule. In yet another example, in the context of an inside service call system, the triggering notification may be an email, phone call, fax, or other communication of the occurrence of a new problem being experienced by a user of an organizations IT system.
If the process has not received a triggering notification (step 625, No), then it continues to receive and store updated information for the user. If the process has received a triggering notification (step 625, Yes), then it presents the stored information to the user (step 630). For example, a mobile device receiving the notification may generate an audible signal or vibrate and display the stored information on its screen after receiving a triggering notification, or it may use voice synthesis to present the information orally to the user.
One of ordinary skill will recognize that steps may be added to, deleted from, or modified in the process depicted in FIG. 6 without departing from the principles of the invention. For example, in the case of an eCOOP system, steps could be added to automatically contact, for example via email from a mobile device, persons on an emergency response contact list when a triggering notification is received. For another example, step 630 could be deleted, so that the user would have to manually access the stored information after receiving a triggering notification.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

## Claims

1. A method for receiving distributed centralized emergency response information, the method comprising:
receiving, at a device associated with a user, emergency response information after the emergency response information is updated in a central data storage apparatus, the emergency response information being relevant to the user and transmitted to the user automatically based on access rights of the user corresponding to a level and an area of responsibility of the user;
storing the information locally; and
presenting the stored emergency response information to the user.

2. The method of claim 1, wherein the emergency response information is a subset of emergency response information from a set of emergency response information regarding an organization.

3. The method of claim 1, wherein the emergency response information includes an emergency response procedure or an updated portion of an emergency response procedure.

4. The method of claim 1, wherein the emergency response information includes instructions, tasks, contact lists, or emergency planning information.

5. The method of claim 4, wherein the instructions include identifying an alternative work site.

6. The method of claim 5, wherein the alternative work site is identified because of an emergency.

7. The method of claim 1, wherein the emergency response information is received periodically regardless of whether the emergency response information has changed, and wherein the device is a Blackberry® device, a personal digital assistant, a laptop computer, or a home computer.

8. The method of claim 1, wherein the method is implemented on a non-transitory computer readable storage medium having embodied thereon a program executable by a processor in the device.

9. The method of claim 1, further comprising the user downloading the emergency response information on demand.

10. The method of claim 1, further comprising:
the user updating the emergency response information; and
storing the updated emergency response information in the central data storage apparatus.

11. A method for providing centralized management and distribution of emergency response information to users, the method comprising:
storing emergency response information regarding an organization and access rights for a plurality of users to the emergency response information in a central data storage apparatus with the plurality of users collectively having a plurality of levels and a plurality of areas of responsibility in the organization and each individually having at least one of the plurality of levels and at least one of the plurality of areas of responsibility in the organization;
accepting an update to the information by the central apparatus;
determining a portion of the information that is relevant to a user and is allowed to be transmitted to the user by the user's access rights; and
transmitting a selected portion of the emergency response information in the central apparatus to the user.

12. The method of claim 11, wherein the selected portion of the emergency response information transmitted to the user is a subset of emergency response information from a set of emergency response information corresponding to the user's responsibility in the organization.

13. The method of claim 11, wherein the emergency response information includes an emergency response procedure or an updated portion of an emergency response procedure.

14. The method of claim 11, wherein the emergency response information includes instructions, tasks, contact lists, or emergency planning information.

15. The method of claim 14, wherein the instructions include identifying an alternative work site.

16. The method of claim 15, wherein the alternative work site is identified because of an emergency.

17. The method of claim 11, wherein the emergency response information is transmitted periodically regardless of whether the emergency response information has changed.

18. The method of claim 11, wherein the method is implemented on a non-transitory computer readable storage medium having embodied thereon a program executable by a processor in a centralized server that is in communication with or contains the central data storage apparatus.

19. The method of claim 11, further comprising transmitting the emergency response information when demanded by a user.

20. The method of claim 11, wherein the transmitting of the emergency response information is performed using a wireless communications link.