Servers, life-saving systems, methods, and programs

The server system addresses inefficiencies in existing life-saving systems by automating the selection of rescuers based on employee databases, ensuring timely and effective lifesaving activities without the need for manual data input.

JP2026080071AActive Publication Date: 2026-05-18MITSUBISHI ELECTRIC BUILDING SOLUTIONS CORP
View PDF 9 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
MITSUBISHI ELECTRIC BUILDING SOLUTIONS CORP
Filing Date
2024-10-31
Publication Date
2026-05-18

AI Technical Summary

Technical Problem

Existing life-saving systems require extensive manual input of information by both individuals needing rescue and potential rescuers, leading to inefficiencies and low practicality in preparing databases for lifesaving activities.

Method used

A server system that includes a determination unit to assess the need for lifesaving activities, an acquisition unit to gather suitability information from an existing employee database, and a selection unit to identify suitable rescuers based on training history and qualifications, eliminating the need for separate dedicated databases.

Benefits of technology

Enables efficient and appropriate implementation of lifesaving activities by automatically selecting qualified rescuers, reducing the administrative burden and ensuring timely and effective response.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026080071000001_ABST
    Figure 2026080071000001_ABST
Patent Text Reader

Abstract

To carry out life-saving activities appropriately using highly feasible methods. [Solution] The server 10 comprises a determination unit 315, an acquisition unit 302, and a selection unit 325. The determination unit 315 determines whether or not life-saving activities are necessary for employee EP1. The acquisition unit 302 acquires predetermined information from an employee DB 25 containing personal information of multiple members of a predetermined organization. The predetermined information is information related to the suitability of each of the multiple members for life-saving activities. If the determination unit 315 determines that life-saving activities are necessary, the selection unit 325 selects a life-saver from among the multiple members, according to the predetermined information, to be instructed to perform life-saving activities for employee EP1.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0004] , ,

[0005] , ,

[0001] The present disclosure relates to a server, a lifesaving system, a method, and a program.

Background Art

[0002] International Publication No. 2022 / 157865 (Patent Document 1) discloses a rescue support device. This rescue support device includes a registration unit, a reception unit, a selection unit, and a notification unit. The registration unit pre-registers information disclosure conditions input from a person to be rescued and rescue response conditions input from each of a plurality of rescue candidates. The reception unit receives a rescue request from an information terminal of a predetermined person to be rescued. The selection unit selects a rescuer from among a plurality of rescue candidates based on the information disclosure conditions of the person to be rescued to whom the rescue request pertains and the rescue response conditions. The notification unit notifies the mobile terminal of the selected rescuer of the rescue request for the person to be rescued.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] It is extremely important to appropriately perform lifesaving activities for a person who has fallen into a serious physical abnormality such as cardiac arrest (a person in need of lifesaving). According to the technique described in Patent Document 1, it is necessary to prepare a dedicated database in which various information of a person in need of lifesaving (the person to be rescued) and a plurality of lifesaving candidates (rescue candidates) is pre-registered. However, in order to prepare such a database, it is necessary for the person in need of lifesaving and the rescue candidates to input various conditions in advance. As a result, it may take a lot of labor. Therefore, the above-described support device may have low practicality.

[0005] This disclosure has been made to solve the problems described above, and its purpose is to provide servers, life-saving systems, methods, and programs that enable the proper and feasible implementation of life-saving activities. [Means for solving the problem]

[0006] The server described herein comprises a determination unit, a first acquisition unit, and a selection unit. The determination unit determines whether life-saving activities are necessary for the first target person. The first acquisition unit acquires predetermined information from a database containing personal information of multiple members of a predetermined organization. The predetermined information is information related to the suitability of each of the multiple members for life-saving activities. If the determination unit determines that life-saving activities are necessary, the selection unit selects a second target person from among the multiple members, according to the predetermined information, to be instructed to perform life-saving activities for the first target person. [Effects of the Invention]

[0007] According to this disclosure, life-saving activities can be carried out appropriately in a highly feasible manner. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows the hardware configuration of a life-saving system equipped with a server according to the embodiment. [Figure 2] This diagram shows an example of the data structure of an employee database. [Figure 3] This diagram shows an example of the data structure for occupancy location data. [Figure 4] This is a block diagram showing the functional configuration of a server according to the embodiment. [Figure 5] This flowchart shows an example of a process performed by the server in the embodiment. [Figure 6] This is a block diagram showing the functional configuration of a server according to Modification Example 1. [Figure 7] This flowchart shows an example of the process performed by the server in Modification Example 1. [Figure 8] This is a block diagram showing the functional configuration of the server in the modified example 6. [Figure 9] This is a block diagram showing the functional configuration of the server in the modified example 7. [Figure 10] This flowchart illustrates the detailed procedure for the process in which the server determines the steps for life-saving activities for an employee (S125 in Figure 5) in Modification Example 7. [Figure 11] This is a block diagram showing the functional configuration of the server according to Modification Example 8. [Figure 12] This flowchart shows an example of the process performed by the server in the modified example 8. [Modes for carrying out the invention]

[0009] Embodiments of this disclosure will be described in detail below with reference to the drawings. The same or corresponding parts in the drawings will be denoted by the same reference numerals and their descriptions will not be repeated. Each of the embodiments and its modifications may be combined with one another as appropriate.

[0010] In this disclosure, “life-saving activities” include primary life support, specified support activities, and secondary life support. Primary life support refers to measures that should be immediately performed on a person in serious physical distress (a person in need of life), and includes, for example, cardiac massage and the operation of an automated external defibrillator (AED). Support activities refer to activities to assist primary life support and include at least one of the following: checking the surroundings of the person in need of life and moving the person to a nearby safe place, speaking to the person in need of life to check for a response, and arranging (preparing) an AED. Secondary life support refers to measures performed after primary life support by medical professionals using advanced equipment in an ambulance or other facility such as a hospital.

[0011] Figure 1 is a diagram showing the hardware configuration of a life-saving system equipped with a server according to an embodiment. Referring to Figure 1, the life-saving system 1 is installed in facility F (an office building in this example) to support life-saving activities for persons in need of rescue, and comprises a server 10, an employee management system 20, a core system 30, and an input device 40. The life-saving system 1 further comprises an occupancy management system 50, a wearable device 60, a terminal device 70, and a camera 80.

