Infusion Container Fluid Replacement Monitoring Method, System, Device, and Medium

Abstract

The present application discloses a method and system, device, and medium for monitoring the replacement of infusion containers, which relates to the technical field of data processing. The method includes: each master control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located; determines the current communication level of each corresponding master control unit according to each ward infusion status label; the monitoring host determines the master control unit with the first communication level as the target communication object and establishes a communication connection; determines the master control unit with the second communication level as the non-target communication object and does not establish a communication connection; determines the message sending delay of the target communication object according to the ward infusion status label; and sends the generated data message to the monitoring host at the target communication interval message sending delay, so that the monitoring host determines the replacement liquid recommendation order information according to the ward infusion status label and the infusion status information. It can improve the accuracy and reliability of infusion monitoring and improve the liquid replacement efficiency.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and in particular to a method and system, device, and medium for monitoring the replacement of infusion containers. Background Art

[0002] During the hospitalization process, patients often need to receive infusion treatment, and at the same time, nurses need to be equipped to perform relevant nursing and infusion replacement work. In the traditional patient infusion process, the patient or the patient's family member monitors the remaining amount of liquid in the infusion container and the infusion flow rate by themselves. When the infusion is too fast or the remaining amount of liquid in the infusion container is small, they call the nurse to handle it. However, the number of nurses configured at each nurse station in the inpatient department is limited, usually only two or three nurses. In the case of a large number of patients and concentrated infusions, the workload of nurses will increase greatly. The traditional method completely relies on manual monitoring, and often the situation is not discovered until the liquid in the infusion container has been completely infused, or when the number of patients who need to replace the liquid medicine at the same time is large and the nurse cannot take care of each infusion person in time. In this way, it is easy to cause dangerous situations such as needle running and blood backflow for patients.

[0003] In the related art, infusion monitoring is a system that uses wireless sensor network technology to automatically read and process patient infusion information and comprehensively process the patient's medicine replacement information. The infusion monitoring system has achieved more comprehensive and effective management. However, the construction of the entire system is relatively complex, and the accuracy of infusion data is not high. The delay of the system is also relatively large, and it is easy to have data congestion, resulting in delayed data transmission, and it is impossible to effectively monitor the ward situation and replace the infusion container in time. The accuracy and reliability of infusion monitoring are relatively low. Even if infusion monitoring is adopted, there will be different call times in the wards at different locations, resulting in nurses making round trips for infusion replacement operations, causing waste and overdraw of nurses' physical strength, and also increasing the response time for other infusion replacement work, reducing the infusion replacement efficiency. Summary of the Invention

[0004] This application aims to at least solve one of the technical problems existing in the prior art. For this purpose, this application provides a method and system, device, and medium for monitoring the replacement of infusion containers, which can reduce data congestion and data delay, improve the accuracy and reliability of infusion monitoring, and provide a reliable reference for nurses to replace the liquid medicine in an orderly manner through the infusion replacement order recommendation information, improving the infusion replacement efficiency.

[0005] In a first aspect, an embodiment of this application provides a method for monitoring the replacement of infusion containers, which is applied to an infusion container replacement monitoring system. The system includes: a monitoring host, a status monitoring module set corresponding to each hospital bed, and a main control unit set corresponding to each ward; each main control unit is electrically connected to all the status monitoring modules in the corresponding ward; the method includes:

[0006] Each of the master control units generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module; determines the current communication level of each of the master control units according to each of the ward infusion status labels; the current communication level is the first communication level or a second communication level lower than the first communication level;

[0007] The monitoring host determines the master control unit with the first communication level as the target communication object, and establishes a communication connection with the target communication object; determines the master control unit with the second communication level as the non-target communication object, and does not establish a communication connection with the non-target communication object; determines the message sending delay of the target communication object according to the ward infusion status label uploaded by the target communication object;

[0008] The target communication object generates a data message according to the ward infusion status label and the infusion status information, and sends the data message to the monitoring host at intervals of the message sending delay, so that the monitoring host determines the liquid change recommendation order information according to the ward infusion status label and the infusion status information.

[0009] In a second aspect, an embodiment of the present application provides an infusion container liquid change monitoring system, including: a monitoring host, a status monitoring module provided for each hospital bed, and a master control unit provided for each ward; each of the master control units is electrically connected to all the status monitoring modules in the corresponding ward; the monitoring host, the status monitoring module, and the master control unit cooperate with each other to implement the infusion container liquid change monitoring method according to any one of the embodiments in the first aspect.

[0010] In a third aspect, an embodiment of the present application provides an electronic device, including at least one processor and a memory for communicating with the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the infusion container liquid change monitoring method according to any one of the embodiments in the first aspect.

[0011] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, and the computer-readable storage medium stores computer-executable instructions for causing a computer to execute the infusion container liquid change monitoring method according to any one of the embodiments in the first aspect.

[0012] Embodiments of the present application include: An infusion container fluid replacement monitoring system includes: a monitoring host, a status monitoring module provided for each hospital bed, and a main control unit provided for each ward; each main control unit is electrically connected to all status monitoring modules in the corresponding ward; during the process of using the infusion container fluid replacement monitoring system to monitor the fluid replacement of the infusion container, first, each main control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module; determines the current communication level of each corresponding main control unit according to each ward infusion status label; the current communication level is the first communication level or the second communication level lower than the first communication level; secondly, the monitoring host determines the main control unit with the first communication level as the target communication object and establishes a communication connection with the target communication object; determines the main control unit with the second communication level as the non-target communication object and does not establish a communication connection with the non-target communication object; thereby reducing the data and connection requests that the monitoring host needs to process, which is beneficial to reducing the processing volume of the monitoring host and ensuring that the monitoring host maintains a relatively high processing performance; the monitoring host determines the message sending delay of the target communication object according to the ward infusion status label uploaded by the target communication object; determining the message sending delay based on the actual ward infusion status label provides a reference for the target communication object to send data messages in an orderly manner and reduces the occurrence probability of the situation where all main control units send data messages at the same time; after establishing the communication connection, the target communication object generates a data message according to the ward infusion status label and the infusion status information, and sends the data message to the monitoring host at intervals of the message sending delay, so that the monitoring host determines the fluid replacement recommendation order information according to the ward infusion status label and the infusion status information. The monitoring host can receive data messages sent by multiple target communication objects in an orderly manner with less conflict, which is beneficial to reducing data congestion and data delay, improving the accuracy and reliability of infusion monitoring, and providing a reliable reference for nurses to replace the liquid medicine in an orderly manner based on the fluid replacement order recommendation information, thereby improving the fluid replacement efficiency. That is to say, the embodiments of the present application can reduce data congestion and data delay, improve the accuracy and reliability of infusion monitoring, and provide a reliable reference for nurses to replace the liquid medicine in an orderly manner through the fluid replacement order recommendation information, thereby improving the fluid replacement efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a schematic diagram of the system framework of an infusion container fluid replacement monitoring system provided by an embodiment of the present application;

