Method for managing information about contents accommodated in container, user device and system for executing method, and recording medium on which program for executing method is recorded

Abstract

The present invention relates to a method for managing contents, which is executed by a user device that is communicably connected to a dispensing device having a sensor for sensing dispensing of contents accommodated in a container and comprises a processor, a memory, and a communication module, the method comprising: a pairing step of connecting communication to the dispensing device; a step of registering medication setting information inputted into the user device; a step of generating a medication schedule and medication information on the basis of the medication setting information; and a step of updating the medication information by receiving the dispensing information of the contents sensed by the sensor, wherein the medication setting information includes the quantity of contents in the container, the number of daily medications, a medication setting time, and a dose, the medication schedule includes the medication setting time and a dose for each medication setting time, and the medication information includes the medication status for the day, the quantity of contents remaining in the container, and the total amount of medication taken.

Description

A method for managing information on contents accommodated in a container, a user device and system for executing the method, and a recording medium recording a program for executing the method

[0001] The present invention relates to a method for managing information on contents contained in a container and a user device and system for executing the method, and more particularly, to a method and system for managing medication information so that a user can take a fixed amount of medication according to a medication schedule.

[0002] Medicines, vitamins, health supplements, etc. are often manufactured as solid granule-type contents (hereinafter referred to as "contents"). The contents of medicines, health supplements, etc. are taken in a fixed or necessary amount to maximize their effectiveness and prevent misuse and addiction. These contents are sold in a designated storage container, but when opening the container cover and taking out the contents, excessive contents often spill out, causing inconvenience. To prevent such excessive spillage and to dispense only the fixed amount of contents, fixed-quantity dispensers are used in various fields.

[0003] By connecting the metered dose dispenser to a user device (e.g., a smartphone app), it can go beyond simple metered dose dispensing and manage medication information such as medication schedules and medication history. Furthermore, it can be used to track changes in drug efficacy based on medication patterns. In this specification, "medication" is not limited to drugs, but also includes metered intake of health supplements such as vitamins.

[0004] A method and device are required to efficiently manage the remaining amount of contents, medication history, medication schedule, etc. in a user device connected to a quantitative dispenser and communication.

[0005] Furthermore, it is necessary to maintain accurate and stable medication information management even when various exceptional events occur during medication administration. These exceptional events include malfunctions of the metered dose dispenser, dispensing errors due to user error, and container replacement. Conventional metered dose dispensers and user devices have struggled to adequately address these exceptional events.

[0006] (Patent Document 1) KR 10-2241567 B

[0007] The present invention has been devised to improve the above problems, and provides a system for efficiently managing contents in a user device connected to a quantitative dispenser through communication, and a method and program thereof.

[0008] Another object of the present invention is to provide a method and program that enable continuous and accurate medication management even when the same quantitative dispenser is installed in a new container or an event such as over-dispensing due to malfunction occurs.

[0009]

[0010] In order to solve the above problem, according to one aspect of the present invention, a contents management method is provided that is communicatively connected to a discharge device having a discharge detection sensor for detecting discharge of contents contained in a container, and is executed by a user device including a processor, a memory, and a communication module.

[0011] The above-described content management method may include a pairing step for communicating with the dispensing device; a step for registering medication setting information input to a user device; a step for generating a medication schedule and medication information based on the medication setting information; and a step for receiving the dispensing information of the contents detected by the sensor to update the medication information. The medication setting information includes the quantity of the contents in the container, the number of times to take the medication per day, the medication setting time, and the dosage. It is preferable that the medication schedule includes the medication setting time and the dosage for each medication setting time, and the medication information includes the medication status for the day, the quantity of the remaining contents in the container, and the total amount of the medication.

[0012] The above-mentioned same-day medication status includes the time of medication on the same day and the amount of medication taken at that time, and the discharge information of the contents detected by the sensor includes the discharge time and amount of medication.

[0013] When a container combination detection signal is received from the above discharge device, the container combination detection indication is provided to the UI module, and a display requesting confirmation of whether or not the container is new is provided, and when confirmation of a new container is input, a request for input of the quantity of contents in the new container is provided to the UI module.

[0014] When confirmation of a new container is input through the UI module, a container change history is generated, which includes the time of separation of the dispensing device from the old container and the time of attachment to the new container. When the quantity of contents in the new container is input, it is desirable to update the quantity of contents remaining in the container with the input quantity of contents in the new container.

[0015] When providing the above container combination detection display as a UI module, a display requesting confirmation of whether the container is new is provided, along with a display confirming whether there is an operational error or a user error.

[0016] The above operational errors include an over-dispensing error in which the contents are over-dispensed, and a jamming error in which the contents are caught in the dispensing mechanism. An input section is provided for inputting the quantity of contents to be reinjected in response to the above over-dispensing error, and the medication information is modified based on the input quantity of contents to be reinjected.

[0017] The above contents are contained in a container that is integral with the dispensing device or a container that is detachably coupled to the dispensing device and are discharged by the dispensing device, and the dispensing device includes a sensor for detecting the discharge of the contents. The medication information is updated based on the discharge information of the contents detected by the sensor. The container combination detection signal includes an on / off signal and on / off time of a container combination detection switch included in the dispensing device.

[0018] A computer-readable program including commands for executing the above method can be stored in a storage medium, and the storage medium is a storage medium in which the computer-readable program is stored.

[0019] According to another aspect of the present invention, a user device is provided, which is connected to a dispensing device having a sensor for detecting dispensing of contents contained in a container, by communication, and which includes a processor, a memory, and a communication module. The user device includes a communication module for two-way communication with the dispensing device, a data management module for generating and processing medication information and a medication schedule and displaying them through a UI module, a UI module, a storage unit, and a control module for controlling the communication module, the data management module, the UI module, and the storage unit.

[0020] The above medication information includes the quantity of the remaining contents in the container, the total quantity of the contents discharged from the container, and the medication history, and the medication schedule and medication information are generated based on the medication setting information. The medication setting information includes the quantity of the contents in the container, the number of times to be taken per day, the medication setting time, and the dosage, and the medication schedule includes the medication setting time and the dosage for each medication setting time. The medication information includes the medication status for the day, the quantity of the remaining contents in the container, and the total amount of the stimulating and discharging medication, and the medication information is updated based on the discharge of the contents in the container detected by the sensor.

