Liquid change monitoring method and system for infusion container, equipment and medium

Abstract

The invention discloses an infusion container liquid change monitoring method and system, equipment and a medium, and relates to the technical field of data processing. The method comprises the steps that each main control unit generates a ward infusion state label according to a first infusion state value corresponding to each infusion task in a ward where the main control unit is located; determining the current communication level of each corresponding main control unit according to the infusion state label of each ward; the monitoring host determines the main control unit with the first communication level as a target communication object and establishes communication connection; determining the main control unit with the second communication level as a non-target communication object, and not establishing the communication connection; determining a message sending time delay of the target communication object according to the ward infusion state label; and the target communication interval message sending time delay sends the generated data message to a monitoring host, so that the monitoring host determines liquid change recommendation sequence information according to the ward infusion state label and the infusion state information. The accuracy and reliability of infusion monitoring can be improved, and the liquid changing efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method and system, equipment, and medium for monitoring fluid replacement in an infusion container. Background Art

[0002] Patients often need infusion therapy during hospitalization, and at the same time, nurses are required to perform related care and fluid replacement. In the traditional patient infusion process, the patient or the patient's family monitors the remaining amount of liquid in the infusion container and the infusion flow rate. When the infusion is too fast or the remaining amount of liquid in the infusion container is small, the nurse is called to handle it. However, the number of nurses configured in each nurse station in the inpatient department is limited, and there are often only two to three nurses. When there are many patients and the infusion is concentrated, the workload of the nurses will increase greatly. The traditional method relies entirely on manual monitoring, and it is often discovered that the liquid in the infusion container has been infused, or there are too many people who need to change the liquid at the same time and the nurses cannot take care of each infusion in time. This can easily cause patients to experience dangerous situations such as needle slippage and blood backflow.

[0003] In the related technology, 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 dressing change information. The infusion monitoring system achieves more comprehensive and effective management. However, the construction of the entire system is relatively complex, and the accuracy of the infusion data is not high. The system delay is also relatively large. Data congestion is prone to cause data delays, 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 low. Even if infusion monitoring is adopted, there will be different call times for wards in different locations, causing nurses to go back and forth to perform fluid changes, resulting in physical waste and overdraft of nurses, and will also increase the response time of other fluid changes, reducing the efficiency of fluid changes. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes 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 recommended information of the replacement sequence, thereby improving the efficiency of the replacement.

[0005] In a first aspect, an embodiment of the present application provides an infusion container fluid replacement monitoring method, which is applied to an infusion container fluid replacement monitoring system, the system comprising: a monitoring host, a status monitoring module corresponding to each bed, and a main control unit corresponding to each ward; each of the main control units is electrically connected to all the status monitoring modules in the corresponding ward; the method comprises: Each of the main control units generates a ward infusion status tag according to the first infusion status value corresponding to each infusion task in the respective ward obtained by 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 tags; the current communication level is the first communication level, or the second communication level lower than the first communication level; 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; determines the message sending delay of the target communication object according to the ward infusion status tag uploaded by the target communication object; The target communication object generates a data message according to the ward infusion status label and infusion status information, and sends the data message to the monitoring host after a message sending delay, so that the monitoring host determines the recommended fluid replacement sequence information according to the ward infusion status label and infusion status information.

[0006] In the second aspect, an embodiment of the present application provides an infusion container fluid exchange monitoring system, comprising: a monitoring host, a status monitoring module arranged corresponding to each bed, and a main control unit arranged corresponding to each ward; each of the main control units is electrically connected to all the status monitoring modules in the corresponding ward; the monitoring host, the status monitoring module, and the main control unit cooperate with each other to implement the infusion container fluid exchange monitoring method as described in any one of the embodiments of the first aspect.

[0007] In a third aspect, an embodiment of the present application provides an electronic device comprising 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 fluid replacement monitoring method as described in any one of the embodiments of the first aspect.

[0008] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the infusion container fluid replacement monitoring method as described in any one of the embodiments of the first aspect.

