Ambulance support device, method, and program

Abstract

To improve accuracy in the matching between a person to be rescued and a rescuer.SOLUTION: A rescue support device comprises: registration means for registering information disclosure conditions of a person to be rescued and rescue corresponding conditions of each of a plurality of rescue candidates; acceptance means for accepting a rescue request from an information terminal of a prescribed person to be rescued; selection means for selecting a rescuer from among the plurality of rescue candidates on the basis of the information disclosure conditions of the person to be rescued related to the rescue request and the rescue corresponding conditions; and notification means for notifying a portable terminal of the selected rescuer of a rescue request of the person to be rescued. The information disclosure conditions include a reward amount additionally payable to the rescuer.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a rescue support device, a rescue support system, a rescue support method, and a non-transitory computer-readable medium, and particularly to a rescue support device, a rescue support system, a rescue support method, and a non-transitory computer-readable medium for supporting the rescue of a victim.

Background Art

[0002] In recent years, due to the rapid increase in unnecessary emergency transports, the rescue and emergency transport for victims with high priority are increasingly delayed. Therefore, there is a growing need for services to assist in emergency rescue and transport for each region in addition to the fire department.

[0003] Patent Document 1 discloses a technology related to a rescue request support device. The rescue request support server according to Patent Document 1 selects a rescuer from among pre-registered rescue candidates based on the current position of the person in need of rescue in response to a rescue request from the person in need of rescue. The rescue request support server transmits a rescue request notification including the current position of the person in need of rescue to the terminal of the selected rescuer. At the same time, the rescue request support server makes an emergency report to the fire command center.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the technology according to Patent Document 1, the accuracy of matching between the victim and the rescuer is insufficient. This is because the rescuer is not a full-time rescuer, and there are variations in skills and available time slots. Also, the victim has desires for the rescuer.

[0006] The present disclosure has been made to solve such problems, and an object thereof is to provide an ambulance support device, a system, a method, and a non-transitory computer-readable medium for improving the accuracy of matching between a person in need of rescue and an ambulance crew member.

Means for Solving the Problem

[0007] The ambulance support device according to the first aspect of the present disclosure includes: registration means for registering information disclosure conditions of a person in need of rescue and ambulance response conditions of each of a plurality of ambulance candidate crew members; reception means for receiving an ambulance request from an information terminal of a predetermined person in need of rescue; selection means for selecting an ambulance crew member from among the plurality of ambulance candidate crew members based on the information disclosure conditions and the ambulance response conditions of the person in need of rescue related to the ambulance request; notification means for notifying the selected ambulance crew member's mobile terminal of the ambulance request for the person in need of rescue; and is provided with.

[0008] The ambulance support system according to the second aspect of the present disclosure includes: an ambulance support device; an emergency institution server, and is provided with, wherein the ambulance support device includes: registration means for registering information disclosure conditions of a person in need of rescue and ambulance response conditions of each of a plurality of ambulance candidate crew members; reception means for receiving an ambulance request from an information terminal of a predetermined person in need of rescue; selection means for selecting an ambulance crew member from among the plurality of ambulance candidate crew members based on the information disclosure conditions and the ambulance response conditions of the person in need of rescue related to the ambulance request; notification means for notifying the selected ambulance crew member's mobile terminal of the ambulance request for the person in need of rescue; and is provided with, the notification means notifies the emergency institution server of notification content corresponding to a response from the mobile terminal to the ambulance request, and the emergency institution server performs processing corresponding to the notification content.

[0009] The first aid support method according to the third aspect of the present disclosure is as follows: A computer registers the information disclosure conditions of the victim and the first aid response conditions of each of the plurality of first aid candidates, receives a first aid request from the information terminal of a predetermined victim, selects a first aider from among the plurality of first aid candidates based on the information disclosure conditions and the first aid response conditions of the victim related to the first aid request, notifies the selected first aider's mobile terminal of the first aid request for the victim.

[0010] A non-transitory computer-readable medium storing a program according to the fourth aspect of the present disclosure includes a registration process for registering the information disclosure conditions of the victim and the first aid response conditions of each of the plurality of first aid candidates, a reception process for receiving a first aid request from the information terminal of a predetermined victim, a selection process for selecting a first aider from among the plurality of first aid candidates based on the information disclosure conditions and the first aid response conditions of the victim related to the first aid request, a notification process for notifying the selected first aider's mobile terminal of the first aid request for the victim, and causes a computer to execute them.

Advantages of the Invention

[0011] According to the present disclosure, it is possible to provide a first aid support device, a system, a method, and a non-transitory computer-readable medium for improving the accuracy of matching between a victim and a first aider.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Mode for Carrying Out the Invention

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and redundant descriptions are omitted as necessary for clarity of explanation.

[0014] <Embodiment 1> FIG. 1 is a block diagram showing the configuration of the ambulance support device 1 according to Embodiment 1. The ambulance support device 1 is a computer for supporting the ambulance of the injured person. Here, the ambulance support device 1 is connected to an information terminal possessed by the injured person and a plurality of mobile terminals respectively possessed by a plurality of ambulance candidate persons via a communication network (not shown, hereinafter also simply referred to as a network). Note that the network may be wired or wireless, and the type of communication protocol is not limited.

[0015] The rescue support device 1 includes a registration unit 11, a reception unit 12, a selection unit 13, and a notification unit 14. The registration unit 11 registers the information disclosure conditions of the person to be rescued and the respective rescue response conditions of a plurality of rescue candidates. Note that the registration unit 11 stores the information disclosure conditions and the rescue response conditions in the same or different storage devices. The storage device may be built into the rescue support device 1 or may be directly or connected to the rescue support device 1 via a network. The information disclosure conditions are information that permits disclosure to rescue candidates and definition information regarding the disclosure destination for information about the person to be rescued. The information about the person to be rescued may include personal information, health information, rescue hope conditions, and the like. The rescue response conditions are definition information such as the rescue content that each rescue candidate can handle and the conditions of the person to be rescued that the candidate desires.

[0016] The reception unit 12 receives a rescue request from the information terminal of a predetermined person to be rescued. Here, the rescue request may include position information indicating the current position of the information terminal. The rescue request may also include the identification information of the information terminal or the personal identification information of the person to be rescued.

[0017] The selection unit 13 selects a rescuer from among a plurality of rescue candidates based on the information disclosure conditions of the person to be rescued related to the rescue request and the rescue response conditions.

[0018] The notification unit 14 notifies the mobile terminal of the selected rescuer of the rescue request for the person to be rescued. Here, the rescue request may include the current position of the person to be rescued and information that satisfies the information disclosure conditions.

[0019] FIG. 2 is a flowchart showing the flow of the rescue support method according to Embodiment 1. First, the registration unit 11 registers the information disclosure conditions of the person to be rescued and the respective rescue response conditions of a plurality of rescue candidates (S11). For example, the registration unit 11 receives the information disclosure conditions from the information terminal of the person to be rescued and registers them in a predetermined storage device. The registration unit 11 also receives the rescue response conditions from the mobile terminal of each rescue candidate and registers them in a predetermined storage device.

[0020] Next, the reception unit 12 receives a rescue request from the information terminal of a predetermined victim (S12). Then, the selection unit 13 selects a rescuer from among a plurality of rescue candidates based on the information disclosure conditions of the victim to whom the rescue request applies and the rescue response conditions (S13). Thereafter, the notification unit 14 notifies the selected rescuer's mobile terminal of the rescue request for the victim (S14).

[0021] The rescue support device 1 according to this embodiment targets a victim who is a user requesting rescue in an emergency and rescue candidates who can conditionally rescue the victim. In particular, the rescue candidates are not full-time first aid providers and have variations in skills and available time slots. The rescue support device 1 pre-registers the information disclosure conditions input from the victim. Also, the rescue support device 1 pre-registers the rescue response conditions input from each of the plurality of rescue candidates. Then, the rescue support device 1 selects a rescuer who satisfies the information disclosure conditions and the rescue response conditions from among the plurality of rescue candidates in response to the rescue request. Therefore, in this embodiment, the desires of both the victim to whom the rescue request applies and each rescue candidate can be satisfied. For example, the victim can specify a rescue candidate with a predetermined skill as the target for disclosing their own information for the rescue request. That is, the skills of the rescue candidate etc. may be specified in the information disclosure conditions. Therefore, the rescue support device 1 can select, from among the plurality of rescue candidates, a person who satisfies the information disclosure conditions specified by the victim to whom the rescue request applies as the rescuer. Thus, a rescuer who satisfies the victim's desires can be selected. Also, the rescue candidate can specify the rescue content and time slot that they can handle as the rescue response conditions. Therefore, when the rescue candidate is requested to rescue as a rescuer by the rescue support device 1, it will be a case where their own rescue response conditions are satisfied. Thus, the accuracy of matching between the victim and the rescuer can be improved. And the rescue support device 1 notifies the rescue request to the mobile terminal of the rescuer thus selected. Therefore, rescue can be effectively supported.

[0022] The first-aid support device 1 includes a processor, a memory, and a storage device, which are not shown. The storage device stores a computer program in which the processing of the first-aid support method according to this embodiment is implemented. Then, the processor causes the memory to read the computer program from the storage device and executes the computer program. Thereby, the processor realizes the functions of the registration unit 11, the reception unit 12, the selection unit 13, and the notification unit 14.

[0023] Alternatively, the registration unit 11, the reception unit 12, the selection unit 13, and the notification unit 14 may each be realized by dedicated hardware. Also, some or all of the components of each device may be realized by general-purpose or dedicated circuitry, a processor, etc., or a combination thereof. These may be constituted by a single chip or by a plurality of chips connected via a bus. Some or all of the components of each device may be realized by a combination of the above-described circuitry, etc., and a program. Also, as the processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (field-programmable gate array), a quantum processor (quantum computer control chip), etc. can be used.

[0024] Also, when some or all of the components of the first-aid support device 1 are realized by a plurality of first-aid support devices, circuitry, etc., the plurality of first-aid support devices, circuitry, etc. may be centrally arranged or may be distributed. For example, the first-aid support device, circuitry, etc. may be realized in a form in which each is connected via a communication network, such as a client-server system or a cloud computing system. Also, the function of the first-aid support device 1 may be provided in the form of SaaS (Software as a Service).

[0025] <Embodiment 2> Embodiment 2 is a specific example of Embodiment 1 described above. FIG. 3 is a block diagram showing the overall configuration of the ambulance support system 1000 according to Embodiment 2. The ambulance support system 1000 is an information system for assisting in the ambulance service for the victim U1 by multiple ambulance candidate persons U21 to U2m (m is a natural number of 2 or more) and ambulance personnel. The ambulance support system 1000 includes an information terminal 100, an authentication device 200, an ambulance support device 300, mobile terminals 41, 42, ··· and 4m, and a fire department server 500. Each of the information terminal 100, the authentication device 200, the ambulance support device 300, the mobile terminals 41, 42, ··· and 4m, and the fire department server 500 is connected via a network N. Here, the network N is a wired or wireless communication line, for example, the Internet.

[0026] In the following description, the authentication for the personal identification process of the victim is face authentication, which is an example of biometric authentication, and the personal identification information is face feature information, which is an example of biometric information. However, other technologies that utilize captured images are applicable to biometric authentication and biometric information. For example, the biometric information may use data (feature quantities) calculated from personal physical characteristics unique to an individual, such as fingerprints, voiceprints, veins, retinas, and iris patterns of the pupils. Also, the personal identification process may be other than biometric authentication, and the personal identification information may also be other than biometric information.

[0027] The victim U1 is a person who requests ambulance service in an emergency. The victim U1 is, for example, an elderly person or a person with a chronic illness. The victim U1 possesses the information terminal 100. The information terminal 100 is, for example, a wearable device (wearable device, vital terminal) worn by the victim U1, a mobile phone terminal, a smartphone, a tablet terminal, etc. operated by the victim U1. The information terminal 100 has an application installed for communicating with the ambulance support device 300, and it is assumed that the application is operating.

[0028] The information terminal 100 transmits a registration request including personal information, health information, condition information, etc. input by the rescued person U1 to the rescue support device 300 via the network N. The personal information includes the name, address, date of birth, gender, information of cohabiting family members, identity certificate, disabled or care-requiring person information, payment means information, biometric information, etc. of the rescued person U1. The payment means information may be credit card information or debit account information of a financial institution. The biometric information may be a face image in which an area including the face of the rescued person U1 is photographed. The health information includes the medical history (such as myocardial infarction) of the rescued person U1, information regarding allergies (such as crustaceans), blood type, etc. Also, the health information may include vital information. The vital information is, for example, body surface temperature, blood pressure, heart rate, etc. The condition information includes notification conditions for rescue requests, types of disclosed information, attributes of disclosure destinations, etc. The type of disclosed information is the type of information regarding the rescued person U1 (rescued person information) that the rescued person U1 permits to be disclosed to rescue candidates. The attribute of the disclosure destination is the attribute information of the rescued person who is the disclosure destination of the rescued person information. Also, the condition information may include an additional gratitude payment amount that can be paid to the rescuer, etc. Note that the above registration request may be made by an information processing device other than the information terminal 100.