[0021] The above medication information further includes a medication history included in the dispensing device, and the UI module includes a medication mode that displays medication information and a medication schedule, and a device mode that displays connectivity with the dispensing device and the status of the dispensing device. The device mode further includes a container history that displays the time of coupling and disengagement between the container and the dispensing device, and a cover history that displays the time of attachment and detachment of the dispensing device and the cover.

[0022] According to another aspect of the present invention, a medication management system is provided. The medication management system comprises: a dispensing device, which is detachably coupled to a container or integrally coupled to the container, and includes a dispensing mechanism for dispensing a fixed amount of content contained in the container, a sensor for detecting the fixed amount of content dispensing, a communication unit, a switch, and a control unit; the user device; and a management server capable of communicating with the user device or the dispensing device. The management server receives medication information based on the dispensing of content detected by the sensor and medication setting information, performs statistical processing, and transmits the information to a third-party device.

[0023] The above contents may be one of the health supplements in the form of solid tablets, vitamins, minerals, etc.

[0024] The above management server may process data received from a user device or a dispensing device and provide one or more of a medication record, medication status, device management, and sensing data.

[0025] The above medication status indicates the medication status by device ID and by day, and includes the medication time and whether the medication was taken, container separation, combination, cover opening, and time of each status.

[0026] The management server processes data received from the dispensing device and / or user device and provides it as sensing data. The sensing data provides the number of times the contents (pills) were dispensed from the container and event information. Event information includes the content (pill) dispensing, container tilting, device and pill bottle separation, mounting, cap opening and closing, and other event details, as well as the date and time the event occurred.

[0027]

[0028] According to one aspect of the present invention, a patient, medical staff, or administrator effectively manages a medication schedule, medication history, remaining amount of contents in a container, container change history, etc., thereby helping a user to take a prescribed amount of medication according to the medication schedule.

[0029] According to the present invention, an administrator can track medication history to analyze a user's medication pattern and use it to verify drug efficacy or change prescriptions.

[0030] In addition, according to the present invention, even if the quantitative dispenser is installed in a new container or the contents are re-injected due to over-dispensing by mistake, medication information can be continuously and accurately managed.

[0031]

[0032] Figure 1 is an exploded perspective view of a container equipped with a quantitative dispensing device.

[0033] Figure 2 is a cross-sectional side view of a container equipped with a quantitative dispensing device.

[0034] Figure 3 is a cross-sectional view showing changes in the position and posture of the contents and the dispensing device during the process of dispensing the contents by tilting the container (200) equipped with the quantitative dispensing device (300).

[0035] Fig. 4 is a cross-sectional view showing a container detection switch and a cover detection switch provided in the quantitative dispensing device of the present invention.

[0036] FIG. 5 is a block diagram showing the configuration and communication connection relationship between a discharge device and a user device according to one embodiment of the present invention.

[0037] Fig. 6 is a block diagram showing an example of the firmware configuration of the discharge device of the present invention.

[0038] Figure 7 is a network configuration diagram of a medication management system according to one embodiment of the present invention.

[0039] Figure 8 is a UI (User Interface) screen of a user device according to one embodiment of the present invention.

[0040] Figure 9 is a flowchart showing the process of operating the container change mode according to one embodiment of the present invention.

[0041] Figure 10 is a UI (User Interface) screen of a container change mode according to one embodiment of the present invention.

[0042] Figure 11 is a flowchart of modifying a medication count value according to one embodiment of the present invention.

[0043] Figure 12 is a main page screen of a medication management website provided by a management server according to one embodiment of the present invention.

[0044] Figure 13 is a screen when Medication Status is selected from the main menu according to one embodiment of the present invention.

[0045] Figure 14 is a sensing data display screen of a medication management website provided by a management server according to one embodiment of the present invention.

[0046] Fig. 15 is a flowchart illustrating a method for modifying a discharge count value according to one embodiment of the present invention.

[0047] Figure 16 is a flowchart illustrating a medication alarm method according to one embodiment of the present invention.

[0048] Figure 17 is a block diagram illustrating the concept of a medication alarm method according to one embodiment of the present invention.

[0049]

[0050] To fully understand the present invention, preferred embodiments of the present invention will be described with reference to the drawings. The embodiments of the present invention may be modified in various forms, and the scope of the present invention should not be construed as being limited to the embodiments described in detail below. The shapes of elements in the drawings may be exaggerated to emphasize clearer explanation. As used herein, the term "coupled" or "connected" includes not only direct coupling or connection of two components, but also indirect coupling or connection through another component. In addition, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the gist of the present invention are omitted.

[0051] First, referring to FIGS. 1 to 4, a dispensing device for quantitative dispensing of contents contained in a container will be described in detail.

[0052] Fig. 1 is an exploded perspective view of a container (200) equipped with a discharge device (300). As shown in Fig. 1, the container (200) and the discharge device (300) may be detachably coupled, or the container (200) and the discharge device (300) may be manufactured as an integral part. A cover (400) may be detachably coupled to the upper portion of the discharge device (300). Republic of Korea Patent Publication No. 2020-0144458 illustrates a coupling structure of a container and a detachable discharge device, the contents of which are incorporated herein as an exemplary part of the present specification.

[0053] As for the specific configuration and operating mechanism of the discharge device, the contents of the content discharge device and discharge detection sensor disclosed in Korean Patent No. 2157445 may be included as part of the description as an example of the discharge device of this specification.

[0054] Referring to Fig. 2, the configuration of the discharge mechanism (100), which is a mechanical element of the discharge device (300), will be described. Fig. 2 is a side cross-sectional view of a container equipped with the discharge device. The discharge mechanism (100) is composed of mechanisms that discharge only a fixed amount of the contents (1) when the contents (1) are discharged through the discharge device (300). As illustrated in Fig. 2, the discharge mechanism (100) includes a guide passage (182) which is a discharge path of the contents, a guide portion (180) which forms the guide passage, and a passage movement portion (123) which blocks or opens the discharge path of the contents. The passage movement portion (123) includes an opening member (124), a blocking member (127), and a rotational axis (125), and when a user tilts the container, the passage movement portion rotates about the rotational axis (125) within a predetermined angular range according to the tilting angle. The rotation of the passage movement part (123) rotates its constituent parts, the opening member (124) and the blocking member (127), to open or block the passage of the contents.

