JP7354538B2 - Terminal devices, monitoring systems and programs - Google Patents

Description

The present disclosure relates to a terminal device used in a monitoring system, and more specifically, to a terminal device that executes processing for recording information regarding a monitored person in the monitoring system.

In recent years, the number of residents in nursing care facilities has been on the rise due to the declining birthrate and aging population. On the other hand, the shortage of care workers for residents is becoming increasingly serious. Therefore, there is a need for a support system that reduces the burden on care workers and allows a small number of people to perform care work.

Regarding a support system for nursing care work, for example, Japanese Patent Application Laid-Open No. 2014-90913 (Patent Document 1) states, ``A camera is provided to take an image of a patient on the bed, and from the image captured by the camera, the patient's upper body is raised up, the patient is The hallway light is equipped with a status determining unit that outputs an attention state signal when the patient is away from the bed, and the nurse call base unit receives the attention state occurrence signal and displays the patient image on the display unit to notify the patient. ” discloses a nurse call system (see [Summary]).

Japanese Patent Application Publication No. 2014-90913

As described in Patent Document 1, information processing devices are effectively utilized in monitoring systems. In recent years, in order to increase the convenience of staff, it has become possible to send various information from the monitoring system server to terminals carried by each care worker (staff), and to input information to the server via the terminal. It is being done. In such a situation, staff members are required to request authentication from the server each time they use each application, which can sometimes feel cumbersome.

The present disclosure has been made in view of the above background, and an objective in one aspect is to provide a technology that improves the convenience of terminals carried by each staff member.

According to certain aspects of the present disclosure, a communication interface for communicating with a server, a memory, a first application for obtaining and displaying information regarding a state of a monitored person, and a first application for recording information regarding a monitored person. a second application; and a processor that executes a second application, the processor stores communication information used for communication with the server regarding the first application in memory, and stores communication information used for communication regarding the second application in the memory. A terminal device is provided that is configured to transmit communication information stored in a server to a server.

The processor is configured to notify a request to start the first application when communication information is not stored in the memory when receiving an instruction to communicate with the server regarding the second application. Good too.

The instruction to communicate with the server regarding the second application may include an instruction to start the second application.

The processor may be configured to run the first application in the background of the second application.

According to another aspect of the present disclosure, a monitoring system including a server and a terminal device is provided. The terminal device includes a communication interface for communicating with the server, a memory, a first application for acquiring and displaying information regarding the state of the person being monitored, and a second application for recording information regarding the person being monitored. and a processor that executes. The processor stores communication information used for communication with the server regarding the first application in the memory, and transmits the communication information stored in the memory to the server for communication regarding the second application. It is composed of

A program is provided that is executed by a processor of a terminal device that can communicate with the server, thereby causing the processor to execute a process for recording information regarding the monitored person. The terminal device includes a memory. The processor is capable of executing a first application that acquires and displays information regarding the state of the monitored person, stores communication information used for communication with the server regarding the first application in the memory, and executes the program. , causes the processor to execute the steps of receiving an instruction to communicate with the server, and transmitting communication information stored in the memory to the server in order to communicate with the server in response to the instruction.

The program may further cause the processor to perform a step of notifying a request to start the first application when the communication information is not stored in the memory when receiving an instruction to communicate with the server.

The instruction to communicate with the server may include an instruction to start a program.

According to an aspect of the present disclosure, if communication is established between a terminal device and a server for an application that obtains and displays information regarding the state of the monitored person, the staff member records information regarding the monitored person. There is no longer a need for an operation to establish communication between the terminal device and the server for the application to be used.

These and other objects, features, aspects and advantages of the present invention will become apparent from the following detailed description of the invention, taken in conjunction with the accompanying drawings.

It is a diagram showing an example of the configuration of a monitoring system. It is a diagram showing the hardware configuration of a sensor box 100, a management device 200, and a terminal device 300 of the monitoring system. 9 is a diagram showing an example of a detection range of a sensor in a living room 900. FIG. 2 is a diagram illustrating a first example of an overview of notification processing to each staff member by the management device 200. FIG. 5 is a diagram showing an example of a staff management table 550 that the management device 200 stores in the storage device 220. FIG. 3 is a diagram illustrating an example of a sequence of notification processing to each staff member by the management device 200. FIG. 3 is a diagram illustrating an example of internal processing of the management device 200 when the management device 200 notifies the terminal device 300. FIG. 7 is a diagram illustrating a second example of an overview of notification processing to each staff member by the management device 200. FIG. FIG. 2 is a diagram illustrating an example of the flow of event notification in the monitoring system. 2 is a diagram showing an example of an event list managed by the management device 200. FIG. 3 is a diagram showing an example of an event notification screen displayed on the terminal device 300. FIG. 12 is a diagram illustrating an example of an operation screen displayed when a row r3 indicating an unsupported event is tapped on the notification screen 411 of FIG. 11. FIG. FIG. 3 is a diagram for explaining changes in the status of a notification application in the terminal device 300. FIG. It is a figure showing an example of an initial screen of a care record application. 3 is a diagram schematically showing an example of how session IDs are stored in the memory of the terminal device 300. FIG. It is a flowchart which shows an example of the process at the time of starting a care record application. FIG. 3 is a diagram for explaining one mode of notification requesting a user to start a notification app.

Hereinafter, embodiments of the technical idea according to the present disclosure will be described with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

<A. System overview＞
FIG. 1 is a diagram showing an example of the configuration of a monitoring system. As an example of the monitoring target, residents in each room provided in the room area RM of the facility 10 are employed. In the monitoring system of FIG. 1, living rooms 900A and 900B (hereinafter collectively referred to as "living room 900") are provided in the living room area RM. Room 900A is assigned to resident 800A. Room 900B is assigned to resident 800B (hereinafter, residents 800A and 800B will be collectively referred to as "resident 800").

The monitoring system includes a gateway server 11, a switching device 12, an access point 13, a management device 200, sensor boxes 100A and 100B (hereinafter collectively referred to as "sensor box 100"), and a sensor box 100. It includes various communicating devices and terminal devices 300A, 300B, 300C, and 300D (hereinafter collectively referred to as "terminal devices 300").

Gateway server 11 interconnects the internal network of facility 10 and the external network 16 of facility 10 . The external network 16 is, for example, the Internet or a public telephone line network. Further, a cloud server 400 , a push server 14 , and a wireless base station 15 are connected to the external network 16 .

