JP7620799B2 - Eye drop information processing device and eye drop information processing program - Google Patents

Description

The present invention relates to an eye drop information processing device and an eye drop information processing program.

In recent years, there has been an increasing demand for managing the use of medicines. In particular, when administering medicine to elderly patients who visit hospitals, it is extremely important for medical personnel, such as doctors, who treat the patients, to know whether the patients are taking the medicines at home as prescribed. Therefore, medication support devices that prevent elderly people from taking too much medicine or forgetting to take their medicine are generally on the market (see, for example, Patent Documents 1 and 2).

However, such medication support devices are mainly designed to handle ingested medicines, and it is difficult to handle eye drops. Therefore, an eye drop action detection device that is compatible with eye drops is disclosed in, for example, Patent Document 3.

Special Publication No. 2013-531548 International Publication No. WO2009/148345 JP 2017-074197 A

However, there is a demand for intuitively knowing whether a patient is using eye drops as prescribed or not. Therefore, it is desirable to provide an eye drop information processing device and an eye drop information processing program that enable intuitively knowing whether a patient is using eye drops as prescribed or not.

According to one aspect of the present invention, an eye drop information processing device includes an acquisition unit and a generation unit. The acquisition unit acquires a plurality of monitoring data from a monitoring device that monitors the operation of an eye drop container. The generation unit generates an eye drop calendar that graphically represents an eye drop history based on a plurality of monitoring data related to the eye drop operation among the plurality of monitoring data acquired by the acquisition unit.

An eye drop information processing program according to one aspect of the present invention causes a computer to execute the following two operations.
(1) acquiring a plurality of monitoring data from a monitoring device that monitors the operation of an eye drop container; and (2) generating an eye drop calendar that graphically represents an eye drop history based on a plurality of monitoring data related to eye drop operations among the acquired plurality of monitoring data.

According to one aspect of the eye drop information processing device and eye drop information processing program of the present invention, an eye drop calendar that graphically represents the eye drop history is generated based on multiple monitoring data related to eye drop operations among the multiple monitoring data acquired. Therefore, by simply looking at the eye drop calendar, patients and medical staff can intuitively understand whether the patient is using the eye drops as prescribed.

1 is a perspective view illustrating an example of a configuration of a motion monitoring device and an eye drop container used in an eye drop information processing system according to a first embodiment of the present invention. FIG. FIG. 2 is a diagram illustrating an example of an exploded perspective configuration of the motion monitoring device of FIG. 1 . 3 is a diagram illustrating an example of a functional block of a sensor unit in FIG. 2 . 1 is a diagram illustrating an example of a schematic configuration of an eye drop information processing system according to a first embodiment of the present invention. FIG. 5 is a diagram illustrating an example of a functional block of the eye drop information processing device of FIG. 4 . FIG. 6 is a diagram illustrating an example of the concept of the tally table in FIG. 5 . FIG. 6 is a diagram showing a display example of the eye drop calendar in FIG. 5 . 5 is a diagram showing an example of a display procedure of an eye drop calendar in the eye drop information processing system of FIG. 4 . FIG. 8 is a diagram showing an example of display of eye drop information in the eye drop calendar of FIG. 7 . FIG. 8 is a diagram illustrating an example of a 3D display of eye drop actions in the eye drop calendar of FIG. 7 . FIG. 13 is a diagram illustrating an example of a schematic configuration of an eye drop information processing system according to a second embodiment of the present invention. 12 is a diagram illustrating an example of functional blocks of the eye drop information processing device and the server device of FIG. 11 . 12 is a diagram showing an example of a display procedure of an eye drop calendar in the eye drop information processing system of FIG. 11 .

Hereinafter, the embodiment of the invention will be described in detail with reference to the drawings. The following description is one specific example of the present invention, and the present invention is not limited to the following embodiment. Furthermore, the present invention is not limited to the arrangement, dimensions, and dimensional ratios of each component shown in each drawing. Furthermore, in the following description, directions such as up/down, left/right, front/back, etc. are directions seen from the patient or medical staff unless otherwise specified. The description will be given in the following order.
1. First embodiment (FIGS. 1 to 8)
1. Example of generating an eye drop calendar using an eye drop information processing device 2. Modification of the first embodiment Example of displaying eye drop operation in 3D (FIGS. 9 and 10)
3. Second embodiment (FIGS. 11 to 13)
4. Example of generating eye drop calendar by server device 4. Modification of second embodiment Example of displaying eye drop operation in 3D

1. First embodiment
[composition]
1 shows an example of a perspective configuration of a motion monitoring device 10 and an eye drop container 20 used in an eye drop information processing system 100 according to an embodiment of the present invention. The eye drop container 20 is, for example, a resin container filled with eye drops. In the eye drop container 20, for example, an opening is provided at the tip of the resin container, and the eye drops are discharged from the tip of the resin container by pointing the tip of the resin container downward and pressing the resin container.

The action monitoring device 10 holds an eye drop container 20 and monitors the action of the held eye drop container 20. The action monitoring device 10 has, for example, a cylindrical housing with an opening 10A provided at the upper end. In the action monitoring device 10, the eye drop container 20 is held in the housing of the action monitoring device 10 by fitting the eye drop container 20 into the opening 10A. As shown in Fig. 2, for example, the action monitoring device 10 has a housing upper part 11 with the opening 10A provided therein, and a housing bottom part 12 connected to the lower end of the housing upper part 11. A sensor part 13 is provided in the housing bottom part 12.

