Counter Device

Abstract

To provide a drip counter device or a method, for reducing a load on a user manually performing information input or the like.SOLUTION: A drip counter device or a method comprises the steps of: obtaining information on the drip counter device; controlling a transceiver to obtain information on an infusion liquid dosing plan of a person to whom infusion liquid is to be administered; controlling the transceiver to transmit the obtained information to a system monitoring device; receiving device parameters to administer infusion liquid according to the dosing plan; monitoring administering of the infusion liquid; comparing the administering with the dosing plan; controlling the transceiver to transmit information on monitoring or comparison results to the system monitoring device; and controlling a user interface to display comparison results.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] SUMMARY OF THE INVENTION Exemplary, non-limiting embodiments of the present invention relate generally to drip counters. [Background technology]

[0002] Counter devices, or drip counters, are used in medicine in connection with intravenous infusion therapy to ensure that a patient receives the desired amount of infusion fluid within the desired time period.

[0003] The infusion rate of an infusion fluid refers to the rate at which the infusion fluid is administered to a patient. Traditionally, infusion rates are measured in drips per minute, but infusion rates can also be expressed as milliliters per hour if the volume of each drip is known and a specific number of drips has been determined for that minute. Summary of the Invention [Problem to be solved by the invention]

[0004] Traditionally, the drip rate of a counter device or drip counter is manually set by the counter operator, such as a nurse, using, for example, a mechanical clamp. Drip counters traditionally only monitor, i.e., they count how many drops are administered to a patient per minute. The operator can set limits / alarms so that an alarm can be given when the drip rate is below / above the limit. Traditionally, separate clamps are present on the pipe, and the clamps are used to control the flow within the pipe. The clamps and monitors are typically not related to each other in any way. [Means for solving the problem]

[0005] According to an aspect of the present invention, an apparatus according to claims 1 and 8 is provided.

[0006] According to an aspect of the present invention, methods according to claims 12 and 16 are provided.

[0007] One or more examples of implementations are shown in more detail in the accompanying drawings and the following description. Other features will be apparent from the description and drawings, and from the claims. The embodiments and / or examples and features described herein that do not fall within the scope of the independent claims, if any, are to be construed as examples useful for understanding various embodiments of the invention.

[0008] In the following, the invention will be explained in more detail by means of preferred embodiments with reference to the accompanying drawings. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example use of the drip counter device. [Figure 2] FIG. 1 illustrates an example of a drip counter device. [Figure 3] 1 illustrates an example of an environment in which a drip counter device embodying some embodiments of the present invention can be used. [Figure 4] 1 is a flow chart illustrating an embodiment. [Figure 5] FIG. 10 illustrates an example of the operation of the drip counter device. [Figure 6A] 1 is a flow chart illustrating some embodiments of the present invention. [Figure 6B] 1 is a flow chart illustrating some embodiments of the present invention. [Figure 7] 1 illustrates an example of an apparatus using some embodiments of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Figure 1 illustrates an example use of a drip counter device. Figure 1 shows a drip counter 100 having an attached container 102 of infusate. The drip counter is configured to administer 104 the infusate to a patient 106 so that the patient obtains a desired amount of infusate within a desired time period. The drip counter typically controls the drip rate of the infusate. The drip rate refers to the rate at which the infusate is administered to the patient.

[0011] A drip counter typically includes a drip detector configured to measure the drip rate. The drip detector can be implemented using an optical detector, such as an LED (light-emitting diode) light source and its associated phototransistor. Modern drip counter devices are capable of indicating on a display the number of drips in a given time period, or the drip rate, such as drops / minute or drops / hour, the counted drip volume, or the counted drops. In addition, drip counters can feature adjustable alarm thresholds, by which the device provides an alarm to nursing staff when the drip rate of the infusion fluid is not at a desired level or when a preset maximum amount of infusion fluid has been administered, i.e., dripped.

[0012] Current drip counter devices are very simple drop counters. Typical devices are not connected to a hospital database or linked to the web. Advanced drop counters can store usage information in an external memory as historical information. Some devices are now known to be connected to an external database or cloud to transmit measurement or monitoring data. Some infusion pumps also exist that are connected to a database to update device information.

