JP7075095B2 - Programs, information processing methods and information processing equipment - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act On February 10, 2016, Life Rhythm Navi + Dr. Announced on page 8 of Silver Industry Newspaper No. 232

The present invention relates to a program, an information processing method and an information processing apparatus.

A monitoring system that monitors the condition of the elderly and the like using IT (Information Technology) has been proposed. If a trouble occurs in the person to be monitored, a caregiver, a nurse, etc. can promptly provide assistance.

An information processing device that displays the status of multiple monitored subjects in real time on the screen and changes the position to display the status of the monitored subject in which an unusual event, that is, an event, is occurring at the top of the screen is disclosed. (Patent Document 1).

Japanese Unexamined Patent Publication No. 2015-191526

In the information processing device disclosed in Patent Document 1, after the caregiver, nurse, etc. respond to the notification that the event has occurred, the notification is canceled and the past event occurrence status is not displayed. There's a problem.

One aspect is to provide a program or the like that outputs an event occurrence history.

The program acquires time-series data in a predetermined range that records the state of the monitored person or the environment around the monitored person, and the event related to the monitored person generated in the range and the event are included in the event. The associated date and time or date is acquired, the time-series data is output, and the index corresponding to the event is output in association with the position corresponding to the date and time or the date in the time-series data . When the selection is accepted, the computer is made to execute a process of outputting a list display in which the events are arranged in chronological order with the events corresponding to the indicators for which the selections are accepted are arranged at the upper part or the central part of the screen .

On one aspect, it becomes possible to provide a program or the like that outputs an event occurrence history.

It is explanatory drawing which shows the structure of an information processing system. It is explanatory drawing which shows the record layout of the target person list DB. It is explanatory drawing which shows the record layout of the graph DB. It is explanatory drawing which shows the record layout of a sensor operation DB. It is explanatory drawing which shows the record layout of the event DB. It is explanatory drawing which shows the main screen. It is explanatory drawing which shows the real-time screen. It is explanatory drawing which shows the report screen. It is explanatory drawing which shows the report screen. It is explanatory drawing which shows the past data screen. It is explanatory drawing which shows the detailed data screen. It is explanatory drawing which shows the alert screen. It is a flowchart which shows the flow of processing of a program. It is a flowchart which shows the processing flow of the subroutine of display switching. It is a flowchart which shows the processing flow of the subroutine of display switching. It is explanatory drawing which shows the report display screen of Embodiment 2. It is explanatory drawing which shows the record layout of the food and drink record DB of Embodiment 3. It is explanatory drawing which shows the report display screen of Embodiment 3. FIG. It is a functional block diagram which shows the operation of the information processing apparatus of Embodiment 4. FIG. It is explanatory drawing which shows the structure of the information processing system of Embodiment 5.

[Embodiment 1]
FIG. 1 is an explanatory diagram showing a configuration of an information processing system 10. The information processing system 10 of the present embodiment is an information processing system that monitors the state of the care recipient in the care facility and notifies the caregiver, the nurse, the family, etc. when an abnormality is detected. In the following description, the care recipient is described as a monitored person, a caregiver, a nurse, a family member, and the like as a user.

The information processing system 10 includes a client 20, a server 30, a sensor I / F (InterFace) device 40, a sleep sensor 41, an environment sensor 42, a motion sensor 43, a toilet sensor 44, and a door sensor 45. The client 20, the server 30, and the sensor I / F device 40 are connected via a network. A large number of clients 20 and sensor I / F devices 40 are connected to the network.

The client 20 is an information device used by the user. The client 20 includes a client CPU (Central Processing Unit) 21, a main storage device 22, a client auxiliary storage device 23, an input unit 24, a display unit 25, a communication unit 26, and a bus.

The client CPU 21 is an arithmetic control device that executes a program according to the present embodiment. As the client CPU 21, one or a plurality of CPUs, a multi-core CPU, or the like is used. The client CPU 21 is connected to each part of the hardware constituting the client 20 via a bus.

The main storage device 22 is a storage device such as a SRAM (Static Random Access Memory), a DRAM (Dynamic Random Access Memory), and a flash memory. The main storage device 22 temporarily stores information necessary in the middle of processing performed by the client CPU 21 and a program being executed by the client CPU 21.

The client auxiliary storage device 23 is a storage device such as a SRAM, a flash memory, a hard disk, or a magnetic tape. The client auxiliary storage device 23 stores a program to be executed by the client CPU 21 and various information necessary for executing the program.

The input unit 24 is a device such as a touch panel, a pen tablet, a mouse, a keyboard, and a microphone, and is used when the client CPU 21 accepts an operation by the user. The display unit 25 is, for example, a display integrated with a touch panel, and displays information presented to the user by the client CPU 21. The communication unit 26 is an interface for communicating with the network.

The client 20 is a general-purpose portable information device such as a smartphone, a multifunctional mobile phone, a tablet, or a notebook computer. As the client 20, a portable information device dedicated to the information processing system 10 or a wall-mounted information device provided with a large display unit 25 may be used.

The server 30 is an information processing device that accumulates data acquired via the sensor I / F device 40 and the like, processes the data in response to a request from the client CPU 21 and the like, and outputs the data. The server 30 includes a server CPU 31, a main storage device 32, a server auxiliary storage device 33, a communication unit 36, and a bus.

The server CPU 31 is an arithmetic control device that executes a program according to the present embodiment. As the server CPU 31, one or a plurality of CPUs, a multi-core CPU, or the like is used. The server CPU 31 is connected to each part of the hardware constituting the server 30 via a bus.

The main storage device 32 is a storage device such as a SRAM, a DRAM, or a flash memory. The main storage device 32 temporarily stores information necessary in the middle of processing performed by the server CPU 31 and a program being executed by the server CPU 31.

The server auxiliary storage device 33 is a storage device such as a SRAM, a flash memory, a hard disk, or a magnetic tape. The server auxiliary storage device 33 stores a program to be executed by the server CPU 31, a target person list DB 51, a graph DB 52, a sensor operation DB 53, an event DB 54, and various information necessary for executing the program. The target person list DB 51, the graph DB 52, the sensor operation DB 53, and the event DB 54 may be stored in another storage device connected via the network.

The communication unit 36 is an interface for communicating with the network.