3 shows an example of a functional block of the sensor unit 13. The sensor unit 13 has, for example, a motion sensor unit 132, a data processing unit 133, a storage unit 134, a clock unit 135, a communication unit 136, and a power supply unit 137. The motion sensor unit 132, the data processing unit 133, the storage unit 134, the clock unit 135, the communication unit 136, and the power supply unit 137 are mounted on, for example, a common substrate 131.

The motion sensor unit 132 includes, for example, an inertial sensor. The inertial sensor is, for example, a MEMS (Micro Electro Mechanical Systems). The motion sensor unit 132 includes, for example, at least one of a three-axis acceleration sensor and a three-axis gyro sensor. The motion sensor unit 132 detects the movement of the eye drop container 20 by using, for example, an inertial sensor. When the movement of the eye drop container 20 is detected by the inertial sensor, the motion sensor unit 132 outputs a sensor signal in time series from the inertial sensor. Hereinafter, the time series sensor signal output from the inertial sensor is referred to as sensing data 132A of the movement of the eye drop container 20. The motion sensor unit 132 outputs the sensing data 132A to the data processing unit 133.

The data processing unit 133 is configured to include, for example, a CPU (Central Processing Unit). The data processing unit 133 processes the sensing data 132A input from the motion sensor unit 132 and the time data 135A input from the clock unit 135. When the sensing data 132A is input from the motion sensor unit 132, the data processing unit 133 acquires the clock data 135A from the clock unit 135, and generates monitoring data 134A in which the acquired clock data 135A and the sensing data 132A are associated with each other. The monitoring data 134A includes the sensing data 132A and the clock data 135A. The data processing unit 133 stores the generated monitoring data 134A in the storage unit 134. The data processing unit 133 reads out a plurality of monitoring data 134A from the storage unit 134 in response to a data output request from the eye drop information processing device 40 described later, and outputs the data to the eye drop information processing device 40 via the communication unit 136.

The storage unit 134 is composed of a non-volatile memory such as a flash memory. For example, a plurality of monitoring data 134A generated by the data processing unit 133 is stored in the storage unit 134. For example, the storage unit 134 stores eye drop information 134B. The eye drop information 134B includes, for example, the patient's name, an ID for identifying the patient, an eye drop period, the name of the eye drop, and the number of times the eye drop is applied per day. The eye drop information 134B does not have to be stored in the storage unit 134. In this case, the eye drop information 134B may be stored in, for example, an eye drop information processing device 40 described later.

The clock unit 135 is a device that outputs time data 135 A. The clock unit 135 outputs the time data 135 A to the data processing unit 133 in response to a data output request from the data processing unit 133, for example.

The communication unit 136 transmits the multiple monitoring data 134A input from the data processing unit 133 to the eye drop information processing device 40 via a network 50 (described later) in accordance with a predetermined communication standard. The power supply unit 137 includes, for example, a button battery. The power supply unit 137 supplies power to each device mounted on the substrate 131.

4 shows a schematic configuration example of the eye drop information processing system 100. The eye drop information processing system 100 includes, for example, a communication device 30 and an eye drop information processing device 40. The communication device 30 is configured to be able to communicate with the sensor unit 13 of the behavior monitoring device 10. The communication device 30 transmits a data output request transmitted from the eye drop information processing device 40 to the behavior monitoring device 10 (sensor unit 13), and transmits a plurality of monitoring data 134A transmitted from the behavior monitoring device 10 (sensor unit 13) to the eye drop information processing device 40. The communication device 30 and the eye drop information processing device 40 are connected to each other via a network 50. The network 50 is configured, for example, by a wired LAN (Local Area Network) such as Ethernet, or a wireless LAN such as Wi-Fi.

The eye drop information processing device 40 acquires a plurality of monitoring data 134A from the action monitoring device 10 via the communication device 30, and processes the acquired plurality of monitoring data 134A. The eye drop information processing device 40 has, for example, a communication unit 41, an eye drop detection model 42, memory units 43 and 44, a display unit 45, and a control unit 46, as shown in FIG.

The control unit 46 includes a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit). The control unit 46 executes, for example, a control program (not shown) for controlling various devices included in the eye drop information processing device 40. The control unit 46 further executes, for example, an eye drop calendar generating program 43A and an eye drop action reproducing program 43B stored in the storage unit 43. The eye drop calendar generating program 43A causes the control unit 46 to execute a series of procedures for generating an eye drop calendar 44B (described later). The eye drop action reproducing program 43B causes the control unit 46 to execute a series of procedures for reproducing an eye drop action in three dimensions.

The control unit 46 (hereinafter simply referred to as the "control unit 46") loaded with the eye drop calendar generating program 43A generates an eye drop calendar 44B based on a plurality of monitoring data 134A related to eye drop operation among the acquired plurality of monitoring data 134A. The control unit 46 judges whether each acquired monitoring data 134A corresponds to an eye drop operation or not, and generates the eye drop calendar 44B based on the judgment result. The control unit 46 generates a tally table 44A (described later) summarizing the judgment result, and stores it in the memory unit 44. The eye drop information processing device 40 generates the eye drop calendar 44B based on the tally table 44A.