[0009] The embodiments of the present application include: an infusion container fluid exchange monitoring system includes: a monitoring host, a status monitoring module corresponding to each hospital bed, and a main control unit corresponding to each ward; each main control unit is electrically connected to all status monitoring modules in the corresponding ward; in the process of using the infusion container fluid exchange monitoring system to monitor the infusion container fluid exchange, 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 respective ward obtained through the status monitoring module; the current communication level of each corresponding main control unit is determined according to the infusion status label of each ward; 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; the main control unit with the second communication level The main control unit determines it as a 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 conducive to reducing the processing volume of the monitoring host and ensuring that the monitoring host maintains a relatively efficient processing performance; the monitoring host determines the message sending delay of the target communication object according to the ward infusion status tag uploaded by the target communication object; the message sending delay is determined based on the actual ward infusion status tag, providing a reference for the target communication object to send data messages in an orderly manner, reducing the probability of all main control units sending 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 tag and 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 recommended fluid replacement sequence information according to the ward infusion status tag and infusion status information. The monitoring host can receive data messages sent by multiple target communication objects in an orderly and less conflicting manner, which is conducive 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 sequence 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 medicine in an orderly manner through the recommended information on the fluid replacement sequence, thereby improving the efficiency of fluid replacement. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] 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; Figure 2 This is a schematic diagram of the specific module composition of a status monitoring module provided by an embodiment of the present application; Figure 3 This is a schematic diagram of the steps of a method for monitoring fluid replacement in an infusion container provided by an embodiment of the present application; Figure 4 It is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0011] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0012] It should be understood that in the description of the present application, the orientation descriptions, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0013] It should be noted that although a logical order is shown in the flowchart in the description of the present application, in some cases, the steps shown or described may be performed in an order different from that in the flowchart. In the description of the present application, a number of means one or more, and a plurality of means two or more. The description of "first" and "second" is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

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

[0015] The present application provides a method for monitoring the replacement of infusion containers, a system for monitoring the replacement of infusion containers, an electronic device and a computer-readable storage medium, the method comprising: 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; the current communication level of each corresponding main control unit is determined 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; sends the generated data message to the monitoring host according to the target communication interval message sending delay, so that the monitoring host determines the recommended order information of the replacement 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 efficiency of replacement.

[0016] The embodiments of the present application are further described below in conjunction with the accompanying drawings.

[0017] like Figure 1As shown, the infusion container fluid exchange monitoring system 100 includes: a monitoring host 110, a status monitoring module 120 corresponding to each bed, and a main control unit 130 corresponding to each ward; each main control unit is electrically connected to all status monitoring modules in the corresponding ward.

[0018] Specifically, the state monitoring module 120 is used to collect gravity detection values ​​and infusion images, and provide a data analysis basis for the main control unit 130 to determine the second infusion state value of each infusion task in the respective ward. Figure 2 As shown, the state monitoring module 120 includes: a gravity sensor 121 and an image collector 122 .

[0019] Specifically, the gravity sensor 121 is arranged on the infusion stand for placing the infusion container, and is used to obtain the gravity detection value. It is understandable that when there is an infusion task with multiple groups of infusion requirements at the same time, multiple hooks can be arranged on the infusion stand, and a gravity sensor 121 is arranged on each hook, so that each gravity sensor 121 detects the gravity detection value of each infusion container respectively. Therefore, the embodiment of the present application does not impose a specific restriction on the number of gravity sensors 121 arranged on the infusion stand.

[0020] Specifically, the image collector 122 is used to be activated when the gravity detection value detected by the gravity sensor 121 is not 0, and collects the infusion image of the corresponding infusion container hanging area; it lays the data foundation for the main control unit 130 to perform image recognition to determine the position of the liquid level boundary line. It is understandable that an image collector 122 can be configured for each bed to collect the image of the infusion container hanging area. Therefore, this application does not make specific restrictions on the number, specific model, and setting position of the image collector 122.

[0021] Specifically, the main control unit 130 is used to: generate a ward infusion status label according to the first infusion status value corresponding to each infusion task in the respective ward obtained through the status monitoring module; determine 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; after being connected to the monitoring host for communication, generate a data message according to the ward infusion status label and infusion 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 infusion status label.

[0022] Specifically, the monitoring host 110 is used to: determine the main control unit 130 with a first communication level as a target communication object, and establish a communication connection with the target communication object; determine the main control unit 130 with a second communication level as a non-target communication object, and do 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 recommended fluid replacement sequence information according to the ward infusion status label and infusion status information.

[0023] The infusion container fluid replacement monitoring system 100 of the embodiment of the present application realizes the infusion container fluid replacement monitoring by the cooperation among the monitoring host 110, the status monitoring module 120, and the main 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 replace the liquid medicine in an orderly manner through the fluid replacement sequence recommendation information, thereby improving the fluid replacement efficiency.

[0024] Those skilled in the art will appreciate 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 a combination of certain components, or a different arrangement of components.

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

[0026] Those skilled in the art will appreciate that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0027] Based on the above system structure, various embodiments of the infusion container fluid replacement monitoring method of the present application are proposed below.