A sleep sensor 41, an environment sensor 42, a motion sensor 43, a toilet sensor 44, and a door sensor 45 are preferentially or wirelessly connected to the sensor I / F device 40. The sensor I / F device 40 is an information processing device that acquires signals from a sleep sensor 41, an environment sensor 42, a motion sensor 43, a toilet sensor 44, and a door sensor 45 and transmits them to a server 30 via a network. When the sensor outputs an analog signal, the sensor I / F device 40 also performs A / D (Analog / Digital) conversion.

The sensor I / F device 40 is appropriately arranged according to the installation location of each sensor. For example, the toilet sensor 44 and the sleep sensor 41 may be connected to separate sensor I / F devices 40. A plurality of motion sensors 43 may be connected to one sensor I / F device 40. The sensor I / F device 40 may be built in each sensor.

The sleep sensor 41 is, for example, a sheet-shaped sensor, and is installed between the bed mattress and the sheets. The sleep sensor 41 detects the pulse, respiration, body movement, body temperature, etc. of the person lying on the bed. The sleep sensor 41 is installed at the bedside of the bed or on the wall of the room, and uses a sensor that detects and analyzes the pulse, respiration, body movement, body temperature, etc. of the person lying on the bed by microwave or infrared rays. Is also good.

The sleep sensor 41 analyzes the detected information and outputs sleep data such as body movement, apnea occurrence state, sleep depth, halfway awakening occurrence state, heart rate, and respiratory rate to the sensor I / F device 40. One sleep sensor 41 is installed on the bed of one monitored person.

The environment sensor 42 is a sensor that measures the environment such as temperature and humidity. The environment sensor 42 is installed on the wall surface or the like in the room where the monitored person lives. The motion sensor 43 is a sensor that detects human movement by infrared rays. The motion sensor 43 is also installed on the wall surface or the like in the room where the monitored person lives.

The toilet sensor 44 is a sensor installed in the toilet. The toilet sensor 44 is a sensor that detects that the toilet has been used. The door sensor 45 is a sensor that detects the opening / closing of a door or the passage of a person through the door. The door sensor 45 is installed on the door or the like of the room where the monitored person lives.

When there is a possibility that one sensor detects a plurality of monitored persons, the detected monitored persons are specified by using face recognition or an ID (IDentification) tag in combination.

FIG. 2 is an explanatory diagram showing a record layout of the target person list DB 51. The target person list DB 51 is a DB that associates the attributes of the monitored person with the real-time situation. The target person list DB 51 has an attribute information field and a real-time information field. The attribute information field has an ID field, a name field, an age field, and a room number field. The real-time information field has a state field, a room temperature field, a humidity field and an event field.

In the ID field, an ID uniquely assigned to the monitored person is recorded. The name of the monitored person is recorded in the name field. In the age field, the age of the monitored person is recorded. The room number field records the number of the room in which the monitored person lives.

The status of the monitored person is recorded in the status field. The room temperature field records the room temperature of the room in which the monitored person is staying. The humidity field records the humidity of the room in which the monitored person is staying. In the event field, the event being detected is recorded in relation to the monitored person. The target person list DB 51 has one record for one monitored person.

The server CPU 31 updates the information recorded in the real-time information field at any time based on the information obtained from each sensor connected to the sensor I / F device 40. The server CPU 31 analyzes the information obtained from each sensor, and when it is determined that an event has occurred, records the information about the event in the event field.

An event is an unusual event that occurs in the state of the monitored person or in the environment surrounding the monitored person. For example, when the sleep sensor 41 detects a stoppage of the heartbeat, respiration, etc. of the monitored person, or when the room temperature detected by the environment sensor 42 deviates from a predetermined range, the toilet sensor 44 exceeds a predetermined time for a long time. When the stay is detected, the server CPU 31 determines that an event has occurred. The server CPU 31 can determine whether or not an event has occurred by using, for example, the method disclosed in Patent Document 1. A specific example of determining whether or not an event has occurred will be described later.

The information about the event recorded in the event field by the server CPU 31 is acquired by the client CPU 21 and displayed on the display unit 25 as described later. As a result, the client CPU 21 notifies the user of a warning about the occurrence of an unusual event in the state of the monitored person or the environment around the monitored person. When the notification becomes unnecessary, such as when the user cancels the warning or detects that the abnormality has been resolved from each sensor, the server CPU 31 deletes the information about the event from the event field.

FIG. 3 is an explanatory diagram showing the record layout of the graph DB 52. The graph DB 52 is a DB that associates the ID of the monitored person with the data detected by the sleep sensor 41 and the data detected by the environment sensor 42. The graph DB 52 has an ID field, a sleep sensor field, and an environment sensor field.

The sleep sensor field has a body movement field, an apnea field, a sleep depth field, a heart rate field and a respiratory rate field. The environment sensor field has a room temperature field and a humidity field.

In the ID field, an ID uniquely assigned to the monitored person is recorded. In the body movement field, graph data showing the temporal change of the body movement of the monitored person detected by the sleep sensor 41 is recorded. The graph data is, for example, a series of data in which a set of a time measured by a sensor and a measured value is recorded each time the measurement is performed.

In the apnea field, graph data showing the temporal change of the occurrence state of the apnea phenomenon of the monitored subject detected by the sleep sensor 41 is recorded. The apnea phenomenon is a phenomenon in which the airflow in the mouth and nose is stopped for 10 seconds or more during sleep time.

In the sleep depth field, graph data showing a temporal change in the sleep depth of the monitored subject detected by the sleep sensor 41 is recorded. In the present embodiment, the sleep sensor 41 is used to detect the sleep depth in three stages of awakening, light sleep and deep sleep. The information recorded in the sleep depth field also includes the occurrence of awakenings and total sleep time per day.

In the heart rate field, graph data showing a temporal change in the heart rate of the monitored person detected by the sleep sensor 41 is recorded. In the respiratory rate field, graph data showing the temporal change of the respiratory rate of the monitored subject detected by the sleep sensor 41 is recorded.

The graph DB 52 has one record for one monitored person. The server CPU 31 updates the graph data recorded in the sleep sensor field and the environment sensor field at any time based on the information obtained from each sensor connected to the sensor I / F device 40.

FIG. 4 is an explanatory diagram showing a record layout of the sensor operation DB 53. The sensor operation record DB 53 is a DB that associates the ID of the person to be monitored, the date and time, and the detection results of each sensor of the motion sensor 43, the toilet sensor 44, and the door sensor 45. The sensor operation DB 53 has an ID field, a date and time field, and a sensor field. The sensor field includes a motion sensor field, a toilet sensor field, and a door sensor field.