[0012] The server 10 includes a storage device 110, a communication device 120, and a processing unit 130. The storage device 110 stores the personal information DB 112 and the life-saving manual DB 114. The personal information DB 112 contains personal information of several members of a predetermined organization. In this embodiment, this organization is a business operator with an office at facility F, and the members are employees of that business operator. The personal information DB 112 is generated based on the employee DB 25 (described later). The life-saving manual DB 114 includes procedure information 115. The procedure information 115 is predetermined as information that represents specific procedures for life-saving activities for a person in need of life, according to the condition of that person. For example, in the case of a person in need of life being in cardiac arrest, the procedure information 115 includes text and images representing at least one specific procedure for basic life-saving measures such as chest compressions and operation of an AED, as well as the aforementioned auxiliary activities. The communication device 120 communicates with systems or devices outside of the server 10.

[0013] The processing unit 130 includes memory and a processor (neither of which are shown). The memory includes ROM (Read Only Memory) and RAM (Random Access Memory). The ROM stores programs executed by the processor. The RAM functions as working memory. The processor is, for example, a CPU (Central Processing Unit) and performs various arithmetic operations according to the above program.

[0014] The employee management system 20 stores the employee DB 25. The employee DB 25 contains the personal information of a plurality of employees of the above-mentioned business operator. The employee DB 25 is generated based on the core data 35 stored in the core system 30 of the business operator. The core data 35 includes various personnel data of the business operator. The employee DB 25 will be described in detail later.

[0015] The input device 40 receives the input of various user operations. The user operations include operations for updating the personal information included in the employee DB 25.

[0016] The in-room management system 50 is provided for managing the in-room status of employees in each room of the facility F (specifically, the location of the room where each employee is). It stores the in-room location data 55. The in-room location data 55 will be described in detail later.

[0017] The wearable device 60 is, for example, a smartwatch and is worn by the employee EP1. The wearable device 60 measures biometric information such as the heart rate, blood pressure, or oxygen concentration in the blood of the employee EP1. The wearable device 60 uses a position detection system such as GPS (Global Positioning System) to obtain the position information PI of the employee EP1. The wearable device 60 is configured to communicate with the server 10. The wearable device 60 transmits the measured value MV of the biometric information and the position information PI to the server 10. When the health condition of the employee EP1 is good, the measured value MV is within a predetermined normal range. On the other hand, when the employee EP1 falls into a serious physical abnormality, the measured value MV deviates from the normal range. For example, when the employee EP1 falls into cardiac arrest, the measured value MV of the heart rate is below a predetermined reference value.

[0018] The terminal device 70 is, for example, a PC (Personal Computer) or a smartphone, and is used by employee EP2. The terminal device 70 is configured to communicate with the server 10. The terminal device 70 has unique information, such as a MAC (Media Access Control) address, associated with the identification number of employee EP2. The terminal device 70 includes a display device.

[0019] Camera 80 is a network camera installed within facility F and is configured to communicate with server 10. In this example, camera 80 is installed near the current location of employee EP1, and it takes a picture of employee EP1 and sends the captured image CI to server 10.

[0020] Figure 2 is a diagram illustrating an example of the data structure of the employee database 25. Referring to Figure 2, the employee database 25 contains various personal information. This personal information includes identification information 251, attribute information 252, training history information 255, qualification information 257, and physical and mental health information 259.

[0021] Identification information 251 indicates the identification information of each employee (e.g., employee number). Attribute information 252 is automatically generated based on core data 35 and indicates various attributes of each employee. Specifically, attribute information 252 includes gender information 253a, age information 253b, and department information 253c. Gender information 253a indicates the gender of each employee. Age information 253b indicates the age of each employee. Department information 253c indicates the department of the business operator to which each employee belongs. Attribute information 252 does not necessarily have to include all three pieces of information: gender information 253a, age information 253b, and department information 253c; it is sufficient if it includes at least one of these three pieces of information.

[0022] The training history information 255 includes history presence / absence information 256a and training date information 256b. The history presence / absence information 256a indicates whether each employee has a history of attending training related to life-saving activities. For example, among employees with identification information "001" to "006", employees with identification information "002", "004", and "006" have a history of attending the training. On the other hand, employees with identification information "001", "003", and "005" do not have such a history. The training date information 256b indicates the date on which each employee attended the training, if the employee has a history of attending the above training.

[0023] Qualification information 257 includes qualification status information 258a and acquisition date information 258b. Qualification status information 258a indicates whether each employee is qualified for life-saving activities. For example, among employees with identification information "001" to "006", employees with identification information "003" and "004" are qualified for life-saving activities. Employees with identification information "001", "002", "005", and "006" are not qualified. Acquisition date information 258b indicates the date on which each employee acquired the qualification, if the employee possesses the qualification.

[0024] The mental and physical health information 259 is generated using core data 35 and shows the results of the diagnosis of the employee's mental and physical condition in a health checkup conducted periodically for each employee. The mental and physical health information 259 includes information indicating whether each employee has physical problems (e.g., fractures, back pain, or other physical disabilities) or problems (disabilities) with mental or intellectual function. Each of the attribute information 252, training history information 255, qualification information 257, and mental and physical health information 259 corresponds to an example of "aptitude-related information" described below.

[0025] Figure 3 is a diagram illustrating an example of the data structure of the occupancy location data 55. Referring to Figure 3, the occupancy location data 55 indicates the occupancy location of each employee within facility F. This occupancy location is represented in units of arbitrarily demarcated areas within facility F. The occupancy location data 55 is generated, for example, based on records of employees entering and leaving each room in facility F. These records are created by an access control system (not shown) for managing such entry and exit. The occupancy location data 55 may also be generated by a location control system (not shown) for managing the location of employees with free addressing. The occupancy location data 55 may also be generated based on the location of the employee, which is identified using short-range communication between an air conditioner installed in facility F and each employee's mobile terminal (neither of which are shown). In this case, the occupancy location of each employee may be represented by two-dimensional or three-dimensional coordinates.

[0026] Referring again to Figure 1, if employee EP1 experiences a serious physical abnormality such as cardiac arrest, life-saving activities are required for employee EP1 (the person in need of life-saving care). Properly carrying out such life-saving activities is extremely important.

[0027] A conventional method is known in which various information about the person in need of rescue and multiple potential rescuers is pre-registered in a dedicated database, and the information of the person in need of rescue is compared with the information of multiple potential rescuers using this database, and a rescuer is selected from among the multiple potential rescuers based on the results of the comparison. However, in order to prepare such a database, the person in need of rescue and multiple potential rescuers must input various conditions in advance. As a result, this can be time-consuming and may have low feasibility.