The switching device 12 interconnects each device in the internal network of the facility 10 . In some aspects, a router or switch may be used as switching device 12. In the example shown in FIG. 1, the number of exchange devices 12 is two, but the number is not limited to this. The internal network of facility 10 may be configured by a combination of multiple switching devices 12.

The access point 13 is used to connect the terminal device 300 to the internal network of the facility 10. In some aspects, a Wi-Fi® (Wireless Fidelity) router may be used as the access point 13.

The management device 200 receives event information from the sensor box 100 in the facility 10 and manages the residents 800 in each room 900. The management device 200 also communicates with each terminal device 300, manages the staff who maintains the terminal device 300, and sends various notifications to the terminal device 300. Note that the management device 200 may use the external push server 14 when transmitting various notifications to the terminal device 300. Further, the external cloud server 400 may have some or all of the functions of the management device 200.

The sensor box 100 acquires information regarding the resident 800 in each room 900 by cooperating with the camera and sensor built into the sensor box 100 and other various sensors in the room 900. Furthermore, the sensor box 100 transmits the acquired information regarding the resident 800 to the management device 200 via the internal network. Details of the sensor box 100 will be described later.

The terminal device 300 is used by staff members engaged in nursing care at the facility 10. The staff uses the terminal device 300 to transmit care records and the like to the management device 200. Furthermore, if a problem occurs with the resident 800, the staff member uses the terminal device 300 to receive a notification from the management device 200. The terminal device 300 is connected to the access point 13 in the facility 10 and communicates with the management device 200 via the internal network. In the example of this specification, staff members 1, 2, 3, and 4 hold terminal devices 300A, 300B, 300C, and 300D, respectively.

The terminal device 300 communicates with the management device 200 via the base station 15 and the gateway server 11 outside the facility 10 . When the terminal device 300 communicates with the management device 200 from outside the facility 10, some of the services provided from the management device 200 to the terminal device 300 may be restricted.

In the example of FIG. 1, the number of rooms included in the monitoring system is two, but the number is not limited to this. Similarly, the number of other devices such as the terminal device 300, the access point 13, and the switching device 12 is not limited to the example shown in FIG.

The living room 900A includes a bed 901A, a toilet 902A, and furniture 903A as facilities. A door sensor 510A is installed on the door of the living room 900A to detect whether the door is opened or closed. A toilet sensor 520A is installed on the door of the toilet 902A to detect whether the toilet 902A is opened or closed. An odor sensor 530A is installed on the bed 901A to obtain excretion information of the resident 800A. The resident 800A is equipped with a vital sensor 540A that detects vital information of the resident 800A. An example of the detected vital information is the resident's body temperature. Another example is the resident's breathing. Yet another example is the resident's heart rate. Yet another example is two or more types of information among these pieces of information. In the living room 900A, the resident 800A can operate the care call handset 500A. The equipment in the living room 900B is also the same as that in the living room 900A.

Below, each of the beds 901A, 901B, toilets 902A, 902B, furniture 903A, 903B, care call handsets 500A, 500B, door sensors 510A, 510B, toilet sensors 520A, 520B, odor sensors 530A, 530B, and vital sensors 540A, 540B. , when collectively referring to "bed 901," "toilet 902," "furniture 903," "care call handset 500," "door sensor 510," "toilet sensor 520," "smell sensor 530," and "vital sensor," respectively. 540".

The sensor box 100 has built-in sensors for detecting the behavior of objects within the living room 900. An example of a sensor is a Doppler sensor for detecting motion of an object. Another example is a camera. Still other examples are the care call handset 500, the door sensor 510, the toilet sensor 520, the odor sensor 530, or the vital sensor 540. The sensor box 100 includes at least one of these sensors as a sensor.

<B. Hardware configuration>
FIG. 2 is a diagram showing the hardware configuration of the sensor box 100, the management device 200, and the terminal device 300 of the monitoring system.

(sensor box 100)
The sensor box 100 includes a control device 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a communication interface 104, a camera 105, a Doppler sensor 106, a wireless communication device 107, and a storage device. 120.

Control device 101 controls sensor box 100. Control device 101 is configured, for example, by at least one integrated circuit. The integrated circuit includes, for example, at least one CPU (Central Processing Unit), at least one ASIC (Application Specific Integrated Circuit), at least one FPGA (Field Programmable Gate Array), or a combination thereof.

An antenna (not shown) and the like are connected to the communication interface 104. The sensor box 100 exchanges data with an external communication device via the antenna. External communication devices include, for example, the management device 200, the terminal device 300, the access point, the cloud server 400, and other communication terminals.

Camera 105, in one implementation, is a near-infrared camera. The near-infrared camera includes an IR (Infrared) projector that projects near-infrared light. By using a near-infrared camera, an image showing the inside of living room 900 can be captured even at night. In other implementations, camera 105 is a surveillance camera that receives only visible light. In still other implementations, the camera 105 may be a 3D sensor or a thermography camera. Sensor box 100 and camera 105 may be configured integrally or may be configured separately.

Doppler sensor 106 is, for example, a microwave Doppler sensor, and detects the behavior (movement) of objects in living room 900 by emitting and receiving radio waves. Thereby, the biometric information of the resident 800 in the living room 900 can be detected. In one example, the Doppler sensor 106 emits a 24 GHz band microwave toward the bed 901 of each room 900, and receives the reflected wave reflected by the resident 800. The reflected waves undergo a Doppler shift due to the movement of the resident 800. The Doppler sensor 106 can detect the breathing state and heart rate of the resident 800 from the reflected waves.

Wireless communication device 107 receives signals from care call handset 500, door sensor 510, toilet sensor 520, odor sensor 530, and vital sensor 540, and transmits the signals to control device 101. For example, the care call handset 500 includes a care call button 501, and when the care call button 501 is operated, it transmits a signal to the wireless communication device 107 indicating that the care call button 501 has been operated. Door sensor 510, toilet sensor 520, odor sensor 530, and vital sensor 540 each transmit their respective detection outputs to wireless communication device 107.

The storage device 120 is, for example, a storage medium such as a hard disk or an external storage device. The storage device 120 stores programs executed by the control device 101 and various data used to execute the programs. The various data may include behavior information of the resident 800.