[0013] Users of current devices face many practical difficulties and problems setting up the device to begin monitoring. First, infusate medical information must be available within the device. Device manufacturers can provide data and load it into the device. However, the device is not connected online, and users may need to manually provide data when new infusate types and formats are used. Second, the patient's medication list must be entered into the device. While the data is likely available in the hospital's patient database, because the device is not connected, the list must be entered manually from paper or a computer. A third problem relates to the follow-up of the patient's planned care plan (infusate) and the monitored administered infusion. Due to the lack of connection to the database, the comparison can be difficult due to the fact that the plan may change during care. For example, users may modify and reset the infusion drip rate and time to reach daily targets. Fourth, problems relate to comparing the achieved infusate administration with the planned care plan specified by the physician.

[0014] An embodiment is illustrated in Figure 2. This figure illustrates a simple example of a drip counter device 100 to which an embodiment of the present invention may be applied.

[0015] It should be understood that the devices are depicted herein as examples illustrating some embodiments. Those skilled in the art will appreciate that the devices may include other functionality and / or structure and may not require all of the functionality and structure described. While the devices are depicted as a single entity, the different modules and memories may be implemented in one or more physical or logical entities.

[0016] The example device 100 includes a control circuit 200 configured to control at least a portion of the operation of the apparatus. The control circuit may be implemented, for example, using at least one processor.

[0017] The device may include a memory 202 for storing data. Additionally, the memory may store software 204 executable by the control circuitry or processor 200. The memory may be integrated into the control circuitry.

[0018] In embodiments, the device may include a detector 206 configured to determine the presence of infusate to be administered. The detector may be, for example, a mechanical or optical switch connected to the control circuitry or processor 200.

[0019] In embodiments, the device may include a drip control unit 208 that controls the amount of fluid administered to the patient. The device further includes a drip detector 210 configured to measure the drip rate. The device may further include a tilt sensor 212 that can determine if the device is not in an upright position, which may be the case if the device is operating incorrectly.

[0020] The device may include a transceiver 216 that may be connected to an antenna 218 .

[0021] The various above-mentioned devices of device 100 may all be connected to and operate under the control of control circuitry or processor 200. For example, the speaker and display of the user interface may indicate an alarm under the control of the control circuitry or processor.

[0022] The transceiver 216 can be a wireless transceiver that utilizes known wireless technologies. An example of a suitable wireless technology is Bluetooth®. Other possible examples of technologies are Wireless Local Area Network (WLAN or WiFi), Worldwide Interoperability for Microwave Access (WiMAX), ZigBee®, and various mobile communication technologies known in the art.

[0023] In an embodiment, the transceiver is a wired transceiver connected using a wired connection to a suitable network, such as the Internet.

[0024] The device may include a user interface 214, which may include, for example, a display, a keypad, and a speaker. The display may be touch-sensitive, in which case a keypad or keyboard is not necessarily required. In an embodiment, the user interface is implemented at least in part in a remote monitoring device connected to the device through a transceiver in a wired or wireless manner.

[0025] In an embodiment, the control circuitry or processor 200 may control the transceiver to connect to a patient database of the hospital where the infusion control device is located. Contact parameters (such as contact address, authentication password, etc.) may be pre-supplied into the control circuitry or processor by operations personnel.

[0026] An embodiment is illustrated in Figure 3. This figure illustrates an environment in which a drip counter device applying an embodiment of the present invention can be used.

[0027] In the example of Figure 3, there are drip counters 300A, 300B installed and used in Hospital 1 Department 1 302, drip counters 300C, 300D installed and used in Hospital 1 Department 2 304, and drip counters 300E, 300F installed and used in another Hospital 2 Department 1 306. In each department, there may be one or more operators 322 of the drip counters. The operators may be, for example, nurses.

[0028] The drip counter's transceiver allows the drip counter to communicate with a database 308. The database can contain various information such as infusion fluid data 310 (data on different fluids used in the hospital), the hospital's patient care plan 312 and medical medication data 314, and drip counter usage conditions data. The usage conditions can include data related to the drip counter's environment, such as the hospital department, room number, and bed number in which the drip counter will be used.

[0029] In the example of Figure 3, there is a monitor device 318 connected to the database 308 and configured to communicate with the drip counter devices 300A-300F. The monitor device can be a computer or corresponding data processing unit, such as a tablet or smartphone. There may also be another computer 320 connected to the database. The computer can be used by medical personnel, such as a doctor, to monitor the operation of the various devices.

