JP2017034361A - Rescue request support apparatus, operation method thereof, program, and system - Google Patents

Abstract

To provide a rescue request support device, method, program, and system capable of prompting a medical worker to rescue more quickly at the current position of a rescuer. A rescue request support server 14 acquires position information, creates and distributes map information. In the position information acquisition, position information indicating the current position is acquired from the portable terminal 11 carried by the rescuer P1 and the portable terminal 12 carried by the rescuer P2. Based on the position information of the portable terminals 11 and 12, map information 49 for mapping the current positions of the rescuer P1 and the rescuer P2 is created. The map information 49 displays a medical worker mark 66M indicating whether or not the rescuer P2 is a medical worker based on the user information. The map information 49 is distributed to the portable terminal 12 of the rescuer P2. It can be determined from the medical worker mark 66M whether or not the rescuer P2 includes a medical worker. If there are no medical workers, further rescue requests can be made, and rescue in the event of an emergency can be made reliably. [Selection] Figure 1

Description

  The present invention relates to a rescue request support apparatus, an operation method thereof, a program, and a system.

  A rescue request support system that supports a user's rescue request when an emergency situation such as a sudden illness occurs in the user and the user becomes a rescuer is known (for example, described in Patent Document 1). Health management device with emergency call and service providing method described in Patent Document 2). Such a system allows emergency rescue by a person in the vicinity of the person in need of help until a specialized ambulance arrives.

  The life-saving emergency assistance system described in Patent Document 1 is a third party (doctor, nursing) that is suitable for the rescue of a user whose life-saving emergency assistance device is in the vicinity of the user when a physical condition abnormality occurs in the user and a life-saving emergency action is required. The lifesaving instruction information is transmitted to the third party terminal device (paragraph 0011). Further, when selecting a third party appropriate for user rescue, medical personnel such as doctors and nurses capable of medical practice are selected from the registered information of the user (paragraph 0025).

  In the rescue system described in Patent Document 2, the server receives safety information from the rescueee's terminal (paragraph 0030). The rescue system that has received the safety information has a function of transmitting to the rescuer's terminal heading for the rescuer's rescue as a map display including the positions of the rescuer and the rescued persons ( Paragraph 0036).

JP 2012-222443 A JP 2014-089543 A

  In the case of rescue, it is more likely that more than one person cooperates and rescues more quickly and more appropriately than one person alone. If there is a medical worker among rescuers, it is possible to perform more appropriate rescue. Further, if there are a plurality of rescuers, each rescuer can feel reassured that the rescuer is not alone.

  As described above, in the case where a plurality of people cooperate to rescue, the technology of Patent Document 1 in which the server selects a medical worker and requests rescue, and the positions of a plurality of rescuers heading for rescue are displayed on a map. The technique of Patent Document 2 that can be grasped is useful.

  However, there was room for further improvement to ensure quick and appropriate rescue. This is because even if a medical worker makes a rescue request as in Patent Document 1, the medical worker may not actually accept the rescue request. In that case, the server will search for another medical worker, but there is no appropriate medical worker among the pre-registered users, or the server will have time to search for another medical worker. May be required. For this reason, there has been a demand for a technique for prompting medical staff to rescue more quickly.

  An object of the present invention is to provide a rescue request support apparatus, an operation method thereof, a program, and a system capable of causing a medical worker to go to rescue more quickly at the current position of a rescuer.

  In order to achieve the above object, a rescue request support apparatus of the present invention includes a position information acquisition unit, a map information creation unit, and a map information distribution unit. The location information acquisition unit obtains location information indicating the current location of the rescuer and the rescuer from the portable terminals carried by the rescuer who requested the rescue and the rescuer who received the rescue request of the rescuer. get. The map information creation unit creates map information that maps the current position of the rescuer and the rescuer. In the map information, an identification mark indicating whether or not the rescuer is a medical worker is displayed based on registered information registered in advance. The map information distribution unit distributes the map information to the rescuer's mobile terminal.

  The medical staff is preferably a doctor, a nurse, or a paramedic, and the identification mark is preferably a mark that identifies the doctor, nurse, or paramedic. In this case, it is possible not only to be a medical worker but also to know the occupation, so it is possible to newly request a doctor with a higher treatment level as a rescuer according to the condition of the rescuer. Become.

  In the map information, when the display of the current positions of a plurality of rescuers overlaps, it is preferable that the rescuer who is a medical worker is preferentially displayed. In this case, when a plurality of rescuers are displayed in an overlapping manner, the presence or absence of a medical worker can be surely determined.

  It is preferable that the position information acquisition unit acquires the position information of all users based on information from a mobile terminal that is carried by a user registered in advance. Furthermore, it is preferable to provide a rescuer selection unit and a rescue request notification transmission unit. A rescuer selection part selects a rescuer from a user based on the present position of a rescuer. The rescue request notification transmission unit transmits a rescue request notification to the selected rescuer. In this case, a user near the rescuer can be selected.

  It is preferable that the map information distribution unit distributes the map information to the transmission destination of the rescue request notification.

  The rescuer selection unit sets the first area as the search area and performs the first selection. When a medical worker is not included in the rescuer in this first selection, it is preferable to set the second area wider than the first area as the search area and perform the second selection. In this case, the possibility of finding a medical worker increases. For example, the area is set to be within walking distance for the first time and to a range where the vehicle can be moved within a predetermined time for the second time.

  It is preferable to include a determination unit that determines whether or not the rescuer who has notified the rescue request is moving toward the current position of the rescuer. By providing the determination unit, it can be determined whether or not the rescuer who has requested the rescue is actually heading, and is effective in determining whether or not a re-request is necessary. In particular, it is very effective because it is possible to grasp whether or not a medical worker who has made a rescue request is heading.

  In the map information, when there is a medical worker among the rescuers determined not to go to the current position of the rescuer, it is preferable to resend a rescue request notification to the medical worker. . In this case, it is possible to request the medical staff again.

  In the map information, it is preferable that the rescuer determined to be approaching the current position of the rescuer and the rescuer determined to be not directed to the current position of the rescuer are preferably displayed in an identifiable manner. In this case, it is easy to confirm whether or not the vehicle is heading for rescue.

  Furthermore, it is preferable to provide a communication function that enables communication between a plurality of rescuers. In this case, cooperation of a plurality of rescuers can be easily obtained. Thereby, for example, it is possible to contact an arbitrary rescuer displayed on the screen, and for example, it is possible to request materials necessary for rescue such as AED.

  The operation method of the rescue request support apparatus of the present invention causes the rescue request support apparatus to execute a position information acquisition step, a map information creation step, and a map information distribution step. In the location information acquisition step, location information indicating the current location of the rescuer and the rescuer is obtained from the portable terminal carried by each of the rescuer who requested the rescue and the rescuer who received the rescue request of the rescuer. get. The map information creation step creates map information that maps the current position of the rescuer and the rescuer. In the map information, an identification mark indicating whether or not the rescuer is a medical worker is displayed based on registered information registered in advance. In the map information distribution step, the map information is distributed to the rescuer's mobile terminal.

  The rescue request support program of the present invention causes a computer to execute a position information acquisition step, a map information creation step, and a map information distribution step. In the location information acquisition step, location information indicating the current location of the rescuer and the rescuer is obtained from the portable terminal carried by each of the rescuer who requested the rescue and the rescuer who received the rescue request of the rescuer. get. The map information creation step creates map information that maps the current position of the rescuer and the rescuer. In the map information, an identification mark indicating whether or not the rescuer is a medical worker is displayed based on registered information registered in advance. In the map information distribution step, the map information is distributed to the rescuer's mobile terminal.

  The rescue request support system according to the present invention includes a rescue request support system including a portable terminal carried by each rescuer who has received a rescue request and a rescuer who has received a rescue request from the rescuer, and a rescue request support device. The rescue request support apparatus includes a position information acquisition unit, a map information creation unit, and a map information distribution unit. The position information acquisition unit acquires position information indicating the current position of the rescuer and the rescuer from the mobile terminal. The map information creation unit creates map information that maps the current position of the rescuer and the rescuer. In the map information, an identification mark indicating whether or not the rescuer is a medical worker is displayed based on registered information registered in advance. The map information distribution unit distributes the map information to the rescuer's mobile terminal.

  ADVANTAGE OF THE INVENTION According to this invention, the rescue request assistance apparatus, method, program, and system which can make a medical worker aim for rescue more quickly to the present position of a rescuer required can be provided.