The control unit 46 inputs the sensing data 132A to the eye drop detection model 42, and requests the eye drop detection model 42 to determine whether the sensing data 132A corresponds to an eye drop action. In response to the request, the control unit 46 obtains a determination result from the eye drop detection model 42. The control unit 46 stores the obtained determination result in the tally table 44A together with the time data 135A corresponding to the sensing data 132A input to the eye drop detection model 42. In the tally table 44A, the determination result and the time data 135A are stored in correspondence with each other. The control unit 46 generates an eye drop calendar 44B based on the multiple time data 135A included in the tally table 44A. The control unit 46 generates an eye drop calendar 44B that graphically distinguishes between days on which the eye drop usage instructions are met and days on which the eye drop usage instructions are not met, based on multiple time data 135A included in the aggregation table 44A and eye drop information 134B regarding the usage instructions of the eye drops.

The control unit 46 (hereinafter simply referred to as the "control unit 46") to which the eye drop application operation reproducing program 43B is loaded generates video data that graphically represents the operation of the eye drop container 20 based on the sensing data 132A.

The control unit 46 generates a video signal for displaying an image including the eye drop calendar 44B and outputs it to the display unit 45. The control unit 46 further generates a video signal for playing the above-mentioned video data and outputs it to the display unit 45. The display unit 45 is, for example, a liquid crystal display or an organic EL display. The display unit 45 displays an image on the display surface 40A based on the video signal input from the control unit 46. The display unit 45 displays the eye drop calendar 44B on the display surface 40A and plays the above-mentioned video data on the display surface 40A based on the video signal input from the control unit 46.

The control unit 46 may calculate the monthly eye drop application rate based on the tally table 44A and the eye drop information 134B. In this case, the control unit 46 may generate a video signal for displaying an image including the calculated eye drop application rate, and output the video signal to the display unit 45.

The eye drop detection model 42 is a learning model that, when the sensing data 132A is input from the control unit 46, outputs a determination result as to whether or not the input sensing data 132A corresponds to an eye drop operation. This learning model is a model that has been trained using the sensing data 132A corresponding to an eye drop operation as teaching data. This learning model includes, for example, a neural network. This learning model may include, for example, a deep neural network such as a convolutional neural network (CNN). The eye drop detection model 42 determines whether or not the sensing data 132A corresponds to a data corresponding to an eye drop operation, and outputs the determination result to the control unit 46.

The storage units 43 and 44 are composed of non-volatile memories such as flash memories. The storage unit 43 stores, for example, an eye drop calendar generating program 43A and an eye drop action reproducing program 43B. The storage unit 44 stores a plurality of monitoring data 134A obtained from one action monitoring device 10 by executing the eye drop calendar generating program 43A. The storage unit 44 further stores a tally table 44A, an eye drop calendar 44B, and eye drop information 134B by executing the eye drop calendar generating program 43A. Note that if the eye drop information 134B is previously stored in the storage unit 44, the tally table 44A and the eye drop calendar 44B are stored by executing the eye drop calendar generating program 43A.

6 shows an example of the concept of the tally table 44A. The tally table 44A includes a plurality of time data 134B and a plurality of discrimination results each associated with each of the time data 134B. The time data 134B is, for example, data of date and time. The discrimination results are, for example, eye drop data or an identifier representing eye drop data, or non-eye drop data or an identifier representing non-eye drop data.

7 shows an example of the display of the eye drop calendar 44B on the display surface 40A. The eye drop calendar 44B shows, for example, one month in a table format, with a square for each day. In each square, for example, a date and one or more time data 134B are displayed as character data. In each square containing one or more time data 134B, a graphical display is provided to indicate whether the eye drop usage is met. In FIG. 7, the squares for the 2nd, 3rd, 6th, and 7th days are graphically displayed to indicate that the eye drop usage is met, and the squares for the 1st, 4th, and 5th days are graphically displayed to indicate that the eye drop usage is not met.

The eye drop calendar 44B may display, for example, data included in the eye drop information 134B. The eye drop calendar 44B may display, for example, the patient's name, an ID for identifying the patient, and the like, as shown in Fig. 7. The eye drop calendar 44B may further display, for example, the monthly eye drop administration rate, as shown in Fig. 7.

[Display procedure]
Next, a description will be given of a procedure for displaying the eye drop calendar 44B in the eye drop information processing system 100. Fig. 8 shows an example of a procedure for displaying the eye drop calendar 44B in the eye drop information processing system 100.

First, the medical worker places the behavior monitoring device 10 received from the patient on the communication device 30. Next, the medical worker instructs the eye drop information processing device 40 to display the eye drop calendar 44B. Then, the control unit 46 of the eye drop information processing device 40 acquires a plurality of monitoring data 134A from the sensor unit 13 of the behavior monitoring device 10 via the communication units 41 and 30 (step S101). Next, the control unit 46 sequentially inputs the acquired plurality of monitoring data 134A to the eye drop detection model 42, thereby requesting the eye drop detection model 42 to determine whether the input sensing data 132A corresponds to data corresponding to an eye drop operation. The eye drop detection model 42 determines whether the sensing data 132A corresponds to data corresponding to an eye drop operation, and outputs the determination result to the control unit 46 (step S102). The control unit 46 acquires the determination result from the eye drop detection model 42 as a response to the input of the monitoring data 134A to the eye drop detection model 42.

The control unit 46 stores the acquired discrimination result together with the time data 135A corresponding to the sensing data 132A input to the eye drop detection model 42 in the tally table 44A. The control unit 46 stores the discrimination result and the time data 135A in the tally table 44A in association with each other. The control unit 46 generates the tally table 44A in this manner (step S103). Next, the control unit 46 generates an eye drop calendar based on the tally table 44A (step S104). Specifically, the control unit 46 generates an eye drop calendar 44B that graphically represents the eye drop history based on the multiple time data 135A included in the tally table 44A. The control unit 46 generates an eye drop calendar 44B that graphically distinguishes between days that meet the eye drop usage instructions and days that do not meet the eye drop usage instructions based on the multiple time data 135A included in the tally table 44A and the eye drop information 134B regarding the usage instructions of the eye drop.