[0030] Figure 4 is a flow chart illustrating some embodiments. Figure 4 illustrates the operation of the drip counter device 100.

[0031] In step 400 of FIG. 4 , the drip counter device is configured to obtain information regarding usage characteristics of the drip counter device. The usage characteristics may include accessories connected to the drip counter device. The accessories may be pipes and clamps attached to the device. The usage characteristics may include information regarding the site where the device is located, such as the hospital department, room number, bed number, etc. At the same time, date and time information may be obtained. Some of this information may be provided by the operator of the device using a user interface. As mentioned, the user interface may be located at least in part on a remote device connected to the drip counter device in a wired or wireless manner. Some information may be read by the control circuitry or processor from memory or using sensors. In embodiments, the drip counter device is also configured to receive information regarding the individual or operator operating the drip counter device. This information may be provided by the operator of the device using a user interface. In embodiments, the device may recognize the operator, for example, using sensors.

[0032] In step 402 of Figure 4, the drip counter device is configured to control the transceiver to obtain information regarding the infusion administration plan of the individual to whom the infusion is to be administered. The device's control circuitry or processor can utilize the transceiver to contact the hospital's database 308. The database can store the hospital's patient care plans, medication lists, and medication plans. The drip counter device operator can input the patient's identification so that the corresponding data can be retrieved from the database.

[0033] In an embodiment, the drip counter device may retrieve the patient's medication list and care plan from a database.

[0034] In step 404 of Figure 4, the drip counter device is configured to control the transceiver to transmit information regarding the received and derived information to the monitor device 318. The monitor device may be a computer or corresponding data processing unit, such as a tablet or smartphone. The information may include data regarding infusion data, the patient's care plan, and medication list. In addition, the information may include data related to device usage, such as, for example, hospital department, room number, bed number, etc.

[0035] In step 406 of Figure 4, the drip counter device is configured to receive device parameters for administering the infusion fluid according to the administration plan. An operator of the device can set the parameters. In embodiments, the drip counter device is configured to show the parameters on a display.

[0036] In embodiments, the drip counter device can be configured to display parameters for administering an infusion according to an administration plan or a change plan, allowing an operator of the device to set the infusion configuration according to the parameters. For example, if the administration plan indicates that a patient connected to the drip counter is to receive 500 ml of infusion in 5 hours, the drip counter device can calculate or receive from the monitor device that a delivery rate of 100 ml / hour or XX drops per minute will be applied. The device can display the delivery rate as a parameter on its display, allowing the operator to control the mechanical clamp rollers so that the delivery rate is accurate.

[0037] 4, the drip counter device is configured to monitor the administration of the infusion fluid. The control circuit or processor 200 can utilize the drip detector 210 to determine how the infusion fluid is administered.

[0038] 4, the drip counter device is configured to compare the administration to the administration plan. The control circuitry or processor 200 can calculate the amount of fluid administered based on the data retrieved from the drip detector and compare this result to the amount set forth in the administration plan.

[0039] In step 412, the drip counter device is configured to control the transceiver to transmit information to the monitor device 318. The information may include monitored data (such as the amount of infusate administered within a given time frame) or the results of the comparison, and potentially other data.

[0040] 4, the drip counter device is configured to control a user interface of the drip counter device to display the comparison results. The display of the user interface may indicate how the realized administration of the infusion fluid compares to the administration plan. As noted, the user interface may be located at least in part on a remote device connected to the drip counter device in a wired or wireless manner.

[0041] The proposed solution improves the quality of monitoring how dosing plans are adhered to.

[0042] In embodiments, prior to the above-described procedure, the drip counter device may be configured to determine the presence of infusate to be administered. The control circuit or processor 200 may control the detector 206 to determine the presence of infusate.

[0043] In embodiments, the drip counter device is configured to determine, based on monitoring the administration of infusate, that the administration plan will not be satisfied. The control circuitry or processor 200 can calculate that a given drip control value will not be able to deliver the required amount of infusate within the required time. Based on the determination, the drip counter device can be configured to generate an alarm that can be indicated using a user interface. The alarm may be visual, audible, or both. In embodiments, the alarm is displayed on a remote device connected to the drip counter device via a wired or wireless method.

[0044] In an embodiment, the drip counter device is configured to determine updated parameters for the drip controller 208 based on the monitoring. The updated parameters may be indicated utilizing a user interface coupled to the alarm.