[0014] Figure 2 is a schematic diagram of the specific module composition of a status monitoring module provided by an embodiment of the present application;

[0015] Figure 3 is a schematic diagram of the step flow of an infusion container fluid replacement monitoring method provided by an embodiment of the present application;

[0016] Figure 4 It is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0017] In order to make the objectives, technical solutions and advantages of the present application more clear and understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments.

[0018] It should be understood that in the description of the present application, the orientation descriptions involved, such as up, down, front, back, left, right, etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. It is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it should not be construed as a limitation to the present application.

[0019] It should be noted that although the logical order is shown in the flowchart in the description of the present application, in some cases, the steps shown or described can be executed in a different order from that in the flowchart. In the description of the present application, the meaning of several is one or more, and the meaning of multiple is two or more. The descriptions of "first" and "second" are only for the purpose of distinguishing technical features, and should not be construed as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features or the sequence of the indicated technical features.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0021] The present application provides an infusion container liquid change monitoring method, an infusion container liquid change monitoring system, an electronic device and a computer-readable storage medium. The method includes: each main control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located; determines the current communication level of each corresponding main control unit according to each ward infusion status label; the monitoring host determines the main control unit with the first communication level as the target communication object and establishes a communication connection; determines the main control unit with the second communication level as the non-target communication object and does not establish a communication connection; determines the message sending delay of the target communication object according to the ward infusion status label; and sends the generated data message to the monitoring host at the target communication interval message sending delay, so that the monitoring host determines the liquid change recommendation order information according to the ward infusion status label and the infusion status information. It can improve the accuracy and reliability of infusion monitoring and improve the liquid change efficiency.

[0022] The following further elaborates on the embodiments of the present application with reference to the accompanying drawings.

[0023] As shown Figure 1 in FIG. 1, the transfusion container fluid replacement monitoring system 100 includes: a monitoring host 110, a status monitoring module 120 provided for each hospital bed, and a main control unit 130 provided for each ward; each main control unit is electrically connected to all the status monitoring modules in the corresponding ward.

[0024] Specifically, the status monitoring module 120 is configured to collect gravity detection values and transfusion images, and provide a data analysis basis for the main control unit 130 to determine the second transfusion status values of each transfusion task in the ward where it is located. Specifically, as Figure 2 shown in FIG. 2, the status monitoring module 120 includes: a gravity sensor 121 and an image collector 122.

[0025] Specifically, the gravity sensor 121 is disposed on the transfusion rack for placing the transfusion container, and is configured to obtain the gravity detection value. It can be understood that when there are multiple groups of transfusion requirements for one transfusion task at the same time, multiple hooks can be provided on the transfusion rack, and a gravity sensor 121 is correspondingly provided on each hook, so that each gravity sensor 121 respectively detects the gravity detection value of each transfusion container. Therefore, the embodiment of the present application does not specifically limit the number of gravity sensors 121 provided on the transfusion rack.

[0026] Specifically, the image collector 122 is configured to be started when the gravity detection value detected by the gravity sensor 121 is not 0, and collect a transfusion image of the corresponding transfusion container hanging area; lay a data foundation for the main control unit 130 to perform image recognition to determine the position of the liquid level dividing line. It can be understood that an image collector 122 can be configured corresponding to each hospital bed to correspondingly collect images of the transfusion container hanging area. Therefore, the present application does not specifically limit the number, specific model, and installation position of the image collector 122.

[0027] Specifically, the main control unit 130 is configured to: generate a ward transfusion status label according to the first transfusion status value corresponding to each transfusion task in the ward where it is located obtained through the status monitoring module; determine the current communication level of the corresponding main control unit according to each ward transfusion status label; the current communication level is the first communication level or a second communication level lower than the first communication level; after being communicatively connected to the monitoring host, generate a data message according to the ward transfusion status label and the transfusion status information, and send the data message to the monitoring host 110 after an interval based on the message sending delay determined by the ward transfusion status label.

[0028] Specifically, the monitoring host 110 is used to: determine the master control unit 130 with the first communication level as the target communication object and establish a communication connection with the target communication object; determine the master control unit 130 with the second communication level as the non-target communication object and not establish a communication connection with the non-target communication object; determine the message sending delay of the target communication object according to the ward infusion status label uploaded by the target communication object; determine the liquid change recommendation order information according to the ward infusion status label and the infusion status information.

[0029] The infusion container liquid change monitoring system 100 of the embodiments of the present application realizes the monitoring of the liquid change of the infusion container through the cooperation of the monitoring host 110, the status monitoring module 120, and the master control unit 130, which can reduce data congestion and data delay, improve the accuracy and reliability of infusion monitoring, and provide a reliable reference for nurses to change the liquid medicine in an orderly manner through the liquid change order recommendation information, improving the liquid change efficiency.

[0030] Those skilled in the art can understand that the system structure shown in the figure does not constitute a limitation on the embodiments of the present application, and may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements.

[0031] The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0032] Those skilled in the art can understand that the system architecture and application scenarios described in the embodiments of the present application are for the purpose of more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art know that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0033] Based on the above system structure, the following are various embodiments of the infusion container liquid change monitoring method of the present application.

[0034] In the first aspect, as Figure 3 shown, the infusion container liquid change monitoring method can be applied to the system framework as Figure 1 shown. The infusion container liquid change monitoring system includes: a monitoring host, a status monitoring module provided for each hospital bed, and a master control unit provided for each ward; each master control unit is electrically connected to all status monitoring modules in the corresponding ward; the infusion container liquid change monitoring method may include but is not limited to steps S110 to S130.