[0055] Referring to FIG. 3, a method for controlling the passage of contents (1) by the rotation of the passage movement part (123) according to the angle at which the user tilts the container will be described. FIG. 3 is a cross-sectional view showing changes in the position and posture of the passage movement part (123) and contents (1) during the process of tilting a container equipped with a discharge device (300) and discharging contents. FIG. 3 shows the state of the passage movement part (123) in the initial state (a) when the container is tilted at a predetermined angle, for example, 135 degrees, and (b) when the container is further tilted and the contents come into contact with the opening member (124) and begin to apply force to the opening member (124), and (c) when the contents are discharged and the next contents located at the rear (upstream) thereof are blocked by the blocking member (127). The passage movement part (123) rotates due to a combined action of the weight of the passage movement part (123), the inertia of the passage movement part (123), and the force applied to the passage movement part (123) by the contents when the container is tilted or moved.

[0056] As shown in Fig. 5, the discharge device (300) includes, in addition to the discharge mechanism (100), a control unit (320), a sensor (330), a switch (340), a communication unit (350), and a memory (360).

[0057] The above sensor (300) includes a discharge detection sensor (331) and a tilt sensor (332). The discharge detection sensor (331) is illustrated in FIGS. 2 and 3. The discharge detection sensor (331) is composed of at least one infrared sensor. The infrared sensor is composed of an infrared emitting unit and a light-receiving unit, which are respectively arranged opposite each other. According to FIGS. 2 and 3, the light-emitting unit is composed of two LEDs, particularly infrared LEDs, arranged in a row along the passage (172), and the light-receiving unit is a photodiode capable of detecting infrared rays, which is arranged in a row along the path of the passage at a position opposite to the two LEDs to detect discharge of the contents. However, this is merely exemplary, and the discharge detection sensor is not limited to a light sensor, and any other sensor that can detect discharge of contents through a discharge device may also be used.

[0058] The above inclination sensor (332) is a motion sensor capable of detecting the inclination of the discharge device (300) and is mounted on a PCB (370) provided in the discharge device. However, this is merely exemplary and may be a sensor capable of detecting the inclination of the discharge device and the container connected thereto in other locations and methods.

[0059] The configuration of the above switch (340) is described with reference to FIG. 4.

[0060] The switch (340) includes a container detection switch (341) that detects whether the discharge device (300) and the container (200) are combined / separated, and a cover detection switch (342) that detects whether the discharge device (300) and the cover (400) are combined / separated. The container detection switch (341) is located at the bottom of the discharge device (300), and when the container (200) is combined, the switch is pushed up by contact with the container, thereby performing an on operation, and when separated from the container, the switch is turned off. The cover detection switch (342) is located at the top of the discharge device (300), and when the cover (400) is combined, the switch is pushed down by contact with the cover, thereby performing an on operation, and when separated from the cover, the switch is turned off. The on / off of the container detection switch (341) and the cover detection switch (342) may be configured to be on when separated and off when combined, contrary to the above-described configuration. The container detection switch (341) and the cover detection switch (342) are preferably contact switches, but may alternatively be non-contact sensors.

[0061] The above-mentioned discharge device (300) is connected to a user device (e.g., a smartphone app) or a remote server via a communication unit (350) so as to be communicative. The communication unit (350) may include one or more communication modules such as a Bluetooth module, WiFi, 5G communication, or Zigbee communication.

[0062] Referring to FIG. 5, the discharge detection sensor (331) detects the discharge of contents, and the discharge time and the discharge amount are matched and stored in the sensing data section of the memory (360). That is, the sensing data section of the memory (360) stores discharge sensing data including the discharge time of the contents detected by the discharge detection sensor (331) and the corresponding discharge amount (generally 1 or a fixed amount). The discharge sensing data is assigned a number (discharge count index) in the order in which it is generated and is tagged to each discharge sensing data, and the last assigned number, i.e., the largest index, is the device-stored sensing count value, and may be stored separately. The discharge sensing data is transmitted to and stored in a user device and / or a management server, and medication information is calculated based on the same. The sensing data section stores not only the discharge sensing data but also all sensing data detected by other sensors, and may thereafter be transmitted to the user device and / or the management server and stored separately.

[0063] Referring to FIGS. 5 to 7, the configuration and connection relationship of the discharge device (300) and the user device (600) according to one embodiment of the present invention will be described.

[0064] The above user device (600) is an information processing device capable of communicating with an external device, including a processor, memory, and communication module, and may be, for example, a mobile device such as a smartphone or tablet, but is not limited thereto.

[0065] The user device (600) includes a communication module (650) for two-way communication with the dispensing device (300) and an external device, a data management module (670) for generating and processing medication information and a medication schedule, a UI module (680) for providing medication information to the user and receiving various data, a storage unit (660) for storing data and programs, and a control module (620) for controlling the communication module, data management module, UI module, and storage unit. The above configuration of the user device may be implemented by a combination of software programs and / or hardware.

[0066] The above communication module (650) may include a BLE (Bluetooth Low Energy) communication module for communication with the discharge device and a remote communication module such as 5G or LTE for communication with external devices including a server.

[0067] The above storage unit (660) includes a program storage unit for storing programs, a sensing data storage unit, and a medication storage unit. The medication storage unit stores medication information and a medication schedule, and the sensing data storage unit stores discharge sensing data received from the discharge device.

[0068] The above data management module (670) stores the discharge sensing data received from the discharge device in the sensing data storage unit of the storage unit (660), and a sequence number (app discharge count INDEX) is assigned to the discharge sensing data according to the generation time (discharge time). The last assigned number, i.e., the largest index among the received discharge sensing data, is the app storage sensing discharge count value, and may be stored separately.

[0069] Separately, medication information, including the quantity of dispensed contents, is stored in the medication storage unit. This medication information is generated based on dispensed sensing data. This medication information can be modified through user input, etc. More precisely, this medication information is generated based on medication counting data generated based on dispensed sensing data.