It is explanatory drawing of the rescue request assistance system which consists of a portable terminal and a rescue request assistance server. It is a block diagram which shows schematic structure of a computer. It is a functional block diagram of a portable terminal. It is explanatory drawing which shows the transition of the operation screen of a portable terminal. It is a functional block diagram of a rescue request support server. It is explanatory drawing which shows an example of the map information of a rescue request. It is explanatory drawing which shows an example of a rescue request notification screen. It is a flowchart which shows the whole process of a rescue request assistance system. It is explanatory drawing which shows an example of the rescue request notification when there is no medical worker in a rescuer. It is explanatory drawing of 2nd Embodiment which searches a medical worker by expanding an area sequentially. It is explanatory drawing which shows an example of the rescue request notification which has the button of the will display confirmation whether rescue is possible. It is a flowchart which shows the process in the example which changes the display color of a rescuer mark by the will display confirmation whether rescue is possible. It is a flowchart which shows the process in the example which determines whether it is heading for rescue based on the moving direction of a rescuer, and changes the display color of a rescuer mark. It is explanatory drawing which shows an example of the map information which displays whether a rescuer is going to rescue using the arrow which shows a moving direction. 10 is a flowchart of another embodiment for resending a rescue request notification when there is a medical worker who is not going to rescue; It is explanatory drawing which shows an example of the map information of another embodiment which contacts between rescuers. It is explanatory drawing which shows an example of the map information which preferentially displays a medical worker when a plurality of rescuers are displayed in an overlapping manner. It is explanatory drawing which shows an example of the map information which displays a medical worker according to occupation. It is explanatory drawing which shows the modification of map information which operates a rescuer mark and displays prescription medicine, a hospital visit destination, etc. It is a flowchart which shows the modification which acquires the present location information of the portable terminal of all the users at the stage of receiving a rescue request, and selects a rescuer.

