A safe infusion dynamic monitoring method and system

Abstract

The application discloses a kind of safety infusion dynamic monitoring methods, it is related to infusion finished product monitoring technical field, comprising: in each key process node, the infusion bag is obtained infusion single information, according to infusion single information in the local / cloud configuration knowledge base matched with corresponding configuration in construction;According to the finished product validity period to and current key process node, calculate the finished product remaining validity period, according to finished product remaining validity period whether infusion bag is judged to be overtime, if overtime, then send overtime warning;If infusion start time judges infusion bag not overtime, then at infusion start time, according to infusion volume and the fastest drip speed calculate the shortest infusion length, whether infusion start time superimposes the shortest infusion length after whether exceeds finished product validity period to, if yes, then send expiration warning.The application realizes whole-process closed-loop management, dynamic intelligent early warning, improves management level and drug safety, improves efficiency and data accuracy.

Description

Technical Field

[0001] This invention relates to the field of finished infusion product monitoring technology, and in particular to a method and system for dynamic monitoring of safe infusion. Background Technology

[0002] Intravenous drug preparation centers (PIVAS) have achieved significant results in improving preparation quality and reducing contamination through centralized and professional intravenous drug preparation. However, current technologies mainly focus on quality control during the preparation process, lacking effective and systematic monitoring and management of the entire process of infusion products, from preparation and delivery to the department until the patient's infusion, particularly regarding the timeliness of drug preparation (such as stabilization time and infusion duration). In current technologies, over 50% of infusion reactions are related to prolonged storage of infusion products. There is also a gap between the standardization rate of drug instructions and actual clinical practice.

[0003] Existing infusion monitoring systems primarily focus on verifying doctor's orders and monitoring the infusion process (such as drip rate and infusion duration). While they can record the start and end times of infusion, they fail to deeply correlate with the "expiration date" of the finished product and provide proactive warnings. Furthermore, they lack analytical methods to assess the compliance between batch management in PIVAS and actual clinical execution time, making it difficult to optimize internal processes and posing potential safety risks from using finished infusion products for excessively long periods or having unreasonable infusion durations.

[0004] Therefore, a method and system for dynamic monitoring of safe intravenous infusion was developed to solve the above problems. Summary of the Invention

[0005] This invention proposes a method and system for dynamic monitoring of safe intravenous infusion to solve the problem that existing technologies cannot provide early warning of safety risks.

[0006] The present invention achieves the above objectives through the following technical solutions: This invention provides a method for dynamic monitoring of safe intravenous infusion, comprising: At each key process node, the infusion bag infusion order information is obtained. The infusion order information includes drug information, solvent information, and infusion volume. Based on the infusion order information, the corresponding configuration is matched in the built local / cloud configuration knowledge base. The configuration includes drug name, solvent name, expiration date, and fastest drip rate. The key process nodes are, in order, configuration completion time, verification time, delivery start time, department receiving time, and infusion start time. At each critical process node after the configuration completion time, the expiration date of the finished product is calculated based on the configuration completion time and the expiration date. The remaining expiration date of the finished product is calculated based on the expiration date of the finished product and the current critical process node. The remaining expiration date of the finished product is used to determine whether the infusion bag has expired. If it has expired, an expiration warning is issued. If the infusion start time indicates that the infusion bag has not expired, then at the infusion start time, the shortest infusion time is calculated based on the infusion volume and the fastest drip rate. It is then determined whether the sum of the infusion start time and the shortest infusion time exceeds the product's expiration date. If so, an expiration warning is issued.

[0007] Furthermore, the infusion record information is obtained by scanning the barcode on the infusion bag at each key process node.

[0008] Furthermore, at the infusion start time, the finished product placement time is calculated based on the infusion start time and the configuration completion time.

[0009] Furthermore, the infusion end time is obtained, and the total infusion placement time is calculated at the infusion start time. The total infusion placement time = (infusion end time - configuration completion time), or the total infusion placement time = (infusion start time - configuration completion time) + actual infusion time.