[0070] Medication counting data is generated based on dispensed sensing data, but is subject to error correction by user input, a data management module, or a management server. If there are no errors, including sensing or transmission errors, the medication counting data can be identical to the dispensed sensing data. Medication counting data is calculated separately through user input or automatic correction and stored in a database separate from the dispensed sensing data. The user's medication information is updated and managed based on the medication counting data and medication schedule.

[0071] If there is an error, the medication counting index of the medication counting data is corrected and stored as a single bundle together with the corresponding medication time and medication quantity. The largest medication counting index indicates the final number of medications with the error corrected, and only this and the medication time may be stored (if the medication quantity is 1, it is the same as the medication counting index). The medication counting data and index may be corrected by the processes of FIGS. 9 to 11. The medication counting data is data with an error corrected from the discharge sensing data received by the user device, and may include, for example, the medication time, the discharge amount at the corresponding time, and an index.

[0072] The medication information managed by the data management module (670) of the user device (600) includes the quantity of the remaining contents in the container and the medication history. The medication schedule is generated based on the medication setting information. The medication setting information includes the number of times to take the medication per day, the medication setting time, and the dosage, and may be input by the user through the UI module, but may also be transmitted from a third-party external device, such as a medical staff device or a server, via wired or wireless communication. The medication setting information may further include the total quantity of the contents in the container.

[0073] The above medication schedule ('Medication Schedule' in Fig. 8) includes medication set times and dosages for each medication set time.

[0074] The above medication information is determined based on medication setting information and the discharge sensing data received from the dispensing device, and may include the medication status for the day (including the medication time for the day and the quantity of the contents taken at the time) and the total amount of stimulant medication. The data management module may calculate the medication status and the total amount of stimulant medication based on medication counting data. The total amount of stimulant medication dispensed from the container is not reset even when the container is changed, and is accumulated as long as the dispensing device ID is the same. The above medication information may further include the medication history included in the dispensing device (300) and may further include the quantity of the remaining contents in the container.

[0075] The data management module (670) updates the medication information based on the discharge sensing data of the contents within the container detected by the sensor (330). That is, the discharge of the contents detected by the sensor (330) is transmitted to the user device by the communication unit (350), and the data management module (670) uses the received discharge sensing data (discharge amount and corresponding discharge time) to modify the quantity of the remaining contents within the container, the total amount of the contents discharged from the container, and the medication history.

[0076] The above UI module (680) includes a medication mode and a device mode and can optionally display them. FIG. 8 illustrates a UI (User Interface) screen of a user device according to one embodiment of the present invention.

[0077] The left screen of Figure 8 is a medication mode screen that displays medication information and a medication schedule. The medication mode may include the number of daily doses, time of dose, dosage, and daily medication history. In medication mode, Pills Taken from Bottle indicates the total number of pills dispensed from the current container, Pills Taken Today indicates the number of pills dispensed from the container today, Pills in Bottle indicates the number of pills currently in the container, and PM 1:44:11 Pill taken indicates the time of pill (content) dispense.

[0078] The right screen of Fig. 8 shows the device mode, which indicates the connectivity with the dispensing device and the status of the dispensing device. In the device mode, the connectivity with the dispensing device may indicate, for example, whether the Bluetooth pairing between the user device and the dispensing device is established, and the status of the dispensing device may include the battery charge status of the dispensing device and data synchronization with the user device. The device mode may further include a container history including the time of coupling and decoupling between the container (200) and the dispensing device (300), and a cover history including the time of detachment between the dispensing device (300) and the cover (400).

[0079] The above container history is generated based on the on / off signal of the container detection switch (341) provided in the discharge device (300), and the above cover history is generated based on the on / off signal of the cover detection switch (342) provided in the discharge device (300). The data management module (670) generates the container history and the cover history using the on / off signals of the container detection switch (341) and the cover detection switch (342) received from the discharge device and the corresponding time information, and displays them by the UI module.

[0080] In the right screen of Fig. 8, PM 2:06:09 Bottle detached indicates the time of separation of the dispenser and the container, and PM 2:07:03 Bottle attached indicates the time of attachment of the dispenser and the container, which are part of the container history. In addition, Bottle Rcored at the bottom right of Fig. 7 indicates the cover history, which indicates the time of opening and closing the container cover in chronological order.

[0081] Many users generate big data (signal data generated by sensors and switches, data input by users, etc.) by using their own dispensing devices (300) and user devices (600). Each user can be individually identified by their own dispensing device (300), i.e., dispensing device ID, regardless of changes in the container. This big data is systematically managed through a management server. That is, even when all the contents (pills) contained in an existing container are consumed and pills in a new container containing the same contents are taken, when the dispensing device attached to the existing container is attached to the new container, the ID of the dispensing device itself is maintained to match the same patient that was initially set, so that all information related to the patient's medication can be managed continuously and continuously.

[0082] The counting values ​​of whether a pill was taken today (Taken), the number of pills taken from the current medicine bottle (Pill Taken from Bottle), the number of pills remaining in the current medicine bottle (Pills in Bottle), and the number of pills taken today (Pills Taken Today) in the user app or user management application of FIG. 8 are displayed by reflecting the counting values ​​according to the amount of medication calculated based on the discharge sensing data and user input data of FIGS. 9 to 11.

[0083] The number of pills dispensed today in Figure 8 is calculated by accumulating the number of pills dispensed today using the previous pill bottle when the medicine bottle is replaced with a new medicine bottle.

[0084]

[0085] Referring to FIG. 7, a network configuration of a medication management system according to an embodiment of the present invention will be described. The dispensing device (300) may be connected to a network via a user device (600) or may be directly connected to the network without going through the user device (600). The management server (500) is communicatively connected to the user device (600) or the dispensing device (300), and receives medication information based on the dispensing of contents detected by the sensor (330) and medication setting information and performs statistical processing. The statistically processed big data may be transmitted to a third-party device (700) and used for various medical services. The third-party device (700) may be, for example, a terminal device of a hospital medical staff, a pharmaceutical company, or an insurance company.

[0086] As illustrated in FIG. 7, the medication management system of the present invention includes a dispensing device including a dispensing mechanism for dispensing a fixed amount of content contained in the container, a sensor for detecting the fixed amount of dispensing of the content, a communication unit, a switch, and a control unit, which is detachably coupled to a container or integrally coupled to the container; the user device described above; and a management server capable of communicating with the user device or the dispensing device.

