Evacuee health management system, evacuee health management methods and programs

Abstract

We provide a system that allows for the health management of evacuees without requiring personally identifiable information. [Solution] The evacuee health management system includes means for acquiring attribute information for each of several evacuees that does not include personally identifiable information; determination conditions for determining which group each evacuee belongs to based on their health status; means for classifying the several evacuees into one of the groups based on the attribute information for each of the several evacuees; means for extracting the group from the group that corresponds to a predetermined health status; and means for outputting information indicating measures to improve the health status of the extracted group.

Description

Technical Field

[0001] The present disclosure relates to an evacuee health management system, an evacuee health management method, and a program.

Background Art

[0002] In disasters such as nuclear disasters, earthquakes, and landslides, the evacuation period tends to be long. During this period, evacuees move between primary evacuation shelters (shelters close to the disaster area), secondary evacuation shelters (shelters for long-term living), emergency temporary housing, etc. Also, the forms of using shelters are diverse, such as working households whose shelter use is limited to only at night, and the elderly who use shelters only during the day for mental reasons although the soundness of their homes has been confirmed. Accordingly, there are also diverse considerations for health management. To conduct individual health management, it is considered important to obtain and use detailed personal information of evacuees. However, handling detailed personal information that can identify individuals in temporary facilities such as shelters causes problems such as an increased risk of information leakage.

[0003] Patent Document 1 discloses a shelter management system in which, instead of the personal information of evacuees, cards storing attribute information such as gender and whether the person requires care are distributed. When an evacuee enters a shelter, the attribute information of this card is read and transmitted to a server together with the identification information of the shelter, and by managing these information on the server, it is possible to quickly grasp the number of evacuees in the shelter even if evacuees do not use cards or the like storing personal information. However, Patent Document 1 does not disclose how to conduct evacuee health management without handling personal information.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] There is a need for a system that can manage the health of evacuees without requiring personally identifiable information.

[0006] This disclosure provides a health management system for evacuees, a method for managing the health of evacuees, and a program that can solve the above-mentioned problems. [Means for solving the problem]

[0007] The evacuee health management system disclosed herein includes: acquisition means for acquiring attribute information that does not include personally identifiable information for each of several evacuees; determination conditions for determining which of several groups to classify each evacuee into based on their health status based on the attribute information; classification means for classifying each of the several evacuees into one of the groups based on the attribute information of each of the several evacuees; extraction means for extracting a group from the group that corresponds to a predetermined health status; and countermeasure presentation means for outputting information indicating countermeasures to improve the health status of the extracted group.

[0008] The method for managing the health of evacuees according to this disclosure is a method for managing the health of evacuees performed by a computer, comprising: a step in which the computer acquires attribute information for each of a plurality of evacuees, which does not include personally identifiable information; a step in which the computer classifies the plurality of evacuees into one of a plurality of groups based on the attribute information and a determination condition for determining whether to classify them into one of a plurality of groups according to their health status; a step in which the computer extracts a group from the group that corresponds to a predetermined health status; and a step in which the computer outputs information indicating measures to improve the health status of the extracted group.

[0009] The program of this disclosure causes a computer to function as a means for acquiring attribute information for each of several evacuees, which does not include personally identifiable information; determination conditions for determining which of several groups to classify each of the several evacuees into based on their health status based on the attribute information; means for classifying the several evacuees into one of the groups based on the attribute information for each of the several evacuees; means for extracting the group corresponding to a predetermined health status from among the groups; and means for outputting information indicating measures to improve the health status of the extracted group. [Effects of the Invention]

[0010] According to the above-mentioned evacuee health management system, evacuee health management method, and program, the health management of evacuees can be carried out without requiring any information that could identify individuals. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of a health management system for evacuees according to the embodiment. [Figure 2A] Figure 1 shows an example of attribute information according to the embodiment. [Figure 2B] Figure 2 shows an example of attribute information according to the embodiment. [Figure 2C] This figure shows an example of the output of the aggregated attribute information according to the embodiment. [Figure 3A] This figure shows an example of a group according to the embodiment. [Figure 3B] This figure shows an example of the group classification results according to the embodiment. [Figure 3C] This figure shows an example of the output of the group classification results for each evacuation shelter according to the embodiment. [Figure 4A] This figure shows an example of measures taken to achieve the desired transition according to the embodiment. [Figure 4B] This figure shows an example of a factor that causes an undesirable transition according to the embodiment. [Figure 5]This flowchart shows an example of a process for managing the health status of evacuees according to the embodiment. [Figure 6] This figure shows an example of the hardware configuration of the evacuee health management system according to the embodiment. [Modes for carrying out the invention]

[0012] <Embodiment> (overview) The evacuee health management system 100 of this embodiment will be described below with reference to the drawings. Figure 1 shows an example of a health management system for evacuees according to an embodiment of this system. The Evacuee Health Management System 100 can be used to manage the health of evacuees in the event of a disaster at a nuclear power plant, but is not limited to this purpose. It can also be used for health management of evacuees in the event of large-scale disasters such as major earthquakes and tsunamis, and various plant disasters. It is particularly suitable for managing the health of evacuees when the evacuation period is prolonged or when the number of evacuees is large.