[First Embodiment]
As shown in FIG. 1, the rescue request support system 10 includes a rescue request support server (rescue request support device) 14 that can communicate with the mobile terminals 11 and 12. The rescue request support server 14 provides an application service for rescue request support to the user registered in advance via the network 16.

  The user registered in advance is a user who owns the mobile terminals 11 and 12 and a user who has registered for use of an application service provided by the rescue request support server 14. The rescue request support application service is a service that allows a rescue request notification to be transmitted to another user near the user when an emergency occurs.

  Specifically, when an emergency situation occurs in a user and the user or a person in the vicinity issues a rescue request and becomes a rescuer P1, the rescuer P1 is required to carry the mobile phone held by the rescuer P1. A rescue request request is transmitted from the terminal 11 to the rescue request support server 14. Upon receiving the rescue request request, the rescue request support server 14 selects another user near the current position of the rescuer P1 as the rescuer P2 from the users other than the rescuer P1, and sends a rescue request notification. Send. Here, an emergency situation refers to a case where a physical condition change or injury has occurred in a user due to a sudden chronic seizure or accident. The rescuer P2 is a person who has received a rescue request from the rescuer P1.

  When the rescue terminal P2 mobile terminal 12 receives the rescue request notification, the rescue request notification screen 36 is displayed on the mobile terminal 12. The rescue request notification screen 36 includes a message including the request for rescue of the rescue requester P1, requesting rescue of a person near the rescue requester P1, and the current position of the rescue requester P1. The current position is displayed in the form of map information 49 in addition to the text address display.

  In addition, when the rescue request support server 14 receives a rescue request request from a user, in addition to sending a rescue request notification to another user, the rescue request support server 14 makes an emergency call to the fire department command center and engages in medical care. An emergency call service may be provided to request the dispatch of an ambulance team.

  In addition to the emergency call service, the benefits of providing rescue request support application services are as follows. That is, even if an emergency call is made, it takes time for the emergency team to arrive at the scene if the fire department where the emergency team is dispatched is away from the current position of the rescuer P1. Therefore, by using the application service provided by the rescue request support server 14, a rescue request is made to a user near the rescuer P 1, so that the rescuer P 2 can quickly respond until the emergency team arrives. Rescue is possible. Further, even when the rescue request support server 14 does not provide a service for making an emergency call to the fire department command center, it is possible to have the rescuer P2 who has received the rescue request notification arrange an emergency call or a medical worker. Become.

  Note that the user has the potential to become a rescuer P1 or a rescuer P2 potentially. In some cases, the owner of the portable terminal 11 becomes the rescuer P2 or the owner of the portable terminal 12 becomes the rescuer P1. However, in this example, a user who owns the portable terminal 11 is necessary for convenience of explanation. An example will be described in which the user who becomes the rescuer P1 and who owns the portable terminal 12 becomes the rescuer P2.

  The portable terminals 11 and 12 are constituted by small computers, for example. The general configuration of a general computer is as shown in FIG. 2, and the basic configuration of the mobile terminals 11 and 12 is the same. As shown in FIG. 2, the computer includes a CPU (Central Processing Unit) 21, a memory 22, a storage device 23, a communication I / F 24, and an input / output unit 26. These are connected via a data bus 27. The input / output unit 26 includes a display 28 and an input device 29 such as operation keys. The display 28 is, for example, a touch panel display, and the display 28 also functions as the input device 29.

  The storage device 23 is, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and stores a control program and an application program (hereinafter referred to as AP) 30. In the case of the portable terminals 11 and 12, the storage device 23 is, for example, an SSD.

  The memory 22 is a work memory for the CPU 21 to execute processing, and includes a RAM (Random Access Memory). The CPU 21 loads the control program stored in the storage device 23 into the memory 22 and executes processing according to the program, thereby comprehensively controlling each part of the computer.

  The communication I / F 24 is a network interface that performs transmission control with the network 16. In the case of the portable terminals 11 and 12, the communication I / F 24 is, for example, a wireless communication module, and the network 16 is a mobile communication network, a wireless LAN, or the like.

  As shown in FIG. 3, a rescue request support AP 30 is installed in the mobile terminals 11 and 12 as an AP 30 for using the application service of the rescue request support server 14. The rescue request support AP 30 is a program that realizes both a function of transmitting a rescue request request as the portable terminal 11 of the rescuer P1 and a function of receiving a rescue request notification as the portable terminal 12 of the rescuer P2. Therefore, in the following, the functions realized by the rescue request support AP 30 will be described together without distinguishing between the mobile terminals 11 and 12.

  Here, in order to distinguish the configuration of the computer used for the portable terminals 11 and 12 from the configuration of the computer of the rescue request support server 14 described later (see FIG. 5), for the convenience of explanation, for example, CPU 21A, The numerical symbol is indicated with an English letter “A”.

  The rescue request support AP 30 </ b> A can be downloaded in response to provision from, for example, a company that operates the rescue request support server 14. When the rescue request support AP 30A is executed after the download, the CPU 21A of the mobile terminals 11 and 12 functions as a GUI (Graphical User Interface) control unit 32, a setting unit 33, a rescue request transmission / reception unit 34, and a location information acquisition unit 35. To do. By linking these units, the mobile terminals 11 and 12 can use an application service for rescue request support. Specifically, it is possible to set user information necessary for using the service, transmit a rescue request request to the rescue request support server 14, receive a rescue request notification from the rescue request support server 14, and the like.

  As shown in FIG. 3, the GUI control unit 32 displays an operation screen on the display 28A, and accepts various operation instructions through the operation screen. The setting unit 33 executes a registration process for the user information 48 input via the GUI control unit 32. After the user information 48 is stored in the storage device 23 </ b> A, it is transmitted to the rescue request support server 14 and registered in the rescue request support server 14. At this time, a user ID is issued from the rescue request support server 14. The issued user ID is recorded in the user information 48. When communication is performed between the registered mobile terminals 11 and 12 of the user and the rescue request support server 14, the user ID is transmitted from each of the mobile terminals 11 and 12 to the rescue request support server 14. Based on the user ID, the rescue request support server 14 identifies the user.

  As shown in FIG. 4, the operation screen controlled by the GUI control unit 32 includes, for example, an initial screen 50, a startup screen 52, a setting registration screen 56, and the like. On the initial screen 50, icons 51 of various applications such as mail, browser, calendar, and map are displayed. When the rescue request support AP 30A is installed, an icon 51 for starting the rescue request support AP 30A is displayed as one of the icons 51. When the icon 51 is operated on the initial screen 50, the screen transitions from the initial screen 50 to the activation screen 52 of the rescue request support AP 30A.

  The start screen 52 is provided with a setting button 53 and a rescue request button 54. When the setting button 53 is operated on the startup screen 52, a setting registration screen 56 is displayed. On the setting registration screen 56, a message for prompting input of user information is displayed, and an input field H1 for inputting user information and a registration button 57 for executing registration of the input user information to the rescue request support server 14 are provided. Is provided.

  When inputting in the input field H1, a character input pad such as a numeric keypad or alphanumeric characters is partially displayed (not shown) on the screen, and user information can be input. Items of user information to be registered include name, gender, age, mobile phone number, e-mail address, occupation, information on whether or not he / she is a medical worker, information on acceptability of rescue request, etc. It is divided into. The information on whether or not the person is a medical worker is information on whether or not the occupation is a medical worker such as a doctor or a nurse. The information on whether or not the rescue request is accepted is information indicating the user's intention as to whether or not it is possible to act as the rescuer P2 when there is a rescue request. A user whose information on whether or not the rescue request is accepted is “No” is excluded from the rescue request notification.

  The setting unit 33 receives user information input through the setting registration screen 56 and stores the user information 48 in the storage device 23A. When the registration button 57 is operated, the setting unit 33 reads the user information 48 in the storage device 23 </ b> A and transmits a registration request for the user information 48 to the rescue request support server 14. In this way, the user information 48 is registered from the portable terminals 11 and 12 to the rescue request support server 14.

  On the startup screen 52, a rescue request button 54 is an operation button that commands transmission of a rescue request request. When the rescue request button 54 is operated, an operation instruction is input to the rescue request transmission / reception unit 34 via the GUI control unit 32.

  In FIG. 3, the rescue request transmission / reception unit 34 performs a process of transmitting a rescue request request based on the operation of the rescue request button 54. In addition, the rescue request transmission / reception unit 34 receives a rescue request notification from the rescue request support server 14. When receiving the rescue request notification, the GUI control unit 32 displays the rescue request notification screen 36 on the display 28A.

  The position information acquisition unit 35 acquires position information indicating the current positions of the mobile terminals 11 and 12 by a GPS method, a base station method, or the like. The position information acquisition unit 35 periodically transmits the position information of the mobile terminals 11 and 12 to the rescue request support server 14. Transmission / reception of information such as a rescue request request, a rescue request notification, position information, and user information 48 to / from the rescue request support server 14 is performed via the communication I / F 24 </ b> A and the network 16.

  The rescue request support server 14 is also a computer, and its basic configuration is as shown in FIG. As shown in FIG. 5, a rescue request support server program 30 </ b> B is stored in the storage device 23 </ b> B of the rescue request support server 14. When the rescue request support server program 30 </ b> B is executed, the CPU 21 </ b> B of the rescue request support server 14 serves as a request reception unit 41, a rescue request notification transmission unit 42, a registration unit 43, a location information acquisition unit 44, and a map information creation unit 46. Function. Here, for the convenience of explanation, the configuration of the CPU of the rescue request support server 14 is distinguished from the configuration of the CPU of the mobile terminals 11 and 12 (the numerals are suffixed with “A”). Append “B” to the sign of the number.

  The request receiving unit 41 receives a rescue request request and a registration request from the mobile terminals 11 and 12 and gives instructions to each unit according to the received request.

  The registration unit 43 assigns a user ID to the user information 48 included in the registration request based on the registration request from the mobile terminals 11 and 12 and records the user information 48 in the registration information 58 stored in the storage device 23B. The registration information 58 is a summary of user information 48 (name, gender, age, mobile phone number, occupation, whether or not a medical worker is accepted, information on whether or not a rescue request is accepted) to which a user ID is assigned. Information.

  As described above, the information indicating whether or not the rescue request can be accepted is set to “permitted” for the user who accepts the rescue request notification and becomes the rescuer P2, and “impossible” for the user who does not accept the rescue request. In this example, “impossible” is set for a user whose user ID is “004”, and “possible” is set for other users.

  The position information acquisition unit 44 acquires position information transmitted from the mobile terminals 11 and 12 periodically. The position information acquisition unit 44 stores the acquired position information in the current position table 45 for each user ID. In this example, the acquisition interval of the position information from each portable terminal 11 and 12 is, for example, 30 seconds. In addition to the latest position information, the current position table 45 records position data up to a predetermined time, for example, 5 minutes before. Thereby, in 3rd Embodiment mentioned later, the moving direction of each portable terminal 12 can be grasped | ascertained now.

  When the request receiving unit 41 receives a rescue request request, the map information creating unit 46 creates the map information 49 shown in FIG. 6 in which the current positions of the rescuer P1 and the rescuer P2 are mapped. The rescue request notification transmission unit 42 transmits a rescue request notification including the map information 49. Thereby, the map information 49 is distributed to the transmission destination of the rescue request notification. The rescue request notification transmission unit 42 functions as a map information distribution unit.

  As shown in FIG. 6, the map information 49 displays, for example, a map of a predetermined area centered on the current position of the rescuer P1, and the current positions of the rescuer P1 and the rescuer P2 on the map. A mark indicating that is mapped.

  The current position of the rescue requester P1 is displayed with the rescue requester mark 65, and the rescuer P2 is displayed with the rescuer mark 66. In this example, a “x” mark is assigned as the form of the rescuer required mark 65, and a “◯” mark is assigned as the form of the rescuer mark 66.

  Further, in the map information 49, an identification mark indicating whether or not the rescuer P2 is a medical worker is displayed. In this example, the identification mark indicating whether or not a medical worker is a medical worker mark 66M indicating that he is a medical worker for the rescuer P2 who is the medical worker among the rescuers P2. It is displayed by giving. The medical worker mark 66M is a form in which the letter “M” is inserted in the “◯” mark of the rescuer mark 66. Whether or not the rescuer P2 is a medical worker can be identified by the presence or absence of the letter “M”.

  In addition, the map information 49 displays a personal mark 66S indicating the recipient himself / herself who has received the rescue request notification including the map information 49 at the mobile terminal 12. Since the recipient himself / herself is also the rescuer P2, the identity mark 66S is in the form of a double circle “◎” in which a small “◯” mark is added to the “◯” mark of the rescuer mark 66.

  The map information 49 includes a rescuer required mark 65 (“×”), a rescuer mark 66 (“◯”), a medical worker mark 66M (“letter M”), and an individual mark 66S (“◎ Two A legend that describes what each mark of “Shigemaru”) indicates. Also, as a description of the mark on the map, a character display “rescuer required” is inserted in the vicinity of the rescue requester mark 65, and a character display “your current position” is inserted in the vicinity of the principal mark 68. It is possible to confirm what each mark on the map indicates by such legend and character display.

  For example, the map information creation unit 46 creates the map information 49 as follows. First, when the request receiving unit 41 receives a rescue request, the map information creating unit 46 reads the current location of the rescue requester P1 from the current location table 45. And the map information preparation part 46 selects rescuer P2 from the user registered previously based on the present position of rescuer P1 required. As the rescuer P2, a user near the rescuer P1 is selected.

  Specifically, the map information creation unit 46 sets a range of a predetermined distance from the current position of the rescue requester P1 as a search area. As the range of the predetermined distance, for example, a range having a radius of 400 m (approximately within a 5-minute walk) from the current position of the rescue requester P1 is set. Then, referring to the current position of the user recorded in the current position table 45, the current position searches for a user in the search area. Furthermore, among the users in the search area, the registration information 58 is referred to, and the user whose information on whether or not the rescue request is accepted is “No” is excluded. The user thus extracted is selected as the rescuer P2. Thus, the map information creation unit 46 functions as a rescuer selection unit.

  After selecting the rescuer P2, the map information creation unit 46 acquires map data in an area within a predetermined range centering on the current position of the rescuer P1 from a map server (not shown). In the map data, position information such as GPS information is associated with each point on the map. The map information creation unit 46 maps the current positions of the rescue requester P1 and the rescuer P2 by the rescue requester mark 65 and the rescuer mark 66. Furthermore, referring to the registration information 58, when there is a medical worker in the rescuer P2, a medical worker mark 67 is added to the rescuer P2.

  The rescue request notification transmission unit 42 includes the map information 49 created by the map information creation unit 46 in the rescue request notification and distributes it to the portable terminal 12 of the rescuer P2. The rescue request notification is displayed on the portable terminal 12 as a rescue request notification screen 36 as shown in FIG.

  Since the rescue request notification is distributed to the mobile terminal 12, the rescue request notification transmission unit 42 creates the rescue request notification in a data format suitable for distribution. As a data format suitable for distribution, for example, a format using a general markup language as a WEB page creation language such as XML (Extensible Markup Language).

  The XML data includes a command for reproducing the map information 49, correspondence information between the position on the map and the current positions of the rescuer P1 and the rescuer P2, and the location of the data serving as the material of the map information 49 (Uniform Resource Locator) is described. When the mobile terminal 12 receives the XML data, the browser software interprets the XML data and reproduces the map information 49. The reproduced map information 49 is displayed on the display 28A.

  The data format of the map information 49 is an example, and the map information creation unit 46 may create the map information 49 as image data in, for example, a PDF (Portable Document Format) format and distribute it. .

  In addition, the rescue request notification transmission unit 42 distributes update information to the mobile terminal 12 of the rescuer P2 as needed when the map information 49 needs to be updated, such as when the current position of the rescuer P1 changes. To do. The mobile terminal 12 updates the map information 49 being displayed on the display 28A based on the update information.

  Hereinafter, the operation of the above configuration will be described with reference to the flowchart of FIG. In the rescue request support server 14, user information 48 of the mobile terminals 11 and 12 is registered, and registration information 58 is stored. As the location information acquisition step, the rescue request support server 14 periodically acquires location information from the registered mobile terminals 11 and 12 of the registered user and records it in the current location table 45 (ST10, ST11).

  When an emergency occurs in the user of the portable terminal 11 and the user becomes a rescuer P1, the rescuer P1 activates the rescue request support AP 30 in the portable terminal 11 and starts up as shown in FIG. A rescue request button 54 is operated from the screen 52. Thereby, a rescue request request is transmitted from the portable terminal 11 to the rescue request support server 14 (ST12).

  When the rescue request support server 14 receives the rescue request request (ST13), the rescue request support server 14 selects a rescuer P2 near the rescuer P1 based on the current position of the rescuer P1 (ST14). Then, the map information creation unit 46 creates map information 49 in which the current positions of the rescuer P1 and the rescuer P2 are mapped as a map information creation step (ST15). In the map information 49, the rescuer P2 who is a medical worker includes the medical worker mark 67, so that it is possible to identify whether the rescuer P2 is a medical worker.

  As a map information distribution step, the rescue request support server 14 transmits a rescue request notification including the map information 49 by the rescue request notification transmission unit 42 to the portable terminal 12 of the selected rescuer P2 (ST16). When receiving the rescue request notification (ST17), the portable terminal 12 of the rescuer P2 displays the rescue request notification screen 36 including the map information 49 on the display 28A (ST18). The rescuer P2 who is the user of the mobile terminal 12 can check the current position of the rescuer P1 by looking at the rescue request notification screen 36. Thereby, rescuer P2 can head for rescue of rescuer P1 who needs nearby.

  Further, as shown in FIG. 6, the map information 49 in the rescue request notification screen 36 (see FIG. 1) also displays the rescuer P2 other than the recipient who received the notification by the rescuer mark 66. It can be confirmed how many rescuers P2 are around the rescuer P1. In addition, since the medical worker mark 67 is displayed when the rescuer P2 is a medical worker, it can be confirmed whether or not the medical worker is included in the rescuer P2.

  By indicating whether or not the rescuer P2 is a medical worker in the map information 49, there is the following merit. First, in order to appropriately rescue the rescuer P1, it is desired that a medical worker is present in the rescuer P2. Therefore, when there is no medical worker in the rescuer P2 in the map information 49, it is necessary for the rescuer P2 receiving the rescue request notification to promptly arrange the medical worker. Can understand.

  As a result, each rescuer P2 who has received a rescue request notice gives a strong motivation to take actions such as searching for a medical worker around him or arranging a medical worker by relying on his own personal network. be able to. In addition, if the recipient who has received the rescue request notification is a medical worker, the rescuer P2 will be informed of the current situation that there is no medical worker in the rescuer P2, and the rescue will appeal to the health worker's sense of mission. It can give a strong motivation to go to.

  As described above, even if an emergency call is made, it may take some time for the ambulance team to arrive at the scene if the dispatch location (fire department) of the ambulance team is far from the current location of the rescuer P1. . Further, since the rescue request notification of the rescue request support server 14 is limited to registered users, a rescue request notification is transmitted if there is no medical worker among the users near the rescue requester P1. I can't. Even in such a case, the medical worker mark 67 of the map information 49 informs each rescuer P2 of whether or not there is a medical worker in the rescuer P2 near the rescuer P1 who is in need. Cooperation can be requested regarding the arrangement of workers.

  That is, even if it takes time until the ambulance team arrives, or even if there is no medical worker in the transmission target of the rescue request notification by the rescue request support server 14, each rescuer P2 can help with the arrangement of the medical worker. It becomes possible. Thereby, it becomes possible to make a medical worker go to rescue more quickly to the current position of the rescuer P1.

  In addition, when there is a medical worker in the rescuer P2 in the map information 49, it is considered that each rescuer P2 can easily cooperate by confirming that each rescuer P2. This is because some rescuers P2 feel a psychological burden, such as what they can do and what they can do when they make a decision to rescue the rescuer P1. It is thought that there are many people. In such a case, if it can be confirmed that there is a medical worker in the rescuer P2, for example, the rescuer P2 who is not a medical worker may have something useful under the direction of the medical worker. Can think. For this reason, the psychological burden of the rescuer P2 is reduced, and it becomes easier to make a decision for rescue. As a result, it becomes easy to obtain cooperation of the rescuer P2.

  In this example, the forms of the rescuer required mark 65, the rescuer mark 66, the medical worker mark 67, and the person mark 68 shown in the map information 49 of FIG. 6 are examples, and shapes, colors, patterns, and combinations thereof Various things are possible. Any form is acceptable as long as each can be identified.

  Further, in this example, the map information 49 is distributed to the selected rescuer P2 that is the transmission destination of the rescue request notification. By including the map information 49 in the rescue request notification, it is possible to provide useful information necessary for rescue to the rescuer P2.

  The map information 49 may be viewed by a user other than the transmission destination of the rescue request notification. In this case, for example, when there is a browsing request from the registered user to the rescue request support server 14, the rescue request support server 14 distributes the map information 49 to the user who has requested the browsing. According to this, the map information 49 can be confirmed even by a user outside the search area. If the number of people viewing the map information 49 increases, the possibility that the number of people going to rescue will increase will also increase.

  Further, a message other than the rescue request message MSG1 may be included as in the rescue request notification screen 36 shown in FIG. For example, at the time of notification, if there is a medical worker in the rescuer P2, or if there is a medical worker near the rescuer P2 (the recipient who received the notification) or a medical worker nearby, a rescue request is made. A message MSG2 indicating the request contents to request is included. If it carries out like this, the intention of the cooperation request regarding arrangement | positioning of a medical worker can be clearly told with respect to rescuer P2.