In the ID field, an ID uniquely assigned to the monitored person is recorded. In the date and time field, the date and time when the data was acquired from each sensor is recorded. In the motion sensor field, it is recorded whether or not the motion sensor 43 has detected the movement of the monitored person. In the toilet sensor field, it is recorded whether or not the toilet sensor 44 has detected the use of the toilet by the monitored person. In the door sensor field, it is recorded whether or not the door sensor 45 has detected the passage of the door by the monitored person.

The sensor operation DB 53 has one record for one data recording for one monitored person. The server CPU 31 updates the information recorded in the sensor field at any time based on the information obtained from each sensor connected to the sensor I / F device 40.

FIG. 5 is an explanatory diagram showing the record layout of the event DB 54. The event DB 54 is a DB that records an ID, a date and time regarding an event detected by the server CPU 31, an item, and a history of correspondence results. The event DB 54 has an ID field, a date field, a time field, an item field, a content field, a corresponding field, and a comment field.

It should be noted that the event is an unusual event that occurs in the state of the monitored person or the environment around the monitored person, and corresponds to the event recorded in the event field of the target person list DB 51 described using FIG. ing. Therefore, the event DB 54 of the present embodiment records the history of warnings notified to the user by the client CPU 21.

In the ID field, an ID uniquely assigned to the monitored person is recorded. In the date field, the date related to the event detected by the server CPU 31 is recorded. In the time field, the time related to the event detected by the server CPU 31 is recorded.

In the item field, an item related to the event detected by the server CPU 31 is recorded. In the content field, the content of the event detected by the server CPU 31 is recorded. In the response field, when the user responds to the event, that fact is recorded. In the comment field, the comment input by the user who responded to the event is recorded. The event DB 54 has one record for one event related to one monitored person.

The recording of data in the event field of the target person list DB 51 and the event DB 54 will be described with reference to specific examples. A case where the server CPU 31 determines that the room temperature is 31.4 degrees, which exceeds the normal range, based on the data acquired by the environment sensor 42 will be described as an example. The server CPU 31 records in the event field of the record regarding the monitored person staying in the room of the target person list DB 51 that the room temperature is 31.4 degrees. The server CPU 31 adds a record to the event DB 54. The server CPU 31 records the date and time when the room temperature is detected in the date field and the time field. The server CPU 31 records "room temperature" in the item field and the detected room temperature "31.4 degrees" in the content field.

Based on the data acquired by the sleep sensor 41 and recorded in the sleep depth field of the graph DB 52, the case where the server CPU 31 determines that the overnight sleep time is 4 hours, which is outside the normal range, will be described as an example. do. The server CPU 31 records in the event field of the record relating to the corresponding monitored person in the target person list DB 51 that the sleep time is 4 hours. The server CPU 31 adds a record to the event DB 54. The server CPU 31 records the date on which the sleep time is determined in the date field. For example, if it is determined for a 24-hour sleep time that spans midnight on September 10, the server CPU 31 records the date of September 10 in the date field. The server CPU 31 records "sleep" in the item field and the overnight sleep time "4 hours" in the content field.

A case where the server CPU 31 determines that the toilet usage time is 20 minutes, which is outside the normal range, based on the data acquired by the toilet sensor 44 will be described as an example. The server CPU 31 records in the event field of the record regarding the monitored person who is using the toilet in the target person list DB 51 that the toilet usage time is 20 minutes. The server CPU 31 adds a record to the event DB 54. The server CPU 31 records the date and time at which the toilet usage time is determined in the date field and the time field. The server CPU 31 records "toilet" in the item field and the detected toilet usage time "20 minutes" in the content field. When it is determined that the use of the toilet continues even after that, for example, the cumulative total is "30 minutes", the server CPU 31 updates the data in the event field of the target person list DB 51. Further, the server CPU 31 updates the data recorded in the content field of the event DB 54 to "30 minutes".

When the server CPU 31 detects another event, it records it in the event field of the target person list DB 51 and similarly adds a record corresponding to the event DB 54.

When the server CPU 31 accepts the input of the correspondence and the input of the comment by the user via the client CPU 21, the server CPU 31 records in the corresponding field and the comment field of the corresponding record.

The reference value for determining whether or not the range is within the normal range is stored in advance in the server auxiliary storage device 33. Different reference values may be recorded for each monitored person.

FIG. 6 is an explanatory diagram showing a main screen. The client CPU 21 displays the screen shown in FIG. 6 on the display unit 25. The main screen is a screen that displays a list of the latest information on a plurality of monitored persons. In the present embodiment, the case where the client 20 is a mobile information device having a relatively small display with a touch panel such as a smartphone will be described as an example.

The screen shown in FIG. 6 has a plurality of personal display fields 61 and a menu button 76. The personal display field 61 includes an icon field 62. In one personal display field 61, information about one monitored person recorded in one record of the target person list DB 51 is displayed. Specifically, the room number, name, room temperature and humidity of one monitored person are displayed in characters, and the status of the monitored person is displayed by the icon in the icon column 62.

In the icon column 62, an icon corresponding to the information recorded in the status field of the target person list DB 51 is displayed. For example, the monitored persons in rooms 601 and 605 are awake. The monitored person in Room 602 is sleeping. The monitored person in Room 603 is using the toilet. The monitored person in Room 604 is active in the facility.

When an event is recorded in the event field of the target person list DB 51, the client CPU 21 displays a mark indicating the occurrence of the event on the right side of the icon column 62.

When the selection of the menu button 76 is accepted, the client CPU 21 displays an operation menu (not shown) on the display unit 25. From the operation menu, the client CPU 21 accepts, for example, a change in the screen setting style, a change in the order in which the personal display fields 61 are arranged, and the like.

A scroll bar is displayed on the right edge of the screen. When the operation of the scroll bar is accepted via the input unit 24, the client CPU 21 scrolls the contents displayed on the display unit 25 up and down. The client CPU 21 may acquire the records corresponding to all the monitored persons recorded in the target person list CB 51 from the target person list DB 51 and display them on the screen shown in FIG. For example, the client CPU 21 may acquire a record corresponding to the monitored person in charge of the user who operates the client 20 from the target person list DB 51 and display it on the main screen shown in FIG.

When using the large screen display unit 25, the client CPU 21 may display the personal display field 61 in a vertical and horizontal grid pattern. The client CPU 21 may arrange the personal display field 61 according to the arrangement of the rooms in the nursing facility, for example.