[0028] Therefore, the server 10 according to this embodiment has a configuration for carrying out life-saving activities appropriately in a highly feasible manner. This point will be explained below.

[0029] Figure 4 is a block diagram showing the functional configuration of server 10 according to the embodiment. Referring to Figure 4, server 10 includes, as its functional configuration, an acquisition unit 302, a detection unit 305, an estimation unit 310, a determination unit 315, a decision unit 320, a selection unit 325, and an instruction unit 335.

[0030] The functions of the acquisition unit 302, detection unit 305, and instruction unit 335 are performed when the communication device 120 and processing unit 130 of the server 10 work together. The functions of the estimation unit 310, determination unit 315, decision unit 320, and selection unit 325 are performed when the CPU of the processing unit 130 executes a program stored in ROM.

[0031] The acquisition unit 302 acquires suitability-related information from the employee DB 25 of the employee management system 20. Suitability-related information is predetermined information related to each employee's suitability for life-saving activities, such as history presence / absence information 256a. Suitability-related information may also be qualification presence / absence information 258a. The acquisition unit 302 may acquire both history presence / absence information 256a and qualification presence / absence information 258a as suitability-related information. The acquisition unit 302 stores the acquired information (at least one of history presence / absence information 256a and qualification presence / absence information 258a) in the storage device 110 as at least one of history presence / absence information 256aa and qualification presence / absence information 258aa in the personal information DB 112. For example, if the acquisition unit 302 acquires both history presence / absence information 256a and qualification presence / absence information 258a, it stores these acquired pieces of information in the personal information DB 112 as history presence / absence information 256aa and qualification presence / absence information 258aa. In this example, the history information 256aa and qualification information 258aa in the personal information DB112 are the same as the history information 256a and qualification information 258a in the employee DB25.

[0032] The acquisition unit 302 acquires at least one of the history presence / absence information 256a and the qualification presence / absence information 258a by synchronizing with the employee DB 25 at predetermined time intervals (for example, every 24 hours). The acquisition unit 302 also functions as an update unit that updates the history presence / absence information 256aa and the qualification presence / absence information 258aa with the information thus acquired. If the acquisition unit 302 acquires only one of the history presence / absence information 256aa and the qualification presence / absence information 258aa, it stores only that one as the history presence / absence information 256aa or the qualification presence / absence information 258aa in the storage device 110.

[0033] The detection unit 305 detects when the measured value MV from the wearable device 60 falls below or exceeds a standard value. In this example, the measured value MV is the heart rate of employee EP1, and this measurement falls below the standard value.

[0034] The estimation unit 310 estimates the physical abnormality of employee EP1 according to the detection results of the detection unit 305. In this example, since employee EP1's heart rate is below the standard value, the estimation unit 310 estimates that employee EP1 is in a state of cardiopulmonary arrest. As a result, employee EP1 is determined to be in need of life-saving assistance.

[0035] The determination unit 315 determines whether life-saving activities are necessary for employee EP1 according to the estimation result of the estimation unit 310. In this example, since employee EP1 is estimated to be in a state of cardiopulmonary arrest, the determination unit 315 determines that life-saving activities are necessary for employee EP1. The determination unit 315 may also determine whether life-saving activities are necessary based on the captured image CI transmitted from the camera 80 (Figure 1). In this case, the determination unit 315 may, for example, determine a change in employee EP1's posture (in one example, falling over) based on the captured image CI and determine that life-saving activities are necessary.

[0036] If the determination unit 315 determines that life-saving activities are necessary, the decision unit 320 determines the procedure for life-saving activities for employee EP1 according to the estimation result of the estimation unit 310. Specifically, the decision unit 320 reads procedure information 115 from the life-saving manual DB 114 and determines the procedure for life-saving activities corresponding to the estimated state of employee EP1. For example, if employee EP1 is estimated to be in a state of cardiopulmonary arrest, the decision unit 320 determines the procedure for basic life support as the procedure for life-saving activities. The decision unit 320 may also determine the procedure for life-saving activities without using the life-saving manual DB 114. In one example, the decision unit 320 may use a pre-created machine learning model or generative AI (Artificial Intelligence) to determine the procedure for life-saving activities according to the estimated state of employee EP1.

[0037] The selection unit 325 selects a life-saver from among the employer's employees to be instructed to perform life-saving activities on employee EP1 according to the procedures determined by the decision unit 320, based on the suitability-related information acquired by the acquisition unit 302 (for example, at least one of the history presence / absence information 256aa and the qualification presence / absence information 258aa from the personal information DB 112). For example, when the selection unit 325 selects a life-saver according to the history presence / absence information 256aa, it selects an employee who (1) has a history of taking training related to life-saving activities as a life-saver from among the above-mentioned employees. In this case, the selection unit 325 selects an employee who has the identification information "002", "004", or "006" (Figure 2) as a life-saver. When the selection unit 325 selects a life-saver according to the qualification presence / absence information 258aa, it (2) selects an employee who has the qualifications related to life-saving activities as a life-saver. For example, the selection unit 325 selects one of the employees having the identification information "003" or "004" (Figure 2) as the life-saver. In this example, the selection unit 325 selects employee EP2 as the life-saver. If there are employees who have only (1), employees who have only (2), and employees who have both (1) and (2), the selection unit 325 may select the employee who has both (1) and (2) as the life-saver.

[0038] The instruction unit 335 transmits an instruction signal IS to the terminal device 70 instructing the rescuer (employee EP2) selected by the selection unit 325 to perform life-saving activities on employee EP1. For example, the terminal device 70 is identified based on unique information associated with the identification information of the selected rescuer, which is included in the identification information 251. The instruction signal IS includes information indicating the current location of employee EP1 based on location information PI, and information indicating the procedure for life-saving activities (e.g., the procedure for first aid). By transmitting the instruction signal IS to the terminal device 70, the current location of employee EP1, the instruction to perform life-saving activities, and the procedure for life-saving activities are displayed on the terminal device 70. As a result, employee EP2 is instructed to go to employee EP1's current location and perform life-saving activities on employee EP1 using the appropriate procedure.