[Second Embodiment]
In the first embodiment, the search area of the rescuer P2 is described as an example in which one range in which the distance from the current position of the rescuer P1 is fixed is set. On the other hand, 2nd Embodiment shown in FIG. 10 is an example which expands a search area in steps, when a medical worker is not found in a search area.

  Specifically, as shown in FIG. 10, in the rescue request support server 14, the map information creation unit 46 (functioning as a rescuer selection unit) determines the rescuer P2's location based on the current location of the rescuer P1. The first area A1 is set as the search area. Then, the registered user in A1 is searched with reference to the current position table 45, and the rescuer P2 is selected for the first time. The map information creation unit 46 selects the searched user as the rescuer P2 regardless of whether or not he / she is a medical worker. Then, with reference to the registration information 58, it is determined whether or not a medical worker is included in the rescuer P2 selected in the first selection.

  If a medical worker is included, the map information creation unit 46 ends the selection of the rescuer P2 at that stage. When a medical worker is not included, a second area A2 wider than the first area A1 is set as a search area, and the second selection is performed. The map information creation unit 46 repeats such a procedure and expands the search area step by step, such as A2, A3, and A4. Thus, possibility that a medical worker can be selected as rescuer P2 increases by expanding a search area in steps. In the example of FIG. 10, since a medical worker exists in the fourth area A4, the expansion of the search area ends in the fourth area A4. Even when a medical worker is not found, the expansion of the search area ends when the preset upper limit value is reached.

  The first area A1 to the fourth area A4 are, for example, in the following ranges. The first area A1 has a radius of 400 m (approximately within a 5-minute walk) from the current position of the rescuer P1, and the second area A2 is 800 m (approximately within a 10-minute walk) from the current position of the rescuer P1. Range. The third area A3 is a range having a radius of 1200 m (approximately within a 15-minute walk) from the current position of the rescue requester P1. The fourth area A4 is within a radius of 6 km from the current position of the rescuer P1, and is within a vehicle movement range that can be reached in 10 minutes using a vehicle such as a bicycle, a motorcycle, or an automobile. When a long time is required for arrival of the ambulance team, there is an advantage that the search area is expanded to the vehicle movement range as in the fourth area A4 to search for a medical worker. The size of the search area and the number of expansions are not limited to this example, and can be changed as appropriate.