[0029] The information terminal 100 acquires GPS information as position information indicating the current position by periodically receiving GPS information from GPS (Global Positioning System) satellites (not shown), etc. The information terminal 100 transmits a rescue request (alert) of the rescued person U1 to the rescue support device 300 via the network N when a predetermined notification condition is satisfied. The rescue request includes the current position of the information terminal 100 and the personal identification information of the rescued person U1. Note that the personal identification information may be identification information such as biometric information or user ID of the rescued person U1. Alternatively, instead of the personal identification information, the rescue request may include terminal identification information such as the identification information of the information terminal 100 or the IP (Internet Protocol) address. Also, the rescue request may include vital information measured below.

[0030] When the information terminal 100 is a vital terminal, the information terminal 100 monitors the health status of the rescued person U1. For example, the information terminal 100 periodically measures vital information such as the body surface temperature, blood pressure, and heart rate of the rescued person U1, and determines whether the measured value meets a predetermined condition. Specifically, the information terminal 100 determines whether the measured value is outside a predetermined range, greater than or equal to a predetermined value, or less than or equal to a predetermined value as a predetermined condition. For example, when the measured heart rate indicates an abnormal value, the information terminal 100 determines that the measured value meets the predetermined condition. When the measured value meets the predetermined condition, the information terminal 100 detects that the health status of the rescued person U1 has deteriorated (for example, the physical condition has changed suddenly). Then, when the measured value meets the predetermined condition, the information terminal 100 determines that a predetermined notification condition is satisfied, and transmits a rescue request for the rescued person U1.

[0031] Alternatively, when the information terminal 100 is a mobile phone terminal, a smartphone, a tablet terminal, etc., the information terminal 100 may transmit a rescue request according to the operation of the rescued person U1 on the above-described application. In this case, the predetermined notification condition is an operation of the rescue request by the rescued person U1 on the information terminal 100. For example, the information terminal 100 may regard a pressing operation on an alert button displayed on the screen by the above-described application as an operation of the rescue request by the rescued person U1. Note that the rescued person U1 may perform an operation of the rescue request not only when his / her own health status is concerned, but also in case of an accident or injury, or when affected by an earthquake, a flood, etc. and unable to evacuate alone.

[0032] Alternatively, when the rescued person U1 wears a pacemaker on the heart, the information terminal 100 may determine that a predetermined notification condition is satisfied when an abnormality of the pacemaker is detected. In addition, when the information terminal 100 detects that the rescued person U1 has stopped operating or fallen for a certain period of time or more, the information terminal 100 may determine that a predetermined notification condition is satisfied. Note that the information terminal 100 may include the presence or absence of an accident or injury in the rescue request.

[0033] The rescue candidates U21, U22, ··· and U2m are persons who can conditionally rescue the injured. The rescue candidates U21, etc. are, for example, doctors, nurses, paramedics, advanced first aid course attendees, basic first aid course attendees, those who hope for vehicle support, local government fire and disaster prevention related personnel, etc. The rescue candidates U21, etc. may, for example, support the rescue of nearby injured persons when doctors, nurses, etc. are outside their working hours (such as holidays and nights). Also, some of the rescue candidates U21, etc. may perform rescue using a vehicle such as a private car. For example, it is assumed that the rescue candidate U22 can use the vehicle 421 for rescue, and the rescue candidate U2m can use the vehicle 4m1 for rescue.

[0034] The rescue candidates U21, etc. possess mobile terminals 41, etc. Specifically, it is assumed that the rescue candidate U21 possesses the mobile terminal 41, the rescue candidate U22 possesses the mobile terminal 42, ··· the rescue candidate U2m possesses the mobile terminal 4m. The mobile terminals 41, etc. are, for example, mobile phone terminals, smartphones, tablet terminals, etc. operated by the rescue candidates U21, etc. who possess them. The mobile terminals 41, etc. have an application installed for communicating with the rescue support device 300, and it is assumed that the application is operating.

[0035] The mobile terminal 41 transmits a registration request including personal information, terminal information, attribute information, rescue response conditions, etc. input by the rescue candidate U21 to the rescue support device 300 via the network N. The personal information is the name, address, date of birth, gender, account information for transferring gratitude money, etc. of the rescue candidate U21. The personal information may include personal identification information such as the biometric information of the rescue candidate U21. The terminal information is the identification information, IP address, etc. of the mobile terminal 41. The attribute information is information indicating the occupation, qualifications, etc. of the rescue candidate U21. The attribute information includes information indicating a doctor, nurse, paramedic, advanced or basic first aid course attendee. Also, the attribute information may include possessing a driver's license. The rescue response conditions include the geographical range where rescue is possible, the rescue content that can be handled, time zones, exclusion conditions, reward conditions, etc. Note that the same applies to the mobile terminal 42, etc. Note that the above registration request may be performed by an information processing device other than the mobile terminals 41, etc.

[0036] The mobile terminal 41 etc. periodically receives GPS information from GPS satellites etc., and acquires the GPS information as position information indicating the current position. The mobile terminal 41 etc. periodically transmits a position report including the current position and the terminal identification information or user ID to the ambulance support device 300 via the network N. Note that the user ID is identification information of the user issued to the ambulance candidate U21 etc. when a registration request is made by the mobile terminal 41 etc.

[0037] The injured person U1 and the ambulance candidates U21 to Um can be said to be users of the ambulance support system 1000.

[0038] The authentication device 200 is an information processing device that stores face feature information of a plurality of persons (users, the injured person U1 etc.). Further, the authentication device 200 collates the face image or face feature information included in the request with the face feature information of each user in response to a face authentication request received from the outside, and returns the collation result (authentication result) to the requester.

[0039] FIG. 4 is a block diagram showing the configuration of the authentication device 200 according to the second embodiment. The authentication device 200 includes a face information DB (DataBase) 210, a face detection unit 220, a feature point extraction unit 230, a registration unit 240, and an authentication unit 250. The face information DB 210 stores the user ID 211 and the face feature information 212 of the user ID in association with each other. The face feature information 212 is a set of feature points extracted from the face image. Note that the authentication device 200 may delete the face feature information 212 in the face feature DB 210 according to the request from the registered user of the face feature information 212. Alternatively, the authentication device 200 may delete the face feature information 212 after a certain period has elapsed since the registration of the face feature information 212.

[0040] The face detection unit 220 detects the face area included in the registration image for registering face information and outputs it to the feature point extraction unit 230. The feature point extraction unit 230 extracts feature points from the face area detected by the face detection unit 220 and outputs face feature information to the registration unit 240. Further, the feature point extraction unit 230 extracts feature points included in the face image received from the user terminal 101 or the like, the rescue support device 300 or the like, and outputs face feature information to the authentication unit 250.

[0041] When registering face feature information, the registration unit 240 newly issues a user ID 211. The registration unit 240 associates the issued user ID 211 with the face feature information 212 extracted from the registration image and registers it in the face information DB 210. The authentication unit 250 performs face authentication using the face feature information 212. Specifically, the authentication unit 250 collates the face feature information extracted from the face image with the face feature information 212 in the face information DB 210. When the collation is successful, the authentication unit 250 identifies the user ID 211 associated with the collated face feature information 212. The authentication unit 250 returns the presence or absence of the match of the face feature information to the requester as the face authentication result. The presence or absence of the match of the face feature information corresponds to the success or failure of the authentication. Here, the case where the face feature information matches (match exists) means that the degree of match is equal to or higher than the threshold value. Further, the face authentication result shall include the identified user ID when the face authentication is successful.

[0042] FIG. 5 is a flowchart showing the flow of the face information registration process according to the second embodiment. Here, an information registration terminal (not shown) photographs the body including the user's face and transmits a face information registration request including the photographed image (registration image) to the authentication device 200 via the network N. The information registration terminal is, for example, a rescue support device such as a personal computer, a smartphone, or a tablet terminal. For example, the information registration terminal may be the information terminal 100, the mobile terminal 41, or the like. Alternatively, the information registration terminal may be the rescue support device 300 that has received a face information registration request from the information terminal 100 or the like.

[0043] First, the authentication device 200 acquires the registration image included in the face information registration request (S21). For example, the authentication device 200 receives the face information registration request from the information registration terminal via the network N. Next, the face detection unit 220 detects the face area included in the registration image (S22). Next, the feature point extraction unit 230 extracts feature points from the face area detected in step S22 and outputs face feature information to the registration unit 240 (S23). Finally, the registration unit 240 issues a user ID 211, associates the user ID 211 with the face feature information 212, and registers them in the face information DB 210 (S24). Note that the authentication device 200 may receive the face feature information 212 from the information registration terminal, associate it with the user ID 211, and register it in the face information DB 210. Also, the registration unit 240 may notify the information registration terminal or the rescue support device 300 of the registered (issued) user ID.

[0044] FIG. 6 is a flowchart showing the flow of face authentication processing by the authentication device 200 according to the second embodiment. First, the feature point extraction unit 230 acquires the face image for authentication included in the face authentication request (S31). For example, the authentication device 200 receives the face authentication request from the rescue support device 300 via the network N, and extracts face feature information from the face image included in the face authentication request as in steps S21 to S23. Alternatively, the authentication device 200 may receive the face feature information from the rescue support device 300. Next, the authentication unit 250 collates the acquired face feature information with the face feature information 212 in the face information DB 210 (S32). When the face feature information matches, that is, when the degree of match of the face feature information is equal to or greater than the threshold (Yes in S33), the authentication unit 250 identifies the user ID 211 of the user whose face feature information matches (S34), and returns to the rescue support device 300 a message indicating that the face authentication has succeeded and the identified user ID 211 (S35). When there is no matching face feature information (No in S33), the authentication unit 250 returns to the rescue support device 300 a message indicating that the face authentication has failed (S36).

[0045] Returning to FIG. 3, the description will be continued. The rescue support device 300 is an example of the above-described rescue support device 1. The rescue support device 300 is an information processing device that registers the information of the person to be rescued and the information of the rescue candidates, selects the rescuer according to the rescue request, notifies the rescue request, and notifies the fire department server 500. The rescue support device 300 may be redundant in a plurality of servers, and each functional block may be realized by a plurality of computers.

[0046] Next, the rescue support device 300 will be described in detail. FIG. 7 is a block diagram showing the configuration of the rescue support device 300 according to the second embodiment. The rescue support device 300 includes a storage unit 310, a memory 320, a communication unit 330, and a control unit 340. The storage unit 310 is an example of a storage device such as a hard disk or a flash memory. The storage unit 310 stores a program 311, information 312 of the person to be rescued, and information 313 of the rescue candidates. The program 311 is a computer program in which the processing of the rescue support method in the rescue support device 300 according to the second embodiment is implemented.

[0047] The information 312 of the person to be rescued is management information regarding the person to be rescued. The information 312 of the person to be rescued is associated with a user ID 3121, personal information 3122, health information 3123, and condition information 3124. The information 312 of the person to be rescued may be further associated with the terminal identification information of the information terminal 100 by the user ID 3121. The user ID 3121 is identification information of the person to be rescued and is an example of personal identification information. Further, the user ID 3121 corresponds to the user ID 211 managed in the face information DB 210 of the authentication device 200 described above. The personal information 3122 is the personal information included in the registration request from the information terminal 100 described above. Note that the personal information 3122 may exclude biometric information. The health information 3123 is the health information included in the registration request from the information terminal 100 described above. Further, the health information 3123 may include vital information periodically measured from the person to be rescued.

[0048] [[ID=]] The conditional information 3124 is the conditional information included in the registration request from the above-described information terminal 100. The conditional information 3124 is an example of the above-described information disclosure conditions. The conditional information 3124 includes a notification condition 31241, a disclosed information type 31242, and a disclosure destination attribute 31243. The notification condition 31241 is information that defines the conditions under which the information terminal 100 notifies an ambulance request. Specifically, the notification condition 31241 may include a case where the vital information of the victim U1 detected in the information terminal 100 worn by the victim U1 satisfies a predetermined condition. Further, the notification condition 31241 may include a case where a pressing operation on an alert button on an application operating on the information terminal 100 is detected. Further, the notification condition 31241 may include a case where an abnormality of the pacemaker is detected.

[0049] The disclosed information type 31242 is the type of victim information that the victim U1 permits to be disclosed to the ambulance candidate. For example, the disclosed information type 31242 is age, gender, name of the disease of the chronic illness, location information, information of the attending physician, etc. Note that the information of the attending physician is information such as the name and location of the medical institution to which the attending physician of the victim U1 belongs. The disclosure destination attribute 31243 is the attribute information of the victim to be the disclosure destination of the victim information corresponding to the information type indicated by the disclosed information type 31242. For example, the disclosure destination attribute 31243 is a person who has taken an advanced first aid training course, a nurse, a doctor, a person who hopes for support by vehicle, etc. Note that the conditional information 3124 may include, as described above, an amount of gratitude money that can be additionally paid to the ambulance staff.