[0087] Although FIG. 7 illustrates that the discharge device is connected to the communication network via the user device, the discharge device can be directly connected to the communication network without going through the user device and communicate data with the server. In the following description, various data processed by the server can be received from the discharge device via the user device, but can also be directly transmitted from the discharge device to the management server (500).

[0088] Hereinafter, a content management method according to one embodiment of the present invention will be described. The content management method of the present invention is executed by a user device (600). The content management method includes a pairing step in which the user device (600) and the dispensing device (300) are connected to each other in a communication manner, a step of registering medication setting information input to the user device, a step of generating a medication schedule and medication information based on the medication setting information, and a step of receiving the dispensing information of the content detected by the sensor (330) to update the medication information. The medication setting information includes the quantity of the content in the container, the number of times to be taken per day, the medication setting time, and the dosage, and the medication schedule includes the medication setting time and the dosage for each medication setting time. The medication information includes the medication status for the day, the quantity of the remaining content in the container, and the total amount of the stimulating and stimulating medication, and may be generated or updated based on medication counting data. The medication status for the day includes the medication time for the day and the medication amount at the corresponding time, and may be generated or updated based on medication counting data. The discharge information of the contents detected by the above sensor (330) includes the discharge time and discharge amount.

[0089] Below, a method is described that allows a user to maintain accurate and stable medication information management even when exceptional events occur while taking medication using a container equipped with a dispensing device. A typical exceptional event is an event where the contents of a container are completely exhausted and replaced with a new container. Other possible events include an over-dispensing event due to a malfunction of the metered dose dispenser, an event where the contents are stuck in the metered dose dispenser and not dispensed, an over-dispensing event due to user error, and an event where the over-dispensed contents are reintroduced into the container. A method for continuously managing medication information even in these exceptional situations is described with reference to FIGS. 9 and 10.

[0090] According to FIG. 9, when the user device (600) receives a container combination detection signal from the container detection switch (341) provided in the dispensing device (300), the container change mode of the user device (600) starts. The container combination detection signal is a signal indicating combination after the dispensing device is separated from the container, and means, for example, an on signal received after the off signal of the container detection switch (341). Each signal is transmitted to the user device and / or server along with the time of generation by the communication unit of the dispensing device. Two signals including the time of generation may be received together, but generally, the on signal may be received with a time difference after the off, and the user device and / or server recognize this (off then on) as the container combination detection signal. Alternatively, depending on the structure of the container detection switch (341), the off signal may be generated upon combination and the on signal may be generated upon separation, as described above.

[0091] When a container combination detection signal is received, the data management module (670) provides a container combination detection display (800) as a UI screen through the UI module (680). The UI screen simultaneously provides a display (810) requesting confirmation of whether the container is new, a display (820) requesting confirmation of whether the dispenser has been attached or detached from the same container to resolve overdispensing due to a malfunction or user error, a display (830) requesting confirmation of whether the dispenser has been attached or detached from the same container to resolve a pill jam, and a display (840) requesting confirmation of whether the dispenser has been attached or detached from the same container due to a simple user error.

[0092] When confirmation of a new container (810) is entered, an additional screen is provided to receive input (811) of the quantity of contents in the new container from the user, and the data management module (670) updates the container history. The container history includes the time of separation of the discharge device from the old container and the time of attachment to the new container. When the quantity of contents in the new container is entered (811), an update is executed to correct the quantity of contents remaining in the container to the quantity of contents in the entered new container.

[0093] When it is confirmed that the same container has been detached to resolve the problem due to a malfunction of the dispensing device or user error resulting in excessive dispensing (820), the number of re-injected pills is input (821), and the data management module (670) modifies the medication counting data based on the input quantity of re-injected contents, and accordingly modifies and updates the medication information and the number of contents (pills) in the container.

[0094] If it is confirmed that the contents (pills) are stuck in the dispensing device and are attached or detached from the same container to clear the jam (830), the container change mode is terminated as there is no change in the number of pills in the container.

[0095] If it is confirmed that the user has simply mistakenly attached or detached the dispensing device to the same container (840), the container change mode is terminated as there is no change in the number of tablets in the container.

[0096] The above confirmation is achieved by the user pressing the confirmation button provided in the interface of Fig. 10 or by entering a specific numerical value and confirming it on the user device. In other words, the above confirmation means confirmation of the input.

[0097] In this way, according to the present invention, the medication history of the same user (patient) is continuously managed by the ID of the same dispensing device without a separate login procedure or container registration through the user device before and after the container change, which makes it possible to simply manage unified medication regardless of the container change.

[0098] Hereinafter, an error correction method according to an embodiment of the present invention will be described with reference to FIG. 11. Even in cases where an error occurs, such as when a quantity exceeding the specified amount is dispensed, when dispense is not detected, or when dispense is detected to exceed the dispensed amount, a dispense signal can be automatically detected by the dispense detection sensor (331), and in this case, the dispense sensing data is stored in the dispenser as is, and transmitted to and stored by the user device and / or the management server. However, since the medication information based on this is not accurate, in cases where such errors exist, correction of the number of doses due to erroneous dispense, etc. is required. The error correction method of FIG. 11 is not the opposite of FIGS. 9 and 10, but rather complements FIGS. 9 and 10 in other aspects, and description of the same contents as FIGS. 9 and 10 will be omitted.

[0099] An application program running on a user device may provide a separate "more" menu for inputting corrections to sensing data. Pressing this "more" menu button may initiate the flowchart of FIG. 11. The error correction method of FIG. 11 is implemented by a combination of hardware and / or software programs on the user device.

[0100] The user input UI at the top of Figure 11 shows that when the more menu button for user input is pressed, a UI for user input is provided.

[0101] The error correction method includes a step of determining whether or not the discharge device is connected after separation from the container; a step of providing a user input UI based on the determination; a step of correcting medication counting data based on the input content error quantity; and a step of calculating medication information based on the medication counting data and displaying it on the UI.

[0102] The above error correction method may further include, instead of the step of correcting the medication counting data and the step of displaying it on a UI, the step of providing the entered content error quantity to a management server or a data storage of a user device via an API; the step of requesting and receiving the corrected medication counting data and medication information from the management server; and the step of displaying the medication information on a UI. In this case, the medication counting data and medication information are corrected on the management server, and the corrected information is downloaded and displayed on the user device.