[Third Embodiment]
The third embodiment shown in FIGS. 11 to 15 is a function for determining whether or not each rescuer P2 who has received a rescue request notification is actually heading toward the current position of the rescuer P1, in other words, a rescuer required It is the form provided with the function which determines whether it is heading for rescue of P1.

  For example, as shown in FIGS. 12 to 14, the determination function is based on the rescuer P2 determined to be in the current position of the rescuer P1 in the map information 49 and the current position of the rescuer P1. It is used for distinguishably displaying the rescuer P2 determined not to face.

  The determination as to whether or not the rescuer P2 is heading toward the current position of the rescuer P1 is performed, for example, by confirming the rescuer P2's intention to rescue. Specifically, as shown in FIG. 11, a rescue request button 72 and a rescue impossible button 73 are provided on the rescue request notification screen 36 as operation buttons for transmitting the intention of the rescuer P2 to the rescue request support server 14. The rescuer P2 operates the rescue possible button 72 when there is an intention to rescue, and operates the rescue impossible button 73 when there is no intention. By the operation of the buttons 72 and 73, an intention display indicating the intention corresponding to each button is transmitted to the rescue request support server 14.

  In the rescue request support server 14, the received intention display is sent to the map information creation unit 46. As shown in the flowchart of FIG. 12, the map information creation unit 46 waits for the intention display to be received. When the intention display is received, the content of the intention display (“rescue is possible” or “rescue is not possible”). Determine. As described above, the map information creation unit 46 functions as a determination unit that determines whether or not the rescuer P2 is heading to the current position of the rescuer based on the received intention display.

  The map information creation unit 46 updates the display of the rescuer mark 66 in the map information 49 according to the content of the intention display. The display color of the rescuer mark 66 corresponding to the rescuer P2 corresponding to the rescuer P2 who indicated the intention of “rescue possible” is “green”, and the display of the rescuer mark 66 corresponding to the rescuer P2 indicating the intention of “rescue impossible” The display color of the rescuer mark 66 is changed so that the color is “red”.

  In addition, instead of changing the display color, or in addition to changing the display color, the display of whether or not the person is going to rescue is changed, the shape of the rescuer mark 66 is changed, the display is blinked, or a display such as “moving” is added. May be performed. When the display color or the like is changed in this way, it is preferable to display a legend so that the meaning can be understood.

  Moreover, as shown in FIG. 13, the map information preparation part 46 transmits periodically from the portable terminal 12 of rescuer P2 whether the rescuer P2 is approaching the present position of the rescuer P1. May be performed based on the position information. As described above, in the current position table 45, in addition to the latest position information, position data up to a predetermined time, for example, 5 minutes before is recorded. The map information creation unit 46 refers to the current position table 45. And the movement direction of each portable terminal 12 is grasped | ascertained based on the time-dependent change of position data. Based on the grasped movement direction, it is determined for each rescuer P2 whether or not the rescuer P1 is heading for the current position. Based on the determination result, the display color of the rescuer mark 66 is changed.

  Further, in addition to or instead of changing the display color of the rescuer mark 66, the moving direction may be displayed in the map information 49 as shown in FIG. The moving direction can be determined based on the position data in the current position table 45. The map information creation unit 46 adds a movement direction mark 81 indicating the determined movement direction in the map information 49 to the rescuer mark 66 for each rescuer P2. Since the approximate moving speed of the rescuer P2 who is approaching the current position of the rescuer P1 can be calculated from the temporal change of the position data, the travel speed is displayed by a method such as changing the length of the mark 81. May be.

  Moreover, you may utilize the determination function whether the rescuer P2 is heading to the present position of the rescuer P1 for another purpose. For example, as shown in FIG. 15, when there is a medical worker who does not face the rescuer P2 by determining whether or not there is a medical worker who is not heading toward the current position of the rescuer P1, , Resend the rescue request notification to the health care worker.

  The map information creation unit 46 functioning as a determination unit refers to the current position table 45 and grasps the moving direction of the rescuer P2. When there is a medical worker in the rescuer P2, it is determined whether or not the rescuer P2 is heading to the current position of the rescuer P1 based on the moving direction of the medical worker. If it is not heading to the current position, that is, if it is not heading for rescue of the rescuer P1, rescue request notification is retransmitted. Re-transmission can strongly appeal to medical professionals for the need for rescue.