[0050] The ambulance candidate information 313 is management information regarding ambulance candidates. The ambulance candidate information 313 has a user ID 3131, attribute information 3132, ambulance response conditions 3133, current location 3134, terminal information 3135, ambulance history 3136, and evaluation information 3137 associated therewith. The user ID 3131 is identification information of the ambulance candidate. The attribute information 3132 is the attribute information included in the registration request from the above-described mobile terminal 41 or the like. The ambulance response conditions 3133 are the ambulance contents that can be handled by the ambulance candidate. The ambulance response conditions 3133 are the ambulance response conditions included in the registration request from the above-described mobile terminal 41 or the like. For example, the ambulance contents that can be handled include emergency treatment as a nurse, AED (Automated External Defibrillator) operation, transportation by vehicle, and the like. The exclusion conditions are the ambulance contents to be excluded, for example, response to accidents or injuries, and the like. The reward conditions are the desired amount of gratitude payment or the like additionally paid to the ambulance provider.

[0051] The current location 3134 is the location information of the mobile terminal 41 or the like periodically received from the above-described mobile terminal 41 or the like. The terminal information 3135 is the terminal information included in the registration request from the above-described mobile terminal 41 or the like.

[0052] The ambulance history 3136 is history information of the ambulance candidate having provided ambulance services. The ambulance history 3136 is information, for example, in which the identification information of the ambulance response, the information of the person being rescued, the information of the ambulance provider, the date and time indicating the progress of the ambulance situation, the ambulance contents, the gratitude payment amount, the evaluation, the comment from the person being rescued, and the like are associated.

[0053] The evaluation information 3137 is information indicating the evaluation by the person being rescued regarding the ambulance candidate and the evaluation from the local government where the person being rescued U1 resides. The evaluation information 3137 may be a score or a level value.

[0054] The memory 320 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information during the operation of the control unit 340. The communication unit 330 is a communication interface with the network N.

[0055] The control unit 340 is a processor, that is, a control device, which controls each component of the rescue support device 300. The control unit 340 causes the memory unit 310 to read the program 311 into the memory 320 and executes the program 311. Thereby, the control unit 340 realizes the functions of the registration unit 341, the reception unit 342, the specification unit 343, the selection unit 344, the notification unit 345, and the update unit 346.

[0056] The registration unit 341 is an example of the above-described registration unit 11. When the registration unit 341 receives a registration request from the information terminal 100, it extracts a face image as the biometric information of the rescued person U1 from the personal information of the rescued person U1 included in the registration request. Then, the registration unit 341 transmits a face information registration request including the extracted face image to the authentication device 200 via the network N. The registration unit 341 receives the user ID issued to the rescued person U1 from the authentication device 200 via the network N. Then, the registration unit 341 associates the received user ID 3121 with the personal information 3122, the health information 3123, and the condition information 3124 included in the registration request, and registers them in the memory unit 310 as the rescued person information 312.

[0057] Further, when the registration unit 341 receives a registration request from the mobile terminal 41 or the like, it issues a user ID for a rescue candidate U21 or the like based on the personal information included in the registration request. The registration unit 341 associates the issued user ID 3131 with the personal information, the attribute information 3132, the rescue response condition 3133, and the terminal information 3135 included in the registration request, and registers them in the memory unit 310 as the rescue candidate information 313. Note that when the personal information included in the registration request includes a face image of a rescue candidate U21 or the like, the registration unit 341 may transmit a face information registration request to the authentication device 200 and receive the user ID issued to the rescue candidate U21 or the like in the same manner as above.

[0058] FIG. 8 is a diagram showing an example of a pre-registration screen 610 for an injured person according to Embodiment 2. The pre-registration screen 610 for the injured person is displayed on the display unit of the information terminal 100 by an application operating on the information terminal 100. The pre-registration screen 610 for the injured person particularly shows an example of a screen for registering information disclosure conditions. The pre-registration screen 610 for the injured person includes a notification condition selection column 611, a disclosure information type selection column 612, a disclosure destination attribute selection column 613, and a registration button 614. The notification condition selection column 611 is a column for accepting selection of notification conditions for the information terminal 100 to notify a rescue request to the rescue support device 300. Here, it shows that "when an abnormal value of the heart rate of the wearable device appears" (when the vital information satisfies a predetermined condition) and "when the alert button of the application is pressed" (when a pressing operation on the alert button is detected) are selected. The disclosure information type selection column 612 is a column for accepting selection of the disclosure information type. Here, the disclosure information types include, but are not limited to, "age", "gender", "name of the underlying disease", and "location information". The disclosure destination attribute selection column 613 is a column for accepting selection of the disclosure destination attribute. Here, the disclosure destination attributes include, but are not limited to, "first aid training participants", "nurses", "ambulance crew candidates using a vehicle", and "doctors". The registration button 614 is a button for registering the information selected in each selection column when pressed. That is, when the registration button 614 is pressed, the information terminal 100 transmits a registration request including the items selected in each selection column to the authentication device 200. In response to this, the registration unit 341 of the rescue support device 300 performs registration according to the received registration request.

[0059] FIG. 9 is a diagram showing an example of the local government fire department cooperation screen 620 according to the second embodiment. The local government fire department cooperation screen 620 is displayed on the display unit of the information terminal 100 by an application operating on the information terminal 100. For example, the local government fire department cooperation screen 620 is displayed after the registration button 614 is pressed on the pre-registration screen 610 of the rescued person. The local government fire department cooperation screen 620 is a screen for obtaining consent regarding data linkage between an existing fire prevention and disaster prevention system (for example, the fire department server 500) and the information of the rescued person and the rescuer and the rescue situation. The local government fire department cooperation screen 620 includes a message display column 621, a non-consent button 622, and a consent button 623. The message display column 621 is a display column for a message asking for consent to data linkage. The message display column 621 displays, for example, a message such as "Do you consent to data linkage between the information of the rescued person and the rescuer and the rescue situation and the fire department server when an alert is issued that meets the notification conditions?", but is not limited thereto. The non-consent button 622 is a button for answering that consent to data linkage is not given. That is, when the non-consent button 622 is pressed, the information terminal 100 transmits a message indicating that consent to data linkage is not given to the rescue support device 300. Incidentally, when the non-consent button 622 is pressed, rescue support by the rescue support system 1000 cannot be received. In this case, the registration unit 341 may delete the rescued person information 312 of the corresponding rescued person U1 from the storage unit 310. The consent button 623 is a button for answering that consent to data linkage is given. That is, when the consent button 623 is pressed, the information terminal 100 transmits a message indicating that consent to data linkage is given to the rescue support device 300. In this case, the registration unit 341 may additionally register a flag indicating consent to data linkage in the rescued person information 312 of the corresponding rescued person U1.

[0060] FIG. 10 is a diagram showing an example of a pre-registration screen 630 for a rescuer according to Embodiment 2. The pre-registration screen 630 for a rescuer is displayed on the display unit of the mobile terminal 41 or the like by an application operating on the mobile terminal 41 or the like. The pre-registration screen 630 for a rescuer particularly shows an example of a screen for registering rescue response conditions. The pre-registration screen 630 for a rescuer includes a response content selection column 631, a condition selection column 632, a time zone selection column 633, and a registration button 634. The response content selection column 631 is a column for accepting the selection of rescue contents that the rescue candidate U21 or the like can handle. Here, it shows that "life rescue response for advanced first aid training" is selected. The response content selection column 631 also includes, but is not limited to, "initial response of a nurse" (emergency treatment response as a nurse) and "only support for transporting to the hospital by car" (transportation by vehicle). The condition selection column 632 is a column for accepting the selection of the geographical range, the applicable reward conditions, and the exclusion conditions that the rescue candidate U21 or the like can handle among the rescue response conditions. Here, it shows that "within 1 km or the like" is selected as the geographical range, "5,000 yen or more" is selected as the reward condition, and "accident" is selected as the exclusion condition. The time zone selection column 633 is a column for accepting the selection of the time zone that the rescue candidate U21 or the like can handle among the rescue response conditions. Here, it shows that "Saturday and Sunday" is selected as the day of the week and "9:00 - 18:00" is selected as the time zone. Note that the selection items and selection contents of the response content selection column 631, the condition selection column 632, and the time zone selection column 633 are not limited to these. The registration button 634 is a button for registering the information selected in each selection column when pressed. That is, when the registration button 634 is pressed, the mobile terminal 41 or the like sends a registration request including the items selected in each selection column to the authentication device 200. In response to this, the registration unit 341 of the rescue support device 300 performs registration according to the received registration request.

[0061] After the registration button 634 is pressed on the rescuer advance registration screen 630, the mobile terminal 41, etc., displays a screen equivalent to the municipal fire department collaboration screen 620 described above. When the disagreement button 622 or the agreement button 623 is pressed, the mobile terminal 41, etc., performs the same process as described above. That is, when the disagreement button 622 is pressed, the mobile terminal 41, etc., transmits to the rescue support device 300 a message indicating that the mobile terminal 41, etc., does not agree to the data collaboration. When the disagreement button 622 is pressed, the rescue support system 1000 does not select the rescue candidate U21, etc., as a rescuer. In this case, the registration unit 341 may delete the rescue candidate information 313 of the corresponding rescuer from the storage unit 310. The agreement button 623 is a button for responding to agree to the data collaboration. That is, when the agreement button 623 is pressed, the mobile terminal 41, etc., transmits to the rescue support device 300 a message indicating that the mobile terminal 41, etc., agrees to the data collaboration. In this case, the registration unit 341 may additionally register a flag indicating consent to data linkage in the rescue candidate information 313 of the corresponding rescue candidate U21 or the like.

[0062] Returning to FIG. 7, the explanation continues. The reception unit 342 is an example of the reception unit 12 described above. The reception unit 342 receives a rescue request from the information terminal 100. For example, the reception unit 342 receives the rescue request when vital sign information of the rescue recipient U1 detected by the information terminal 100 worn by the rescue recipient U1 satisfies a predetermined condition. At this time, the rescue request may include vital sign information of the rescue recipient U1 detected by the information terminal 100. The reception unit 342 also receives a response from the mobile terminal to the rescue request made by the notification unit 345, which will be described later. The reception unit 342 also receives the above-mentioned position report from the mobile terminal 41, etc.

[0063] The specific part 343 identifies the person to be rescued using the personal identification information included in the received rescue request. For example, when the personal identification information is a user ID, the specific part 343 extracts the user ID from the received rescue request. Also, when the personal identification information is biometric information, the specific part 343 identifies the person to be rescued U1 by performing biometric authentication on the biometric information included in the received rescue request. For example, when the biometric information is a face image, the specific part 343 causes the authentication device 200 to perform face authentication on the face image. Therefore, the specific part 343 may be called an authentication control part. Specifically, the specific part 343 extracts the face image from the received rescue request. Then, the specific part 343 transmits a face authentication request including the extracted face image to the authentication device 200 via the network N. Note that the specific part 343 may detect the user's face area from the face image and include the image of the face area in the face authentication request. Or, the specific part 343 may extract face feature information from the face area and include the face feature information in the face authentication request. After that, the specific part 343 receives the face authentication result from the authentication device 200 via the network N. And when the face authentication result indicates success, the specific part 343 identifies the user ID included in the face authentication result. Note that when the rescue request includes terminal identification information instead of personal identification information, the specific part 343 identifies the user ID 3121 associated with the terminal identification information of the person to be rescued information 312.

[0064] The selection part 344 is an example of the selection part 13 described above. The selection part 13 selects a rescuer from among a plurality of rescue candidates based on the disclosure information type 31242 and the disclosure destination attribute 31243 of the person to be rescued U1 related to the rescue request, and the attribute information 3132 and the rescue response condition 3133. Specifically, the selection part 344 may select, as the rescuer, a rescue candidate whose rescue content that can be corresponded by the attribute information included in the disclosure destination attribute 31243 is the rescue response condition 3133 from among the plurality of rescue candidates. Or, the selection part 344 may select, as the rescuer, a rescue candidate whose attribute information matches the attribute information 3132 included in the disclosure destination attribute 31243.

[0065] Further, the selection unit 344 may select, as the rescuer, a rescue candidate whose rescued person information 312 corresponding to the information type included in the disclosure information type 31242 satisfies the rescue response condition 3133 from among a plurality of rescue candidates. Further, the selection unit 344 may select the rescuer in further consideration of the current position included in the rescue request, the current position 3134 of each rescue candidate, and the geographical range included in the rescue response condition 3133. Further, the selection unit 344 may select the rescuer in further consideration of the vital information included in the rescue request.

[0066] Further, the selection unit 344 selects the rescuer using the condition information 3124 corresponding to the rescued person specified by the specifying unit 343. Further, the selection unit 344 may select, from among a plurality of fire departments, the fire department having jurisdiction over the current position included in the rescue request, and select the fire department server 500 belonging to the fire department.