[0013] The evacuee health management system 100 includes a server 10, code information 2 possessed by evacuees 1, and a mobile terminal 4 possessed by staff members 3 who support evacuees 1 at evacuation shelters 5. There are multiple evacuation shelters 5a, 5b, etc., and each evacuation shelter 5 has multiple evacuees 1 possessing code information 2 and multiple staff members 3 possessing mobile terminals 4. Code information 2 is, for example, a QR code (registered trademark) printed on paper. Code information 2 is distributed to each evacuee 1 entering evacuation shelter 5 and is treated as identification information for evacuee 1. Therefore, code information 2 is generated to be unique using a predetermined algorithm. The mobile terminal 4 has the function of reading code information 2. The mobile terminal 4 is also connected to the server 10 so as to be able to communicate data. Evacuation shelters 5 include schools, gymnasiums, community centers, temporary housing, etc.

[0014] When evacuee 1 enters evacuation shelter 5, staff member 3 distributes code information 2 to evacuee 1, and staff member 3 uses the mobile terminal 4 to read the code information 2 of the entering evacuee 1. Also, staff member 3 listens to the attribute information of evacuee 1 and inputs the attribute information into the mobile terminal 4. Alternatively, a terminal device (such as a PC or tablet terminal) not shown that can perform data communication with server 10 is installed in each evacuation shelter 5, and evacuee 1 himself or herself may input his or her own attribute information into this terminal device. Attribute information is information that cannot identify evacuee 1 individually but can identify individuals, and is necessary for managing the health status of evacuee 1. Examples of attribute information are shown in FIGS. 2A and 2B. The attribute information is composed of (1) basic information, (2) basic health information, (3) disaster information, and (4) physical condition management information. (1) Basic information is, for example, name, date of birth, age, gender, address, etc. These pieces of information may be such that an individual cannot be identified. For example, the name may be a nickname. The date may be just the month, just the day, etc. The age may be information representing an age group such as the 10s, 20s, etc. The address only needs to indicate the residential area, and for example, it may be a postal code. (2) Basic health information is the presence or absence of underlying diseases, and if there are underlying diseases, the types thereof, whether there are problems with motor functions such as walking ability and sitting-holding ability, the state of cognitive function, the level of care, etc. Information on motor functions is used for determining the necessity of facilities equipped with barrier-free functions, and cognitive function is used for determining the necessity of private rooms, etc. (3) Disaster information is the damage situation in the residential area, the damage situation of one's own house, the damage situation and restoration situation of electricity, gas, water, communication, etc. These are used for PTSD diagnosis and estimating how long an evacuation period is required. The damage situation may be quantified based on, for example, the collapse rate in that area. (4) Physical condition management information is the dietary intake situation, drinking situation, exercise habits, bathing, basic vital signs such as body temperature, blood pressure, and heart rate, the participation situation in various events such as exchange meetings, the period of stay (number of days of stay), the physical condition and mental state declared by the individual, etc. In the examples of FIGS. 2A and 2B, for the information in (1) that basically does not change, and for the information in (2) to (3) that may be updated but does not change much, it is managed by table 201 illustrated in FIG. 2A, and for the information in (4) that is accumulated daily, it is managed by table 202 illustrated in FIG. 2B.

[0015] For example, if evacuee 1 is to move to another evacuation center 5 due to the disaster situation or personal circumstances, staff member 3 at the original evacuation center 5 uses a mobile terminal 4 to read the code information 2 of evacuee 1 who is leaving. After reading the code information 2, staff member 3 inputs information indicating departure into the mobile terminal 4 and instructs the mobile terminal 4 to send data. The mobile terminal 4 then sends the code information 2, the identification information of the evacuation center 5 that staff member 3 is in charge of (the identification information of evacuation center 5 is pre-registered in the mobile terminal 4), and the information indicating departure to the server 10. The server 10 acquires this information and stores the transmitted code information 2, etc., in association with the date the information was acquired (for example, the "Departure" box in Table 202 in Figure 2B is checked). Similarly, at the destination evacuation center 5, staff member 3 uses a mobile terminal 4 to read the code information 2 of the newly arriving evacuee 1 and sends the read information, along with the identification information of the destination evacuation center 5, to the server 10. Server 10 retrieves this information and stores code information 2, etc., in association with the date the information was retrieved (for example, it adds data with the "Admission" check box in table 202 in Figure 2B). If code information 2 is lost, the person can be identified by referring to (1) basic information, etc., registered at the previous evacuation center 5, and code information 2 may be reissued.