FIG. 7 is an explanatory diagram showing a real-time screen. When the client CPU 21 accepts that the personal display field 61 is selected on the screen using FIG. 6, the client CPU 21 displays the screen shown in FIG. 7 on the display unit 25. The real-time screen is a screen that displays a list of information on one person to be monitored.

The real-time screen includes a real-time data field 63, a menu button 76, a real-time button 77, a report button 78, a past data button 79, and an alert button 80. The real-time data column 63 is a screen for displaying real-time information about one monitored person.

The client CPU 21 displays, for example, information for the past 12 hours regarding one monitored person in the real-time data column 63. The real-time data column 63 includes a sleep depth column 631, an indoor column 632, a toilet column 633, a door column 634, and a room temperature column 635. The horizontal axis of each column is the time. The right end of the horizontal axis is the current time.

The client CPU 21 displays the sleep depth of the monitored person recorded in the sleep depth field of the graph DB 52 in the sleep depth column 631 as a band graph. The shaded area in the band graph indicates the time when the sleep depth is deep, the part indicated by the small dot indicates the time when the sleep depth is shallow, and the blank part indicates the time when the person is awake.

The client CPU 21 displays the presence or absence of movement of a person in the room recorded in the motion sensor field of the sensor operation DB 53 as a band graph in the room column 632. The shaded portion of the band graph indicates the time during which the motion sensor 43 detects the movement of the monitored person.

The client CPU 21 displays the presence / absence of use of the toilet recorded in the toilet sensor field of the sensor operation DB 53 in the toilet column 633 as a band graph. The shaded area of the band graph indicates the time during which the toilet sensor 44 detects the use of the toilet by the monitored person.

The client CPU 21 displays in the door column 634 whether or not the door is used, which is recorded in the door sensor field of the sensor operation DB 53, as a band graph. The shaded area of the band graph indicates the time during which the door sensor 45 detects the opening / closing or passing of the door by the monitored person.

The client CPU 21 displays the room temperature recorded in the room temperature field of the graph DB 52 in the room temperature column 635 as a line graph.

The client CPU 21 displays the time and the vicinity of the item corresponding to the event recorded in the event DB 54 by the index 81. A specific example will be described. In the screen shown in FIG. 7, that the server CPU 31 detected an event when the room temperature was 31.4 degrees at 14:00 is the index 81 in the room temperature column 635 and the label "31.4" on the right side thereof. Indicated by. The user can grasp that an event has occurred in the past and provide appropriate care to the monitored person.

Since the menu button 76 is the same as in FIG. 6, the description thereof will be omitted. In the screen shown in FIG. 7, the real-time button 77 is selected. When the selection of the real-time button 77 is accepted while the other screens described later are being displayed, the client CPU 21 displays the screen shown in FIG. 7. The screens displayed by the client CPU 21 when the selection of the report button 78, the past data button 79, and the alert button 80 are accepted will be sequentially described.

8 and 9 are explanatory views showing a report screen. The report screen is a screen that the client CPU 21 displays on the display unit 25 when the selection of the report button 78 is accepted via the input unit 24. FIG. 8 shows a state in which the upper end of the report screen is displayed. FIG. 9 shows a state in which a portion below FIG. 8 is displayed by scrolling the screen.

The report screen includes a report column 64, a menu button 76, a real-time button 77, a report button 78, a past data button 79, and an alert button 80. The report screen is a screen that displays one month's worth of data regarding one monitored person. Since the menu button 76, the real-time button 77, the report button 78, the past data button 79, and the alert button 80 are the same as those in FIG. 7, the description thereof will be omitted.

The client CPU 21 displays data in the report column 64 separately for each item. For example, in the screen shown in FIG. 8, the client CPU 21 shows the sleep state of the monitored person for the past month recorded in the sleep depth field of the graph DB 52 in the report column 64. The horizontal axis of the screen shown in FIG. 8 is time, and the left end indicates noon and the right end indicates noon of the next day. The vertical axis of the screen shown in FIG. 8 is a date. Let's take the top line as an example to explain in detail. The left end shows noon on July 31st, and the right end shows noon on August 1st the next day.

The band graph displayed in the report column 64 shows the sleep depth. Fine dots indicate a light sleep. The shaded hatches indicate a deep sleep. I haven't hatched when I'm awake. A line graph shows the total amount of sleep per day. The numbers to the right of the data points in the line graph indicate total sleep time. The total sleep time is recorded in the sleep depth field of graph DB 52. The client CPU 21 may analyze the sleep depth recorded in the sleep depth field of the graph DB 52 to calculate the total sleep time.

In the screen shown in FIG. 8, the sleep time on August 9 is 5.7 hours, whereas the server CPU 31 has detected an event by the index 81 and the label "5.7" on the right side thereof. Has been done. Further, and the fact that the server CPU 31 detected the event for the sleep time of 4.3 hours on August 10 is indicated by the index 81 and the label "4.3" on the right side thereof. .. The client CPU 21 acquires the event occurrence date and time and the contents from the event DB 54.

In the screen shown in FIG. 9, the client CPU 21 displays the temperature and humidity of the room of the monitored person for the past month recorded in the room temperature field and the humidity field of the graph DB 52 in the report column 64. Report column 64 includes temperature column 641 and humidity column 642. The horizontal axis of the temperature column 641 is temperature. The horizontal axis of the humidity column 642 is humidity. The vertical axis of the temperature column 641 and the humidity column 642 is the date. In the temperature column 641, the minimum temperature and the maximum temperature of the day are displayed as a line graph. In the humidity column 642, the minimum humidity and the maximum humidity of the day are displayed as a line graph.

In the screen shown in FIG. 9, the maximum temperature of the room temperature on August 7 is 31.1 degrees, whereas the detection of the event by the server CPU 31 is the label of "31.1" indicating the value of the maximum temperature. It is shown by the index 81 arranged on the left side of. In addition, the fact that the server CPU 31 detected an event while the maximum temperature of the room temperature on August 8 was 32.3 degrees is placed on the left side of the label "32.3" indicating the value of the maximum temperature. It is shown by the index 81. The client CPU 21 acquires the event occurrence date and time and the contents from the event DB 54.

The client CPU 21 serves as an index 81 and a label by displaying the label indicating the value of the maximum room temperature on August 7 and August 8 in a color different from the label on other days. Is also good.

FIG. 10 is an explanatory diagram showing a past data screen. The past data screen is a screen that the client CPU 21 displays on the display unit 25 when the selection of the past data button 79 is accepted via the input unit 24.

