JP2017174012A - Program, information processing method and information processing apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a program and the like for intelligibly outputting event occurrence history.SOLUTION: The program causes a computer to execute processes of acquiring time series data of a prescribed range in which a state of a monitoring object person or an environment around the monitoring object person, acquiring an event related to the monitoring object person occurring within the range, and time-of-day or a date associated with the event, outputting the time series data, and also outputting an index 81 corresponding to the event in association with a position corresponding to the time-of-day or the date in the time series data.SELECTED DRAWING: Figure 7

Description

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

  A monitoring system has been proposed for monitoring the state of the elderly using IT (Information Technology). When troubles occur in the person to be monitored, caregivers, nurses, etc. can promptly assist.

  An information processing apparatus is disclosed that displays the status of a plurality of monitoring subjects in real time on the screen, and changes the position of displaying an event different from normal, that is, the status of the monitoring subject in which the event has occurred, to the top of the screen. (Patent Document 1).

JP2015-191526A

  In the information processing device disclosed in Patent Document 1, after a caregiver, a nurse, or the like responds to a notification that an event has occurred, the notification is canceled and a state that should be an event has occurred. There is a problem that it is not recorded.

  In one aspect, an object of the present invention is to provide an information processing apparatus that outputs an event occurrence history in an easy-to-understand manner.

  The program acquires time-series data of a predetermined range in which the condition of the monitoring target person or the environment around the monitoring target person is recorded, and an event related to the monitoring target person generated in the range, and the event A computer that obtains an associated date / time or date, outputs the time-series data, and outputs an index corresponding to the event in association with a position corresponding to the date / time or the date in the time-series data. To run.

  In one aspect, it is possible to provide an information processing apparatus that outputs an event occurrence history in an easy-to-understand manner.

It is explanatory drawing which shows the structure of an information processing system. It is explanatory drawing which shows the record layout of object person list DB. It is explanatory drawing which shows the record layout of graph DB. It is explanatory drawing which shows the record layout of sensor operation DB. It is explanatory drawing which shows the record layout of event DB. It is explanatory drawing which shows a main screen. It is explanatory drawing which shows a real-time screen. It is explanatory drawing which shows a report screen. It is explanatory drawing which shows a report screen. It is explanatory drawing which shows the past data screen. It is explanatory drawing which shows a detailed data screen. It is explanatory drawing which shows an alert screen. It is a flowchart which shows the flow of a process of a program. It is a flowchart which shows the flow of a process of the subroutine of display switching. It is a flowchart which shows the flow of a process of the subroutine of display switching. 10 is an explanatory diagram illustrating a report display screen according to Embodiment 2. FIG. It is explanatory drawing which shows the record layout of the eating and drinking record DB of Embodiment 3. FIG. 10 is an explanatory diagram showing a report display screen of a third embodiment. FIG. 10 is a functional block diagram illustrating an operation of the information processing apparatus according to the fourth embodiment. FIG. 10 is an explanatory diagram illustrating a configuration of an information processing system according to a fifth embodiment.