[0016] At the shelter 5, daily provisions of meals, exercises such as radio gymnastics, and measurements of body temperature and blood pressure are carried out. In addition, bathing and various events and activities to support evacuees (such as exchange meetings, counseling by nurses, and life guidance) are held. Each time such actions occur, the staff member 3 uses the mobile terminal 4 to read the code information 2 for each evacuee 1 and inputs information indicating that the evacuee 1 has participated in various events and received various services into the mobile terminal 4. Then, this information is transmitted from the mobile terminal 4 to the server 10. For example, if meals are provided three times a day and the evacuee 1 has received all of them, the number of meal times, three times, is recorded in the table 202 in association with the code information 2 of the evacuee 1. If the evacuee 1 has received meals only twice, the number of meal times, two times, is recorded in association with the code information 2 of the evacuee 1 (Figure 2B). In the case of transferring to another shelter on the same day, the number of meals provided at each shelter 5 is recorded for each shelter ID (identifier: identification information). Similarly, information such as body temperature, blood pressure, heart rate, physical condition, mental state, presence or absence of bathing, and presence or absence of participation in events is accumulated in the table 202 every day.

[0017] The server 10 includes an evacuee information management department 11, a group management department 12, and a countermeasure management department 13. The evacuee information management department 11 has the tables 201 and 202 illustrated in Figures 2A and 2B. The evacuee information management department 11 acquires the attribute information of the evacuee 1 transmitted from the mobile terminal 4, records the acquired attribute information in the tables 201 and 202, and manages the attribute information.

[0018] The evacuee information management unit 11 calculates the trend of basic vital signs for a specific evacuee 1 during a predetermined evaluation period, and calculates the number of evacuees 1 with a specific tendency for each evacuation center 5, based on the records in tables 201 and 202. The evacuee information management unit 11 outputs this calculated information to a display device (not shown) or transmits it to a mobile terminal 4. Figure 2C shows an example of output of the aggregated attribute information. Image 203 in Figure 2C is a map image that aggregates the number of evacuees 1 whose blood pressure rose above a predetermined value during a predetermined evaluation period for each evacuation center 5a to 5c in area a, and represents the aggregated results by the size of the circles. From Image 203, it can be seen that in area a, a high incidence of blood pressure elevation is observed at evacuation center 5b. This allows for measures to be taken to address the blood pressure elevation occurring at evacuation center 5b. Furthermore, by outputting the number of evacuees 1 with certain characteristics, regardless of the group described later, it is possible to grasp the trends of evacuees 1 in area a without being limited by groups.

[0019] The Group Management Unit 12 classifies each evacuee 1 into several groups based on attribute information stored by the Evacuee Information Management Unit 11. An example of a group is shown in Table 301 of Figure 3A. Two examples of criteria for classifying into groups are given. Pattern 1 is an example of classification based on the presence or absence of underlying diseases, basic vital signs, and physical condition. As shown in the figure, the group of evacuee 1 with underlying diseases and poor physical condition is classified as Group 1, the group of evacuee 1 with underlying diseases and good physical condition but poor basic vital signs is classified as Group 2, and the group of evacuee 1 with underlying diseases and good physical condition and basic vital signs is classified as Group 3. The Group Management Unit 12 refers to Tables 201 and 202 to determine the presence or absence of underlying diseases for each evacuee 1, to determine whether they are in good physical condition, to determine whether they are in good condition or not, to determine whether they are in good condition or not based on the average values ​​of basic vital signs, etc. (for example, comparing the average values ​​of body temperature, blood pressure, and heart rate during the evaluation period with their respective reference ranges), and classifies each evacuee 1 into one of Groups 1 to 3. This allows the person in charge to understand how many evacuee 1 have health problems. Generally, evacuation shelters do not have the resources to provide adequate health management for each individual. In contrast, this embodiment aims to efficiently maintain the health of the group of evacuees by grouping them based on their health status, understanding the overall trends, identifying groups that require countermeasures, and implementing those countermeasures.

[0020] Pattern 2 is an example of grouping based on the frequency of transfers between shelters 5, basic vital signs, and the health condition reported by the individual. Group 1 is a group of evacuees 1 who frequently move between shelters 5 and have poor basic vital signs; Group 2 is a group of evacuees 1 who frequently move between shelters but have good health; and Group 3 is a group of evacuees 1 who stay at a specific shelter 5 and have good health. The group management unit 12 refers to tables 201 and 202 to determine the frequency of transfers between shelters 5 for each evacuee 1 (for example, by referring to table 202 and aggregating the number of "admissions" and "departures" during the evaluation period, or the number of "IDs" for shelters, and using the aggregated value as the transfer frequency), determines whether the evacuee is in good or bad health, and classifies each evacuee 1 into one of the groups 1 to 3 based on the average basic vital signs, etc. Since evacuees 1 who frequently move between shelters 5 are likely to be experiencing stress, the unit considers providing counseling and job referrals to evacuees 1 in Group 1 (see "Measures" below).