[Fourth Embodiment]
16th Embodiment shown in FIG. 16 is a form provided with the communication function which enables communication between the rescuer P2. In this case, as shown in FIG. 16, an operation tool 84 for contact is displayed on the rescue request notification screen 83 of the mobile terminal 12.

  The operation tool 84 is opened by operating the rescuer mark 66 (including the medical worker mark 66M) indicating the rescuer P2 on the rescue request notification screen 83. The operation tool 84 is provided with a call button 85 and a mail button 86. When the call button 85 is operated, the mobile phone number of the corresponding rescue requester P1 is displayed from the registration information 58 of the rescue request support server 14, and a call can be made between the rescuers P2 by selecting and operating it. Become. Calls are made via a mobile communication network provided by a telephone company. Of course, a telephone call using the Internet may be used.

  When the mail button 86 is operated, a message input screen (not shown) is opened and a message can be input. By selecting the rescuer mark 66, the mail address is automatically inserted into the mail. When the message has been entered, an email is sent. The transmission of the mail may be performed via the rescue request support server 14 or may be performed via a server of another Internet connection company to which the user of the mobile terminal 12 is subscribed.

  By providing such a communication function between rescuers P2, for example, medical workers among rescuers P2 request other rescuers P2 to transport materials necessary for rescue such as AED (Automated External Defibrillator). Or, conversely, it is possible to inquire whether or not it is necessary to transport rescue supplies. In this way, a plurality of rescuers P2 can easily cooperate.

  In addition, the rescuer P2 who first arrived at the current position of the rescuer P1 calls the medical worker who is going to rescue, tells the condition of the rescuer P1 and asks how to deal with it. Will also be possible.