[0028] First, as Figure 3 As shown, the infusion container fluid replacement monitoring method can be applied to Figure 1 In the system framework shown, the infusion container fluid exchange monitoring system includes: a monitoring host, a status monitoring module corresponding to each bed, and a main control unit corresponding to each ward; each main control unit is electrically connected to all status monitoring modules in the corresponding ward; the infusion container fluid exchange monitoring method may include but is not limited to steps S110 to S130.

[0029] Step S110: Each main control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the respective ward obtained through the status monitoring module; the current communication level of each corresponding main control unit is determined according to each ward infusion status label; the current communication level is the first communication level, or the second communication level which is lower than the first communication level.

[0030] Step S120: 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; determines the message sending delay of the target communication object based on the ward infusion status tag uploaded by the target communication object.

[0031] 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 an interval message sending delay, so that the monitoring host determines the recommended fluid replacement sequence information according to the ward infusion status label and the infusion status information.

[0032] Specifically, the monitoring host and the target communication object are connected by wireless communication.

[0033] Through steps S110 to S130, in the process of monitoring the fluid exchange of infusion containers using the infusion container fluid exchange monitoring system, 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 respective ward obtained by the status monitoring module; the current communication level of each corresponding main control unit is determined 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 is conducive to reducing the processing volume of the monitoring host and ensuring that the monitoring host maintains a relatively efficient processing performance; the monitoring host determines the message sending delay of the target communication object according to the ward infusion status tag uploaded by the target communication object; the message sending delay is determined based on the actual ward infusion status tag, providing a reference for the target communication object to send data messages in an orderly manner, reducing the probability of all main control units sending 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 tag and 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 recommended fluid replacement sequence information according to the ward infusion status tag and infusion status information. The monitoring host can receive data messages sent by multiple target communication objects in an orderly and less conflicting manner, which is conducive 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 in an orderly manner based on the recommended fluid replacement sequence information, thereby improving the fluid replacement efficiency. Therefore, the embodiments of the present application can reduce data congestion and data delay, improve the accuracy and reliability of infusion monitoring, and provide nurses with a reliable reference for orderly changing of medication through recommended information on the fluid change sequence, thereby improving fluid change efficiency.

[0034] According to some embodiments of the present application, step S110 is further described, wherein each main control unit generates a ward infusion status label according to the first infusion status value corresponding to each infusion task in the respective ward obtained through the status monitoring module, including but not limited to steps S210 to S230.

[0035] Step S210: Each main control unit determines the second infusion state value of at least one infusion container corresponding to each infusion task in the respective ward through the state monitoring module.

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

[0037] Step S230: each main control unit sequentially concatenates the first infusion status values ​​corresponding to each infusion task in the ward in descending order to obtain an initial infusion status label corresponding to the ward in which it is located; Step S240: counting the label lengths of the initial infusion status labels, and determining the label length with the largest value as the target length; Step S250: determine the initial infusion status label with a label length equal to the target length as the final ward infusion status label; add 0 to the end of the initial infusion status label with a label length less than the target length to obtain the ward infusion status label with a label length equal to the target length.

[0038] It is understandable that if there are multiple patients in a ward who need infusion, there will be corresponding infusion tasks. There may be 0 or more infusion tasks. The number of infusion tasks is at most the same as the number of patients. This application does not make any specific restrictions on the number of infusion tasks in a ward.

[0039] It is understandable that the numerical length of the ward infusion status label is the same as the number of beds, and there are four in a ward.

[0040] It is understandable that in an infusion task, it may be possible that only one type of liquid medicine can be infused into the patient at a time, in which case an infusion container needs to be hung and multiple dressing changes are required; it may also be necessary to infuse multiple liquid medicines into the patient at the same time, in which case 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 change the dressings midway. Therefore, the embodiment of the present application needs to detect each infusion container involved in the infusion task separately. The embodiment of the present application does not impose specific restrictions on the number of dressing changes and infusion types involved in the infusion task.

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

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

[0043] Step S211: obtaining a gravity detection value through a gravity sensor.

[0044] Step S212: When the gravity detection value is 0, determine that the second infusion state value is 0.

[0045] Step S213: when the gravity detection value is not 0, the current tare weight is determined by calculation according to the gravity detection value, and when the current tare weight is greater than a preset threshold, the second infusion state value of the infusion container is determined to be 1.

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

[0047] Step S215: performing image recognition processing on the infusion image to determine the position of the liquid level boundary line.

[0048] Step S216: When the liquid level boundary line is located in the infusion container and is higher than the preset boundary position, the second infusion state value of the infusion container is determined to be 2.

[0049] Step S217: When the liquid level boundary line is located in the infusion container and is not higher than the preset boundary position, the second infusion state value of the infusion container is determined to be 3.