[0021] Note that the group classification criteria exemplified in Table 301 of Figure 3A are examples only and are not limited to these. The group management unit 12 receives input of classification criteria from knowledgeable users (hereinafter referred to as administrators) and stores the received classification criteria. In the example in Figure 3A, the groups are classified into three categories, but the number of groups may be two or four or more. Furthermore, the group classification criteria and the number of groups may be changed as the period of evacuation lengthens.

[0022] The group management unit 12 performs the process of classifying evacuee 1 into one of the groups based on the judgment conditions illustrated in Figure 3A at predetermined intervals or based on the instructions of the administrator, and stores the classification results. Figure 3B shows an example of a table 302 for recording the judgment results. As shown, table 302 has the following items: "code information," which is the identification information of evacuee 1; "judgment date," which is the date the grouping was performed; and "group," which is the result of the grouping. In the example in Figure 3B, there are records of evacuee 1 with code information "001," who was classified into group 1 in YYYYMMDD1, but whose health condition improved and was subsequently classified into group 2 in YYYYMMDD2, and records of evacuee 1 with code information "002," who belonged to group 3 and had no health problems from YYYYMMDD1 to YYYYMMDD2. In this way, by repeatedly performing grouping as time passes, it is possible to grasp the latest health condition of evacuee 1 and any changes in their health condition.

[0023] Furthermore, the group management unit 12 aggregates the records in table 302, as illustrated in Figure 3B, to calculate the group transition of a specific evacuee 1 during a predetermined evaluation period, calculate the number of evacuees 1 belonging to each group and code information 2, and calculate the number of evacuees 1 belonging to a specific group for each evacuation center 5. The group management unit 12 can output the calculated information to a display device (not shown) or transmit it to a mobile terminal 4. Figure 3C shows an example of the information output by the group management unit 12. Image 303 in Figure 3C(a) is a map image of region a that visualizes the number of people belonging to group 1 for each evacuation center 5a to 5c when grouped according to the judgment conditions of pattern 1. The size of the circles indicates the number of people belonging to group 1 in that evacuation center 5. From image 303, it can be seen that health measures for evacuation center 5c are particularly necessary in region a. Similarly, the number of people who transitioned from Group 1 to Groups 2 or 3 (improved health) during a predetermined evaluation period, and the number of people who transitioned from Group 3 to Group 2 or Group 1 (worsened health), can be calculated and this information can be displayed. By understanding the group transitions over time, it is possible to determine whether the health status of each evacuation center 5 is improving, worsening, or remaining unchanged, and if signs of deterioration are observed, countermeasures can be taken early. Image 304 in Figure 3C(b) is a map image that visualizes the number of people belonging to Group 1 for each evacuation center 5 in areas a and b, when grouped according to the judgment conditions of Pattern 1. Image 304 shows that health measures are needed in area b. By visualizing the number of people belonging to a specific group over a wide area in a comparable manner, it is possible to identify areas where health status is deteriorating on a regional basis, understand problems in each region, and take early countermeasures.

[0024] The countermeasures management unit 13 presents measures to improve the health condition of evacuee 1 and factors that worsen the health condition of evacuee 1. Figure 4A shows Table 401, which registers measures to improve health condition. Table 401 registers Measure 1, which is effective for transitions from Group 1 to Group 2, Measure 2, which is effective for transitions from Group 1 to Group 3, and Measure 3, which is effective for transitions from Group 2 to Group 3. Measure 1 is, for example, a measure that helps reduce stress, such as participating in social events. Measures 2 and 3 are measures that improve lifestyle habits, such as reviewing diet and providing exercise guidance. Figure 4B shows Table 402, which registers factors that cause deterioration of health condition. Table 402 registers Factor 1 that causes transitions from Group 2 to Group 1, Factor 2 that causes transitions from Group 3 to Group 1, and Factor 3 that causes transitions from Group 3 to Group 2. For example, Factors 1 to 3 register events or incidents that occurred before these transitions occurred (relocation of evacuation center 5, change of job, separation from family, etc.). Although not shown in Figure 4B, Table 402 may also contain factors that further worsen the health status of Group 1.

[0025] The Countermeasure Management Unit 13 receives input of Countermeasures 1-3 and Factors 1-3 from the administrator and registers the received information in tables 401 and 402. For example, when the Group Management Unit 12 compiles the number of people belonging to Group 1, the Countermeasure Management Unit 13 outputs or sends the information for "Countermeasure 1" to the mobile terminal 4. Staff member 3 uses the mobile terminal 4 to confirm "Countermeasure 1" and tries to implement "Countermeasure 1" for evacuee 1 classified as Group 1. Also, for example, when the Group Management Unit 12 compiles the number of people belonging to Group 2, the Countermeasure Management Unit 13 outputs or sends the information for "Countermeasure 3" and "Factor 1" to the mobile terminal 4. Staff member 3 uses the mobile terminal 4 to confirm "Countermeasure 3" and "Factor 1" and tries to implement "Countermeasure 3" for evacuee 1 classified as Group 2, while also trying to prevent "Factor 1" from occurring. Furthermore, if "Factor 1" occurs for the relevant evacuee 1, care is taken to prevent that evacuee 1 from moving to Group 1.