At least one of the above programs and data may be stored in a storage device other than the storage device 120, as long as the storage device is accessible by the control device 101 (for example, the storage area of the control device 101 (such as a cache memory), the ROM 102, It may be stored in the RAM 103 or an external device (for example, the management device 200, the terminal device 300, etc.).

(behavior information)
The above behavior information will be explained. The behavior information is, for example, information indicating that the resident 800 has performed a predetermined behavior. In one example, the predetermined actions include "get up" indicating that the resident 800 has woken up, "leave the bed" indicating that the resident 800 has left the bedding, and "fall" indicating that the resident 800 has fallen from the bedding. , and "fall" indicating that the resident 800 has fallen.

In one embodiment, control device 101 generates behavior information of resident 800 associated with each room 900 based on images captured by camera 105 installed in each room 900 . For example, the control device 101 detects the head of the resident 800 from the above-mentioned image, and based on the detected time change in the size of the head of the resident 800, the control device 101 detects the "wake up" of the resident 800. ”, “getting out of bed”, “fall”, and “fall”. Hereinafter, a specific example of the generation of behavior information will be described in more detail.

First, the storage device 120 stores the location area of the bed 901 in the living room 900, a first threshold Th1, a second threshold Th2, and a third threshold Th3. The first threshold Th1 is used by the control device 101 to identify the size of the head of the resident between the lying position and the sitting position within the area where the bed 901 is located. The second threshold Th2 is set by the control device 101 in order to identify whether or not the resident is in a standing posture based on the size of the resident's head in the living room 900 excluding the area where the bed 901 is located. used by The third threshold Th3 is set by the control device 101 in order to identify whether or not the resident is in a recumbent position based on the size of the resident's head in the living room RM excluding the area where the bed 901 is located. used.

The control device 101 extracts a moving object region as a region of the person of the resident 800 from the target image, for example, by a background subtraction method or a frame subtraction method. The control device 101 further uses a neural network trained for head detection to perform head detection from the extracted moving body region, for example, by circular or elliptical Hough transform, or by pattern matching using a head model prepared in advance. The head region of resident 800 is extracted using the determined threshold value. The control device 101 detects "getting up," "getting out of bed," "falling over," and "falling down" from the extracted head position and size.

The control device 101 determines whether the head position extracted as described above is within the location area of the bed 901 and the size of the head extracted as described above is determined to be in a lying position using the first threshold Th1. It may be determined that the action "wake up" has occurred when a change in the size of the posture from the size of the sitting posture is detected.

When the position of the head extracted as described above moves from within the region where the bed 901 is located to outside the region where the bed 901 is located, the control device 101 controls the size of the head extracted as described above. It may be determined that the action "getting out of bed" has occurred when it is detected that the size has changed from a certain size to the size of the standing posture by using the second threshold Th2.

When the position of the head extracted as described above moves from within the region where the bed 901 is located to outside the region where the bed 901 is located, the control device 101 controls the size of the head extracted as described above. If the size changes over time from a certain size to the size of the lying posture by using the third threshold Th3, it may be determined that the action "fall" has occurred.

The control device 101 determines that the position of the head extracted as described above is located in the living room 900 excluding the area where the bed 901 is located, and that the size of the extracted head is determined by using the third threshold Th3. If it is detected that the size has changed from a certain size to the size of the lying posture, it may be determined that the action "fall" has occurred.

As explained above, in one specific example, the control device 101 of the sensor box 100 generates behavior information of the resident 800. Note that in the monitoring system, other elements may generate behavior information of the resident 800 using images inside the living room 900.

(Management device 200)
The management device 200 includes a control device 201 , a ROM 202 , a RAM 203 , a communication interface 204 , a display interface 205 , an operation interface 207 , and a storage device 220 .

Control device 201 controls management device 200 . Control device 201 is configured, for example, by at least one integrated circuit. The integrated circuit is configured, for example, by at least one CPU, at least one ASIC, at least one FPGA, or a combination thereof.

An antenna (not shown) and the like are connected to the communication interface 204. The management device 200 exchanges data with an external communication device via the antenna. External communication equipment includes sensor box 100, for example.

The display interface 205 is connected to the display 206 and sends an image signal for displaying an image to the display 206 according to commands from the control device 201 and the like.

The operation interface 207 is, for example, a USB (Universal Serial Bus) terminal, and is connected to the input device 209. Operation interface 207 receives a signal indicating a user operation from input device 209 . The input device 209 is, for example, a mouse, a keyboard, a touch panel, or other device capable of accepting user input operations.

The storage device 220 is, for example, a storage medium such as a hard disk or an external storage device. In one implementation, storage device 220 stores a program executed by control device 201, but the program may be stored in another storage device accessible by control device 201.

(Terminal device 300)
Terminal device 300 includes a control device 301 , a RAM 303 , a communication interface 304 , a display 305 , an input device 306 , and a built-in memory 320 .

Control device 301 controls terminal device 300 . Control device 301 is configured, for example, by at least one integrated circuit. The integrated circuit is configured by, for example, at least one CPU, at least one ASIC, at least one FPGA, or a combination thereof.

An antenna (not shown) and the like are connected to the communication interface 304. The terminal device 300 exchanges data with an external communication device via the antenna and the access point 13. External communication devices include, for example, the sensor box 100, the management device 200, and the like.

The display 305 is realized by, for example, an organic EL (Electro Luminescence) display. Input device 306 is realized, for example, by a touch sensor overlaid on display 305. The touch sensor accepts various operations on the terminal device 300 through touch operations, and outputs the contents of the operations to the control device 301 .

Built-in memory 320 is, for example, a storage medium such as an eMMC (Embedded Multimedia Card). As an example, the built-in memory 320 stores a program executed by the control device 301, but the program may be stored in a storage device other than the built-in memory 320 as long as it is a storage device that the control device 301 can access. Good too.

(“Program” in this specification)
In the monitoring system, various "programs" may be provided not as a single program but as a part of an arbitrary program. Various "programs" can be realized by arbitrary multiple programs working together. In one example, when the control device 101 of the sensor box 100 implements the functions described herein by executing a first program, the first program may include some modules of the second program. may be used. Even if the first program does not include some modules for realizing the function, if it mainly contributes to realizing the function, it deviates from the purpose of the program as a program for realizing the function. It's not something you do. Additionally, some or all of the functions described herein may be implemented by dedicated hardware. Furthermore, a device that provides the functions described in this specification may have some or all of its functions provided by an external device as a so-called cloud service.

(Modified example of behavior information detection)
A modified example of behavior information will be explained. In one embodiment, the control device 101 may detect "getting up,""getting out of bed,""lyingdown," and "falling down" as the resident's 800 behavior information.

More specifically, in the monitoring system, an area occupied by the bed 901 (hereinafter referred to as a "bed area") is set in advance for an image taken by the camera 105. The bed area may be manually set in advance, or may be automatically detected using an image processing technique such as template matching. The information specifying the bed area is stored, for example, in the storage device 120, but is not limited thereto. The information may be stored in any storage device as long as it can be accessed by the element (for example, the control device 101) that detects the resident's behavior information.

The control device 101 detects "waking up" as the resident's behavior information when a part of the area occupied by the resident in the image overlaps with the bed area.

The control device 101 detects "leave bed" as the resident's behavior information when the area occupied by the resident in the image is not included in the bed area.

The control device 101 detects "lying down" as the resident's behavior information when the area occupied by the resident in the image is included in the bed area and the amount of movement of the resident is less than a predetermined amount.

The control device 101 detects "fall" as the resident's behavior information when the area occupied by the resident in the image is not included in the bed area and the amount of movement is greater than or equal to a predetermined amount. .

The detected behavioral information is stored in a given storage device (eg, storage device 120). Note that in the monitoring system, detection of resident behavior information may be performed by an element other than the control device 101. For example, the control device 201 of the management device 200 may detect behavior information of the resident using an image acquired from the camera 105 of the sensor box 100.

<C. Sensing mode of Doppler sensor>
In the sensor box 100 of the present disclosure, the camera 105 is provided as an example of an image sensor, and the Doppler sensor 106 is provided as an example of a microwave sensor. The control device 101 uses the Doppler sensor 106 of each room 900 in at least two sensing modes (microbody motion sensing mode and distance sensing mode) in which the states of the residents to be detected are different from each other. In one example, the control device 101 switches the mode by changing the output mode of the microwave by the Doppler sensor 106. For example, the Doppler sensor 106 emits unmodulated continuous waves in micro-motion sensing mode, and emits frequency-modulated waves in distance sensing mode. Each mode will be explained below.

(Microbody motion sensing mode)
In micromotion sensing mode, Doppler sensor 106 emits an unmodulated continuous wave. Thereby, the sensor box 100 can detect the presence or absence of a resident's movement in the living room while operating the Doppler sensor 106 with relatively low power. In the micro-motion sensing mode, the sensor box 100 is expected to acquire information such as whether or not the resident on the bed is breathing, the respiratory rate, and the heart rate.

(distance sensing mode)
In the distance sensing mode, the Doppler sensor 106 emits frequency modulated waves, so that the sensor box 100 detects the distance between the sensor box 100 and the object to be operated (occupant). In the distance sensing mode, the detection range may cover the entire area inside the living room 900. Thereby, even if the resident moves away from the bed 901 in the living room 900, the distance between the resident and the Doppler sensor 106 can be detected based on the detection output of the Doppler sensor 106.

In one embodiment, in the distance sensing mode, the control device 101 uses the distance obtained using the detection output of the Doppler sensor 106 and the captured image (or video) from the camera 105 to A person's condition (fall, fall from bed, etc.) can be detected.

FIG. 3 is a diagram showing an example of the detection range of the sensor in the living room 900. In the example of FIG. 2, the sensor box 100 is installed on the ceiling CL of the living room 900. Range AR schematically represents the detection range of the sensor. If the sensor is a Doppler sensor 106, the Doppler sensor 106 detects behavior occurring within range AR. If the sensor is a camera, the camera 105 captures an image within the range AR.

Note that the sensor box 100 does not necessarily have to include the camera 105 and/or the Doppler sensor 106. Camera 105 and/or Doppler sensor 106 may be provided outside sensor box 100, similar to door sensor 510 and the like. The control device 101 may acquire the detection output of the camera 105 and/or Doppler sensor 106 provided outside the sensor box 100 via a given interface.

The vital sensor 540 does not necessarily have to be worn by the resident. In one example, the vital sensor 540 is realized by an infrared sensor or the like installed apart from the resident, and outputs vital information (body temperature) by detecting the resident's temperature. In other examples, vital sensor 540 is implemented by Doppler sensor 106. The Doppler sensor 106 irradiates microwaves toward the resident. The microwave causes a Doppler effect due to slight displacement of the resident's chest caused by the heartbeat, causing its frequency to vary. The Doppler sensor 106 detects the resident's heartbeat based on the frequency fluctuation. In yet other examples, Doppler sensor 106 detects the resident's breathing.

As described with reference to FIGS. 2 and 3, the sensor box 100 can acquire "behavior information" of the resident 800 using various sensors and cameras. The management device 200 can monitor the status of each resident by receiving events including "behavior information" from the sensor box 100. Furthermore, the management device 200 issues a notification (for example, resident 800A has fallen, etc.) to the staff terminal device 300 based on the received event, thereby making it possible to provide appropriate nursing care to the resident. can.

<D. Processing notifications to staff＞
The management device 200 can issue a notification to the staff terminal device 300 based on the event received from the sensor box 100. However, if the staff member is on break and is outside the facility 10, the staff member may not be able to respond appropriately to the notification. Therefore, with reference to FIGS. 4 to 7, a method in which the management device 200 selects a staff member who can respond to a notification and sends the notification to the selected staff member will be described.

FIG. 4 is a diagram illustrating a first example of an overview of notification processing to each staff member by the management device 200. In the example shown in FIG. 4, it can be seen that the staff members 1 and 2 holding the terminal devices 300A and 300B are inside the facility 10. Further, it can be seen that the staff members 3 and 4 holding the terminal devices 300C and 300D are outside the facility 10.

For example, assume that the sensor box 100A transmits an event 451 including behavior information of the resident 800A to the management device 200. The management device 200 determines that the resident 800A requires care based on the acquired event 451.

The management device 200 transmits a notification 452 linked to the event to the terminal devices 300A and 300B held by the staff members 1 and 2 in the facility 10, respectively. On the other hand, even if the staff members 3 and 4 outside the facility 10 receive the notification, there is a high possibility that they will not be able to respond immediately. Therefore, the management device 200 does not transmit the notification 453 associated with the event to the terminal devices 300C and 300D.

As described above, the management device 200 selects only the staff who can immediately care for the resident 800 at the facility 10, and sends a notification to the selected staff to provide appropriate care to the resident 800. Can be provided. Furthermore, since the management device 200 does not send unnecessary notifications, it is possible to reduce the burden on staff who are outside the facility during breaks or the like.

FIG. 5 is a diagram showing an example of a staff management table 550 that the management device 200 stores in the storage device 220. The staff management table 550 includes a staff ID 551, a priority 552, a timestamp 553, a status 554, an IP address 555, and location information 556.

The staff ID 551 is an identifier for uniquely identifying a staff member. The priority 552 is the priority of the staff that the management device 200 refers to when transmitting a notification. For example, if the staff member 1 is in the facility 10 and is free, there is a high possibility that the staff member 1 will be able to respond immediately upon receiving the notification. Therefore, the priority of Staff 1 becomes high. Further, if the staff member 3 is eating lunch outside the facility 10, there is a low possibility that the staff member 3 will be able to respond immediately even if the staff member 3 receives the notification. Therefore, the priority of staff 3 becomes low. Management device 200 calculates priority 552 based on time stamp 553, status 554, IP address 555, and location information 556.

The timestamp 553 is the timestamp when the management device 200 last communicated with each terminal device 300. Status 554 is the status of each staff member. In the example shown in FIG. 5, the status 554 includes "Available" indicating that the staff member is free, "Currently responding" indicating that the staff member is working on other tasks, and "Working" indicating that the staff member is taking a break such as lunch break. These include "rest" indicating that the staff is working, and "vacation" indicating that the staff is not at work, but these are just examples and may include other states.

The IP address 555 is the source address of the terminal device 300 that the management device 200 acquires when communicating with the terminal device 300 of each staff member. The management device 200 determines the network to which the terminal device 300 belongs by referring to the IP address 555. The management device 200 then determines whether a staff member holding the terminal device 300 is present in the facility 10 based on the network to which the terminal device 300 belongs.

Location information 556 is information regarding the location of each terminal device 300. The location information 556 may be the latitude and longitude obtained by the GPS (Global Positioning System) function of the terminal device 300, or may be the identifier of an access point to which the terminal device 300 has connected. In an emergency, the management device 200 may refer to the location information 556 and send a notification to the terminal device 300 of the staff member located closest to the facility 10 from among the staff members located outside the facility 10 .

FIG. 6 is a diagram illustrating an example of a sequence of notification processing performed by the management device 200 to each staff member. Referring to FIG. 6, an example will be described in which the management device 200 communicates with the terminal device 300A of the staff member 1 who is inside the facility 10 and the terminal device 300C of the staff member 3 who is outside the facility 10.

In step S605, the terminal device 300A communicates with the management device 200 through the operation of the staff member 1. Since the terminal device 300A is connected to the internal network of the facility 10, it can communicate with the management device 200 without going through the gateway server 11. In the communication, the terminal device 300A transmits a message including at least an ID that identifies the terminal device 300A or the staff member 1 to the management device 200.

In step S610, the terminal device 300C communicates with the management device 200 through the operation of the staff member 3. Since the terminal device 300C is connected to the external network 16 of the facility 10, it is necessary to communicate with the management device 200 via the gateway server 11. In the communication, the terminal device 300C transmits a message including at least an ID for identifying the terminal device 300C or the staff member 3 to the management device 200.

In step S615, the gateway server 11 transfers the communication from the terminal device 300C to the management device 200. Note that when there is communication from outside, the gateway server 11 may block communication from devices that are not permitted to access the internal network of the facility 10 through filtering or authentication processing.

In step S620, the management device 200 updates the staff management table 550 based on the content of communication with the terminal devices 300A and 300C. When there is a communication from each terminal device 300, the management device 200 refers to the ID that identifies the terminal device 300 or staff included in the communication, and records the timestamp 553 and status 554 of the corresponding record in the staff management table 550. , updates the IP address 555 and location information 556. Furthermore, the management device 200 calculates the priority level 552 based on the updated information.

In step S625, the management device 200 receives an event including "behavior information" from any sensor box 100 in the facility 10.

In step S630, the management device 200 refers to the staff management table 550 and determines the staff member to whom the notification based on the received event will be sent. The management device 200 may select multiple staff members, or may select only the staff member with the highest priority 552. Furthermore, the management device 200 may select all the staff members whose priority level 552 is above a certain value.

In step S635, the management device 200 transmits a notification associated with the event to the terminal device 300 of the staff member selected in step S630. In the example shown in FIG. 6, the management device 200 selects the staff member 1 as the notification destination.

In step S640, the terminal device 300A transmits a response notification to the management device 200 based on the input from the staff member 1. Note that, based on receiving the response notification, the management device 200 may re-notify other terminal devices 300 other than the terminal device 300A that the person in charge has been determined. If the management device 200 notifies the staff in the facility 10 in step S640, it does not need to execute the processes from step S645 onwards.

In step S645, when there is no staff member in the facility 10 who can respond to the event and the event that has occurred is of high urgency, the management device 200 controls the terminal device 300 of the staff member outside the facility 10. Send notifications to. In the example shown in FIG. 6, the management device 200 selects the staff member 3 as the notification destination.

In step S650, the terminal device 300C transmits a response notification to the management device 200 based on the input from the staff member 3. Based on receiving the response notification, the management device 200 may re-notify the other terminal device 300 that sent the notification that the person in charge has been determined.

FIG. 7 is a diagram illustrating an example of internal processing of the management device 200 when the management device 200 notifies the terminal device 300. In one aspect, the control device 201 of the management device 200 may read a program for performing the processing in FIG. 7 from the storage device 220 and execute it.

In step S710, the control device 201 determines whether there is a communication request from the terminal device 300 of each staff member. When the control device 201 determines that there is a communication request from the terminal device 300 of each staff member (YES in step S710), the control device 201 moves the control to step S720. Otherwise (NO in step S710), the control device 201 moves control to step S740.

In step S720, the control device 201 communicates with the terminal device 300 that has made the communication request. In the communication, the control device 201 acquires all or part of the source address, staff ID (or terminal device ID), staff status information, and location information of the terminal device 300. The processing in step S720 corresponds to the processing in steps S605 and S615 in FIG.

In step S730, the control device 201 updates the staff management table 550 based on the information acquired through the communication in step S720. The process in step S730 corresponds to the process in step S620 in FIG.

In step S740, the control device 201 determines whether an event from the sensor box 100 has been notified. If the control device 201 determines that the event has been notified from the sensor box 100 (YES in step S740), the control device 201 moves the control to step S750. Otherwise (NO in step S740), the control device 201 ends the process.

In step S750, the control device 201 reads the staff management table 550 from the storage device 220 and selects a staff member to whom a notification associated with the event is to be sent. The process in step S750 corresponds to the process in step S630 in FIG.

In step S760, the control device 201 transmits a notification linked to the event to the terminal device 300 of the staff member selected in step S750. The process in step S760 corresponds to the process in step S635 in FIG.

In step S770, the control device 201 determines whether there is a response from any of the terminal devices 300 that sent the notification associated with the event. The control device 201 may continue to wait for a response for a certain period of time. If the control device 201 determines that there is a response from any of the terminal devices 300 that sent the notification associated with the event (YES in step S770), the process ends. The process in step S770 corresponds to the process in step S640 of FIG. 6 by the management device 200. Otherwise (NO in step S770), the control device 201 moves control to step S780.

In step S780, the control device 201 also sends a notification associated with the event to the terminal device 300 with a low priority. For example, if there is no response from any staff member inside the facility 10, the control device 201 sends a notification to the terminal device 300 of the staff member outside the facility 10. After executing the process of step S780, the control device 201 may repeat the processes of steps S770 and S780 until there are no more terminal devices 300 that are candidates for transmitting a notification associated with the event. The process in step S780 corresponds to the process in step S645 in FIG.

As described with reference to FIGS. 4 to 7, the management device 200 updates the staff management table 550 in advance based on the content of communication with the terminal device 300, and manages the priority of each staff member. By referring to the priority, the management device 200 can appropriately select the staff member to whom the notification should be sent when the resident 800 requires care. This makes it possible to increase convenience for the resident 800 and reduce the burden on the staff.

<E. Notification of events in the monitoring system>
FIG. 9 is a diagram illustrating an example of the flow of event notification in the monitoring system. In the monitoring system of this embodiment, when a resident operates care call handset 500, information representing the operation is transmitted to management device 200 via sensor box 100. Further, when the sensor box 100 generates behavioral information such as "falling down", it transmits the behavioral information to the management device 200. When the control device 201 of the management device 200 receives the operation information and behavior information of the care call handset 500, it registers an event corresponding to each piece of information in an event list (FIG. 10, which will be described later). In this example, the management device 200 functions as a management server that manages the status of the resident.

The control device 201 of the management device 200 transmits the event list to the terminal device 300. The management device 200 may transmit the event list directly to the terminal device 300, or may transmit the event list via the gateway server 11. Upon receiving the event list, the terminal device 300 notifies each event included in the event list.

<F. Event notification via notification app>
Referring to FIGS. 10 to 12, event notification of "behavior information" of resident 800 will be described.

(Event list)
FIG. 10 is a diagram showing an example of an event list managed by the management device 200. In one implementation example, upon receiving event information from the sensor box 100, the control device 201 of the management device 200 manages the event in an event list. Note that the event information may be generated by the management device 200. That is, upon receiving the sensor detection output from the sensor box 100, the control device 201 generates event information using the detection output.

As shown in FIG. 10, the event list includes nine items (event ID, detection unit ID, person to be cared for, event type, date and time of occurrence, image, progress information, staff ID, and corresponding date and time). The event ID identifies each piece of event information. The detection unit ID identifies a room that is a target of event information. The care target person identifies the resident associated with the room that is the target of the event information. The event type identifies the type of event information, such as the type of "behavior information". The occurrence date and time specifies the date and time when the event targeted by the event information occurred, and specifies, for example, the date and time when the output targeted by the event information was detected. The image represents an image included in the output that is the subject of event information.

Among the above nine items, three items (progress information, staff ID, and corresponding date and time) are information regarding the staff corresponding to the event information. The progress information indicates whether or not the staff responded to the event. The staff ID identifies the staff member corresponding to the event. The response date and time represents the date and time when the staff responded to the event.

As an example, a case will be described in which behavior information "fall" is generated in Mr. A's room (room number 101) at 12:39 on a certain day. When the sensor box 100 installed in the living room with room number 101 generates the behavior information "fall", it transmits the behavior information to the management device 200. In this case, the behavior information "fall" is accompanied by information specifying the event occurrence time (12:39) and the room (room number 101).

When the control device 201 of the management device 200 receives the behavior information "Fall" and the information specifying the time of occurrence and the room, it associates these with a new event ID and creates an event list along with the progress information "Not handled". Register. Information associated with event ID "014" in FIG. 10 is an example of information registered in this example. The sensor box 100 may further add an image photographed by the camera 105 to the action information "fall". The control device 201 associates the image with the same event ID as the action information "fall" and registers it in the event list (image "i014" in FIG. 10).

(Event notification screen)
FIG. 11 is a diagram showing an example of an event notification screen displayed on the terminal device 300. The control device 201 of the management device 200 transmits the event list to the terminal device 300. The terminal device 300 notifies each event in the received event list, for example, as a function of an application (hereinafter referred to as a "notification application") installed on the terminal device 300.

The notification screen 411 shown in FIG. 11 is a screen for notifying each event included in the event list shown in FIG. 10. The control device 301 of the terminal device 300 displays a notification screen 411 on the display 305 as an example of a display screen of a notification application. The notification screen 411 includes areas a1 to a4 in order from the top. Area a1 is a tab area and can be scrolled in the horizontal direction. Area a2 and area a4 are fixed areas. Area a3 is a scroll area and can be scrolled in the vertical direction. A list of events in the event list is displayed in the scroll area a3, and various icons and keys for operations are arranged in the areas a1, a2, and a4.

Events are displayed in each of the plurality of rows in the scroll area a3. In the example of FIG. 10, rows r1 and r2 each display information for event IDs 010 and 011, respectively. Row r3 collectively displays a plurality of event IDs 012 to 015 that meet a predetermined condition. An example of the predetermined condition is an event in which the progress information is "not handled" and the care recipients are common.

The scroll area a3 may display part of the event list. In the scroll area a3, the display may be scrolled by a staff member's scroll operation (a flick of a finger sliding in a predetermined direction), thereby changing the displayed event.

As an example of display content, row r1 of the notification screen 411 will be described.
Row r1 contains the room number (room 101), care recipient (Mr. A (Ichiro Yamashita)), care staff ID (user 0003), date and time of occurrence, and progress information (for event ID001 whose progress information is "handled"). (already supported) is displayed. Row r1 also displays an icon i1 (nurse cap) so that the user can intuitively recognize that the event type is a care call (operation on a care call button).

As another example of display content, row r3 of the notification screen 411 will be described.
All event IDs 012 to 015 whose progress information is "not handled" have a common care recipient (or room number). Therefore, the notification app displays these events together in one row r3. Row r3 displays the duration of the unsupported state (“unsupported 0 minutes” in FIG. 11). An example of the duration of the unsupported state is the elapsed time from the earliest occurrence time of the events to be displayed to the current time. An example of a thumbnail image to be displayed is a thumbnail image of an image associated with the latest event (the one with the latest date and time of occurrence) among the events to be displayed. Note that priorities may be set among a plurality of event types, and a thumbnail image of an image associated with the event with the highest priority among the events to be displayed may be displayed. In one example, the behavioral information "Fall" is given a higher priority than the behavioral information "Care Call."

When displaying multiple events in the same row, the notification app may display icons corresponding to each event in one row. In the example of FIG. 11, row r3 displays, in addition to the icon i1 representing a care call, an icon i2 representing getting up, an icon i3 representing getting out of bed, and an icon i4 representing falling.

FIG. 12 is a diagram showing an example of an operation screen displayed when row r3 indicating an unsupported event is tapped on the notification screen 411 of FIG. 11. The control device 301 of the terminal device 300 displays an operation screen 412 on the display 305 as an example of a display screen of the notification application.

The operation screen 412 displays images to be notified. When the care staff member responds to the event (for example, calls to the room to be notified), the care staff member taps the key k1 (“Respond”). In response, control device 301 transmits information indicating that key k1 has been tapped to management device 200. In response, the control device 201 changes the value of the progress information of the event information corresponding to row r3 from "unsupported" to "completed" in the event list. Furthermore, in the event information corresponding to row r3, the control device 201 registers information that identifies the staff member associated with the terminal device 300 that is the transmission source of the information as the staff ID, and also registers the information as the response date and time. Register the sending time.

By tapping the key k2 (“talk”) on the operation screen 412, the staff member can talk to the resident 800 (call out). This call is realized by the notification app using the telephone function of the terminal device 300 to make a call to the care call handset 500 in each room.

By tapping the key k3 (“Watch LIVE”) on the operation screen 412, the staff member can cause the display 305 to display a live video taken by the camera 105 that captures the interior of the current room number 101. Such video display is realized, for example, by the notification application using the communication function of the terminal device 300 to obtain a captured image from the camera 105 via the management device 200.

By tapping key k4 (“Temporary OFF”) on the operation screen 412, the staff may be able to stop notifications about new events that have occurred in the room corresponding to row r3, or may be notified as a handled event. For example, the notification app transmits information indicating that key k4 has been tapped to management device 200. In response, the control device 201 registers "handled" as the progress information of the event corresponding to the room that is the target of row r3, among the events newly registered in the event list.

When the key k10 in the tab area a1 of the operation screen 412 is tapped, the notification app returns the screen displayed on the display 305 to the previous screen (notification screen 411 in FIG. 11).

<G. Notification app status>
FIG. 13 is a diagram for explaining changes in the status of the notification application in the terminal device 300. FIG. 13 shows four states A to D of the notification app.

State A represents a state in which the terminal device 300 is in operation and the notification application is not activated. In state A, the control device 301 displays an initial screen on the display 305. The initial screen includes a care record application icon 1301 and a notification application icon 1302. The care record app will be described later. When the icon 1301 is tapped, the control device 301 launches a notification app. As a result, the state of the terminal device 300 is shifted to state B.

In state B, the control device 301 operates the notification app in the foreground. In state B, for example, the notification screen 411 of FIG. 11 is displayed on the display 305. The control device 301 shifts the state of the terminal device 300 to state C when an operation to start another application or an operation to operate another application in the foreground is performed.

In state C, the notification app runs in the background. After that, if no operation is received for a predetermined period of time or more, the control device 301 shifts the state of the terminal device 300 to a sleep state.

State D in FIG. 13 shows an example of the display on the display 305 when the event list is received from the management device 200 during the sleep state. In one example, in response to receiving the event list, the notification application generates a banner representing an event that occurred after the time when the sleep state was entered (an event whose occurrence date and time is later than the time when the sleep state was entered), and displays the banner on the display 305. to be displayed. In the example of FIG. 13, a banner 1303 is displayed. When the banner 1303 is tapped, the control device 301 operates the notification app in the foreground.

<H. Care record app＞
FIG. 14 is a diagram showing an example of the initial screen of the care record application. The care record application is an application for recording the condition of residents. More specifically, the terminal device 300 transmits resident information input via the care record application to the management device 200. The management device 200 manages the input information about each resident, for example, as a care record for the resident. When icon 1302 (FIG. 13) is tapped, control device 301 starts the care record application and displays screen 810 shown in FIG. 14 on display 305.

As shown in FIG. 14, screen 810 includes nine circular icons displayed at the top and center, and three icons displayed at the bottom. The former nine icons are for "Meals," "Excretion," "Vitals," "Snacks," "Regular Medications," "Oral Care," "Hydration," "Temporary Medications," and "Individual Training." is operated to enter information for the item. The latter three icons include an icon 811 for specifying a resident, an icon for checking each resident's record, and an icon for inputting care record application settings.

<I. Server authentication for app use>
At least some of the applications installed on the terminal device 300 require authentication by the management device 200 (server) in order to execute the applications. In one implementation example, in order to authenticate a certain application (herein referred to as "application A" for the sake of explanation), the control device 301 of the terminal device 300 sends authentication information (for example, user ID and password) to the management device 200. ) to send. The control device 201 of the management device 200 verifies the authentication information, and when determining that the authentication information is correct, creates a session with the terminal device 300 and transmits the session ID together with the access token. Upon receiving the session ID, control device 301 stores the session ID in memory (for example, RAM 303). Thereafter, the control device 301 transmits data regarding application A to the management device 200 along with the stored session ID. Thereby, the terminal device 300 communicates with the management device 200 in order to execute application A by using the session generated above.