[0050] Step S218: When the liquid level boundary line is not within the infusion container, determine that the second infusion state value of the infusion container is 4.

[0051] Step S219: when the infusion container with the second infusion status value of 4 is the last infusion container, the second infusion status value is increased by 1 to obtain a new second infusion status value of 5.

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

[0053] In one embodiment, further illustrating step S212 and step S213, during the dressing change process of removing an empty infusion container and replacing an infusion container filled with liquid medicine, the gravity detection value will fluctuate and may fluctuate to 0; and when the empty infusion container is removed to directly end the infusion task, or when the infusion task is not required, the gravity detection value will be detected as 0; therefore, in order to exclude the situation where the gravity detection value fluctuates due to dressing change and accurately determine whether there is an infusion task at present, a preset fluctuation allowance time is configured. Specifically, when the gravity detection value is continuously detected as 0 within the preset fluctuation allowance time, it is determined that the second infusion state value is 0, that is, it can be determined that there is no infusion task; specifically, when the gravity detection value is continuously detected as not 0 within the preset fluctuation allowance time, it is determined that the second infusion state value is not 0, that is, it can be determined that there is an infusion task. It can be understood that the preset fluctuation allowance time can be 3 seconds, or 5 seconds, etc. Therefore, the embodiment of the present application does not impose specific restrictions on the specific value of the preset fluctuation allowance time, and can be configured according to the average single dressing change time of the nurse.

[0054] In some embodiments, when it is determined through 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 peeled weight calculated based on the gravity detection value is not greater than the preset threshold value, and then start the 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 long time from the time when the liquid is just changed to the time when the liquid level of the infusion container drops to the stage where close attention is required; if the image recognition detection is always turned on during this period, it will cause the main control unit of each ward to have a large amount of data processing, complex data processing, and high load on the main control unit. Therefore, the embodiment of the present application implements the first stage of rough detection based on monitoring the gravity detection value through steps S211 to S213; judges through step S214 that the result of the rough detection reaches the starting condition, and then starts the second stage of fine detection; and then through steps S215 to S218, image recognition processing is performed based on the infusion image to implement the second stage of fine detection; thereby reducing the data processing load of the main control unit to a certain extent.

[0055] To further explain step S213, after determining 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 be active, 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 the appearance of discrete values ​​with large deviations. 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 and determining the current tare weight based on the gravity detection value includes but is not limited to the following steps.

[0056] 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.

[0057] Take an example to further illustrate that the detection cycle T is 5 seconds, and the time interval between two adjacent discrete time points is 1 second. The real-time detection value of gravity corresponding to the discrete time point t1 (the first second) is 60g, recorded as discrete point A1; the real-time detection value of gravity corresponding to the discrete time point t2 (the second second) is 59.8g, recorded as discrete point A2; the real-time detection value of gravity corresponding to the discrete time point t3 (the third second) is 100g, recorded as discrete point A3; the real-time detection value of gravity corresponding to the discrete time point t4 (the fourth second) is 59.6g, recorded as discrete point A4; the real-time detection value of gravity corresponding to the discrete time point t5 (the fifth second) is 59.5g, recorded as discrete point A5. After obtaining the line graph, in the line graph, the line segment L1 is connected by the two endpoints 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 endpoints 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 endpoints 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 endpoints 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 target line segments whose absolute values ​​of the line segment slopes are greater than the preset slope threshold, and the discrete point (A3) that appears twice in the two target line segments (L2 and L3) is determined as a deviation point. After the deviation point is eliminated, the first discrete point and the last discrete point are excluded, and the average of the remaining intermediate discrete points (i.e., A2 and A4) is calculated as the gravity detection value of the detection period T. It is understandable that to determine whether the first discrete point in a detection cycle deviates, it is also necessary to combine it with the last discrete point in the previous detection cycle for judgment; similarly, to determine whether the last discrete point in a detection cycle deviates, it is also necessary to combine it with the first discrete point in the next detection cycle for judgment. Therefore, the first discrete point and the last discrete point that cannot be judged are excluded. In addition, when the detection cycle is longer, the deviated points can be eliminated more effectively, and the calculated gravity detection value is more accurate; but if the detection cycle is too long, it will also cause the calculated mean to deviate too much from the current actual gravity detection value of the infusion container; configure the actual detection cycle according to the test drip rate of the liquid medicine.

[0058] Specifically, the detection period T can be ten seconds, and the time interval between two adjacent discrete time points is 1 second. The detection period T and the interval between discrete time points can also be configured according to actual conditions. The preset slope threshold can also be set based on experience. This application only illustrates the method by way of example, and does not impose specific restrictions on the detection period T, the time interval between two adjacent discrete time points, and the value of the preset slope threshold.