[0035] Step S110: Each master control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module; determines the current communication level of each corresponding master control unit according to each ward infusion status label; the current communication level is the first communication level or the second communication level lower than the first communication level.

[0036] Step S120: The monitoring host determines the master control unit with the first communication level as the target communication object and establishes a communication connection with the target communication object; determines the master control unit with the second communication level as the non-target communication object and does not establish a communication connection with the non-target communication object; determines the message sending delay of the target communication object according to the ward infusion status label uploaded by the target communication object.

[0037] Step S130: The target communication object generates a data message according to the ward infusion status label and the infusion status information, and sends the data message to the monitoring host at intervals of the message sending delay, so that the monitoring host determines the liquid change recommendation order information according to the ward infusion status label and the infusion status information.

[0038] Specifically, the connection method between the monitoring host and the target communication object is a wireless communication connection.

[0039] Through steps S110 to S130, in the process of monitoring the replacement of an infusion container using the infusion container replacement monitoring system, first, each master control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module; determines the current communication level of each corresponding master control unit according to each ward infusion status label; the current communication level is the first communication level or the second communication level lower than the first communication level; secondly, the monitoring host determines the master control unit with the first communication level as the target communication object and establishes a communication connection with the target communication object; determines the master control unit with the second communication level as the non-target communication object and does not establish a communication connection with the non-target communication object; thereby reducing the data and connection requests that the monitoring host needs to process, which is beneficial to reducing the processing volume of the monitoring host and ensuring that the monitoring host maintains a relatively high processing performance; the monitoring host determines the message sending delay of the target communication object according to the ward infusion status label uploaded by the target communication object; determining the message sending delay based on the actual ward infusion status label provides a reference for the target communication object to send data messages in an orderly manner and reduces the probability of the situation where all master control units send data messages at the same time; after establishing a communication connection, the target communication object generates a data message according to the ward infusion status label and the infusion status information, and sends the data message to the monitoring host at intervals of the message sending delay, so that the monitoring host determines the replacement liquid recommendation order information according to the ward infusion status label and the infusion status information. The monitoring host can receive data messages sent by multiple target communication objects in an orderly manner with fewer conflicts, which is beneficial to reducing data congestion and data delay, improving the accuracy and reliability of infusion monitoring, and providing a reliable reference for nurses to replace the liquid medicine in an orderly manner based on the replacement liquid order recommendation information, thereby improving the replacement liquid efficiency. Therefore, the embodiment of the present application can reduce data congestion and data delay, improve the accuracy and reliability of infusion monitoring, and provide a reliable reference for nurses to replace the liquid medicine in an orderly manner based on the replacement liquid order recommendation information, thereby improving the replacement liquid efficiency.

[0040] According to some embodiments of the present application, step S110 is further described. Among them, each master control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module, including but not limited to steps S210 to S230.

[0041] Step S210: Each master control unit determines the second infusion status value of at least one infusion container corresponding to each infusion task in the ward where it is located through the status monitoring module.

[0042] Step S220: From the at least one second infusion status value corresponding to a single infusion task, determine the second infusion status value with the largest value as the first infusion status value corresponding to the infusion task.

[0043] Step S230: Each master control unit sequentially splices the first infusion status values corresponding to each infusion task in the ward where it is located in descending order to obtain the initial infusion status label corresponding to the ward where it is located.

[0044] Step S240: Count the label lengths of each initial infusion status label, and determine the maximum value of the label lengths as the target length.

[0045] Step S250: Determine the initial infusion status label with the label length equal to the target length as the final ward infusion status label; add 0 at the end of the initial infusion status label with the label length less than the target length to obtain the ward infusion status label with the label length equal to the target length.

[0046] It can be understood that there are multiple patients in a ward who need infusion, so there are corresponding infusion tasks. The number of infusion tasks may be 0 or multiple. The maximum number of infusion tasks is the same as the number of patients. This application does not specifically limit the number of infusion tasks in a ward.

[0047] It can be understood that the numerical length of the ward infusion status label is the same as the number of hospital beds, and there are four in a ward.

[0048] It can be understood that in one infusion task, it may be possible to only infuse one kind of liquid medicine into the patient at a time, so one infusion container needs to be hung and multiple medicine replacements are required; it may also be necessary to infuse multiple kinds of liquid medicines into the patient at the same time, and multiple infusion containers need to be hung; the flow rates of the liquid medicines in multiple infusion containers are different, and it may be necessary to replace the medicine midway. Therefore, the embodiments of this application need to detect each infusion container involved in the infusion task separately. The embodiments of this application do not specifically limit the number of medicine replacements and the types of infusions involved in the infusion task.

[0049] It can be understood that the infusion container is made of a transparent material, and the liquid situation inside it can be observed from the outside.

[0050] According to some embodiments of the present application, step S210 is further described. The status monitoring module includes: a gravity sensor and an image collector; step S210: Determine the second infusion status value of at least one infusion container corresponding to each infusion task in the ward where it is located through the status monitoring module, including but not limited to steps S211 to S218.

[0051] Step S211: Obtain the gravity detection value through the gravity sensor.

[0052] Step S212: When the gravity detection value is 0, determine the second infusion status value as 0.

[0053] Step S213: When the gravity detection value is not 0, calculate based on the gravity detection value to determine the current tare weight. When the current tare weight is greater than the preset threshold, determine that the second infusion status value of the infusion container is 1.

[0054] Step S214: When the current tare weight is equal to the preset threshold, start the image collector to collect an infusion image of the corresponding infusion container hanging area.

[0055] Step S215: Perform image recognition processing on the infusion image to determine the position of the liquid level dividing line.

[0056] Step S216: When the position of the liquid level dividing line is inside the infusion container and higher than the preset dividing position, determine that the second infusion status value of the infusion container is 2.

[0057] Step S217: When the position of the liquid level dividing line is inside the infusion container and not higher than the preset dividing position, determine that the second infusion status value of the infusion container is 3.

[0058] Step S218: When the position of the liquid level dividing line is not inside the infusion container, determine that the second infusion status value of the infusion container is 4.