[0039] Employees who have a history of receiving training and / or possess at least one qualification related to life-saving activities (hereinafter also referred to as "employees with training history / qualifications") tend to have a more accurate understanding of life-saving procedures than employees who do not have either the aforementioned training history or qualifications (hereinafter also referred to as "employees without training history / qualifications"). According to the selection unit 325, employees with training history / qualifications are selected as life-saver from among multiple employees. This ensures that employees who are likely to have an accurate understanding of life-saving procedures are instructed to carry out life-saving activities. As a result, life-saving activities can be appropriately carried out for employee EP1. Furthermore, any organization, including the above-mentioned business operator, basically has a database containing various personal information, such as the employee DB 25. In substance, the history information 256aa and qualification information 258aa are information obtained from the employee DB 25, so they can be easily prepared by effectively utilizing the existing personal information database. As a result, it is not necessary to go to the trouble of separately preparing a dedicated database for selecting life-savers, as in conventional methods. Therefore, the life-saving system 1 and server 10 according to the embodiment are highly feasible. Based on the above, it is possible to carry out life-saving activities appropriately in a highly feasible manner.

[0040] Figure 5 is a flowchart showing an example of processing performed by the server 10 in this embodiment. Before the start of this flowchart, the acquisition unit 302 acquires at least one of the history presence / absence information 256a and qualification presence / absence information 258a from the employee DB 25 as suitability-related information, and stores the acquired at least one of the history presence / absence information 256aa and qualification presence / absence information 258aa in the personal information DB 112. Hereinafter, steps will be abbreviated as "S". Steps S105 to S135 described below are performed when the CPU of the processing unit 130 of the server 10 executes a program stored in ROM.

[0041] Referring to Figure 5, the server 10 receives the measured value MV of employee EP1's biometric information from the wearable device 60 (S105). In this example, the biometric information is assumed to be heart rate. The server 10 detects that the measured value MV of the heart rate has fallen below a baseline value (S110).

[0042] Server 10 estimates the physical abnormality of employee EP1 according to the detection result in S110 (S115). In this example, Server 10 estimates that employee EP1 is in a state of cardiopulmonary arrest.

[0043] Server 10 determines whether life-saving measures are necessary for employee EP1 based on the estimation result in S115 (S119), and switches the processing according to that determination (S120). In this example, Server 10 determines that life-saving measures are necessary (YES in S120), so the process proceeds to S125. If Server 10 determines that life-saving measures are not necessary (NO in S120), the process ends.

[0044] Server 10 uses the life-saving manual DB 114 to determine the procedures for life-saving activities for employee EP1 (S125). For example, Server 10 determines the procedures for basic life support for employee EP1 as the procedures for life-saving activities.

[0045] Server 10 selects a life-saver according to at least one of the history information 256aa and the qualification information 258aa from the personal information DB 112 (S130). Specifically, Server 10 selects employees with training history / qualifications from among multiple employees as life-saver. Server 10 may select a life-saver according to at least one of the history information 256a and the qualification information 258a obtained from the employee DB 25 without storing the obtained information in the storage device 110.

[0046] Server 10 instructs employee EP2 to carry out life-saving activities by transmitting an instruction signal IS to terminal device 70 (S135).

[0047] As described above, according to this embodiment, at least one of the history information 256a and qualification information 258a of the employee DB 25 is effectively utilized to appropriately select a life-saver. As a result, there is no need to go to the trouble of separately preparing a dedicated database for selecting life-saver. Therefore, life-saving activities can be carried out appropriately in a highly feasible manner.

[0048] [Example 1] An employee's training history and qualifications can change over time. For example, an employee who has not previously received life-saving training may take such training and acquire accurate knowledge about life-saving activities, or an employee who did not have a life-saving qualification may acquire one. It is important to appropriately address such changes in circumstances.

[0049] Therefore, the server 10 according to Modification 1 has a configuration to address such problems. This will be explained below.

[0050] Figure 6 is a block diagram showing the functional configuration of server 10 according to Modification 1. Referring to Figure 6, when the determination unit 315 determines that life-saving activities are necessary, the acquisition unit 302 synchronizes with employee DB 25 immediately after the determination (specifically, within a predetermined time, in one example, within 1 second). As a result, the acquisition unit 302 acquires at least one of the history presence / absence information 256a and qualification presence / absence information 258a from employee DB 25 (in detail, the latest information thereof) as suitability-related information. The acquisition unit 302 updates personal information DB 112 (in detail, at least one of history presence / absence information 256aa and qualification presence / absence information 258aa) with the at least one of the above information acquired by synchronizing with employee DB 25 as described above. The selection unit 325 selects a life-saver according to the at least one of the above information acquired by synchronizing with employee DB 25 (at least one of the history presence / absence information 256aa and qualification presence / absence information 258aa in the updated personal information DB 112).

[0051] The acquisition unit 302 may update the personal information DB 112 as described above immediately after the procedure for life-saving activities has been determined by the decision unit 320. The acquisition unit 302 may also update the personal information DB 112 as described above by synchronizing with the employee DB 25 when it detects an update in the employee DB 25.

[0052] The training history and qualification status of each employee may change. In this case, at least one of the training history information 256a and qualification information 258a in the employee database 25 can be sequentially updated to the latest information by user operation based on reports from each employee using the input device 40. This information may also be automatically updated based on information entered or updated in other systems, such as the company's training management system.

[0053] According to the above function of the acquisition unit 302, immediately after it is determined that life-saving activities are necessary for employee EP1, at least one of the history presence / absence information 256aa and qualification presence / absence information 258aa in the personal information DB 112 is automatically updated to the latest version through synchronization between the server 10 and the employee DB 25. As a result, the latest status regarding each employee's training attendance history and qualifications is automatically reflected in the selection of life-saver by the selection unit 325. Consequently, even if the status regarding training attendance history and qualifications changes as described above, life-saver can be appropriately selected based on the latest status. Furthermore, according to this modified example 1, since at least one of the history presence / absence information 256aa and qualification presence / absence information 258aa is automatically updated, the administrator of the server 10 does not need to take the time to update at least one of the information. Therefore, life-saver can be appropriately selected while reducing the administrator's workload.

[0054] Figure 7 is a flowchart showing an example of the processing performed by the server 10 in Modification 1. Referring to Figure 7, this flowchart differs from the flowchart of the embodiment (Figure 5) in that S123 is added, but in other respects, it is basically the same as this flowchart unless otherwise specified. Therefore, a detailed explanation will not be repeated.

[0055] If it is determined that life-saving action is required for employee EP1 (after S120), the server 10 immediately synchronizes with the employee DB 25 of the employee management system 20. As a result, the server 10 obtains the latest information on at least one of the history information 256a and the qualification information 258a from the employee DB 25 as suitability-related information (S123), and updates the personal information DB 112. After determining the procedure for life-saving action (after S125), the server 10 selects a life-saver according to at least one of the history information 256aa and the qualification information 258aa in the updated personal information DB 112 (S130). S123 may be performed after S125 and before S130.