The past data screen includes a past data field 65, a menu button 76, a real-time button 77, a report button 78, a past data button 79, and an alert button 80. The past data screen is a screen that displays one month's worth of data about one monitored person. Since the menu button 76, the real-time button 77, the report button 78, the past data button 79, and the alert button 80 are the same as those in FIG. 7, the description thereof will be omitted.

The client CPU 21 shows one day's worth of data about one monitored person in the past data column 65. The past data column 65 includes an activity record column 66 and a detail button 82. Below the activity record column 66, the total sleep time, minimum room temperature, maximum room temperature, minimum humidity, maximum humidity and score for each day are displayed.

The activity record column 66 in the past data column 65 on September 15, 2015 shown on the upper side of FIG. 10 will be described as an example. The horizontal axis of the activity record column 66 is time. The right end shows noon on September 14th, and the left end shows noon on September 15th, the next day. The client CPU 21 shows the sleep depth acquired from the sleep depth field of the graph DB 52 in the activity record column 66 by means of a band graph. Fine dots indicate a light sleep. The shaded hatches indicate a deep sleep.

The client CPU 21 divides the non-hatched time zone in the activity record column 66 in parallel with the time axis, and displays a band graph showing the activity of the monitored person at the time of awakening in each divided portion. In the present embodiment, the client CPU 21 divides the unhatched portion into three stages. The client CPU 21 displays the presence / absence of movement of a person in the room recorded in the motion sensor field of the sensor operation DB 53 on the top row. The client CPU 21 displays in the central column whether or not the toilet is used, which is recorded in the toilet sensor field of the sensor operation DB 53. The client CPU 21 displays in the bottom column whether or not the door is used, which is recorded in the door sensor field of the sensor operation DB 53.

In this way, the client CPU 21 displays the sleep depth of the monitored person detected by the sleep sensor 41 and the detection status of the awake human sensor 43, the toilet sensor 44, and the door sensor 45 in one activity record column 66. The user can grasp the sleep state and the awake state of the monitored person for one day by looking at one activity record column 66.

FIG. 11 is an explanatory diagram showing a detailed data screen. The detailed data screen is a screen displayed on the display unit 25 by the client CPU 21 when the selection of the detailed button 82 is accepted via the input unit 24. The case where the selection of the detail button 82 in the past data column 65 for September 7, 2015 is accepted by scrolling the past data screen described with reference to FIG. 10 will be described as an example.

The detailed data screen includes a menu button 76, a detailed data field 68 and a close button 83. The detailed data screen is a screen for displaying one day's worth of data regarding one monitored person. Since the menu button 76 is the same as that shown in FIG. 7, the description thereof will be omitted.

The detailed data column 68 shows a body movement column 681, an apnea frequency column 682, a sleep depth column 683, an awakening column 684, a room temperature column 685, and an activity column 686. The horizontal axis of the detailed data column 68 is time. The right end shows noon on September 6th, and the left end shows noon on September 7th, the next day.

The client CPU 21 displays the magnitude of the body movement recorded in the body movement field of the graph DB 52 in the body movement column 681. The client CPU 21 displays the number of apnea phenomena per hour recorded in the apnea field of the graph DB 52 in the apnea frequency column 682. The client CPU 21 displays the sleep depth recorded in the sleep depth field of the graph DB 52 in the sleep depth column 683. The client CPU 21 displays the occurrence status of the mid-term awakening recorded in the sleep depth field of the graph DB 52 in the mid-term awakening column 684. The client CPU 21 may analyze the sleep depth data displayed in the sleep depth column 683 and use the occurrence status of the awakening. The client CPU 21 displays the room temperature recorded in the room temperature field of the graph DB 52 in the room temperature column 685. The client CPU 21 displays in the activity column 686 whether or not the monitored person is moving, whether or not the toilet is used, and whether or not the door is used, which is recorded in the sensor operation DB 53.

The client CPU 21 displays the time and the vicinity of the item corresponding to the event recorded in the event DB 54 by the index 81. A specific example will be described. In the apnea frequency column 682 of the screen shown in FIG. 11, it is recorded by the index 81 that an event in which the number of apnea phenomena exceeds the reference value from 23:00 to 0:00 is recorded in the event DB 54. .. In the room temperature column 685 of the screen shown in FIG. 11, it is indicated by the index 81 that an event in which the room temperature is 30.5 degrees is recorded in the event DB 54 from 14:00 to 15:00.

FIG. 12 is an explanatory diagram showing an alert screen. The alert screen is a screen that the client CPU 21 displays on the display unit 25 when the selection of the alert button 80 is accepted via the input unit 24.

The alert screen includes an event display field 67, a menu button 76, a real-time button 77, a report button 78, a past data button 79, and an alert button 80. The alert screen is a screen that displays one month's worth of data about one monitored person. Since the menu button 76, the real-time button 77, the report button 78, the past data button 79, and the alert button 80 are the same as those in FIG. 7, the description thereof will be omitted.

In the screen shown in FIG. 12, a plurality of event display fields 67 are displayed side by side in chronological order. One event display field 67 displays information about one event recorded in one record of the event DB 54.

When the selection of the index 81 shown in FIG. 7, FIG. 8, 9 or 11 is accepted via the input unit 24, the client CPU 21 has an event display field 67 corresponding to the selected index 81 at the upper part of the screen or. The alert screen may be displayed in the center.

FIG. 13 is a flowchart showing the flow of processing of the program. The flow of processing of the program of this embodiment will be described with reference to FIG.

The client CPU 21 requests the data of the target person list DB 51 from the server CPU 31 via the communication unit 26, the network, and the communication unit 36 (step S501). In step S501, the client CPU 21 may request only the data of the monitored person in charge of the user who is using the client 20, for example. In the following description, the description of the communication unit 26, the network, and the communication unit 36 will be omitted, and the description will be, for example, "the client CPU 21 requests data from the server CPU 31".

The server CPU 31 receives the request from the client CPU 21 (step S601). The server CPU 31 transmits the requested data to the client CPU 21 (step S602). The client CPU 21 receives the data (step S504). The client CPU 21 displays the main screen described with reference to FIG. 6 on the display unit 25 (step S505).

The client CPU 21 determines whether or not the selection of the target person has been accepted (step S506). For example, when the selection of the personal display field 61 is accepted via the input unit 24, the client CPU 21 determines that the selection of the target person has been accepted.

When it is determined that the selection of the target person has been accepted (YES in step S506), the client CPU 21 requests the server CPU 31 for a predetermined time range regarding the selected target person, for example, data for the past 12 hours (step S507).

