US20090018869A1 - Method and system for data aggregation for real-time emergency resource management - Google Patents
Method and system for data aggregation for real-time emergency resource management Download PDFInfo
- Publication number
- US20090018869A1 US20090018869A1 US12/243,860 US24386008A US2009018869A1 US 20090018869 A1 US20090018869 A1 US 20090018869A1 US 24386008 A US24386008 A US 24386008A US 2009018869 A1 US2009018869 A1 US 2009018869A1
- Authority
- US
- United States
- Prior art keywords
- resource
- resource availability
- information
- data
- availability
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
Definitions
- the present invention relates generally to a resource management system for use by personnel managing an incident. Additionally, the present invention relates to a computer system and method for emergency personnel to efficiently collect, store, aggregate and manage availability information regarding resources and equipment according to the needs of the patients, evacuees, people or those injured.
- a multiple-victim disaster or an emergency can overwhelm ill-prepared local or state officials. This is especially true if resources available to handle the disaster or the emergency are constrained.
- disaster victims may be routed to medical facilities where the medical resources (number of available beds, facilities to treat a certain type of victims) are limited or already in use for treating similar victims from the same disaster location or another disaster location.
- the system should be able to categorize these resources and the patients/victims needs so that it can better direct the patients/victims according to the type of resource required to treat the patient/victim.
- the system should also be able to track the availability of resources from multiple facilities across regions, cities and in certain cases across states. This system should be accessible at the emergency location or at multiple locations in case of a natural disaster to enable central tracking of the resources.
- the system should also support communication of resource status and availability across one or many users in the region, city, county, state or other response territory.
- this system should utilize common standards such that different facilities can use existing systems to connect to such a system and report their resource availability.
- This system should be able to collect availability information from a number of facilities and aggregate the data so that people responsible for managing the emergencies are provided with aggregated counts by cities, regions or other aggregation criterion.
- U.S. Publication No. 20030074222 titled “System and method for Managing Patient Bed Assignments and Bed Occupancy in a Health Care Facility” describes a computer implemented system for managing the assignment of beds in a medical facility.
- the claimed system functions in conjunction with an admission/discharge/transfer system and keeps track of the beds in a medical facility and the assignment of beds to incoming patients. It also displays a real-time status of the beds available in the facility and the beds that are currently assigned to patients in the facility.
- U.S. Publication No. 20040243446, titled “Method and a System for Optimizing Hospital Beds and Ambulance Allocations via a Computer Network” describes a computer based system that enables users to view the real-time status of beds available in a medical facility such as a hospital. Further, the system enables the hospital to communicate this status to an ambulance that is directing one or more patients to the hospital. If the hospital does not have the available capacity to accommodate the patients being transported in the ambulance, then the ambulance is redirected to a second facility or hospital.
- the system should also be able to list resources by type so that availability of a certain type of resource, such as, bed capacity by triage category is readily available. Additionally, the system should be able to gather resource availability information from different regional systems and medical facilities. It should be able to present this information at the time of emergency so that the information can be used to make better decisions.
- a first aspect of the present invention is to provide a system for providing resource information to a user, the resource information comprising availability of resources in at least one facility in at least one region, the system including at least one database, the at least one database storing the resource information for at least one facility, an access control module for controlling access to the resource information stored in the database, at least one client for viewing the resource information, a resource interface module for collecting resource information from the at least one facility in the at least one region, and a data aggregation module for aggregating the collected resource information based on one or more attributes associated with the resource information, wherein the data aggregation module is operable to access the information on the at least one database.
- a second aspect of the present invention is to provide a method for providing resource information to at least one user, the resource information comprising availability of resources associated with one or more facilities in one or more regions, the method including the steps of collecting resource availability information from at least two facilities, the resource availability information further comprising a region associated with the facility, storing the resource information in a database along with a timestamp identifying a date and time at which the information was collected, aggregating resource availability information by summing resource availability based on the region associated with each of the facilities, and providing the aggregated resource information to the at least one user.
- FIG. 1 is a schematic view of the overall system in accordance with an embodiment of the present invention.
- FIG. 2 is a schematic view of a system for providing clients with resource information, in accordance with an embodiment of the present invention.
- FIG. 3 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with the same region, in accordance with an embodiment of the present invention.
- FIG. 4 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with another region, in accordance with an embodiment of the present invention.
- FIG. 5 is a flowchart depicting the steps involved in giving access to resource information to a user for a specific event, in accordance with an embodiment of the present invention.
- FIG. 6 is a schematic of the system for polling resource information from external resource stores and providing aggregated resource information to external users and databases, in accordance with an embodiment of the present invention.
- FIG. 7 is a schematic view of the system for communicating with external state and federal resource databases, in accordance with an embodiment of the present invention.
- FIG. 8 is a schematic view of an exemplary XML schema for exchange of resource availability information, in accordance with an embodiment of the present invention.
- the present invention provides a method and system for aggregating resource availability information collected from multiple facilities in one or more regions.
- the present system tracks medical and non-medical resource availability information by type and provides it to users requesting the information.
- the system collects availability information from individual hospitals and other medical facilities. This is enabled through a web interface that connects to the facilities and queries the availability data through industry standard techniques. There is an addition web interface that allows administration personnel to connect to the system and manually input the resource availability information.
- the system can also connect to central systems, such as those maintained by states, counties, etcetera to collect availability information.
- the system is setup to collect the resource availability information at pre-determined time intervals; alternatively the time intervals are determined ad hoc or as needed. These intervals are user defined and can be changed/modified as per the user requirements.
- the system collects resource availability information, such as availability information about hospital beds, and stores this information in a database. This information is stored along with the time at which it was collected. This allows uses who query the system, to obtain the latest information along with the time at which it was obtained. This is important in emergencies, where personnel directing patients should have access to the latest information.
- Resource information collected from individual medical facilities is stored in a database.
- a region that the medical facility is associated with is also stored along with the resource information. This region can be a city, county, state, or any other geographic region that can be used to aggregate data.
- the system also allows for protecting the resource information, and the resource information is provided only to authorized users. Further, the users are only authorized to view resource information for certain specified resources. This enables the system of the present invention to restrict certain users from viewing resource information from resources that they are not authorized to view. Administrators of the system can define resources by region. Additionally, they can define the regions for which the users are authorized to view resource information. In certain special cases, the administrators can grant access to certain users to view resource information for regions for which the users are not initially authorized. This can be done on a per user basis, for a specified time frame or for a specified medical emergency or event.
- the present invention provides for tracking of medical resources including but not limited to hospital beds, hospital rooms, Emergency Medical Services such as ambulance availability, medical personnel availability, availability of medical equipment such as defibrillators, decontamination facilities, negative pressure isolation rooms, ventilators, etc. These resources are tracked across one or multiple regions. A region can be defined as a part of a town or city, a town, city, county, state and even a country.
- the present invention also provides for tracking of non-medical resources including but not limited to shelters, vehicles, equipment, beds and other resources such as capacity in shelters, etc.
- the present invention also provides a method and a system for interacting and exchanging resource information from other systems, such as Crisis Information Management System (CIMS), Computer Aided Dispatch system (CAD), Hospital Alert Network (HAN), etc.
- CIMS Crisis Information Management System
- CAD Computer Aided Dispatch system
- HAN Hospital Alert Network
- the present invention also provides a method and a system for gathering, aggregating, storing, and exchanging information to support regional or federal guidelines including Hospital Availability Exchange (HAVE) guidelines (see “HAVE.” COMCARE; available at http://www.comcare.org/HAVE.html, herein incorporated by reference in its entirety) and Hospital Available Beds in Emergencies and Disasters (HAvBED) specifications (see “National Hospital Available Beds for Emergencies and Disasters (HAvBED) System: Final Report.” AHRQ Publication No. 05-0103, December 2005. Agency for Healthcare Research and Quality, Rockville, Md.; available at http://www.ahrq.gov/research/havbed/, herein incorporated by reference in its entirety).
- HAVE Hospital Availability Exchange
- HAVE Hospital Availability Exchange
- the system allows users to update the status of the resources of one or more facilities that the users are associated with, and is capable of reporting resource availability in standard categories as defined by the standard, and report data back to state and federal systems in a standardized format, using one or more standardized interface methodologies.
- the system allows standard categories of resource availability information to be stored, accessed, and updated by authorized users.
- FIG. 1 is a schematic view of the overall system in accordance with an embodiment of the present invention.
- Server 102 is connected to multiple clients 104 , 106 and 108 via network 110 .
- Server 102 may be any personal computer having one or processing means, storage means and memory means, as commonly known in the art.
- Clients 104 , 106 and 108 can be personal computers, laptop computers, tablet PCs, mobile phones and other devices known in the art capable of accessing a website or running a standalone application.
- Clients 104 , 106 and 108 access server 102 via network 110 .
- Network 110 can be a local intranet, the internet, and the means of access the server 102 may be wired, wireless or via a mobile network.
- Database 112 is a database having means for storing data and organizing data into tables.
- Commercial examples of database 112 include Microsoft® SQL Server and Oracle®
- database 112 may be separate from server 102 .
- Database 112 may be on a second server that is connected to server 102 by means commonly known in the art.
- Database 112 stores resource information 114 for one or more resources.
- database 112 is with a part of CIMS.
- database 112 includes data elements specified in the Hospital Availability Exchange (HAVE) guidelines and the Hospital Available Beds in Emergencies and Disasters (HAvBED) specifications.
- Resource information 114 further comprises resource details 116 and resource access information 120 .
- Resource details 116 include location of resource (region, city, state), type of resource, availability information, timing information, contact information, etc.
- Resource access information 120 is used to determine if users can access resource details 116 . It also determines if users can search for a resource based on resource details 116 .
- resource access information 120 stores a list of regions to which the resource details 116 will be visible.
- resource access information 120 stores a list of users that can view resource details 116 .
- Server 102 further comprises access control module 122 .
- Access control module screens clients 104 , 106 and 108 access server 102 and provides access to resource details on the basis of the resource access information 120 .
- access control module 122 first determines if client has access to resource information by matching client information with resource access information 120 .
- clients 104 , 106 or 108 request to view a list of all available resources.
- Access control module 122 retrieves resource details 116 for all resources that have specified access to client 104 in their resource access information 120 .
- Server 102 also comprises resource interface 124 that interfaces and exchanges resource information with external sources, such as resource stores 128 and 130 .
- Resource stores 128 and 130 are computer systems that store resource availability information for one or more medical facilities.
- Resource interface 124 connects to resource stores 128 , 130 through a web interface application that allows resource interface to poll required information from resource clients.
- Medical facilities that do not have resource stores 128 , 130 can also manually feed their resource information by connected to resource interface 124 via a standard web browser or a customized application running on a computing device at that medical facility.
- resource interface 124 can be configured to pull in resource information from multiple sources at predefined time intervals, e.g., hourly, daily, weekly, etc.
- it can be configured to pull in information based on user requests or client requests.
- it can be configured to pull in information on the basis of change in resource information 114 or resource details 116 . For example, if the resource level for a given resource changes, the change is automatically reflected in resource details 116 for that particular resource.
- the interface provides access to resource data for authorized systems. These outside systems may include CIMS, state and federal HAVE systems, Health Alert Networks, and other systems.
- Server 102 further comprises data aggregation module 126 .
- Data aggregation module 126 aggregates the resource availability information stored in database 112 .
- Module 126 provides clients 104 , 106 , 108 with aggregated resource availability information by one or more attributes in resource details 116 , such as region, when requested by the clients.
- access control module 122 is not part of server 102 , but is part of another server that can communicate with server 102 by means known in the art.
- resource interface 124 is not part of server 102 , but is part of another server that can communicate with server 102 by means known in the art.
- FIG. 2 is a schematic view of a system for providing clients with resource information, in accordance with an embodiment of the present invention.
- Resource access information 120 further comprises regions list 202 , medical facilities list 204 , users list 206 and emergencies list 208 . These lists specify regions, medical facilities, users and emergencies that can access resource details 116 .
- a client 210 associated with region A tries to retrieve resource information for region B.
- the access control module 122 first determines the region of client 210 .
- access control module 122 retrieves a list of resources that have region A in their regions list 202 and belong to region B. This resource availability of these resources is then passed to client 210 .
- client 212 associated with medical facility XYZ tries to retrieve availability information of one resource.
- the access control module 122 determines if that resource has medical facility XYZ in its medical facilities list 204 . In case the medical facility is present in medical facilities list 204 , resource details 116 for that resource are sent to client 212 . In another embodiment, client 214 associated with region C requests resource information for resources in region C. The access control module 122 retrieves a list of resources in region C. In this case, access control module does not check to see if resources have given access to region C, since a client of region C requests to view resources of region C. In another embodiment, access control module 122 may first determine if the resources have region C in their regions list 202 before sending the resource information to client 214 .
- FIG. 3 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with the same region, in accordance with an embodiment of the present invention.
- a client that is associated with a given region sends a request to view resource information for the same region, in step 302 .
- the system retrieves all resources that belong to that region and also have specified the same region in their regions list 202 , in step 304 .
- the resource information from all the retrieved resources is then sent to the client requesting the resource information, in step 306 .
- the client requests resource information only for a certain type of resource. In this case, the resource information is filtered and only the requested resource information is forwarded to the client.
- the client only requests resource information from a single resource. In this case, the resource information for that resource is retrieved after verifying that the client has access to that resource information.
- FIG. 4 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with another region, in accordance with an embodiment of the present invention.
- a client that is associated with a given region sends a request to view resource information for another region, in step 402 .
- the system retrieves all resources that belong to the second region and also have specified the first region in their regions list 202 , in step 404 .
- the resource information from all the retrieved resources is then sent to the client requesting the resource information, in step 406 .
- the client requests resource information only for a certain type of resource. In this case, the resource information is filtered and only the requested resource information is forwarded to the client.
- the client only requests resource information from a single resource. In this case, the resource information for that resource is retrieved after verifying that the client has access to that resource information.
- FIG. 5 is a flowchart depicting the steps involved in giving access to resource information to a user for a specific event, in accordance with an embodiment of the present invention.
- a supervisor needs to create an emergency or event in the system. This is depicted as step 502 .
- the supervisor associates one or more resources with the emergency or event, at step 504 .
- the access rights of users are updated to provide access to the resources associated with the created emergency or event based on the users' previous access rights.
- the supervisor instead of creating an emergency, can specify a time frame for which the list of resources retrieved in step 506 will be available to a region, user or medical facility.
- FIG. 6 is a schematic of the system for polling resource information from external resource stores and providing aggregated resource information to external users and databases, in accordance with an embodiment of the present invention.
- Resource interface 124 connects with resource stores 128 and 130 to collect resource availability information. This information is stored in database 112 as resource information.
- Resource interface 124 preferably uses standard web service architecture to connect to resource stores 128 and 130 . This process is similar to the web interface described above with the exception that the resource interface that is retrieving the resource availability information is authenticated using the web service.
- the same authorization module is used as with the web interface described above.
- the data is also aggregated in the same manner as described and is returned via an XML schema.
- resource stores 128 use standard XML schema to communicate data to resource interface 124 .
- An example of this XML schema is the HAvBED EDXL Communication Schema.
- Resource interface 124 receives the data as an XML document, parses the document and stores the parsed data in database 112 .
- a non-web service interface could be utilized in place of the above described web interface.
- Resource availability information is collected from multiple medical facilities and stored in database 112 .
- the resource information comprises various fields, such as resource type (bed, room, emergency response vehicle), resource sub category (staffed bed, unstaffed bed, containment facility, etc), medical facility name, contact person and details, regional information (medical facility city, county and state, FEMA region, CDC region or other region types), and resource availability details such as number of resources available, time period of availability (immediate, in the next 24 hours, in the next 72 hours) and other related information.
- This information is stored along with a time and date at which it was recorded in database 112 .
- Resource type can also be selected from the following list of hospital resource types: i. Intensive Care Unit (ICU), ii.
- resource stores 128 and 130 store data that is compatible with Hospital Availability Exchange (HAVE) standards.
- Resource interface 124 collects resource information from resource stores 128 and 130 on a periodic basis.
- the time interval at which the information is collected is variable and can be modified as and when needed. It is typically 2 times per day, i.e., about every 12 hours.
- region information is stored along with the resource availability information.
- This region information is hierarchical in nature, which means that the facility can be identified by city, county, state, country or any other regional information such as FEMA region, CDC region. This allows for easy aggregation of availability data to a higher regional sum.
- a region could also be defined as a hospital system, such as those prevalent in metropolitan areas.
- Some medical facilities may use a web interface 602 provided by resource interface 124 to input resource availability information for their facility. Administrative or other personnel from these facilities connect to the web interface, provide login credentials assigned to them, and input information for their respective facility. This information is then stored in database 112 .
- emergency response coordinators In case of large scale emergencies, multiple casualty incidents and disasters, it is desirable for emergency response coordinators to obtain resource availability information from regions that are close to the location of the emergency or disaster. These personnel or others who desire to obtain aggregated resource information connect to server 102 through clients 104 , 106 or 108 . Clients need to provide a login and password to be able to connect to server 102 . Once connected, they can request aggregated resource data from data aggregation module 126 . Data aggregation module 126 first verifies if the user requesting aggregated data has sufficient rights to access the data. This is carried out in a manner similar to that for providing resource data to clients, as shown in FIG. 2 .
- access control module uses a mechanism similar to resource access information 120 to determine if a user can view the requested aggregated data.
- information similar to resource access information 120 is maintained for each user that can login to the server 102 . This is compared to the request for aggregated information to determine if the user can view the requested aggregated information.
- the user may request aggregated information by a region such as a state, city, county, or other region type (eg. FEMA region II which comprises the states of New Jersey and New York).
- Data aggregation module queries database 112 for the requested information and sums resource availability counts for the latest available information by resource type to provide aggregated counts for each resource type available in those regions, based on the latest available data.
- data aggregation module would only query database 112 for that specific resource type and aggregate data on this basis. It will be apparent to one skilled in the art that there are many different ways of aggregating data and querying data. This invention is not limited to the aggregation methods described above and is applicable to those other aggregations, which have been left out for the sake of brevity and readability.
- a state or federal resource availability system 604 can connect to server 102 to request aggregated resource availability information.
- the system 604 requests resource availability information via XML, using a predefined XML schema such as HAvBED EDXL Communication Schema.
- Data aggregation module 126 queries database 112 and parses the data into the same schema and sends the data as XML to system 604 .
- system 604 polls server 102 for aggregated data at fixed time intervals, such as every 12 hours.
- FIG. 7 is a schematic view of the system for communicating with external state and federal resource databases, in accordance with an embodiment of the present invention.
- FIG. 7 shows server 702 , which preferably functions as a central repository, that is connected to two servers 704 and 706 .
- Server 706 is in turn connected to server 708 .
- Servers 702 , 704 , 706 and 708 have the same functionality as server 102 , as described in FIG. 6 .
- the information for the regions may be stored in the same physical server or in the same database.
- Servers 704 , 706 and 708 each are also connected to multiple resource stores that are not shown in the figure.
- Servers 704 , 706 and 708 each also have a web interface that is also not shown in FIG. 7 .
- server 702 is a federal resource information server that provides resource availability information at a federal level (aggregated by state, FEMA region or other federal region).
- Server 702 uses the resource interface of the server to collect state level resource availability data from servers 704 and 706 (and other state resource servers not shown in the figure).
- server 702 acts as a federal resource availability system 604 for servers 704 and 706 .
- Servers 704 and 706 aggregate data at state level from resource stores and other local medical facilities and hospitals.
- Server 706 also connects to server 708 , which runs at a county or city level.
- server 708 aggregates information at a city or county level by collecting resource availability information from all medical facilities in the city/county.
- Resource stores can be other similar systems that store resource information.
- resource stores are CIMS or HAN system.
- federal or state systems 604 are compatible with HAVE standards.
- Resource interface connects to the servers 704 and 706 via a network, such as the internet. The systems return data on the basis of the query sent and this data is stored in database 112 .
- the system is configured to derive performance metrics from the aggregated resource availability information.
- the performance metrics are user customizable, and are automatically generated by the data aggregation module based on the user specified schedule. Examples of metrics are metrics that show a percentage of hospitals that can report resource availability data within an hour, percentage of state emergency operation centers that can report bed availability within four hours of an emergency event.
- users of the system are provided with modify and update rights for the stored resource information. These rights are assigned to the users on the basis of the medical facility or region with which they are associated, similar to which access rights to the users are assigned.
- the resource management system is operable for use by first-alert responders to a medical crisis scene for coordinating patient-related data with resource-related data for optimizing system utilization and for making decisions regarding directing and transporting patients to suitable medical facilities having capabilities and capacity for treating each patient, wherein the system provides for use “on-site” of a disaster, accident, or location of a patient or at a medical facility.
- the system enables the monitoring of resource availability information at a central location (such as by city, county, state or federal authorities).
- the system also provides for gathering resource availability information for mass casualty movement that may be required during large scale disasters and emergencies. It is also useful when trying to allocate patients to facilities that have appropriate capabilities to handle the patients (burn units, de-contamination, etc).
- the system of the present invention us useful in determining the capacity of facilities in regions in and around the disaster or emergency.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- General Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Public Health (AREA)
- Marketing (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Biomedical Technology (AREA)
- Quality & Reliability (AREA)
- Emergency Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Operations Research (AREA)
- Signal Processing (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
Description
- This application is a Continuation of U.S. application Ser. No. 11/895,705 filed on Aug. 27, 2007, which is a Continuation-In-Part of U.S. application Ser. No. 11/506,850, filed Aug. 18, 2006. U.S. application Ser. No. 11/895,705 is also a Continuation-In-Part of U.S. application Ser. No. 11/226,875, filed Sep. 14, 2005, incorporated herein by reference in its entirety.
- 1. Field of the Invention
- The present invention relates generally to a resource management system for use by personnel managing an incident. Additionally, the present invention relates to a computer system and method for emergency personnel to efficiently collect, store, aggregate and manage availability information regarding resources and equipment according to the needs of the patients, evacuees, people or those injured.
- 2. Description of the Prior Art
- A multiple-victim disaster or an emergency can overwhelm ill-prepared local or state officials. This is especially true if resources available to handle the disaster or the emergency are constrained. In the case of a medical disaster, disaster victims may be routed to medical facilities where the medical resources (number of available beds, facilities to treat a certain type of victims) are limited or already in use for treating similar victims from the same disaster location or another disaster location. In such a case, there may be other medical facilities that are equipped to accommodate the victims, but may be unutilized for a number of reasons, primarily lack of knowledge about the availability of resources at a facility.
- Hence, there is a need for a system that tracks in real-time the availability of resources across multiple facilities in order to better direct victims of an emergency or disaster to these resources. Additionally, the system should be able to categorize these resources and the patients/victims needs so that it can better direct the patients/victims according to the type of resource required to treat the patient/victim. The system should also be able to track the availability of resources from multiple facilities across regions, cities and in certain cases across states. This system should be accessible at the emergency location or at multiple locations in case of a natural disaster to enable central tracking of the resources. The system should also support communication of resource status and availability across one or many users in the region, city, county, state or other response territory. Furthermore, this system should utilize common standards such that different facilities can use existing systems to connect to such a system and report their resource availability. This system should be able to collect availability information from a number of facilities and aggregate the data so that people responsible for managing the emergencies are provided with aggregated counts by cities, regions or other aggregation criterion.
- One such system is described in U.S. Publication No. 20040138925, titled “Resources utilization management system and method of use”. This patent application describes a resource utilization system that graphically depicts utilization levels of resources in a hospital. Examples of the different types of resources include beds, rooms as well as human resources such as medical staff, physicians, etc. The application further describes the method of managing these resources by first assigning these resources to subjects such as patients. During the assignment, the system displays the utilization of the resources giving an indication to the user about the availability of the resources.
- U.S. Publication No. 20030074222, titled “System and method for Managing Patient Bed Assignments and Bed Occupancy in a Health Care Facility” describes a computer implemented system for managing the assignment of beds in a medical facility. The claimed system functions in conjunction with an admission/discharge/transfer system and keeps track of the beds in a medical facility and the assignment of beds to incoming patients. It also displays a real-time status of the beds available in the facility and the beds that are currently assigned to patients in the facility.
- U.S. Publication No. 20040243446, titled “Method and a System for Optimizing Hospital Beds and Ambulance Allocations via a Computer Network” describes a computer based system that enables users to view the real-time status of beds available in a medical facility such as a hospital. Further, the system enables the hospital to communicate this status to an ambulance that is directing one or more patients to the hospital. If the hospital does not have the available capacity to accommodate the patients being transported in the ambulance, then the ambulance is redirected to a second facility or hospital.
- From the above discussion, it is clear that there is a need for a system that will enable tracking availability of resources from multiple facilities. The system should also be able to list resources by type so that availability of a certain type of resource, such as, bed capacity by triage category is readily available. Additionally, the system should be able to gather resource availability information from different regional systems and medical facilities. It should be able to present this information at the time of emergency so that the information can be used to make better decisions.
- A first aspect of the present invention is to provide a system for providing resource information to a user, the resource information comprising availability of resources in at least one facility in at least one region, the system including at least one database, the at least one database storing the resource information for at least one facility, an access control module for controlling access to the resource information stored in the database, at least one client for viewing the resource information, a resource interface module for collecting resource information from the at least one facility in the at least one region, and a data aggregation module for aggregating the collected resource information based on one or more attributes associated with the resource information, wherein the data aggregation module is operable to access the information on the at least one database.
- A second aspect of the present invention is to provide a method for providing resource information to at least one user, the resource information comprising availability of resources associated with one or more facilities in one or more regions, the method including the steps of collecting resource availability information from at least two facilities, the resource availability information further comprising a region associated with the facility, storing the resource information in a database along with a timestamp identifying a date and time at which the information was collected, aggregating resource availability information by summing resource availability based on the region associated with each of the facilities, and providing the aggregated resource information to the at least one user.
- It is yet another aspect of the present invention to provide a system for providing resource information to a user, the resource information comprising availability of resources in at least one facility in at least one region, the system including at least one database, the at least one database storing the resource information for at least one facility, an access control module for controlling access to the resource information stored in the database, at least one client for viewing the resource information, a first resource interface module for collecting resource information from the at least one facility in the at least one region, wherein the resource interface is a web service that connects to at least one HAVE compatible resource information data store over a network to collect resource information about the at least one facility, a second resource interface module for collecting resource information from the at least one facility in the at least one region, wherein the resource interface is a web portal that allows at least one second user to manually input resource information for the at least one facility in the at least one region, a data aggregation module for aggregating the collected resource information based on one or more attributes associated with the resource information, wherein the data aggregation module is operable to access the information on the at least one database, and a data exchange module for providing the aggregated resource information to a central repository, thereby providing gathering, aggregating, storing, and exchanging information to support regional or federal guidelines including HAVE guidelines and HAvBED specifications.
- These and other aspects of the present invention will become apparent to those skilled in the art after a reading of the following description of the preferred embodiment when considered with the drawings, as they support the claimed invention.
-
FIG. 1 is a schematic view of the overall system in accordance with an embodiment of the present invention. -
FIG. 2 is a schematic view of a system for providing clients with resource information, in accordance with an embodiment of the present invention. -
FIG. 3 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with the same region, in accordance with an embodiment of the present invention. -
FIG. 4 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with another region, in accordance with an embodiment of the present invention. -
FIG. 5 is a flowchart depicting the steps involved in giving access to resource information to a user for a specific event, in accordance with an embodiment of the present invention. -
FIG. 6 is a schematic of the system for polling resource information from external resource stores and providing aggregated resource information to external users and databases, in accordance with an embodiment of the present invention. -
FIG. 7 is a schematic view of the system for communicating with external state and federal resource databases, in accordance with an embodiment of the present invention. -
FIG. 8 is a schematic view of an exemplary XML schema for exchange of resource availability information, in accordance with an embodiment of the present invention. - The present invention provides a method and system for aggregating resource availability information collected from multiple facilities in one or more regions. The present system tracks medical and non-medical resource availability information by type and provides it to users requesting the information. The system collects availability information from individual hospitals and other medical facilities. This is enabled through a web interface that connects to the facilities and queries the availability data through industry standard techniques. There is an addition web interface that allows administration personnel to connect to the system and manually input the resource availability information. Furthermore, the system can also connect to central systems, such as those maintained by states, counties, etcetera to collect availability information.
- Preferably the system is setup to collect the resource availability information at pre-determined time intervals; alternatively the time intervals are determined ad hoc or as needed. These intervals are user defined and can be changed/modified as per the user requirements. The system collects resource availability information, such as availability information about hospital beds, and stores this information in a database. This information is stored along with the time at which it was collected. This allows uses who query the system, to obtain the latest information along with the time at which it was obtained. This is important in emergencies, where personnel directing patients should have access to the latest information.
- Resource information collected from individual medical facilities is stored in a database. A region that the medical facility is associated with is also stored along with the resource information. This region can be a city, county, state, or any other geographic region that can be used to aggregate data.
- The system also allows for protecting the resource information, and the resource information is provided only to authorized users. Further, the users are only authorized to view resource information for certain specified resources. This enables the system of the present invention to restrict certain users from viewing resource information from resources that they are not authorized to view. Administrators of the system can define resources by region. Additionally, they can define the regions for which the users are authorized to view resource information. In certain special cases, the administrators can grant access to certain users to view resource information for regions for which the users are not initially authorized. This can be done on a per user basis, for a specified time frame or for a specified medical emergency or event.
- The present invention provides for tracking of medical resources including but not limited to hospital beds, hospital rooms, Emergency Medical Services such as ambulance availability, medical personnel availability, availability of medical equipment such as defibrillators, decontamination facilities, negative pressure isolation rooms, ventilators, etc. These resources are tracked across one or multiple regions. A region can be defined as a part of a town or city, a town, city, county, state and even a country. The present invention also provides for tracking of non-medical resources including but not limited to shelters, vehicles, equipment, beds and other resources such as capacity in shelters, etc.
- The present invention also provides a method and a system for interacting and exchanging resource information from other systems, such as Crisis Information Management System (CIMS), Computer Aided Dispatch system (CAD), Hospital Alert Network (HAN), etc.
- The present invention also provides a method and a system for gathering, aggregating, storing, and exchanging information to support regional or federal guidelines including Hospital Availability Exchange (HAVE) guidelines (see “HAVE.” COMCARE; available at http://www.comcare.org/HAVE.html, herein incorporated by reference in its entirety) and Hospital Available Beds in Emergencies and Disasters (HAvBED) specifications (see “National Hospital Available Beds for Emergencies and Disasters (HAvBED) System: Final Report.” AHRQ Publication No. 05-0103, December 2005. Agency for Healthcare Research and Quality, Rockville, Md.; available at http://www.ahrq.gov/research/havbed/, herein incorporated by reference in its entirety). The system allows users to update the status of the resources of one or more facilities that the users are associated with, and is capable of reporting resource availability in standard categories as defined by the standard, and report data back to state and federal systems in a standardized format, using one or more standardized interface methodologies. The system allows standard categories of resource availability information to be stored, accessed, and updated by authorized users.
- Referring now to the drawings in general, the illustrations are for the purpose of describing a preferred embodiment of the invention and are not intended to limit the invention thereto.
FIG. 1 is a schematic view of the overall system in accordance with an embodiment of the present invention.Server 102 is connected tomultiple clients network 110.Server 102 may be any personal computer having one or processing means, storage means and memory means, as commonly known in the art.Clients Clients access server 102 vianetwork 110.Network 110 can be a local intranet, the internet, and the means of access theserver 102 may be wired, wireless or via a mobile network. -
Server 102 hasdatabase 112 residing on it.Database 112 is a database having means for storing data and organizing data into tables. Commercial examples ofdatabase 112 include Microsoft® SQL Server and Oracle® In another embodiment of the present invention,database 112 may be separate fromserver 102.Database 112 may be on a second server that is connected toserver 102 by means commonly known in the art. -
Database 112stores resource information 114 for one or more resources. In one embodiment of the present invention,database 112 is with a part of CIMS. In another embodiment,database 112 includes data elements specified in the Hospital Availability Exchange (HAVE) guidelines and the Hospital Available Beds in Emergencies and Disasters (HAvBED) specifications.Resource information 114 further comprises resource details 116 andresource access information 120. Resource details 116 include location of resource (region, city, state), type of resource, availability information, timing information, contact information, etc.Resource access information 120 is used to determine if users can access resource details 116. It also determines if users can search for a resource based on resource details 116. In one embodiment of the present invention,resource access information 120 stores a list of regions to which the resource details 116 will be visible. In another embodiment of the present invention,resource access information 120 stores a list of users that can view resource details 116. -
Server 102 further comprisesaccess control module 122. Access controlmodule screens clients access server 102 and provides access to resource details on the basis of theresource access information 120. When a client requests to view resource information,access control module 122 first determines if client has access to resource information by matching client information withresource access information 120. In another embodiment of the present invention,clients Access control module 122 retrievesresource details 116 for all resources that have specified access toclient 104 in theirresource access information 120. -
Server 102 also comprisesresource interface 124 that interfaces and exchanges resource information with external sources, such asresource stores Resource stores Resource interface 124 connects to resourcestores resource stores resource interface 124 via a standard web browser or a customized application running on a computing device at that medical facility. In a preferred embodiment,resource interface 124 can be configured to pull in resource information from multiple sources at predefined time intervals, e.g., hourly, daily, weekly, etc. In another embodiment, it can be configured to pull in information based on user requests or client requests. In a third embodiment, it can be configured to pull in information on the basis of change inresource information 114 or resource details 116. For example, if the resource level for a given resource changes, the change is automatically reflected inresource details 116 for that particular resource. In a fourth embodiment, the interface provides access to resource data for authorized systems. These outside systems may include CIMS, state and federal HAVE systems, Health Alert Networks, and other systems. -
Server 102 further comprisesdata aggregation module 126.Data aggregation module 126 aggregates the resource availability information stored indatabase 112.Module 126 providesclients resource details 116, such as region, when requested by the clients. - In another embodiment of the present invention,
access control module 122 is not part ofserver 102, but is part of another server that can communicate withserver 102 by means known in the art. In yet another embodiment of the present invention,resource interface 124 is not part ofserver 102, but is part of another server that can communicate withserver 102 by means known in the art. -
FIG. 2 is a schematic view of a system for providing clients with resource information, in accordance with an embodiment of the present invention.Resource access information 120 further comprisesregions list 202,medical facilities list 204, users list 206 andemergencies list 208. These lists specify regions, medical facilities, users and emergencies that can access resource details 116. Aclient 210 associated with region A tries to retrieve resource information for region B. Theaccess control module 122 first determines the region ofclient 210. Next,access control module 122 retrieves a list of resources that have region A in theirregions list 202 and belong to region B. This resource availability of these resources is then passed toclient 210. In another embodiment of the present invention,client 212 associated with medical facility XYZ tries to retrieve availability information of one resource. Theaccess control module 122 determines if that resource has medical facility XYZ in itsmedical facilities list 204. In case the medical facility is present inmedical facilities list 204, resource details 116 for that resource are sent toclient 212. In another embodiment,client 214 associated with region C requests resource information for resources in region C. Theaccess control module 122 retrieves a list of resources in region C. In this case, access control module does not check to see if resources have given access to region C, since a client of region C requests to view resources of region C. In another embodiment,access control module 122 may first determine if the resources have region C in their regions list 202 before sending the resource information toclient 214. -
FIG. 3 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with the same region, in accordance with an embodiment of the present invention. A client that is associated with a given region sends a request to view resource information for the same region, instep 302. The system retrieves all resources that belong to that region and also have specified the same region in theirregions list 202, instep 304. The resource information from all the retrieved resources is then sent to the client requesting the resource information, instep 306. In an embodiment of the present invention, the client requests resource information only for a certain type of resource. In this case, the resource information is filtered and only the requested resource information is forwarded to the client. In another embodiment of the present invention, the client only requests resource information from a single resource. In this case, the resource information for that resource is retrieved after verifying that the client has access to that resource information. -
FIG. 4 is a flowchart depicting the steps of retrieving resource information of a region by a client associated with another region, in accordance with an embodiment of the present invention. A client that is associated with a given region sends a request to view resource information for another region, instep 402. The system retrieves all resources that belong to the second region and also have specified the first region in theirregions list 202, instep 404. The resource information from all the retrieved resources is then sent to the client requesting the resource information, instep 406. In an embodiment of the present invention, the client requests resource information only for a certain type of resource. In this case, the resource information is filtered and only the requested resource information is forwarded to the client. In another embodiment of the present invention, the client only requests resource information from a single resource. In this case, the resource information for that resource is retrieved after verifying that the client has access to that resource information. -
FIG. 5 is a flowchart depicting the steps involved in giving access to resource information to a user for a specific event, in accordance with an embodiment of the present invention. First a supervisor needs to create an emergency or event in the system. This is depicted asstep 502. Subsequently, the supervisor associates one or more resources with the emergency or event, atstep 504. Atstep 506, the access rights of users are updated to provide access to the resources associated with the created emergency or event based on the users' previous access rights. In another embodiment of the present invention, instead of creating an emergency, the supervisor can specify a time frame for which the list of resources retrieved instep 506 will be available to a region, user or medical facility. -
FIG. 6 is a schematic of the system for polling resource information from external resource stores and providing aggregated resource information to external users and databases, in accordance with an embodiment of the present invention.Resource interface 124 connects withresource stores database 112 as resource information.Resource interface 124 preferably uses standard web service architecture to connect toresource stores - In a preferred embodiment,
resource stores 128 use standard XML schema to communicate data toresource interface 124. An example of this XML schema is the HAvBED EDXL Communication Schema.Resource interface 124 receives the data as an XML document, parses the document and stores the parsed data indatabase 112. Alternatively a non-web service interface could be utilized in place of the above described web interface. - Resource availability information is collected from multiple medical facilities and stored in
database 112. The resource information comprises various fields, such as resource type (bed, room, emergency response vehicle), resource sub category (staffed bed, unstaffed bed, containment facility, etc), medical facility name, contact person and details, regional information (medical facility city, county and state, FEMA region, CDC region or other region types), and resource availability details such as number of resources available, time period of availability (immediate, in the next 24 hours, in the next 72 hours) and other related information. This information is stored along with a time and date at which it was recorded indatabase 112. Resource type can also be selected from the following list of hospital resource types: i. Intensive Care Unit (ICU), ii. Medical and Surgical (Med/Surge), iii. Burn Care, iv. Peds ICU, v. Pediatrics (Peds), vi. Psychiatric (Psych), vii. Negative Pressure Isolation, viii. Emergency Department Divert Status, ix. Decontamination Facility Available and x. Ventilators Available. This list is not meant to be exhaustive but is meant to illustrate the various types of resources on which availability data can be collected. - In a preferred embodiment,
resource stores Resource interface 124 collects resource information fromresource stores - As described above, information about region of a medical facility is stored along with the resource availability information. This region information is hierarchical in nature, which means that the facility can be identified by city, county, state, country or any other regional information such as FEMA region, CDC region. This allows for easy aggregation of availability data to a higher regional sum. A region could also be defined as a hospital system, such as those prevalent in metropolitan areas.
- Some medical facilities, that may not have resource stores capable of communicating with
resource interface 124, may use aweb interface 602 provided byresource interface 124 to input resource availability information for their facility. Administrative or other personnel from these facilities connect to the web interface, provide login credentials assigned to them, and input information for their respective facility. This information is then stored indatabase 112. - In case of large scale emergencies, multiple casualty incidents and disasters, it is desirable for emergency response coordinators to obtain resource availability information from regions that are close to the location of the emergency or disaster. These personnel or others who desire to obtain aggregated resource information connect to
server 102 throughclients server 102. Once connected, they can request aggregated resource data fromdata aggregation module 126.Data aggregation module 126 first verifies if the user requesting aggregated data has sufficient rights to access the data. This is carried out in a manner similar to that for providing resource data to clients, as shown inFIG. 2 . Hence, access control module uses a mechanism similar toresource access information 120 to determine if a user can view the requested aggregated data. In an embodiment, information similar toresource access information 120 is maintained for each user that can login to theserver 102. This is compared to the request for aggregated information to determine if the user can view the requested aggregated information. The user may request aggregated information by a region such as a state, city, county, or other region type (eg. FEMA region II which comprises the states of New Jersey and New York). Data aggregation module then queriesdatabase 112 for the requested information and sums resource availability counts for the latest available information by resource type to provide aggregated counts for each resource type available in those regions, based on the latest available data. In another case, client requesting such information may be only interested in a certain resource type. Hence, data aggregation module would only querydatabase 112 for that specific resource type and aggregate data on this basis. It will be apparent to one skilled in the art that there are many different ways of aggregating data and querying data. This invention is not limited to the aggregation methods described above and is applicable to those other aggregations, which have been left out for the sake of brevity and readability. - In an alternate embodiment of the present invention, a state or federal
resource availability system 604 can connect toserver 102 to request aggregated resource availability information. Thesystem 604 requests resource availability information via XML, using a predefined XML schema such as HAvBED EDXL Communication Schema.Data aggregation module 126queries database 112 and parses the data into the same schema and sends the data as XML tosystem 604. In a preferred embodiment of the present invention,system 604polls server 102 for aggregated data at fixed time intervals, such as every 12 hours. -
FIG. 7 is a schematic view of the system for communicating with external state and federal resource databases, in accordance with an embodiment of the present invention.FIG. 7 showsserver 702, which preferably functions as a central repository, that is connected to twoservers Server 706 is in turn connected toserver 708.Servers server 102, as described inFIG. 6 . Alternatively, the information for the regions (e.g. external state and federal resources) may be stored in the same physical server or in the same database.Servers Servers FIG. 7 . In an exemplary embodiment,server 702 is a federal resource information server that provides resource availability information at a federal level (aggregated by state, FEMA region or other federal region).Server 702 uses the resource interface of the server to collect state level resource availability data fromservers 704 and 706 (and other state resource servers not shown in the figure). Henceserver 702 acts as a federalresource availability system 604 forservers Servers Server 706 also connects toserver 708, which runs at a county or city level. Hence,server 708 aggregates information at a city or county level by collecting resource availability information from all medical facilities in the city/county. Resource stores can be other similar systems that store resource information. In an embodiment, resource stores are CIMS or HAN system. In an embodiment, federal orstate systems 604 are compatible with HAVE standards. Resource interface connects to theservers database 112. - In an embodiment of the present invention, the system is configured to derive performance metrics from the aggregated resource availability information. The performance metrics are user customizable, and are automatically generated by the data aggregation module based on the user specified schedule. Examples of metrics are metrics that show a percentage of hospitals that can report resource availability data within an hour, percentage of state emergency operation centers that can report bed availability within four hours of an emergency event.
- In an embodiment of the present invention, users of the system are provided with modify and update rights for the stored resource information. These rights are assigned to the users on the basis of the medical facility or region with which they are associated, similar to which access rights to the users are assigned.
- Certain modifications and improvements will occur to those skilled in the art upon a reading of the foregoing description. Also, the resource management system is operable for use by first-alert responders to a medical crisis scene for coordinating patient-related data with resource-related data for optimizing system utilization and for making decisions regarding directing and transporting patients to suitable medical facilities having capabilities and capacity for treating each patient, wherein the system provides for use “on-site” of a disaster, accident, or location of a patient or at a medical facility.
- The system enables the monitoring of resource availability information at a central location (such as by city, county, state or federal authorities). The system also provides for gathering resource availability information for mass casualty movement that may be required during large scale disasters and emergencies. It is also useful when trying to allocate patients to facilities that have appropriate capabilities to handle the patients (burn units, de-contamination, etc). In case of large scale disasters or emergencies, the system of the present invention us useful in determining the capacity of facilities in regions in and around the disaster or emergency.
- All modifications and improvements have been deleted herein for the sake of conciseness and readability but are properly within the scope of the following claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/243,860 US20090018869A1 (en) | 2005-09-14 | 2008-10-01 | Method and system for data aggregation for real-time emergency resource management |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US22687505A | 2005-09-14 | 2005-09-14 | |
US11/506,850 US20080046285A1 (en) | 2006-08-18 | 2006-08-18 | Method and system for real-time emergency resource management |
US11/895,705 US8428961B2 (en) | 2005-09-14 | 2007-08-27 | Method and system for data aggregation for real-time emergency resource management |
US12/243,860 US20090018869A1 (en) | 2005-09-14 | 2008-10-01 | Method and system for data aggregation for real-time emergency resource management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/895,705 Continuation US8428961B2 (en) | 2005-09-14 | 2007-08-27 | Method and system for data aggregation for real-time emergency resource management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090018869A1 true US20090018869A1 (en) | 2009-01-15 |
Family
ID=46328204
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/895,705 Active 2028-12-11 US8428961B2 (en) | 2005-09-14 | 2007-08-27 | Method and system for data aggregation for real-time emergency resource management |
US12/243,860 Abandoned US20090018869A1 (en) | 2005-09-14 | 2008-10-01 | Method and system for data aggregation for real-time emergency resource management |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/895,705 Active 2028-12-11 US8428961B2 (en) | 2005-09-14 | 2007-08-27 | Method and system for data aggregation for real-time emergency resource management |
Country Status (1)
Country | Link |
---|---|
US (2) | US8428961B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120316892A1 (en) * | 2011-06-08 | 2012-12-13 | Huster Keith A | System and method of bed data aggregation, normalization and communication to third parties |
US8548911B2 (en) * | 2012-02-09 | 2013-10-01 | Bank Of America Corporation | Devices and methods for disaster-relief support |
CN103810560A (en) * | 2013-11-01 | 2014-05-21 | 北京交通大学 | Emergency resource scheduling method for emergencies of rail transit |
US20170200690A1 (en) * | 2015-07-23 | 2017-07-13 | Nippon Micrometal Corporation | Bonding wire for semiconductor device |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8050939B2 (en) * | 2005-02-11 | 2011-11-01 | Avaya Inc. | Methods and systems for use in the provision of services in an institutional setting such as a healthcare facility |
NZ574850A (en) * | 2006-08-10 | 2011-02-25 | Univ Loma Linda Med | Advanced emergency geographical information system |
GB2473572A (en) * | 2008-07-04 | 2011-03-16 | Fujitsu Ltd | Information processor, information processing program, information processing method |
US8788247B2 (en) * | 2008-08-20 | 2014-07-22 | International Business Machines Corporation | System and method for analyzing effectiveness of distributing emergency supplies in the event of disasters |
US9450834B2 (en) * | 2010-07-19 | 2016-09-20 | Soasta, Inc. | Animated globe showing real-time web user performance measurements |
US9024757B1 (en) | 2012-05-09 | 2015-05-05 | Priority 5 Holdings, Inc. | Event prediction using temporal and geospatial precursor networks |
US9245440B2 (en) * | 2012-07-26 | 2016-01-26 | Airbus Ds Communications, Inc. | Location based event notification systems and methods |
US20140136223A1 (en) | 2012-11-15 | 2014-05-15 | Rachel Phillips | Systems and methods for automated repatriation of a patient from an out-of-network admitting hospital to an in-network destination hospital |
US8844050B1 (en) * | 2013-03-15 | 2014-09-23 | Athoc, Inc. | Personnel crisis communications management and personnel status tracking system |
US20150234989A1 (en) * | 2014-02-14 | 2015-08-20 | Kamal Kejriwal | Patient Transition by Web Based program to have real time availability of Skilled nursing home beds |
US20150269700A1 (en) | 2014-03-24 | 2015-09-24 | Athoc, Inc. | Exchange of crisis-related information amongst multiple individuals and multiple organizations |
US20150281927A1 (en) * | 2014-03-27 | 2015-10-01 | Cadmium Solutions, Llc | Emergency services dispatch system with user-defined resource restrictions |
US20150278732A1 (en) * | 2014-03-27 | 2015-10-01 | Cadmium Solutions, Llc | Emergency services dispatch system with dynamic rostering of resources |
DE102014006825A1 (en) * | 2014-05-07 | 2015-11-12 | Weinmann Emergency Medical Technology Gmbh + Co. Kg | Preclinical care system |
US10332050B2 (en) * | 2014-07-10 | 2019-06-25 | Bank Of America Corporation | Identifying personnel-staffing adjustments based on indoor positioning system detection of physical customer presence |
US10108952B2 (en) | 2014-07-10 | 2018-10-23 | Bank Of America Corporation | Customer identification |
US10074130B2 (en) | 2014-07-10 | 2018-09-11 | Bank Of America Corporation | Generating customer alerts based on indoor positioning system detection of physical customer presence |
EP3121777A1 (en) * | 2015-07-20 | 2017-01-25 | Tata Consultancy Services Limited | Systems and methods for dynamic allocation of mobile agents |
US20170154374A1 (en) * | 2015-11-30 | 2017-06-01 | Marcos Alfonso Iglesias | Output adjustment and monitoring in accordance with resource unit performance |
US11250529B2 (en) | 2016-09-13 | 2022-02-15 | Intergraph Corporation | Computer-aided dispatch including automatic diversions |
US10349148B2 (en) | 2016-12-20 | 2019-07-09 | Intergraph Corporation | Computer-aided dispatch systems and methods utilizing biometrics to assess responder condition and suitability |
US20180308576A1 (en) * | 2017-04-21 | 2018-10-25 | Dallas/Fort Worth International Airport Board | System and method for patient tracking during mass casualty events |
CN115380336A (en) * | 2020-04-10 | 2022-11-22 | 通用电气精准医疗有限责任公司 | System and method for determining patient disease burden |
US12062434B2 (en) * | 2020-04-10 | 2024-08-13 | GE Precision Healthcare LLC | Systems and methods for resource availability management |
US20210319886A1 (en) * | 2020-04-10 | 2021-10-14 | GE Precision Healthcare LLC | Systems and methods for determining and visualizing medical device resource availability |
US20230162847A1 (en) * | 2021-11-22 | 2023-05-25 | Smirta Innovations Inc. | System and method for facilitating patient scheduling at a healthcare facility |
Citations (68)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5301105A (en) * | 1991-04-08 | 1994-04-05 | Desmond D. Cummings | All care health management system |
US5454024A (en) * | 1989-08-31 | 1995-09-26 | Lebowitz; Mayer M. | Cellular digital packet data (CDPD) network transmission system incorporating cellular link integrity monitoring |
US5911687A (en) * | 1995-11-15 | 1999-06-15 | Hitachi, Ltd. | Wide area medical information system and method using thereof |
US5945919A (en) * | 1996-05-30 | 1999-08-31 | Trimble Navigation Limited | Dispatcher free vehicle allocation system |
US6014629A (en) * | 1998-01-13 | 2000-01-11 | Moore U.S.A. Inc. | Personalized health care provider directory |
US6055506A (en) * | 1997-04-25 | 2000-04-25 | Unitron Medical Communications, Inc. | Outpatient care data system |
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US6117073A (en) * | 1998-03-02 | 2000-09-12 | Jones; Scott J. | Integrated emergency medical transportation database system |
US6212393B1 (en) * | 1999-08-02 | 2001-04-03 | Motorola, Inc. | Method and apparatus for communication within a vehicle dispatch system |
US20010032195A1 (en) * | 2000-03-30 | 2001-10-18 | Graichen Catherine Mary | System and method for identifying productivity improvements in a business organization |
US6305605B1 (en) * | 1999-08-09 | 2001-10-23 | John W. Goetz | Multiple-casualty incident patient tracking |
US20020013714A1 (en) * | 2000-05-19 | 2002-01-31 | Sanalink Ag | System and method for transmitting information between doctors and hospitals |
US20020032593A1 (en) * | 2000-05-25 | 2002-03-14 | Berman Phillip M. | Method and system for determining cat scan availability |
US6377210B1 (en) * | 2000-02-25 | 2002-04-23 | Grey Island Systems, Inc. | Automatic mobile object locator apparatus and method |
US20020153413A1 (en) * | 1999-07-30 | 2002-10-24 | Piatek John T. | System and method for tracking victims of a mass casualty incident |
US20020198445A1 (en) * | 2001-06-26 | 2002-12-26 | Steven Dominguez | System and method for monitoring body functions |
US20030021417A1 (en) * | 2000-10-20 | 2003-01-30 | Ognjen Vasic | Hidden link dynamic key manager for use in computer systems with database structure for storage of encrypted data and method for storage and retrieval of encrypted data |
US20030040939A1 (en) * | 2001-08-24 | 2003-02-27 | Daniel Tritch | Method of storing and retrieving advance medical directives |
US20030074222A1 (en) * | 2001-09-07 | 2003-04-17 | Eric Rosow | System and method for managing patient bed assignments and bed occupancy in a health care facility |
US6560569B1 (en) * | 1998-05-13 | 2003-05-06 | Nabil A. Abu El Ata | Method and apparatus for designing and analyzing information systems using multi-layer mathematical models |
US6563910B2 (en) * | 2001-02-26 | 2003-05-13 | Royal Thoughts, Llc | Emergency response information distribution |
US6567796B1 (en) * | 1999-03-23 | 2003-05-20 | Microstrategy, Incorporated | System and method for management of an automatic OLAP report broadcast system |
US6571285B1 (en) * | 1999-12-23 | 2003-05-27 | Accenture Llp | Providing an integrated service assurance environment for a network |
US6574480B1 (en) * | 1999-12-10 | 2003-06-03 | At&T Corp. | Method and apparatus for providing intelligent emergency paging |
US20030115085A1 (en) * | 2001-12-13 | 2003-06-19 | Allied Telesis Kabushiki Kaisha | Management system and method |
US6594637B1 (en) * | 1998-09-14 | 2003-07-15 | International Business Machines Corporation | Schedule management system and method |
US20030177051A1 (en) * | 2003-03-13 | 2003-09-18 | Robin Driscoll | Method and system for managing worker resources |
US20030212494A1 (en) * | 2001-03-30 | 2003-11-13 | Alexander John Franklin | Emergency management system |
US20040006492A1 (en) * | 2002-01-30 | 2004-01-08 | Nec Infrontia Corporation | Health care service system |
US6701156B2 (en) * | 2000-12-19 | 2004-03-02 | Lucent Technologies Inc | System and method for managing response to a need at a site |
US20040070515A1 (en) * | 2002-07-02 | 2004-04-15 | Raymond Burkley | First responder communications system |
US20040138925A1 (en) * | 2002-12-23 | 2004-07-15 | Zheng Shu Sean | Resources utilization management system and method of use |
US20040153440A1 (en) * | 2003-01-30 | 2004-08-05 | Assaf Halevy | Unified management of queries in a multi-platform distributed environment |
US20040153343A1 (en) * | 2003-01-31 | 2004-08-05 | Phyllis Gotlib | Medical information query system |
US20040162707A1 (en) * | 2003-02-12 | 2004-08-19 | Saint-Amour Paula J. | Early alert and response system |
US6789046B1 (en) * | 2000-12-05 | 2004-09-07 | Microsoft Corporation | Performance logging solution |
US20040193447A1 (en) * | 2003-03-28 | 2004-09-30 | Joseph Sameh S. | Website messaging system for public health information |
US20040243446A1 (en) * | 2000-04-06 | 2004-12-02 | Phil Wyatt | Method and a system for optimizing hospital beds and ambulance allocations via a computer network |
US20050001720A1 (en) * | 2002-07-02 | 2005-01-06 | Charles Mason | Emergency response personnel automated accountability system |
US20050010436A1 (en) * | 2003-07-08 | 2005-01-13 | Richard Merkin | Health care administration method |
US20050038696A1 (en) * | 2002-08-02 | 2005-02-17 | American Medical Response | System and method for managing requests for medical transportation |
US20050055330A1 (en) * | 2001-05-15 | 2005-03-10 | Britton Colin P. | Surveillance, monitoring and real-time events platform |
US20050075904A1 (en) * | 2003-10-06 | 2005-04-07 | Cerner Innovation, Inc. | System and method for automatically generating evidence-based assignment of care providers to patients |
US20050131740A1 (en) * | 2003-12-10 | 2005-06-16 | Geoage, Incorporated | Management tool for health care provider services |
US20050137929A1 (en) * | 2003-06-13 | 2005-06-23 | Ibex Healthdata Systems, Inc. | Health unit assessment tool |
US20050201529A1 (en) * | 2004-03-13 | 2005-09-15 | Intrado Inc. | Method and apparatus for increasing the reliability of an emergency call communication network |
US20050201359A1 (en) * | 2004-03-13 | 2005-09-15 | Intrado Inc. | Dynamically establishing media channels between resources of an emergency services network and conforming emergency systems |
US20050201345A1 (en) * | 2004-03-15 | 2005-09-15 | Williamson Robert D. | Mobile patient care system |
US20050201528A1 (en) * | 2004-03-13 | 2005-09-15 | Intrado Inc. | Bi-directional messaging for an emergency services network |
US6957218B1 (en) * | 2000-04-06 | 2005-10-18 | Medical Central Online | Method and system for creating a website for a healthcare provider |
US6975963B2 (en) * | 2002-09-30 | 2005-12-13 | Mcdata Corporation | Method and system for storing and reporting network performance metrics using histograms |
US20050282141A1 (en) * | 2004-06-17 | 2005-12-22 | Falash Mark D | Scenario workflow based assessment system and method |
US7001334B2 (en) * | 1999-11-05 | 2006-02-21 | Wcr Company | Apparatus for non-intrusively measuring health parameters of a subject and method of use thereof |
US20060235936A1 (en) * | 2005-04-15 | 2006-10-19 | General Electric Company | System and method for PACS workstation conferencing |
US20060235716A1 (en) * | 2005-04-15 | 2006-10-19 | General Electric Company | Real-time interactive completely transparent collaboration within PACS for planning and consultation |
US20060236247A1 (en) * | 2005-04-15 | 2006-10-19 | General Electric Company | Interface to display contextual patient information via communication/collaboration application |
US20060277595A1 (en) * | 2005-06-06 | 2006-12-07 | Novell, Inc. | Techniques for providing role-based security with instance-level granularity |
US20070021981A1 (en) * | 2005-06-29 | 2007-01-25 | James Cox | System for managing emergency personnel and their information |
US7177623B2 (en) * | 2003-07-02 | 2007-02-13 | The United States Of America As Represented By The Secretary Of The Army | Localized cellular awareness and tracking of emergencies |
US20070061393A1 (en) * | 2005-02-01 | 2007-03-15 | Moore James F | Management of health care data |
US7200207B2 (en) * | 2004-03-13 | 2007-04-03 | Intrado Inc. | Communication network for providing emergency services |
US20070078677A1 (en) * | 2003-05-19 | 2007-04-05 | Intellirad Solutions Pty Ltd | Controlling access to medical records |
US20070239484A1 (en) * | 2006-03-20 | 2007-10-11 | Arond Betty J | System and method for managing patient bed assignments, bed occupancy, and staffing in a healthcare facility operation |
US20070280462A1 (en) * | 2006-05-30 | 2007-12-06 | Roger Neil Neece | System and method for security monitoring and response delivery |
US20070285226A1 (en) * | 2006-06-12 | 2007-12-13 | Healthpia Co., Ltd. | System and method for emergency alarm |
US7337146B2 (en) * | 2002-03-04 | 2008-02-26 | Swan Island Networks, Inc. | Emergency information management system |
US7661146B2 (en) * | 2005-07-01 | 2010-02-09 | Privamed, Inc. | Method and system for providing a secure multi-user portable database |
US7899682B2 (en) * | 2002-03-22 | 2011-03-01 | Thinksharp, Inc. | Method and system of rule-based triage |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5558638A (en) * | 1993-04-30 | 1996-09-24 | Healthdyne, Inc. | Patient monitor and support system |
US6594634B1 (en) * | 1998-09-14 | 2003-07-15 | Medtronic Physio-Control Corp. | Method and apparatus for reporting emergency incidents |
JP2002358371A (en) | 2001-06-01 | 2002-12-13 | Canon Inc | Health care system, information management device, method thereof, computer program, and computer readable recording medium |
JP2003067502A (en) | 2001-08-27 | 2003-03-07 | Toyo Commun Equip Co Ltd | Health care management system |
JP4244272B2 (en) | 2001-09-18 | 2009-03-25 | 日本電信電話株式会社 | Health check system and method using internet (IP network) connection service |
JP2003111735A (en) | 2001-10-03 | 2003-04-15 | Ntt Data Corp | Health information management system |
US7890341B2 (en) * | 2002-12-09 | 2011-02-15 | Baxter International Inc. | System and a method for providing integrated access management for peritoneal dialysis and hemodialysis |
JP2005174111A (en) | 2003-12-12 | 2005-06-30 | Tatsuo Aoki | Priority emergency reporting system |
JP2006167400A (en) | 2004-12-16 | 2006-06-29 | Ipsquare Inc | Medical device management system |
JP2007094459A (en) | 2005-09-27 | 2007-04-12 | Honda Motor Co Ltd | System and program for coping with vehicle emergency circumstance |
JP4484894B2 (en) | 2006-12-25 | 2010-06-16 | 修 中田 | Emergency medical system |
-
2007
- 2007-08-27 US US11/895,705 patent/US8428961B2/en active Active
-
2008
- 2008-10-01 US US12/243,860 patent/US20090018869A1/en not_active Abandoned
Patent Citations (72)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5454024A (en) * | 1989-08-31 | 1995-09-26 | Lebowitz; Mayer M. | Cellular digital packet data (CDPD) network transmission system incorporating cellular link integrity monitoring |
US5301105A (en) * | 1991-04-08 | 1994-04-05 | Desmond D. Cummings | All care health management system |
US5911687A (en) * | 1995-11-15 | 1999-06-15 | Hitachi, Ltd. | Wide area medical information system and method using thereof |
US5945919A (en) * | 1996-05-30 | 1999-08-31 | Trimble Navigation Limited | Dispatcher free vehicle allocation system |
US6055506A (en) * | 1997-04-25 | 2000-04-25 | Unitron Medical Communications, Inc. | Outpatient care data system |
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US6014629A (en) * | 1998-01-13 | 2000-01-11 | Moore U.S.A. Inc. | Personalized health care provider directory |
US6117073A (en) * | 1998-03-02 | 2000-09-12 | Jones; Scott J. | Integrated emergency medical transportation database system |
US6560569B1 (en) * | 1998-05-13 | 2003-05-06 | Nabil A. Abu El Ata | Method and apparatus for designing and analyzing information systems using multi-layer mathematical models |
US6594637B1 (en) * | 1998-09-14 | 2003-07-15 | International Business Machines Corporation | Schedule management system and method |
US6567796B1 (en) * | 1999-03-23 | 2003-05-20 | Microstrategy, Incorporated | System and method for management of an automatic OLAP report broadcast system |
US6761312B2 (en) * | 1999-07-30 | 2004-07-13 | Salamander Technologies, Inc. | System and method for tracking victims of a mass casualty incident |
US20020153413A1 (en) * | 1999-07-30 | 2002-10-24 | Piatek John T. | System and method for tracking victims of a mass casualty incident |
US6212393B1 (en) * | 1999-08-02 | 2001-04-03 | Motorola, Inc. | Method and apparatus for communication within a vehicle dispatch system |
US6305605B1 (en) * | 1999-08-09 | 2001-10-23 | John W. Goetz | Multiple-casualty incident patient tracking |
US20020011518A1 (en) * | 1999-08-09 | 2002-01-31 | Goetz John W. | Multiple-casualty incident patient tracking |
US6499658B2 (en) * | 1999-08-09 | 2002-12-31 | John W. Goetz | Multiple-casualty incident patient tracking |
US7001334B2 (en) * | 1999-11-05 | 2006-02-21 | Wcr Company | Apparatus for non-intrusively measuring health parameters of a subject and method of use thereof |
US6574480B1 (en) * | 1999-12-10 | 2003-06-03 | At&T Corp. | Method and apparatus for providing intelligent emergency paging |
US6571285B1 (en) * | 1999-12-23 | 2003-05-27 | Accenture Llp | Providing an integrated service assurance environment for a network |
US6377210B1 (en) * | 2000-02-25 | 2002-04-23 | Grey Island Systems, Inc. | Automatic mobile object locator apparatus and method |
US20010032195A1 (en) * | 2000-03-30 | 2001-10-18 | Graichen Catherine Mary | System and method for identifying productivity improvements in a business organization |
US20040243446A1 (en) * | 2000-04-06 | 2004-12-02 | Phil Wyatt | Method and a system for optimizing hospital beds and ambulance allocations via a computer network |
US6957218B1 (en) * | 2000-04-06 | 2005-10-18 | Medical Central Online | Method and system for creating a website for a healthcare provider |
US20020013714A1 (en) * | 2000-05-19 | 2002-01-31 | Sanalink Ag | System and method for transmitting information between doctors and hospitals |
US20020032593A1 (en) * | 2000-05-25 | 2002-03-14 | Berman Phillip M. | Method and system for determining cat scan availability |
US20030021417A1 (en) * | 2000-10-20 | 2003-01-30 | Ognjen Vasic | Hidden link dynamic key manager for use in computer systems with database structure for storage of encrypted data and method for storage and retrieval of encrypted data |
US6789046B1 (en) * | 2000-12-05 | 2004-09-07 | Microsoft Corporation | Performance logging solution |
US6701156B2 (en) * | 2000-12-19 | 2004-03-02 | Lucent Technologies Inc | System and method for managing response to a need at a site |
US6563910B2 (en) * | 2001-02-26 | 2003-05-13 | Royal Thoughts, Llc | Emergency response information distribution |
US20030212494A1 (en) * | 2001-03-30 | 2003-11-13 | Alexander John Franklin | Emergency management system |
US20050055330A1 (en) * | 2001-05-15 | 2005-03-10 | Britton Colin P. | Surveillance, monitoring and real-time events platform |
US20020198445A1 (en) * | 2001-06-26 | 2002-12-26 | Steven Dominguez | System and method for monitoring body functions |
US20030040939A1 (en) * | 2001-08-24 | 2003-02-27 | Daniel Tritch | Method of storing and retrieving advance medical directives |
US20030074222A1 (en) * | 2001-09-07 | 2003-04-17 | Eric Rosow | System and method for managing patient bed assignments and bed occupancy in a health care facility |
US20030115085A1 (en) * | 2001-12-13 | 2003-06-19 | Allied Telesis Kabushiki Kaisha | Management system and method |
US20040006492A1 (en) * | 2002-01-30 | 2004-01-08 | Nec Infrontia Corporation | Health care service system |
US7337146B2 (en) * | 2002-03-04 | 2008-02-26 | Swan Island Networks, Inc. | Emergency information management system |
US7899682B2 (en) * | 2002-03-22 | 2011-03-01 | Thinksharp, Inc. | Method and system of rule-based triage |
US7034678B2 (en) * | 2002-07-02 | 2006-04-25 | Tri-Sentinel, Inc. | First responder communications system |
US20040070515A1 (en) * | 2002-07-02 | 2004-04-15 | Raymond Burkley | First responder communications system |
US20050001720A1 (en) * | 2002-07-02 | 2005-01-06 | Charles Mason | Emergency response personnel automated accountability system |
US20050038696A1 (en) * | 2002-08-02 | 2005-02-17 | American Medical Response | System and method for managing requests for medical transportation |
US6975963B2 (en) * | 2002-09-30 | 2005-12-13 | Mcdata Corporation | Method and system for storing and reporting network performance metrics using histograms |
US20040138925A1 (en) * | 2002-12-23 | 2004-07-15 | Zheng Shu Sean | Resources utilization management system and method of use |
US20040153440A1 (en) * | 2003-01-30 | 2004-08-05 | Assaf Halevy | Unified management of queries in a multi-platform distributed environment |
US20040153343A1 (en) * | 2003-01-31 | 2004-08-05 | Phyllis Gotlib | Medical information query system |
US20040162707A1 (en) * | 2003-02-12 | 2004-08-19 | Saint-Amour Paula J. | Early alert and response system |
US20030177051A1 (en) * | 2003-03-13 | 2003-09-18 | Robin Driscoll | Method and system for managing worker resources |
US20040193447A1 (en) * | 2003-03-28 | 2004-09-30 | Joseph Sameh S. | Website messaging system for public health information |
US20070078677A1 (en) * | 2003-05-19 | 2007-04-05 | Intellirad Solutions Pty Ltd | Controlling access to medical records |
US20050137929A1 (en) * | 2003-06-13 | 2005-06-23 | Ibex Healthdata Systems, Inc. | Health unit assessment tool |
US7177623B2 (en) * | 2003-07-02 | 2007-02-13 | The United States Of America As Represented By The Secretary Of The Army | Localized cellular awareness and tracking of emergencies |
US20050010436A1 (en) * | 2003-07-08 | 2005-01-13 | Richard Merkin | Health care administration method |
US20050075904A1 (en) * | 2003-10-06 | 2005-04-07 | Cerner Innovation, Inc. | System and method for automatically generating evidence-based assignment of care providers to patients |
US20050131740A1 (en) * | 2003-12-10 | 2005-06-16 | Geoage, Incorporated | Management tool for health care provider services |
US20050201528A1 (en) * | 2004-03-13 | 2005-09-15 | Intrado Inc. | Bi-directional messaging for an emergency services network |
US20050201359A1 (en) * | 2004-03-13 | 2005-09-15 | Intrado Inc. | Dynamically establishing media channels between resources of an emergency services network and conforming emergency systems |
US20050201529A1 (en) * | 2004-03-13 | 2005-09-15 | Intrado Inc. | Method and apparatus for increasing the reliability of an emergency call communication network |
US7200207B2 (en) * | 2004-03-13 | 2007-04-03 | Intrado Inc. | Communication network for providing emergency services |
US20050201345A1 (en) * | 2004-03-15 | 2005-09-15 | Williamson Robert D. | Mobile patient care system |
US20050282141A1 (en) * | 2004-06-17 | 2005-12-22 | Falash Mark D | Scenario workflow based assessment system and method |
US20070061393A1 (en) * | 2005-02-01 | 2007-03-15 | Moore James F | Management of health care data |
US20060235716A1 (en) * | 2005-04-15 | 2006-10-19 | General Electric Company | Real-time interactive completely transparent collaboration within PACS for planning and consultation |
US20060236247A1 (en) * | 2005-04-15 | 2006-10-19 | General Electric Company | Interface to display contextual patient information via communication/collaboration application |
US20060235936A1 (en) * | 2005-04-15 | 2006-10-19 | General Electric Company | System and method for PACS workstation conferencing |
US20060277595A1 (en) * | 2005-06-06 | 2006-12-07 | Novell, Inc. | Techniques for providing role-based security with instance-level granularity |
US20070021981A1 (en) * | 2005-06-29 | 2007-01-25 | James Cox | System for managing emergency personnel and their information |
US7661146B2 (en) * | 2005-07-01 | 2010-02-09 | Privamed, Inc. | Method and system for providing a secure multi-user portable database |
US20070239484A1 (en) * | 2006-03-20 | 2007-10-11 | Arond Betty J | System and method for managing patient bed assignments, bed occupancy, and staffing in a healthcare facility operation |
US20070280462A1 (en) * | 2006-05-30 | 2007-12-06 | Roger Neil Neece | System and method for security monitoring and response delivery |
US20070285226A1 (en) * | 2006-06-12 | 2007-12-13 | Healthpia Co., Ltd. | System and method for emergency alarm |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120316892A1 (en) * | 2011-06-08 | 2012-12-13 | Huster Keith A | System and method of bed data aggregation, normalization and communication to third parties |
US8548911B2 (en) * | 2012-02-09 | 2013-10-01 | Bank Of America Corporation | Devices and methods for disaster-relief support |
CN103810560A (en) * | 2013-11-01 | 2014-05-21 | 北京交通大学 | Emergency resource scheduling method for emergencies of rail transit |
CN103810560B (en) * | 2013-11-01 | 2017-10-31 | 北京交通大学 | A kind of track traffic accident emergency resources dispatching method |
US20170200690A1 (en) * | 2015-07-23 | 2017-07-13 | Nippon Micrometal Corporation | Bonding wire for semiconductor device |
Also Published As
Publication number | Publication date |
---|---|
US8428961B2 (en) | 2013-04-23 |
US20070297589A1 (en) | 2007-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8428961B2 (en) | Method and system for data aggregation for real-time emergency resource management | |
US20080046285A1 (en) | Method and system for real-time emergency resource management | |
US8364500B2 (en) | Publisher gateway systems for collaborative data exchange, collection, monitoring and/or alerting | |
US8306831B2 (en) | Systems with message integration for data exchange, collection, monitoring and/or alerting | |
US7827234B2 (en) | Privacy entitlement protocols for secure data exchange, collection, monitoring and/or alerting | |
US7912733B2 (en) | System, method and program product for delivering medical services from a remote location | |
US20180240545A1 (en) | Systems and methods for delivering on-call data for health care locations and physicians | |
US20080288466A1 (en) | User selectable data attributes for automated electronic search, identification and publication of relevant data from electronic data records at multiple data sources | |
US20100256994A1 (en) | Privacy entitlement protocols for secure data exchange, collection, monitoring and/or alerting | |
US20080243545A1 (en) | System and method of aggregating and disseminating in-case-of-emergency medical and personal information | |
US20040078229A1 (en) | System and method of managing electronic medical records | |
US20080208914A1 (en) | Centralized mining of remote medical records databases | |
WO2005059681A2 (en) | Management tool for health care provider services | |
JPH1125190A (en) | Outpatient nursing data system | |
WO2011044838A1 (en) | Electronic health archives system oriented to resident individual | |
US10319056B1 (en) | Biased task assignments based on geotracking of discharge vehicles | |
US20050209884A1 (en) | Method, system and computer program product for providing medical information | |
US20080114613A1 (en) | Integrated Electronic Healthcare Management System | |
US20020059246A1 (en) | Method of distributing information to emergency personnel | |
US20040030579A1 (en) | Method, system and computer program product for providing medical information | |
Fabbri et al. | Explaining accesses to electronic health records | |
Hauenstein et al. | A cross-functional service-oriented architecture to support real-time information exchange in emergency medical response | |
US20220148693A1 (en) | Patent-centric health care system | |
US20070174093A1 (en) | Method and system for secure and protected electronic patient tracking | |
JP2004192498A (en) | System for managing information related to medical service and welfare |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EMSYSTEM, LLC, WISCONSIN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GREISCHAR, PATRICK J.;BARTHELL, EDWARD;HEDGCOCK, ROBERT;AND OTHERS;REEL/FRAME:022534/0266;SIGNING DATES FROM 20090306 TO 20090317 |
|
AS | Assignment |
Owner name: KAPI MEZZANINE, L.P., CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS, LLC;REEL/FRAME:023712/0141 Effective date: 20091113 |
|
AS | Assignment |
Owner name: EMSYSTEMS LLC,WISCONSIN Free format text: CERTIFICATE OF CONVERSION AND CERTIFICATE OF NAME CHANGE;ASSIGNOR:EMSYSTEM LLC;REEL/FRAME:024116/0751 Effective date: 20080612 |
|
AS | Assignment |
Owner name: EMSYSTEMS LLC,WISCONSIN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GREISCHAR, PATRICK J.;BARTHELL, EDWARD;HEDGCOCK, ROBERT;AND OTHERS;SIGNING DATES FROM 20100326 TO 20100329;REEL/FRAME:024205/0956 |
|
AS | Assignment |
Owner name: EMSYSTEMS LLC,WISCONSIN Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 023712/0141;ASSIGNOR:KAPI MEZZANINE, L.P.;REEL/FRAME:024290/0598 Effective date: 20100426 Owner name: GE BUSINESS FINANCIAL SERVICES INC., FORMERLY KNOW Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:024290/0896 Effective date: 20100426 Owner name: EMSYSTEMS LLC, WISCONSIN Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 023712/0141;ASSIGNOR:KAPI MEZZANINE, L.P.;REEL/FRAME:024290/0598 Effective date: 20100426 |
|
AS | Assignment |
Owner name: MCG CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT,V Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:024296/0274 Effective date: 20100426 Owner name: MCG CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT, Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:024296/0274 Effective date: 20100426 |
|
AS | Assignment |
Owner name: GENERAL ELECTRIC CAPITAL CORPORATION, ILLINOIS Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:024874/0001 Effective date: 20100823 Owner name: EMSYSTEMS LLC, WISCONSIN Free format text: PATENT RELEASE AND REASSIGNMENT;ASSIGNOR:GE BUSINESS FINANCIAL SERVICES INC.;REEL/FRAME:024874/0465 Effective date: 20100823 Owner name: EMSYSTEMS LLC, WISCONSIN Free format text: PATENT RELEASE AND REASSIGNMENT;ASSIGNOR:MCG CAPITAL CORPORATION;REEL/FRAME:024874/0542 Effective date: 20100823 |
|
AS | Assignment |
Owner name: GENERAL ELECTRIC CAPITAL CORPORATION, AS ADMINISTR Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:025970/0180 Effective date: 20110314 |
|
AS | Assignment |
Owner name: EMSYSTEMS LLC, WISCONSIN Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:GENERAL ELECTRIC CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT;REEL/FRAME:026034/0671 Effective date: 20110314 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: ARES CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT, Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:029548/0702 Effective date: 20121227 Owner name: GENERAL ELECTRIC CAPITAL CORPORATION, AS ADMINISTR Free format text: SECURITY AGREEMENT;ASSIGNOR:EMSYSTEMS LLC;REEL/FRAME:029548/0492 Effective date: 20121227 Owner name: EMSYSTEMS LLC, FLORIDA Free format text: RELEASE BY SECURED PARTY OF REEL/FRAME 025970/0180;ASSIGNOR:GENERAL ELECTRIC CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT;REEL/FRAME:029548/0483 Effective date: 20121227 |
|
AS | Assignment |
Owner name: ARES CAPITAL CORPORATION, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GENERAL ELECTRIC COMPANY, AS SUCCESSOR IN INTEREST BY MERGER TO GENERAL ELECTRIC CAPITAL CORPORATION;REEL/FRAME:043702/0835 Effective date: 20170920 |
|
AS | Assignment |
Owner name: INTERMEDIX OFFICE BASED, LLC, FLORIDA Free format text: NOTICE OF RELEASE OF SECURITY INTEREST IN PATENTS (SECOND LIEN);ASSIGNOR:ARES CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT;REEL/FRAME:046106/0685 Effective date: 20180508 Owner name: EMSYSTEMS LLC, FLORIDA Free format text: NOTICE OF RELEASE OF SECURITY INTEREST IN PATENTS (SECOND LIEN);ASSIGNOR:ARES CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT;REEL/FRAME:046106/0685 Effective date: 20180508 Owner name: INTERMEDIX OFFICE BASED, LLC, FLORIDA Free format text: NOTICE OF RELEASE OF SECURITY INTEREST IN PATENTS (FIRST LIEN);ASSIGNOR:ARES CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT;REEL/FRAME:046106/0644 Effective date: 20180508 Owner name: EMSYSTEMS LLC, FLORIDA Free format text: NOTICE OF RELEASE OF SECURITY INTEREST IN PATENTS (FIRST LIEN);ASSIGNOR:ARES CAPITAL CORPORATION, AS ADMINISTRATIVE AGENT;REEL/FRAME:046106/0644 Effective date: 20180508 |