[0067] The notification unit 345 is an example of the above-described notification unit 14. The notification unit 345 notifies the mobile terminal of the rescuer selected by the selection unit 344 of the rescue request for the rescued person. Specifically, the notification unit 345 specifies the terminal information 3135 of the rescuer selected by the selection unit 344 from among the rescue candidate information 313. Further, the notification unit 345 acquires the information included in the disclosure information type 31242 of the rescued person U1 from among the rescued person information 312. Then, the notification unit 345 transmits, via the network N, a rescue request including the acquired information regarding the rescued person U1 to the IP address corresponding to the specified terminal information 3135.

[0068] In addition, the notification unit 345 notifies the fire department server 500 of the notification content corresponding to the response from the mobile terminal to the emergency medical assistance request. When the response from the mobile terminal indicates acceptance of the emergency medical assistance request, the notification unit 345 notifies the fire department server 500 of the information about the victim U1 and the accepted emergency medical assistance candidate information 313 as the notification content. On the other hand, when the response from the mobile terminal indicates non-acceptance of the emergency medical assistance request, the notification unit 345 notifies the fire department server 500 of the information about the victim U1 as the notification content. The information about the victim U1 includes the victim information 312 and the current location included in the emergency medical assistance request. Note that the notification unit 345 shall notify the fire department server 500 selected by the selection unit 344.

[0069] The update unit 346 updates the current location 3134 of the corresponding emergency medical assistance candidate information 313 according to the location report received by the reception unit 342. Specifically, the update unit 346 extracts the current location, terminal identification information, etc. from the location report, and identifies the emergency medical assistance candidate information 313 corresponding to the terminal identification information, etc. Then, the update unit 346 updates the extracted current location as the current location 3134 of the identified emergency medical assistance candidate information 313. In addition, when the update unit 346 receives a notification of the completion of the emergency medical assistance from the mobile terminal of the emergency medical assistance provider, the update unit 346 updates the emergency medical assistance history 3136 of the corresponding emergency medical assistance candidate information 313.

[0070] Returning to FIG. 3, the description will continue. The fire department server 500 is an example of an emergency institution server and is an information processing device operated in a fire department that has jurisdiction over the current location of the person to be rescued. The fire department server 500 receives the notification content corresponding to the response from the mobile terminal to the rescue request and performs processing according to the notification content. Specifically, the fire department server 500 registers the notification content received from the rescue support device 300 as the rescue situation. In addition, the fire department server 500 receives the rescue situation from the mobile terminal 41 etc. during rescue and updates the rescue situation. For example, when it is received that the mobile terminal that requested rescue in the rescue support device 300 has accepted, the fire department server 500 receives the information about the person to be rescued and the rescuer information from the rescue support device 300 as the notification content (rescue situation). And when the fire department server 500 receives a situation report of the person to be rescued from the mobile terminal of the rescuer, it updates the rescue situation according to the situation report. Also, when non-acceptance is received from any of the mobile terminals that requested rescue in the rescue support device 300, the fire department server 500 receives the information about the person to be rescued U1 from the rescue support device 300 as the notification content (rescue request). And the fire department server 500 instructs the departure of the emergency vehicle for the rescue of the person to be rescued based on the received notification content.

[0071] FIG. 11 is a block diagram showing the configuration of the fire department server 500 according to the second embodiment. The fire department server 500 includes a storage unit 510, a memory 520, a communication unit 530, and a control unit 540. The storage unit 510 is an example of a storage device such as a hard disk or a flash memory. The storage unit 510 stores a program 511 and rescue situation information 512. The program 511 is a computer program in which the processing of the rescue support method in the fire department server 500 according to the second embodiment is implemented.

[0072] The rescue situation information 512 is information for managing the rescue situation. The rescue situation information 512 has the rescued person information 5121, the rescuer information 5122, the rescue situation 5123, and the current location 5124 associated therewith. The rescued person information 5121 is information on the rescued person notified from the rescue support device 300. The rescuer information 5122 is information on the rescuer notified from the rescue support device 300. The rescue situation 5123 is information indicating the rescue situation by the rescuer for the rescued person. The rescue situation 5123 includes, for example, the date and time, the rescue details of the rescuer, the health status of the rescued person, and the like. The current location 5124 is the location information of the rescuer's mobile terminal.

[0073] The memory 520 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information during the operation of the control unit 540. The communication unit 530 is a communication interface with the network N.

[0074] The control unit 540 is a processor, that is, a control device for controlling each component of the fire department server 500. The control unit 540 causes the memory 520 to read the program 511 from the storage unit 510 and executes the program 511. Thereby, the control unit 540 realizes the functions of the reception unit 541, the update unit 542, and the permission unit 543.

[0075] The reception unit 541 receives the notification content from the rescue support device 300. The notification content includes information about the rescued person, for example, the rescued person information 312 and the current location of the rescued person U1. In particular, when the rescuer accepts the rescue, the notification content includes the rescue candidate information 313. Further, the reception unit 541 receives the rescue situation from the mobile terminal 41 etc. of the rescue support device 300 during the rescue. In particular, the reception unit 541 receives the current location from the mobile terminal 41 etc. during the rescue. Also, when a rejection is received from any of the mobile terminals that requested rescue in the rescue support device 300, the reception unit 541 receives the information about the rescued person U1 from the rescue support device 300 as the notification content (rescue request).

[0076] The update unit 542 updates the ambulance situation information 512 based on the received notification content. Specifically, the update unit 542 generates the ambulance situation information 512 by associating the injured person information 5121, the ambulance personnel information 5122, and the ambulance situation 5123 included in the notification content, and registers it in the storage unit 510. In addition, the update unit 542 updates the ambulance situation information 512 based on the received ambulance situation 5123 and the current location 5124.

[0077] When the permission unit 543 receives an ambulance request from the ambulance support device 300, it instructs the departure of the ambulance vehicle for the rescue of the injured person based on the current location of the injured person U1 included in the notification content.