The control unit 46 generates a video signal for displaying an image including the eye drop calendar 44B and outputs it to the display unit 45. The display unit 45 displays an image on the display surface 40A based on the video signal input from the control unit 46. The display unit 45 displays the eye drop calendar 44B on the display surface 40A based on the video signal input from the control unit 46 (step S105). Finally, the control unit 46 instructs the behavior monitoring device 10 (sensor unit 13) on the communication device 30 to erase the multiple monitoring data 134 stored in the memory unit 134 via the communication units 41 and 30. When the sensor unit 13 receives such an erasure instruction, it erases the monitoring data 134 in the memory unit 134 (step S106). In this way, the eye drop calendar 44B is displayed in the eye drop information processing system 100.

[effect]
Next, the effects of the eye drop information processing system 100 will be described.

In recent years, there has been an increasing demand for managing the use of medicines. In particular, when administering medicine to elderly patients who visit hospitals, it is extremely important for medical personnel, such as doctors, who treat the patients, to know whether the patient is taking the medicine at home as prescribed. Therefore, medicine administration support devices that prevent elderly people from taking too much medicine or forgetting to take it are generally on the market. However, such medicine administration support devices are mainly used for taking medicines, and it is difficult to deal with eye drops. Therefore, an eye drop application action detection device that is compatible with eye drops has been proposed (see, for example, Patent Document 3). However, the method described in Patent Document 3 does not make it easy to intuitively know whether the patient is taking the eye drops as prescribed.

On the other hand, in the present embodiment, an eye drop calendar 44B that graphically represents the eye drop history is generated based on a plurality of monitoring data 134A related to the eye drop operation among the plurality of acquired monitoring data 134A. This allows the patient or medical staff to intuitively know whether the patient is using the eye drops as prescribed or not just by looking at the eye drop calendar 44B.

In this embodiment, it is determined whether each piece of monitoring data 134A corresponds to the eye drop action, and the eye drop calendar 44B is generated based on the result. This makes it possible to prevent information unrelated to the eye drop action from being displayed on the eye drop calendar 44B. As a result, patients and medical staff can intuitively know whether the patient is using the eye drops as prescribed by simply looking at the eye drop calendar 44B.

In this embodiment, a tally table 44A summarizing the discrimination results is generated and stored in the storage unit 44. This makes it possible to generate an eye drop calendar 44B using the tally table 44A. As a result, patients and medical staff can intuitively know whether or not the patient is using the eye drops as prescribed simply by looking at the eye drop calendar 44B.

In the present embodiment, the monitoring data 134A includes sensing data 132A and time data 135A. It is determined whether the sensing data 132A corresponds to the eye drop action, and the determination result is stored in the tally table 44A together with the time data 135A corresponding to the sensing data 132A corresponding to the eye drop action. This makes it possible to generate the eye drop calendar 44B based on the multiple time data 135A included in the tally table 44A. As a result, the patient or medical staff can intuitively know whether the patient is using the eye drops as prescribed just by looking at the eye drop calendar 44B.

In this embodiment, an eye drop calendar 44B is generated that graphically distinguishes between days when the eye drop usage instructions are met and days when the eye drop usage instructions are not met, based on a plurality of time data 135A included in the tally table 44A and eye drop information 134B regarding the usage instructions of the eye drop. This allows patients and medical staff to intuitively know whether the patient is using the eye drop as prescribed or not, simply by looking at the eye drop calendar 44B.

In addition, in this embodiment, when the sensing data 132A is input to the eye drop detection model 42, a determination result as to whether or not the input sensing data 132A corresponds to the eye drop operation is output. This makes it possible to prevent information unrelated to the eye drop operation from being displayed on the eye drop calendar 44B. As a result, patients and medical staff can intuitively know whether or not the patient is using the eye drops as prescribed, simply by looking at the eye drop calendar 44B.

2. Modification of the First Embodiment
Next, a modification of the eye drop information processing system 100 according to the above embodiment will be described.

In the above embodiment, when the eye drop information processing device 40 (control unit 46) is displaying an eye drop calendar 44B as shown in Fig. 7 on the display unit 45, it is assumed that one time data 135A displayed on the eye drop calendar 44B is selected. At this time, the eye drop information processing device 40 (control unit 46) may generate a video signal for displaying an eye drop information display window 40-1 including the selected time data 135A and the eye drop information 134B, and output the video signal to the display unit 45. At this time, the eye drop information display window 40-1 is displayed on the display surface 40A in a manner overlapping the eye drop calendar 44B, as shown in Fig. 9, for example.

9, the eye drop information processing device 40 (control unit 46) may generate a video signal for displaying an eye drop information display window 40-1 including several buttons in addition to the time data 135A and the eye drop information 134B, and output the video signal to the display unit 45. An example of a button displayed in the eye drop information display window 40-1 is a "3D display" button.