[0045] An example of this is shown in Figure 5. The figure shows a patient's administration plan 500 over the time frame 14:00-16:00, with time on the x-axis and fluid volume on the y-axis. The total fluid volume target to be delivered in the given time frame is shown at 502.

[0046] Administration begins at 14:00, and monitored administration of infusate 504 follows the plan fairly well until 14:50, 506, when infusion administration is stopped for some reason at 15:05, 508. At 15:30, 510, the drip counter device monitoring administration indicates an alarm that the administration plan is likely to not be met. At 15:35, 512, a new administration set point is set for the drip controller (suggested by the drip counter device connected to the alarm and set by the device operator). With the new set point, the target volume is achieved in the desired time frame.

[0047] In embodiments, the drip counter device can generate a given type of alarm. If the device does not receive an acknowledgement of the alarm using the user interface within a given time limit, it can be configured to change the alarm type, for example, to a louder sound or a different visual appearance. This relates to the problem of alarms not initially being noticed. If an infusion is interrupted for too long, the cannula will likely become blocked and there is a need to perform a recannulation at the infusion site. Clinicians may have problems with recannulation for patients with poor veins. The infusion may continue normally shortly after it is stopped and not cause a problem, but if the infusion is stopped for too long, recannulation is necessary. To this end, changing the alarm type is useful to increase the noticeability of potential problems.

[0048] In embodiments, the drip counter device immediately warns when an infusion has stopped with a low priority alert (such as a yellow traffic light alert symbol). The device can indicate the time the infusion stopped. The device can provide a medium priority alarm (such as an audio alarm and a flashing yellow traffic light) if the time since the alarm is greater than T1, at which point the risk of the cannula becoming blocked is high. The device can provide a high priority alarm (such as a more frequent audio alarm) if the time since the alarm is greater than T2 and the risk of the cannula becoming blocked is very high.

[0049] T1 and T2 can be set by the clinician and could be, for example, in the range of 5 to 15 minutes for T1 and 15 to 30 minutes for T2.

[0050] In an embodiment, the drip counter device is configured to generate an alarm having a given type, the type of alarm being selected based on received information regarding the individual to whom the infusion fluid is to be administered.

[0051] As an example, a drip counter device may detect that an infusion has stopped, which will trigger an alarm. A stopped infusion may be due to technical or infusate handling issues (empty infusion bag, crushed pipe, non-functioning monitor). One other reason may be that the cannula set in the vein is blocked. The risk of cannula blockage may depend on the patient and the cannula setting. The drip counter device can take this into account when triggering the alarm. For example, elderly people may have small, stiff veins, which makes cannula blockage more likely than younger and healthier people. This also means that setting the cannula is (again) difficult, so it is important to try to avoid it if possible; system alarm prioritization can assist with this.

[0052] The drip counter device operator, such as a caregiver or clinician, can configure the monitored individual to be at "higher risk" for cannula blockage. In such cases, the system's configuration will prioritize alarms. The alarm may be a medium priority alarm at a time, and the time frame may be shorter than "normal," e.g., 20-50% shorter, as the alarm type increases.

[0053] Prioritization can also be automatic based on the individual's age, weight, infusion type, infusion fluid used, etc. This data can be available from database 308 or entered individually.

[0054] In an embodiment, the drip counter device may determine that an alarm is to be given, it may determine that a previous alarm was given within a given time frame, and select the type of alarm based on that determination.

[0055] In embodiments, the alarm type and / or frequency of changing alarm type may depend on information determined by comparing the administration to the administration plan. For example, when a drip counter device compares monitored data to the administration plan, it may alert with a low priority alert (e.g., a yellow light alert symbol) if there is an XX% deviation from the care plan. A medium priority alarm (e.g., an audio alarm and a flashing yellow light) may be given if there is a YY% deviation from the care plan. Here, XX and YY may be set by an operator or clinician and could be, for example, in the range of 15-25% for XX and 25-50% for YY.

[0056] In embodiments, the monitoring system or device may also know that the infusion cannot be safely carried out according to the dosing plan. For example, if 2 liters must be infused in 2 hours due to a slow infusion rate at the beginning of the infusion, the monitoring system or device may provide a warning that it may not be safe to infuse such a large amount of fluid in such a short time.