[0056] As described above, according to Modification 1, when it is determined that life-saving activities are necessary, at least one of the history information 256a and the qualification information 258a is obtained from the employee DB 25 immediately after the determination. This means that, compared to the case where a rescuer is selected based on the information obtained before it is determined that life-saving activities are necessary (when employee EP1 has not yet suffered a physical abnormality such as cardiac arrest), more recent information is obtained and a rescuer is selected based on it. As a result, more recent information regarding each employee's training history and qualifications is reflected in the rescuer selection result. Therefore, a rescuer can be selected more appropriately. In addition, the effort required of the server 10 administrator to update the personal information DB 112 can be reduced.

[0057] [Differentiation 2] When the selection unit 325 selects a life-saver according to the history information 256aa, two or more employees among the employer's multiple employees may have a history of receiving training related to life-saving activities. In this case, it is preferable to select the employee who is more likely to accurately remember the procedures for life-saving activities from among those two or more employees as the life-saver.

[0058] Therefore, in the modified example 2, the acquisition unit 302 acquires history information 256a and training date information 256b (Figure 2) from the employee DB 25 as suitability-related information, and the selection unit 325 selects a life-saver according to both the history information 256aa and the acquired training date information 256b. Specifically, the selection unit 325 prioritizes selecting as a life-saver employees the employees whose training dates are closest to the current date and time from among two or more employees who have a training attendance history. For example, the selection unit 325 selects as a life-saver the employee whose training date is closest to the current date and time from among three employees who have identification information "002", "004", and "006" (Figure 2). The selection unit 325 may also select as a life-saver any employee whose training date is within a predetermined period (for example, within one year) from the current date and time.

[0059] Among two or more employees with a training history, those whose training date is close to the current date are more likely to accurately remember the life-saving procedures than those whose training date is farther away. According to Modification 2, the training date information 256b in the employee database 25 is effectively utilized, and when two or more employees have a training history, the employee who is relatively more likely to accurately remember the life-saving procedures is preferentially selected as the life-saver. This allows for more appropriate execution of life-saving activities.

[0060] [Difference 3] When the selection unit 325 selects a life-saver in accordance with the qualification information 258aa, two or more employees among the employer's multiple employees may be qualified to perform life-saving activities. In this case, it is preferable to select the employee who is more likely to accurately remember the procedures for life-saving activities from among those two or more employees as the life-saver.

[0061] Therefore, the acquisition unit 302 acquires qualification status information 258a and acquisition date information 258b (Figure 2) from the employee DB 25 as suitability-related information, and the selection unit 325 selects a life-saver according to both the qualification status information 258aa and the acquired acquisition date information 258b. Specifically, the selection unit 325 prioritizes selecting as a life-saver employees the employee whose qualification acquisition date is closest to the current date and time from among two or more employees who have qualifications related to life-saving activities. For example, the selection unit 325 selects as a life-saver the employee whose qualification acquisition date is closest to the current date and time from among two employees who have identification information "003" and "004" (Figure 2). The selection unit 325 may also select as a life-saver any employee whose qualification acquisition date is within a predetermined period (for example, within one year) from the current date and time.

[0062] Among two or more qualified employees, those whose qualification acquisition date is closer to the present time are more likely to accurately remember the life-saving procedures than those whose qualification acquisition date is further away. According to Variation 3, the qualification acquisition date information 258b in the employee database 25 is effectively utilized, and when two or more employees are qualified, the employee who is relatively more likely to accurately remember the life-saving procedures is preferentially selected as the life-saver. This allows for more appropriate execution of life-saving activities.

[0063] [Differentiation Example 4] Life-saving activities may involve cardiac massage and other basic life support measures. Therefore, it may be preferable for the life-saver to be of the same gender as employee EP1. Alternatively, because life-saving activities require physical strength, such as cardiac massage, it may be preferable for the life-saver to be male or young. Alternatively, because employees in certain job roles tend to be better suited to life-saving activities, it may be preferable for the life-saver to be an employee in one of those roles. For example, employees in the general affairs department may be responsible for informing other employees about life-saving activities, and therefore tend to have a good understanding of life-saving procedures. Thus, attributes such as an employee's gender, age, or job role may be relevant to whether or not that employee is suitable to be a life-saver.

[0064] Therefore, in the modified example 4, the acquisition unit 302 acquires attribute information 252 (Figure 2) as suitability-related information from the employee DB 25 in place of or in addition to at least one of the history information 256aa and the qualification information 258aa, and the selection unit 325 selects a life-saver according to the acquired attribute information 252.

[0065] For example, the selection unit 325 selects a lifesaver from among at least one employee who has the same gender as employee EP1. The gender of employee EP1 is determined based on the gender information 253a included in the attribute information 252.

[0066] Alternatively, the selection unit 325 may select a lifesaver from among at least one employee who is male or young (for example, under 30 years of age). The age of employee EP1 is determined based on the age information 253b contained in the attribute information 252.

[0067] Alternatively, the selection unit 325 may select a lifesaver from among at least one employee belonging to a specific job category (for example, the general affairs department). The job category of employee EP1 is determined based on the department information 253c included in the attribute information 252.

[0068] According to Modification 4, the attribute information 252 of the employee database 25 is effectively utilized, and rescuers are appropriately selected according to the attributes of each employee. This allows for the proper implementation of rescue operations. Modification 4 may be combined with the embodiment or Modifications 1, 2, or 3.

[0069] [Difference 5] Life-saving activities may require physical strength, such as chest compressions as part of basic life support, and the ability to act calmly even in emergencies. Therefore, life-saving personnel must be in good physical and mental condition to the extent that they can properly perform life-saving activities. For example, it is undesirable for life-saving personnel to be unable to properly perform life-saving activities due to fractures, back pain, or other physical problems, or due to mental or intellectual function problems.

[0070] Therefore, in Modification 5, the acquisition unit 302 acquires mental and physical health information 259 (Figure 2) as suitability-related information from the employee DB 25, in place of or in addition to at least one of the history information 256aa and the qualification information 258aa, and the selection unit 325 selects a person to be saved according to the acquired mental and physical health information 259. Specifically, the selection unit 325 selects a person to be saved from among at least one employee who does not have a mental or physical health problem.

[0071] According to Modification 5, the mental and physical health information 259 in the employee database 25 is effectively utilized, and employees in good mental and physical condition are selected as life-saver. This allows for the appropriate implementation of life-saving activities. Modification 5 may be combined with the embodiment or with Modifications 1, 2, 3, or 4.