[0059] Next, after obtaining the gravity detection value, the main control unit obtains the pre-configured infusion specification information, wherein the infusion specification information includes: candidate empty shell weights and initial liquid heights of infusion containers of different models; a QR code is provided on the infusion container, and the target model of the infusion container is obtained by scanning the QR code with an image collector, so as to match the target empty shell weight in the candidate empty shell weights of the infusion specification information according to the target model; the gravity detection value is subtracted from the target empty shell weight to obtain the current peeled weight; when the current peeled weight is greater than a preset threshold, the second infusion state value of the infusion container is determined to be 1, to indicate that the patient in the bed has an infusion task, and there is still a lot of liquid medicine in the current infusion container, and the urgency of replacing the liquid medicine is low.

[0060] Further explaining step S214, when the current tare weight is equal to the preset threshold, the urgency of replacing the medicine solution increases, and it is necessary to further monitor the infusion situation of the infusion container in detail; thereby starting the image acquisition device to capture the infusion image of the corresponding hanging area of ​​the infusion container; so as to more accurately determine the infusion situation based on image recognition.

[0061] Further explanation of step S215 to step S216, specifically, the image recognition processing includes: image preprocessing of the infusion image to obtain a target image that can be input into a pre-trained deep neural network; wherein the image preprocessing includes but is not limited to filtering, noise reduction, cropping and other operations, and the present application does not limit the specific process of image preprocessing. In addition, a liquid level dividing line is displayed in the target image, and the liquid level dividing line divides the infusion container area into a liquid medicine area and a liquid medicine-free area. Then, the target image is input into the pre-trained deep neural network, the position height information of the liquid level dividing line is output, and the initial liquid height is determined by step S213; the image will be scaled, therefore, the remaining liquid level height is determined by conversion based on the initial liquid height, the initial liquid height in the current image, and the position height information of the liquid level dividing line. When the remaining liquid level height is greater than the preset height threshold of the preset dividing position, it is judged that the liquid level dividing line position is located in the infusion container and is higher than the preset dividing position, and the second infusion state value of the infusion container is determined to be 2.

[0062] Further explaining step S217, specifically, when the height of the remaining liquid level is not greater than the preset height threshold of the preset dividing position, it is determined that the liquid surface dividing line position is located in the infusion container and is not higher than the preset dividing position, and the second infusion state value of the infusion container is determined to be 3.

[0063] Further explaining step S218, specifically, when the remaining liquid level is equal to 0, it is determined that the liquid level boundary position is not in the infusion container, the liquid level has dropped to the catheter or the drip pot, and the second infusion state value of the infusion container is determined to be 4.

[0064] In some embodiments, some infusion tasks are: different liquid medicines need to be input in sequence, one at a time; such as: the first bottle is liquid medicine A, the second bottle is liquid medicine B, and the third bottle is liquid medicine C. Usually, when the input of the last bottle of liquid medicine is about to be completed, the nurse needs to remove the needle, recycle the used medical equipment, record the infusion situation, etc.; it takes a long time. When the input of a non-last bottle of liquid medicine is completed, the nurse usually only needs to replace the next infusion container and adjust the flow rate; the replacement speed is fast and the time consumption is short. There may be an infusion task in which the second infusion status value of the last bottle of infusion container is 4, and the second infusion status value of the non-last bottle of infusion container in another infusion task is also 4. Therefore, in order to more accurately distinguish the urgency between multiple infusion containers with a second infusion status value of 4, and further prompt the nurse to perform the corresponding operation 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 state value of the infusion container is 4, the image collector scans the QR code on the infusion container to obtain: the infusion sequence number of the infusion container with the second infusion state value of 4 in the current infusion task; when the infusion sequence number indicates that the infusion container is the last infusion container, add 1 to the second infusion state value to obtain a new second infusion state value of 5, to indicate that the current infusion task is about to end; when the infusion sequence number indicates that the infusion container is not the last infusion container, maintain the second infusion state value as 4, to indicate that the current infusion task is not over, and only the next infusion container needs to be replaced. In this way, the infusion task end warning mechanism is realized to remind nurses to deal with the infusion task that is about to end first.

[0065] Step S220 is further described. Specifically, in Example 1, if a single infusion task can only infuse one kind of liquid medicine into a patient at a time, an infusion container needs to be hung, and the second infusion state value of the single infusion container is directly identified and determined as the first infusion state value corresponding to the infusion task. For example, the infusion task of bed No. 1 corresponds to an infusion container. When the second infusion state value is identified as 1, the first infusion state value corresponding to the infusion task of bed No. 1 is determined to be 1.