[0059] Step S219: When the infusion container with the second infusion status value of 4 is the last infusion container, add 1 to the second infusion status value to get a new second infusion status value of 5.

[0060] It can be understood that when the gravity detection value is 0, it is judged that there is no infusion container hanging and no infusion task, and then the second infusion status value is determined to be 0 to indicate that there is no infusion task for the patient in this hospital bed. When the gravity detection value is not 0, it is judged that there is an infusion container hanging and there is an infusion task.

[0061] In an embodiment, steps S212 and S213 are further described. During the dressing change process of removing an empty infusion container and replacing it with a full infusion container, the gravity detection value may fluctuate and may fluctuate to 0; and when directly ending the infusion task after removing the empty infusion container or when there is no need to perform an infusion task, it will be detected that the gravity detection value is 0; therefore, in order to exclude the situation where the gravity detection value fluctuates due to dressing change and accurately judge whether there is an infusion task currently, a preset fluctuation allowable time is configured. Specifically, when it is continuously detected that the gravity detection value is 0 within the preset fluctuation allowable time, it is determined that the second infusion status value is 0, that is, it can be judged that there is no infusion task; specifically, when it is continuously detected that the gravity detection value is not 0 within the preset fluctuation allowable time, it is determined that the second infusion status value is not 0, that is, it can be judged that there is an infusion task. It can be understood that the preset fluctuation allowable time can be 3 seconds, 5 seconds, etc. Therefore, the specific value of the preset fluctuation allowable time in the embodiments of the present application is not specifically limited and can be configured according to the average single dressing change time of the nurse.

[0062] In some embodiments, when it is determined in step S212 that there is an infusion task, it is necessary to continuously monitor the gravity detection value of the infusion container through step S213 until the current tare weight calculated based on the gravity detection value is not greater than a preset threshold, and then start image recognition detection to more accurately identify the position of the liquid level boundary line in the infusion container. It can be understood that it takes a relatively long time from just changing the liquid to the stage where the liquid level in the infusion container drops to a stage that requires close attention; if image recognition detection is always enabled during this period, it will result in a large data processing volume, complex data processing, and high load on the main control unit in each ward. Therefore, in the embodiment of the present application, through steps S211 to S213, rough detection in the first stage is realized based on monitoring the gravity detection value; if it is determined in step S214 that the result of the rough detection reaches the start condition, fine detection in the second stage is started; and then through steps S215 to S218, image recognition processing is performed based on the infusion image to realize fine detection in the second stage; thereby reducing the data processing load on the main control unit to a certain extent.

[0063] To further illustrate step S213, after it is determined that there is an infusion task, it is necessary to continuously monitor the gravity detection value of the infusion container. However, during this process, the patient will move, and the patient's activity state will cause the infusion container to shake, resulting in fluctuations and mutations in the gravity detection value collected by the gravity sensor, and discrete values with large deviations will appear. Inaccurate gravity detection values will also lead to inaccurate calculated tare weights, affecting subsequent judgments. Therefore, it is necessary to design a gravity detection value processing mechanism to improve the accuracy of the selected gravity detection value and the calculated tare weight. Specifically, calculating the current tare weight based on the gravity detection value includes but is not limited to the following steps.

[0064] First, in the current detection cycle T, all discrete real-time gravity detection values ​​detected and recorded in the previous detection cycle T are obtained, and data graph drawing processing is performed based on the discrete real-time gravity detection values ​​in the previous detection cycle T to obtain a two-dimensional line graph, wherein the X-axis in the line graph is the time axis and the Y-axis is the real-time gravity detection value; the data graph drawing processing includes: determining a discrete point based on a discrete time point and the real-time gravity detection value detected at the discrete time point; the time interval between each two adjacent discrete time points is the same. For example: there are discrete time points t1, t2, and t3; the time interval between t1 and t2, and the time interval between t2 and t3 are all 1s. When all discrete points are drawn, a straight line is used to connect from the first discrete point to the next discrete point in sequence until it is connected to the last discrete point to obtain a line graph. Then, based on the discrete values ​​of the discrete points at both ends of the line segment (that is, the real-time gravity detection value), the absolute value of the line segment slope of each line segment in the line graph is calculated. Then, at least two target line segments whose absolute values ​​of line segment slopes are greater than a preset slope threshold are screened out, and the discrete points that appear twice in at least two target line segments are determined as deviation points. Alternatively, the discrete points other than the first discrete point and the last discrete point are determined as intermediate discrete points. When the absolute values ​​of the line segment slopes of the two line segments with the intermediate discrete point as one of the endpoints are greater than the preset slope threshold, it is determined that data fluctuations and mutations occur, and the intermediate discrete point is determined as a deviation point. The deviation points are eliminated from the intermediate discrete points to obtain the remaining intermediate discrete points; finally, based on the number of the remaining intermediate discrete points and the sum of the discrete values, the mean is calculated to obtain the gravity detection value within the last detection cycle T. In this way, the gravity detection value processing mechanism is realized. By excluding the discrete points within the last detection cycle T and estimating the gravity detection value of the last detection cycle T, the accuracy of the gravity detection value used is improved, which is conducive to improving the accuracy of the subsequently calculated tare weight and improving the reliability of infusion monitoring to a certain extent.