[0026] Note that the measures 1-3 and factors 1-3 exemplified in tables 401 and 402 are examples, and more than two measures or factors may be registered in each column of the tables. Furthermore, the measures and factors may be changed as knowledge regarding the health management of evacuees is accumulated. For example, if a measure that was previously thought to be effective in transitioning from group 1 to groups 2 and 3 is found to be not very effective, the administrator will instruct the deletion of the ineffective measure. The measures management unit 13 will delete that measure from table 401. Also, if a new effective measure is found, that measure will be entered by the administrator. The measures management unit 13 will register the entered measure in table 401.

[0027] Furthermore, the countermeasure management unit 13 may have a function to suggest countermeasures to achieve desirable transitions and candidate factors that cause undesirable transitions. For example, the countermeasure management unit 13 obtains attribute information of all evacuees 1 or evacuees 1 staying at the evacuation shelter 5 to be evaluated from the evacuee information management unit 11 and identifies attribute information common to evacuees 1 who transitioned from group 1 to group 2 during a predetermined evaluation period. For example, the countermeasure management unit 13 identifies events in which many of the evacuees 1 who transitioned from group 1 to group 2 participated during the evaluation period. The countermeasure management unit 13 also extracts other evacuees 1 who participated in the identified events and checks whether a desirable transition has occurred in the extracted evacuees 1. If events similar to the identified events occur outside the evaluation period, the unit may calculate the number of evacuees who underwent a desirable transition and the number of evacuees who did not undergo a desirable transition in the group of evacuees who participated in those events. The countermeasure management unit 13 then calculates the probability of a desirable transition occurring by dividing the total number of evacuees 1 who experienced a desirable transition by the total number of event participants. If this probability is greater than or equal to a predetermined value, it determines that this event is an effective countermeasure for the transition from group 1 to group 2. The countermeasure management unit 13 outputs the countermeasures it has determined to be effective and the calculated probabilities to a display device or the like. The administrator checks the outputted countermeasures and probabilities, makes a final judgment on whether the presented countermeasures are effective, and inputs the result of that judgment into the server 10. If the administrator has input a final judgment that the countermeasures are effective, the countermeasure management unit 13 registers those countermeasures in table 401. This makes it possible to find countermeasures that humans would not notice.

[0028] The same applies to factors that cause undesirable transitions. The countermeasure management unit 13 analyzes attribute information to identify, for example, attribute information common to evacuees 1 who transitioned from group 2 to group 1. For example, the countermeasure management unit 13 identifies events in which many such evacuees 1 participated, and if the probability obtained by dividing the total number of evacuees 1 who experienced an undesirable transition by the total number of event participants is greater than or equal to a predetermined value, it determines that this event is a factor that causes a transition from group 2 to group 1 and outputs this to a display device, etc. If the administrator has finally determined that the event is a factor that causes a transition from group 2 to group 1, the countermeasure management unit 13 registers that factor in table 402. This makes it possible to find factors that humans would not notice.

[0029] (operation) Figure 5 shows an example of the process for managing the health status of evacuees. First, the administrator performs the initial setup (step S1). The administrator registers the group classification criteria, as exemplified in Figure 3A, and the countermeasures and factors, as exemplified in Figures 4A and 4B, with the server 10. In the server 10, the group management unit 12 stores the registered classification criteria, and the countermeasure management unit 13 registers the registered countermeasures and factors in tables 401 and 402, respectively. The administrator also registers information (for example, group 1 or group 1 and group 2) in the server 10 specifying which groups are to be considered as having poor health status, or which groups to be extracted. Next, the evacuee information management unit 11 registers attribute information (step S2). The evacuee information management unit 11 acquires attribute information for each evacuee 1 transmitted from each of the mobile terminals 4 used in one or more evacuation centers 5, and registers it in tables 201 and 202. Information regarding the actions and basic vital signs of evacuee 1 is transmitted daily from the mobile terminal 4, and the evacuee information management unit 11 registers the transmitted information in table 202. In the next step S3 and beyond, the daily registration and accumulation of attribute information will continue.

[0030] Next, based on the administrator's instructions, the group management unit 12 groups the evacuees 1 based on the judgment criteria (step S3). The group management unit 12 groups them, for example, by shelter 5. After grouping, the group management unit 12 outputs the classification results to a display device or the like. For example, the group management unit 12 outputs the number of evacuees 1 classified into each group for each shelter 5. The administrator refers to the grouping results and determines whether regrouping is necessary (step S4). For example, if the majority of evacuees are classified into one specific group, the administrator will determine that the current grouping is inappropriate and regrouping is necessary. If evacuees 1 with various tendencies are mixed together to form one group, the countermeasures will also be diverse, making it difficult to implement countermeasures efficiently. Therefore, the judgment criteria are considered so that each group consists of evacuees 1 with tendencies in their respective health conditions. In this case, the administrator may instruct the server 10 to output the number of evacuees 1 with certain attribute information, as illustrated in Figure 2C, and consider the judgment criteria without being restricted by groups. If it is determined that regrouping is necessary (Step S4; Yes), the administrator re-examines the grouping criteria and registers the new criteria in Server 10. The group management unit 12 updates the stored criteria with the newly registered criteria. Then, it executes the process from Step S3 onwards again.