[0103] Specifically, the step of determining whether or not the dispensing device is reattached after separation from the container is determined based on the container combination detection signal. If it is reattached after separation from the container of the dispensing device, the user input (i.e., the number of contents re-inserted due to a jam or accidental dispensing by a child, etc., i.e., how many pills should be re-inserted? The user inputs a modified number according to the situation) is modified by subtracting the index of the medication counting data. That is, if 2 pills are re-inserted, 2 is input, and the medication counting value is displayed by subtracting 2. Accordingly, the medication information is also modified.

[0104] If the user input is not provided after separation from the container of the dispensing device, and in this case, if it is not a dispensing but is incorrectly counted as a dispensing, the medication counting value should be deducted, and if there is a dispensing but is not sensed, the medication counting value should be added. For this purpose, the provided user input UI can have a non-dispensing sensing input section and a dispensing non-sensing input section. If the user inputs the number of dispensings that are incorrectly recognized or not recognized as an error in the non-dispensing sensing input section or the dispensing non-sensing input section, the medication counting value is deducted or generated by the input quantity accordingly.

[0105] Hereinafter, a method for processing medication information, etc. in a management server will be described with reference to the UI screen of the management server in FIGS. 12 to 14.

[0106] The management server (500) is an information processing device, which may be a computer including a processor, a communication unit, and a memory, and may be implemented as a single device or may be a system in which multiple devices are connected.

[0107] To use the management server, you can go through the standard membership registration and login procedures via the management server's UI or via the UI of a terminal device connected to the management server. The following description does not specify the management server's UI or the terminal device's (information processing device) UI, but all screen displays are based on one of the two UIs, and the same content may also be provided via a third-party device (such as a medical professional, insurance company, or pharmaceutical company's information processing device UI).

[0108] When logged in, the management server displays the main page screen as shown in Fig. 12. On the left side of the main page, a Device ID list (indicated by ②) is displayed, i.e., a list of dispensing device IDs, from which a device ID can be selected. Filtering (①) on the upper left allows filtering of the Device list by All, Paired, Non-paired, Pill Size 8 mm, and 6 mm, etc.

[0109] The main menu indicated by ⑤ in Fig. 12 includes Medication Record, Medication Status, Device Management, and Sensing Data, and displays the selected items on the screen below the main menu. ③ indicates a period search, and you can search for today, a week, a month, 3 months, 1 year, or a specific period. In Fig. 12, the current medication record is selected as weekly, and the medication record for one week (Medication Record, ⑥) is displayed. The medication record includes the medication time and normal medication, abnormal medication, and non-medication, and a graph and table of these are displayed on the left. When the cursor is placed on a specific point, a pop-up is displayed so that the detailed medication date and time can be confirmed, as in ④.

[0110] Figure 13 shows the screen when Medication Status is selected from the main menu, with a list of Device IDs displayed on the left (① in Figure 13). Medication Status displays the daily medication time and whether the medication has been taken, container separation, combination, cap opening, and the time for each status.

[0111] Meanwhile, information regarding replacement of a new container by separation and reassembly of the dispenser and container (container replacement date and time) can be transmitted to the management server directly from the dispenser or via the user device, and the management server provides this information for each dispenser. If information regarding replacement of a new container by separation / reassembly of the container from the user device is confirmed by the user, more accurate container replacement information can be transmitted to the management server.

[0112] Figure 14 illustrates a sensing data display screen of a management server. The management server processes data received from a discharge device and / or a user device and displays it as discharge sensing data, as shown in Figure 14.

[0113] According to Figure 14, ① represents the Dispenser Count, which indicates the number of times the contents (pills) are dispensed from the container. ② represents the Event Time, which indicates the details of events such as contents (pills) dispensing, container tilting, separation of the device and the pill bottle, mounting, opening and closing of the cap, etc., as well as the date and time when the event occurred. At this time, the Event App Time, which is the time when the corresponding dispensing sensing data was transmitted to the app, is also stored and displayed.

[0114] ③ is the number of tilts (Tilt Count, Information idx) that the tilt sensor of the discharge device has detected the tilt of the discharge device mounted on the container, and ④ is the tilt status (Tilt Status, Status Info) that indicates the tilt sensing value of the container (and discharge device) detected by the tilt sensor. 7 indicates Tilt, 8 indicates Not Tilt, and the standard may be a predetermined tilt sensor value.

[0115] ⑤ is the container status, indicated as Bottle Status (Body status), and is the value sensed by the container detection switch (341) for the separation / combination of the discharge device and the container, with 0 indicating attachment (Attach) and 1 indicating detachment (Detach). ⑥ is the attachment / detach time, indicated as Attach / detach Time, and indicates the time sensed for the separation / attachment of the discharge device and the container. ⑦ is the number of times the container cover is opened / closed, indicated as Cap Count, and is determined by the sensing value of the cover detection switch (342). ⑧ is the Cap Status (Cover status), which is the value sensed for the opening and closing of the cover, with 0: open and 1: close.

[0116] In this way, by using the management server, the administrator can continuously collect and manage the medication history and container information of the same user (patient) remotely by the ID of the dispensing device, and the collected sensing data can be transmitted as is or after being processed and statistically processed to medical staff, pharmaceutical companies, or insurance companies.

[0117] According to one embodiment of the present invention, the discharge device and the user device are capable of BLE (Bluetooth Low Energy) communication. BLE (Bluetooth Low Energy) is mainly used for communication between low-power devices such as smartphones, wearable devices, sensors, and healthcare devices. BLE basically operates in two modes: Advertising mode, which is a one-way communication mode, and Connection mode, which is a two-way communication mode. Advertising mode is a low-power mode and the amount of communication data is limited, while Connection mode allows for more data communication, but consumes much more power than Advertising mode.

[0118] According to one embodiment of the present invention, the device (discharge device) periodically transmits a predetermined amount (e.g., three) of discharge sensing data in one direction in an advertising mode, so that the user device can receive and process the data, and power consumption of the discharge device is minimized, thereby enabling efficient communication.