The server CPU 31 receives the request from the client CPU 21 (step S608). The server CPU 31 extracts data in a predetermined time range regarding the target person selected from the graph DB 52, the sensor operation DB 53, and the event DB 54 (step S609). The server CPU 31 transmits the extracted data to the client CPU 21 (step S610).

The client CPU 21 receives the data (step S511). The client CPU 21 displays the title, button, and each graph of the real-time screen described with reference to FIG. 7 on the display unit 25 (step S512). The client CPU 21 determines whether or not the data received in step S511 includes data related to the event extracted from the event DB 54 (step S513).

When it is determined that the data related to the event is included (YES in step S513), the client CPU 21 displays the index 81 in the vicinity of the time and the item corresponding to the event (step S514). When it is determined that the data related to the event is not included (NO in step S513) and after the end of step S514, the client CPU 21 determines whether or not the display switching instruction has been accepted (step S515). For example, when it is determined that the selection of the report button 78, the past data button 79, or the alert button 80 has been accepted via the input unit 24, it is determined that the quant CPU 21 has accepted the display switching instruction.

When it is determined that the display switching instruction has been accepted (YES in step S515), the client CPU 21 activates the display switching subroutine (step S516). The display switching subroutine is described using the real-time screen described using FIG. 7, the report screen described using FIGS. 8 and 9, the past data screen described using FIG. 10, and FIG. This is a subroutine that switches the alert screens that have been created. The flow of processing of the display switching subroutine will be described later.

When it is determined that the display switching instruction is not accepted (NO in step S515) and after the end of step S516, the client CPU 21 determines whether or not the instruction to return to the main screen described using FIG. 6 has been accepted (NO). Step S517). For example, the client CPU 21 receives an instruction to return to the main screen from the menu screen displayed on the display unit 25 when the menu button 76 is selected.

If it is determined that the instruction to return to the main screen is not accepted (NO in step S517), the client CPU 21 returns to step S507. In the second and subsequent steps S507, the client CPU 21 may request the server CPU 31 only for the data of the difference from the previous time. When it is determined that the instruction to return to the main screen has been accepted (YES in step S517), the client CPU 21 returns to step S501.

When it is determined that the selection of the target person is not accepted (NO in step S506), the client CPU 21 determines whether or not the instruction to end the process has been accepted (step S518). For example, the client CPU 21 receives an instruction to end the process from the menu screen displayed on the display unit 25 when the menu button 76 is selected.

If it is determined that the instruction to end the process is not accepted (NO in step S518), the client CPU 21 returns to step S501. When it is determined that the instruction to end the process has been accepted (YES in step S518), the client CPU 21 ends the process.

14 and 15 are flowcharts showing the processing flow of the display switching subroutine. The display switching subroutine is described using the real-time screen described using FIG. 7, the report screen described using FIGS. 8 and 9, the past data screen described using FIG. 10, and FIG. This is a subroutine that switches the alert screens that have been created. A flow of processing of the display switching subroutine will be described with reference to FIGS. 14 and 15.

The client CPU 21 determines whether or not the selection of the report button 78 has been accepted (step S531). When it is determined that the selection of the report button 78 has been accepted (YES in step S531), the client CPU 21 requests the server CPU 31 for a predetermined time range regarding the displayed target person, for example, data for the past one month (step S532).

The server CPU 31 receives the request from the client CPU 21 (step S633). The server CPU 31 extracts data in a predetermined time range regarding the target person selected from the graph DB 52, the sensor operation DB 53, and the event DB 54 (step S634). The server CPU 31 transmits the extracted data to the client CPU 21 (step S635).

The client CPU 21 receives the data (step S536). The client CPU 21 displays the title, buttons, and graphs of the report screen described with reference to FIGS. 8 and 9 on the display unit 25 (step S537). The client CPU 21 determines whether or not the data received in step S536 includes data related to the event extracted from the event DB 54 (step S538).

When it is determined that the data related to the event is included (YES in step S538), the client CPU 21 displays the index 81 in the vicinity of the time and the item corresponding to the event (step S539).

When it is determined that the data related to the event is not included (NO in step S538) and after the end of step S539, the client CPU 21 determines whether or not the selection of the past data button 79 has been accepted (step S541). Even when it is determined that the selection of the report button 78 is not accepted (NO in step S531), the client CPU 21 determines whether or not the selection of the past data button 79 has been accepted (step S541).

When it is determined that the selection of the past data button 79 has been accepted (YES in step S541), the client CPU 21 requests the server CPU 31 for a predetermined time range regarding the target person being displayed, for example, data for the past two months (step S542). ..

The server CPU 31 receives the request from the client CPU 21 (step S643). The server CPU 31 extracts data in a predetermined time range regarding the target person selected from the graph DB 52, the sensor operation DB 53, and the event DB 54 (step S644). The server CPU 31 transmits the extracted data to the client CPU 21 (step S645).

The client CPU 21 receives the data (step S546). The client CPU 21 displays the title, button, and each graph of the past data screen described with reference to FIG. 10 on the display unit 25 (step S547). The client CPU 21 determines whether or not the data received in step S546 includes data related to the event extracted from the event DB 54 (step S548).

When it is determined that the data related to the event is included (YES in step S548), the client CPU 21 displays the index 81 in the vicinity of the time and the item corresponding to the event (step S549).

The client CPU 21 determines whether or not the selection of the detail button 82 has been accepted (step S550). When it is determined that the acceptance has been made (YES in step S550), the client CPU 21 displays the detailed screen described with reference to FIG. 11 on the display unit 25 (step S551). The client CPU 21 waits for the selection of the close button 83 to be accepted (step S552). After accepting the selection of the close button 83, the client CPU 21 returns to step S548.

When it is determined that the selection of the detail button 82 is not accepted (NO in step S550) and when it is determined that the selection of the past data button 79 is not accepted (NO in step S541), the client CPU 21 selects the alert button 80. It is determined whether or not the data has been accepted (step S561). When it is determined that the selection of the alert button 80 has been accepted (YES in step S561), the client CPU 21 requests the server CPU 31 for a predetermined time range regarding the displayed target person, for example, event data for the past two weeks (step S562). ..

The server CPU 31 receives the request from the client CPU 21 (step S663). The server CPU 31 extracts data in a predetermined time range regarding the target person selected from the event DB 54 (step S664). The server CPU 31 transmits the extracted data to the client CPU 21 (step S665).

The client CPU 21 receives the data (step S566). The client CPU 21 displays the alert screen described with reference to FIG. 12 on the display unit 25 (step S567).