[0065] Taking an example for further illustration, the detection period T is 5 seconds, and the time interval between two adjacent discrete time points is 1 s. The real-time gravity detection value corresponding to the discrete time point t1 (the 1st second) is 60 g, denoted as the discrete point A1; the real-time gravity detection value corresponding to the discrete time point t2 (the 2nd second) is 59.8 g, denoted as the discrete point A2; the real-time gravity detection value corresponding to the discrete time point t3 (the 3rd second) is 100 g, denoted as the discrete point A3; the real-time gravity detection value corresponding to the discrete time point t4 (the 4th second) is 59.6 g, denoted as the discrete point A4; the real-time gravity detection value corresponding to the discrete time point t5 (the 5th second) is 59.5 g, denoted as the discrete point A5. After obtaining the line graph, in the line graph, the line segment L1 is connected by the two end points A1 and A2, and the absolute value of the line segment slope of the line segment L1 is 0.2; the line segment L2 is connected by the two end points A2 and A3, and the absolute value of the line segment slope of the line segment L2 is 40.2; the line segment L3 is connected by the two end points A3 and A4, and the absolute value of the line segment slope of the line segment L3 is 40.4; the line segment L4 is connected by the two end points A4 and A5, and the absolute value of the line segment slope of the line segment L4 is 0.1. When the preset slope threshold is set to 1, it can be determined that the line segments L2 and L3 are the target line segments whose absolute values of the line segment slopes are greater than the preset slope threshold. The discrete point (A3) that appears twice repeatedly in the two target line segments (L2 and L3) is determined as the deviation point. After removing the deviation point, excluding the first discrete point and the last discrete point, the mean value of the remaining intermediate discrete points (i.e., A2, A4) is calculated as the gravity detection value of the detection period T. It can be understood that to determine whether the first discrete point in a detection period deviates, it is also necessary to combine the last discrete point in the previous detection period for judgment; similarly, to determine whether the last discrete point in a detection period deviates, it is also necessary to combine the first discrete point in the next detection period for judgment. Therefore, the first discrete point and the last discrete point that cannot be judged are excluded. In addition, when the detection period is longer, it can more effectively remove the deviation points, and the calculated gravity detection value is more accurate; however, if the detection period is too long, it will also cause too large a deviation between the calculated mean value and the current actual gravity detection value of the infusion container; the actual detection period is configured according to the liquid drop speed of the medicine solution.

[0066] Specifically, the detection period T can be ten seconds, and the time interval between two adjacent discrete time points is 1 s. The detection period T and the value of the interval between discrete time points can also be configured according to the actual situation. The preset slope threshold can also be set according to experience. This application only gives examples to illustrate the method here, and does not make specific limitations on the values of the detection period T, the time interval between two adjacent discrete time points, and the preset slope threshold.

[0067] Next, after obtaining the gravity detection value, the main control unit acquires the pre-configured infusion specification information, where the infusion specification information includes: the candidate empty shell weights of different models of infusion containers and the initial liquid height; a two-dimensional code is set on the infusion container, and the target model of the infusion container is obtained by scanning the two-dimensional code through an image collector, so as to correspondingly match the target empty shell weight in the candidate empty shell weights of the infusion specification information according to the target model; subtract the target empty shell weight from the gravity detection value to obtain the current peeled weight; when the current peeled weight is greater than a preset threshold, determine that the second infusion status value of the infusion container is 1; to indicate that the patient in this hospital bed has an infusion task, and there is still a relatively large amount of liquid medicine in the current infusion container, and the urgency of replacing the liquid medicine is low.

[0068] Further illustrate step S214. When the current peeled weight is equal to the preset threshold, the urgency of replacing the liquid medicine increases, and it is necessary to further finely monitor the infusion situation of the infusion container; thus, start the image collector to collect an infusion image of the corresponding infusion container suspension area; so as to more accurately determine the infusion situation based on image recognition.

[0069] Further illustrate steps S215 to S216. Specifically, the image recognition process includes: performing image preprocessing on the infusion image to obtain a target image that can be input into a pre-trained deep neural network; where the image preprocessing includes but is not limited to operations such as filtering and noise reduction, and cropping. The specific process of the image preprocessing in this application is not limited. In addition, a liquid level dividing line is shown in the target image, and the liquid level dividing line divides the infusion container area into a liquid medicine area and a non-liquid medicine area. Then, input the target image into the pre-trained deep neural network, output the position height information of the liquid level dividing line, and determine the initial liquid height through step S213; the image will be scaled, so, according to the initial liquid height, the initial liquid height in the current image, and the position height information of the liquid level dividing line, perform conversion to determine the remaining liquid medicine liquid level height. When the remaining liquid medicine liquid level height is greater than the preset height threshold of the preset dividing position, it is determined that the position of the liquid level dividing line is inside the infusion container and higher than the preset dividing position, and determine that the second infusion status value of the infusion container is 2.

[0070] Further illustrate step S217. Specifically, when the remaining liquid medicine liquid level height is not greater than the preset height threshold of the preset dividing position, it is determined that the position of the liquid level dividing line is inside the infusion container and not higher than the preset dividing position, and determine that the second infusion status value of the infusion container is 3.

[0071] Further illustrate step S218. Specifically, when the remaining liquid medicine liquid level height is equal to 0, it is determined that the position of the liquid level dividing line is not inside the infusion container, and the liquid level has dropped to the catheter or the drip chamber, and determine that the second infusion status value of the infusion container is 4.

[0072] In some embodiments, some infusion tasks are as follows: different medicinal liquids need to be input sequentially, one at a time; for example, the first bottle contains medicinal liquid A, the second bottle contains medicinal liquid B, and the third bottle contains medicinal liquid C. Usually, when the input of the last bottle of medicinal liquid is about to be completed, the nurse needs to pull out the needle, recycle the used medical devices, record the infusion situation, etc.; which takes a long time. When the input of a non-last bottle of medicinal liquid is completed, usually the nurse only needs to replace the next infusion container and adjust the flow rate; the replacement speed is fast and the time consumption is short. It is possible that the second infusion status value of the last infusion container in one infusion task is 4, and the second infusion status value of a non-last infusion container in another infusion task is also 4. Therefore, in order to more accurately distinguish the urgency among multiple infusion containers with the second infusion status value of 4 and further prompt the corresponding operations for the nurse to perform next, the present application further proposes an infusion task end warning mechanism. Specifically, the infusion task end warning mechanism is as follows: when the second infusion status value of an infusion container is 4, the two-dimensional code on the infusion container is scanned by an image collector to obtain: the infusion serial number of the infusion container with the second infusion status value of 4 in the current infusion task; when the infusion serial number indicates that the infusion container is the last infusion container, the second infusion status value is incremented by 1 to obtain a new second infusion status value of 5, indicating that the current infusion task is about to end; when the infusion serial number indicates that the infusion container is a non-last infusion container, the second infusion status value is maintained at 4, indicating that: the current infusion task has not ended and only the next infusion container needs to be replaced. In this way, the infusion task end warning mechanism is realized to remind the nurse to process the infusion task that is about to end first.