[0066] Specifically, Example 2: When a single infusion task requires the simultaneous infusion of multiple liquid medicines to a patient, that is, multiple infusion containers need to be hung at the same time; then the second infusion state value corresponding to each infusion container is obtained at the same time, and the second infusion state value with the largest value is determined as the first infusion state value corresponding to the infusion task. For example: The infusion task of bed No. 2 requires four groups of different liquid medicines to be simultaneously infused into the patient, and four infusion containers are hung. Through steps S211 to S217, the second infusion state values ​​of the four infusion containers are determined to be 1, 2, 2, and 3, respectively. Then the largest value 3 is determined as the first infusion state value corresponding to the infusion task of bed No. 2.

[0067] It can be understood that, the larger the first infusion status value is, the more urgent it is to replace the medicine solution of the infusion task; and the smaller the second infusion status value is, the less urgent it is to replace the medicine solution of the infusion task.

[0068] To further explain step S230, Example 3: When a ward A is equipped with six beds (i.e., A1, A2, A3, A4, A5, A6), the main control unit configured in the ward A obtains the first infusion status values ​​corresponding to the infusion tasks of each bed through steps S210 to S220: 0, 1, 2, 5, 4, 3. In the order of the first infusion status values ​​from large to small, the first infusion status values ​​(0, 1, 2, 4, 4, 3) are sequentially spliced ​​to obtain the initial infusion status label corresponding to ward A: 543210. Synchronously, each main control unit obtains the initial infusion status label of its respective ward according to this process.

[0069] To further illustrate step S240, the label length refers to: the number of first infusion status values ​​contained in the initial infusion status label. The number of first infusion status values ​​is the same as the number of beds in the ward. For example, in Example 3, the initial infusion status label of Ward A (equipped with six beds) is: 543210, and the label length is 6. Correspondingly, the label length of the initial infusion status label of the ward equipped with four beds is 4. It is difficult to perform numerical comparison on multiple initial infusion status labels with different label lengths. Therefore, the data expansion process shown in step S250 is required to make the label lengths of the multiple initial infusion status labels to be compared the same.