[0010] Furthermore, the system obtains or compares the actual infusion time with the preset standard infusion time, and provides alerts for cases where the infusion is too fast or too slow. The preset standard infusion time includes both the shortest and longest infusion times.

[0011] Furthermore, it also includes conducting overtime execution analysis, infusion duration exceeding limit analysis, and batch time compliance analysis, and generating analysis reports based on the analysis results of overtime execution analysis, infusion duration exceeding limit analysis, and batch time compliance analysis, specifically including: Timeout analysis is performed, including: counting monthly timeout warnings to form a monthly timeout warning trend; counting the cumulative timeout warnings for each key process node to form the timeout warning percentage for each key process node; counting the cumulative timeout warnings for each batch to form the timeout warning percentage for each batch; counting the cumulative timeout warnings for each department to form the timeout warning percentage for each department; and counting the cumulative timeout warnings for each drug to form the timeout warning percentage for each drug. Here, "batch" refers to a method used by the intravenous compounding center to classify the order of infusions. For example, the infusion time range for batch 1 is 8:00-8:59, and the infusion time range for batch 2 is 9:00-10:59. An analysis of excessive infusion time was conducted, including counting the number of cases with excessively fast / slow infusion time each month to form a monthly trend of non-compliance in actual infusion time, counting the cumulative number of cases with excessively fast / slow infusion time in each department to form the proportion of non-compliance in actual infusion time in each department, and counting the cumulative number of cases with excessively fast / slow infusion time for each drug to form the proportion of non-compliance in actual infusion time for each drug. Batch time compliance analysis is performed, including obtaining the planned execution time range for each batch, determining whether the actual infusion start time of each batch of infusion orders falls within the planned execution time range of the corresponding batch. If so, it indicates compliance; otherwise, it indicates non-compliance. The "compliance" and "non-compliance" status of each department and each batch is statistically analyzed to generate the compliance percentage for each department and each batch.

[0012] Furthermore, overtime warnings / expiration alerts, remaining shelf life of the finished product, and minimum infusion time are sent to the nurse's handheld terminal and displayed as pop-up prompts.

[0013] Furthermore, it also includes building a list of finished infusion rules, which includes drug information, approval numbers, drug names, and manufacturers for drugs in the cloud or at the hospital. It receives user edit or delete commands and performs editing or deletion operations on the list based on these commands. Editing operations include modifying or deleting drug information, approval numbers, drug names, and manufacturers; selecting drug storage methods, expiration dates, and finished product categories; and modifying or deleting dosing rate rules, which include dosage, age group, drip rate range, and duration range. Editing operations also include viewing the drug instructions. Age groups include newborns, infants, toddlers, children, adolescents, adults, and the elderly; and dosage includes both unlimited and custom settings.

[0014] Furthermore, the infusion status of each infusion bag in each department is displayed on the monitoring screen using color blocks and lists. The color blocks include green, yellow, and red. Green indicates normal, yellow indicates an expiration warning, and red indicates a timeout warning. The lists display the timeout / expiration warning, remaining shelf life of the finished product, and minimum infusion time for each infusion bag.

[0015] This invention also provides a dynamic monitoring system for safe infusion, comprising: The key process node terminal includes a static preparation PDA, a computer, and a mobile nursing PDA. The static preparation PDA is used to scan the infusion bag's infusion slip information and record the configuration completion time, verification time, and delivery start time. The computer is used to scan the infusion bag's infusion slip information and record the department's receiving time. The mobile nursing PDA is used to scan the infusion bag's infusion slip information and record the infusion start time and infusion end time. A local / cloud-based knowledge base is configured for creating, editing, reviewing, updating, and storing configurations, including drug name, solvent name, expiration date, and fastest drip rate. The hospital-side business system includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the aforementioned dynamic monitoring method for safe infusion. The data sent by the terminal at key process nodes includes infusion bag information, configuration completion time, verification time, and delivery start time sent by the static preparation PDA; infusion bag information and departmental receipt time sent by the computer; and infusion bag information, infusion start time, and infusion end time sent by the mobile nursing PDA.