Here, when the eye drop information processing device 40 (controller 46) is displaying an eye drop calendar 44B as shown in FIG. 9 on the display unit 45, it is assumed that one button ("3D display") displayed on the eye drop calendar 44B is selected. At this time, the eye drop information processing device 40 (controller 46) may generate video data that graphically represents the operation of the eye drop container 20 based on the sensing data 132A corresponding to the selected time data 135A. The eye drop information processing device 40 (controller 46) may further generate a video signal for playing the generated video data and output it to the display unit 45. At this time, the display unit 64 displays the operation of the eye drop container 20 on the display surface 40A based on the video signal input from the control unit 46. On the display surface 40A, for example, a 3D display window 40-3 for graphically representing the operation of the eye drop container 20 is displayed in a manner overlapping the eye drop calendar 44B.

The eye drop information processing device 40 (control unit 46) may further generate a video signal for displaying the sensing data 132A corresponding to the selected time data 135A in a graph format, and output the video signal to the display unit 45. At this time, the display unit 64 displays the sensing data 132A corresponding to the selected time data 135A in a graph format on the display surface 40A based on the video signal input from the control unit 46. On the display surface 40A, for example, as shown in FIG. 10, an eye drop graph display window 40-2 in which the sensing data 132A corresponding to the selected time data 135A is displayed in a graph format is displayed in a manner overlapping the eye drop calendar 44B.

The eye drop information processing device 40 (control unit 46) may further generate a video signal for tracing the graph of the sensing data 132A in dot display in synchronization with the graphical reproduction of the operation of the eye drop container 20, and output the generated video signal to the display unit 45. At this time, the display unit 64 displays a moving image on the display surface 40A, which traces the graph of the sensing data 132A in dot display, in synchronization with the graphical reproduction of the operation of the eye drop container 20, based on the video signal input from the control unit 46. On the display surface 40A, for example, as shown in FIG. 10, a moving image for tracing the graph of the sensing data 132A in dot display is displayed in an eye drop graph display window 40-2 in synchronization with the graphical reproduction of the operation of the eye drop container 20.

In this modification, video data that graphically represents the operation of the eye drop container 20 is generated based on the sensing data 132A. This enables, for example, a medical professional to instruct a patient on the correct way to administer eye drops.

3. Second embodiment
11 shows a schematic configuration example of an eye drop information processing system 200 according to a second embodiment of the present disclosure. The eye drop information processing system 200 includes, for example, a communication device 30, an eye drop information processing device 60, and a server device 70. The communication device 30 transmits a data output request transmitted from the eye drop information processing device 60 to the behavior monitoring device 10 (sensor unit 13), and transmits a plurality of monitoring data 134A transmitted from the behavior monitoring device 10 (sensor unit 13) to the eye drop information processing device 60. The communication device 30 and the eye drop information processing device 60 are connected to each other via a network 50. The network 50 is, for example, configured by a wired LAN (Local Area Network) such as Ethernet, or a wireless LAN such as Wi-Fi.

The eye drop information processing device 60 and the server device 70 are connected to each other via a network 80. The network 80 is, for example, a network that performs communication using a communication protocol (TCP/IP) that is commonly used on the Internet. The network 80 may be, for example, a secure network that performs communication using a communication protocol unique to the network. The network 80 is, for example, the Internet, an intranet, or a local area network.

The eye drop information processing device 60 acquires a plurality of monitoring data 134A from the action monitoring device 10 via the communication device 30, and processes the acquired plurality of monitoring data 134A. The eye drop information processing device 60 has, for example, a communication unit 61, memory units 62 and 63, a display unit 64, a communication unit 65, and a control unit 66, as shown in FIG.

The control unit 66 includes a CPU and a GPU. The control unit 66 executes, for example, a control program (not shown) for controlling various devices included in the eye drop information processing device 60. The control unit 66 further executes, for example, an eye drop information processing program 62A stored in the storage unit 62. The eye drop information processing program 62A causes the control unit 66 to execute a part of a series of procedures for generating the eye drop calendar 44B and a part of a series of procedures for reproducing the eye drop operation in three dimensions.

The control unit 66 (hereinafter, simply referred to as "control unit 66") loaded with the eye drop information processing program 62A transmits the acquired multiple monitoring data 134A to the server device 70 via the communication unit 65. As a response to the transmission of the multiple monitoring data 134A to the server device 70, the control unit 66 receives the eye drop calendar 44B from the server device 70 via the communication unit 65. The control unit 66 generates a video signal for displaying an image including the received eye drop calendar 44B, and outputs it to the display unit 64. The display unit 64 displays the image on the display surface 60A based on the video signal input from the control unit 66. The display unit 64 displays the eye drop calendar 44B on the display surface 60A based on the video signal input from the control unit 66.

The control unit 66 transmits the selected time data 135A to the server device 70 via the communication unit 65. As a response to the transmission of the time data 135A to the server device 70, the control unit 66 receives from the server device 70 via the communication unit 65 video data based on the sensing data 132A corresponding to the transmitted time data 135A. This video data is data on the operation of the eye drop container 20, which is graphically represented based on the sensing data 132A corresponding to the transmitted time data 135A. The control unit 66 generates a video signal for playing the received video data and outputs it to the display unit 64. The display unit 64 displays an image on the display surface 60A based on the video signal input from the control unit 66. The display unit 64 displays the operation of the eye drop container 20 on the display surface 60A based on the video signal input from the control unit 66.