[0057] Figure 6A is a flow diagram illustrating some embodiments of the present invention. Figure 6A illustrates the operation of the monitor device 318. Generally, the monitor device (or computer 320) is configured to monitor one or more drip counter devices. The monitor device can be a processing device or computer that includes a transceiver and a user interface.

[0058] In step 600 of Figure 6A, the monitoring device is configured to obtain information regarding one or more individuals who control the transceiver of the device to activate one or more drip counter devices, individuals to whom infusion fluid will be administered utilizing the one or more drip counter devices, and characteristics of the one or more drip counter devices and the environment in which they are used. The transceiver may utilize wired or wireless communication methods. The information may be obtained from database 308 or from the drip counter devices.

[0059] 6A, in step 602, the monitoring device is configured to control the device's transceiver to obtain information regarding care plans and infusate administration plans for one or more individuals to whom infusate is to be administered. In an embodiment, the information may be obtained from database 308.

[0060] In step 604 of Figure 6A, the monitor device is configured to control the transceiver to receive information regarding the monitored administration of the received infusion fluid. In an embodiment, the information is sent from one or more drip counter devices.

[0061] In step 606 of FIG. 6A, the monitoring device is configured to combine and compare the monitored administration with an administration plan.

[0062] In step 608 of Figure 6A, the monitoring device is configured to control a user interface to display information related to the monitored administration and administration plans of one or more drip counter devices. In embodiments, the monitoring device is configured to show the status of all connected drip counter devices on a single overview screen, providing a quick and reliable method of monitoring the devices. The information may also be stored in database 308.

[0063] In a hospital ward, there may be several patients receiving intravenous infusions at the same time. There may be few personnel to check the infusions, especially at night. Problems may arise when one of the personnel does not have time to go to the patient and check the infusion. The infusion may be performed too quickly, or it may stop without any alarm. These problems may lead to complications. The proposed solution facilitates the management of infusion counters.

[0064] 6B is another flow diagram illustrating some embodiments of the present invention. FIG. 6B illustrates another example of the operation of the monitor device 318.

[0065] In step 620 of FIG. 6B , the monitor device is configured to combine the monitored administration with information about the individual to whom the infusion fluid was administered and the characteristics of one or more drip counter devices and the environment in which they are used to obtain statistical data related to the individual to whom the infusion fluid was administered, to multiple individuals to whom the infusion fluid was administered, to the individual who activated the drip counter device, and to the characteristics of the one or more drip counter devices and the environment in which they are used.

[0066] In step 622 of FIG. 6B, the monitoring device is configured to calculate a correlation between the care plan and the infusate administration plan and the difference in the monitored administration.

[0067] 6B, the monitor device is configured to control a user interface to display the results. The information may also be stored in the database 308.

[0068] In embodiments, the monitoring device may provide suggestions for actions to reduce the difference between the care plan and the infusate administration plan and the monitored administration.

[0069] For example, the actions may include one or more of: inspecting drip counter device functionality; inspecting drip counter device accessories; inspecting drug or fluid packaging; inspecting care practices; inspecting user instructions; inspecting usage settings and practices; suggesting dedicated plan instructions; and suggesting instructions related to usage conditions.

[0070] The proposed solution allows for analyzing how the realized care plan (infusion fluid) relates to the planned care plan in different use cases and situations. It is useful to know if there is a correlation with device type, setpoints, user, department, drug, fluid type and manufacturer, pipe and clamp type and manufacturer to improve reliability and accuracy and potentially guide users to test devices separately, notify and alarm users separately, and guide care plan designers (such as doctors) to plan separately.

[0071] An embodiment is illustrated in Figure 7. This figure shows a simple example of a monitoring device or apparatus 318 to which an embodiment of the present invention may be applied.

[0072] It should be understood that the devices are depicted herein as examples illustrating some embodiments. It will be apparent to those skilled in the art that the devices may also include other functions and / or structures and may not require all of the functions and structures described. Although the devices are depicted as a single entity, different modules or memories may be implemented in one or more physical or logical entities.

[0073] The device 318 in this example includes a control circuit or processor 700 configured to control at least a portion of the operation of the device.

[0074] The device may include a memory 702 for storing data. Additionally, the memory may store software 704 executable by the control circuitry or processor 700. The memory may be integrated into the control circuitry.