When it is determined that the selection of the alert button 80 is not accepted (NO in step S561) and after the end of step S567, the client CPU 21 determines whether or not the selection of the real-time button 77 is accepted (step S571).

When it is determined that the selection of the real-time button 77 is not accepted (NO in step S571), the client CPU 21 returns to step S531. When it is determined that the selection of the real-time button 77 is accepted (YES in step S571), the client CPU 21 ends the process.

According to this embodiment, it is possible to provide an information processing device or the like that displays an event occurrence history in an easy-to-understand manner. Users such as caregivers can grasp events that have occurred in the past and provide appropriate care to the monitored person. If similar events occur repeatedly, it is possible to take measures such as early detection of illness and accident prevention by taking measures such as consulting a doctor.

For example, when an event that the sleep time is short occurs frequently, the amount of sleeping pills and the like can be appropriately adjusted by attaching data and reporting to the doctor. For example, when an event related to an abnormality in room temperature occurs frequently, it is possible to prevent diseases such as heat stroke and cold by checking whether or not the air conditioner is out of order.

From the menu screen displayed on the display unit 25 when the menu button 76 is selected, the client CPU 21 may accept adjustments of the time width displayed on the screen and the items displayed on the screen.

The sensor connected to the sensor I / F device 40 is an example. For example, a wristwatch-type wearable sensor worn on the arm of the monitored person may be used. By doing so, it is possible to acquire data such as a pulse rate, the number of steps, and the amount of activity even when the monitored person is awake from the bed and record it in the graph DB 52.

The sensor I / F device 40 and various sensors may be installed at the home of the monitored person. One caregiver or the like can be in charge of multiple persons to be monitored at home, and when an abnormality is detected, assistance can be provided by referring to the past situation.

The index 81 may be displayed at any place near a label indicating numerical values such as temperature and sleep time, for example, on the right side, upper side, lower side, or the like.

When it is detected that the index 81 displayed on each screen is selected, the client CPU 21 may display a dialog box for displaying the contents of the event related to the selected index 81 on the display unit 25. In this case, the client CPU 21 acquires the record corresponding to the selected event mark from the event DB 54 and displays it on the display unit 25. By doing so, the user can quickly grasp the details of the event.

When it detects that the indicator 81 displayed on the report screen described using FIGS. 8 and 9 has been selected, the client CPU 21 describes the details of the date on which the indicator 81 was displayed using FIG. The screen may be displayed on the display unit 25. By doing so, the user can quickly grasp the status of the monitored person on the day when the event occurs.

The event of this embodiment may be an objective event such as a family coming to a visit, going out, or having an event such as a birthday party. The event of the present embodiment may be a subjective state of the monitored person, such as feeling good, feeling depressed, or having a headache. These events are input to the event DB 54 by the monitored person himself or a user such as a caregiver who has heard from the monitored person. The event detected by the server CPU 31 and the item input by the monitored person or the user may be displayed by an index 81 having a different color or shape. The user may be able to set which item is displayed by the index 81.

The server CPU 31 may create data used for displaying the screen on the display unit 25 of the client 20 and output the data to the network. The client CPU 21 displays the screen by sending the data received via the network to the display unit 25. In this case, a client 20 having a low-performance or low-speed client CPU 21 can be used.

[Embodiment 2]
The present embodiment relates to an information processing system 10 or the like that displays an index 81 on a screen that displays items that are not directly related to the event. The description of the parts common to the first embodiment will be omitted.

FIG. 16 is an explanatory diagram showing a report display screen of the second embodiment. In FIG. 16, a second index 85 indicating that an event related to sleep time is recorded in the event DB 54 is additionally displayed on the report display screen described with reference to FIG.

According to the present embodiment, the user can grasp that the event exists even while browsing the data regarding the item for which the event is not recorded.

The second index 85 may be added to a screen other than the report screen. For example, when an event related to humidity that is not displayed on the real-time screen described with reference to FIG. 7 is recorded in the event DB 54, the client CPU 21 displays the second index 85 in the vicinity of the horizontal axis, for example.

Marks of different colors or shapes may be used for the index 81 and the second index 85. The second index 85 may use different colors or shapes depending on the items related to the event.

[Embodiment 3]
The present embodiment relates to an information processing system 10 or the like that displays an event based on a care record input by a user. The description of the parts common to the first embodiment will be omitted.

FIG. 17 is an explanatory diagram showing a record layout of the food and drink record DB of the third embodiment. The food and drink record DB is a DB that extracts the state of food and water intake of the monitored person from the care record recorded by the caregiver or the like. The food and drink record DB has an ID field, a date field, a breakfast field, a lunch field, a dinner field, and a moisture field.

In the ID field, an ID uniquely assigned to the monitored person is recorded. The date is recorded in the date field. The breakfast field, lunch field, and supper field record the food intake status of the monitored person. The water field records the amount of water consumed by the monitored person per day. The food and drink record DB has one record for one day of the monitored person.

FIG. 18 is an explanatory diagram showing a report display screen of the third embodiment. In FIG. 18, the food and drink record of the monitored person is displayed in the report column 64. The circles in the breakfast, lunch and dinner columns indicate that you have eaten all the meals served. The triangle indicates that you ate only a small amount. X is an index 81 indicating that a person did not eat a meal. The circle in the water column indicates that sufficient water has been ingested. The cross in the water column is an index 81 indicating that the amount of water intake is insufficient.

According to this embodiment, it is possible to provide a program or the like that displays an event as necessary for information other than the data detected by various sensors.

[Embodiment 4]
FIG. 19 is a functional block diagram showing the operation of the information processing apparatus according to the fourth embodiment. The information processing apparatus operates as follows based on the control by the server CPU 31.

The first acquisition unit 91 acquires time-series data in a predetermined range that records the state of the monitored person or the environment around the monitored person. The second acquisition unit 92 acquires an event related to the same monitored person that occurred within the same range and a date / time or date associated with the event. The output unit 93 outputs the time-series data acquired by the first acquisition unit 91, and sets the index 81 corresponding to the event acquired by the second acquisition unit 92 to the date and time or date associated with the event in the time-series data. Output in association with the corresponding position.

[Embodiment 5]
The fifth embodiment relates to a mode in which a client 20, a server 30, a sensor I / F device 40 to which various sensors are connected, and a program 71 are operated in combination.