The storage units 62 and 63 are composed of non-volatile memories such as flash memories. The storage unit 62 stores, for example, an eye drop information processing program 62A. The storage unit 63 stores a plurality of monitoring data 134A obtained from one behavior monitoring device 10 by executing the eye drop information processing program 62A. The display unit 64 is, for example, a liquid crystal display or an organic EL display. The display unit 64 displays an image on the display surface 60A based on a video signal input from the control unit 66. The display unit 64 displays the eye drop calendar 44B on the display surface 60A and plays the above-mentioned video data on the display surface 60A based on the video signal input from the control unit 66.

The server device 70 includes, for example, a communication unit 71, an eye drop detection model 42, storage units 43 and 44, and a control unit 72, as shown in FIG.

The control unit 72 includes a CPU and a GPU. The control unit 72 executes, for example, a control program (not shown) for controlling various devices included in the eye drop information processing device 60. The control unit 72 further executes, for example, an eye drop calendar generating program 43A and an eye drop action reproducing program 43B stored in the storage unit 43. The eye drop calendar generating program 43A causes the control unit 72 to execute a series of procedures for generating an eye drop calendar 44B. The eye drop action reproducing program 43B causes the control unit 72 to execute a series of procedures for reproducing an eye drop action in three dimensions.

The control unit 72 (hereinafter simply referred to as "control unit 72") into which the eye drop calendar generating program 43A is loaded generates an eye drop calendar 44B based on a plurality of monitoring data 134A related to eye drop action among the acquired plurality of monitoring data 134A. The control unit 72 judges whether each acquired monitoring data 134A corresponds to an eye drop action or not, and generates an eye drop calendar 44B based on the judgment result. The control unit 72 generates a tally table 44A summarizing the judgment result, and stores it in the memory unit 44. The server device 70 generates the eye drop calendar 44B based on the tally table 44A.

The control unit 72 inputs the sensing data 132A to the eye drop detection model 42, and requests the eye drop detection model 42 to determine whether the sensing data 132A corresponds to an eye drop action. In response to the request, the control unit 72 acquires a determination result from the eye drop detection model 42. The control unit 72 stores the acquired determination result in the tally table 44A together with the time data 135A corresponding to the sensing data 132A input to the eye drop detection model 42. In the tally table 44A, the determination result and the time data 135A are stored in correspondence with each other. The control unit 72 generates an eye drop calendar 44B based on the multiple time data 135A included in the tally table 44A. The control unit 72 generates an eye drop calendar 44B that graphically distinguishes between days on which the eye drop usage instructions are met and days on which the eye drop usage instructions are not met, based on multiple time data 135A included in the aggregation table 44A and eye drop information 134B regarding the usage instructions of the eye drops.

The control unit 72 (hereinafter simply referred to as the "control unit 72") to which the eye drop application operation reproducing program 43B is loaded generates video data that graphically represents the operation of the eye drop container 20 based on the sensing data 132A.

The control unit 72 transmits the generated eye drop calendar 44B to the eye drop information processing device 60 via the communication unit 71. The control unit 72 further transmits the above-mentioned video data to the eye drop information processing device 60 via the communication unit 71. The control unit 72 may calculate the monthly eye drop application rate based on the tally table 44A and the eye drop information 134B. In this case, the control unit 72 may transmit the calculated eye drop application rate to the eye drop information processing device 60 via the communication unit 71.

The eye drop detection model 42 is a learning model that, when the sensing data 132A is input from the control unit 72, outputs a determination result as to whether or not the input sensing data 132A corresponds to an eye drop operation. This learning model is a model that has been trained using the sensing data 132A corresponding to an eye drop operation as teaching data. This learning model includes, for example, a neural network. This learning model may include, for example, a deep neural network such as a convolutional neural network (CNN). The eye drop detection model 42 determines whether or not the sensing data 132A corresponds to a data corresponding to an eye drop operation, and outputs the determination result to the control unit 72.

[Display procedure]
Next, a description will be given of a procedure for displaying the eye drop calendar 44B in the eye drop information processing system 200. Fig. 13 shows an example of a procedure for displaying the eye drop calendar 44B in the eye drop information processing system 200.

First, the medical professional places the action monitoring device 10 received from the patient on the communication device 30. Next, the medical professional instructs the eye drop information processing device 60 to display the eye drop calendar 44B. Then, the control unit 46 of the eye drop information processing device 60 acquires a plurality of monitoring data 134A from the sensor unit 13 of the action monitoring device 10 via the communication units 41 and 30 (step S201). Next, the control unit 46 transmits the acquired plurality of monitoring data 134A to the server device 70 via the communication unit 65 (step S202).

The server device 70 (control unit 72) receives a plurality of monitoring data 134A from the eye drop information processing device 60 via the communication unit 71 (step S203). The control unit 72 sequentially inputs the received plurality of monitoring data 134A to the eye drop detection model 42, and requests the eye drop detection model 42 to determine whether the input sensing data 132A corresponds to data corresponding to an eye drop operation. The eye drop detection model 42 determines whether the sensing data 132A corresponds to data corresponding to an eye drop operation, and outputs the determination result to the control unit 72 (step S204). The control unit 72 obtains the determination result from the eye drop detection model 42 as a response to the input of the monitoring data 134A to the eye drop detection model 42.

The control unit 72 stores the acquired discrimination result together with the time data 135A corresponding to the sensing data 132A input to the eye drop detection model 42 in the tally table 44A. The control unit 72 stores the discrimination result and the time data 135A in the tally table 44A in association with each other. The control unit 72 generates the tally table 44A in this manner. Next, the control unit 72 generates an eye drop calendar based on the tally table 44A (step S205). Specifically, the control unit 72 generates an eye drop calendar 44B that graphically represents the eye drop history based on the multiple time data 135A included in the tally table 44A. The control unit 72 generates an eye drop calendar 44B that graphically distinguishes between days that meet the eye drop usage instructions and days that do not meet the eye drop usage instructions based on the multiple time data 135A included in the tally table 44A and the eye drop information 134B regarding the usage instructions of the eye drop.