[0016] Furthermore, it also includes a large monitoring screen, which is used to display the infusion status of each infusion bag in each department.

[0017] The beneficial effects of this invention are as follows: The beneficial effects of the dynamic monitoring method and system for safe intravenous infusion proposed in this invention are as follows: 1. Closed-loop management throughout the entire process: It realizes closed-loop time-efficiency monitoring of the entire process from PIVAS configuration to bedside infusion, filling the gap in safety supervision of finished infusion products in clinical use.

[0018] 2. Dynamic Intelligent Early Warning: Based on real-time data collection and rule engine calculation, it proactively issues early warnings at critical nodes, blocking potential safety hazards before execution and ensuring patient medication safety.

[0019] 3. Data-driven decision-making: Through multi-dimensional and in-depth data analysis, not only can specific safety incidents be discovered, but systemic problems can also be revealed (such as unreasonable batch planning and problems with the execution habits of specific departments). This provides a scientific and quantitative basis for PIVAS to optimize its internal allocation process and adjust batch division, thereby fundamentally improving management level and medication safety.

[0020] 4. High system coupling: Through deep integration with the hospital's existing information system, automatic data flow is achieved, eliminating the need for additional recording by medical staff, thus improving efficiency and data accuracy. Attached Figure Description

[0021] Figure 1 This is a flowchart illustrating a method for dynamic monitoring of safe intravenous infusion according to an embodiment of this application; Figure 2 This is a schematic diagram of the details page for the drug rule configuration in this embodiment of the application; Figure 3 This is a schematic diagram of the status monitoring interface of the finished infusion order list in an embodiment of this application; Figure 4 This is a schematic diagram of the interface for timeout analysis and infusion duration exceeding the limit analysis in the embodiments of this application; Figure 5 This is a schematic diagram of the interface of the monitoring screen in the embodiments of this application; Figure 6 This is a schematic diagram of the interface for batch time compliance analysis in an embodiment of this application; Figure 7 This is a schematic diagram of the details page of the finished infusion rule list in an embodiment of this application; Figure 8 This is a schematic diagram of the finished infusion rule list editing page in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0023] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0024] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0025] like Figure 1 As shown, a method for dynamic monitoring of safe intravenous infusion includes: S1: At each key process node, obtain the infusion bag infusion slip information, which includes drug information, solvent information, and infusion volume. Based on the infusion slip information, match the corresponding configuration in the built local / cloud configuration knowledge base. The configuration includes drug name, solvent name, expiration date, and fastest drip rate. The key process nodes are, in order, configuration completion time, verification time, delivery start time, department receiving time, and infusion start time. S2: At each critical process node after the configuration completion time, calculate the product's expiration date based on the configuration completion time and the expiration date, calculate the remaining expiration date of the product based on the expiration date of the product and the current critical process node, and determine whether the infusion bag has expired based on the remaining expiration date of the product. If it has expired, issue an expiration warning. S3: If the infusion start time is determined to be within the time limit for the infusion bag, then at the infusion start time, the shortest infusion time is calculated based on the infusion volume and the fastest drip rate. It is then determined whether the sum of the infusion start time and the shortest infusion time exceeds the product's expiration date. If so, an expiration warning is issued.

[0026] The system analyzes the drug list and solvent information in the infusion prescription, matches them with the local / cloud-based knowledge base, accurately finds the corresponding "drug + solvent" rule, and extracts the expiration date of the finished product and the fastest drip rate.

[0027] Fastest drip rate: The fastest permissible infusion rate for a drug or combination of drugs, measured in milliliters per minute (ml / min). Used to calculate the "shortest infusion time," the formula is: Shortest infusion time = Infusion volume (ml) / Fastest drip rate (ml / min).

[0028] The shelf life refers to the maximum stable time of the prepared infusion solution. It is derived from the drug instructions and evidence-based data on pharmaceutical stability (such as literature research and compatibility stability studies).