[0070] Take an example to illustrate steps S240 to S250. Example 4: The initial infusion status label of ward A (equipped with six beds) is: 543210; the label length is 6; the initial infusion status label of ward E (equipped with four 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 to the end of the initial infusion status label (3210) of ward E to obtain the ward infusion status label of ward E: 321000; to facilitate comparison between ward infusion status labels.

[0071] Through steps S210 to S250, the ward infusion status label can be obtained based on the infusion status of each infusion task in the ward, thereby simply and directly reflecting the current urgency of changing the medicine for each infusion task in the ward, and at the same time laying a reference foundation for the subsequent determination of the current communication level of each main control unit.

[0072] According to some embodiments of the present application, step S110 is further described, wherein the current communication level of each corresponding main control unit is determined according to the infusion status label of each ward, including but not limited to steps S310 to S320.

[0073] Step S310: When the ward infusion status tag is all 0, it is determined that the current communication level of the corresponding main control unit is the second communication level.

[0074] Step S320: When the ward infusion status tag is not all zeros, it is determined that the current communication level of the corresponding main control unit is the first communication level.

[0075] It can be understood that when the ward infusion status label 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 ward infusion status label is not all 0, it means that there is an infusion task in the ward and there is a need to monitor the infusion in this ward.

[0076] Through steps S310 to S320, the current communication level of each main control unit is determined according to whether there is an infusion task in each ward, so that the monitoring host can selectively communicate with the main control unit with monitoring requirements (i.e., the 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 efficient processing performance.

[0077] According to some embodiments of the present application, step S120 is further described, wherein the message sending delay of the target communication object is determined based on the ward infusion status tag uploaded by the target communication object, including but not limited to steps S410 to S430.

[0078] Step S410: Count the quantity information of the first infusion status values ​​with different values ​​in the ward infusion status tag.

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

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

[0081] The preset sending delay determination formula is: ; in, is the message sending delay, is a first weight coefficient determined according to the first number of first infusion state values ​​having a value of 0, is a second weight coefficient determined according to the second number of first infusion status values ​​having a value of 1, is a third weight coefficient determined according to the third number of the first infusion state value having a value of 2, is a fourth weight coefficient determined according to a fourth quantity of the first infusion state value having a value of 3; A fifth weight coefficient determined according to a fifth number of the first infusion state values ​​having a value of 4 and a value of 5; is the maximum transmission delay; , , , , The preset delay values ​​decrease in sequence.

[0082] Specifically, Greater than or equal to The product of the number of first infusion status values.

[0083] Through step S410 to step S430, the message sending delay is determined by comprehensive consideration and calculation based on the urgency of changing the medicine solution for each infusion task in the ward indicated by the ward infusion status label. The higher the urgency of changing the medicine solution, 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 medicine solution, the larger the message sending delay, and the lower the frequency of the main control unit uploading data messages; thereby reducing the probability of all main control units sending data messages at the same time, reducing data congestion and data delay, and improving the accuracy and reliability of infusion monitoring.

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

[0085] An example is given to illustrate the specific process of determining the message sending delay in an embodiment of the present application.

[0086] Example 5: Based on Example 3, the ward infusion status label corresponding to ward A is: 543210. Count the number of first infusion status values ​​with different values ​​in the ward infusion status label: the first number of first infusion status values ​​with a value of 0 is 1, the second number of first infusion status values ​​with a value of 1 is 1, the third number of first infusion status values ​​with a value of 2 is 1, the fourth number of first infusion status values ​​with a value of 3 is 1, and the fifth number of first infusion status values ​​with a value of 4 is 2. The weight coefficient information is thus determined as follows: the first weight coefficient 1, the second weight coefficient 1, the third weight coefficient 1, the fourth weight coefficient 1, the fifth weight coefficient 2. Pre-configured maximum transmission delay 65ms; 10ms, 8ms, 6ms, 4ms, 2ms. Substitute it into the preset sending delay determination formula and calculate: 65-10*2-8-6-4-2=25ms. And so on, determine the message sending delay of each target communication object.

[0087] According to some embodiments of the present application, step S130 is further described, wherein the monitoring host determines the recommended fluid replacement sequence information based on the ward infusion status label and the infusion status information, including but not limited to steps S410 to S430.

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

[0089] Step S420: Perform global sorting processing according to the value of the ward infusion status label in descending order 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.

[0090] Step S430: When the initial sorting information includes wards with the same priority, the initial sorting information is partially sorted in ascending order according to the shortest remaining infusion time to obtain the second fluid exchange sequence recommendation information.

[0091] 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.

[0092] 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.

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

[0094] 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.

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

[0096] 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.

[0097] 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).

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

[0099] like Figure 4 As shown, the present invention also provides an electronic device, including: The processor 401 may be implemented by a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit, or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application; The memory 402 may be implemented in the form of a read-only memory, a static storage device, a dynamic storage device, or a random access memory. The memory 402 may store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 402, and the processor 401 calls and executes the infusion container liquid replacement monitoring method of the embodiment of this application; Input / output interface 403, used to implement information input and output; Communication interface 404, used to realize communication interaction between the apparatus and other devices, which can be realized by wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.); A bus 405 that transmits information between various components of the device (e.g., processor 401, memory 402, input / output interface 403, and communication interface 404); The processor 401 , the memory 402 , the input / output interface 403 and the communication interface 404 are connected to each other in communication within the device via the bus 405 .

[0100] An embodiment of the present application further provides a storage medium, which is a computer-readable storage medium and stores a computer program. When the computer program is executed by a processor, the above-mentioned infusion container fluid replacement monitoring method is implemented.

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

[0102] It will be appreciated by those skilled in the art that all or some of the steps and systems in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or transient medium). As known to those skilled 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 technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0103] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions without violating the spirit of the present application. These equivalent deformations or substitutions are all included in the scope defined by the present application.

Claims

1. A method for monitoring liquid replacement in an infusion container, characterized in that: Applicable to the infusion container liquid replacement monitoring system, the system comprises: a monitoring host, a status monitoring module corresponding to each bed, and a main control unit corresponding to each ward; each main control unit is electrically connected to all the status monitoring modules in the corresponding ward; the method comprises: Each of the main control units generates a ward infusion status tag according to the first infusion status value corresponding to each infusion task in the respective ward obtained by 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 tags; the current communication level is the first communication level, or the second communication level lower than the first communication level; 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; determines the message sending delay of the target communication object according to the ward infusion status tag uploaded by the target communication object; The target communication object generates a data message according to the ward infusion status label and infusion status information, and sends the data message to the monitoring host after a message sending delay, so that the monitoring host determines the recommended fluid replacement sequence information according to the ward infusion status label and infusion status information.