[0075] The apparatus may include a transceiver 708 configured to communicate with other devices in a wired or wireless manner. The transceiver may be connected to an antenna arrangement 710. The transceiver may be a wireless transceiver utilizing Bluetooth®, Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN or E-UTRAN), Long Term Evolution (LTE, same as E-UTRA), Wireless Local Area Network (WLAN or WiFi), Worldwide Interoperability for Microwave Access (WiMAX), or any combination thereof. The interface may be an interface to a wired communication system. The transceiver may be operatively connected to the control circuitry 700.

[0076] The software 704 may include a computer program including program code means adapted to cause the device's control circuitry or processor 700 to carry out the embodiments described above and claimed.

[0077] The device may include a user interface 706. The user interface may include, for example, a display, a keyboard, or a keypad. The display may also be touch-sensitive.

[0078] The steps and associated functions described above and in the accompanying drawings are not in an absolute chronological order, and some of the steps may be performed simultaneously or in a different order than given. Other functions may also be performed between or within steps. Some of the steps may also be omitted or replaced by corresponding steps.

[0079] The device or controller capable of performing the above-described steps can be implemented as an electronic digital computer that can include a working memory (RAM), a central processing unit (CPU), and a system clock. The CPU can include a set of registers, an arithmetic logic unit, and a controller. The controller is controlled by a series of program instructions transferred from the RAM to the CPU. The controller may contain several microinstructions for basic operations. The implementation of the microinstructions may vary depending on the CPU design. The program instructions can be coded in a programming language that can be a high-level programming language such as C, Java, etc., or a low-level programming language such as machine language or assembler. The electronic digital computer can also have an operating system that can provide system services to computer programs written in the program instructions.

[0080] As used in this application, the term "circuitry" refers to all of the following: (a) hardware-only circuit implementations, such as implementations with only analog and / or digital circuitry, and (b) combinations of circuitry and software (and / or firmware) (when applicable), such as (i) a combination of a processor or (ii) portions of a processor / software including a digital signal processor, software, and memory that work together to cause a device to perform various functions, and (c) a microprocessor or portion of a microprocessor that requires software or firmware for operation even if the software or firmware is not physically present.

[0081] This definition of "circuit" applies to all uses of the term in this application. As yet another example, when used in this application, the term "circuit" is also considered to cover merely a processor(s) or portion of a processor and its(their) accompanying software and / or firmware implementation. The term "circuit" is also considered to cover, for example, and where applicable to the particular element, a baseband integrated circuit or an application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network device, or another network device.

[0082] The computer program may be in source code form, object code form or any intermediate form and it may be stored on any kind of carrier, which may be any entity or device capable of carrying a program. Such carriers include, for example, recording media, computer memory, read-only memory and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or it may be distributed among several computers.

[0083] The device can also be implemented as one or more integrated circuits, such as an application specific integrated circuit (ASIC). Other hardware implementations are also possible, such as circuits built from discrete logic components. Hybrids of these different implementations are also possible. When selecting an implementation method, one skilled in the art will consider a set of requirements regarding, for example, the size and power consumption of the device, the required processing capacity, production costs, and production volume.

[0084] In embodiments, an apparatus applying some embodiments of the present invention includes means for acquiring information about a drip counter device, means for acquiring information about an infusion fluid administration plan for an individual to whom the infusion fluid is to be administered, means for transmitting information about the acquired information to a system monitor device, means for receiving device parameters for administering the infusion fluid according to the administration plan, means for monitoring the administration of the infusion fluid, means for comparing the administration with the administration plan, means for controlling the transmission of information about the monitoring or comparison results to the system monitor device, and means for controlling the display of the comparison results.

[0085] In embodiments, an apparatus for applying some embodiments of the present invention includes means for obtaining information regarding one or more individuals who operate one or more drip counter devices, individuals to whom infusion fluid will be administered using one or more drip counter devices, characteristics of the one or more drip counter devices and the environment in which they are used, means for obtaining information regarding the care plans and infusion fluid administration plans of the one or more individuals to whom the infusion fluid will be administered, means for receiving information regarding the monitored administration of the received infusion fluid, means for combining and comparing the monitored administration with the administration plans, and means for displaying information related to the monitored administration and administration plans of the one or more drip counter devices.

[0086] It will be obvious to those skilled in the art that, as technology advances, the concept of the present invention can be implemented in various ways. The present invention and its embodiments are not limited to the examples described above, but rather may vary within the scope of the claims. [Explanation of symbols]