[0073] To further illustrate step S220, specifically, Example 1: If only one kind of medicinal liquid can be input to a patient in a single infusion task, then one infusion container needs to be hung, and the second infusion status value of the single infusion container is directly identified and determined as the first infusion status value corresponding to the infusion task. For example: the infusion task of Bed No. 1 corresponds to one infusion container. When the second infusion status value is identified as 1, it is determined that the first infusion status value corresponding to the infusion task of Bed No. 1 is 1.

[0074] Specifically, Example 2: When multiple kinds of medicinal liquids need to be input to a patient simultaneously in a single infusion task, that is, multiple infusion containers need to be hung simultaneously; then the second infusion status values corresponding to each infusion container are obtained simultaneously, and the maximum second infusion status value is determined as the first infusion status value corresponding to the infusion task. For example: the infusion task of Bed No. 2 requires four groups of different medicinal liquids to be input into the patient's body simultaneously, then four infusion containers are hung. Through steps S211 to S217, the second infusion status values of the four infusion containers are determined to be: 1, 2, 2, and 3 respectively. Then the maximum value of 3 is determined as the first infusion status value corresponding to the infusion task of Bed No. 2.

[0075] It can be understood that the larger the first infusion status value, the higher the urgency of changing the infusion solution for the infusion task; the smaller the second infusion status value, the lower the urgency of changing the infusion solution for the infusion task.

[0076] To further illustrate step S230, Example 3: When there are six hospital beds (i.e., A1, A2, A3, A4, A5, A6) configured in a ward A, the master control unit configured in this ward A obtains the first infusion status values corresponding to the infusion tasks of each hospital bed through steps S210 to S220: 0, 1, 2, 5, 4, 3. In the order from largest to smallest of the first infusion status values, the first infusion status values (0, 1, 2, 4, 4, 3) are concatenated in sequence to obtain the initial infusion status label corresponding to ward A as: 543210. Synchronously, each master control unit obtains the initial infusion status label of its respective ward according to this process.

[0077] To further illustrate step S240, the label length refers to the number of first infusion status values included in the initial infusion status label. The number of first infusion status values is the same as the number of hospital beds in the ward. For example, in Example 3, the initial infusion status label of ward A (configured with six hospital beds) is: 543210, and the label length is 6. Correspondingly, the label length of the initial infusion status label of a ward configured with four hospital beds is 4. In this way, it is difficult to compare the numerical values of multiple initial infusion status labels with different label lengths. Therefore, it is necessary to perform the data expansion process shown in step S250 to make the label lengths of the multiple initial infusion status labels to be compared the same.

[0078] Take an example to illustrate steps S240 to S250. Example 4: The initial infusion status label of ward A (configured with six hospital beds) is: 543210; the label length is 6; the initial infusion status label of ward E (configured with four hospital beds) is: 3210; the label length is 4; then the target length is determined to be 6. The initial infusion status label is directly determined as the ward infusion status label of ward A. Add 0 at the end of the initial infusion status label (3210) of ward E to obtain the ward infusion status label of ward E as: 321000; for the convenience of comparing between ward infusion status labels.

[0079] Through steps S210 to S250, it is possible to obtain the ward infusion status label based on the infusion status of each infusion task in the ward, thereby simply and directly reflecting the current urgency of changing the infusion solution for each infusion task in the ward, and at the same time laying a reference foundation for determining the current communication level of each master control unit subsequently.

[0080] According to some embodiments of the present application, step S110 is further described. Among them, determining the current communication level of each corresponding master control unit according to the infusion status labels of each ward includes, but is not limited to, steps S310 to S320.

[0081] Step S310: When the infusion status label of the ward is all 0, determine that the current communication level of the corresponding master control unit is the second communication level.

[0082] Step S320: When the infusion status label of the ward is not all 0, determine that the current communication level of the corresponding master control unit is the first communication level.

[0083] It can be understood that when the infusion status label of the ward is all 0, it means that there is no infusion task in the ward and there is no need to monitor the infusion in this ward; when the infusion status label of the ward is not all 0, it means that there is an infusion task in the ward and it is necessary to monitor the infusion in this ward.

[0084] Through steps S310 to S320, determine the current communication level of each master control unit according to whether there is an infusion task in each ward, so that the monitoring host can selectively communicate and connect with the master control units with monitoring requirements (i.e., the target communication objects), thereby reducing the data and connection requests that the monitoring host needs to process, which is beneficial to reducing the processing volume of the monitoring host and ensuring that the monitoring host maintains a relatively high processing performance.

[0085] According to some embodiments of the present application, step S120 is further described. Among them, determining the message sending delay of the target communication object according to the infusion status label of the ward uploaded by the target communication object includes, but is not limited to, steps S410 to S430.

[0086] Step S410: Count the quantity information of the first infusion status values with different values in the infusion status label of the ward.

[0087] Step S420: Determine the weight coefficient information according to the quantity information.

[0088] Step S430: Calculate the message sending delay according to the weight coefficient information and the preset sending delay determination formula.

[0089] The preset sending delay determination formula is: ;

[0090] Among them, is the message sending delay, is the first weight coefficient determined according to the first quantity of the first infusion status values with a value of 0, is the second weight coefficient determined according to the second quantity of the first infusion status values with a value of 1, The third weight coefficient determined according to the third quantity of the first infusion status value with a value of 2, The fourth weight coefficient determined according to the fourth quantity of the first infusion status value with a value of 3; The fifth weight coefficient determined according to the fifth quantity of the first infusion status values with values of 4 and 5; Is the maximum transmission delay; 、 、 、 、 Are preset delay values that decrease in sequence.

[0091] Specifically, Greater than or equal to The product of the quantity of the first infusion status value.

[0092] Through steps S410 to S430, according to the urgency of changing the liquid medicine for each infusion task in the ward indicated by the ward infusion status label, comprehensively considering and calculating, the message sending delay is determined. The higher the urgency of changing the liquid medicine, the smaller the message sending delay, and the higher the frequency of the main control unit uploading data messages; the lower the urgency of changing the liquid medicine, the larger the message sending delay, and the lower the frequency of the main control unit uploading data messages; thereby reducing the occurrence probability of all main control units sending data messages simultaneously, reducing data congestion and data delay, and improving the accuracy and reliability of infusion monitoring.