2. The method for monitoring liquid replacement in an infusion container according to claim 1, characterized in that: 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 respective ward obtained by the status monitoring module, including: Each of the main control units determines, through the status monitoring module, a second infusion status value of at least one infusion container corresponding to each infusion task in the respective ward; From at least one second infusion state value corresponding to a single infusion task, determine the second infusion state value with the largest value as the first infusion state value corresponding to the infusion task; Each of the main control units sequentially concatenates the first infusion status values ​​corresponding to each of the infusion tasks in the ward in order from large to small to obtain an initial infusion status label corresponding to the respective ward; Counting the label lengths of the initial infusion state labels, and determining the label length with the largest value as the target length; The initial infusion status label whose label length is equal to the target length is determined as the final ward infusion status label; 0 is added to the end of the initial infusion status label whose label length is less than the target length to obtain the ward infusion status label whose label length is equal to the target length.

3. The method for monitoring liquid replacement in an infusion container according to claim 2, characterized in that: The state monitoring module includes: a gravity sensor and an image collector; The determining, by the state monitoring module, the second infusion state value of at least one infusion container corresponding to each infusion task in each ward includes: Acquiring a gravity detection value through the gravity sensor; When the gravity detection value is 0, determining that the second infusion state value is 0; When the gravity detection value is not 0, the current tare weight is determined by calculation according to the gravity detection value, and when the current tare weight is greater than a preset threshold, the second infusion state value of the infusion container is determined to be 1; When the current tare weight is equal to a preset threshold, the image collector is started to collect an infusion image of the corresponding infusion container hanging area; Performing 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 located in the infusion container and is higher than a preset dividing line, determining that the second infusion state value of the infusion container is 2; when the position of the liquid level dividing line is located in the infusion container and is not higher than the preset dividing line, determining that the second infusion state value of the infusion container is 3; when the position of the liquid level dividing line is not located in the infusion container, determining that the second infusion state value of the infusion container is 4; When the infusion container whose second infusion state value is 4 is the last infusion container, the second infusion state value is increased by 1 to obtain a new second infusion state value of 5.

4. The method for monitoring liquid replacement in 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 status tag includes: When the infusion status tag of the ward is all 0, determining that the current communication level of the corresponding main control unit is the second communication level; When the ward infusion status tag is not all 0, it is determined that the current communication level of the corresponding main control unit is the first communication level.

5. The method for monitoring liquid replacement in an infusion container according to claim 3, characterized in that: The determining, according to the ward infusion status tag uploaded by the target communication object, the message sending delay of the target communication object comprises: Counting the quantity information of the first infusion status values ​​with different values ​​in the infusion status tag of the ward; Determine weight coefficient information according to the quantity information; The message sending delay is calculated according to the weight coefficient information and a preset sending delay determination formula.

6. The method for monitoring liquid replacement in an infusion container according to claim 5, characterized in that: The preset sending delay determination formula is: ; in, is the message sending delay, is a first weight coefficient determined according to the first number of the first infusion state values ​​having a value of 0, is a second weight coefficient determined according to the second number of the first infusion state values ​​having a value of 1, is a third weight coefficient determined according to the third number of the first infusion state values ​​having a value of 2, is a fourth weight coefficient determined according to a fourth number of the first infusion state values ​​having a value of 3; is a fifth weight coefficient determined according to a fifth number of the first infusion status values ​​having a value of 4 and a value of 5; is the maximum transmission delay; , , , , The preset delay values ​​decrease in sequence.

7. The method for monitoring liquid replacement in an infusion container according to claim 5, characterized in that: The monitoring host determines the recommended fluid replacement sequence information according to the ward infusion status label and the infusion status information, including: The monitoring host parses the data message to obtain the ward infusion status tag and the infusion status information; the infusion status information includes: the shortest remaining infusion time of each infusion container; Performing global sorting processing according to the values ​​of the ward infusion status tags in descending order to obtain initial sorting information of the wards; 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 tag, the higher the sorting priority of the ward; When the initial sorting information includes wards with the same priority, the initial sorting information is partially sorted according to the ascending order of the shortest remaining infusion time to obtain the recommended fluid exchange sequence information.

8. An infusion container liquid replacement monitoring system, characterized in that: include: A monitoring host, a status monitoring module corresponding to each bed, and a main control unit corresponding to each ward; each main control unit is electrically connected to all the status monitoring modules in the corresponding ward; the monitoring host, the status monitoring module, and the main control unit cooperate with each other to implement the infusion container fluid replacement monitoring method as described in any one of claims 1 to 7.

9. An electronic device, characterized in that: It includes at least one processor and a memory for communicating with the at least one processor; the memory stores instructions that can be executed 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 fluid replacement monitoring method as described in 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, and the computer-executable instructions are used to enable a computer to execute the infusion container fluid replacement monitoring method according to any one of claims 1 to 7.

Images