[0029] Configuration maintenance is a centralized, task-based review process within a local / cloud configuration knowledge base to ensure the professionalism, accuracy, and traceability of the rules. Configuration maintenance occurs within a separate management module of the local / cloud configuration knowledge base, and the main steps are as follows: Creation and Configuration: Pharmacists, based on clinical medication guidelines, set the "Shelf life (stability duration)" and "Fastest infusion rate" for each specific drug (or drug combination) and its corresponding solvent (such as 0.9% sodium chloride solution, 5% glucose injection, etc.). For example: Meropenem is dissolved in 0.9% sodium chloride solution, and the stability duration is set to 360 minutes (6 hours).

[0030] Multi-level review workflow: After a pharmacist completes a new rule or makes a modification in the knowledge base configuration, they submit it through the knowledge base configuration task function, entering the standard "submission -> standard review -> final review" review process. Only rules that pass the final review can be officially written into the knowledge base for subsequent use by hospital-side business systems.

[0031] This multi-level review workflow ensures that configuration rule changes are subject to secondary confirmation by a professional pharmacist, preventing security risks caused by single-person errors. The configuration rule base can be stored on a local server or a cloud server to form a local / cloud configuration knowledge base, facilitating knowledge sharing and continuous updates. The approved cloud configuration rule package can be downloaded and imported into the local business system (i.e., the hospital's business system) using the data export / import function to make the rules effective.

[0032] Step 1: Build a local / cloud-based knowledge base. The management interface for the local / cloud-based knowledge base includes the following functions: Rule management interface: Provides functions for displaying, querying, modifying, and deleting configured rules. Fuzzy search is supported, for example, searching for all solvent rules related to the drug name "meropenem".

[0033] View rule details: You can view the complete definition of each rule, including drug name, solvent, stabilization time, fastest drip rate, average preparation time, and you can also view the original drug instructions.

[0034] like Figure 2 The image shows the details page of the drug rule configuration in the local business system, using "meropenem" as an example. It displays the basic information and configuration rules for "meropenem". Step 2: Calculate the verification period and duration.

[0035] The formula for calculating the expiration date of finished products is: Finished product expiration date = preparation completion time + stabilization period. The finished product expiration date is the absolute boundary for determining whether the infusion has expired.

[0036] The formula for calculating the minimum permissible infusion time (i.e., the safe infusion floor) is: Shortest infusion time = infusion volume / fastest drip rate defined in the rules.

[0037] The unit for shortest infusion time is minutes, the unit for infusion volume is ml, and the unit for fastest drip rate is ml / minute. Shortest infusion time is the shortest time required to complete the infusion under the current conditions.

[0038] Calculate the remaining product's validity period until: The remaining expiration date of finished products = Expiration date of finished products - Current time. The current time is the time for each key process node, such as the review time, delivery start time, department receiving time, and infusion start time.

[0039] The formula for calculating the actual / estimated total infusion placement time is: Patient infusion placement time = infusion start time - preparation completion time.

[0040] Total infusion placement time = infusion end time - configuration completion time (or calculated as: infusion start time - configuration completion time + actual infusion time).

[0041] Step 3: Perform dynamic verification based on the verification period and duration.

[0042] The system checks if "current time > product expiration date". If true, the infusion bag has expired, and the system should issue the highest-level expiration alarm. If the calculated remaining product expiration date is negative, it indicates that the product has expired, and a timeout warning should be issued.

[0043] If the remaining expiration date of the finished product is calculated and it is determined that it has not expired and no timeout warning is issued, then at the start time of infusion, the shortest infusion time is calculated based on the infusion volume and the fastest drip rate. It is then determined whether the sum of the start time of infusion and the shortest infusion time exceeds the expiration date of the finished product. If so, an expiration warning is issued.

[0044] To issue an expiration warning and determine whether the infusion may expire during the infusion process (risk warning): At the start of the infusion, during verification, the current time plus the minimum infusion duration is calculated, and then it is determined whether this value exceeds the expiration date of the finished product. If it does, it means that even if the infusion is administered at the fastest allowed rate, the stable time may be exceeded before the end of the infusion, posing a risk. At this time, the system needs to issue an alert to remind the nurse to pay attention to the drip rate or adjust the infusion plan.

[0045] The system compares the actual infusion time with the preset standard infusion time and provides alerts if the infusion is too fast or too slow. The preset standard infusion time includes both the shortest and longest infusion times.

[0046] This also includes performing timeout analysis, infusion duration exceeding limit analysis, and batch time compliance analysis, and generating analysis reports based on the results of these analyses, specifically including: Timeout analysis is performed, including: counting monthly timeout warnings to form a monthly timeout warning trend; counting the cumulative timeout warnings for each key process node to form the timeout warning percentage for each key process node; counting the cumulative timeout warnings for each batch to form the timeout warning percentage for each batch; counting the cumulative timeout warnings for each department to form the timeout warning percentage for each department; and counting the cumulative timeout warnings for each drug to form the timeout warning percentage for each drug. Here, "batch" refers to a method used by the intravenous compounding center to classify the order of infusions. For example, the infusion time range for batch 1 is 8:00-8:59, and the infusion time range for batch 2 is 9:00-10:59. An analysis of excessive infusion time was conducted, including counting the number of cases with excessively fast / slow infusion time each month to form a monthly trend of non-compliance in actual infusion time, counting the cumulative number of cases with excessively fast / slow infusion time in each department to form the proportion of non-compliance in actual infusion time in each department, and counting the cumulative number of cases with excessively fast / slow infusion time for each drug to form the proportion of non-compliance in actual infusion time for each drug. Batch time compliance analysis is performed, including obtaining the planned execution time range for each batch, determining whether the actual infusion start time of each batch's infusion order falls within the planned execution time range of the corresponding batch. If so, it indicates compliance; otherwise, it indicates non-compliance. The "compliance" and "non-compliance" status of each department and each batch is statistically analyzed to generate the compliance percentage for each department and each batch.

[0047] Step 4: Output of calculation results and presentation of early warnings.

[0048] like Figure 3 As shown, at each critical process node, the verification interface will return the following content to the hospital's business system: The expiration date of the finished product is until (point in time). Minimum infusion time (minutes); The remaining finished product is valid until (minutes), after which it will be a negative number; The verification result includes an error alert.

[0049] Figure 2 The system displays several monitoring process records for finished infusion products. Each monitoring process record includes configuration, verification, delivery, departmental receipt, infusion start, and infusion end. The corresponding time is recorded at each node, and the completion status of the node is displayed. Each monitoring process displays the infusion order number, batch number, batch sequence, calculation result output, and early warning presentation. The calculation result output and early warning presentation include the finished product's expiration date, remaining expiration date, total infusion placement time, infusion time range, drip rate range, and whether the infusion time exceeds the standard.

[0050] like Figure 4 The chart shows the cumulative total infusion volume (calculated by the total number of infusion bags), infusion volume exceeding the time limit, and infusion volume not scanned. It also includes a monthly bar chart showing the trend of infusion volume exceeding the time limit; a pie chart showing the percentage of infusion bags exceeding the time limit (i.e., the percentage of infusion bags at each key process node), including configuration completion (configuration completion time), finished product verification (verification time), and nurse station reception (department reception time); a pie chart showing the percentage of drug stability time; a pie chart showing the percentage of batch finished product infusions exceeding the time limit; a pie chart showing the percentage of timed infusions exceeding the time limit for each clinical department; a bar chart showing the percentage of delayed drug rule executions, displaying the statistics of delayed executions for various drugs; and a monthly trend chart of unscanned infusions.

[0051] like Figure 6 As shown, the data shows the "compliance" and "non-compliance" status of each department and batch, generating pie charts and bar charts of compliance percentages for each department and batch.

[0052] like Figure 7 and Figure 8As shown, it also includes building a list of finished infusion rules. The list of finished infusion rules includes drug information, approval number, drug name, and manufacturer for drugs in the cloud or hospital. It receives user edit or delete commands and performs editing or deletion operations on the list of finished infusion rules according to the user's editing commands. Editing operations include modifying or deleting drug information, approval number, drug name, and manufacturer. Editing operations also include selecting drug storage method, expiration date, and finished product category. Editing operations also include modifying or deleting dosing rate rules. Dosing rate rules include dosage, age group, drip rate range, and duration range. Editing operations also include viewing the drug instructions. Age groups include newborns, infants, toddlers, children, adolescents, adults, and the elderly. Dosage includes two settings: unlimited and custom.

[0053] The specific maintenance content of the finished product infusion rules includes: The rules for finished infusion solutions are maintained based on the active pharmaceutical ingredient and the solvent. When the active pharmaceutical ingredient and all solvents have the same expiration date, only the active pharmaceutical ingredient needs to be maintained. For example, Meropenem for Injection + 0.9% Sodium Chloride Injection is a rule, and the storage method and expiration date are set in the rule maintenance. The system provides drug instructions, which can be viewed during maintenance. The system maintains drug administration rate rules to determine infusion duration, based on age group and dosage. Age groups include: newborns [0-28 days], infants [28-365 days], toddlers [1-3 years], children [3-12 years], adolescents [12-18 years], adults [18-65 years], and the elderly [65 years and older]. Dosage settings include [Unrestricted] and [Custom]. When maintaining the drip rate, maintenance can be performed according to both drip rate and duration. The drip rate can be set to the slowest and fastest ml / min, and the duration can be set to the shortest and longest minutes. The system requires maintaining the sources of references to provide a basis for setting up the system.

[0054] The matching rule logic is as follows: The drug and solvent are matched according to specific rules. The active pharmaceutical ingredient is matched according to its medical insurance code, and the solvent is matched according to its medical insurance product code. The solvent is not differentiated by specification or manufacturer. The result of the matching is the expiration date of the drug. For example, Meropenem for Injection + 0.9% Sodium Chloride Injection will have an expiration date of 6 hours after matching, meaning that the infusion bag must be used within 6 hours after preparation.

[0055] After the rules are matched, the dosing rate rules are matched according to age group and dosage. The drip rate range or duration range is obtained from the rate rules. When the matching is a drip rate range, the maximum infusion time is obtained by dividing the infusion bag volume by the slowest drip rate (ml / min), and the shortest infusion time is obtained by dividing the infusion bag volume by the fastest drip rate (ml / min). The infusion time used for this infusion is then used to determine whether it exceeds the limit.

[0056] This embodiment also provides a dynamic monitoring system for safe infusion, including: The key process node terminal includes a static preparation PDA, a computer, and a mobile nursing PDA. The static preparation PDA is used to scan the infusion bag's infusion slip information and record the configuration completion time, verification time, and delivery start time. The computer is used to scan the infusion bag's infusion slip information and record the department's receiving time. The mobile nursing PDA is used to scan the infusion bag's infusion slip information and record the infusion start time and infusion end time. A local / cloud-based knowledge base is configured for creating, editing, reviewing, updating, and storing configurations, including drug name, solvent name, expiration date, and fastest drip rate. The hospital-side business system includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the aforementioned dynamic monitoring method for safe infusion. Data sent by the terminal at key process nodes includes infusion bag information, configuration completion time, verification time, and delivery start time sent by the static preparation PDA; infusion bag information and departmental reception time sent by the computer; and infusion bag information, infusion start time, and infusion end time sent by the mobile nursing PDA.

[0057] The system connects with various information systems within the hospital to collect key timestamps throughout the entire lifecycle of infusion orders, either in real-time or periodically, forming a complete timeline. These nodes include at least: configuration completion time (from PIVAS, PDA, or the system); finished product verification time (from PIVAS, PDA, or the system); delivery start time (from PIVAS, PDA, or the system); departmental receipt time (from the departmental computer system); infusion start time (from mobile nursing PDA scanning); and infusion end time (from mobile nursing PDA scanning or calculation).

[0058] Clinical alerts: When a nurse scans the barcode of an IV bag using a mobile nursing PDA to prepare for infusion, the system returns the above results in real time. If the system determines that the IV bag is about to expire (remaining time is too short), may expire, or has already expired, a pop-up window or prominent marker will be displayed on the PDA screen to provide a strong reminder. Specifically, an overdue warning / expiration alert, the remaining shelf life of the product, and the minimum infusion time will be sent to the nurse's handheld terminal and displayed as a pop-up message.

[0059] The system also provides an HTTP interface service, allowing third-party systems to make external calls through the interface.

[0060] like Figure 5 As shown, the monitoring screen displays the infusion status of the entire hospital or individual departments using color blocks (green for normal, yellow for warning, and red for expired) and lists, based on the remaining expiration date of the finished products. This facilitates comprehensive monitoring and timely intervention by management personnel. The monitoring screen displays the infusion status of each infusion bag in each department using color blocks and lists. The color blocks include green, yellow, and red; green indicates normal, yellow indicates an expiration warning, and red indicates a timeout warning. The lists display the timeout warning (about to expire) / expiration warning (already expired), remaining expiration date, and minimum infusion time for each infusion bag.

[0061] Hospital-side business system: Used to download corresponding configurations from the local / cloud configuration knowledge base based on infusion order information and to receive data sent by terminals at key process nodes.

[0062] The beneficial effects of the dynamic monitoring method and system for safe intravenous infusion proposed in this invention compared with existing technologies are as follows: 1. Closed-loop management throughout the entire process: It realizes closed-loop timeliness monitoring of the entire process from PIVAS configuration to bedside infusion, filling the gap in safety supervision of finished infusion products in the clinical use process.

[0063] 2. Dynamic Intelligent Early Warning: Based on real-time data collection and rule engine calculation, it proactively issues early warnings at critical nodes, blocking potential safety hazards before execution and ensuring patient medication safety.

[0064] 3. Data-driven decision-making: Through multi-dimensional and in-depth data analysis, not only can specific safety incidents be discovered, but systemic problems can also be revealed (such as unreasonable batch planning and problems with the execution habits of specific departments). This provides a scientific and quantitative basis for PIVAS to optimize its internal allocation process and adjust batch division, thereby fundamentally improving management level and medication safety.

[0065] 4. High system coupling: Through deep integration with the hospital's existing information systems (HIS, PIVAS, mobile nursing), automatic data flow is achieved, eliminating the need for additional recording by medical staff and improving efficiency and data accuracy.

[0066] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for dynamic monitoring of safe intravenous infusion, characterized in that, include: At each key process node, the infusion bag infusion order information is obtained. The infusion order information includes drug information, solvent information, and infusion volume. Based on the infusion order information, the corresponding configuration is matched in the built local / cloud configuration knowledge base. The configuration includes drug name, solvent name, expiration date, and fastest drip rate. The key process nodes are, in order, configuration completion time, verification time, delivery start time, department receiving time, and infusion start time. At each critical process node after the configuration completion time, the expiration date of the finished product is calculated based on the configuration completion time and the expiration date. The remaining expiration date of the finished product is calculated based on the expiration date of the finished product and the current critical process node. The remaining expiration date of the finished product is used to determine whether the infusion bag has expired. If it has expired, an expiration warning is issued. If the infusion start time indicates that the infusion bag has not expired, then at the infusion start time, the shortest infusion time is calculated based on the infusion volume and the fastest drip rate. It is then determined whether the sum of the infusion start time and the shortest infusion time exceeds the product's expiration date. If so, an expiration warning is issued.

2. The method for dynamic monitoring of safe intravenous infusion according to claim 1, characterized in that, The infusion record information is obtained by scanning the barcode on the infusion bag at each key process node.

3. The method for dynamic monitoring of safe intravenous infusion according to claim 1, characterized in that, At the infusion start time, the finished product placement time is also calculated based on the infusion start time and the configuration completion time.

4. The method for dynamic monitoring of safe intravenous infusion according to claim 3, characterized in that, Obtain the infusion end time. At the infusion start time, calculate the total infusion placement time. Total infusion placement time = (infusion end time - configuration completion time), or total infusion placement time = (infusion start time - configuration completion time) + actual infusion time.

5. The method for dynamic monitoring of safe intravenous infusion according to claim 4, characterized in that, The system obtains or compares the actual infusion time with the preset standard infusion time, and provides reminders for cases where the infusion is too fast or too slow.

6. The method for dynamic monitoring of safe intravenous infusion according to claim 5, characterized in that, This also includes performing timeout analysis, infusion duration exceeding limit analysis, and batch time compliance analysis, and generating analysis reports based on the results of these analyses, specifically including: Perform timeout analysis, including counting the number of timeout warnings per month to form a monthly timeout warning trend, counting the cumulative number of timeout warnings for each key process node to form the timeout warning percentage for each key process node, counting the cumulative number of timeout warnings for each batch to form the timeout warning percentage for each batch, counting the cumulative number of timeout warnings for each department to form the timeout warning percentage for each department, and counting the cumulative number of timeout warnings for each drug to form the timeout warning percentage for each drug; An analysis of excessive infusion time was conducted, including counting the number of cases with excessively fast / slow infusion time each month to form a monthly trend of non-compliance in actual infusion time, counting the cumulative number of cases with excessively fast / slow infusion time in each department to form the proportion of non-compliance in actual infusion time in each department, and counting the cumulative number of cases with excessively fast / slow infusion time for each drug to form the proportion of non-compliance in actual infusion time for each drug. Batch time compliance analysis is performed, including obtaining the planned execution time range for each batch, determining whether the actual infusion start time of each batch of infusion orders falls within the planned execution time range of the corresponding batch. If so, it indicates compliance; otherwise, it indicates non-compliance. The "compliance" and "non-compliance" status of each department and each batch is statistically analyzed to generate the compliance percentage for each department and each batch.

7. The method for dynamic monitoring of safe intravenous infusion according to claim 1, characterized in that, The timeout / expiration warning, remaining shelf life of the finished product, and minimum infusion time will be sent to the nurse's handheld terminal and displayed as a pop-up notification.

8. The method for dynamic monitoring of safe intravenous infusion according to claim 1, characterized in that, It also includes building a list of finished infusion rules, which includes drug information, approval numbers, drug names, and manufacturers for drugs in the cloud or at the hospital. It receives user edit or delete commands and performs editing or deletion operations on the list based on these commands. Editing operations include modifying or deleting drug information, approval numbers, drug names, and manufacturers; selecting drug storage methods, expiration dates, and finished product categories; and modifying or deleting dosing rate rules, which include dosage, age group, drip rate range, and duration range. Editing operations also include viewing the drug instructions. Age groups include newborns, infants, toddlers, children, adolescents, adults, and the elderly. Dosage options include unlimited and custom settings.

9. A dynamic monitoring system for safe intravenous infusion, characterized in that, include: The key process node terminal includes a static preparation PDA, a computer, and a mobile nursing PDA. The static preparation PDA is used to scan the infusion bag's infusion slip information and record the configuration completion time, verification time, and delivery start time. The computer is used to scan the infusion bag's infusion slip information and record the department's receiving time. The mobile nursing PDA is used to scan the infusion bag's infusion slip information and record the infusion start time and infusion end time. A local / cloud-based knowledge base is configured for creating, editing, reviewing, updating, and storing configurations, including drug name, solvent name, expiration date, and fastest drip rate. The hospital-side business system includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the dynamic monitoring method for safe infusion as described in any one of claims 1-8. The data sent by the terminal at key process nodes includes infusion bag infusion slip information, configuration completion time, verification time, and delivery start time sent by the static preparation PDA; infusion bag infusion slip information and departmental reception time sent by the computer; and infusion bag infusion slip information, infusion start time, and infusion end time sent by the mobile nursing PDA.

10. A dynamic monitoring system for safe intravenous infusion according to claim 9, characterized in that, It also includes a large monitoring screen, which is used to display the infusion status of each infusion bag in each department.

Images