[0119] Meanwhile, when the dispensing device continuously transmits three pieces of dispensing sensing data in Advertising mode, the highest dispensing count index, the app-stored sensing dispensing count value, in the user device that receives and stores the data must match the device-stored sensing dispensing count value. However, the user device may not receive some of the dispensing sensing data generated by the dispensing device due to events such as a communication connection being cut off in the middle between the dispensing device and the user device or the medication management application being turned off. In this case, the app-stored sensing dispensing count value may not match the device-stored sensing dispensing count value. If the user device and the management server do not receive some of the dispensing sensing data generated by the dispensing device, there may be an error in the medication information generated and updated based on this, and thus it is necessary to correct this in real time. In this case, it is also necessary to minimize the battery consumption of the dispensing device.

[0120] Figure 15 is a flowchart illustrating a method for additionally receiving the missing discharge sensing count index from the device via connection communication and storing it in a server or app when there is a transmission omission of discharge sensing data from the device. Blocks indicated by dotted lines in Figure 15 indicate steps that may be optionally included.

[0121] According to FIG. 15, it is desirable, but not limited to, that the BLE communication connection between the discharge device and the user device be restarted after being interrupted for a predetermined period of time.

[0122] The above-described method for modifying a discharge count value includes the steps of: obtaining an app-stored sensing discharge count value and a device-stored sensing discharge count value; comparing the app-stored sensing discharge count value and the device-stored sensing discharge count value to calculate a difference therebetween; and, if the difference is less than a predetermined value, receiving and storing a predetermined amount (e.g., 3) of the latest discharge sensing data in an advertising mode, and receiving and storing missing sensing data in a connection mode if the difference exceeds the predetermined value. The method may be executed by a data management module (670) of the user device, but may also be executed on a management server via the user device. In this case, BLE communication with the discharge device may be performed via the user device, and data processing received via the app of the user device may be performed on the management server.

[0123] The following description details the above process in a manner executed by the user device. The data management module (670) of the user device obtains the app storage sensing discharge count value and the device storage sensing discharge count value. For example, when the BLE communication channel is reconnected, the data management module (670) receives and obtains the three latest discharge sensing data and the device storage sensing discharge count value from the discharge device, and reads the pre-stored app storage sensing discharge count value. The three latest discharge sensing data are each assigned a discharge count INDEX and transmitted together.

[0124] If the above app storage sensing discharge count value is compared with the device storage sensing discharge count value and the difference (device storage sensing discharge count value - app storage sensing discharge count value) is less than or equal to a predetermined amount (here, 3), a predetermined amount (e.g., 3) of the latest discharge sensing data is received and stored from the discharge device in Advertising mode, and if the difference exceeds the predetermined amount, the entire discharge sensing data corresponding to the number of missing data is requested from the discharge device and received and stored in connected mode. Here, the predetermined amount is the limit of the amount of data that can be transmitted at one time in Advertising mode. That is, even if the difference exceeds the predetermined amount, the latest discharge sensing data (e.g., 3) may be received first in Advertising mode, and then the remaining missing discharge sensing data may be requested, received, and stored in connected mode.

[0125] The above method for modifying a discharge count value may further include a step of obtaining a discharge count INDEX list that is not present in the user device (app DB) from the sensing data storage unit to determine whether there is missing data; and a step of receiving discharge sensing data corresponding to the missing discharge count index from the discharge device through connection mode communication and storing the data in the user device if there is missing data. In addition, the method may further include a step of transmitting the discharge sensing data corresponding to the missing discharge count index to the management server and storing the data. Since each discharge sensing date stored in the sensing data storage unit is matched with a discharge count INDEX, the list is read to find a discharge count INDEX list that is missing in the middle, for example, if the latest index (device-stored sensing discharge count value) is 15 but 9 is missing, the missing discharge count index is 9. The data management module (670) can request and receive the discharge sensing data corresponding to index 9 from the discharge device in a connection mode, supplement the missing data, update the discharge sensing data, and update the medication information.

[0126] In the Advertising mode, the device (dispenser) periodically transmits the three most recent dispensing sensing data, thereby reducing power consumption. By communicating in the connected mode only when necessary, the power consumption of the dispensing device is minimized while obtaining accurate sensing information, thereby improving the accuracy of medication information and energy efficiency.

[0127] Hereinafter, a medication alarm method according to one embodiment of the present invention will be described with reference to FIGS. 16 and 17.

[0128] A medication alarm method according to one embodiment of the present invention includes the steps of: determining whether the current time is a set alarm time (8:00 a.m. in FIG. 17) according to alarm settings; requesting discharge sensing data and user input data from an alarm operation start time (here, 30 minutes before the set time, i.e., 7:30 a.m.) to the set alarm time (8:00 a.m.) if the current time is the set alarm time; determining whether the set amount of medication of the contents exceeds a medication amount calculated based on the discharge sensing data and the user input data; and sounding an alarm if the determination result is positive and terminating the alarm process if the determination result is negative.

[0129] According to Figures 16 and 17, the above-described process is a first alarm process, and a second alarm may be provided after the first alarm is sounded. The second alarm process is not mandatory, and the first alarm may be terminated alone.

[0130] In the case of a second alarm, it can be executed after the first alarm. The second alarm method includes the steps of: determining whether a predetermined time (e.g., 10 minutes) has elapsed from the set alarm time and the set second alarm time has arrived; if the set second alarm time (here, 8:10 AM) is currently present, the step of requesting the discharge sensing data and user input data from the alarm operation start time (here, 7:30 AM, which is 30 minutes before the set alarm time) to the set second alarm time (here, 8:10 AM); the step of determining whether the set dosage of the contents exceeds the dosage calculated based on the discharge sensing data and the user input data; and the step of sounding an alarm if the determination result is positive and terminating the alarm process if the determination result is negative.

[0131] Figure 17 displays two daily medication reminders, one for the morning and one for the afternoon, in chronological order. The morning reminder uses the alarm method described above, and the second reminder in the afternoon is triggered in the same manner.

[0132]

[0133] The present invention relates to a method and device for managing information on contents contained in a container, and can be applied to patient medication management and data collection, and thus can be used in the medical, pharmaceutical, and insurance industries.

Claims