FIG. 20 is an explanatory diagram showing the configuration of the information processing system 10 of the fifth embodiment. The configuration of this embodiment will be described with reference to FIG. The description of the parts common to the first embodiment will be omitted.

The information processing system 10 includes a client 20, a server 30, and a sensor I / F device 40 to which various sensors are connected via a network. The client 20 includes a client CPU 21, a main storage device 22, a client auxiliary storage device 23, an input unit 24, a display unit 25, a communication unit 26, and a bus.

The server 30 includes a server CPU 31, a main storage device 32, a server auxiliary storage device 33, a communication unit 36, a reading unit 37, and a bus. The reading unit 37 is a device that reads the portable storage medium 72, and specifically, for example, a micro SD (Secure Digital) card slot, a disk drive, or the like.

The program 71 is recorded on the portable storage medium 72. The server CPU 31 reads the program 71 via the reading unit 37 and stores it in the server auxiliary storage device 33. Further, the server CPU 31 may read the program 71 stored in the semiconductor memory 73 such as the flash memory mounted in the server 30. Further, the server CPU 31 may download the program 71 from another server computer (not shown) connected via the communication unit 36 and store the program 71 in the server auxiliary storage device 33.

The portion of the program 71 executed by the client 20 is transmitted to the client 20 via the network and stored in the client auxiliary storage device 23. The client 20 may download a portion of the program 71 executed by the client 20 via the network.

The server CPU 31 reads the program 71 that executes the above-mentioned various software processes from the portable storage medium 72 or the semiconductor memory 73, or downloads the program 71 from another server computer (not shown) via the communication unit 36. The program 71 is installed as a control program of the server 30, is loaded into the main storage device 32, and is executed by the server CPU 31.

The client CPU 21 reads the transmitted program 71 from the client auxiliary storage device 23. The program 71 is installed as a control program of the client 20, is loaded into the main storage device 22, and is executed by the client CPU 21. As described above, the information processing system functions as the above-mentioned information processing system 10 as a whole.

The technical features (constituent requirements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed.
The embodiments disclosed this time should be considered to be exemplary in all respects and not restrictive. The scope of the present invention is not shown above, but is indicated by the scope of claims, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

10 Information processing system 20 Client 21 Client CPU
22 Main memory 23 Client auxiliary storage 24 Input section 25 Display section 26 Communication section 30 Server 31 Server CPU
32 Main storage device 33 Server auxiliary storage device 36 Communication unit 37 Reading unit 40 Sensor I / F device 41 Sleep sensor 42 Environment sensor 43 Human sensor 44 Toilet sensor 45 Door sensor 51 Target person list DB
52 Graph DB
53 Sensor operation DB
54 Event DB
61 Personal display column 62 Icon column 63 Real-time data column 631 Sleep depth column 632 Indoor column 633 Toilet column 634 Door column 635 Room temperature column 64 Report column 641 Temperature column 642 Humidity column 65 Past data column 66 Activity record column 67 Event display column 68 Details Data column 681 Body movement column 682 Inspiration frequency column 683 Sleep depth column 684 Mid-sleep awakening column 685 Room temperature column 686 Activity column 71 Program 72 Portable storage medium 73 Semiconductor memory 76 Menu button 77 Real-time button 78 Report button 79 Past data button 80 Alert Button 81 Index 82 Detail button 83 Close button 85 Second index 91 First acquisition unit 92 Second acquisition unit 93 Output unit

Claims (11)

Acquire time-series data in a predetermined range that records the status of the monitored person or the environment around the monitored person.
The event related to the monitored person that occurred within the range and the date and time or date associated with the event are acquired.
In addition to outputting the time-series data, the index corresponding to the event is output in association with the date and time of the time-series data or the position corresponding to the date.
When the selection of the index is accepted, a program that causes the computer to output a list display in which the events are arranged in chronological order with the events corresponding to the index for which the selection is accepted are arranged at the top or center of the screen. .. The program according to claim 1, wherein the time-series data includes time-series data for each of a plurality of items acquired by a plurality of types of sensors. The program according to claim 1 or 2, wherein the list display is output in such a manner that the event display fields combining the event occurrence time and the contents of the event are arranged in a line in chronological order. When an instruction for real-time output is received, the time-series data of a plurality of items are output using a common time axis, and the index corresponding to the event is output in association with the position corresponding to the time axis.
The program according to claim 2 or 3, which outputs a plurality of graphs individually showing each item of the time series data when an instruction for output a report is received. When the instruction to output the past data is received, the time-series data for a predetermined number of days is acquired and the time series data is acquired.
The time-series data is divided into daily data and illustrated by a band graph, and the sleep time in each period is displayed in characters between the band graphs according to any one of claims 2 to 4. Program. When a detailed display instruction for one of the band graphs is received, a plurality of the time series data for one day corresponding to the specified band graph are output using a common time axis. Item 5. The program according to Item 5. When receiving an instruction to display the status of a plurality of the monitored subjects, the information regarding the status of the plurality of monitored subjects is acquired in real time and the status of each of the monitored subjects is displayed in a list in real time from claim 1. The program according to any one of claims 6. The state of the monitored person includes the distinction between waking up, sleeping, using the toilet and being active.
The program according to claim 7, wherein a list display is output in a manner in which personal display fields combining the names of the monitored persons and the icons indicating the distinction are arranged in a row. The program according to claim 7 or 8, wherein the environment around the monitored person includes the temperature and humidity of the room of the monitored person. Acquire time-series data in a predetermined range that records the status of the monitored person or the environment around the monitored person.
The event related to the monitored person that occurred within the range and the date and time or date associated with the event are acquired.
In addition to outputting the time-series data, the index corresponding to the event is output in association with the date and time of the time-series data or the position corresponding to the date.
When the selection of the index is accepted, the information that the computer executes the process of outputting the list display in which the events are arranged in chronological order with the event corresponding to the index for which the selection is accepted is arranged at the upper part or the center of the screen. Processing method. The first acquisition unit that acquires time-series data in a predetermined range that records the state of the monitored person or the environment around the monitored person, and
A second acquisition unit that acquires an event related to the monitored person generated within the range and a date / time or date associated with the event.
Output of the time-series data acquired by the first acquisition unit and output of the index corresponding to the event acquired by the second acquisition unit in relation to the date and time of the time-series data or the position corresponding to the date. Department and
When the selection of the index is accepted, it is provided with an event list output unit that outputs a list display in which the events are arranged in chronological order with the events corresponding to the indicators for which the selection is accepted are arranged at the upper part or the center of the screen. Information processing device.

Images