(How session ID is stored)
FIG. 15 is a diagram schematically showing an example of how session IDs are stored in the memory of the terminal device 300. As shown in FIG. 15, in the terminal device 300, the session ID is stored in association with the server information and the application ID. The server information identifies the server that issued the session ID. The application ID identifies the application whose authentication information has been verified (that is, the application being executed on the terminal device 300). For example, if the session ID "0012345" shown in FIG. 15 is notified from the management device 200 regarding the notification application, the server information "SERVER001" shown in FIG. 15 represents the management device 200, and the application ID "10 ” represents a notification app.

The terminal device 300 according to the present embodiment may use the session ID notified about the notification application to use the care record application. That is, in the management device 200, the notification application and the care record application do not need to be distinguished from each other and treated as a single application. As a result, if the user (staff) has been authenticated by the management device 200 for use of the notification app, there is no need for the user (staff) to be authenticated for use of the care record app. This reduces the number of times the staff is required to input authentication information, improving convenience for the staff.

(Processing flow)
FIG. 16 is a flowchart illustrating an example of processing when the care recording application is started. With reference to FIG. 16, communication between the terminal device 300 and the management device 200 for executing the care record application will be described.

In step S10, the control device 301 determines whether activation of the care recording application has been instructed. An example of the instruction is a tap on the icon 1302. The control device 301 repeats the control in step S10 until it determines that the instruction has been input (NO in step S10), and when it determines that the instruction has been input (YES in step S10), the control proceeds to step S12. .