The control unit 72 transmits the generated eye drop calendar 44B to the eye drop information processing device 60 via the communication unit 71 as a response to the input multiple monitoring data 134A (step S206). The eye drop information processing device 60 (control unit 66) receives the eye drop calendar 44B from the server device 70 via the communication unit 65 (step S207). When the control unit 66 receives the eye drop calendar 44B, it generates a video signal for displaying an image including the received eye drop calendar 44B and outputs it to the display unit 45. The display unit 45 displays the image on the display surface 40A based on the video signal input from the control unit 66. The display unit 45 displays the eye drop calendar 44B on the display surface 40A based on the video signal input from the control unit 66 (step S208). Finally, the control unit 66 instructs the behavior monitoring device 10 (sensor unit 13) on the communication device 30 to delete the multiple monitoring data 134 stored in the memory unit 134 via the communication units 61 and 30. Upon receiving such an erasure instruction, the sensor unit 13 deletes the monitoring data 134 in the memory unit 134 (step S209). In this manner, the eye drop information processing system 200 displays the eye drop calendar 44B.

[effect]
Next, the effects of the eye drop information processing system 200 will be described.

In this embodiment, an eye drop calendar 44B that graphically represents the eye drop history is generated based on the plurality of monitoring data 134A related to the eye drop operation among the plurality of acquired monitoring data 134A. This allows the patient or medical staff to intuitively know whether the patient is using the eye drops as prescribed or not just by looking at the eye drop calendar 44B.

In this embodiment, it is determined whether each piece of monitoring data 134A corresponds to the eye drop action, and the eye drop calendar 44B is generated based on the result. This makes it possible to prevent information unrelated to the eye drop action from being displayed on the eye drop calendar 44B. As a result, patients and medical staff can intuitively know whether the patient is using the eye drops as prescribed by simply looking at the eye drop calendar 44B.

In this embodiment, a tally table 44A summarizing the discrimination results is generated and stored in the storage unit 44. This makes it possible to generate an eye drop calendar 44B using the tally table 44A. As a result, patients and medical staff can intuitively know whether or not the patient is using the eye drops as prescribed simply by looking at the eye drop calendar 44B.

In the present embodiment, the monitoring data 134A includes sensing data 132A and time data 135A. It is determined whether the sensing data 132A corresponds to the eye drop action, and the determination result is stored in the tally table 44A together with the time data 135A corresponding to the sensing data 132A corresponding to the eye drop action. This makes it possible to generate the eye drop calendar 44B based on the multiple time data 135A included in the tally table 44A. As a result, the patient or medical staff can intuitively know whether the patient is using the eye drops as prescribed just by looking at the eye drop calendar 44B.

In this embodiment, an eye drop calendar 44B is generated that graphically distinguishes between days when the eye drop usage instructions are met and days when the eye drop usage instructions are not met, based on a plurality of time data 135A included in the tally table 44A and eye drop information 134B regarding the usage instructions of the eye drop. This allows patients and medical staff to intuitively know whether the patient is using the eye drop as prescribed or not, simply by looking at the eye drop calendar 44B.

In addition, in this embodiment, when the sensing data 132A is input to the eye drop detection model 42, a determination result as to whether or not the input sensing data 132A corresponds to the eye drop operation is output. This makes it possible to prevent information unrelated to the eye drop operation from being displayed on the eye drop calendar 44B. As a result, patients and medical staff can intuitively know whether or not the patient is using the eye drops as prescribed, simply by looking at the eye drop calendar 44B.

4. Modification of the Second Embodiment
Next, a modification of the eye drop information processing system 200 according to the second embodiment will be described.

In the second embodiment, when the eye drop information processing device 40 (control unit 46) is displaying an eye drop calendar 44B as shown in Fig. 7 on the display unit 45, it is assumed that one time data 135A displayed on the eye drop calendar 44B is selected. At this time, the eye drop information processing device 40 (control unit 46) may generate a video signal for displaying an eye drop information display window 40-1 including the selected time data 135A and the eye drop information 134B, and output the video signal to the display unit 45. At this time, the eye drop information display window 40-1 is displayed on the display surface 40A in a manner overlapping the eye drop calendar 44B, as shown in Fig. 9, for example.

9, the eye drop information processing device 40 (control unit 46) may generate a video signal for displaying an eye drop information display window 40-1 including several buttons in addition to the time data 135A and the eye drop information 134B, and output the video signal to the display unit 45. An example of a button displayed in the eye drop information display window 40-1 is a "3D display" button.

Here, when the eye drop information processing device 40 (controller 46) is displaying an eye drop calendar 44B as shown in FIG. 9 on the display unit 45, it is assumed that one button ("3D display") displayed on the eye drop calendar 44B is selected. At this time, the eye drop information processing device 40 (controller 46) may generate video data that graphically represents the operation of the eye drop container 20 based on the sensing data 132A corresponding to the selected time data 135A. The eye drop information processing device 40 (controller 46) may further generate a video signal for playing the generated video data and output it to the display unit 45. At this time, the display unit 64 displays the operation of the eye drop container 20 on the display surface 40A based on the video signal input from the control unit 46. On the display surface 40A, for example, a 3D display window 40-3 for graphically representing the operation of the eye drop container 20 is displayed in a manner overlapping the eye drop calendar 44B.