[Fifth Embodiment]
In 5th Embodiment shown in FIG. 17, when the rescuer mark 66 which is a display of the present position of the several rescuer P2 is overlapped and displayed on the map information 49, a medical worker is displayed preferentially. It is a form.

  As a form of preferential display, for example, among the overlapping rescuer marks 66, the medical worker mark 66M of the medical worker is displayed on the top so that the presence of the medical worker is conspicuous. . In this case, it is easy to confirm the presence of a medical worker even when a plurality of rescuers P2 are close to each other. Further, in FIG. 17, the total number of rescuers P2 that overlap each other may be displayed as a number, as indicated by a circled number. For example, when three people are displayed in a superimposed manner, a circle number “3” indicating that three people are displayed in a superimposed manner is added to the rescuer P2 in the uppermost layer. In this way, it is easy to confirm the total number of rescuers P2 that overlap.

  Such processing is performed by the map information creation unit 46. The map information creation unit 46 refers to the current position table 45 to grasp the current positions of the rescuers P2. Based on the current position, the presence / absence of a plurality of rescuers P2 close to each other is determined. Furthermore, when there are a plurality of rescuers P2 that are close to each other, it is determined based on the registration information 58 whether or not there is a medical worker. When there is a medical worker, priority display is performed so that the medical worker mark 66M is positioned at the top.

[Sixth Embodiment]
In the above embodiment, display indicating whether or not the person is a medical worker is simply performed. However, in the sixth embodiment, the medical worker is further subdivided in the map information 49, such as a doctor, a nurse, and an emergency medical technician. It is a form that makes it possible to identify even occupations.

  As shown in FIG. 18, the medical staff mark 66M is classified into a doctor mark 66M1 indicating a doctor, a nurse mark 66M2 indicating a nurse, and an emergency medical technician mark 66M3 indicating an emergency medical technician. These marks 66M1 to 66M3 function as identification marks indicating any of doctors, nurses, and emergency medical technicians. Each of the marks 66M1, 66M2, and 66M3 is a form in which a letter “D” for the doctor, a letter “N” for the nurse, and a letter “E” for the emergency medical technician are inserted in a circle. The map information 49 preferably displays a legend indicating what each of the marks 66M1 to 66M3 indicates.

  Thus, displaying the occupation of the medical worker has the following advantages. Even if it is a medical worker in a word, doctors, nurses, and lifesaving paramedics are restricted by work by law, so it is very important to know which profession is heading It is. Moreover, when rescuer P2 who arrived at the current position of rescuer P1 confirmed the condition of rescuer P1, rescuer P1 was clearly in a serious state, and rescue requires the power of a doctor. Suppose that it is. In this case, in the map information 49, for example, when there is only a nurse in the rescuer P2, it is possible to respond such as contacting the nurse or the like and requesting the rescue of the doctor.

[Seventh Embodiment]
As shown in FIG. 19, the seventh embodiment is a form in which the medical information of the rescue requester P <b> 1 is displayed when the rescue requester mark 65 is operated in the map information 49. The medical information is registered in the registration information 58 in advance. The rescue request support server 14 distributes this medical information to the rescuer P2's mobile terminal. Delivery of such medical information is performed, for example, by the rescue request notification transmission unit 42.

  For example, when the rescuer required mark 65 is operated in the map information 49, the selection screen 96 is opened. The selection screen 96 is provided with buttons 97 to 99 for selecting the type of medical information such as prescription drugs, hospital visits, and medical history. When each button 97 to 99 is operated, a delivery request for medical information such as prescription drugs, a hospital visit, and a medical history is transmitted to the rescue request support server 14. In the rescue request support server 14, when the rescue request notification transmission unit 42 receives a prescription drug delivery request, the rescue request notification transmission unit 42 reads the prescription drug currently taken by the rescuer P1 from the registration information 58 and carries the request source mobile phone. Delivered to the terminal 12. As a result, the prescription history of the rescue requester P1 is displayed on the mobile terminal 12. Similarly, by operating the hospital button 98, a hospital or clinic destination is displayed. The medical history is displayed by operating the medical history button 99.

  Since the medical information is personal information that is strongly requested to be concealed, it is preferable that the distribution request for such medical information is permitted only to medical workers. In this case, when there is a request for delivery of medical information, the rescue request notification transmission unit 42 refers to the registration information 58 to determine whether or not the request source is a medical worker, and determines that it is a medical worker. Deliver only if you do.

  Such medical information may not be registered in the registered information 58. For example, the rescue request support server 14 accesses the server of the hospital of the rescue requester P1 and obtains the medical information therefrom. The acquired medical information may be distributed. In this case, for example, the hospital ID and patient ID of the user's visit destination are registered in the registration information 58. Based on this information, the rescue request support server 14 identifies the hospital where the rescuer P1 is required and transmits an acquisition request including the patient ID to the hospital.

  Further, when a my number system for assigning a unique number to each citizen is introduced in the future, the my number may be registered in the registration information 58. If there is a my number, it is possible to obtain medical information by accessing a plurality of hospital servers using the my number as a search key.

  In each of the above embodiments, the rescue request request of the rescue requester P1 has been described as an example of transmitting from the mobile terminal 11 of the rescue requester P1 to the rescue request support server 14, but the mobile terminal 11 and the biosensor And a trigger signal for requesting a rescue request may be transmitted. For example, the biosensor is a wearable biosensor that can be worn by the rescuer P1. When the biological sensor detects an abnormality, the portable terminal 11 transmits a rescue request request according to the trigger signal from the biological sensor. For example, a chronic disease patient is constantly monitored by a biological sensor, and a trigger signal is input to the mobile terminal 11 when an abnormal value is detected. The portable terminal 11 transmits a rescue request request based on the trigger signal.

  In each of the above embodiments, as shown in FIG. 8, the position information indicating the current position of each mobile terminal 11, 12 is always acquired at regular time intervals. Instead, as in the modification shown in the flowchart of FIG. 20, the rescuer's portable terminal 11 transmits a rescue request request (ST20), and the rescue request support server 14 sends the rescue request request to the rescue request request. After receiving (ST21), acquisition of position information from the mobile terminals 11 and 12 may be started.

  In the case of this modification, the rescue request support server 14 transmits a current position acquisition command to the mobile terminal 12 excluding the mobile terminal 11 of the rescue requester P1 when receiving a rescue request (ST22). When each portable terminal 12 receives this current position acquisition command (ST23), it transmits the current position information to the rescue request support server 14 (ST24). The rescue request support server 14 selects only a user within a certain distance centered on the current position of the rescuer P1 as the rescuer P2 based on the sent current position information, as in the first embodiment ( ST14). After the selection, as in the first embodiment, map information is created (ST15), and a rescue request notification including this map information is transmitted to the selected rescuer P2 (ST16). When receiving the rescue request notification (ST17), the portable terminal 12 of the rescuer P2 displays the rescue request notification screen 36 including the map information 49 on the display 28A (ST18). The rescuer P2 who is the user of the mobile terminal 12 can check the current position of the rescuer P1 by looking at the rescue request notification screen 36. Thereby, rescuer P2 can head for rescue of rescuer P1 who needs nearby. Note that the current position information is periodically acquired only for the selected rescuer P2, and the map information 49 is updated.

  In the case of this modification, since the current position of another user is acquired after receiving a rescue request, selection of the rescuer P2 may be delayed by that amount compared to the first embodiment. However, the mobile terminal 12 of the other user outside the search area centered on the rescuer P1 does not regularly acquire the current position information, and the mobile terminal located outside the search request support server 14 or the search area 12 loads can be reduced.

  The operating entity of the rescue request support server 14 and the rescue request support application service may be a private business operator or a public organization such as a local government.

  The hardware configuration of the rescue request support server 14 can be variously modified. For example, for the purpose of improving processing capability and reliability, the rescue request support server 14 may be configured by a plurality of server computers separated as hardware. As described above, the hardware configuration of the computer system can be appropriately changed according to required performance such as processing capability, safety, and reliability. Further, not limited to hardware, programs may be duplicated or distributed and stored in a plurality of storage devices for the purpose of ensuring safety and reliability.

  The present invention is not limited to the above-described embodiment and the above-described modifications, and it is needless to say that various configurations can be adopted without departing from the gist of the present invention. For example, the above embodiment and the above-described modifications can be combined as appropriate. In addition to the program, the present invention extends to a storage medium that stores the program.