In step S12, the control device 301 determines whether the session ID issued by the management device 200 for the notification application is stored in the terminal device 300. In one example, the control device 301 determines whether a session ID associated with an application ID corresponding to the notification application is stored in the memory within the terminal device 300. If the control device 301 determines that the session ID is stored (YES in step S12), the control proceeds to step S16, and if not (NO in step S12), the control proceeds to step S14.

In step S14, the control device 301 notifies the user of a request to start the notification app, and then returns control to step S10. FIG. 17 is a diagram for explaining one aspect of notification requesting the user to start a notification application. As shown in FIG. 17, a screen 1700 is displayed on the display 305 of the terminal device 300. Screen 1700 includes a pop-up 1701 containing the message "Please launch the notification app." Note that the notification is not limited to visual notification, and may be made in other forms such as audio.

When an instruction to start the notification app is input, the control device 301 starts the notification app and requests authentication from the management device 200 regarding the notification app. At this time, the control device 301 requests authentication by transmitting authentication information regarding the notification application. The authentication information may be input when the notification application is started, or may be already stored in the terminal device 300. After authenticating the user of the terminal device 300, the management device 200 transmits the session ID for the notification application to the terminal device 300. The control device 301 stores the session ID in the memory within the terminal device 300.

In one example, the notification app may be executed in the foreground on the terminal device 300 when launched. When a session is established between the terminal device 300 and the management device 200 for the notification app, the notification app causes the control device 301 to execute the notification app in the background and the care record app in the foreground. may be instructed.