[0031] If grouping is performed appropriately and it is determined that regrouping is unnecessary (Step S4; No), the group management unit 12 extracts a predetermined group and outputs the extracted group (Step S5). The groups to be extracted and the extraction conditions are registered in the initial settings of Step S1. For example, the group management unit 12 extracts groups whose level of health status, based on attribute information such as physical condition, psychological state, cognitive function, presence or absence of underlying diseases, and basic vital signs, is lower than a predetermined value (for example, Group 1, or Group 1 and Group 2). Alternatively, the group management unit 12 may extract groups in which the level of health status is lower than a predetermined value and the number of evacuees 1 belonging to that group is greater than a predetermined value. The number of extracted groups is not limited to one. Multiple groups may be extracted. For example, if there are different types of poor physical condition and the judgment conditions are set so that each type is grouped separately, all of those groups may be extracted. Furthermore, it may be possible to extract Group 1, which consists of people currently in poor health, and Group 2, which consists of people who may potentially transition to Group 1 in the future, and take appropriate measures for each group in an attempt to reduce the number of evacuees belonging to Group 1 as much as possible. The group management unit 12 outputs the number of people in the extracted groups and the attribute information of the evacuees belonging to those groups to a display device or the like.

[0032] Next, the countermeasure management unit 13 outputs countermeasures and factors related to the group extracted in step S5 (step S6). For example, if group 1 is extracted, the countermeasure management unit 13 refers to table 401 to obtain countermeasure 1 for transitioning from group 1 to group 2 and countermeasure 2 for transitioning from group 1 to group 3, and outputs these to a display device or the like. Next, the administrator considers the countermeasures and factors (step S7). The administrator determines whether the outputted countermeasures and factors are effective based on past results. The administrator may also instruct the countermeasure management unit 13 to present countermeasures that are effective for transitioning from group 1 to group 2. As described above, the countermeasure management unit 13 searches for attribute information of evacuees who have transitioned from group 1 to group 2 in the past, finds common attribute information, calculates the success probability, and presents attribute information with a success probability of a certain level or higher to the administrator. Alternatively, the countermeasure management unit 13 may present the found common attribute information to the administrator as a candidate for effective countermeasures without calculating the success probability. The administrator determines whether the presented attribute information (e.g., participation in a specific event) is valid, and if so, registers this fact with server 10. The administrator also considers factors that may worsen the health condition of evacuee 1, determines whether they are appropriate factors for the group output in step S5, and updates the factors as necessary.

[0033] The administrator contacts the person in charge at each shelter 5 (3) with the code information 2 and countermeasure 1 for each evacuee 1 belonging to group 1, and requests that they implement countermeasure 1. For example, the administrator instructs the server 10 to send the code information 2 and countermeasure 1 for each evacuee 5 belonging to group 1 staying at that shelter 5 to the mobile terminal 4 held by the staff member 3 at that shelter 5. Based on this instruction, the server 10 sends the code information 2 and countermeasure 1 for each evacuee 1 to the mobile terminal 4. At each shelter 5, countermeasure 1 is implemented by the staff member 3, etc.

[0034] Next, server 10 determines whether to check the health status of evacuee 1 (step S8). For example, if a predetermined period of time has elapsed since the last execution of steps S5 to S7, server 10 may determine to check the health status. Alternatively, if the administrator instructs server 10 to check the health status, server 10 may determine to check the health status. If it is determined to check the health status (step S8; Yes), the processes from step S2 onward are repeated. This makes it possible to understand the changes in evacuee 1's health status over time. In addition, prolonged evacuation may necessitate attribute groups that were not initially anticipated. In such situations, step S2 allows for the addition, deletion, and editing of attribute information. For example, if evacuee 1's age was initially classified in 10-year increments, but it is later discovered that it is easier to manage their health status if attributes are registered in categories such as teens, 20s, 30s-50s, 60s-80s, and 80s and over, then step S2 allows for the editing of each evacuee's age based on these classifications. Furthermore, in step S4, the criteria for grouping can be reset. For example, if it is determined that the criteria need to be changed, such as appropriately grouping evacuee 1 who needs immediate health improvement, grouping evacuee 1 whose health may deteriorate even if there are no problems now, or grouping evacuee 1 with low health risk, the appropriate criteria can be reset in step S4. This enables appropriate grouping according to the time elapsed since the disaster and the characteristics of the region. In addition, in step S7, it is possible to replace measures that were previously considered effective but were not actually effective with other effective measures, or to apply better measures for each group. Note that the attribute information of evacuee 1, the criteria for grouping, and the review and modification of measures and factors can be performed at any time. This allows the system to evolve to suit the local situation.