The eye drop information processing device 40 (control unit 46) may further generate a video signal for displaying the sensing data 132A corresponding to the selected time data 135A in a graph format, and output the video signal to the display unit 45. At this time, the display unit 64 displays the sensing data 132A corresponding to the selected time data 135A in a graph format on the display surface 40A based on the video signal input from the control unit 46. On the display surface 40A, for example, as shown in FIG. 10, an eye drop graph display window 40-2 in which the sensing data 132A corresponding to the selected time data 135A is displayed in a graph format is displayed in a manner overlapping the eye drop calendar 44B.

The eye drop information processing device 40 (control unit 46) may further generate a video signal for tracing the graph of the sensing data 132A in dot display in synchronization with the graphical reproduction of the operation of the eye drop container 20, and output the generated video signal to the display unit 45. At this time, the display unit 64 displays a moving image on the display surface 40A, which traces the graph of the sensing data 132A in dot display, in synchronization with the graphical reproduction of the operation of the eye drop container 20, based on the video signal input from the control unit 46. On the display surface 40A, for example, as shown in FIG. 10, a moving image for tracing the graph of the sensing data 132A in dot display is displayed in an eye drop graph display window 40-2 in synchronization with the graphical reproduction of the operation of the eye drop container 20.

In this modification, video data that graphically represents the operation of the eye drop container 20 is generated based on the sensing data 132A. This enables, for example, a medical professional to instruct a patient on the correct way to administer eye drops.

10...operation monitoring system, 10A...opening, 11...upper part of housing, 12...bottom part of housing, 13...sensor part, 20...eye drop container, 30...communication device, 40...eye drop information processing device, 40-1...eye drop information display window, 40-2...eye drop graph display window, 40-3...3D display window, 40A...display surface, 41...communication unit, 42...eye drop detection model, 43...storage unit, 43A...eye drop calendar generation program, 43B...eye drop operation reproduction program, 44...storage unit, 44A...aggregation table, 44B...eye drop calendar, 45...display unit, 46...control unit, 50...network, 60...eye drop information processing device device, 60A...display surface, 61...communication unit, 62...memory unit, 62A...eye drop information processing program, 63...memory unit, 64...display unit, 65...communication unit, 66...control unit, 70...server device, 71...communication unit, 72...control unit, 80...network, 100...eye drop information processing system, 131...substrate, 132...motion sensor unit, 132A...sensing data, 133...data processing unit, 134...memory unit, 134A...monitoring data, 134B...eye drop information, 135...timing unit, 135A...time data, 136...communication unit, 137...power supply unit, 200...eye drop information processing system.

Claims (5)

a monitoring device including a motion sensor that detects a movement of an eye drop container, a timer that outputs time data, and a first storage that stores a plurality of sets of time-series motion data and the time data obtained each time the movement of the eye drop container is detected by the motion sensor; and an acquisition unit that acquires the plurality of sets from the first storage unit in accordance with an instruction from a user of an eye drop information processing device ;
a determination unit that determines whether each of the time-series motion data acquired by the acquisition unit corresponds to data corresponding to an eye drop action;
a generating unit configured to generate an eye drop calendar that graphically represents an eye drop history based on one or more of the time-series motion data that are determined by the determining unit to correspond to an eye drop action among the plurality of time-series motion data acquired by the acquiring unit ;
A second storage unit;
Equipped with
the discrimination unit generates a compilation table summarizing discrimination results and stores the compilation table in the second storage unit;
The generation unit generates the eye drop calendar based on the tally table,
the determination unit determines whether each of the time-series motion data acquired by the acquisition unit corresponds to data corresponding to an eye drop action, and stores the determination result in the tallying table together with the time data corresponding to the time-series motion data corresponding to the eye drop action;
The generation unit generates the eye drop calendar based on one or more of the time data included in the tally table.
Eye drop information processing device. The eye drop information processing device according to claim 1, wherein the generation unit generates the eye drop calendar that graphically distinguishes between days on which the eye drop usage instructions are met and days on which the eye drop usage instructions are not met, based on one or more of the time data included in the aggregation table and eye drop information regarding the usage instructions of the eye drop. The eye drop information processing device according to claim 1 , wherein the generating unit generates video data that graphically represents an operation of the eye drop container based on the sensing data. The eye drop information processing device according to claim 1 , wherein the discrimination unit is a learning model that, when the sensing data is input, outputs a discrimination result as to whether or not the input sensing data corresponds to data corresponding to an eye drop action. a monitoring device including a motion sensor that detects a movement of an eye drop container, a timer that outputs time data, and a memory that stores a plurality of sets of time-series motion data and the time data obtained each time the movement of the eye drop container is detected by the motion sensor; acquiring the plurality of sets from the memory in accordance with an instruction from a computer user ;
determining whether each of the acquired time-series motion data corresponds to an eye drop application operation;
generating an eye drop calendar that graphically represents an eye drop history based on one or more of the time-series motion data determined to correspond to an eye drop action among the acquired multiple time-series motion data ;
determining whether each of the acquired time-series motion data corresponds to an eye-applying action, and storing the determination result in a compilation table together with the time data corresponding to the time-series motion data corresponding to the eye-applying action;
generating the eye drop calendar based on one or more of the time data included in the tally table;
An eye drop information processing program that causes a computer to execute the above.