Returning to FIG. 16, in step S16, the control device 301 connects to the management device 200 using the session ID of the notification application stored in the terminal device 300.

In step S18, the control device 301 executes the operation of the care record application. In this operation, for example, resident information (for example, meal information) input by the user is registered in the management device 200.

According to the present disclosure, the control device 301 stores the session ID used for communication with the management device 200 regarding the notification application in the memory within the terminal device 300. Then, the control device 301 transmits the session ID stored in the memory to the management device 200 for communication regarding the care record application. In one implementation example, when the care record application is started in the terminal device 300 while the notification application is running in the background, the care record application establishes a connection between the notification application and the management device 200. The session is used to communicate with the management device 200. In another implementation example, when the care record application is started while the notification application is running in the foreground on the terminal device 300, the control device 301 executes the notification application in the background and causes the care record application to run in the foreground. Execute. The care record application communicates with the management device 200 using the session established with the management device 200 for the notification application.

In the present disclosure, the session ID is an example of communication information. The communication information may be authentication information (eg, user ID and password) for the notification app. In this case, authentication information is stored in the memory of the terminal device 300 in association with the notification application. In order to connect to the management device 200 for the care record application, the control device 301 reads authentication information associated with the notification application from the memory and transmits the authentication information to the management device 200 . In this case, the control device 301 may transmit the authentication information to the management device 200 as authentication information for a notification application (although the care recording application is executed).