[Embodiment 1]
FIG. 1 is an explanatory diagram illustrating a configuration of the information processing system 10. The information processing system 10 of this embodiment is an information processing system that monitors the status of a care recipient in a care facility and notifies a caregiver, nurse, family, etc. when an abnormality is detected. In the following description, a care recipient is described as a monitoring subject, a caregiver, a nurse, a family, 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 human 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 hardware unit constituting the client 20 via a bus.

  The main storage device 22 is a storage device such as an SRAM (Static Random Access Memory), a DRAM (Dynamic Random Access Memory), or a flash memory. The main storage device 22 temporarily stores information necessary during the 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 an 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 receives an operation by a user. The display unit 25 is, for example, a display integrated with a touch panel, and displays information that the client CPU 21 presents to the user. The communication unit 26 is an interface that performs communication with a network.

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

  The server 30 is an information processing apparatus that accumulates data acquired via the sensor I / F device 40 and the like, processes and outputs the data in response to a request from the client CPU 21 and the like. 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 hardware unit constituting the server 30 via a bus.

  The main storage device 32 is a storage device such as SRAM, DRAM, or flash memory. The main storage device 32 temporarily stores information necessary during 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 an 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 subject list DB 51, a graph DB 52, a sensor operation DB 53, an event DB 54, and various types of information necessary for executing the program. The subject 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 a network.

  The communication unit 36 is an interface that performs communication with a network.

  A sleep sensor 41, an environmental sensor 42, a human 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 the sleep sensor 41, the environment sensor 42, the human sensor 43, the toilet sensor 44, and the door sensor 45 and transmits the signals to the server 30 via the 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 different sensor I / F devices 40. A plurality of human 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 a sheet-like sensor, for example, and is installed between a bed mattress and a sheet. The sleep sensor 41 detects the pulse, respiration, body movement, body temperature, etc. of the person lying on the bed. Using a sensor for detecting and analyzing the pulse, breathing, body movement, body temperature, etc. of a person lying on the bed with microwaves or infrared rays in the sleep sensor 41 on the bed bed or the wall of the room Also good.

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

  The environmental sensor 42 is a sensor that measures an environment such as temperature and humidity. The environmental sensor 42 is installed on the wall surface of the room where the monitoring subject lives. The human sensor 43 is a sensor that detects a human motion using infrared rays. The human sensor 43 is also installed on the wall surface of the room where the monitoring subject 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 opening / closing of a door or that a person has passed through the door. The door sensor 45 is installed on the door of the room where the monitoring subject lives.

  When there is a possibility that one sensor detects a plurality of monitoring subjects, the detected monitoring subject is specified by using a face authentication or ID (IDentification) tag together.

  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 monitoring target person with the real-time situation. The subject 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 status field, a room temperature field, a humidity field, and an event field.

  In the ID field, an ID uniquely assigned to the monitoring subject is recorded. In the name field, the name of the monitoring subject is recorded. The age of the monitoring subject is recorded in the age field. In the room number field, the number of the room where the monitoring subject lives is recorded.

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

  The server CPU 31 updates information recorded in the real-time information field as needed based on information obtained from each sensor connected to the sensor I / F device 40. When the server CPU 31 analyzes information obtained from each sensor and determines that an event has occurred, the server CPU 31 records information about the event in the event field.

  An event is an unusual event that occurs in the condition of the monitored person or the environment around the monitored person. For example, when the sleep sensor 41 detects a stop of heartbeat, breathing, etc. of the monitoring subject, 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. For example, when a 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 using, for example, the method disclosed in Patent Document 1. A specific example of determining whether an event has occurred will be described later.

  As will be described later, the client CPU 21 acquires and displays information on the event recorded by the server CPU 31 in the event field on the display unit 25. As a result, the client CPU 21 notifies the user of a warning that an unusual event has occurred in the condition of the monitoring target person or the environment around the monitoring target person. When the notification is no longer necessary, such as when the user cancels the warning or when it is detected that the abnormality has been resolved from each sensor, the server CPU 31 deletes the information related to the event from the event field.

  FIG. 3 is an explanatory diagram showing a record layout of the graph DB 52. The graph DB 52 is a DB that associates the ID of the monitoring subject, 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 motion field, an apnea field, a sleep depth field, a heart rate field, and a respiration rate field. The environmental sensor field has a room temperature field and a humidity field.

  In the ID field, an ID uniquely assigned to the monitoring subject is recorded. In the body motion field, data of a graph indicating a temporal change in the body motion of the monitoring subject 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 when a sensor performs measurement and a measured value is recorded each time measurement is performed.

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

  In the sleep depth field, data of a graph indicating a temporal change in the sleep depth of the monitoring 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, shallow sleep and deep sleep. The information recorded in the sleep depth field includes the state of occurrence of mid-wake and the total sleep time of the day.

  In the heart rate field, graph data indicating the temporal change in the heart rate of the monitoring subject detected by the sleep sensor 41 is recorded. In the respiration rate field, graph data indicating temporal changes in the respiration rate of the monitoring subject detected by the sleep sensor 41 is recorded.

  The graph DB 52 has one record for one person to be monitored. Server CPU31 updates the data of the graph recorded on the sleep sensor field and the environmental sensor field at any time based on the information obtained from each sensor connected to 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 of the human sensor 43, the toilet sensor 44, and the door sensor 45. The sensor operation DB 53 has an ID field, a date / time field, and a sensor field. The sensor field includes a human sensor field, a toilet sensor field, and a door sensor field.

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

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

  FIG. 5 is an explanatory diagram showing a record layout of the event DB 54. The event DB 54 is a DB that records the ID and the history of the date and time, items, and correspondence results related to the event detected by the server CPU 31. 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.

  The event is an unusual event that occurs in the condition of the monitoring target person or the surrounding environment of the monitoring target person, and corresponds to the event recorded in the event field of the target person list DB 51 described with reference to FIG. ing. Therefore, the event DB 54 of the present embodiment records a history of warnings notified to the user by the client CPU 21.

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

  In the item field, items related to events detected by the server CPU 31 are recorded. The content of the event detected by the server CPU 31 is recorded in the content field. In the response field, when the user responds to the event, that fact is recorded. In the comment field, a comment input by the user who has responded to the event is recorded. The event DB 54 has one record for one event related to one monitoring target 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 a specific example. The case where the server CPU 31 determines that the room temperature is 31.4 degrees exceeding the normal range based on the data acquired by the environment sensor 42 will be described as an example. The server CPU 31 records that the room temperature is 31.4 degrees in the event field of the record related to the monitoring target person staying in the room of the target person list DB 51. 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 server CPU 31 will be described as an example when the overnight sleep time is determined to be 4 hours outside the normal range. To do. The server CPU 31 records that the sleep time is 4 hours in the event field of the record related to the corresponding monitoring target person in the target person list DB 51. 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 about 24 hours of sleep time that crosses 0:00 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.

  Based on the data acquired by the toilet sensor 44, the case where the server CPU 31 determines that the toilet usage time is 20 minutes outside the normal range will be described as an example. The server CPU 31 records that the use time of the toilet is 20 minutes in the event field of the record related to the monitoring target person using the toilet in the target person list DB 51. The server CPU 31 adds a record to the event DB 54. The server CPU 31 records the date and time when the usage time of the toilet is determined in the date field and the time field. The server CPU 31 records “toilet” in the item field and the toilet use time “20 minutes” detected in the content field. Thereafter, the use of the toilet continues, and for example, when it is determined that 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”.

  Even when other events are detected, the server CPU 31 records the event in the event list of the target person list DB 51 and similarly adds a record corresponding to the event DB 54.

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

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

  FIG. 6 is an explanatory diagram showing a main screen. The client CPU 21 displays the screen shown in FIG. The main screen is a screen that displays a list of the latest information regarding a plurality of monitoring subjects. In the present embodiment, the case where the client 20 is a portable 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 menu buttons 76. The personal display column 61 includes an icon column 62. In one individual display column 61, information related to one monitoring target 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 monitoring subject are displayed as characters, and the status of the monitoring subject is displayed as an icon in the icon column 62.

  In the icon column 62, icons corresponding to the information recorded in the status field of the target person list DB 51 are displayed. For example, the monitoring subjects in Room 601 and Room 605 are getting up. The monitoring subject in room 602 is sleeping. The person to be monitored in room 603 uses a toilet. The monitoring subject 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. The client CPU 21 accepts, for example, a change in the setting style of the screen, a change in the order in which the personal display fields 61 are arranged, and the like from the operation menu.

  A scroll bar is displayed at the right end of the screen. When the operation of the scroll bar is received via the input unit 24, the client CPU 21 scrolls the content displayed on the display unit 25 up and down. The client CPU 21 may acquire records corresponding to all monitoring subjects recorded in the subject list CB51 from the subject 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 monitoring target person in charge of the user who operates the client 20 from the target person list DB 51 and display the record on the main screen shown in FIG.

  When the display unit 25 having a large screen is used, the client CPU 21 may display the personal display column 61 in a vertical and horizontal grid pattern. The client CPU 21 may arrange the personal display column 61 in accordance with, for example, the arrangement of rooms in the nursing facility.

  FIG. 7 is an explanatory diagram showing a real-time screen. When accepting that the personal display column 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 column 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 that displays real-time information related to one monitoring target person.

  The client CPU 21 displays, for example, information for the past 12 hours related to one monitoring target 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 time. The right end of the horizontal axis is the current time.

  The client CPU 21 displays the sleep depth of the monitoring subject recorded in the sleep depth field of the graph DB 52 in the sleep depth column 631 as a band graph. A portion indicated by diagonal lines in the band graph indicates a time when the sleep depth is deep, a portion indicated by a small dot indicates a time when the sleep depth is shallow, and a blank portion indicates a time when the user is awake.

  The client CPU 21 displays the presence / absence of the movement of the person in the room recorded in the human sensor field of the sensor operation DB 53 in the room column 632 as a band graph. The portion indicated by the diagonal lines in the band graph indicates the time during which the human sensor 43 detects the movement of the monitoring target person.

  The client CPU 21 displays the use / non-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 hatched portion of the band graph indicates the time during which the toilet sensor 44 detects the use of the toilet by the monitoring subject.

  The client CPU 21 displays the presence / absence of use of the door recorded in the door sensor field of the sensor operation DB 53 in the door column 634 as a band graph. The hatched portion of the band graph indicates the time during which the door sensor 45 detects the opening / closing or passing of the door by the person being monitored.

  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 an index 81 near the time and item corresponding to the event recorded in the event DB 54. A specific example will be described. In the screen shown in FIG. 7, the fact that the server CPU 31 has detected an event when the room temperature is 31.4 degrees at 14:00 indicates that the index 81 in the room temperature column 635 and the label “31.4” on the right side thereof. Is indicated by The user can grasp that an event has occurred in the past and perform appropriate care or the like for the monitoring target person.

  The menu button 76 is the same as that shown in FIG. On the screen shown in FIG. 7, the real-time button 77 is selected. When the selection of the real-time button 77 is accepted during display of another screen described later, the client CPU 21 displays the screen shown in FIG. 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 is received will be sequentially described.

  8 and 9 are explanatory diagrams 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 received 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 where the lower part of 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 data for one month related to one person to be monitored. 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.

  The client CPU 21 displays data separately for each item in the report column 64. For example, in the screen shown in FIG. 8, the client CPU 21 shows the sleep state of the monitoring target 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, with the left end indicating noon and the right end indicating noon the next day. The vertical axis of the screen shown in FIG. 8 is the date. The top row will be described as an example. The left end shows noon on July 31 and the right end shows noon on August 1 of the next day.

  The band graph displayed in the report column 64 indicates the sleep depth. A fine dot indicates a light sleep. Diagonal hatching indicates deep sleep. The awakening time is not hatched. The total sleep time of the day is shown by a line graph. The numbers to the right of the data points on the line graph indicate the total sleep time. The total sleep time is recorded in the sleep depth field of the 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, while the server 81 detects the event by the index 81 and the label “5.7” on the right side thereof. Has been. In addition, the fact that the server CPU 31 has detected an event is indicated by the index 81 and the label “4.3” on the right side thereof, in contrast to the sleep time of August 10 being 4.3 hours. . The client CPU 21 obtains the event occurrence date / time and contents from the event DB 54.

  On the screen shown in FIG. 9, the client CPU 21 displays in the report column 64 the temperature and humidity of the monitoring subject's room for the past month recorded in the room temperature field and humidity field of the graph DB 52. The report column 64 includes a temperature column 641 and a 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 in a line graph. In the humidity column 642, the minimum humidity and the maximum humidity of the day are displayed in 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 event that the server CPU 31 has detected an event is a label “31.1” indicating the value of the maximum temperature This is indicated by an index 81 arranged on the left side of the screen. The maximum temperature of the room temperature on August 8 is 32.3 degrees, and the fact that the server CPU 31 has detected an event is arranged on the left side of the label “32.3” indicating the value of the maximum temperature. The index 81 is shown. The client CPU 21 obtains the event occurrence date / time and contents from the event DB 54.

  The client CPU 21 displays the label indicating the maximum temperature value of the room temperature on August 7 and August 8 in a color different from the labels on the other days, thereby serving as the index 81 and the label. 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 received via the input unit 24.

  The past data screen includes a past data column 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 data for one month related to one monitoring target person. 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.

  The client CPU 21 shows one day's worth of data relating to one monitoring target 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 sleeping time of the day, the minimum room temperature, the maximum room temperature, the minimum humidity, the maximum humidity and the score are displayed.

  An explanation will be given by taking the activity record field 66 in the past data field 65 on September 15, 2015 shown in the upper side of FIG. 10 as an example. The horizontal axis of the activity record column 66 is time. The right end shows noon on September 14, and the left end shows noon on September 15, 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 as a band graph. A fine dot indicates a light sleep. Diagonal hatching indicates 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 indicating the activity at the time of awakening of the monitoring target person 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 a person's movement in the room recorded in the motion sensor field of the sensor operation DB 53 at the top row. 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 center column. The client CPU 21 displays the presence / absence of use of the door recorded in the door sensor field of the sensor operation DB 53 in the bottom column.

  As described above, the client CPU 21 displays the sleep depth of the monitoring target detected by the sleep sensor 41 and the detection statuses of the awakening human sensor 43, the toilet sensor 44, and the door sensor 45 in one activity record column 66. The user can grasp the monitoring target person's sleeping state and awakening state by looking at one activity record column 66.

  FIG. 11 is an explanatory diagram showing a detailed data screen. The detail data screen is a screen that the client CPU 21 displays on the display unit 25 when the selection of the detail button 82 is received via the input unit 24. An example will be described in which the past data screen described with reference to FIG. 10 is scrolled and selection of the detailed button 82 in the past data column 65 for September 7, 2015 is received.

  The detailed data screen includes a menu button 76, a detailed data column 68, and a close button 83. The detailed data screen is a screen that displays one day's worth of data relating to one person to be monitored. The menu button 76 is the same as that shown in FIG.

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

  The client CPU 21 displays the size of the body motion recorded in the body motion field of the graph DB 52 in the body motion column 681. The client CPU 21 displays the number of apnea events per hour recorded in the apnea field of the graph DB 52 in the apnea number 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 state of midway awakening recorded in the sleep depth field of the graph DB 52 in the midway awakening column 684. The client CPU 21 may analyze the sleep depth data displayed in the sleep depth column 683 and use the state of occurrence of mid-wake. 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 the presence / absence of the monitoring target person's movement recorded in the sensor operation DB 53, the presence / absence of toilet use, and the presence / absence of door use.

  The client CPU 21 displays an index 81 near the time and item corresponding to the event recorded in the event DB 54. A specific example will be described. In the apnea number 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 events exceeds the reference value from 23:00 to 00:00 is recorded in the event DB 54. . In the room temperature column 685 of the screen shown in FIG. 11, an index 81 indicates that an event whose 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 809 is received 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 data for one month related to one monitoring target person. 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.

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

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

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

  The client CPU 21 requests 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). Note that in step S501, the client CPU 21 may request only the data of the monitoring target person in charge of the user using the client 20, for example. In the following description, description of the communication unit 26, the network, and the communication unit 36 is omitted, and for example, “client CPU 21 requests data from server CPU 31” is described.

  The server CPU 31 receives a 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 subject has been accepted (step S506). For example, when the selection of the personal display column 61 is received via the input unit 24, the client CPU 21 determines that the selection of the target person has been received.

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

  The server CPU 31 receives a request from the client CPU 21 (step S608). Server CPU31 extracts the data of the predetermined time range regarding the subject selected from graph DB52, sensor operation DB53, and event DB54 (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 the data received in step S511 includes data related to the event extracted from the event DB 54 (step S513).

  If it is determined that data related to the event is included (YES in step S513), the client CPU 21 displays the index 81 near the time and item corresponding to the event (step S514). When it is determined that the data regarding the event is not included (NO in step S513) and after the end of step S514, the client CPU 21 determines whether an instruction to switch the display is received (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 received via the input unit 24, the client CPU 21 determines that the display switching instruction has been received.

  If it is determined that a display switching instruction has been received (YES in step S515), the client CPU 21 starts a 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 for switching between the alert screens. The processing flow of the display switching subroutine will be described later.

  When it is determined that the display switching instruction is not received (NO in step S515) and after the end of step S516, the client CPU 21 determines whether an instruction to return to the main screen described with reference to FIG. 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 an instruction to return to the main screen has not been received (NO in step S517), the client CPU 21 returns to step S507. In step S507 after the second time, the client CPU 21 may request the server CPU 31 only for difference data from the previous time. If it is determined that an instruction to return to the main screen has been received (YES in step S517), the client CPU 21 returns to step S501.

  If it is determined that the selection of the subject has not been received (NO in step S506), the client CPU 21 determines whether an instruction to end the process has been received (step S518). For example, the client CPU 21 accepts 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 an instruction to end the process has not been received (NO in step S518), the client CPU 21 returns to step S501. If it is determined that an instruction to end the process has been received (YES in step S518), the client CPU 21 ends the process.

  14 and 15 are flowcharts showing the flow of processing 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 for switching between the alert screens. The flow 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). If 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 relating to the displayed target person, for example, data for the past month (step S532).

  The server CPU 31 receives a request from the client CPU 21 (step S633). Server CPU31 extracts the data of the predetermined time range regarding the subject selected from graph DB52, sensor operation DB53, and event DB54 (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).

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

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

  If 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 relating to the displayed target person, for example, data for the past two months (step S542). .

  The server CPU 31 receives a request from the client CPU 21 (step S643). Server CPU31 extracts the data of the predetermined time range regarding the subject selected from graph DB52, sensor operation DB53, and event DB54 (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 the data received in step S546 includes data related to the event extracted from the event DB 54 (step S548).

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

  The client CPU 21 determines whether the selection of the detail button 82 has been accepted (step S550). If it is determined that it has been accepted (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 reception of selection of the close button 83 (step S552). After accepting the selection of the close button 83, the client CPU 21 returns to step S548.

  If it is determined that the selection of the detail button 82 has not been accepted (NO in step S550) and the selection of the past data button 79 has not been accepted (NO in step S541), the client CPU 21 selects the alert button 80. It is determined whether it has been accepted (step S561). If 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 event data for a predetermined time range related to the displayed target person, for example, the past two weeks (step S562). .

  The server CPU 31 receives a request from the client CPU 21 (step S663). The server CPU 31 extracts data in a predetermined time range related to the selected target person 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 has not been 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 has been accepted (step S571).

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

  According to the present embodiment, it is possible to provide an information processing apparatus or the like that displays an event occurrence history in an easy-to-understand manner. A user such as a caregiver can grasp an event that has occurred in the past and perform appropriate care or the like for the person to be monitored. When similar events occur repeatedly, measures such as early detection of illnesses and prevention of accidents can be taken by taking measures such as consultation with a doctor.

  For example, when there are frequent events that sleep time is short, the amount of sleeping pills and the like can be adjusted appropriately by attaching data and reporting to a doctor. For example, when events related to room temperature abnormalities occur frequently, it is possible to prevent diseases such as heat stroke and cold by confirming whether or not the air conditioner has failed.

  From the menu screen displayed on the display unit 25 when the menu button 76 is selected, the client CPU 21 may accept the adjustment 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 watch-type wearable sensor worn on the arm of the person to be monitored may be used. By doing in this way, data, such as a pulse, the number of steps, and the amount of activity, can be acquired and recorded in graph DB52 also at the time when the person to be monitored gets up from the bed.

  The sensor I / F device 40 and various sensors may be installed at the monitoring subject's home. One caregiver or the like can be in charge of a plurality of at-home monitoring subjects, and when an abnormality is detected, assistance can be performed with reference to the past situation.

  The indicator 81 may be displayed at an arbitrary location near the label indicating the numerical values such as temperature and sleep time, for example, on the right side, the upper side, the lower side, and 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 that displays the contents of the event related to the selected index 81 on the display unit 25. In this case, the client CPU 21 acquires a 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 is detected that the index 81 displayed on the report screen described with reference to FIGS. 8 and 9 is selected, the client CPU 21 details the date described with reference to FIG. 11 regarding the date on which the index 81 is displayed. A screen may be displayed on the display unit 25. By doing in this way, the user can grasp | ascertain quickly the condition of the monitoring subject on the day when the event occurred.

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

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

[Embodiment 2]
The present embodiment relates to an information processing system 10 that displays an index 81 on a screen that displays items not directly related to an event. Description of portions common to the first embodiment is omitted.

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

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

  Note that 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 near 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 a different color or shape depending on the item related to the event.

[Embodiment 3]
The present embodiment relates to an information processing system 10 that displays an event based on a care record input by a user. Description of portions common to the first embodiment is omitted.

  FIG. 17 is an explanatory diagram illustrating a record layout of the food and drink record DB according to the third embodiment. The eating and drinking record DB is a DB obtained by extracting the food and water intake state of the monitoring target person from the care record recorded by a caregiver or the like. The eating and drinking 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 monitoring subject is recorded. The date is recorded in the date field. In the breakfast field, the lunch field, and the dinner field, the food intake status of the monitoring subject is recorded. In the moisture field, the amount of moisture taken by the monitoring subject in one day is recorded. The eating and drinking record DB has one record for one monitoring target person's day.

  FIG. 18 is an explanatory diagram illustrating a report display screen according to the third embodiment. In FIG. 18, the food and drink record of the monitoring subject is displayed in the report column 64. Circles in the breakfast, lunch and dinner columns indicate that all meals served were eaten. The triangle indicates that only a small amount was eaten. X is an index 81 indicating that a meal was not eaten. The circle in the water column indicates that sufficient water has been ingested. The cross in the column of water is an index 81 indicating that the amount of water intake is insufficient.

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

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

  The first acquisition unit 91 acquires time-series data in a predetermined range in which the state of the monitoring target person or the environment around the monitoring target person is recorded. The 2nd acquisition part 92 acquires the event relevant to the same monitoring subject who generate | occur | produced in the same range, and the date and time or date linked | related with the said 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 the client 20, the server 30, the 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 illustrating a configuration of the information processing system 10 according to the fifth embodiment. The configuration of this embodiment will be described with reference to FIG. Note that description of portions common to the first embodiment is 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 in 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. The server CPU 31 may read a program 71 stored in a semiconductor memory 73 such as a flash memory installed 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 it in the server auxiliary storage device 33.

  A 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 that is executed by the client 20 via the network.

  The server CPU 31 reads the program 71 for executing the above-described various software processes from the portable storage medium 72 or the semiconductor memory 73 or downloads it from another server computer (not shown) via the communication unit 36. The program 71 is installed as a control program for the server 30, loaded into the main storage device 32, and 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 for the client 20, loaded into the main storage device 22, and executed by the client CPU 21. As described above, the information processing system functions as the information processing system 10 described above as a whole.

The technical features (components) described in each embodiment can be combined with each other, and new technical features can be formed by combining them.
The embodiments disclosed herein are illustrative in all respects and should not be considered as restrictive. The scope of the present invention is defined not by the above-described meaning but by the scope of the claims, and is intended to include all modifications within the meaning and scope equivalent to the scope of the claims.

10 Information processing system 20 Client 21 Client CPU
22 main storage device 23 client auxiliary storage device 24 input unit 25 display unit 26 communication unit 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 Environmental sensor 43 Human sensor 44 Toilet sensor 45 Door sensor 51 Target 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 Apnea count column 683 Sleep depth column 684 Mid-wake 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)

Obtain time-series data of a predetermined range that records the condition of the monitoring target person or the environment around the monitoring target person,
Obtaining an event related to the monitored person that occurred within the range and a date and time or date associated with the event;
A program that causes the computer to execute processing for outputting the time-series data and outputting an index corresponding to the event in association with the date and time or the position corresponding to the date in the time-series data. Obtain time-series data of a predetermined range that records the sleep depth of the monitored person and the presence or absence of multiple types of awakening activity,
The sleep depth is output in a band graph that is colored by the sleep depth along the time axis,
Dividing a portion of the band graph corresponding to the awakening time in parallel with the time axis,
A program for causing a computer to execute a process of separately outputting each divided part according to the presence or absence of each type of awakening activity. The time series data includes the monitoring subject's sleep depth and presence / absence of multiple types of awakening activity,
The sleep depth is output in a band graph that is colored by the sleep depth along the time axis,
Dividing a portion of the band graph corresponding to the awakening time in parallel with the time axis,
The program according to claim 1, wherein the divided parts are output separately according to the presence or absence of each type of activity at the time of awakening. The time series data is output by a graph in which the first axis is the date and time, and the second axis is the state of the monitoring target person or the environment around the monitoring target person,
The index is output in association with a position on the graph determined by a first axis corresponding to the date and time associated with the event and a second axis related to the content of the event. The listed program. The time series data is output by a graph in which the first axis is the date and the second axis is the state of the monitoring target person or the environment around the monitoring target person,
The index is set at a position on the graph defined by a first axis corresponding to a date associated with the event or a date including a date and time associated with the event, and a second axis associated with the content of the event. The program according to claim 1 or 3, wherein the program is output in association with each other. The time series data is output by a graph in which the first axis is the date and the second axis is the state of the monitoring target person or the environment around the monitoring target person,
When the graph associated with the event is not output, the index is output in association with a first axis corresponding to a date associated with the date associated with the event or the date associated with the event. The program according to claim 1 or claim 3. The index is output in association with a label indicating a sleep time of the monitoring target person or a temperature around the monitoring target person corresponding to a date or time associated with the event. Item 7. The program according to any one of Items 6. The color of the label indicating the sleep time of the monitored person or the temperature around the monitored person corresponding to the date or time associated with the event in the time series data related to the event, The program according to any one of claims 1 or 3 to 6, wherein the program is output by making it different from a color of a label corresponding to another date and time or a date. The program according to any one of claims 1 to 3 to 8, wherein a record of an event that notifies a warning regarding a state of the monitoring target person or an environment around the monitoring target person is acquired. Obtain time-series data of a predetermined range that records the condition of the monitoring target person or the environment around the monitoring target person,
Obtaining an event related to the monitored person that occurred within the range and a date and time or date associated with the event;
An information processing method for causing a computer to execute a process of outputting the time series data and outputting an index corresponding to the event in association with the date and time or a position corresponding to the date in the time series data. A first acquisition unit that acquires time-series data of a predetermined range in which a state of the monitoring target person or an environment around the monitoring target person is recorded;
A second acquisition unit that acquires an event related to the monitored person that occurred within the range, and a date and time or date associated with the event;
The time series data acquired by the first acquisition unit is output, and an index corresponding to the event acquired by the second acquisition unit is output in association with the date / time or the position corresponding to the date in the time series data. An information processing apparatus comprising: an output unit.

Images