[0072] [Modification 6] The ability to initiate life-saving operations early is extremely important. Therefore, in Modification 6, the selection unit 325 selects a life-saver from among employees who are closest to employee EP1. The server configuration that enables such selection is described below.

[0073] Figure 8 is a block diagram showing the functional configuration of the server in Modification 6. Referring to Figure 8, Server 10A differs from Server 10 of the previously described embodiment (Figure 4) in that its functional configuration further includes an acquisition unit 304 and a calculation unit 345. In other respects, the hardware configuration and functional configuration of Server 10A are the same as those of Server 10 unless otherwise specified. Therefore, a detailed explanation will not be repeated.

[0074] The acquisition unit 304 acquires the occupancy location data 55 (Figure 3) from the occupancy management system 50 and includes it in the personal information DB 112. As a result, the occupancy location data 55aa is stored in the personal information DB 112 of the storage device 110. In this example, the occupancy location data 55aa in the personal information DB 112 is the same as the occupancy location data 55 from the occupancy management system 50.

[0075] The calculation unit 345 calculates the distance between each of the multiple employees and the rescuer according to the room location data 55aa and location information PI.

[0076] The selection unit 325 selects a life-saver based on at least one of the history information 256aa and the qualification information 258aa, and the calculation result of the calculation unit 345. Specifically, the selection unit 325 selects as a life-saver any employee who has at least one of the history of receiving life-saving training and qualifications, and who is within a predetermined distance (e.g., 30 meters) from employee EP1. For example, the selection unit 325 selects as a life-saver the employee who is closest to employee EP1 among the employees who have at least one of the above-mentioned training history and qualifications.

[0077] According to Modification 6, the presence location data 55 of the presence management system 50 is effectively utilized to prioritize the selection of an employee who has at least one of the above-mentioned training history and qualifications, and who is close to employee EP1, as a life-saver. This appropriately shortens the time it takes for the life-saver (employee EP2) to reach employee EP1's location. As a result, life-saving activities can be started early with a simple configuration. Modification 6 may be combined with the embodiment or Modifications 1, 2, 3, 4, or 5.

[0078] [Difference 7] If it is determined that life-saving measures are necessary for employee EP1, the emergency medical services must be immediately notified of this fact and the employee EP1's current location. The appropriate life-saving measures taken by the rescuers for employee EP1 may vary depending on the time it takes for the emergency medical services to arrive at employee EP1's current location and begin life-saving measures.

[0079] For example, if the time required is relatively short, paramedics can immediately arrive at employee EP1's current location and perform basic life support. Therefore, employee EP2 may not necessarily need to perform basic life support, but may only need to perform the aforementioned auxiliary activities (e.g., checking the surroundings of employee EP1 and moving employee EP1 to a nearby safe place, speaking to employee EP1 to check for a response, and arranging for an AED). Performing these auxiliary activities before the paramedics arrive at employee EP1's current location allows for the smooth execution of basic life support by the paramedics and the subsequent advanced life support. On the other hand, if the time required is relatively long, paramedics may not be able to immediately arrive at employee EP1's current location. Therefore, employee EP2 will need to perform both auxiliary activities and basic life support before the paramedics arrive.

[0080] Therefore, the server according to Modification 7 has a configuration for appropriately determining the procedures for life-saving activities by the rescuer based on the above-mentioned required time. This point will be explained below.

[0081] Figure 9 is a block diagram showing the functional configuration of the server in Modification 7. Referring to Figure 9, Server 10B differs from Server 10 of the previously described embodiment (Figure 4) in that its functional configuration further includes a transmitting unit 350 and a receiving unit 355. In other respects, the hardware and functional configuration of Server 10B are the same as those of Server 10 unless otherwise specified. Therefore, a detailed explanation will not be repeated.

[0082] The transmission unit 350 transmits location information PIA and life-saving information RI to the ambulance management server 405. Location information PIA is the same as location information PI transmitted from the wearable device 60 and indicates the current location of employee EP1 (person in need of life-saving). Life-saving information RI is generated based on the determination result of the determination unit 315 and indicates that life-saving activities are necessary for employee EP1.

[0083] The ambulance management server 405 is operated by the organization that manages ambulance dispatches (in this example, the fire department). The ambulance management server 405 determines that an ambulance dispatch is necessary based on the life-saving information RI. The ambulance management server 405 predicts the time required from when the ambulance arrives at the current location of employee EP1 until life-saving activities by the ambulance begin, based on the location information PIA. Specifically, the time required is predicted based on the current location of employee EP1, as indicated by the location information PIA, and the location of the fire department. The above time required may be replaced by the time it takes for the ambulance to transport employee EP1 to the hospital and for secondary life support to begin within the hospital. The ambulance management server 405 transmits time information TI to server 10B. The time information TI indicates the predicted time required. The receiving unit 355 receives the time information TI from server 10B.

[0084] The decision unit 320 determines, in addition to the estimation result from the estimation unit 310, the procedure for life-saving activities to be instructed to the rescuer when life-saving activities are required for employee EP1, according to the time information TI. For example, if the required time is shorter than the standard time, the decision unit 320 determines the procedure for auxiliary activities of basic life support for employee EP1 (e.g., checking the surroundings, checking for responsiveness, and arranging for an AED) as the procedure for life-saving activities to be instructed to the rescuer. On the other hand, if the required time is longer than or equal to the standard time, the decision unit 320 determines the procedure for auxiliary activities and basic life support (e.g., chest compressions, and operating an AED) as the procedure for life-saving activities to be instructed to the rescuer.

[0085] With this configuration, if the time required is relatively short, employee EP2 (life-saver) is instructed to perform auxiliary activities. This ensures that primary life support measures by the ambulance crew and subsequent secondary life support measures are carried out smoothly and reliably. On the other hand, if the time required is relatively long, employee EP2 is instructed to perform both auxiliary activities and primary life support measures. This ensures that life-saving activities can be properly carried out for employee EP1 even if it takes time for the ambulance crew to arrive.

[0086] Figure 10 is a flowchart illustrating the detailed procedure (S125 in Figure 5) in the modified example 7, where the server 10 determines the procedure for life-saving activities for employee EP1. Steps S205 to S225, described below, occur when the CPU of the server 10's processing unit 130 executes a program stored in ROM.

[0087] Referring to Figure 10, Server 10 transmits location information PIA and life-saving information RI to the ambulance management server 405 (S205). Server 10 receives time information TI from the ambulance management server 405 (S210).