The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims rather than the above description, and it is intended that all changes are included within the meaning and scope equivalent to the claims.

10 facility, 11 gateway server, 12 switching device, 13 access point, 14 push server, 15 wireless base station, 16 external network, 100, 100A, 100B sensor box, 101, 201, 301 control device, 102, 202 ROM, 103 , 203, 303 RAM, 104, 204, 304 Communication interface, 105 Camera, 106 Doppler sensor, 107 Wireless communication device, 120, 220 Storage device, 200 Management device, 205 Display interface, 206, 305 Display, 207 Operation interface, 209 , 306 input device, 300, 300A, 300B, 300C, 300D, 303A, 303C terminal device, 320 built-in memory, 400 cloud server, 500, 500A, 500B care call handset, 501 care call button, 510, 510A, 510B door sensor, 520, 520A, 520B Toilet sensor, 530, 530A, 530B Odor sensor, 540, 540A, 540B Vital sensor, 800, 800A, 800B Resident, 900, 900A, 900B Room, 901, 901A, 901B Bed, 902, 902A, 902B Toilet, 903, 903A, 903B Furniture.

Claims (7)

a communication interface for communicating with the server;
memory and
a processor that executes a first application that acquires and displays information regarding the state of the monitored person; and a second application that records information regarding the monitored person;
The processor includes:
storing communication information used for communication with the server regarding the first application in the memory;
configured to transmit the communication information stored in the memory to the server for communication regarding the second application ;
When an instruction to communicate with the server regarding the second application is received and the communication information is not stored in the memory, a request to start the first application is notified. terminal device. The processor is configured to start the second application when the communication information is stored in the memory when receiving an instruction to start the second application. The terminal device according to claim 1 . 3. The terminal device according to claim 1, wherein the instruction to communicate with the server regarding the second application includes an instruction to start the second application. The terminal device according to any one of claims 1 to 3 , wherein the processor is configured to execute the first application in the background of the second application. A monitoring system comprising a server and a terminal device,
The terminal device is
a communication interface for communicating with the server;
memory and
a processor that executes a first application that obtains and displays information regarding the state of the monitored person; and a second application that records information regarding the monitored person;
The processor includes:
storing communication information used for communication with the server regarding the first application in the memory;
configured to transmit the communication information stored in the memory to the server for communication regarding the second application ;
When an instruction to communicate with the server regarding the second application is received and the communication information is not stored in the memory, a request to start the first application is notified. A monitoring system. A program that is executed by a processor of a terminal device that can communicate with a server and causes the processor to execute processing for recording information regarding a monitored person, the program comprising:
The terminal device includes a memory,
The processor includes:
A first application is executable to obtain and display information regarding the condition of the monitored person;
storing communication information used for communication with the server regarding the first application in the memory;
The program causes the processor to
accepting instructions for communication with the server;
transmitting the communication information stored in the memory to the server in order to communicate with the server in accordance with the instruction ;
The communication instruction with the server is a communication instruction regarding a process for recording information regarding the monitored person,
The program further causes the processor to:
The program further executes the step of notifying a request to start the first application when the communication information is not stored in the memory when an instruction to communicate with the server is received. 7. The program according to claim 6 , wherein the instruction to communicate with the server includes an instruction to start the program.

Images