[0093] It can be understood that if the monitoring host polls the main control units one by one, when there are many main control units, the access cycle in one round is relatively long. When accessing other main control units, a main control unit that has been accessed previously may have a need to change the liquid medicine, and it may only be possible to access this main control unit again in the next round of access. In this way, the situation in the ward cannot be obtained in a timely manner, and the timeliness of infusion monitoring is relatively low. If all main control units generate data messages immediately and send them immediately, the data processing volume is large, and data loss may occur during the transmission process, and the accuracy and reliability of infusion monitoring are relatively low. However, in the embodiment of the present application, by comprehensively considering and calculating according to the urgency of changing the liquid medicine for each infusion task in the ward indicated by the ward infusion status label, the message sending delay is determined to control the message sending frequency of the main control unit, reducing data congestion and data delay, and improving the accuracy and reliability of infusion monitoring. Even if there may be a situation where the message sending delays determined by different main control units are the same, it can still ensure the accuracy and reliability of monitoring to a certain extent on the basis of ensuring the monitoring timeliness.

[0094] Give an example to illustrate the specific process of determining the message sending delay in the embodiment of the present application.

[0095] Example 5: Based on Example 3, the ward infusion status label corresponding to Ward A is: 543210. Count the quantity information of the first infusion status values with different values in the ward infusion status label: the first quantity of the first infusion status value with a value of 0 is 1, the second quantity of the first infusion status value with a value of 1 is 1, the third quantity of the first infusion status value with a value of 2 is 1, the fourth quantity of the first infusion status value with a value of 3 is 1, and the fifth quantity of the first infusion status value with a value of 4 is 2. Thus, the weight coefficient information is determined as: the first weight coefficient is 1, the second weight coefficient is 1, the third weight coefficient is 1, the fourth weight coefficient is 1, the fifth weight coefficient is 2. The preconfigured maximum transmission delay is 65ms; is 10ms, is 8ms, is 6ms, is 4ms, is 2ms. Substitute into the preset transmission delay determination formula for calculation to obtain: 65 - 10 * 2 - 8 - 6 - 4 - 2 = 25ms. And so on, determine the message sending delays of each target communication object.

[0096] According to some embodiments of the present application, step S130 is further described. Among them, the monitoring host determines the liquid change recommendation order information according to the ward infusion status label and the infusion status information, including but not limited to steps S410 to S430.

[0097] Step S410: The monitoring host parses the data message to obtain the ward infusion status label and the infusion status information; the infusion status information includes: the shortest remaining infusion time of each infusion container.

[0098] Step S420: Perform global sorting processing according to the order from largest to smallest of the values of the ward infusion status label to obtain the initial sorting information of the ward; the initial sorting information is used to indicate the sorting priority of the ward to be viewed; the larger the value of the ward infusion status label, the higher the sorting priority of the ward.

[0099] Step S430: When there are wards with the same priority in the initial sorting information, perform partial sorting processing on the initial sorting information according to the order from smallest to largest of the shortest remaining infusion time to obtain the second liquid change order recommendation information.

[0100] It is understood that the infusion status information includes but is not limited to: the shortest remaining infusion time of each infusion container, the latest collected infusion image, liquid flow rate and other information. It is understood that the infusion specification information can be combined with multiple infusion images collected at preset intervals to perform image recognition, detect the liquid flow rate, and estimate the shortest remaining infusion time; this application will not repeat it here.

[0101] It is understandable that the smaller the value of the ward infusion status tag is, the lower the ward's sorting priority is. In step S420, a global sorting is performed quickly based on the ward infusion status tags to quickly obtain initial sorting information.

[0102] In step S430, local sorting is performed in combination with the shortest remaining infusion time to obtain recommended fluid replacement sequence information.

[0103] Through steps S410 to S430, the embodiment of the present application can provide a reliable reference for nurses to replace the liquid medicine in an orderly manner based on the recommended information on the liquid replacement sequence, thereby improving the efficiency of the liquid replacement.

[0104] An example is given to further illustrate the sorting method implemented in steps S410 to S430.

[0105] like Figure 4 As shown, the ward infusion status label corresponding to ward A is: 543210, and the shortest remaining infusion time is 3 minutes; the ward infusion status label corresponding to ward B is: 444310, and the shortest remaining infusion time is 3 minutes; the ward infusion status label corresponding to ward C is: 443210, and the shortest remaining infusion time is 2 minutes; the ward infusion status label corresponding to ward D is: 332210, and the shortest remaining infusion time is 8 minutes; the ward infusion status label corresponding to ward E is: 321000, and the shortest remaining infusion time is 15 minutes.

[0106] The initial sorting information based on the ward infusion status label sorting is: 543210 (Ward A), 443210 (Ward C) and 444310 (Ward B) in parallel, 332210 (Ward D), and 321000 (Ward E).

[0107] Further global sorting results in: 543210 (Ward A), 443210 (Ward C), 444310 (Ward B), 332210 (Ward D), 321000 (Ward E).

[0108] like Figure 4 As shown, the present invention also provides an electronic device, including:

[0109] The processor 401 can be implemented in the form of a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit, or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0110] The memory 402 can be implemented in the form of a read-only memory, a static storage device, a dynamic storage device, or a random access memory, etc. The memory 402 can store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 402 and are called by the processor 401 to execute the infusion container fluid change monitoring method of the embodiments of the present application;

[0111] The input / output interface 403 is used to implement information input and output;

[0112] The communication interface 404 is used to implement communication interaction between this device and other devices, and can implement communication through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.);

[0113] The bus 405 transmits information between various components of the device (such as the processor 401, the memory 402, the input / output interface 403, and the communication interface 404);

[0114] Among them, the processor 401, the memory 402, the input / output interface 403, and the communication interface 404 achieve communication connections with each other inside the device through the bus 405.

[0115] The embodiments of the present application also provide a storage medium, which is a computer-readable storage medium. The storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned infusion container fluid change monitoring method is implemented.

[0116] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory may optionally include memories remotely disposed relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. The device embodiments described above are merely illustrative, where the units described as separate components may or may not be physically separated, and may be located in one place, or may also be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0117] Those of ordinary skill in the art can understand that all or some of the steps and systems disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or can be implemented as hardware, or can be implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, a communication medium generally includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.