[0088] Server 10 determines whether the aforementioned required time is equal to or greater than the standard time according to the time information TI (S215). If the required time is shorter than the standard time (NO in S215), Server 10 determines the procedure for auxiliary activities of basic life support for employee EP1 as the procedure for life-saving activities to be instructed by the rescuer (S220). If the required time is equal to or greater than the standard time (YES in S215), Server 10 determines the procedure for auxiliary activities and basic life support as the procedure for life-saving activities to be instructed by the rescuer (S225).

[0089] From the above, according to Modification 7, life-saving activities can be carried out appropriately according to the required time. Modification 7 may be combined with the embodiment or Modifications 1, 2, 3, 4, 5 or 6.

[0090] [Differentiation 8] Since life-saving activities for employee EP1 involve various actions, it is sometimes preferable for them to be carried out by multiple rescuers. In this case, it is preferable for the selection unit 325 to select these rescuers so that all of them are employees with the aforementioned training history / qualifications. However, there may be only a few employees with the training history / qualifications at facility F, or many of the employees near employee EP1 may not have the training history / qualifications. As a result, the selection unit 325 may select multiple rescuers from among the employees, including both employees with and without the training history / qualifications.

[0091] Basic life support, which includes cardiac massage and AED operation, requires precise knowledge of life-saving activities. On the other hand, auxiliary activities do not require as much precise knowledge of life-saving activities. Employees with training history / qualifications are relatively more likely to accurately understand the procedures for life-saving activities. In contrast, employees without training history / qualifications are relatively less likely to accurately understand the procedures for life-saving activities. Therefore, when the selection unit 325 selects multiple life-saver as described above, it is preferable for the instruction unit 335 to instruct each life-saver to perform life-saving activities according to their knowledge level. The following describes the server configuration that enables such instructions.

[0092] Figure 11 is a block diagram showing the functional configuration of a server according to Modification 8. Referring to Figure 11, Server 10C differs from Server 10 of the previously described embodiment (Figure 4) in that the selection unit 325 selects multiple survivors and the instruction unit 335 transmits instruction signals IS to each of the terminal devices 70 of these survivors.

[0093] The selection unit 325 selects several life-saver individuals from among several employees to be instructed to carry out the life-saving activities determined by the decision unit 320, based on at least one of the history information 256aa and the qualification information 258aa in the personal information DB 112. In this example, there are only two employees with training history / qualifications, so the selection unit 325 selects employees EP2A, EP2B, and EP2C as the aforementioned life-saver individuals.

[0094] Employee EP2A is an employee with training history / qualifications, and in this example, has training history related to life-saving activities. Employee EP2B is an employee with training history / qualifications, and in this example, has qualifications related to life-saving activities. Employees EP2A and EP2B each correspond to an example of a “first member” in this disclosure. Employee EP2C is an employee without training history / qualifications. Employee EP2C corresponds to an example of a “second member” in this disclosure. Terminal devices 70A, 70B, and 70C correspond to terminal devices 70 (Figure 4) of employees EP2A, EP2B, and EP2B, respectively.

[0095] Server 10C may further include a calculation unit 345 (Figure 8). In this case, the selection unit 325 selects the multiple rescuers from among multiple employees near employee EP1 according to at least one of the history presence / absence information 256aa and the qualification presence / absence information 258aa, and the calculation result of the calculation unit 345.

[0096] The instruction unit 335 divides the instructions for life-saving activities for employee EP1 and transmits instruction signals IS indicating the divided instructions to each rescuer's terminal device 70. Specifically, the instruction unit 335 transmits instruction signals ISA and ISB to terminal devices 70A and 70B, respectively, instructing employees EP2A and EP2B to perform basic life support as part of the life-saving activities for employee EP1. In addition, the instruction unit 335 transmits instruction signal ISC to terminal device 70C, instructing employee EP2C to perform auxiliary life-saving activities.

[0097] Instructional signal ISA includes information indicating the current location of employee EP1 and information indicating the procedure for operating an AED as part of basic life support. Instructional signal ISB includes information indicating the current location of employee EP1 and information indicating the procedure for chest compressions as part of basic life support. Instructional signal ISC includes information indicating the current location of employee EP1 and information indicating the procedure for assistive activities.

[0098] By transmitting instruction signals ISA, ISB, and ISC to terminal devices 70A, 70B, and 70C, terminal devices 70A, 70B, and 70C display screens showing employee EP1's current location, instructions for performing a corresponding life-saving activity, and the procedure for that activity. As a result, employees EP2A, EP2B, and EP2C are instructed to go to employee EP1's current location and perform the corresponding life-saving activity on employee EP1. For example, employee EP2A is instructed to operate an AED on employee EP1. Employee EP2B is instructed to perform chest compressions on employee EP1. Employee EP2C is instructed to perform an auxiliary activity.

[0099] Figure 12 is a flowchart showing an example of the processing performed by the server 10 in the modified example 8. This flowchart is executed after S125 in Figure 5, replacing S130 and S135. S130A and S135A, described below, occur when the CPU of the processing unit 130 of the server 10 executes the program stored in ROM.

[0100] Referring to Figure 12, the server 10 selects multiple rescuers according to at least one of the history information 256aa and qualification information 258aa from the personal information DB 112 (S130A). The server 10 instructs each rescuer to perform the life-saving activity corresponding to that rescuer (S135A). For example, the server 10 instructs employees EP2A, EP2B, and EP2C to operate an AED, perform cardiac massage, and perform auxiliary activities, respectively, by sending instruction signals ISA, ISB, and ISC to terminal devices 70A, 70B, and 70C. After S135A, the process ends.

[0101] Thus, according to Modification 8, employees EP2A and EP2B are instructed to perform basic life support if they are selected as life-saver. On the other hand, if employee EP2C is selected as life-saver, they are instructed to perform auxiliary activities. This ensures that life-saving activities for employee EP1 are appropriately instructed to each employee according to their knowledge level. As a result, life-saving activities can be carried out smoothly as a whole. Modification 8 may be combined with Embodiment or Modifications 1, 2, 3, 4, 5, 6, or 7.

[0102] [Other variations] In the above, the life-saving system 1 is assumed to be applicable to an office building as facility F, but it may also be applied to a hotel building. In this case, the employee DB 25 (or personal information DB 112) is replaced by a management database containing various personal information of hotel employees and customers. The room location data 55 may be replaced by data indicating the room location of each user, determined by at least one of the following: (1) user-specific lock / unlock records of electronic keys used to lock / unlock the doors of hotel rooms, or (2) user-specific usage records of elevators that can restrict user destinations using electronic keys.