[0087] 400 Obtaining information about characteristics 402 controlling the transceiver to receive 404 controlling the transceiver to transmit 406 Receiving Administration Parameters 408 Monitoring Administration

Claims

1. 1. A drip counter device for counting infusion fluid drips, comprising: a drip detector; A user interface; A transmitter / receiver, at least one processor; at least one memory containing computer program code; Including, The at least one memory and the computer program code are used by the at least one processor to: obtaining information about the drip counter device regarding characteristics of the drip counter device, including accessories connected to the drip counter device, the location where the drip counter device is located, and date and time information; controlling the transceiver to obtain information regarding an infusion administration plan including an amount of infusion to be administered within a given time interval for an individual to whom the infusion is to be administered; controlling the transceiver to transmit the acquired information to a system monitoring device that monitors the drip counter device; receiving device parameters for administering an infusate according to the infusate administration plan; monitoring said administration of said infusion solution; comparing said administration to said infusion dosing plan; determining, based on the monitoring of the administration of the infusate, that the infusate administration plan is not being met; controlling the transceiver to transmit information regarding the monitoring or comparison results to the system monitoring device; controlling the user interface to display the comparison results; generating an alarm based on said determination; indicating the time elapsed since the alarm; and causing the drip counter device to at least: Drip counter device.

2. The at least one memory and the computer program code are used by the at least one processor to: determining updated device parameters based on said monitoring; indicating the updated parameters; and further configured to cause the device to:

10. The drip counter device of claim 1.

3. The at least one memory and the computer program code are used by the at least one processor to: Raising an alarm having a given type; changing the type of the alarm if an acknowledgment of the alarm is not detected by the user interface within a given time limit; and further configured to cause the device to:

10. The drip counter device of claim 1.

4. The at least one memory and the computer program code are used by the at least one processor to: receiving information regarding the individual to whom the infusion is to be administered; generating an alarm having a given type selected based on the received information regarding the individual to whom the infusion solution is to be administered; and further configured to cause the device to:

10. The drip counter device of claim 1.

5. The at least one memory and the computer program code are used by the at least one processor to: determining that a previous alarm was given within a given time frame; selecting the alarm type based on the determination; and further configured to cause the device to:

10. The drip counter device of claim 1.

6. 1. An apparatus for monitoring one or more drip counter devices, comprising: A user interface; A transmitter / receiver, at least one processor; at least one memory containing computer program code; Including, The at least one memory and the computer program code are used by the at least one processor to: controlling the transceiver to obtain information regarding one or more individuals who operate one or more drip counter devices, individuals to whom infusion fluids will be administered utilizing the one or more drip counter devices, characteristics of the one or more drip counter devices, and the environment in which they are used; controlling the transceiver to obtain information regarding one or more individual care plans to which an infusate is to be administered and an infusate administration plan including an amount of infusate to be administered within a given time interval; controlling the transceiver to receive information regarding monitored administration of the accepted infusion fluid indicating that the infusion fluid administration plan is not being met; combining and comparing the monitored administration with the infusion administration plan; controlling the user interface to display information related to the monitored administrations and the infusion administration plan of the one or more drip counter devices; and causing the drip counter device to at least: Device.

7. The at least one memory and the computer program code are used by the at least one processor to: combining the monitored administrations with information about the individuals to whom the infusion fluid is administered and the characteristics of the one or more drip counter devices and the environments in which they are used to obtain statistical data relating to each individual to whom the infusion fluid is administered, and to a plurality of individuals to whom the infusion fluid is administered, to individuals who activate the one or more drip counter devices, and to the characteristics of the one or more drip counter devices and the environments in which they are used; calculating a correlation between the care plan and the infusion fluid administration plan and the difference in monitored administration; controlling the user interface to display the results; The device is further configured to:

7. The apparatus of claim 6.

8. The at least one memory and the computer program code are used by the at least one processor to: providing action suggestions to reduce discrepancies between the care plan and the infusion fluid administration plan and monitored administration; The device is further configured to:

8. The apparatus of claim 7.

9. The action is Inspection of drip counter device functionality, inspection of drip counter device accessories, inspection of drug or liquid packaging, inspection of care practices, inspection of user instructions, inspection of usage settings and practices, suggestions on dedicated plan instructions, suggestions on instructions related to conditions of use, including one or more of 9. The apparatus of claim 8.

