WO2011101817A1 - Medical emergency management - Google Patents

Medical emergency management Download PDF

Info

Publication number
WO2011101817A1
WO2011101817A1 PCT/IB2011/050692 IB2011050692W WO2011101817A1 WO 2011101817 A1 WO2011101817 A1 WO 2011101817A1 IB 2011050692 W IB2011050692 W IB 2011050692W WO 2011101817 A1 WO2011101817 A1 WO 2011101817A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer
information
medical
emergency
module
Prior art date
Application number
PCT/IB2011/050692
Other languages
French (fr)
Inventor
Ajith Kamath
Original Assignee
Ajith Kamath
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ajith Kamath filed Critical Ajith Kamath
Publication of WO2011101817A1 publication Critical patent/WO2011101817A1/en

Links

Images

Classifications

    • 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

Definitions

  • the subject matter described herein in general, relates to management of medical emergency and in particular relates to a system for delivering information of a registered customer across a network to manage an emergency situation.
  • a victim an injured, sick and/or the like
  • an emergency person needs information about the victim to provide best assistance to the victim.
  • the information about the victim is limited to information that the victim may orally convey at that time.
  • ECC emergency call centres Due to rising needs for the medical support during the emergency situation, many emergency call centres (ECC) have come into existence.
  • ECC stores clinical information and electronic medical records (EMR) of a customer (victim after the casualty) in a database.
  • EMR electronic medical records
  • the medical records of the customers are used as a tool during the medical emergency of the customers.
  • the EMR have been used to structure and store customer information in a comprehensive, longitudinal manner so that relevant information is accessible to the emergency person at an appropriate time and place. This reduces time and effort required to document and retrieve details of the care provided to the victim entity details which are required for providing care to the victim.
  • the emergency person is required to locate a suitable medical facility for the victim in time.
  • the medical facility further will require insurance details such as cashless facility for the victim, the medical history details of the victim and/or the like.
  • well-wisher of the victim is needed to be informed in order to take care of the victim and to perform the medical and financial formalities for treatment of the victim.
  • the subject matter described herein is directed to a method and system for delivering information of a registered customer across a network to manage an emergency situation.
  • the system includes a storage module for storing individual specific emergency information of the registered customer.
  • the emergency information includes identity information of the customer.
  • the system requires the identity information of the customer to identify the customer at the time of emergency situation such as casualty.
  • the identity information of the customer may be provided by an emergency person present at the casualty spot.
  • the emergency information of the entity includes contact information of at least one well-wisher of the entity. Based on the contact information of the well-wisher, the system notifies the well-wisher of the customer regarding the emergency situation and location. The system further transmits filtered travelling information to the well-wisher.
  • the travelling information provides convenience for well-wisher to select the suitable travelling option without wasting any time on searching for the relevant information.
  • the system provides a list of medical facility to a customer care executive.
  • the customer care executive provides the information of medical facility and financial coverage of insurance information.
  • the emergency person may transfer the entity to the nearest suitable medical facility.
  • the system facilitates the management of medical emergency and provides emergency support to the customer.
  • the system further eliminates the painful procedures faced by the customer at the time of medical emergencies.
  • FIG. 1 is a block diagram of a system 100 illustrating a medical emergency management, in accordance with an aspect of the present invention
  • FIG. 2 is a flow diagram of a method 200 illustrating a method of operation of the medical emergency management system in accordance with an embodiment of the present invention
  • FIG. 3 is a flow diagram of a method 300 illustrating a method followed by a medical emergency management system after a customer meets any casualty, in accordance with an aspect of the present invention
  • FIG. 4 is a flow diagram of a method 400 illustrating a method for identifying a customer under the casualty as a registered customer of a medical emergency management system, in accordance with an aspect of the present invention
  • FIG. 5 is a flow diagram of a method 500 for illustrating a method for identifying suitable medical facility for the customer and transferring the customer to the identified medical facility, in accordance with an aspect of the present invention.
  • FIG. 6 is a flow diagram of a method 600 for illustrating a method of communication between a logistic provider and one or more well-wishers of a customer, in accordance with an aspect of the present invention.
  • FIG. 1 is a block diagram of a system 100 illustrating a medical emergency management (MEM) for a customer under a medical emergency due to a casualty (e.g., an accident, sickness, and/or the like) according to one or more embodiments of the invention.
  • the system 100 includes a registration module (RgM) 102, an information module (InM) 104, a medical support module (MSM) 106, a logistic module (LM) 108 and an identification module (IdM) 110.
  • the system 100 records information regarding one or more entities and utilizes the information to manage a situation of the medical emergency of the customer.
  • the registration module 102 is implemented to facilitate registration of one or more entities to the system 100.
  • the one or more entities may include one or more customers, one or more well wishers of the one or more of the customers, one or more medical facilities, one or more insurance companies of the one or more customers, one or more logistic providers, one or more customer care executives, one or more volunteers and/or the like.
  • the registration module 102 includes a registration form (which may be online) in order to fill up information of the entities.
  • the system 100 retrieves the registration form from the registration module 102 and displays the registration form to the entity.
  • the entity furnishes the required information in the registration form.
  • the registration module 102 communicates the information as filled up in the registration form to an information module 104.
  • the registration module 102 provides a unique account to the entity.
  • the account of the entity may include a login ID and a password in order to access and/or edit the information.
  • the well-wisher of the customer may map his account as well-wisher of the customer.
  • the information module 104 is required to save the information regarding the entity.
  • the information module 104 includes the information of the entity such as, details of the customer, details of the one or more well wishers of the customer, details of the one or more medical facilities, details of the one or more insurance companies, details of the one or more logistic providers and/or the like.
  • the details of the customer may include personal details, medical history details, insurance details, identification details and/or the like.
  • the personal details of the customer may include name, address, contact number, one or more preferred locations, name of one or more well wishers in case of emergency and/or the like.
  • the insurance details of the customer may include insurance plan, financial coverage of the insurance plan according to the type of casualty and/or the like.
  • the identification details of the customer may include driving license number of the entity, pan card number of the entity, vehicle number of the entity ATM card, club membership card and/or the like.
  • Thesystem 100 enhances customer's capability to manage information pertaining to insurance policies and details of all types of investments.
  • the system 100 allows smooth processing of documentation and information access pertaining to insurance and investment details.
  • the system 100 further allows documenting of information like deposit amount, withdrawal amount, deposit date, due date, overdraft facility availability, emergency rollback flexibility, risk factor details, nominee details and like information.
  • the insurance parameters include insurance cover denomination, cover grant terms, casualties covered, diseases covered and like information.
  • the system 100 also allows documenting the description of whereabouts of the paper and digital records pertaining to insurance and investments owned by the customer. The system makes it convenient to make quick decision about managing investments and day to day cash flows for the customer.
  • the details of the one or more well wishers of the customer may include name, address, contact number, preferred locations, preferred budget in case of travelling during the medical emergency of the customer and/or the like.
  • the details of the one or more medical facilities may include medical facility name, route details, details of available doctors, doctor's specializations, available devices and/or instruments, number of beds, efficiency to accommodate emergency wards and operation theatres also, human resource real-time tracking and/or the like.
  • the details of the one or more insurance companies may include name, plans, list of type of casualties each of the insurance companies insures, financial coverage for each type of the casualties and/or the like.
  • the information module 104 may further include information regarding casualty of the registered customer such as, location of the casualty of the registered customer, type of injury (for example, mental sickness, consciousness, accident and/or the like) and/ or the like.
  • the information module 104 is further connected to an identification module 110, a medical support module 106 and a logistic support module 108 in order to communicate the information to one and/or each of the module in case of the medical emergency of the customer.
  • the identification module 110 is implemented to identify the identity of registered customer.
  • the identification module 110 utilizes the identification details of the information module 104 in order to identify the identity of the registered customer.
  • the identification module 110 facilitates a customer care executive in identifying the identity of the registered customer. For example, if the customer care executive is informed about a casualty of a customer by an emergency person, then the customer care executive fills up the identification details of the customer in the identification module 110 as provided by the emergency person.
  • the identification module 110 matches the identification details of the customer with the information in the information module as provided by registered customer during registration 104 and verifies whether the customer is the registered customer or not. Furthermore, if the customer is the registered customer, then the identification module 110 displays the information of the registered customer to the customer care executive. The customer care executive is then required to enter details of the casualty of the registered customer such as, location of the casualty, type of injury to the customer and/ or the like. The details of the casualty are saved in the information module 104.
  • the medical support module 106 is implemented to support the registered customer in the need of the medical emergency.
  • the medical support module 106 identifies the medical facility nearest to the casualty location on the basis of casualty location and the medical facility information as retrieved from the information module 104.
  • the medical support module 106 displays the medical facility information to the customer care executive.
  • the customer care executive further informs the emergency person regarding the medical facility information.
  • the medical support module 106 communicates information regarding the customer (e.g., location of the casualty, type of injury/sickness, insurance details and/or the like) to the identified medical facility. In yet another embodiment, the medical support module 106 communicates information regarding the customer such as, location of the casualty, location of the medical facility to which the customer is to be admitted or taken, type of injury and/or the like to the logistic module 108.
  • the customer e.g., location of the casualty, type of injury/sickness, insurance details and/or the like
  • the medical support module 106 communicates information regarding the customer such as, location of the casualty, location of the medical facility to which the customer is to be admitted or taken, type of injury and/or the like to the logistic module 108.
  • the logistic module 108 is required to inform and support the well wishers of the customer under the medical emergency.
  • the logistic module 108 retrieves information regarding the well wishers of the customer from the information module 110 after receiving the information from the medical support module 106.
  • the logistic module 108 further sends an alert to the well wishers of the customer information regarding casualty such as, location of the casualty, injury type and/ or the like via email, SMS,instant messengers, typical messaging system, such as blackberry messaging system, inter-office social network of the one or more well wisher's employer and/or the like.
  • the logistic module 108 retrieves information regarding the logistics provider from the information module 110 and sends information regarding the well wisher of the customer such as name of the well wisher, contact number, budget for travelling and/or the like to the logistics provider.
  • the logistics provider then provides the information on travelling options according to the information registered by the well-wisher of the customer.
  • the logistics provider arranges the ticket based on selected option of the well wisher and sends the ticket to the well wisher via any physical means, such as door delivery, any digital means, such as online and/or the like.
  • FIG. 2 is a flow diagram of a method 200 for illustrating a method of operation of a medical emergency management system, for example, the system 100.
  • the method 200 starts at step 202 and proceeds to step 204, at which a registration of a customer is done.
  • the customer registers with the medical emergency management system, for example, the system 100, in order to attain life supporting help in case of any casualty of the customer.
  • the customer is required to fill up details of one or more well-wishers of the customer.
  • registration of one or more well-wishers of the customer is done.
  • the one or more well-wishers of the customer are required to register with the system 100 and furnish the required information.
  • registration of one or more insurance companies is performed.
  • the customer is required to fill information regarding insurance company with which the customer is insured.
  • one or more insurance companies may register with the system 100 as an entity.
  • registration of one or more medical facilities is done.
  • the one or more desired medical facility may register with the system 100 as an entity and to provide medical support during the casualty of the customer.
  • registration of one or more logistic providers is done.
  • one or more desired logistic providers may register with the system 100 as an entity and to provide travelling facilities to the one or more well-wishers of the customer during the casualty of the customer.
  • the customer is identified after meeting any casualty. For example, if the customer meets any casualty, then the customer is identified in order to provide each and every support to the customer.
  • medical support to the customer is provided during the casualty and the well-wishers of the customer are informed about the casualty of the customer.
  • the method 200 ends at step 218.
  • FIG. 3 is a flow diagram of a method 300 for illustrating a method followed by a medical emergency management system, for example, the system 100 after a customer meets any casualty.
  • the customer meeting the casualty is referred to as a customer until the customer is identified as a registered customer of the system 100.
  • the method 300 starts at step 302 and proceeds to step 304, at which a customer care executive is called by an emergency person regarding the casualty of the customer.
  • the emergency person calls a call centre regarding the casualty of the customer.
  • the customer care executive attends the call of the emergency person.
  • calling contact number is identified.
  • the calling contact number refers to the contact number through which the emergency person calls at the call centre.
  • IVR Interactive Voice Response
  • IVR Interactive Voice Response hardware at the call centre detects the calling contact number and checks whether the calling contact number corresponds to any of the registered customers. If the calling contact number corresponds to any of the registered customers, then record of that customer is displayed in browser of computer screen of the customer care executive.
  • the CCE in case the emergency person calls the CCE from his contact number, the CCE asks for contact number of the customer for identification. The emergency person may then provide the contact number of the customer.
  • the customer has footwear that are embedded with an RFID whose embedded unique digital identification number is sold to the customer along with footwear or the customer can buy an RFID whose embedded unique digital identification number is sold to the customer along with RFID;
  • the customer registers the embedded digital identification number with his account.
  • the emergency person is equipped with RFID sensing and their embedded ID reading device which on switching on detects the RFID ID and thus ultimately the identity of the medical emergency customer at casualty spot.
  • This facility has many benefits because many people can be detected within a short time instant and this arrangement gives user a highly effective and practical advantage even in case of natural calamities as users tend to stay not too distant from their personal belongings like footwear and/or like.
  • the RFID may also be embedded into clothing or hair clips or ornaments or leg bandages or neck bands and/or like devices.
  • the embedding device can be of any wireless technology protocol and technology standard.
  • information regarding the customer is acquired.
  • the customer care executive acquires information regarding the customer from the emergency person in order to identify the customer.
  • the customer is identified as a registered customer.
  • one or more well-wishers of the customer are notified regarding the casualty of the customer.
  • the system 100 automatically notifies the one or more well-wishers of the customer regarding casualty of the customer.
  • the customer provides information regarding the one or more well-wishers and well-wishers that are required to be contacted in case of any emergency.
  • the CCE selectively controls notifications to the individual well wisher (at the time of emergency) on the basis of information provided by the customer.
  • step 31 geographical location of the casualty and type of injury to the customer are determined.
  • step 316 a medical facility located nearest to the casualty location is identified.
  • one or more medical facilities are automatically displayed on the computer screen of the customer care executive after the customer care executive provides the information about location of the casualty.
  • the customer care executive determines the medical facility that is nearest to the location of the casualty and suitable for the type of injury of the customer.
  • CCE provides information regarding the identified medical facility and financial coverage of insurance of the customer to the emergency person.
  • the system makes it possible for the emergency person to take calculated financial risk taking which risk might be required for undertaking treatment costing more than the amount covered by insurance covers owned by identified user.
  • a transport means is arranged in order to transfer the customer to the identified medical facility.
  • the customer care executive arranges for the transport means in order to transfer the customer to the identified medical facility.
  • a communication is made with the identified medical facility.
  • the customer care executive communicates with staff and/or doctor of the identified medical facility and sends medical details, insurance details and/or the like.
  • communication with one or more well-wishers of the customer is done and the method 300 ends at step 326.
  • FIG. 4 is a flow diagram of a method 400 for illustrating a method for identifying a customer under the casualty as a registered customer of a medical emergency management system, for example, the system 100.
  • the method 400 starts at a step 402 and proceeds to step 404, at which a contact number of the customer is acquired.
  • emergency person calls to a customer care executive.
  • the customer care executive inquires whether the calling contact number is of the customer or not.
  • the customer care executive acquires contact number of the customer from the emergency person if the calling contact number is not related to the customer.
  • plate number of the vehicle is acquired. In an embodiment, the emergency person provides the plate number of the vehicle to the customer care executive. If a determination is made that the customer was not riding the vehicle (option 'NO'), then the method 400 proceeds to step 412.
  • registration card number is acquired. In an embodiment, the emergency person provides the registration card number of the customer to the customer care executive.
  • the customer has a device, which is fixed to any part of a wheeled vehicle, even to a cab that the customer takes on a given day which senses sudden stopping of vehicle by sensing instantaneous velocity of the device at high speed continuously with very small time gaps.
  • the device includes audio recording facility by user. User voice recording ability assures device can spell out user registration information, mobile number or like information, which realises the same effect of emergency management even if accident location does not have communication connectivity.
  • the button press will start playing the recorded message and this setup is configurable by user such that the playback starts either immediately when a jerky stop of vehicle is detected with or without a time delay or only when button pressed as configured by the customer at a given moment on a given day.
  • the device further includes a ⁇ stop playing ⁇ button and an optical indicator.
  • the device optical indicator activates when a vehicle suddenly decelerates. These facilities makes it possible to avoid user embarrassment that may result due to immediate playback of information as a result of just a sudden break by driver of vehicle and not a result of coming to rest due to accident.
  • User can press the ⁇ stop playing ⁇ button when optical indicator lights up indicating that jerk has been sensed.
  • the device includes a voice recognition control to supplement the ⁇ stop playing ⁇ button press process so that the user may relax by communicating with the device by speaking to the device.
  • the device includes a voice control based reacting component attached to this system which makes this device serve the user as stress busting device during driving.
  • customer details of the respective registration card number are displayed on the system 100.
  • the customer care executive enters the registration card number of the customer in a database of the system 100 as provided by the emergency person. Consequently, customer details related to the registration card number are displayed on the system and the customer care executive inquires the emergency person regarding other details of the customer.
  • other pre-registered parameters such as skin tone, facial and body geometry of the customer are matched.
  • the facial and body geometry includes information about structure of face (broad, narrow, oval or the like) or body (tall, short, slim or the like) and any identifying mark on the face and/or body.
  • the customer is identified as the registered customer. In an embodiment, if the pre-registered parameters of the customer are matched with the customer, then the customer is identified as the registered customer and thus, the identity of the customer is determined.
  • the method 400 ends at step 420.
  • FIG. 5 is a flow diagram of a method 500 for illustrating a method for identifying suitable hospital for the customer and directing the customer to the medical facility identified by a medical emergency management system, for example, the system 100.
  • the method 500 starts at a step 502 and proceeds to step 504, at which the customer care executive receives location information of casualty from the EP.
  • the customer care executive further receives details of type of injury caused to the customer.
  • the customer care executive asks various pre-documented questions about the customer situation such as cause of the customer casualty, state of the customer and type of the casualty suffered.
  • the EP provides the answers that are further processed by the system 100 in order to determine resources required for the treatment of the customer.
  • the resources include medical devices, hospital infrastructure, medical experts and other resources.
  • the system records the conversation between the CCE and EP for future use.
  • a 3D animated interface of human body is provided for easier and quicker understanding of injury diagnosis, treatment diagnosis and/or like when patient is on the way.
  • the doctor may find out what type of injury might the patient seems to have undergone internally based on what appears as medical situation of the customer.
  • the doctor may further diagnose what treatment would be perfect applicable treatment to external and internal body parts of customer.
  • the interface makes it easy for the treating doctor and one or more treatment and diagnosis experts to understand the analysis of situation of the customer as perceived by each other.
  • the interface may further allow to diagnose the probable best fit treatment for the customer thereby making best use of available precious time.
  • the CCE retrieves a list of medical facilities.
  • the customer care executive enquires the medical facilities regarding the resources such as path to the medical facility,details of doctors available, doctor's specializations, available devices, bed counts, capability to accommodate emergency wards, human resource real-time tracking and/or like.
  • the customer care executes the conversation between the CCE and EP in a conference call at the reception of all nearby medical facilities.
  • the medical facilities provide the voice feedback to the CCE about resources available.
  • the CCE may access and use pre-documented information (information collected during the time of registration) about the resources available in the medical facility.
  • the CCE identify best suited medical facility based on location and resources information.
  • the customer care executive transmits the customer information to the medical facility.
  • the medical facility receives the detailed information about the insurance details such as cashless facility, insurance amount available and the like of the customer.
  • the medical facility further receives medical history and blood group information from the CCE.
  • doctors may access medical records of the customer only when an access key is provided by the well-wisher. The access key is available to the well-wisher in case the user has indicated during registration. Further, sensitive medical records may not be shared to any doctor except family doctor. The family doctor may provide the medical records to the doctor of the medical facility.
  • the medical facility sends an ambulance to the casualty location as soon as the alert is received from the system.
  • the CCE provides information of the duration required for the customer to reach medical facility.
  • the system allows real time telephonic conference to be created between the doctor of the identified medical facility and the emergency person.
  • the emergency person can describe condition of the customer.
  • aportable device for the medical facility staff and travel agents to make human resource tracking and active travel agent tracking possible.
  • the portable device that is connected to a centralised information management system customised for the purpose of managing the information furnished by the medical facility staff and travel agents makes it possible to track information provided by the medical facility staff and travel facilitators regarding their geographical location, their availability at pre-named locations (like the medical facility lobby, the medical facility eatery, specific named hotel's reception 'and like'), physical preparedness (whether they are too tired for attending), time wise readiness in offering service 'and like' information
  • This portable device also facilitates documentation of private (access restricted) content describing the aspects reasoning their availability at the medical facility, non availability of various treatment resources and like information which makes it possible for specific set of people to precisely decide upon availability of each of all the resources (resources including human resource, treatment device and like) for treatment of the medical emergency occurred in and around the medical facility. This makes it possible to precisely decide the perfect fit medical facility which can deliver the treatment harnessing all the resources which were considered to be available
  • the emergency person carries a mobile phone with 3G, 4G facilities or the like
  • the real-time video of the customer is displayed to the doctor.
  • the CCE avails the facility ofnon-paid and paid volunteers (nearest to casualty spot) if the customer has registered for the facility during the registration. The volunteer has at least quite a good knowledge about how to handle the emergency situation.
  • the method 500 ends at step 518.
  • FIG. 6 is a flow diagram of a method 600 for illustrating a method of communication between logistic provider and one or more well-wishers of a customer of the system 100.
  • the method 600 starts at step 602 and proceeds to step 604, at which a logistics provider is notified regarding an emergency situation of a customer.
  • the logistics provider is notified in order to provide travelling arrangements for the well-wisher of the customer.
  • the logistic module 108 of the system alerts the logistics provider regarding casualty of the customer.
  • information regarding one or more well-wishers of the customer is provided to the logistics provider.
  • the logistic module 108 communicates information regarding the one or more well-wishers of the customer to the logistics provider.
  • the logistic module 108 communicates information, such as location of the casualty, travelling budget of the one or more well-wishers of the customer, location of a medical facility to which the customer is taken or admitted and the like.
  • step 608 information regarding travelling options is provided.
  • the logistics provider looks for one or more travelling options after receiving the alert from the logistic module.
  • the search for the travelling options depends on the travelling budget of the one or more well-wishers of the customer.
  • information regarding the travelling budget is filled up during registration of the one or more well-wishers of the customer.
  • the system 100 allows the well-wisher to pre-document travel facility requirements from all desired combinations of means of travel, travel comfort level, various possible travel departure and arrival location wise and travel departure and arrival time of the day wise and which day of the week wise including interconnecting travel facility requirement documentation with each of these possibilities based on travel cost ranges.
  • the system allows travel details requirement of the well-wisher to be visible to all or selected travel facilitators.
  • This system allows travel facilitator to document all possible travel facilities which can be offered for each of all combinations of travel requirement parameters documented (or demanded) by the well-wisher.
  • the system 100 provides a dashboard for the well-wisher to filter specific offered travel facilities by all the travel facilitators by selecting desired values for each of all the travel requirement parameters.
  • Travel facilitator will have a dashboard for viewing the entire finalised travel requirement by all the travel facility seekers, arrange the facilities and update the status of finalisation of offering of finalised travel requirements by the well-wisher.
  • the well-wisher will have another dashboard, which conveys each of the details of reserved facility status including requested facility details, travel facilitator contact details, travel pickup and drop destinations, interconnecting travel facility details and like.
  • an appropriate travelling option is selected.
  • the one or more well-wishers of the customer selects appropriate travelling option in order to reach the location of the medical facility or the casualty.
  • selected travelling means for the one or more well-wishers are reserved.
  • the logistics provider reserves the travelling options as selected by the one or more well-wishers of the customer.
  • the one or more well-wishers of the customer may decide to opt for another logistic provider and inform a customer care executive regarding the same. Further, the customer care executive contacts the logistics provider in order to inform the logistics provider regarding cancelling or halting reservation of the travelling option.
  • a communication with the one or more well-wishers of the customer regarding reserved travelling arrangements is done.
  • the logistics provider may send a ticket to the one or more well-wishers of the customer via online, door delivery or any physical or digital means.
  • the logistics provider may inform the one or more well-wishers of the customer regarding details of a cab, a taxi, name, contact number, and/or the like of a driver, and/or the like.
  • the method 600 ends at step 616.
  • the advantage of the present subject matter is that the present invention providesan automated online emergency management system portal.
  • the system effectively manages the critical available time during a casualty of the customer to reach the hospital and notifying well-wishers about the casualty. Further, the system reduces the number of deaths due to casualties.

Abstract

A system and method for delivering information of a registered customer across a network to manage an emergency situation is described. The system includes an information module for storing individual specific emergency information of the registered customer. The emergency information includes identity information of the customer and contact information of at least one well-wisher of the customer. The system further includes an identification module for identifying the customer based on identity information. The identity information is provided by an emergency person at the time of an emergency. Further, a medical support module is included that provides medical facility information to the emergency person based on location information of the customer. The system further includes a logistic module for communicating filtered travelling information to the at least one well-wisher of the customer.

Description

MEDICAL EMERGENCY MANAGEMENT
RELATED APPLICATION INFORMATION
This application claims priority from Indian provisional Patent Application No. 437/CHE/2010 filed on February 20, 2010. The entire content of which is incorporated herein by this reference. The applicant claims the benefit of this provisional application.
FIELD OF THE INVENTION
The subject matter described herein, in general, relates to management of medical emergency and in particular relates to a system for delivering information of a registered customer across a network to manage an emergency situation.
BACKGROUND OF THE INVENTION
During an emergency situation, a victim (an injured, sick and/or the like) faces difficulties due to lack of timely medical support and information. In such a situation, an emergency person needs information about the victim to provide best assistance to the victim. But the information about the victim is limited to information that the victim may orally convey at that time.
Due to rising needs for the medical support during the emergency situation, many emergency call centres (ECC) have come into existence. The ECC stores clinical information and electronic medical records (EMR) of a customer (victim after the casualty) in a database. The medical records of the customers are used as a tool during the medical emergency of the customers. The EMR have been used to structure and store customer information in a comprehensive, longitudinal manner so that relevant information is accessible to the emergency person at an appropriate time and place. This reduces time and effort required to document and retrieve details of the care provided to the victim entity details which are required for providing care to the victim.
Besides the medical records, the emergency person is required to locate a suitable medical facility for the victim in time. The medical facility further will require insurance details such as cashless facility for the victim, the medical history details of the victim and/or the like. Moreover, well-wisher of the victim is needed to be informed in order to take care of the victim and to perform the medical and financial formalities for treatment of the victim.
Therefore, there is need to provide a method and system for delivering information regarding the customer across a network during the emergency situation that overcomes the above said limitations and thereby facilitating emergency support in an efficient manner.
SUMMARY OF THE INVENTION
The subject matter described herein is directed to a method and system for delivering information of a registered customer across a network to manage an emergency situation. The system includes a storage module for storing individual specific emergency information of the registered customer. The emergency information includes identity information of the customer. The system requires the identity information of the customer to identify the customer at the time of emergency situation such as casualty. The identity information of the customer may be provided by an emergency person present at the casualty spot.
Further, the emergency information of the entity includes contact information of at least one well-wisher of the entity. Based on the contact information of the well-wisher, the system notifies the well-wisher of the customer regarding the emergency situation and location. The system further transmits filtered travelling information to the well-wisher. The travelling information provides convenience for well-wisher to select the suitable travelling option without wasting any time on searching for the relevant information.
Further, based on the casualty location of the customer, the system provides a list of medical facility to a customer care executive. The customer care executive provides the information of medical facility and financial coverage of insurance information. The emergency person may transfer the entity to the nearest suitable medical facility.
According to an aspect of the present invention, the system facilitates the management of medical emergency and provides emergency support to the customer. The system further eliminates the painful procedures faced by the customer at the time of medical emergencies.
These and other features, aspects, and advantages of the present subject matter will be better understood with reference to the following description and appended claims. This summary is provided to introduce a selection of concepts in a simplified form. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
BRIEF DISCRIPTION OF THE DRAWINGS
These and other features, aspects, and advantages of the present invention will become better understood, when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
FIG. 1 is a block diagram of a system 100 illustrating a medical emergency management, in accordance with an aspect of the present invention;
FIG. 2 is a flow diagram of a method 200 illustrating a method of operation of the medical emergency management system in accordance with an embodiment of the present invention;
FIG. 3 is a flow diagram of a method 300 illustrating a method followed by a medical emergency management system after a customer meets any casualty, in accordance with an aspect of the present invention;
FIG. 4 is a flow diagram of a method 400 illustrating a method for identifying a customer under the casualty as a registered customer of a medical emergency management system, in accordance with an aspect of the present invention;
FIG. 5 is a flow diagram of a method 500 for illustrating a method for identifying suitable medical facility for the customer and transferring the customer to the identified medical facility, in accordance with an aspect of the present invention; and
FIG. 6 is a flow diagram of a method 600 for illustrating a method of communication between a logistic provider and one or more well-wishers of a customer, in accordance with an aspect of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
Figure 1 is a block diagram of a system 100 illustrating a medical emergency management (MEM) for a customer under a medical emergency due to a casualty (e.g., an accident, sickness, and/or the like) according to one or more embodiments of the invention. The system 100 includes a registration module (RgM) 102, an information module (InM) 104, a medical support module (MSM) 106, a logistic module (LM) 108 and an identification module (IdM) 110. In an embodiment, the system 100 records information regarding one or more entities and utilizes the information to manage a situation of the medical emergency of the customer.
According to an embodiment of the invention, the registration module 102 is implemented to facilitate registration of one or more entities to the system 100. The one or more entities may include one or more customers, one or more well wishers of the one or more of the customers, one or more medical facilities, one or more insurance companies of the one or more customers, one or more logistic providers, one or more customer care executives, one or more volunteers and/or the like.
The registration module 102 includes a registration form (which may be online) in order to fill up information of the entities. On the request of the entity for registration, the system 100 retrieves the registration form from the registration module 102 and displays the registration form to the entity. The entity furnishes the required information in the registration form. Further, the registration module 102 communicates the information as filled up in the registration form to an information module 104. The registration module 102 provides a unique account to the entity. The account of the entity may include a login ID and a password in order to access and/or edit the information. Further, the well-wisher of the customer may map his account as well-wisher of the customer.
According to an embodiment of the invention, the information module 104 is required to save the information regarding the entity. The information module 104 includes the information of the entity such as, details of the customer, details of the one or more well wishers of the customer, details of the one or more medical facilities, details of the one or more insurance companies, details of the one or more logistic providers and/or the like.
According to another embodiment of the invention, the details of the customer may include personal details, medical history details, insurance details, identification details and/or the like. Further, the personal details of the customer may include name, address, contact number, one or more preferred locations, name of one or more well wishers in case of emergency and/or the like. The insurance details of the customer may include insurance plan, financial coverage of the insurance plan according to the type of casualty and/or the like. The identification details of the customer may include driving license number of the entity, pan card number of the entity, vehicle number of the entity ATM card, club membership card and/or the like. In an embodiment, if the customer hires a cab or uses a vehicle of any family member, friend and/or the like, then the customer is required to provide the respective vehicle number in order to map vehicle to account of customer. Thesystem 100 enhances customer's capability to manage information pertaining to insurance policies and details of all types of investments. The system 100 allows smooth processing of documentation and information access pertaining to insurance and investment details. The system 100 further allows documenting of information like deposit amount, withdrawal amount, deposit date, due date, overdraft facility availability, emergency rollback flexibility, risk factor details, nominee details and like information. Further the insurance parameters include insurance cover denomination, cover grant terms, casualties covered, diseases covered and like information. The system 100 also allows documenting the description of whereabouts of the paper and digital records pertaining to insurance and investments owned by the customer. The system makes it convenient to make quick decision about managing investments and day to day cash flows for the customer.
According to one or more embodiments of the invention, the details of the one or more well wishers of the customer may include name, address, contact number, preferred locations, preferred budget in case of travelling during the medical emergency of the customer and/or the like. Further, the details of the one or more medical facilities may include medical facility name, route details, details of available doctors, doctor's specializations, available devices and/or instruments, number of beds, efficiency to accommodate emergency wards and operation theatres also, human resource real-time tracking and/or the like. The details of the one or more insurance companies may include name, plans, list of type of casualties each of the insurance companies insures, financial coverage for each type of the casualties and/or the like.
The information module 104 may further include information regarding casualty of the registered customer such as, location of the casualty of the registered customer, type of injury (for example, mental sickness, consciousness, accident and/or the like) and/ or the like. The information module 104 is further connected to an identification module 110, a medical support module 106 and a logistic support module 108 in order to communicate the information to one and/or each of the module in case of the medical emergency of the customer.
According to an embodiment of the invention, the identification module 110 is implemented to identify the identity of registered customer. The identification module 110 utilizes the identification details of the information module 104 in order to identify the identity of the registered customer. The identification module 110 facilitates a customer care executive in identifying the identity of the registered customer. For example, if the customer care executive is informed about a casualty of a customer by an emergency person, then the customer care executive fills up the identification details of the customer in the identification module 110 as provided by the emergency person.
Further, the identification module 110 matches the identification details of the customer with the information in the information module as provided by registered customer during registration 104 and verifies whether the customer is the registered customer or not. Furthermore, if the customer is the registered customer, then the identification module 110 displays the information of the registered customer to the customer care executive. The customer care executive is then required to enter details of the casualty of the registered customer such as, location of the casualty, type of injury to the customer and/ or the like. The details of the casualty are saved in the information module 104.
According to an embodiment of the invention, the medical support module 106 is implemented to support the registered customer in the need of the medical emergency. The medical support module 106 identifies the medical facility nearest to the casualty location on the basis of casualty location and the medical facility information as retrieved from the information module 104. In one embodiment, the medical support module 106 displays the medical facility information to the customer care executive. The customer care executive further informs the emergency person regarding the medical facility information.
In another embodiment, the medical support module 106 communicates information regarding the customer (e.g., location of the casualty, type of injury/sickness, insurance details and/or the like) to the identified medical facility. In yet another embodiment, the medical support module 106 communicates information regarding the customer such as, location of the casualty, location of the medical facility to which the customer is to be admitted or taken, type of injury and/or the like to the logistic module 108.
According to an embodiment of the invention, the logistic module 108 is required to inform and support the well wishers of the customer under the medical emergency. In one embodiment, the logistic module 108 retrieves information regarding the well wishers of the customer from the information module 110 after receiving the information from the medical support module 106. The logistic module 108 further sends an alert to the well wishers of the customer information regarding casualty such as, location of the casualty, injury type and/ or the like via email, SMS,instant messengers, typical messaging system, such as blackberry messaging system, inter-office social network of the one or more well wisher's employer and/or the like.
In another embodiment, the logistic module 108 retrieves information regarding the logistics provider from the information module 110 and sends information regarding the well wisher of the customer such as name of the well wisher, contact number, budget for travelling and/or the like to the logistics provider. The logistics provider then provides the information on travelling options according to the information registered by the well-wisher of the customer. The logistics provider arranges the ticket based on selected option of the well wisher and sends the ticket to the well wisher via any physical means, such as door delivery, any digital means, such as online and/or the like.
FIG. 2 is a flow diagram of a method 200 for illustrating a method of operation of a medical emergency management system, for example, the system 100.The method 200 starts at step 202 and proceeds to step 204, at which a registration of a customer is done. According to an illustrated embodiment, the customer registers with the medical emergency management system, for example, the system 100, in order to attain life supporting help in case of any casualty of the customer. During the registration of the customer with the system 100, the customer is required to fill up details of one or more well-wishers of the customer.
At step 206, registration of one or more well-wishers of the customer is done. In an embodiment, the one or more well-wishers of the customer are required to register with the system 100 and furnish the required information. At step 208, registration of one or more insurance companies is performed. In an embodiment, the customer is required to fill information regarding insurance company with which the customer is insured. In another embodiment, one or more insurance companies may register with the system 100 as an entity.
At step 210, registration of one or more medical facilities is done. In an embodiment, the one or more desired medical facility may register with the system 100 as an entity and to provide medical support during the casualty of the customer. At step 212, registration of one or more logistic providers is done. In an embodiment, one or more desired logistic providers may register with the system 100 as an entity and to provide travelling facilities to the one or more well-wishers of the customer during the casualty of the customer.
At step 214, the customer is identified after meeting any casualty. For example, if the customer meets any casualty, then the customer is identified in order to provide each and every support to the customer. At step 216, medical support to the customer is provided during the casualty and the well-wishers of the customer are informed about the casualty of the customer. The method 200 ends at step 218.
FIG. 3 is a flow diagram of a method 300 for illustrating a method followed by a medical emergency management system, for example, the system 100 after a customer meets any casualty. According to an embodiment, the customer meeting the casualty is referred to as a customer until the customer is identified as a registered customer of the system 100. The method 300 starts at step 302 and proceeds to step 304, at which a customer care executive is called by an emergency person regarding the casualty of the customer. In an embodiment, the emergency person calls a call centre regarding the casualty of the customer. In another embodiment, the customer care executive attends the call of the emergency person. At step 306, calling contact number is identified. In an embodiment, the calling contact number refers to the contact number through which the emergency person calls at the call centre. In another embodiment, IVR (Interactive Voice Response) hardware at the call centre detects the calling contact number and checks whether the calling contact number corresponds to any of the registered customers. If the calling contact number corresponds to any of the registered customers, then record of that customer is displayed in browser of computer screen of the customer care executive. According to an embodiment of the invention, in case the emergency person calls the CCE from his contact number, the CCE asks for contact number of the customer for identification. The emergency person may then provide the contact number of the customer.
According to another embodiment of the invention, the customer has footwear that are embedded with an RFID whose embedded unique digital identification number is sold to the customer along with footwear or the customer can buy an RFID whose embedded unique digital identification number is sold to the customer along with RFID; The customer registers the embedded digital identification number with his account. The emergency person is equipped with RFID sensing and their embedded ID reading device which on switching on detects the RFID ID and thus ultimately the identity of the medical emergency customer at casualty spot. This facility has many benefits because many people can be detected within a short time instant and this arrangement gives user a highly effective and practical advantage even in case of natural calamities as users tend to stay not too distant from their personal belongings like footwear and/or like. The RFID may also be embedded into clothing or hair clips or ornaments or leg bandages or neck bands and/or like devices. The embedding device can be of any wireless technology protocol and technology standard.
At step 308, information regarding the customer is acquired. In an embodiment, the customer care executive acquires information regarding the customer from the emergency person in order to identify the customer. At step 310, the customer is identified as a registered customer. At step 312, one or more well-wishers of the customer are notified regarding the casualty of the customer. In an embodiment, after identifying the customer, the system 100 automatically notifies the one or more well-wishers of the customer regarding casualty of the customer. In another embodiment, the customer provides information regarding the one or more well-wishers and well-wishers that are required to be contacted in case of any emergency. The CCE selectively controls notifications to the individual well wisher (at the time of emergency) on the basis of information provided by the customer.
At step 314, geographical location of the casualty and type of injury to the customer are determined. At step 316, a medical facility located nearest to the casualty location is identified. In an embodiment, one or more medical facilities are automatically displayed on the computer screen of the customer care executive after the customer care executive provides the information about location of the casualty. In another embodiment, the customer care executive determines the medical facility that is nearest to the location of the casualty and suitable for the type of injury of the customer.
At step 318, CCE provides information regarding the identified medical facility and financial coverage of insurance of the customer to the emergency person. The system makes it possible for the emergency person to take calculated financial risk taking which risk might be required for undertaking treatment costing more than the amount covered by insurance covers owned by identified user. At step 320, a transport means is arranged in order to transfer the customer to the identified medical facility. In an embodiment, the customer care executive arranges for the transport means in order to transfer the customer to the identified medical facility. At step 322, a communication is made with the identified medical facility. In an embodiment, the customer care executive communicates with staff and/or doctor of the identified medical facility and sends medical details, insurance details and/or the like. At step 324, communication with one or more well-wishers of the customer is done and the method 300 ends at step 326.
FIG. 4 is a flow diagram of a method 400 for illustrating a method for identifying a customer under the casualty as a registered customer of a medical emergency management system, for example, the system 100. The method 400 starts at a step 402 and proceeds to step 404, at which a contact number of the customer is acquired. According to an embodiment of the invention, emergency person calls to a customer care executive. The customer care executive inquires whether the calling contact number is of the customer or not. In an embodiment, the customer care executive acquires contact number of the customer from the emergency person if the calling contact number is not related to the customer.
At step 406, a determination is made whether the acquired contact number of the customer matches with contact number of any of the registered customers. If the determination is made that the acquired contact number matches with the registered customer (option 'YES'), then the method 400 proceeds to step 412. If the determination is made that no contact number of the registered customer is matched with the acquired contact number (option 'NO'), then the method 400 proceeds to step 408.
At the step 408, a determination is made whether the customer was riding a vehicle. If a determination is made that the customer was riding the vehicle (option 'YES'), then the method 400 proceeds to step 410. At the step 410, plate number of the vehicle is acquired. In an embodiment, the emergency person provides the plate number of the vehicle to the customer care executive. If a determination is made that the customer was not riding the vehicle (option 'NO'), then the method 400 proceeds to step 412. At the step 412, registration card number is acquired. In an embodiment, the emergency person provides the registration card number of the customer to the customer care executive.
According to another embodiment of the invention, the customer has a device, which is fixed to any part of a wheeled vehicle, even to a cab that the customer takes on a given day which senses sudden stopping of vehicle by sensing instantaneous velocity of the device at high speed continuously with very small time gaps. The device includes audio recording facility by user. User voice recording ability assures device can spell out user registration information, mobile number or like information, which realises the same effect of emergency management even if accident location does not have communication connectivity. The button press will start playing the recorded message and this setup is configurable by user such that the playback starts either immediately when a jerky stop of vehicle is detected with or without a time delay or only when button pressed as configured by the customer at a given moment on a given day. The device further includes a `stop playing` button and an optical indicator. The device optical indicator activates when a vehicle suddenly decelerates. These facilities makes it possible to avoid user embarrassment that may result due to immediate playback of information as a result of just a sudden break by driver of vehicle and not a result of coming to rest due to accident. User can press the `stop playing` button when optical indicator lights up indicating that jerk has been sensed. The device includes a voice recognition control to supplement the `stop playing` button press process so that the user may relax by communicating with the device by speaking to the device. The device includes a voice control based reacting component attached to this system which makes this device serve the user as stress busting device during driving.
At step 414, customer details of the respective registration card number are displayed on the system 100. According to an embodiment of the invention, the customer care executive enters the registration card number of the customer in a database of the system 100 as provided by the emergency person. Consequently, customer details related to the registration card number are displayed on the system and the customer care executive inquires the emergency person regarding other details of the customer. At step 416, other pre-registered parameters, such as skin tone, facial and body geometry of the customer are matched. The facial and body geometry includes information about structure of face (broad, narrow, oval or the like) or body (tall, short, slim or the like) and any identifying mark on the face and/or body. At step 418, the customer is identified as the registered customer. In an embodiment, if the pre-registered parameters of the customer are matched with the customer, then the customer is identified as the registered customer and thus, the identity of the customer is determined. The method 400 ends at step 420.
FIG. 5 is a flow diagram of a method 500 for illustrating a method for identifying suitable hospital for the customer and directing the customer to the medical facility identified by a medical emergency management system, for example, the system 100. The method 500 starts at a step 502 and proceeds to step 504, at which the customer care executive receives location information of casualty from the EP. At step 506, the customer care executive further receives details of type of injury caused to the customer. During the interaction on call with the EP, the customer care executive asks various pre-documented questions about the customer situation such as cause of the customer casualty, state of the customer and type of the casualty suffered. The EP provides the answers that are further processed by the system 100 in order to determine resources required for the treatment of the customer. The resources include medical devices, hospital infrastructure, medical experts and other resources. According to an embodiment of the invention, the system records the conversation between the CCE and EP for future use.
Further, a 3D animated interface of human body is provided for easier and quicker understanding of injury diagnosis, treatment diagnosis and/or like when patient is on the way. The doctor may find out what type of injury might the patient seems to have undergone internally based on what appears as medical situation of the customer. The doctor may further diagnose what treatment would be perfect applicable treatment to external and internal body parts of customer. The interface makes it easy for the treating doctor and one or more treatment and diagnosis experts to understand the analysis of situation of the customer as perceived by each other. The interface may further allow to diagnose the probable best fit treatment for the customer thereby making best use of available precious time.
At step 508, based on the location information, the CCE retrieves a list of medical facilities. At step 510, the customer care executive enquires the medical facilities regarding the resources such as path to the medical facility,details of doctors available, doctor's specializations, available devices, bed counts, capability to accommodate emergency wards, human resource real-time tracking and/or like. In another embodiment, the customer care executes the conversation between the CCE and EP in a conference call at the reception of all nearby medical facilities. The medical facilities provide the voice feedback to the CCE about resources available. In another embodiment, the CCE may access and use pre-documented information (information collected during the time of registration) about the resources available in the medical facility.
At step 512, the CCE identify best suited medical facility based on location and resources information. Once the best fit and nearest medical facility is identified, at step 514, the customer care executive transmits the customer information to the medical facility.The medical facility receives the detailed information about the insurance details such as cashless facility, insurance amount available and the like of the customer. The medical facility further receives medical history and blood group information from the CCE. According to another embodiment of the present invention, doctors may access medical records of the customer only when an access key is provided by the well-wisher. The access key is available to the well-wisher in case the user has indicated during registration. Further, sensitive medical records may not be shared to any doctor except family doctor. The family doctor may provide the medical records to the doctor of the medical facility. The medical facility sends an ambulance to the casualty location as soon as the alert is received from the system. At step 516, the CCE provides information of the duration required for the customer to reach medical facility. Further, the system allows real time telephonic conference to be created between the doctor of the identified medical facility and the emergency person. The emergency person can describe condition of the customer.
According to another embodiment of the invention, aportable device is provided for the medical facility staff and travel agents to make human resource tracking and active travel agent tracking possible. The portable device that is connected to a centralised information management system customised for the purpose of managing the information furnished by the medical facility staff and travel agents makes it possible to track information provided by the medical facility staff and travel facilitators regarding their geographical location, their availability at pre-named locations (like the medical facility lobby, the medical facility eatery, specific named hotel's reception 'and like'), physical preparedness (whether they are too tired for attending), time wise readiness in offering service 'and like' information This portable device also facilitates documentation of private (access restricted) content describing the aspects reasoning their availability at the medical facility, non availability of various treatment resources and like information which makes it possible for specific set of people to precisely decide upon availability of each of all the resources (resources including human resource, treatment device and like) for treatment of the medical emergency occurred in and around the medical facility. This makes it possible to precisely decide the perfect fit medical facility which can deliver the treatment harnessing all the resources which were considered to be available during the perfect fit medical facility decision making.
Moreover, if the emergency person carries a mobile phone with 3G, 4G facilities or the like, the real-time video of the customer is displayed to the doctor. Further, according to one embodiment of the invention, the CCE avails the facility ofnon-paid and paid volunteers (nearest to casualty spot) if the customer has registered for the facility during the registration. The volunteer has at least quite a good knowledge about how to handle the emergency situation.The method 500 ends at step 518.
FIG. 6 is a flow diagram of a method 600 for illustrating a method of communication between logistic provider and one or more well-wishers of a customer of the system 100. The method 600 starts at step 602 and proceeds to step 604, at which a logistics provider is notified regarding an emergency situation of a customer. The logistics provider is notified in order to provide travelling arrangements for the well-wisher of the customer. In an embodiment, the logistic module 108 of the system alerts the logistics provider regarding casualty of the customer. At step 606, information regarding one or more well-wishers of the customer is provided to the logistics provider. In an embodiment, the logistic module 108 communicates information regarding the one or more well-wishers of the customer to the logistics provider. In another embodiment, the logistic module 108 communicates information, such as location of the casualty, travelling budget of the one or more well-wishers of the customer, location of a medical facility to which the customer is taken or admitted and the like.
At step 608, information regarding travelling options is provided. In an embodiment, the logistics provider looks for one or more travelling options after receiving the alert from the logistic module. In another embodiment, the search for the travelling options depends on the travelling budget of the one or more well-wishers of the customer. In yet another embodiment, information regarding the travelling budget is filled up during registration of the one or more well-wishers of the customer.
According to another embodiment of the invention, the system 100 allows the well-wisher to pre-document travel facility requirements from all desired combinations of means of travel, travel comfort level, various possible travel departure and arrival location wise and travel departure and arrival time of the day wise and which day of the week wise including interconnecting travel facility requirement documentation with each of these possibilities based on travel cost ranges. The system allows travel details requirement of the well-wisher to be visible to all or selected travel facilitators. This system allows travel facilitator to document all possible travel facilities which can be offered for each of all combinations of travel requirement parameters documented (or demanded) by the well-wisher. The system 100 provides a dashboard for the well-wisher to filter specific offered travel facilities by all the travel facilitators by selecting desired values for each of all the travel requirement parameters. User can finalise one or more offered travel facilities. Travel facilitator will have a dashboard for viewing the entire finalised travel requirement by all the travel facility seekers, arrange the facilities and update the status of finalisation of offering of finalised travel requirements by the well-wisher. The well-wisher will have another dashboard, which conveys each of the details of reserved facility status including requested facility details, travel facilitator contact details, travel pickup and drop destinations, interconnecting travel facility details and like.
At step 610, an appropriate travelling option is selected. In an embodiment, the one or more well-wishers of the customer selects appropriate travelling option in order to reach the location of the medical facility or the casualty. At step 612, selected travelling means for the one or more well-wishers are reserved. In an embodiment, the logistics provider reserves the travelling options as selected by the one or more well-wishers of the customer. In another embodiment, the one or more well-wishers of the customer may decide to opt for another logistic provider and inform a customer care executive regarding the same. Further, the customer care executive contacts the logistics provider in order to inform the logistics provider regarding cancelling or halting reservation of the travelling option.
At step 614, a communication with the one or more well-wishers of the customer regarding reserved travelling arrangements is done. In an embodiment, the logistics provider may send a ticket to the one or more well-wishers of the customer via online, door delivery or any physical or digital means. In another embodiment, the logistics provider may inform the one or more well-wishers of the customer regarding details of a cab, a taxi, name, contact number, and/or the like of a driver, and/or the like. The method 600 ends at step 616.
The aforementioned versions of the subject matter and equivalent thereof have many advantages, including those that are described below.
The advantage of the present subject matter is that the present invention providesan automated online emergency management system portal. The system effectively manages the critical available time during a casualty of the customer to reach the hospital and notifying well-wishers about the casualty. Further, the system reduces the number of deaths due to casualties.
Although the subject matter has been described with reference to specific embodiments, this description is not meant to be construed in a limiting sense. Various modifications of the disclosed embodiments, as well as alternate embodiments of the subject matter, will become apparent to persons skilled in the art upon reference to the description of the subject matter. It is therefore contemplated that such modifications can be made without departing from the spirit or scope of the present subject matter as defined.

Claims (17)

  1. A system for delivering information of a registered customer across a network to manage an emergency situation, the system comprising:
    an information module, wherein said information module includes emergency information of said registered customer;
    an identification module for identifying said customer based on identity information of said customer provided by an emergency person at a time of an emergency;
    a medical support module for providing medical facility information to said emergency person based on casualty location information of said customer; and
    a logistics module for communicating filtered travelling information to at least one well-wisher of said customer;
    wherein information module communicates with said medical support module and said logistics module in order to provide emergency support to said customer.
  2. The system as claimed in claim 1, wherein said information module includes a registration module for registering at least one set of entities, wherein each set of entities provide entity specific information.
  3. The system as claimed in claim 1, wherein said entity includes a hospital, a travel agent, a volunteer, customer and/or the like.
  4. The system as claimed in claim 1, wherein said logistics module provides online login facility for said at least one well-wisher.
  5. The system as claimed in claim 1, wherein said well-wisher accesses information of emergency support provided to said customer via online login facility.
  6. The system as claimed in claim 1, wherein said medical support module communicates with said information module to retrieve a list of medical facilities.
  7. The system as claimed in claim 1, wherein said medical support module communicates with said medical facilities and/or said information module to retrieve resource information of said medical facilities.
  8. The system as claimed in claim 1 & claim 5, wherein resource information includes path to the medical facility, details of doctors available, doctor's specializations, available devices, bed counts, capability to accommodate emergency wards, human resource real-time tracking and the like.
  9. The system as claimed in claim 1, wherein said identity information of said customer includes a contact number, a driving license number, a pan card Number, a vehicle number and/or the like.
  10. The system as claimed in claim 1, wherein said emergency information includes identity information and contact information of said customer, insurance details of said customer, name, address, preferred locations, contact information of said at least one well-wisher, and/or the like.
  11. The system as claimed in the claim 1 and claim 8, wherein the insurance details include name of an insurance company, insurance coverage for each type of casualty, cashless facility and/or like.
  12. The system as claimed in claim 1, wherein medical facility information includes a list of one or more medical facilities, medical centre, dispensary and/or the like based on said casualty location information.
  13. The system as claimed in claim 1, wherein an alert is transmitted to said volunteer, wherein said volunteer is equipped with wireless communication device for interacting with said medical facility.
  14. The system as claimed in claim 1, wherein providing interaction between a doctor of said identified medical facility and said emergency person or volunteer via said communication device.
  15. The system as claimed in claim 1, wherein medical information of said customer includes insurance details, blood group of said customer, equipments required for treatment of the customer and/or the like.
  16. The system as claimed in the claim 1 wherein travelling information includes a list of reservation options provided by at least one logistic provider based on contact information of said well-wisher and said medical facility.
  17. The system as claimed in claim 1 and claim 6, wherein the travelling information further includes mode of travelling such as flight, train, road and the like.
PCT/IB2011/050692 2010-02-20 2011-02-20 Medical emergency management WO2011101817A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN437CH2010 2010-02-20
IN437/CHE/2010 2010-02-20

Publications (1)

Publication Number Publication Date
WO2011101817A1 true WO2011101817A1 (en) 2011-08-25

Family

ID=44279068

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2011/050692 WO2011101817A1 (en) 2010-02-20 2011-02-20 Medical emergency management

Country Status (1)

Country Link
WO (1) WO2011101817A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6117073A (en) * 1998-03-02 2000-09-12 Jones; Scott J. Integrated emergency medical transportation database system
WO2009077963A2 (en) * 2007-12-16 2009-06-25 Richard Garrick Law Emergency identification
US20090198733A1 (en) * 2008-02-01 2009-08-06 Microsoft Corporation Healthcare resource locator

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6117073A (en) * 1998-03-02 2000-09-12 Jones; Scott J. Integrated emergency medical transportation database system
WO2009077963A2 (en) * 2007-12-16 2009-06-25 Richard Garrick Law Emergency identification
US20090198733A1 (en) * 2008-02-01 2009-08-06 Microsoft Corporation Healthcare resource locator

Similar Documents

Publication Publication Date Title
CN104750997B (en) A kind of diagnosis and treatment follow-up service implementation method based on mobile interchange
US20160117471A1 (en) Medical event lifecycle management
WO2014035182A1 (en) Method and apparatus for personal medical treatment using mobile terminal
KR20170018401A (en) Personal emergency response system with predictive emergency dispatch risk assessment
JP2003109160A (en) Emergency rescue supporting system, portable terminal with emergency rescue function, wireless terminal for receiving emergency rescue information and emergency rescue supporting method
Crawshaw Male coping with cancer-fertility issues: putting the ‘social’into biopsychosocial approaches
CN109767542A (en) Voice guide intelligence wisdom Office visits system and method based on wireless location
CN103942454A (en) Emergency patient emergency rescue system based on mobile monitoring car
JP6869726B2 (en) Emergency information system and emergency information management method
KR20130012286A (en) A first-aid information and emergency medical system using smart device
CN104123818A (en) Health monitoring rescue system and first aid method
KR102453879B1 (en) Companion matching service and companion matching system
CN110265154A (en) A kind of Internet-based 120 cooperate with savng system and implementation method
CN108091374A (en) A kind of bedside informationization interactive system
WO2007104007A2 (en) Patient discharge system and associated methods
CN112509681A (en) Intelligent medical service system based on big data
KR101100658B1 (en) Therapeutic autologous-cell delivery support system, and method therefor
JP2017073013A (en) Inter-clinic cooperation method and computer program for inter-clinic cooperation
CN116862031A (en) Bed reservation system
WO2011101817A1 (en) Medical emergency management
CN112397182A (en) System, subsystem, method and storage medium for emergency alert and alarm receiving
KR20060009070A (en) System for handling the state of emergency based on the on-line network
WO2014037038A1 (en) Instant aid
Holtmann et al. Medical opportunities by mobile IT usage–a case study in the stroke chain of survival
KR20110050118A (en) System for servicing of medical appointment and examination in remote and method thereof

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11730429

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11730429

Country of ref document: EP

Kind code of ref document: A1