[0118] The above is a specific description of the preferred embodiments of this application, but this application is not limited to the above embodiments. Those skilled in the art can also make various equivalent deformations or substitutions without departing from the spirit of this application, and these equivalent deformations or substitutions are all included within the scope defined by this application.

Claims

1. A method for monitoring the replacement of an infusion container, characterized in that, Applied to an infusion container liquid change monitoring system, the system includes: a monitoring host, a status monitoring module set for each hospital bed, and a main control unit set for each ward; each of the main control units is electrically connected to all the status monitoring modules in the corresponding ward; the method includes: Each of the main control units generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module; determines the current communication level of each of the corresponding main control units according to each of the ward infusion status labels; the current communication level is the first communication level or a second communication level lower than the first communication level; The monitoring host determines the main control units with the first communication level as the target communication objects, establishes a communication connection with the target communication objects; determines the main control units with the second communication level as non-target communication objects, does not establish a communication connection with the non-target communication objects; determines the message sending delay of the target communication objects according to the ward infusion status labels uploaded by the target communication objects; The target communication objects generate data messages according to the ward infusion status labels and infusion status information, and send the data messages to the monitoring host at intervals of the message sending delay, so that the monitoring host determines the liquid change recommendation order information according to the ward infusion status labels and infusion status information.

2. The method for monitoring the replacement of infusion containers according to claim 1, wherein Each of the main control units generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the ward where it is located obtained through the status monitoring module, including: Each of the main control units determines the second infusion status value of at least one infusion container corresponding to each infusion task in the ward where it is located through the status monitoring module; From the at least one second infusion status value corresponding to a single infusion task, determines the second infusion status value with the largest value as the first infusion status value corresponding to the infusion task; Each of the main control units sequentially splices the first infusion status values according to the descending order of the first infusion status values corresponding to each infusion task in the ward where it is located to obtain the initial infusion status label corresponding to the ward where it is located; Counts the label lengths of each of the initial infusion status labels, and determines the largest label length as the target length; Determines the initial infusion status label with the label length equal to the target length as the final ward infusion status label; adds 0 at the end of the initial infusion status label with the label length less than the target length to obtain the ward infusion status label with the label length equal to the target length.

3. The method for monitoring the replacement of the infusion container according to claim 2, wherein, The status monitoring module includes: a gravity sensor and an image collector; Determining the second infusion status value of at least one infusion container corresponding to each infusion task in the ward where it is located through the status monitoring module includes: Obtaining a gravity detection value through the gravity sensor; When the gravity detection value is 0, determining the second infusion status value as 0; When the gravity detection value is not 0, calculate and determine the current tare weight according to the gravity detection value. When the current tare weight is greater than a preset threshold, determine that the second infusion state value of the infusion container is 1; When the current tare weight is equal to the preset threshold, start the image collector to collect an infusion image of the corresponding infusion container suspension area; Perform image recognition processing on the infusion image to determine the position of the liquid level dividing line; when the position of the liquid level dividing line is inside the infusion container and higher than the preset dividing position, determine that the second infusion state value of the infusion container is 2; when the position of the liquid level dividing line is inside the infusion container and not higher than the preset dividing position, determine that the second infusion state value of the infusion container is 3; when the position of the liquid level dividing line is not inside the infusion container, determine that the second infusion state value of the infusion container is 4; When the infusion container with the second infusion state value of 4 is the last infusion container, add 1 to the second infusion state value to obtain a new second infusion state value of 5.

4. The method for monitoring the replacement of an infusion container according to claim 3, characterized in that, The determining the current communication level of each corresponding main control unit according to each ward infusion state label includes: When the ward infusion state label is all 0, determine that the current communication level of the corresponding main control unit is the second communication level; When the ward infusion state label is not all 0, determine that the current communication level of the corresponding main control unit is the first communication level.

5. The liquid infusion container fluid replacement monitoring method according to claim 3, characterized in that, The determining the message sending delay of the target communication object according to the ward infusion state label uploaded by the target communication object includes: Count the quantity information of the first infusion state values with different values in the ward infusion state label; Determine the weight coefficient information according to the quantity information; Calculate the message sending delay according to the weight coefficient information and a preset sending delay determination formula.

6. The method for monitoring the replacement of infusion containers according to claim 5, characterized in that, The preset transmission delay determination formula is as follows: ; Wherein, is the message sending delay; is the first weight coefficient determined according to the first quantity of the first infusion state value with a value of 0; is the second weight coefficient determined according to the second quantity of the first infusion state value with a value of 1; is the third weight coefficient determined according to the third quantity of the first infusion state value with a value of 2; is the fourth weight coefficient determined according to the fourth quantity of the first infusion state value with a value of 3; is the fifth weight coefficient determined according to the fifth quantity of the first infusion state values with values of 4 and 5; is the maximum transmission delay; , , , , are preset delay values that decrease in sequence.

7. The method for monitoring the replacement of an infusion container according to claim 5, wherein, The monitoring host determines the liquid change recommendation order information according to the ward infusion state label and the infusion state information, including: The monitoring host analyzes the data message to obtain the ward infusion state label and the infusion state information; the infusion state information includes: the shortest remaining infusion time of each infusion container; Perform global sorting processing in descending order according to the value of the ward infusion state label to obtain the initial sorting information of the ward; the initial sorting information is used to indicate the sorting priority of the ward to be viewed; the larger the value of the ward infusion state label, the higher the sorting priority of the ward; When the initial sorting information includes wards with equal priorities, perform partial sorting processing on the initial sorting information in ascending order according to the shortest remaining infusion time to obtain the liquid change recommendation order information.

8. An infusion container liquid change monitoring system, characterized in that, Including: A monitoring host, a state monitoring module provided for each hospital bed, and a main control unit provided for each ward; each main control unit is electrically connected to all the state monitoring modules in the corresponding ward; the monitoring host, the state monitoring module, and the main control unit cooperate with each other to implement the infusion container liquid change monitoring method according to any one of claims 1 to 7.

9. An electronic device, characterized in that, Comprising at least one processor and a memory for communicatively connecting with the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the infusion container fluid replacement monitoring method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to execute the infusion container fluid replacement monitoring method according to any one of claims 1 to 7.

Images