[0103] Alternatively, the life-saving system 1 may be applied to the buildings of educational institutions such as universities. In this case, the employee database 25 (or personal information database 112) is replaced by a management database containing various personal information of faculty, staff, and students of the educational institution. The location data 55 may then be replaced by data representing the location of each faculty member and student, recorded in an attendance management system that manages attendance at lectures.

[0104] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims rather than by the foregoing description, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of symbols]

[0105] 10, 10A, 10B, 10C Servers, 20 Employee Management System, 30 Core System, 40 Input Devices, 50 Occupancy Management System, 60 Wearable Devices, 70, 70A, 70B, 70C Terminal Devices, 110 Storage Devices, 120 Communication Devices, 130 Processing Devices, 302, 304 Acquisition Units, 305 Detection Units, 310 Estimation Units, 315 Judgment Units, 320 Decision Units, 325 Selection Units, 335 Instruction Units, 345 Calculation Units, 350 Transmission Units, 355 Receiving Units, 405 Emergency Medical Services Management Server.

Claims

1. A determination unit that determines whether or not life-saving activities are necessary for the first target person, The system includes a first acquisition unit that acquires predetermined information from a database containing personal information of multiple members of a predetermined organization, The aforementioned predetermined information is information relating to the suitability of each of the multiple members for the life-saving activities. A server further comprising a selection unit that, when the determination unit determines that the life-saving activity is necessary, selects a second person from among the multiple members, in accordance with the predetermined information, to be instructed to perform the life-saving activity on the first person.

2. The first acquisition unit acquires the predetermined information by synchronizing with the database when the determination unit determines that the life-saving activity is necessary. The server according to claim 1, wherein the selection unit selects the second target person according to the predetermined information obtained by synchronizing with the database.

3. The aforementioned predetermined information includes first information indicating whether or not each of the multiple members has a history of attending training related to the life-saving activities. The server according to claim 1, wherein the selection unit selects, from among the plurality of members, a member who has the course history as a second target in accordance with the first information.

4. The predetermined information further includes, for each of the plurality of members, a first date information indicating the date on which the member attended the training if that member has the aforementioned training history, The server according to claim 3, wherein the selection unit selects a second target person according to the first information and the first date information when two or more of the plurality of members have the course attendance history.

5. The aforementioned predetermined information includes second information indicating whether each of the multiple members is qualified to perform the life-saving activities, The server according to claim 1, wherein the selection unit selects members who meet the qualifications from among the plurality of members as second targets in accordance with the second information.

6. The predetermined information further includes, for each of the plurality of members, second date information indicating the date on which the member acquired the qualification if that member possesses the qualification, The server according to claim 5, wherein the selection unit selects the second target person according to the second information and the second date information when two or more of the plurality of members have the qualification.

7. The predetermined information includes third information indicating the attributes of each of the plurality of members, including gender, age, and at least one of the departments of the organization. The server according to claim 1, wherein the selection unit selects the second target person in accordance with the third information.

8. The predetermined information includes a fourth piece of information showing the diagnostic results of the physical and mental condition of each of the multiple members. The server according to claim 1, wherein the selection unit selects the second target person in accordance with the fourth information.

9. A second acquisition unit acquires location data indicating the location of each of the aforementioned multiple members within the organization's facilities. The system further includes a calculation unit that calculates the distance between each of the plurality of members and the first subject according to the room location data, The server according to claim 1, wherein the selection unit selects the second target person according to the predetermined information and the calculation result of the calculation unit.

10. A transmission unit that transmits location information indicating the location of the first subject and life-saving information indicating that life-saving activities are necessary for the first subject to a management server that manages the dispatch of emergency medical services, A receiving unit that receives time information from the server indicating the time required until the emergency medical team begins the life-saving activities, The system further comprises a determination unit that determines the procedure for the life-saving activity according to the time information, The aforementioned determination unit, If the time required is shorter than the standard time, the procedure for the prescribed activities to assist in the first person's basic life support is determined as the procedure for the life-saving activity instructed to the second person. The server according to claim 1, wherein if the required time is equal to or greater than the standard time, the server determines the predetermined activity and the procedure for the first life-saving measures as the procedure for the life-saving activity to be instructed to the second person.

11. The aforementioned predetermined information includes at least one of the first information and the second information, The first piece of information is information indicating whether or not each of the multiple members has a history of taking training related to the life-saving activities. The second piece of information is information indicating whether each of the multiple members is qualified to perform the life-saving activities. The selection unit selects a plurality of second subjects from among the plurality of members according to at least one of the first information and the second information, and the plurality of second subjects include a first member who has at least one of the training history and the qualification, and a second member who does not have either the training history or the qualification. The aforementioned server, The server according to claim 1, further comprising an instruction unit that instructs a first member to perform primary life support measures for the first target person as part of the life-saving activities, and instructs a second member to perform predetermined activities to assist the primary life support measures as part of the life-saving activities.

12. A determination unit that determines whether or not life-saving activities are necessary for the first target person, It comprises a storage unit that stores a database containing personal information of multiple members of a predetermined organization, The aforementioned personal information includes predetermined information relating to the suitability of each of the aforementioned members for the aforementioned life-saving activities, A life-saving system further comprising a selection unit that, when the determination unit determines that life-saving activities are necessary, selects a second person from among the multiple members in accordance with the predetermined information to be instructed to carry out the life-saving activities for the first person.

13. The first step is to determine whether or not life-saving measures are necessary for the target person, This includes the step of obtaining predetermined information from a database containing the personal information of multiple members of a predetermined organization, The aforementioned predetermined information is information relating to the suitability of each of the multiple members for the life-saving activities. A method further comprising the step of selecting, from among the multiple members, a second person to be instructed to perform the life-saving activity on the first person, in accordance with the predetermined information, when it is determined that the life-saving activity is necessary.

14. A program that causes a computer to perform a method, The aforementioned method, The first step is to determine whether or not life-saving measures are necessary for the target person, This includes the step of obtaining predetermined information from a database containing the personal information of multiple members of a predetermined organization, The aforementioned predetermined information is information relating to the suitability of each of the multiple members for the life-saving activities. The aforementioned method, A program that, when it is determined that the life-saving activity is necessary, further includes the step of selecting a second person from among the multiple members, in accordance with the predetermined information, to be instructed to carry out the life-saving activity for the first person.