10. 1. A method of operating a drip counter device, comprising: obtaining information about the drip counter device regarding characteristics including accessories connected to the drip counter device, the location where the drip counter device is located, and date and time information; controlling the transceiver to obtain information regarding an infusion administration plan including an amount of infusion to be administered within a given time interval for an individual to whom the infusion is to be administered; controlling the transceiver to transmit the acquired information to a system monitoring device that monitors the drip counter device; receiving device parameters for administering the infusate according to the infusate administration plan; monitoring said administration of said infusion fluid; comparing said administration to said infusion administration plan; determining that the infusion fluid administration plan is not being met based on the monitoring of the administration of the infusion fluid; controlling the transceiver to transmit information regarding the monitoring or comparison results to the system monitoring device; controlling a user interface to display the comparison results; generating an alarm based on said determination; indicating the time elapsed since said alarm; A method comprising:

11. determining updated device parameters based on said monitoring; indicating the updated parameters; The method of claim 10 further comprising:

12. generating an alarm having a given type; changing the type of the alarm if an acknowledgment of the alarm is not detected by the user interface within a given time limit; The method of claim 10 further comprising:

13. 1. A method of monitoring one or more drip counter devices, comprising: controlling the transceiver to obtain information regarding one or more individuals who operate one or more drip counter devices, individuals to whom infusion fluids will be administered utilizing the one or more drip counter devices, and characteristics of the one or more drip counter devices and the environment in which they are used; controlling the transceiver to obtain information regarding one or more individual care plans to which infusate is to be administered and an infusate administration plan including an amount of infusate to be administered within a given time interval; controlling the transceiver to receive information regarding monitored administration of the accepted infusion fluid indicating that the infusion fluid administration plan is not being met; combining and comparing the monitored administration with the infusion administration plan; controlling a user interface to display information related to the monitored administrations of the one or more drip counter devices and the infusion administration plan; A method comprising:

14. combining the monitored administrations with information about the individuals to whom the infusion fluid is administered and the characteristics of the one or more drip counter devices and the environment in which they are used to obtain statistical data relating to each individual to whom the infusion fluid is administered, and to multiple individuals to whom the infusion fluid is administered, to individuals who activate the drip counter devices, and to the characteristics of the one or more drip counter devices and the environment in which they are used; calculating a correlation between the care plan and the infusion fluid administration plan and the difference in monitored administration; controlling the user interface to display results; The method of claim 13 further comprising:

15. 1. A computer program comprising instructions for causing a drip counter device to execute: obtaining information about the drip counter device regarding characteristics of the drip counter device, including accessories connected to the drip counter device, the location where the drip counter device is located, and date and time information; controlling the transceiver to obtain information regarding an infusion administration plan including an amount of infusion to be administered within a given time interval for an individual to whom the infusion is to be administered; controlling the transceiver to transmit the acquired information to a system monitoring device that monitors the drip counter device; receiving device parameters for administering the infusate according to the infusate administration plan; controlling a drip detector to monitor administration of infusate by determining the amount of infusate administered; comparing the determined amount of infusate administered with the required amount of infusate to be administered as indicated in the infusate administration plan; calculating the amount of fluid administered from the start of administration based on data obtained from the drip detector; determining whether the infusion fluid administration plan is met or not met based on the monitoring of the administration of the infusion fluid and the determination; controlling the transceiver to transmit information regarding the monitoring or comparison results to the system monitoring device; Controlling a user interface to display the comparison results; generating an alarm based on said determination; indicating the time elapsed since the alarm; A computer program that makes things happen.

16. 1. A computer program comprising instructions for causing an apparatus for monitoring one or more drip counter devices to execute the computer program, the computer program comprising: controlling the transceiver to obtain information regarding one or more individuals who operate one or more drip counter devices, individuals to whom infusion fluids will be administered utilizing the one or more drip counter devices, and characteristics of the one or more drip counter devices and the environment in which they are used; controlling the transceiver to obtain information regarding one or more individual care plans to which an infusate is to be administered and an infusate administration plan including an amount of infusate to be administered within a given time interval; controlling the transceiver to receive information regarding monitored administration of the accepted infusion fluid indicating that the infusion fluid administration plan is not being met; combining and comparing the monitored administration with the infusion administration plan; controlling a user interface to display information related to the monitored administrations of the one or more drip counter devices and the infusion administration plan; A computer program that makes things happen.

Images