[0035] If the health status is not checked (Step S8; No), it is determined whether to terminate the process in Figure 5 (Step S9). For example, if the evacuation center is to be disbanded, the administrator will determine to terminate the process in Figure 5. In this case (Step S9; Yes), the process in Figure 5 is terminated. If the process in Figure 5 is not terminated (Step S9; No), the processes from Step S8 onwards are repeatedly executed.

[0036] (effect) In evacuation shelters, daily temperature checks and health checks are conducted, and measures are often taken for evacuees with problems. However, with this method, if an evacuee does not report a problem, no measures are taken, and there is a possibility that their health may deteriorate without their knowledge or that they may be left untreated. If the number of evacuees is small, it is possible for the administrators to proactively take measures for each individual, but disasters that result in prolonged evacuation periods are often severe disasters and involve a large number of evacuees. In such situations, it is not realistic to provide sufficient health management services to each individual. Furthermore, providing services to each individual raises the issue of needing to properly manage personal information. Therefore, in this embodiment, based on the attribute information of evacuee 1, evacuee 1 is grouped according to the level and type of health condition, and each group is prioritized from the perspective of desirability in managing their health condition (for example, wanting to immediately resolve their current health condition, or the likelihood or likelihood of their health condition deteriorating, etc.), and appropriate measures are taken on a group basis for the high-priority groups, thereby managing the health condition of all evacuees 1. This makes it possible to efficiently manage the health condition of evacuee 1. For example, by providing a somewhat standardized service, it is expected that the health condition of evacuee 1, who has a problem, can be efficiently improved. Furthermore, when classifying evacuee 1 into groups according to their health condition, information to identify individuals is not necessary. According to this embodiment, health management of evacuees is possible without handling any information that could identify individuals. In addition, if the evacuation is prolonged, it may be necessary to group people according to criteria not initially anticipated. However, according to this embodiment, the criteria for determining group classification can be reviewed at any time, enabling optimal group management. Furthermore, measures for each group can also be reviewed at any time, allowing for the provision of optimal measures to improve their health.

[0037] Figure 6 shows an example of the hardware configuration of the evacuee health management system according to the embodiment. The computer 900 includes a CPU 901, main memory 902, auxiliary memory 903, input / output interface 904, and communication interface 905. The server 10 and mobile terminal 4 described above are implemented in the computer 900. The functions described above are stored in the auxiliary memory 903 in the form of programs. The CPU 901 reads the program from the auxiliary memory 903, expands it into the main memory 902, and executes the above processing according to the program. The CPU 901 also allocates a memory area in the main memory 902 according to the program. The CPU 901 also allocates a memory area in the auxiliary memory 903 to store the data being processed according to the program.

[0038] A program to implement all or part of the functions of the server 10 and the mobile terminal 4 may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed to perform processing by each functional unit. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, if a WWW system is used, "computer system" also includes the homepage provisioning environment (or display environment). Furthermore, "computer-readable recording medium" refers to portable media such as CDs, DVDs, USBs, and storage devices such as hard disks built into the computer system. Furthermore, if this program is distributed to computer 900 via a communication line, computer 900 that receives the distribution may load the program into main memory 902 and execute the above processing. Furthermore, the above program may be for implementing only a part of the functions described above, and may also be able to implement the above functions in combination with programs already recorded in the computer system.

[0039] As described above, several embodiments relating to this disclosure have been explained, but all of these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be carried out in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0040] <Note> The evacuee health management system, evacuee health management method, and program described in each embodiment can be understood, for example, as follows:

[0041] (1) The evacuee health management system according to the first embodiment includes: acquisition means for acquiring attribute information that does not include personally identifiable information for each of a plurality of evacuees; determination conditions for determining which group to classify each evacuee into according to their health status based on the attribute information; classification means for classifying the plurality of evacuees into one of the groups based on the attribute information for each of the plurality of evacuees; extraction means for extracting the group from the group that corresponds to a predetermined health status; and countermeasure presentation means for outputting information indicating countermeasures to improve the health status of the extracted group. This allows for health management of evacuees without requiring personally identifiable information.

[0042] (2) The evacuee health management system according to the second embodiment is the evacuee health management system according to (1), wherein the countermeasure suggestion means identifies attribute information for realizing the transition based on attribute information relating to evacuees who have previously transitioned from a group corresponding to a predetermined health condition to a group with a better health condition than the group in question, and outputs the identified attribute information as candidate countermeasures for improving the health condition. This allows us to discover countermeasures that humans would not notice.

[0043] (3) The evacuee health management system according to the third embodiment is the evacuee health management system according to (2), wherein the countermeasure presentation means outputs the countermeasure candidate as information indicating the countermeasure when the user has set that the outputted countermeasure candidate is valid. This allows only countermeasures that have been deemed effective by knowledgeable users to be adopted.