[0078] In addition, as an emergency organization that performs data linkage with the ambulance support device 300 according to the second embodiment, in addition to the fire departments of the above-mentioned local governments, there is an emergency consultation center (in the case of Japan, the destination reached by calling the phone number #7119, etc.). In that case, the server of the emergency consultation center may be used together with the fire department server 500 or instead of the fire department server 500. Then, in the local government fire department linkage screen 620 shown in FIG. 9, non-consent or consent to data linkage with the emergency consultation center may be received.

[0079] FIG. 12 is a flowchart showing the flow of the ambulance support process of the ambulance support device 300 according to the second embodiment. First, the reception unit 342 receives an ambulance request from the information terminal 100 via the network N (S410). Next, the identification unit 343 performs an injured person identification process based on the received ambulance request (S420). For example, the identification unit 343 identifies the injured person by face authentication as described above. Alternatively, the identification unit 343 identifies the injured person as described above based on the personal identification information or terminal identification information included in the ambulance request.

[0080] Subsequently, the selection unit 344 selects a rescuer based on the rescued person information 312 of the identified rescued person and the rescue response conditions 3133 (S430). Here, when there are multiple rescue candidates who meet the condition information 3124 and the rescue response conditions 3133, the selection unit 344 shall select the rescue candidate with a higher degree of condition matching as the rescuer. For example, it is assumed that the selection unit 344 selects the rescue candidate U21. Then, the notification unit 345 notifies the mobile terminal 41 of the selected rescuer U21 of the rescue request (S440). That is, the reception unit 342 transmits the rescue request to the mobile terminal 41 via the network N. In response to this, the mobile terminal 41 responds whether it accepts or rejects the rescue request according to the input of the rescue candidate U21.

[0081] Then, the reception unit 342 receives whether the rescue request is accepted or rejected from the mobile terminal 41 via the network N. Then, the reception unit 342 determines whether the rescue request has been accepted (S450). If the rescue request has been accepted, the notification unit 345 notifies the fire department server 500 via the network N of the rescued person information 312 of the rescued person U1 and the rescue candidate information 313 of the rescue candidate U21 (S460).

[0082] If it is determined in step S450 that the rescue request has not been accepted, the selection unit 344 determines whether other rescuers can be selected (S470). For example, in step S430, the selection unit 344 determines whether there are multiple rescue candidates who meet the conditions and whether there are unselected rescue candidates. If it is determined that other rescuers can be selected, the process proceeds to step S430.

[0083] On the other hand, when other rescuers are not selectable in step S470, the notification unit 345 notifies the fire department server 500 via the network N of the rescue request for the victim U1 (S480). In addition, not limited to the case where other rescuers are not selectable in step S470, if a certain period of time (for example, several tens of minutes) or more has elapsed since the first rescue request in step S440 and no acceptance has been received from any rescuer, the notification unit 345 may execute step S480. For example, if there is no response from the notified mobile terminal for a certain period of time or more in step S450, the notification unit 345 may execute step S480.

[0084] FIG. 13 is a sequence diagram showing the flow of the rescue support process according to the second embodiment. Here, it is assumed that the information terminal 100 of the victim U1 is a vital terminal. Further, it is assumed that the victim U1 has selected "when an abnormal value of the heart rate of the wearable device appears" in the notification condition selection column 611.

[0085] First, the information terminal 100 measures the vital information of the victim U1 and detects that the measured value is outside the predetermined range. That is, the information terminal 100 detects a change in the physical condition of the victim U1 (S511). Then, the information terminal 100 takes a pre-shot of the victim U1 and acquires the face image stored inside. In addition, the information terminal 100 acquires the latest current position. Then, the information terminal 100 transmits a rescue request including the face image and the current position to the rescue support device 300 via the network N (S512). In response to this, the reception unit 342 of the rescue support device 300 receives the rescue request from the information terminal 100. Then, the specifying unit 343 extracts the face image from the received rescue request and transmits a face authentication request including the extracted face image to the authentication device 200 via the network N (S513). In response to this, the authentication device 200 receives the face authentication request from the rescue support device 300 and performs the face authentication process as described above (S514). Here, it is assumed that the face authentication is successful, and the authentication device 200 includes the fact that the face authentication is successful and the user ID 211 of the victim U1 in the face authentication result. Then, the authentication device 200 transmits the face authentication result to the rescue support device 300 via the network N (S515).

[0086] The specifying unit 343 of the rescue support device 300 receives the face authentication result from the authentication device 200 and specifies the user ID included in the face authentication result. Then, the specifying unit 343 specifies the information 312 of the person to be rescued corresponding to the specified user ID 3121 (S516). Note that FIG. 13 shows the case where face authentication is performed as the person-to-be-rescued specifying process, but the rescue request may include personal identification information other than the face image or the terminal identification information of the information terminal 100. In that case, instead of steps S513 to S516, the specifying unit 343 specifies the user ID of the person to be rescued as described above based on the personal identification information or the terminal identification information included in the rescue request. Then, the selection unit 344 selects a rescuer as described above (S517). For example, assume that the person to be rescued U1 has selected "Name of the underlying disease" in the disclosure information type selection field 612 and has selected "Participants in the life-saving training" in the disclosure destination attribute selection field 613. Therefore, the specifying unit 343 specifies the name of the underlying disease as the disclosure information type 31242 of the person to be rescued U1 and the participants in the life-saving training as the disclosure destination attribute 31243. Then, the selection unit 344 selects, from a plurality of rescue candidates, a person whose rescue response condition 3133 includes "Life-saving response in advanced life-saving training", the current position included in the rescue request is within the geographical range of the rescue response condition 3133, and the date and time when the rescue request was received is included in the time zone of the rescue response condition 3133. Note that the selection unit 344 may add a condition for further selecting the attribute information 3132 corresponding to the disclosure destination attribute 31243. Here, assume that the rescue candidate U21 is selected.

[0087] Therefore, the notification unit 345 specifies the terminal information 3135 (mobile terminal 41) of the rescue candidate U21 from among the rescue candidate information 313. Further, the notification unit 345 acquires the information included in the disclosure information type 31242 of the person to be rescued U1 from among the information 312 of the person to be rescued. Then, the notification unit 345 transmits, to the mobile terminal 41, a rescue request including the acquired information regarding the person to be rescued U1 via the network N (S518). In response to this, the mobile terminal 41 displays a rescue request display screen in response to the received rescue request.

[0088] FIG. 14 is a diagram showing an example of an ambulance request display screen 640 according to the second embodiment. The ambulance request display screen 640 includes an ambulance request summary 641 and a detailed display button 642. The ambulance request summary 641 is information indicating the summary of the ambulance request. Here, it shows that the time when the ambulance request or the ambulance call was notified, the fact that it is in the vicinity of the mobile terminal 41, the fact that the person to be rescued has a pre-existing medical condition, and the fact that the urgency is high are displayed. However, the display content of the ambulance request summary 641 is not limited to these. The detailed display button 642 is a button for displaying detailed information of the person to be rescued regarding the ambulance request. When the mobile terminal 41 receives the pressing of the detailed display button 642 by the ambulance candidate U21, it displays an ambulance request response screen.

[0089] FIG. 15 is a diagram showing an example of a rescue request response screen 650 according to Embodiment 2. The rescue request response screen 650 includes an alert message 651, a rescued person summary position 652, detailed information 653, an acceptance button 654, and a non-acceptance button 655. The alert message 651 displays a message such as "Rescue alert nearby! With pre-existing conditions and high urgency", but is not limited thereto. The rescued person summary position 652 indicates the current position of the information terminal 100, that is, the location of the rescued person U1, on the map around the information terminal 100. The detailed information 653 shows the detailed information of the rescue request. For example, it shows that the rescued person U1 and the rescue candidate U21 are staying at the same hotel, that the rescued person U1 has a history of myocardial infarction, that the alert was sent at 9:23, and that 10,000 yen is promised as a reward. Also, when the information on the attending physician related to the disclosed information type 31242 of the rescued person U1 is included, the detailed information 653 may include the name and location of the medical institution to which the attending physician of the rescued person U1 belongs. However, the detailed information 653 is not limited thereto. The acceptance button 654 is a button for answering that the rescue request is accepted. The non-acceptance button 655 is a button for answering that the rescue request is not accepted (non-acceptance). The mobile terminal 41 transmits the fact of pressing the acceptance button 654 or the non-acceptance button 655 to the rescue support device 300. Here, it is assumed that the rescue candidate U21 has pressed the acceptance button 654. Therefore, the mobile terminal 41 transmits a message indicating that the rescue request is accepted to the rescue support device 300 via the network N (S519).

[0090] Therefore, the reception unit 342 of the rescue support device 300 receives a response to the rescue request (here, an acceptance message) from the mobile terminal 41. Then, the notification unit 345 transmits the notification content including the rescued person information 312 of the rescued person U1 and the rescue candidate information 313 of the rescue candidate U21 to the fire department server 500 via the network N (S520). In response to this, the fire department server 500 registers the received notification content as rescue situation information 512 in the storage unit 510 (S521).

[0091] After that, the rescue candidate U21 moves to the location indicated in the rescued person summary position 652 while holding the mobile terminal 41. Here, after the rescue candidate U21 accepts a rescue request, the mobile terminal 41 may periodically transmit the current position of the mobile terminal 41 to the rescue support device 300 and the fire department server 500 via the network N as a rescue situation.

[0092] Then, the rescue candidate U21 arrives at the location of the rescued person U1 and performs rescue. During the rescue, the rescue candidate U21 may input the condition of the rescued person U1 (confirmation of consciousness and breathing), the use of an AED, etc. each time using the mobile terminal 41. In addition, if there is an unconscious person (for example, lying down) when the rescue candidate U21 arrives, the rescue candidate U21 may take a picture of the person's face with the mobile terminal 41 and identify the rescued person U1 by face authentication. In that case, the mobile terminal 41 transmits a face authentication request including a photographed image of the face of the unconscious person to the rescue support device 300 via the network N. The rescue support device 300 controls face authentication as in steps S513 to S516 and returns the authentication result to the mobile terminal 41.

[0093] Then, the mobile terminal 41 transmits the rescue situation corresponding to the input of the rescue candidate U21 to the rescue support device 300 and the fire department server 500 via the network N (S522). In response to this, the fire department server 500 updates the rescue situation information 512 (rescue situation 5123 and current position 5124) according to the received rescue situation (S523). In addition, the rescue candidate U21 may report the rescue situation to the nearest fire department by phone instead of the application of the mobile terminal 41. Thus, the fire department side can precisely determine whether to dispatch an ambulance as needed.

[0094] Still, in conjunction with step S520, the notification unit 345 of the emergency support device 300 may transmit the current position of the rescuer who has received the emergency request and the scheduled arrival time of the rescuer to the information terminal 100 via the network N. In this case, the information terminal 100 displays the current position of the rescuer and the scheduled arrival time of the rescuer on the map around the information terminal 100 on the emergency waiting screen. Still, the emergency support device 300 may calculate the scheduled arrival time based on the current position of the rescuer and the current position of the victim U1. Alternatively, the mobile terminal 41 may receive an input of the scheduled arrival time from the potential rescuer U21 and transmit it to the emergency support device 300 in step S519. Also, while the potential rescuer U21 is moving towards the victim U1, the mobile terminal 41 may transmit the latest information on the current position and the scheduled arrival time of the mobile terminal 41 to the emergency support device 300 regularly or in response to an input from the potential rescuer U21. Then, the emergency support device 300 may appropriately transmit the received latest information on the current position and the scheduled arrival time to the information terminal 100. Then, the information terminal 100 updates the emergency waiting screen to display the current position and the scheduled arrival time, which are the received latest information. Thereby, when the victim U1 is conscious at the time of the emergency request, the victim U1 can grasp the current position of the rescuer and the scheduled arrival time of the rescuer in real time via the information terminal 100.

[0095] FIG. 16 is a diagram showing an example of the emergency waiting screen 680 for a victim according to the second embodiment. Still, in the example of FIG. 16, it is assumed that the rescuer (potential rescuer U21) is at a location different from the victim U1 (not in the same hotel) and is moving towards the victim U1 on foot while carrying the mobile terminal 41. The emergency waiting screen 680 for the victim includes the current position 681 of the rescuer, the message 682, and the scheduled arrival time 683. Still, the configuration of the emergency waiting screen 680 for the victim is not limited to these. The current position 681 of the rescuer indicates the current position of the rescuer who has received the emergency request on the map. The message 682 is a message for informing the victim that the rescuer has received the emergency request. The scheduled arrival time 683 is the scheduled arrival time of the rescuer described above.

[0096] Returning to FIG. 13, the description will continue. After that, it is assumed that the first-aid candidate U21 has completed the first-aid for the victim U1. Then, the first-aid candidate U21 inputs to the mobile terminal 41 that the first-aid has been completed. In response to this, the mobile terminal 41 transmits the fact that the first-aid has been completed to the first-aid support device 300 (and the fire department server 500) via the network N (S524). Then, the reception unit 341 of the first-aid support device 300 receives the fact that the first-aid has been completed from the mobile terminal 41. And the update unit 346 registers (updates) the first-aid history 3136 of the first-aid candidate information 313 of the first-aid candidate U21 (S525). Incidentally, the update unit 346 may update the first-aid history 3136 each time it receives the first-aid situation, similar to the fire department server 500.

[0097] Then, the notification unit 345 of the first-aid support device 300 transmits a thank-you input request to the information terminal 100 of the victim U1 via the network N (S526). For example, after the first-aid for the victim U1 is completed by the first-aid candidate U21, the notification unit 345 acquires the first-aid history 3136 of the first-aid for the victim U1 by the first-aid candidate U21, the reward condition (desired amount of gratitude) of the first-aid response condition 3133, the personal information of the first-aid candidate U21, etc. And the notification unit 345 makes this include a thank-you input request. Also, the notification unit 345 transmits a thank-you input request to the information terminal 100 via the network N based on the terminal identification information of the information terminal 100 of the victim U1. The information terminal 100 displays a thank-you input screen for the victim based on the thank-you input request received from the first-aid support device 300.

[0098] FIG. 17 is a diagram showing an example of a gratitude input screen 660 for the rescued person according to the second embodiment. The gratitude input screen 660 for the rescued person includes rescuer information 661, rescue record 662, gratitude information 663, evaluation information 664, comment 665, and send button 666. The rescuer information 661 is a display column for the rescuer who rescued the rescued person U1. Here, it shows that the information of the rescue candidate U21 is displayed. The rescue record 662 is a display column for the rescue status of the rescued person U1 by the rescue candidate U21. Here, the rescue record 662 includes, but is not limited to, the time, the status of the rescued person U1, the details of the rescue, etc. The gratitude information 663 is a display column for the prescribed gratitude payment amount that the rescued person U1 pays to the rescue candidate U21 and a selection column for the additional gratitude payment amount. Here, it shows that 10,000 yen is selected as the additional gratitude payment (a token of appreciation). The evaluation information 664 is an input column for the evaluation of the rescue response of the rescue candidate U21 by the rescued person U1. Here, the evaluation information 664 shows an example of a five - level evaluation, but is not limited to this. The comment 665 is an input column for the gratitude comment of the rescued person U1 to the rescue candidate U21. The send button 666 is a button for sending the input contents of the gratitude information 663, evaluation information 664, and comment 665. That is, when the send button 666 is pressed, the information terminal 100 sends the input contents of the gratitude information 663, evaluation information 664, and comment 665 as gratitude information to the rescue support device 300 via the network N (S527).

[0099] Accordingly, the reception unit 342 of the emergency rescue support device 300 receives the gratitude information from the information terminal 100. Then, the update unit 346 updates the evaluation information 3137 of the emergency rescue candidate U21 based on the gratitude information (S528). At this time, the update unit 346 may calculate the evaluation points from the municipality where the rescued person U1 resides based on the evaluation information included in the gratitude information. For example, the update unit 346 calculates the evaluation points according to a predetermined calculation formula based on the number of rescues and the evaluation information for each rescue response from the rescue history 3136 of the emergency rescue candidate U21. In addition, the update unit 346 may calculate the ranking of the evaluation points among the emergency rescue candidates in the municipality where the rescued person U1 resides. Furthermore, when the number of rescues is a certain number or more, or the evaluation points are a certain value or more, an additional incentive payment may be given from the municipality. Alternatively, instead of the incentive payment, incentives such as a certificate of commendation or local currency may be granted from the municipality. Then, the update unit 346 updates the evaluation information 3137 by including the calculated evaluation points and ranking.

[0100] Then, the emergency rescue support device 300 performs a money transfer process for the gratitude money included in the gratitude information to the account of the emergency rescue candidate (S529). For example, the emergency rescue support device 300 transmits a money transfer request for the gratitude money from the payment means information included in the personal information 3122 of the rescued person U1 to the account information of the transfer destination included in the personal information of the emergency rescue candidate U21 to the server (not shown) of the financial institution.

[0101] After that, the notification unit 345 transmits the gratitude report to the mobile terminal 41 via the network N (S530). Specifically, the notification unit 345 generates a gratitude report including the personal information 3122 of the rescued person U1, the evaluation information 3137 of the emergency rescue candidate U21, and the gratitude information. Then, the notification unit 345 transmits the gratitude report with the terminal information 3135 (mobile terminal 41) of the emergency rescue candidate U21 as the destination. Accordingly, the mobile terminal 41 displays a gratitude confirmation screen for the rescuer based on the gratitude report received from the emergency rescue support device 300.

[0102] FIG. 18 is a diagram showing an example of a rescuer gratitude confirmation screen 670 according to Embodiment 2. The rescuer gratitude confirmation screen 670 includes rescued person information 671, gratitude information 672, evaluation information 673, comment 674, point information 675, and a confirmation button 676. The rescued person information 671 is a display field for a part of personal information such as the name of the rescued person U1. The gratitude information 672 is a display field for the total amount and breakdown of the gratitude money from the rescued person U1 to the rescue candidate U21. The evaluation information 673 is a display field for evaluation information of the rescue candidate U21 by the rescued person U1. The comment 674 is a display field for a comment of the rescued person U1 on the rescue candidate U21. The point information 675 is a display field for evaluation information of the rescue candidate U21 by the municipality where the rescued person U1 resides. Here, the point information 675 indicates the number of rescues, evaluation points, ranking, etc., but is not limited thereto. For example, instead of or together with the point information 675, the balance of the local currency of the municipality may be displayed. The confirmation button 676 is a button for notifying that the rescue candidate U21 has confirmed the gratitude report. That is, when the confirmation button 676 is pressed, the mobile terminal 41 transmits a message indicating that the gratitude report has been confirmed to the rescue support device 300 via the network N. In response to this, the rescue support device 300 may receive the message indicating that the gratitude report has been confirmed and update the rescue history 3136.

[0103] Furthermore, after the rescue, the rescue support device 300 enables the rescued person to register their favorite rescuer this time. Then, when a rescue request is received from the same rescued person, the registered favorite rescuer can be preferentially selected for the rescue request. In that case, for example, the gratitude input screen 660 of the rescued person in FIG. 17 is provided with a selection input field for registering a favorite rescuer. When the rescued person U1 selects the registration of a favorite rescuer, when the information terminal 100 presses the send button 666, it transmits a request for registering a favorite rescuer (the user ID of the rescuer) together with gratitude information to the rescue support device 300 via the network N. In response, the reception unit 342 of the rescue support device 300 receives the gratitude information and the request for registering a favorite rescuer from the information terminal 100. Then, the update unit 346 temporarily registers the user ID of the rescuer (candidate) included in the request for registering a favorite rescuer in the condition information 3124 of the rescued person U1. And in step S530, the notification unit 345 transmits a request for approval of registering a favorite rescuer together with a gratitude report to the mobile terminal 41 via the network N. In response, the mobile terminal 41 displays a request for approval of registering a favorite rescuer as the rescuer of the rescued person U1 on the gratitude confirmation screen of the rescuer. For example, the gratitude confirmation screen 670 of the rescuer in FIG. 18 may further display a message indicating a request for approval of registering a favorite rescuer, and the confirmation button 676 may be used as an approval button. Then, when the mobile terminal 41 presses the approval button, it transmits to the rescue support device 300 via the network N that it has confirmed the gratitude report and the approval. In response, the rescue support device 300 updates the rescue history 3136 and updates the user ID of the rescuer (candidate) temporarily registered in the condition information 3124 of the rescued person U1 to a formal registration. Note that the temporary registration may be omitted. After that, when a second or subsequent rescue request is received from the rescued person U1, the rescue support device 300 makes a selection of the rescuer taking into account the user ID of the registered favorite rescuer (candidate). That is, a rescue request may be preferentially made to the registered favorite rescuer candidate.

[0104] In addition, when a second or subsequent rescue request is received from the same rescued person, the rescue support device 300 may identify the previous rescuer from the rescue history 3136 and preferentially select the rescuer for the rescue request.

[0105] As described above, according to this embodiment, an ambulance worker can be selected from among the ambulance candidates permitted by the victim to disclose information. Also, each ambulance candidate is notified of an ambulance request when the ambulance candidate's own ambulance response conditions are met. Therefore, in Embodiment 2 as well, similar to Embodiment 1 described above, the accuracy of matching between the victim and the ambulance worker can be improved. And even if the person is not a professional in first aid, the victim who meets the conditions can perform first aid quickly and effectively. Also, since the ambulance situation can be shared with the nearest fire department server, it can be utilized as first aid information. Furthermore, the ambulance candidate can register the desired amount of additional gratitude money as a reward condition. For example, the ambulance support device 300 may include the additional gratitude money amount registered by the victim U1 in the ambulance request. Therefore, ambulance candidates U21, etc. can confirm in advance the additional gratitude money amount displayed in the detailed information 653 of the ambulance request response screen 650, making it easier to accept. Thus, proactive ambulance services are promoted. Furthermore, ambulance candidates U21, etc. can grasp their own evaluation of the ambulance response from the point information 675 on the gratitude confirmation screen 670 for the ambulance worker. Therefore, the motivation of ambulance candidates U21, etc. for the next ambulance service is improved.

[0106] <Embodiment 3> This Embodiment 3 is an improved example of Embodiment 2 described above. For example, depending on the condition of the victim U1, it may be difficult for a first aid training participant to respond. On the other hand, a doctor who can provide ambulance response may not be in the vicinity of the victim U1. In that case, it is necessary to rely on a medical institution such as a hospital for the actual ambulance response for the victim U1. Therefore, the ambulance worker will transport the victim U1 to the medical institution by a vehicle such as a private car. However, since the ambulance worker's vehicle is an ordinary car, it is necessary to follow traffic rules such as traffic lights during the transportation to the medical institution, and there is a possibility that prompt first aid cannot be achieved. Therefore, in this Embodiment 3, the fire department or the like temporarily permits the vehicle used by the ambulance worker as an emergency vehicle and supports the vehicle to quickly pass through the road to the medical institution.

[0107] FIG. 19 is a block diagram showing the overall configuration of the ambulance support system 1000a according to Embodiment 3. Compared with the ambulance support system 1000 described above, the fire department server 500a is changed in the ambulance support system 1000a, and the traffic signal control system 700, traffic signals 710 and 720 are added. The traffic signal control system 700 is an information system operated by the traffic control center. The traffic signal control system 700 controls the signals to be lit for predetermined traffic signals 710, 720, etc. Further, FIG. 19 shows a situation where, after the ambulance candidate U22 receives an ambulance request, the injured person U1 is placed in the vehicle 421 of the ambulance candidate U22, and the injured person U1 is transported to a medical institution. Since other configurations are the same as those of the ambulance support system 1000, overlapping descriptions and illustrations are omitted as appropriate.

[0108] FIG. 20 is a block diagram showing the configuration of the fire department server 500a according to Embodiment 3. Compared with the fire department server 500 described above, the program 511a and the permission unit 543a are changed in the fire department server 500a, and the signal control unit 544 is added. The program 511a is a computer program in which the processing of the ambulance support method in the fire department server 500a according to Embodiment 3 is implemented.

[0109] The reception unit 541 receives vehicle information of the vehicle that transports the injured person and the position information of the mobile terminal from the mobile terminal of the ambulance staff who has received the ambulance request. The permission unit 543a permits the vehicle as an emergency vehicle based on the vehicle information. The signal control unit 544 transmits a request for traffic signal control to give priority to the vehicle to the traffic signal control system 700 from the position information until the transport destination of the injured person. Further, the reception unit 541 receives position information from the mobile terminal (mounted on the vehicle) while the vehicle is transporting the injured person. Then, the signal control unit 544 transmits the received position information to the traffic signal control system 700.

[0110] Here, it is assumed that the aid recipient U1 has previously selected "desiring a first-aider who uses a car" in the disclosure destination attribute selection field 613. Then, in step S516 of FIG. 13, the identification unit 343 identifies a person who desires vehicular support as the disclosure destination attribute 31243 of the aid recipient U1. Then, the selection unit 344 selects from the multiple aid candidates a person whose aid response condition 3133 includes "transportation by car," whose current location included in the aid request is within the geographic range of the aid response condition 3133, and whose date and time of receiving the aid request is within the time zone of the aid response condition 3133 (S517). Note that the selection unit 344 may further add a selection condition of having a driver's license to the attribute information 3132. Here, it is assumed that the aid candidate U22 is selected.

[0111] Therefore, the notification unit 345 transmits a rescue request to the mobile terminal 42 carried by the rescue candidate U22 (S518), and the mobile terminal 42 replies that the rescue request has been accepted (S519). After that, the rescue candidate U22 drives the vehicle 421 while still carrying the mobile terminal 42, and moves to the location indicated in the rescue recipient general position 652.

[0112] FIG. 21 is a sequence diagram showing the flow of emergency transport processing according to the third embodiment. Following the above, the rescue candidate U22 arrives at the rescue recipient U1 and starts rescue. Then, the rescue candidate U22 puts the rescue recipient U1 in the vehicle 421 and inputs a rescue start notification to the mobile terminal 42. At this time, the mobile terminal 42 transmits the rescue start notification to the fire department server 500a via the network N in response to the input by the rescue candidate U22 (S601). At this time, the mobile terminal 42 includes vehicle information (identification information such as a vehicle number) and the current location of the vehicle 421 in the rescue start notification. The mobile terminal 42 may also include the rescue situation in the rescue start notification.

[0113] In response to this, the reception unit 541 of the fire department server 500a receives a rescue start notification from the mobile terminal 42. Then, the permission unit 543 extracts vehicle information from the rescue start notification and permits the vehicle 421 as an emergency vehicle based on the extracted vehicle information (S602). Also, the permission unit 543 determines the medical institution to which the rescued person U1 is to be transported. Note that the medical institution of the transport destination may be included in the rescue start notification. In addition, the update unit 542 updates the rescue situation information 512 (rescue situation 5123 and current position 5124) based on the received rescue start notification (S603).

[0114] Then, the signal control unit 544 transmits a traffic signal control request including the position information and the transport destination included in the rescue start notification to the traffic signal control system 700 via the network N (S604). The traffic signal control system 700 determines the traffic signal to be controlled based on the position information and the transport destination included in the received traffic signal control request. For example, the traffic signal control system 700 determines the traffic signal 710 closest to the path from the position information to the transport destination as the traffic signal to be controlled. Therefore, the traffic signal control system 700 transmits a traffic signal control instruction to the traffic signal 710 via the network N (S605). For example, the traffic signal control system 700 may issue a traffic signal control instruction to turn the traffic signal in the traveling direction of the vehicle 421 green and turn the other surrounding traffic signals red.

[0115] Next, the vehicle 421, driven by the rescue candidate U22, starts moving (driving) to the medical institution to which the vehicle 421 is to be transported. At this time, the vehicle 421 transports the rescue recipient U1, the mobile terminal 42, and the rescue candidate U22. The mobile terminal 42 periodically acquires location information and transmits a rescue situation including the vehicle information and the location information to the fire department server 500a via the network N (S606). In response to this, the reception unit 541 of the fire department server 500a receives the rescue situation from the mobile terminal 42. The update unit 542 then updates the rescue situation information 512 (rescue situation 5123 and current location 5124) based on the received rescue situation (S607). The fire department server 500a then recognizes the vehicle as an emergency vehicle based on the vehicle information included in the rescue situation. Therefore, the signal control unit 544 transmits a traffic light control request including the location information included in the rescue situation and the transport destination determined above to the traffic light control system 700 via the network N (S608). The traffic light control system 700 determines the traffic light to be controlled based on the location information and transport destination included in the received traffic light control request. For example, the traffic light control system 700 determines the traffic light 720, which is the closest on the route to the transport destination based on the location information, as the traffic light to be controlled, and determines to release control of the traffic light 710. Therefore, the traffic light control system 700 transmits a traffic light control instruction (control release) to the traffic light 710 via the network N (S609). The traffic light control system 700 also transmits a traffic light control instruction to the traffic light 720 via the network N (S610).

[0116] Subsequently, it is assumed that the vehicle 421 arrives at the medical institution as the destination by the driving of the ambulance candidate U22. Then, the ambulance candidate U22 gets the victim U1 out of the vehicle 421 and transfers the rescue of the victim U1 to the staff of the medical institution. Subsequently, the ambulance candidate U22 inputs a rescue completion notice to the mobile terminal 42. At this time, the mobile terminal 42 transmits the rescue completion notice to the fire department server 500a via the network N in response to the input of the ambulance candidate U22 (S611). In response to this, the reception unit 541 of the fire department server 500a receives the rescue situation from the mobile terminal 42. Then, the update unit 542 updates the rescue situation information 512 according to the received rescue completion notice (S612). And the fire department server 500a recognizes the vehicle information included in the rescue completion notice as an emergency vehicle and recognizes the completion of the rescue. Therefore, the signal control unit 544 transmits a traffic signal control request including the position information included in the rescue completion notice and the determined destination to the traffic signal control system 700 via the network N (S613). The traffic signal control system 700 determines to cancel the control of the traffic signal 720 based on the position information and the destination included in the received traffic signal control request. Therefore, the traffic signal control system 700 transmits a traffic signal control instruction (control cancellation) to the traffic signal 720 via the network N (S614).

[0117] FIG. 22 is a diagram for explaining the concept of traffic signal control according to the third embodiment. Here, it shows that the vehicle 421 is permitted as an emergency vehicle and is moving to the hospital 730 as the destination. For example, the traffic signal control system 700 initially issues a traffic signal control instruction to make the traffic signal 711 green and the traffic signals 712, 713, and 714 red. After the vehicle 421 passes the traffic signal 711, the traffic signal control system 700 cancels the traffic signal control of the traffic signals 711 to 714. Subsequently, the traffic signal control system 700 issues a traffic signal control instruction to make the traffic signal 721 green and the traffic signals 722, 723, and 724 red. After the vehicle 421 arrives at the hospital 730 and a rescue completion notice is transmitted from the mobile terminal 42, the traffic signal control system 700 cancels the traffic signal control of the traffic signals 721 to 724.

[0118] In this way, this embodiment allows the rescuer to quickly transport the rescue recipient U1 to a medical institution in a vehicle such as a private car. In particular, since the location information during transportation is notified to the traffic light control system 700 via the fire department server 500a each time, the traffic light control system 700 can appropriately give priority to the passage of the vehicle.

[0119] The mobile terminal 42 may transmit the rescue status to the rescue support device 300 as needed. Alternatively, the fire department server 500a may transfer the rescue status to the rescue support device 300 every time the mobile terminal 42 receives the rescue status.

[0120] <Embodiment 4> The present embodiment 4 is a modified example of the above-described embodiment 3. The difference between the present embodiment 4 and embodiment 3 is that the rescue support device 300b makes a traffic light control request to the traffic light control system 700 when the rescue recipient U1 is transported by an emergency vehicle.

[0121] Fig. 23 is a block diagram showing the overall configuration of a rescue support system 1000b according to the fourth embodiment. The rescue support system 1000b is different from the rescue support system 1000a described above in that the rescue support device 300b is modified. The fire department server 500a has the same permission unit 543a as in Fig. 20, but may not have the signal control unit 544. Other configurations and situations are the same as those of the rescue support system 1000a, and therefore, overlapping explanations and illustrations will be omitted where appropriate.

[0122] 24 is a block diagram showing the configuration of a rescue support device 300b according to the present embodiment 4. In the rescue support device 300b, a program 311b and a notification unit 345b are changed and a signal control unit 347 is added compared to the above-described rescue support device 300. The program 311b is a computer program in which the processing of the rescue support method in the rescue support device 300b according to the present embodiment 4 is implemented.

[0123] The reception unit 342 receives vehicle information of the vehicle transporting the rescued person and location information of the mobile terminal from the mobile terminal of the rescuer who accepted the rescue request. The notification unit 345b notifies the fire department server 500a of the emergency vehicle permission application for the vehicle, including the vehicle information. If the vehicle is permitted as an emergency vehicle, the signal control unit 347 transmits a request for traffic light control to the traffic light control system 700 to give priority to the vehicle to the rescued person's destination based on the location information. Furthermore, the reception unit 342 receives location information from the mobile terminal (mounted on the vehicle) while the vehicle is transporting the rescued person. Then, the signal control unit 347 transmits the received location information to the traffic light control system 700. Note that the signal control unit 347 may be included in the notification unit 345b.

[0124] Fig. 25 is a sequence diagram showing the flow of emergency transport processing according to the fourth embodiment. As described above, the rescue candidate U22 accepts a rescue request from the rescue recipient U1 and moves to the rescue recipient U1 by vehicle 421, which is similar to the third embodiment. Fig. 25 also shows a case where communication between the mobile terminal 42 and the traffic light control system 700 is performed by the rescue support device 300b, as a main difference from Fig. 21.

[0125] Therefore, in response to the input from the rescue candidate U22, the mobile terminal 42 transmits a rescue start notification to the rescue support device 300b via the network N (S601a). In response, the reception unit 342 of the rescue support device 300b receives the rescue start notification from the mobile terminal 42. The notification unit 345b then extracts vehicle information and location information from the rescue start notification and transmits an emergency vehicle permission application including the extracted vehicle information and location information to the fire department server 500a via the network N (S601b). The fire department server 500a then authorizes the vehicle 421 as an emergency vehicle based on the vehicle information included in the received permission application and determines a medical institution to which the rescue recipient U1 should be transported. The fire department server 500a transmits a permission notification including information about the medical institution to the rescue support device 300b via the network N (S602a).

[0126] In response, the reception unit 342 of the emergency rescue support device 300b receives a permission notification from the fire department server 500a. Then, the update unit 346 updates the rescue situation (rescue history 3136) based on the received rescue start notification (S603a). Note that the fire department server 500a may update the rescue situation in the same manner as step S603 in FIG. 21.

[0127] Then, the signal control unit 347 transmits a traffic signal control request including the location information included in the rescue start notification and the destination included in the permission notification to the traffic signal control system 700 via the network N (S604a). Thereafter, the traffic signal control system 700 executes step S605 in the same manner as in FIG. 21.

[0128] Subsequently, while the vehicle 421 is traveling to the destination, the mobile terminal 42 periodically acquires location information and transmits the rescue situation including the vehicle information and the location information to the emergency rescue support device 300b via the network N (S606a). In response, the reception unit 342 of the emergency rescue support device 300b receives the rescue situation from the mobile terminal 42. Then, the update unit 346 updates the rescue situation (rescue history 3136) according to the received rescue situation (S607a). Then, the emergency rescue support device 300b recognizes the vehicle as an emergency vehicle from the vehicle information included in the rescue situation. Therefore, the signal control unit 347 transmits a traffic signal control request including the location information included in the rescue situation and the destination included in the permission notification to the traffic signal control system 700 via the network N (S608a). Thereafter, the traffic signal control system 700 executes steps S609 and S610 in the same manner as in FIG. 21.

[0129] After that, the vehicle 421 arrives at the medical institution at the destination, and the rescue candidate U22 transfers the rescue of the victim U1 to the staff of the medical institution. Then, the mobile terminal 42 transmits a rescue completion notification to the rescue support device 300b via the network N in response to the input of the rescue candidate U22 (S611a). In response to this, the reception unit 342 of the rescue support device 300b receives the rescue situation from the mobile terminal 42. Then, the update unit 346 updates the rescue situation (rescue history 3136) based on the received rescue completion notification (S612a). Then, the rescue support device 300b recognizes the emergency vehicle from the vehicle information included in the rescue completion notification and also recognizes the completion of the rescue. Therefore, the signal control unit 347 transmits a traffic signal control request including the position information included in the rescue completion notification and the destination included in the permission notification to the traffic signal control system 700 via the network N (S613a). Thereafter, the traffic signal control system 700 executes step S614 in the same manner as in FIG. 21.

[0130] Thus, also in this embodiment, the same effects as in Embodiment 3 can be achieved.

[0131] In addition, the mobile terminal 42 may appropriately transmit the rescue situation to the fire department server 500a. Alternatively, the rescue support device 300b may transfer the rescue situation to the fire department server 500a each time the mobile terminal 42 receives the rescue situation.

[0132] <Embodiment 5> This Embodiment 5 is a modification of Embodiments 2 to 4 described above. In this Embodiment 5, a biometric authentication function is incorporated into the rescue support device 300. For example, the rescue support device 300 according to this Embodiment 5 further associates and stores a face image or face feature information of the user with the user ID 3121 of the victim information 312. Then, the identification unit 343 of the rescue support device 300 according to this Embodiment 5 controls face authentication by comparing the face feature information of a plurality of persons with the face feature information of the user to be authenticated. That is, the identification unit 343 obtains a face authentication result by performing face authentication by comparing the face feature information extracted from the face area of the user with the face feature information stored in the storage unit 310.

[0133] Thus, also in the fifth embodiment, the same effects as those of the second to fourth embodiments described above can be achieved.

[0134] <Other Embodiments> In addition, in the third or fourth embodiment, as support for the rescuer when the rescuer transports the victim directly to the hospital, candidates for the destination of transportation may be presented based on information about the victim (disclosure information that satisfies the disclosure information type) and the current condition.

[0135] For example, in the case of the third embodiment, the rescue candidate U22 who has arrived at the location of the victim U1 inputs the condition of the victim U1 to the mobile terminal 42 when starting the rescue. The mobile terminal 42 transmits the condition of the victim U1 input by the rescue candidate U22 to the fire department server 500a via the network N. The fire department server 500a determines candidates for the medical institution as the destination of transportation (candidates for the destination of transportation) based on the notification content (disclosure information of the victim U1) notified in advance in step S520 etc. and the condition of the victim U1 received from the mobile terminal 42. At this time, the fire department server 500a may determine (select) two or more candidates for the destination of transportation from among a plurality of medical institutions. Then, the fire department server 500a notifies the mobile terminal 42 of one or more candidates for the destination of transportation determined (selected) via the network N. The mobile terminal 42 displays the notified candidates for the destination of transportation on the screen. Therefore, the rescue candidate U22 can grasp (quickly and accurately without checking by himself) the candidates for the destination of transportation of the victim U1 via the screen of the mobile terminal 42. Here, when the medical institution of the doctor regularly treating the victim U1 is included in the disclosure information of the victim U1, the fire department server 500a may prioritize the medical institution in determining the candidates for the destination of transportation. Thereby, a more suitable destination of transportation for the rescue of the victim U1 can be presented. Further, the fire department server 500a may determine (select) a plurality of candidates for the destination of transportation together with the reason for determination (reason for selection) from among a plurality of medical institutions, taking into account the distance from the current location of the victim U1, the pre-existing diseases of the victim U1, the current condition, etc.

[0136] In addition, when starting the rescue, the rescue candidate U22 may use the mobile terminal 42 to take a picture of the body of the victim U1 and cause the captured image to be transmitted to the fire department server 500a. That is, the mobile terminal 42 transmits the captured image of the victim U1 at the start of the rescue to the fire department server 500a via the network N. The fire department server 500a analyzes the received captured image to estimate the condition of the victim U1. Then, the fire department server 500a may determine the candidate for the transfer destination based on the disclosed information of the victim U1 and the estimated condition. In this case, it is assumed that the victim U1 has given prior consent to the photographing of his / her own body during the rescue and the provision of the captured image to the fire department server 500a.

[0137] Also, in the case of Embodiment 4, the destination for transmitting the condition and the captured image of the victim U1 by the mobile terminal 42 becomes the rescue support device 300b instead of the fire department server 500a. And the rescue support device 300b, similar to the fire department server 500a, estimates the condition of the victim U1 from the captured image and makes and notifies the determination of the candidate for the transfer destination.

[0138] FIG. 26 is a diagram showing an example of a display screen 690 of transport destination candidates. When the mobile terminal 42 or the like receives one or more transport destination candidates and the reasons for selection from the fire department server 500a or the ambulance support device 300b as described above, it displays the display screen 690 of the transport destination candidates. The display screen 690 of the transport destination candidates includes the current position 691 of the rescued person, transport destination candidates 6921 to 6923, a selection column 693, the reasons for selection 694, and a decision button 695. The current position 691 of the rescued person indicates the current position of the rescued person U1 on the map. The transport destination candidates 6921 to 6923 indicate the positions on the map of the transport destination candidates selected by the fire department server 500a or the ambulance support device 300b. Note that the transport destination candidates 6921 to 6923 may indicate marks indicating positions, names of medical institutions, or the like. For example, let the transport destination candidate 6921 be XXX Hospital, the transport destination candidate 6922 be YYY Hospital, and the transport destination candidate 6923 be ZZZ Emergency Medical Center. The selection column 693 is a column for accepting the selection of a transport destination candidate, and is, for example, a check box. The reasons for selection 694 is a display column for the reasons why each transport destination candidate was selected. For example, the transport destination candidate 6921 (A) is XXX Hospital, and the reason for selection indicates that it is the "family doctor" of the rescued person U1. The transport destination candidate 6922 (B) is YYY Hospital, indicating that it is the closest to the current position of the rescued person U1. The transport destination candidate 6923 (C) is ZZZ Emergency Medical Center, indicating that it can handle the condition of the rescued person U1 (although it is a bit farther away in terms of distance). The decision button 695 is a button that, when pressed, determines the transport destination candidate selected by the selection column 693 and notifies the fire department server 500a or the ambulance support device 300b. For example, the ambulance candidate U21 checks the position and the reasons for selection 694 of the transport destination candidates 6921 to 6923 on the display screen 690 of the transport destination candidates, checks "A" in the selection column 693, and presses the decision button 695. In response, the mobile terminal 42 notifies the fire department server 500a or the ambulance support device 300b via the network N that the selected transport destination candidate A "XXX Hospital" is the transport destination.

[0139] In the above-described embodiments, although described as a hardware configuration, it is not limited thereto. The present disclosure can also implement any processing by causing a CPU to execute a computer program.

[0140] In the above example, the program can be stored using various types of non-transitory computer readable media and supplied to the computer. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, DVD (Digital Versatile Disc), semiconductor memories (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). Also, the program may be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer readable media can supply the program to the computer via wired communication paths such as electric wires and optical fibers, or wireless communication paths.

[0141] Note that the present disclosure is not limited to the above-described embodiments and can be appropriately modified without departing from the gist. Also, the present disclosure may be implemented by appropriately combining each embodiment.

[0142] Some or all of the above-described embodiments may be described as follows in the appended claims, but are not limited thereto. (Appended Claim A1) a registration means for registering information disclosure conditions for a person to be rescued and rescue response conditions for each of a plurality of rescue candidates; a receiving means for receiving a rescue request from an information terminal of a predetermined rescue recipient; a selection means for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure condition of the rescue recipient related to the rescue request and the rescue response condition; a notification means for notifying a mobile terminal of the selected rescuer of a rescue request from the rescue recipient; A rescue support device comprising: (Appendix A2) The information disclosure conditions include attribute information of the relief candidate to be disclosed, The medical response conditions include medical response contents that each medical candidate can provide, The selection means selects, from the plurality of rescue candidates, the rescue candidate whose rescue response condition is rescue content that can be provided according to attribute information included in the information disclosure condition, as the rescue candidate. 1. A rescue assistance device as described in Appendix A1. (Appendix A3) the information disclosure conditions include types of information about the recipient that the recipient permits to be disclosed to the plurality of recipients, The selection means selects, from the plurality of rescue candidates, a rescue candidate whose information on the rescue recipient corresponding to the information type included in the information disclosure conditions satisfies the rescue response conditions. A rescue support device according to appendix A1 or A2. (Appendix A4) The rescue request includes a current location of the rescue recipient, The relief response conditions include a geographical range in which each relief candidate can respond, The selection means selects the rescuer by further taking into consideration the current location included in the rescue request, the current locations of each rescue candidate, and the geographical range included in the rescue response conditions. A rescue support device according to any one of appendices A1 to A3. (Appendix A5) The receiving means Receiving the rescue request including the vital information transmitted from the information terminal when the vital information of the rescued person detected in the information terminal worn by the rescued person satisfies a predetermined condition. The selection means Selecting the rescuer by further considering the vital information included in the rescue request The rescue support device according to any one of Appendices A1 to A4. (Appendix A6) The notification means notifies the emergency institution server of the notification content corresponding to the response from the mobile terminal to the rescue request. The rescue support device according to any one of Appendices A1 to A5. (Appendix A7) The reception means Receiving vehicle information of the vehicle for transporting the rescued person and position information of the mobile terminal from the mobile terminal of the rescuer who has accepted the rescue request. The notification means Notifying the emergency institution server of an application for permission of the emergency vehicle of the vehicle including the vehicle information. When the vehicle is permitted as an emergency vehicle, sending a request for traffic signal control to preferentially pass the vehicle to a predetermined traffic signal control system during the period from the position information to the destination of the rescued person. The rescue support device according to Appendix A6. (Appendix A8) The notification means When the vehicle receives the position information from the mobile terminal while transporting the rescued person, sending the position information to the traffic signal control system. The rescue support device according to Appendix A7. (Appendix A9) The rescue request includes the personal identification information of the rescued person. The rescue request further includes a specifying means for specifying the rescued person using the personal identification information included in the rescue request. The selection means selects the rescuer using the information disclosure condition corresponding to the specified rescued person. The rescue support device according to any one of Appendices A1 to A8. (Appendix A10) the personal identification information is biometric information of the rescue recipient, The identification unit identifies the person to be rescued by performing biometric authentication on the biometric information included in the rescue request. A rescue assistance device as described in Appendix A9. (Appendix B1) A rescue support device; an emergency service server; The rescue support device is a registration means for registering information disclosure conditions for a person to be rescued and rescue response conditions for each of a plurality of rescue candidates; a receiving means for receiving a rescue request from an information terminal of a predetermined rescue recipient; a selection means for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure condition of the rescue recipient related to the rescue request and the rescue response condition; a notification means for notifying a mobile terminal of the selected rescuer of a rescue request from the rescue recipient; Equipped with the notification means notifies the emergency service server of a notification content corresponding to a response from the mobile terminal to the rescue request; The emergency service server performs processing according to the notification content. Rescue support system. (Appendix B2) The notification means When the mobile terminal responds to the request for rescue by notifying the emergency service center server of information about the rescue recipient and the rescuer, The emergency service server The received notification content is registered as a rescue situation, When a status report of the rescue recipient is received from the mobile terminal, the rescue status is updated based on the status report. A rescue support system as described in Appendix B1. (Appendix B3) The notification means When the mobile terminal responds to the request for rescue by notifying the emergency service center server that the request for rescue has been rejected, the emergency service center server notifies the emergency service center server of information about the person to be rescued as the content of the notification. The emergency service server Based on the received notification, an emergency vehicle is instructed to depart to rescue the person being rescued. A rescue support system as described in Appendix B1 or B2. (Appendix B4) The emergency service server receiving, from the mobile terminal of the rescuer who has accepted the rescue request, vehicle information of a vehicle transporting the rescue recipient and location information of the mobile terminal; Authorizing the vehicle as an emergency vehicle based on the vehicle information; A request for traffic light control to give priority to the vehicle from the location information to the destination of the rescued person is transmitted to a predetermined traffic light control system. A rescue support system according to any one of appendices B1 to B3. (Appendix B5) The emergency service server When the vehicle receives the location information from the mobile terminal while transporting the person to be rescued, the vehicle transmits the location information to the traffic light control system. A rescue support system as described in Appendix B4. (Appendix C1) The computer registering information disclosure conditions for the person to be rescued and rescue response conditions for each of a plurality of rescue candidates; Accept a request for assistance from the information terminal of the designated person to be rescued, selecting a rescuer from among the plurality of rescue candidates based on the information disclosure conditions of the rescue recipient related to the rescue request and the rescue response conditions; notifying the mobile terminal of the selected rescuer of a rescue request from the rescue recipient; Relief support method. (Appendix D1) a registration process for registering information disclosure conditions for the person to be rescued and rescue response conditions for each of a plurality of rescue candidates; A reception process for receiving a rescue request from a specified information terminal of a person to be rescued, a selection process for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure conditions and the rescue response conditions of the person to be rescued regarding the rescue request, a notification process for notifying the selected rescuer's mobile terminal of the rescue request for the person to be rescued, and a non-transitory computer-readable medium storing a program for causing a computer to execute the above.

[0143] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above embodiments (and examples). Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

Explanation of Signs

[0144] 1 Rescue support device 11 Registration section 12 Reception section 13 Selection section 14 Notification section 1000 Rescue support system 1000a Rescue support system 1000b Rescue support system 100 Information terminal 200 Authentication device 210 Face information DB 211 User ID 212 Face feature information 220 Face detection section 230 Feature point extraction section 240 Registration section 250 Authentication section 300 Rescue support device 300b Rescue support device 310 Storage section 311 Program 311b Program 312 Information of person to be rescued 3121 User ID 3122 Personal information 3123 Health information 3124 Condition Information 31241 Notification Conditions 31242 Disclosure Information Type 31243 Recipient Attribute 313 Ambulance Candidate Information 3131 User ID 3132 Attribute Information 3133 Ambulance Response Conditions 3134 Current Location 3135 Terminal Information 3136 Ambulance History 3137 Evaluation Information 320 Memory 330 Communication Unit 340 Control Unit 341 Registration Unit 342 Reception Unit 343 Identification Unit 344 Selection Unit 345 Notification Unit 345b Notification Unit 346 Update Unit 347 Signal Control Unit Mobile Terminal Mobile Terminal Mobile Terminal 421 Vehicle 4m1 Vehicle 500 Fire Department Server 500a Fire Department Server 510 Storage Unit 511 Program 511a Program 512 Ambulance Situation Information 5121 Victim Information 5122 Ambulance Crew Information 5123 Ambulance Situation 5124 Current Location 520 Memory 530 Communication Unit 540 Control Unit 541 Reception Unit [[ID=8!]]542 Update Unit 543 Permission Unit 543a Permission Unit 544 Signal Control Unit 610 Pre-registration screen for recipients of assistance 611 Notification condition selection field 612 Disclosure information type selection field 613 Disclosure destination attribute selection field 614 Registration button 620 Municipal Fire Department Collaboration Screen 621 Message display field 622 Disagree button 623 Agree button 630 Pre-registration screen for rescuers 631 Response content selection field 632 Condition selection field 633 Time zone selection field 634 Registration button 640 Rescue request display screen 641 Relief request summary 642 Details button 650 Response screen for emergency response request 651 Alert Message 652 Outline location of rescued person 653 More Information 654 Accept button 655 Reject button 660 Thank you message input screen for the person receiving aid 661 Rescuer information 662 Relief Record 663 Reward Information 664 Rating Information 665 comments 666 Send button 670 Thank you confirmation screen for rescuers 671 Rescue recipient information 672 Reward Information 673 Rating Information 674 comments 675 points information 676 Confirm button 680 Screen showing the person waiting for assistance 681 Current location of rescuer 682 Messages 683 Estimated Arrival Time 690 Display screen of destination candidates 691 Current location of the casualty 6921 Candidate destination 6922 Candidate destination 6923 Candidate destination 693 Selection column 694 Reason for selection 695 Decision button 700 Signal control system 710 Signal 711 Signal 712 Signal 713 Signal 714 Signal 720 Signal 721 Signal 722 Signal 723 Signal 724 Signal 730 Hospital N Network U1 Casualty U21 Ambulance candidate U22 Ambulance candidate U2m Ambulance candidate

Claims

1. Registration means for registering the information disclosure conditions of the injured person and the rescue response conditions of each of a plurality of rescue candidates; Receiving means for receiving a rescue request from an information terminal of a predetermined injured person; Selection means for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure conditions of the injured person to whom the rescue request pertains and the rescue response conditions; Notification means for notifying the selected rescuer's mobile terminal of the rescue request for the injured person; Comprising: The information disclosure conditions include the amount of gratitude money that can be additionally paid to the rescuer Rescue support device.

2. Registration means for registering the information disclosure conditions of the injured person and the rescue response conditions of each of a plurality of rescue candidates; Receiving means for receiving a rescue request from an information terminal of a predetermined injured person; Selection means for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure conditions of the injured person to whom the rescue request pertains and the rescue response conditions; Notification means for notifying the selected rescuer's mobile terminal of the rescue request for the injured person; Comprising: The rescue response conditions include the reward conditions for the rescuer Rescue support device.

3. Registration means for registering the information disclosure conditions of the injured person and the rescue response conditions of each of a plurality of rescue candidates; Receiving means for receiving a rescue request from an information terminal of a predetermined injured person; Selection means for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure conditions of the injured person to whom the rescue request pertains and the rescue response conditions; Notification means for notifying the selected rescuer's mobile terminal of the rescue request for the injured person; Comprising: The notification means notifies the emergency institution server of the notification content according to the response from the mobile terminal to the rescue request, The receiving means: Receives vehicle information of the vehicle for transporting the injured person and the location information of the mobile terminal from the mobile terminal of the rescuer who has accepted the rescue request, The notification means: Notifies the emergency institution server of an application for permission of the vehicle as an emergency vehicle including the vehicle information, When the vehicle is permitted as an emergency vehicle, a request for traffic signal control for preferentially passing the vehicle is transmitted to a predetermined traffic signal control system during the period from the location information to the transport destination of the injured person Rescue support device.

4. A rescue support method executed by a computer, comprising: Registering the information disclosure conditions of the injured person and the rescue response conditions of each of a plurality of rescue candidates; Receive an ambulance request from the information terminal of a predetermined victim, Based on the information disclosure conditions of the victim related to the ambulance request and the ambulance response conditions, select an ambulance provider from among the plurality of ambulance candidate providers, Notify the selected ambulance provider's mobile terminal of the ambulance request for the victim, The information disclosure conditions include the amount of gratitude payment that can be additionally paid to the ambulance provider Ambulance support method.

5. An ambulance support method executed by a computer, Register the information disclosure conditions of the victim and the ambulance response conditions of each of the plurality of ambulance candidate providers, Receive an ambulance request from the information terminal of a predetermined victim, Based on the information disclosure conditions of the victim related to the ambulance request and the ambulance response conditions, select an ambulance provider from among the plurality of ambulance candidate providers, Notify the selected ambulance provider's mobile terminal of the ambulance request for the victim, The ambulance response conditions include the reward conditions for the ambulance provider Ambulance support method.

6. An ambulance support method executed by a computer, Register the information disclosure conditions of the victim and the ambulance response conditions of each of the plurality of ambulance candidate providers, Receive an ambulance request from the information terminal of a predetermined victim, Based on the information disclosure conditions of the victim related to the ambulance request and the ambulance response conditions, select an ambulance provider from among the plurality of ambulance candidate providers, An ambulance support method for notifying the selected ambulance provider's mobile terminal of the ambulance request for the victim, Notify the emergency institution server of the notification content according to the response from the mobile terminal to the ambulance request, Receive the vehicle information of the vehicle for transporting the victim and the position information of the mobile terminal from the mobile terminal of the ambulance provider who has accepted the ambulance request, Notify the emergency institution server of the application for permission of the vehicle as an emergency vehicle including the vehicle information, When the vehicle is permitted as an emergency vehicle, send a request for traffic signal control to give priority to the vehicle to a predetermined traffic signal control system during the period from the position information to the destination of the victim's transportation Ambulance support method.

7. A registration process for registering the information disclosure conditions of the victim and the ambulance response conditions of each of the plurality of ambulance candidate providers, A reception process for receiving an ambulance request from the information terminal of a predetermined victim, A selection process for selecting an ambulance provider from among the plurality of ambulance candidate providers based on the information disclosure conditions of the victim related to the ambulance request and the ambulance response conditions, A notification process for notifying the selected rescuer's mobile terminal of the rescue request for the rescued person, to be executed by a computer, The information disclosure condition includes the amount of gratitude money that can be additionally paid to the rescuer Rescue support program.

8. A registration process for registering the information disclosure conditions of the rescued person and the respective rescue response conditions of a plurality of rescue candidates, A reception process for receiving a rescue request from the information terminal of a predetermined rescued person, A selection process for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure condition and the rescue response condition of the rescued person related to the rescue request, A notification process for notifying the selected rescuer's mobile terminal of the rescue request for the rescued person, to be executed by a computer, The rescue response condition includes the reward condition for the rescuer Rescue support program.

9. A registration process for registering the information disclosure conditions of the rescued person and the respective rescue response conditions of a plurality of rescue candidates, A reception process for receiving a rescue request from the information terminal of a predetermined rescued person, A selection process for selecting a rescuer from among the plurality of rescue candidates based on the information disclosure condition and the rescue response condition of the rescued person related to the rescue request, A notification process for notifying the selected rescuer's mobile terminal of the rescue request for the rescued person, to be executed by a computer, The notification process notifies the emergency institution server of the notification content according to the response from the mobile terminal to the rescue request, The reception process is to receive the vehicle information of the vehicle for transporting the rescued person and the location information of the mobile terminal from the mobile terminal of the rescuer who has accepted the rescue request, The notification process is to notify the emergency institution server of the application for permission of the emergency vehicle of the vehicle including the vehicle information, When the vehicle is permitted as an emergency vehicle, a request for traffic signal control for preferentially passing the vehicle is transmitted to a predetermined traffic signal control system during the period from the location information to the transport destination of the rescued person Rescue support program.

Images