1. A method for managing contents, which is executed by a user device including a processor, a memory, and a communication module and is communicatively connected to a dispensing device having a sensor for detecting dispensing of contents contained in a container, Steps to obtain a medication schedule; A step of receiving discharge sensing data of contents detected by the above sensor; and A method for managing contents, characterized by comprising a step of generating or updating medication information using the above discharge sensing data.

2. In paragraph 1, A step of registering medication setting information input into a user device; further comprising: The medication schedule is created based on the above medication setting information, The above medication setting information includes the quantity of contents in the container, the number of times to take the medication per day, the medication setting time, and the dosage. The above medication schedule includes a medication setting time and a dosage for each medication setting time, and is generated by the user device or received from an external device. The above medication information includes the medication status on the day, the amount of remaining contents in the container, and the total amount of medication. The above same-day medication status includes the time of medication taken on the same day and the amount of medication taken at that time. A contents management method characterized in that the contents discharge information detected by the above sensor is discharge sensing information including discharge time and discharge amount.

3. In paragraph 1 or 2, When a container combination detection signal is received from the above discharge device, The above container combination detection display is provided as a UI module, and a display requesting confirmation of whether or not it is a new container is provided. A contents management method characterized in that when confirmation of a new container is entered, a request for input of the quantity of contents in the new container is provided as a UI module.

4. In paragraph 3, When confirmation of a new container is entered through the UI module, a container change history is created, The above container change history includes the time of separation of the discharge device from the old container and the time of joining with the new container, A method for managing contents, characterized in that when the quantity of contents in a new container is entered, the quantity of contents remaining in the container is updated with the quantity of contents in the new container entered.

5. In paragraph 3, When providing the above container combination detection display as a UI module, a display requesting confirmation of whether it is a new container is provided along with a display confirming whether there is an operation error or a user error. The above operating error is, Includes an over-discharge error in which the contents are over-discharged, and a jamming error in which the contents are caught in the discharge mechanism. A method for managing contents, characterized in that an input section is provided for inputting the quantity of contents to be reinjected for the above over-dispensing error, and the medication information is modified based on the input quantity of contents to be reinjected.

6. In any one of paragraphs 1 to 5, The above contents are contained in a container integral with the discharge device or a container detachably coupled to the discharge device and discharged by the discharge device, and the discharge device includes a sensor for detecting discharge of the contents. A method for managing contents, characterized in that the medication information is updated based on the discharge sensing data of the contents detected by the sensor.

7. In paragraph 3, The discharge of the above contents is quantitatively controlled by the rotation of the passage movement part according to the angle at which the container is tilted. The above sensors are composed of a light emitting part and a light receiving part that are respectively arranged opposite to each other, and are arranged in a row along the path of the passage to detect the quantitative discharge of contents. A contents management method, characterized in that the container combination detection signal includes an on / off signal and on / off time of a container combination detection switch included in the discharge device.

8. In any one of paragraphs 1 to 7, The discharge device and the user device can communicate via BLE (Bluetooth Low Energy) communication, The above contents management method further includes a process for modifying the discharge count value, The above discharge count value modification process is: A step of obtaining an app storage sensing discharge count value and a device storage sensing discharge count value; A step of comparing the app storage sensing discharge count value and the device storage sensing discharge count value and calculating the difference; and If the difference is less than a predetermined value, a step of receiving and storing a predetermined amount of the latest discharge sensing data in an advertising mode, and if the difference exceeds the predetermined value, a step of receiving and storing the missing sensing data in a connection mode; The above device storage sensing discharge count value is the largest value among the discharge count indexes sequentially assigned to the discharge sensing data, A content management method characterized in that the above app storage sensing discharge count value is the largest value among discharge count indexes sequentially assigned to discharge sensing data received from a discharge device and stored in a user device or management server.

9. In paragraph 8, The above discharge count value modification process is: A step of obtaining a list of ejection count indexes that are not present in the user device and determining whether there is missing data; and A method for managing contents, characterized in that it further comprises a step of receiving discharge sensing data corresponding to a missing discharge count index from a discharge device through connection mode communication and storing the data in a user device if there is missing data.

10. In paragraph 9, A method for managing contents, wherein the medication counting data is generated based on the discharge sensing data, but is data with errors corrected by a user input or a data management module or a management server, and is stored separately from the discharge sensing data.

11. In paragraph 10, A method for managing contents, characterized in that medication information is generated based on medication counting data.

12. A storage medium having stored thereon a computer-readable program, wherein the program includes commands for executing the method of any one of claims 1 to 11.

13. A user device including a processor, a memory, and a communication module, and connected by communication to a dispensing device having a sensor for detecting dispensing of contents contained in a container, A communication module for two-way communication with the discharge device, A data management module that creates and processes medication information and medication schedules and displays them through a UI module. UI module, Storage and It includes a control module that controls a communication module, a data management module, a UI module, and a storage unit. The above medication information includes the quantity of remaining contents in the container, the total amount of contents dispensed from the container, and medication history. The medication schedule and medication information are created based on the medication setting information. The above medication setting information includes the quantity of contents in the container, the number of times to take the medication per day, the medication setting time, and the dosage. The above medication schedule includes the medication set time and the dosage for each medication set time, The above medication information includes the medication status on the day, the amount of remaining contents in the container, and the total amount of medication. A user device characterized in that the medication information is updated based on the discharge of the contents in the container detected by the sensor.

14. In paragraph 13, The above medication information further includes the medication history included in the above discharge device, The above UI module includes a medication mode that displays medication information and a medication schedule, and a device mode that displays connectivity with the dispensing device and the status of the dispensing device. A user device characterized in that the above device mode further includes a container history indicating the time of coupling and separation between the container and the discharge device, and a cover history indicating the time of detachment of the discharge device and the cover.

15. A dispensing device including a dispensing mechanism for quantitatively dispensing contents contained in the container, a sensor for detecting quantitative dispensing of contents, a communication unit, a switch, and a control unit, which is detachably coupled with the container or is integrally coupled with the container; User device of Article 13; and A medication management system including a management server capable of communicating with the user device or the dispensing device; A medication management system characterized in that the management server receives medication information based on the discharge of contents detected by the sensor and medication setting information, performs statistical processing, and transmits the information to a third-party device.

Images