[0044] (4) The evacuee health management system according to the fourth embodiment is the evacuee health management system according to (1) to (3), further comprising means for receiving the setting of the judgment conditions and means for reclassifying the plurality of evacuees into the group based on the received judgment conditions. This allows for appropriate grouping of evacuees based on their health status.

[0045] (5) The evacuee health management system according to the fifth embodiment is the evacuee health management system according to (1) to (4), further comprising means for calculating the number of evacuees belonging to the group according to the predetermined health status for each evacuation center, and means for outputting the number for each evacuation center. This allows us to determine how many evacuees belong to a group with a health condition of particular interest.

[0046] (6) The evacuee health management system according to the sixth embodiment is the evacuee health management system according to (1) to (5), further comprising means for outputting information that causes a transition from the group corresponding to the predetermined health condition to the group in which the health condition has deteriorated. It is possible to identify factors that worsen health. By eliminating these factors, it is expected that the deterioration of health can be avoided.

[0047] (7) The evacuee health management method according to the seventh embodiment is an evacuee health management method performed by a computer, comprising: a step in which the computer acquires attribute information for each of a plurality of evacuees that does not include information that identifies an individual; a step in which the computer classifies the plurality of evacuees into one of the groups based on determination conditions for determining whether to classify them into one of a plurality of groups according to their health status based on the attribute information for each of the plurality of evacuees; a step in which the computer extracts from the group a group according to a predetermined health status; and a step in which the computer outputs information indicating measures to improve the health status of the extracted group.

[0048] (8) The program according to the eighth aspect causes the computer to function as an acquisition means for acquiring attribute information that does not include personally identifiable information for each of a plurality of evacuees; determination conditions for determining which of a plurality of groups according to health status to classify each of the plurality of evacuees into one of the groups based on the attribute information of each of the plurality of evacuees; a means for extracting from the group a group according to a predetermined health status; and a means for outputting information indicating measures to improve the health status of the extracted group. [Explanation of symbols]

[0049] 1...evacuee 2. Code Information 3. Staff 4. Mobile devices 5...shelter 10. Server 11...Evacuator Information Management Department 12. Group Management Department 13. Countermeasures Management Department 100... Evacuee Health Management System 900... Computer 901···CPU 902...Main memory 903...Auxiliary storage device 904... Input / Output Interface 905...Communication Interface

Claims

1. A means of acquiring attribute information that does not include personally identifiable information for each of multiple evacuees, A determination condition for determining which of several groups to classify each of the several evacuees into based on their health status, and a classification means for classifying each of the several evacuees into one of the groups based on the attribute information of each of the several evacuees. An extraction means for extracting a group from the aforementioned group that corresponds to a predetermined health condition, A means for presenting countermeasures that outputs information indicating measures to improve the health status of the extracted group, A health management system for evacuees equipped with the necessary components.

2. The countermeasure suggestion means identifies attribute information necessary to achieve a transition based on attribute information relating to evacuees who have previously transitioned from a group corresponding to a predetermined health condition to a group with a better health condition than that group, and outputs the identified attribute information as candidate countermeasures for improving the health condition. The evacuee health management system according to claim 1.

3. The countermeasure suggestion means outputs the countermeasure candidate as information indicating the countermeasure when the user has set that the outputted countermeasure candidate is valid. The evacuee health management system according to claim 2.

4. A means for receiving the setting of the aforementioned determination conditions, A means for reclassifying the multiple evacuees into the group based on the accepted determination conditions, The evacuee health management system according to claim 1 or claim 2, further comprising:

5. A means for calculating the number of evacuees belonging to the group according to the predetermined health status for each evacuation center, A means for outputting the number of people for each of the aforementioned evacuation shelters, The evacuee health management system according to claim 1 or claim 2, further comprising:

6. means for outputting information that causes a transition from the group corresponding to the predetermined health condition to the group in which the health condition has worsened compared to the group, The evacuee health management system according to claim 1 or claim 2, further comprising:

7. A method for managing the health of evacuees performed by computer, The computer obtains attribute information for each of the multiple evacuees, which does not include personally identifiable information. The computer determines whether to classify the evacuees into one of several groups based on their health status, based on the attribute information, and the computer classifies the evacuees into one of the groups based on the attribute information of each of the evacuees. The computer performs the step of extracting a group from the group that corresponds to a predetermined health condition, The computer outputs information indicating measures to improve the health status of the extracted group, A method for managing the health of evacuees.

8. Computers, A means of obtaining attribute information for each of the multiple evacuees, which does not include personally identifiable information. A determination condition for determining which of several groups to classify each of the several evacuees into based on their health status, and a means for classifying the several evacuees into one of the groups based on the attribute information of each of the several evacuees. means for extracting a group from the aforementioned group that corresponds to a predetermined health condition, means for outputting information indicating measures to improve the health status of the extracted group, A program designed to function as such.

Images