10 Rescue Request Support System 11, 12 Mobile Terminal 14 Rescue Request Support Server 30A Rescue Request Support AP
30B Rescue request support server program 36 Rescue request notification screen 48 User information 49 Map information 65 Rescuer mark required 66 Rescuer mark 67 Medical worker mark 68 Personal mark 84 Contact tool 85 Call button 86 Mail button P1 Rescuer required P2 Rescuer

Claims (13)

A position for acquiring position information indicating the current position of the rescuer and the rescuer from portable terminals carried by each of the rescuer who requested the rescue and the rescuer who received the rescue request of the rescuer. An information acquisition unit;
An identification mark indicating whether or not the rescuer is a medical worker is displayed based on map information to which the rescuer and the current position of the rescuer are mapped, and based on registered information registered in advance A map information creating unit for creating the map information
A rescue request support apparatus comprising a map information distribution unit that distributes the map information to the rescuer's mobile terminal.   The rescue request support apparatus according to claim 1, wherein the medical staff is any one of a doctor, a nurse, and a paramedic, and the identification mark is a mark that identifies the doctor, a nurse, and a paramedic.   The rescue request support according to claim 1 or 2, wherein in the map information, when the display of current positions of a plurality of rescuers overlaps, the rescuer who is the medical worker is preferentially displayed. apparatus. The location information acquisition unit acquires location information of the user based on information from a portable terminal carried by a user registered in advance,
Furthermore, based on the current location of the rescuer required by the location information acquisition unit, a rescuer selection unit that selects the rescuer from the user,
The rescue request support apparatus according to any one of claims 1 to 3, further comprising a rescue request notification transmission unit that transmits a rescue request notification to the selected rescuer.   The rescue request support apparatus according to claim 4, wherein the map information distribution unit distributes the map information to a transmission destination of the rescue request notification.   The rescuer selection unit sets a first area as a search area for the rescuer and performs a first selection, and the medical worker is included in the rescuer selected in the first selection. 6. The rescue request support apparatus according to claim 5, wherein if there is no such area, a second area wider than the first area is set as the search area and the second selection is performed.   The rescue request support apparatus according to claim 6, further comprising a determination unit that determines whether or not the rescuer who has transmitted the rescue request notification is heading toward a current position of the rescuer.   8. The rescue request notification is retransmitted to the medical staff when the medical staff is among the rescuers determined not to go to the current location of the rescuer. Rescue request support device according to claim 1.   In the map information, the rescuer determined to be heading toward the current position of the rescuer and the rescuer determined not to head toward the current position of the rescuer are displayed in an identifiable manner. The rescue request support apparatus according to claim 7 or 8.   The rescue request support apparatus according to any one of claims 1 to 9, further comprising a communication function that enables communication between the plurality of rescuers. Location information acquisition in which each rescuer who has requested rescue and each rescuer who has received a rescue request from the rescuer obtains location information indicating the current location of the rescuer and the rescuer from the mobile terminal. Steps,
An identification mark indicating whether or not the rescuer is a medical worker is displayed based on map information to which the rescuer and the current position of the rescuer are mapped, and based on registered information registered in advance A map information creating step for creating the map information;
A map information distribution step of distributing the map information to the rescuer's mobile terminal;
A method for operating a rescue request support apparatus to be executed by a rescue request support apparatus. A position for acquiring position information indicating the current position of the rescuer and the rescuer from portable terminals carried by each of the rescuer who requested the rescue and the rescuer who received the rescue request of the rescuer. An information acquisition step;
An identification mark indicating whether or not the rescuer is a medical worker is displayed based on map information to which the rescuer and the current position of the rescuer are mapped, and based on registered information registered in advance A map information creating step for creating the map information;
A map information distribution step of distributing the map information to the rescuer's mobile terminal;
A rescue request support program that causes a computer to function as a rescue request support device when executed by a computer. A rescue request support system comprising a portable terminal carried by each of a rescue requester who has made a rescue request and a rescuer who has received a rescue request from the rescuer, and a rescue request support device;
The rescue request support device includes:
A position information acquisition unit for acquiring position information indicating the current position of the rescuer and the rescuer from the portable terminal;
An identification mark indicating whether or not the rescuer is a medical worker is displayed based on map information to which the rescuer and the current position of the rescuer are mapped, and based on registered information registered in advance A map information creating unit for creating the map information
A rescue request support system comprising: a map information distribution unit that distributes the map information to the rescuer's mobile terminal.

Images