WO2024060090A1 - 药物输注分析方法、装置、电子设备及存储介质 - Google Patents

药物输注分析方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2024060090A1
WO2024060090A1 PCT/CN2022/120345 CN2022120345W WO2024060090A1 WO 2024060090 A1 WO2024060090 A1 WO 2024060090A1 CN 2022120345 W CN2022120345 W CN 2022120345W WO 2024060090 A1 WO2024060090 A1 WO 2024060090A1
Authority
WO
WIPO (PCT)
Prior art keywords
infusion
drug
information
analysis
pump
Prior art date
Application number
PCT/CN2022/120345
Other languages
English (en)
French (fr)
Inventor
胡铃
唐小成
唐亚洲
王祁
Original Assignee
深圳麦科田生物医疗技术股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳麦科田生物医疗技术股份有限公司 filed Critical 深圳麦科田生物医疗技术股份有限公司
Priority to CN202280004924.1A priority Critical patent/CN116097368A/zh
Priority to PCT/CN2022/120345 priority patent/WO2024060090A1/zh
Publication of WO2024060090A1 publication Critical patent/WO2024060090A1/zh

Links

Images

Classifications

    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/142—Pressure infusion, e.g. using pumps
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G16H20/17—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection

Definitions

  • the present application relates to data processing technology, and in particular to a drug infusion analysis method, device, electronic device and storage medium.
  • an infusion pump When a patient is infused or injected, an infusion pump can be used to execute the infusion order for the patient and realize automatic infusion of the drug. Medical staff need to manually input infusion parameters, such as infusion speed, on the infusion pump so that the infusion pump can infuse the drug according to the infusion parameters.
  • This application provides a drug infusion analysis method, device, electronic equipment and storage medium to improve the analysis efficiency and accuracy of drug infusion.
  • the present application provides a drug infusion analysis method, comprising:
  • the drug infusion analysis result is outputted.
  • this application provides a drug infusion analysis device, including:
  • a data acquisition module used to acquire the infusion data of the drug infusion pump within a set time interval, as well as the patient information and/or attribute information corresponding to the drug infusion pump;
  • a data analysis module configured to analyze drug infusion based on the infusion data and patient information and/or attribute information corresponding to the drug infusion pump, and obtain drug infusion analysis results;
  • the result output module is used to output the drug infusion analysis result.
  • the present application provides a drug infusion analysis system, comprising: a processor, and a memory communicatively connected to the processor;
  • the memory stores computer execution instructions
  • the processor executes computer execution instructions stored in the memory to implement the drug infusion analysis method described in the first aspect of the application.
  • the present application provides a computer-readable storage medium.
  • Computer-executable instructions are stored in the computer-readable storage medium. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect of the present application. Drug infusion analysis methods.
  • the present application provides a computer program product, which includes a computer program that, when executed by a processor, implements the drug infusion analysis method described in the first aspect of the present application.
  • This application provides a drug infusion analysis method, device, electronic equipment and storage medium.
  • the drug By acquiring the infusion data generated by the drug infusion pump within a set time interval, as well as patient information and/or attribute information, the drug can be analyzed.
  • the infusion situation is automatically analyzed to determine whether the infusion parameters set for different patients and/or different departments are reasonable, whether the infusion parameters need to be adjusted, etc., and the drug infusion analysis results are obtained.
  • Comprehensive infusion information can be obtained through infusion data, saving manpower and time, and effectively improving the efficiency and accuracy of drug infusion analysis.
  • Figure 1 is a schematic flow chart of a drug infusion analysis method provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of the data transmission process of drug infusion analysis provided by the embodiment of the present application.
  • Figure 3 is a schematic flow chart of a drug infusion analysis method provided by an embodiment of the present application.
  • Figure 4 is a schematic flow chart of a drug infusion analysis method provided by an embodiment of the present application.
  • Figure 5 is a structural block diagram of a drug infusion analysis device provided by an embodiment of the present application.
  • Figure 6 is a structural block diagram of a drug infusion analysis device provided by an embodiment of the present application.
  • FIG7 is a structural block diagram of an electronic device provided in an embodiment of the present application.
  • FIG. 8 is a structural block diagram of an electronic device provided by an embodiment of the present application.
  • Drug infusion pumps can include infusion pumps, syringe pumps, nutrition pumps and analgesic pumps, etc.
  • Medical staff need to manually input infusion parameters on the infusion pump.
  • the infusion parameters can be infusion speed, infusion time, and infusion volume. In this way, it is inevitable that incorrect infusion parameters will be entered manually, causing the patient to overdose or under-medicate, thus bringing risks to the patient.
  • DERS Dose Error Reduction System
  • DERS can determine the preset thresholds for different drug infusions related to departments or patient types by developing a departmental drug library, and burn the developed drug library into the infusion pump.
  • the infusion pump can check whether the value of the infusion parameter manually entered by the medical staff exceeds the preset threshold for drug infusion. If the threshold is exceeded, the infusion pump can remind the clinician. Confirmation of the input threshold or not allowing the input of the threshold can be required before starting the infusion.
  • the existing DERS technology uses existing experience data to formulate a drug library.
  • the infusion pump checks the values of manually entered infusion parameters according to the thresholds set by the drug library, and provides corresponding prompts to clinical users, preventing the infusion pump from Manual input errors lead to insufficient or excessive supply of drugs or liquids, solving the problem of clinical infusion dosage errors causing harm to patients.
  • manual analysis is performed later, it will be impossible to know whether the thresholds and other configurations set by the department are in line with the actual clinical situation, and the data in the clinical practice process cannot be continuously monitored, analyzed, and improved. Analysis can only be performed manually, but manual analysis requires a lot of time and manpower, and the analysis results are prone to errors. The analysis efficiency and accuracy of drug infusion are low.
  • This application provides a drug infusion analysis method, device, electronic equipment and storage medium, aiming to solve the above technical problems of the prior art.
  • Figure 1 is a schematic flowchart of a drug infusion analysis method provided according to an embodiment of the present application. The method is executed by a drug infusion analysis device. As shown in Figure 1, the method includes the following steps:
  • a drug infusion pump can be used to automatically infuse drugs to patients and monitor the patient's condition.
  • a drug infusion pump can include an infusion pump, a syringe pump, a nutrition pump, and an analgesic pump.
  • a pre-established drug library can be burned into the drug infusion pump.
  • the drug library is a configuration file of thresholds or default values of infusion parameters of different drugs related to departments or patients determined by medical staff.
  • the infusion parameters may include drug name, infusion speed, infusion volume, and infusion time.
  • the drug library may be provided with drugs that need to be infused and preset infusion speed thresholds.
  • the drug infusion pump can automatically perform infusion work through the drug library.
  • the drug infusion pump can record its own infusion situation in real time and generate an infusion log according to its own infusion situation. Its own infusion situation can be its own infusion speed and infusion volume when working.
  • the real-time infusion data and infusion log of the drug infusion pump can be obtained as the infusion data.
  • the infusion log of the drug infusion pump can be obtained periodically, for example, once a minute. After obtaining the infusion log, you can perform an analysis and conversion to convert the original format of the infusion log into another preset format and store it on the server.
  • the infusion data may include at least one of infusion information of the drug infusion pump, pump information, drug information, control information, infusion alarm information, alarm processing information, operator type, operator authority, and usage of the drug library. item.
  • the infusion information represents the corresponding infusion parameters and their corresponding values. For example, it may include one or more of the actual infusion speed, infusion volume, infusion duration, infusion time, etc.; the pump information may include drug infusion.
  • the basic information of the drug infusion pump can include one or more of the pump model, factory time and manufacturer.
  • the usage information can Including the historical usage time of the pump, etc.; drug information can include drug types and drug amounts; control information can include actions of medical staff operating on the drug infusion pump, etc.; infusion alarm information can include automatic alarms from the drug infusion pump.
  • the drug infusion pump can alarm when the infusion is abnormal, and the infusion abnormality can include Situations such as infusion obstruction and infusion being about to be completed may also include equipment abnormality.
  • equipment abnormality may be an abnormality in the pushing head.
  • the medical staff can confirm the alarm situation and relieve the conditions that caused the alarm, and then the alarm will disappear.
  • the operator type can be a medical staff, for example, a doctor or a nurse, etc.; the operator permissions are Permissions set in advance for various operators; the usage of the drug library can be whether the drug library mode is used for the current infusion, and which drug library is used.
  • the time interval is preset, and the time interval can be a time period.
  • the server can obtain the infusion log of the drug infusion pump within a preset time interval at any time. For example, it can obtain the infusion log of the drug infusion pump in the past six hours. You can also use the time period between two preset times as a time interval to obtain the infusion log of the drug infusion pump between the two preset times. For example, you can obtain the infusion log of the drug infusion pump from 9 a.m. to 2 p.m. every day. Infusion log generated between 10 o'clock. Alternatively, the infusion pump can also transmit the infusion log to the server in real time or periodically, and the server will save it. When analysis is needed, the server will obtain the stored data within the preset time interval for analysis. Of course, it can also be set according to needs, and this application does not impose restrictions.
  • the server can also obtain patient information and/or attribute information corresponding to the drug infusion pump.
  • the attribute information may include one or more of location information and infusion level.
  • the location information may be information indicating the geographical location or jurisdiction information.
  • the jurisdiction information may be information indicating the ownership of the drug infusion pump.
  • the infusion level can be divided into levels in advance.
  • the location information can be the geographical location where the drug infusion pump is located, or it can be the hospital information, department information, ward information or beds where the drug infusion pump is located, etc., or it can be other jurisdictions divided according to actual needs.
  • Patient information represents the information of the infusion object of the drug infusion pump.
  • the patient information may include at least one of patient basic information, physiological parameter information, patient alarm information, physiological alarm information, disease information, medical history, doctor's orders, and treatment history. item.
  • the patient's basic information can include personal information such as the patient's age and name, as well as basic physiological information such as the patient's height and weight;
  • physiological parameter information can include blood pressure, heart rate, ECG, blood oxygen saturation, body temperature, radiation energy, etc. Item or multiple parameter information.
  • Physiological parameter information can be obtained through equipment or pumps that monitor physiological parameters; patient alarm information refers to information about patients actively making alarms, which can include at least one of alarm type, alarm information, alarm level, etc.
  • patient alarm information can be sent by a pump, or by an independent device such as a preset mobile terminal; physiological alarm information refers to alarm information for the patient's physiological parameters, which can be monitored by electronic equipment that monitors the patient's physiological parameters. An alarm is issued when physiological parameters are abnormal.
  • the physiological alarm information may include at least one of physiological alarm type, alarm information, alarm level, etc.; the disease information may include the name of the current or historical disease, the degree of disease, and the number of patients. At least one of duration, etc.
  • Patient information can be uploaded to the server by medical staff for storage, or it can be actively acquired and/or passively received by the server.
  • the server can receive physiological alarm information generated by electronic equipment that monitors the patient's physiological parameters at any time.
  • the server can also obtain department information, which may include at least one of the name of the department where the drug infusion pump is located, the location of the department, and the personnel of the department.
  • a drug infusion pump can only work in one department at a time.
  • the medical staff can send the department information of the department where the drug infusion pump is located to the server.
  • the department information of each department can also be stored in the server in advance.
  • the medical staff sends the department where the drug infusion pump is located to the server, and the server searches for the department information corresponding to the department.
  • the association between departments and drug infusion pumps can be stored in the server in advance.
  • the drug infusion situation can be analyzed to determine the drug infusion rate of the drug infusion pump. Pay attention to whether the situation needs adjustment.
  • the infusion log can be analyzed based on the patient information to determine whether the infusion process of the patient corresponding to the patient information is reasonable; the infusion log can also be analyzed based on the department information to determine whether the infusion process in the department corresponding to the department information is reasonable.
  • Different patient information and/or attribute information can correspond to different medication analysis rules.
  • the server can match the infusion information in the infusion log with the medication analysis rules corresponding to the patient information to realize the analysis of drug infusion; it can also The infusion information in the note log is matched with the medication analysis rules corresponding to the department information to realize the analysis of drug infusion.
  • the drug infusion pump can also be pre-burned with a drug library, and the server can also be pre-stored with a drug library.
  • the drug library includes thresholds or default values of infusion parameters of different drugs related to departments or patients. Different attribute information and/or different patient information can correspond to different drug libraries. According to the attribute information and/or patient information, from Obtain the threshold or default value of the infusion parameter from the corresponding drug library.
  • the medication analysis rule may be to compare the determined threshold and default value of the infusion parameter with the actual infusion information recorded in the infusion log to obtain the medication infusion analysis result.
  • the expected value of the infusion parameter manually set during infusion is compared with the infusion parameter threshold value in the drug library sent to the infusion pump, and the corresponding infusion parameter over-limit event is given.
  • the infusion parameter over-limit event is the drug library over-limit event.
  • the medical staff actually uses the drug infusion pump for infusion the setting of the infusion parameters exceeds the preset threshold or default value of the drug library. This situation can be called a drug library over-limit event.
  • a drug library over-limit event When a drug library over-limit event occurs, an alarm may not be issued, but a prompt may pop up. For example, a status prompt may be displayed on the infusion interface to indicate that the current infusion rate exceeds the preset infusion rate threshold.
  • the infusion log can record events in which the infusion parameters exceed the limit, analyze these infusion parameter over-limit events, and the user's operating behavior after the limit is exceeded.
  • the operating behavior can include confirming the limit exceedance, modifying the parameter expected value, and not using the parameter expected value. and continuation of infusions, etc.
  • the drug library can be a standard drug infusion database set up for a certain department, a certain disease, or a certain type of patient. It can be analyzed based on the actual medication use to determine whether the drug library is reasonable.
  • the patient information includes the patient's disease information, indicating the disease the patient suffers from and the extent of the disease. Different diseases and different levels of illness may have different drug and drug dosage infusion requirements.
  • the drug library records the drugs and drug dosage thresholds and default values required for different diseases and/or different degrees of illness.
  • infusion requirements may include infusion rate defaults, infusion volume defaults, etc. After obtaining the infusion log, you can obtain information such as the name of the drug and the dose of the drug infused in the infusion log.
  • the medication analysis rules determine whether the name of the drug and the name of the drug infused are consistent with the name of the drug in the library, and whether the name of the drug infused is consistent with the drug name in the library. Whether the infused drug dose is consistent with the default value of the drug dose, thereby enabling analysis of the drug infusion situation. If the infused drugs and drug doses recorded in the infusion log are consistent with the drug names and drug dose default values in the drug library, it is determined that the drug infusion analysis result is that the infusion situation is consistent with the drug library, and there is no need to adjust the drug library.
  • the name of the drug that needs to be adjusted and the drug that needs to be adjusted can be determined based on the actual drug name and drug dose required in the infusion log. Dosage value, the name of the drug that needs to be adjusted and the drug dosage value that needs to be adjusted can be determined as the drug infusion analysis result.
  • expected measurement indicators can be obtained from multiple dimensions. For example, statistical analysis can be performed by department, drug library name, time period, pump type, pump number, patient hospitalization number, drug name, etc., to improve the flexibility of analysis. performance and accuracy. By analyzing a large number of infusion logs, specific measurement indicators can be obtained. For example, the proportion of drug libraries used by each department and the top ten drugs that cause alarm events can be obtained as drug infusion analysis results.
  • drug infusion analysis is performed based on the infusion data and the patient information and/or attribute information corresponding to the drug infusion pump, including: performing alarm event analysis based on the infusion alarm information and alarm processing information in the infusion data and the patient information and/or attribute information corresponding to the drug infusion pump; wherein the alarm event analysis includes analysis of the alarm type and/or alarm response time; performing drug usage analysis based on the infusion information and drug information in the infusion data and the patient information and/or attribute information corresponding to the drug infusion pump; wherein the drug usage analysis includes analysis of the drug usage rate and/or usage amount; performing pump usage analysis based on the pump information and control information in the infusion data and the patient information and/or attribute information corresponding to the drug infusion pump; wherein the pump usage analysis includes one or more of the infusion mode, pump type, pump usage rate, pump usage time, pump status and consumables usage analysis.
  • the infusion alarm information and alarm processing information in the infusion data as well as the patient information corresponding to the drug infusion pump, it is possible to determine the alarm types that are prone to alarms under the corresponding patient information, and the response time to the alarm. wait.
  • the patient information is a critically ill patient
  • based on the alarm processing information it can be determined that most of the alarm response times for level three alarms are 1 minute.
  • the department where the patient is located can also be determined based on the location information, and the alarm times under different departments can be analyzed. For example, the patients are all critically ill, but the alarm response time for critically ill patients in different departments may be different.
  • the use of the pump can also be analyzed based on the pump information and control information in the infusion data, as well as the patient information and/or attribute information corresponding to the drug infusion pump.
  • the infusion mode of the drug infusion pump used by different patients and/or different departments can be determined.
  • the infusion mode can include a mode using a drug library and a custom mode.
  • the custom mode can be a mode that does not use drugs. Library, a mode for customizing infusion parameters by medical staff. It can also analyze the type, usage rate, usage time, pump status and consumables of drug infusion pumps for different patients and/or different departments. Realize multi-dimensional analysis of different patient information and/or department information, and improve the accuracy and comprehensiveness of drug infusion analysis.
  • the server can output the drug infusion analysis results to the client's browser for display, for medical staff to view.
  • the drug infusion analysis results can be a CQI (continuous quality improvement, continuous quality improvement) report.
  • Medical staff can refer to the drug infusion analysis results to adjust the drug library of the drug infusion pump to improve the determination accuracy and efficiency of the drug library. .
  • Figure 2 is a schematic diagram of the data transmission process of drug infusion analysis in the embodiment of the present application.
  • the drug infusion pump can send the infusion log to the server through the wired or wireless network, and the server can output the drug infusion analysis results to the client browser through the wired or wireless network.
  • the infusion log can be collected through the network, or the infusion log can be exported through a USB flash drive.
  • the infusion log can include patient information, and patient information and department information can also be stored in the server in advance, or sent to the server through the client.
  • the drug infusion analysis results can be displayed in graphics or tables, and the drug infusion analysis results can be exported to files in the form of text or tables.
  • a drug infusion analysis method automatically analyzes the drug infusion situation by acquiring the infusion data generated by the drug infusion pump within a set time interval, as well as patient information and/or attribute information. , determine whether the infusion parameters set for different patients and/or different departments are reasonable, whether the infusion parameters need to be adjusted, etc., and obtain the drug infusion analysis results. This solves the problem of analysis errors caused by the medical staff manually checking the infusion situation of the drug infusion pump and manually analyzing the drug infusion situation in the existing technology. Comprehensive infusion information can be obtained through infusion data, saving manpower and time, and effectively improving the efficiency and accuracy of drug infusion analysis.
  • Figure 3 is a schematic flow chart of a drug infusion analysis method provided by an embodiment of the present application. This embodiment is an optional embodiment based on the above embodiment.
  • the attribute information includes the location information of the drug infusion pump; based on the infusion data and the attribute information corresponding to the drug infusion pump, the analysis of the drug infusion can be refined into: based on the infusion data and the drug
  • the position information corresponding to the infusion pump is used to analyze the use of the drug library preset in the drug infusion pump; wherein the drug library includes infusion parameters of at least one drug, and the infusion parameters include infusion speed, Fast forward one or more of dose and infusion volume.
  • the method includes the following steps:
  • this step can refer to the above-mentioned step S101, which will not be described again.
  • the location range corresponding to the location information is determined.
  • the location information may include department information, and may be the department corresponding to the department information.
  • the location information may be the department information of one or several selected departments, or it may be the location information of all departments within the hospital.
  • the drug infusion is analyzed based on the infusion data and the patient information and/or attribute information corresponding to the drug infusion pump, and the drug infusion analysis results are obtained, including: based on the infusion data, and the drug infusion
  • the department information corresponding to the pump is used to analyze the department's medication and obtain the drug infusion analysis results.
  • the location information may include department information. After determining the department information of the department where the drug infusion pump is located, a medication analysis can be performed on the infusion situation in the department corresponding to the department information based on the infusion log and department information of the drug infusion pump to determine whether the drug infusion in the department needs to be adjusted.
  • the drug library can pre-set the thresholds and default values of each infusion parameter when patients in each department undergo infusion, that is, the same infusion parameters between different departments.
  • the thresholds may be different, and the default values of the same infusion parameter may also be different between different departments.
  • the drug infusion pump can obtain the actual infusion information in real time and compare the actual infusion information with the thresholds of the infusion parameters in the drug library. If the actual infusion If the information does not meet the threshold requirements of the infusion parameters, the drug infusion pump can alarm. The time and location of the alarm, as well as the drug and department targeted by the alarm, can be recorded in the infusion log.
  • the drug library can give the default value of the infusion parameter or the threshold range of the infusion parameter.
  • the medical staff Before starting the infusion, the medical staff must set the expected value of the infusion parameter on the drug infusion pump, that is, in the actual infusion, the Expected value for infusion.
  • the drug library preset values may include default values and thresholds for infusion parameters.
  • the threshold refers to a numerical range, that is, the threshold range.
  • the threshold range can include soft upper limit, soft lower limit, hard upper limit and hard lower limit. If the expected value set by the medical staff exceeds the soft upper limit or soft lower limit, there will be a prompt message to prompt the medical staff whether to use this exceeded expected value.
  • the hard upper limit and Hard lower limits are not allowed to be exceeded.
  • the default value is not changed in most cases, it means that the preset default value is appropriate and the treatment plan is in line with the department's use. If the medical staff changes the default value, it means that the default value is inappropriate, or the infusion parameters used by the department may be different under different circumstances. If the changed expected value is not within the threshold range, for example, it often exceeds the soft upper limit, it means that the set soft upper limit value is inappropriate, and the infusion parameters of the soft upper limit can be modified to a larger value.
  • the drug library provides a threshold range for infusion parameters to prevent hospital staff from mistakenly entering values that are too small or too large when setting parameters, thereby reducing the risk of medication use.
  • the infusion log of the drug infusion pump in a certain department can be determined based on the department information. Based on the department's infusion log, the medication usage of the department was analyzed. Medication analysis rules can be pre-stored in the server. For example, the medication analysis rules can be to find the time period for each alarm from the infusion alarm information in the infusion log to determine the time period with the highest number of alarms; The number of alarms when injecting various drugs is determined, and the drug with the highest number of alarms is determined.
  • the infusion alarm information can be a drug library over-limit alarm.
  • the drug library over-limit alarm can indicate the time period in a day when over-limit events in the drug library occur, or drugs that are prone to over-limit events, etc.
  • Infusion alarms can also only count the number and/or proportion of occurrences of each alarm type within a period of time to obtain the types of frequently occurring alarms. Specifically, using the drug library model for infusion can be considered a safer way. Therefore, the number and/or proportion of infusions using the drug library can be determined for each department in the hospital. You can also count the number of drug library over-limit events by department. Drug library over-limit events refer to the infusion parameters set by medical staff exceeding the preset infusion parameter threshold in the drug library, or the infusion parameters set by medical staff. The threshold range of the infusion parameters preset in the drug library was exceeded. Understand the number of drug library over-limit events that occur in each department.
  • the threshold range of the infusion parameters is preset too small. It is also possible to determine which drug is most prone to over-limit events through the actual infused drug and the actual infusion parameters of the drug, thereby determining that the drug library setting of this drug may be inappropriate and needs improvement.
  • the distribution interval of the infusion rate set by the medical staff can also be analyzed to understand the range of the drug infusion rate set by the medical staff.
  • the server can store medication analysis rules corresponding to various infusion parameters in the infusion log, and can also store medication analysis rules corresponding to each department, which facilitates comprehensive analysis of the infusion log and obtains a complete drug infusion. Analyze the results.
  • a drug library usage analysis is performed on the drug library preset in the drug infusion pump, including: drug infusion within the location range corresponding to the position information.
  • the infusion data of the pump determines the infusion parameters of the drugs infused within the position range corresponding to the position information; the infusion parameters of the drugs infused within the position range corresponding to the position information and the infusion parameters of the drugs in the drug library , determine the drug library events within the location range corresponding to the location information; wherein the drug library events include at least one of drug library usage rate, infusion parameter over-limit events, user operation statistics after exceeding the limit, and over-limit value distribution.
  • the infusion data of the drug infusion pump within the location range corresponding to the location information is obtained.
  • the infusion log of the drug infusion pump can be obtained, and the infusion parameters of the drug can be determined from the infusion log.
  • the infusion parameters It is the actual infusion parameter set by hospital personnel during drug infusion.
  • the actual infusion parameter is the expected value of the infusion parameter manually set by medical staff.
  • the rate of drug library usage can be determined.
  • the departments using the drug library it is also possible to determine the drug library usage time interval, as well as the number and time of infusion parameter over-limit events, etc.
  • Statistics on user operations after exceeding the limit can also be made based on the operations of medical staff after the limit is exceeded.
  • the over-limit value distribution may refer to the numerical distribution range of the expected value set by medical staff.
  • the thresholds of the infusion parameters preset in the drug library may also include the infusion volume threshold of the drug, and the infusion information in the infusion log may include the actual infusion volume of the drug.
  • the drug infusion pump can obtain the actual infusion volume of each drug from the infusion data, and obtain the infusion volume threshold value of the drug corresponding to each department from the drug library. Determine whether the actual infusion volume exceeds the preset infusion volume threshold, and if so, determine that the infusion volume of the drug exceeds the limit. Alternatively, it can be determined whether the actual infusion volume exceeds the infusion volume threshold range, and if so, it is determined that the infusion volume of the drug exceeds the limit.
  • the infusion volume over-limit can be recorded in the infusion log as the drug library over-limit time, and an over-limit time alarm can also be set.
  • medication analysis is performed on the department corresponding to the department information to obtain the drug infusion analysis results, including: based on the infusion data and the corresponding department information of the drug infusion pump Based on the patient information and department information, medication analysis is performed on the departments corresponding to the department information, and the drug infusion analysis results are obtained.
  • patient information and department information can be combined.
  • the patient information of the patients in the department corresponding to the department information can be determined, and based on the patient information of each patient in the department, the degree of compatibility between the drug library in each drug infusion pump of the department and each patient can be determined.
  • the actual infusion information of the drug infusion pump for patients with the same medical history is consistent with the default value of the infusion parameter in the drug library, if not, the difference between the actual infusion information and the default value of the infusion information can be determined . That is, the drug infusion analysis results for various patient information under a department are obtained.
  • a variety of medication analysis rules can be formulated in the server for department information and patient information.
  • the medication analysis rules for different departments can be different, and the medication analysis rules corresponding to different patient information in the same department can also be different. For example, in the same department, if the patient information indicates a medical history, the medication analysis rule may be to analyze drugs whose infusion rate exceeds the limit; if the patient information indicates a treatment history, the medication analysis rule may be to analyze drugs whose infusion volume exceeds the limit.
  • the beneficial effect of this setting is that by combining patient information and department information, the infusion logs of different departments and different patient information can be analyzed, improving the accuracy of drug infusion analysis and facilitating the precise improvement of the drug library.
  • the server can send the drug infusion analysis results to the client, and the drug infusion analysis results include the results obtained by analyzing each information in the infusion log.
  • the drug infusion analysis results can be whether the drug infusion pump infuses according to the preset drug library, or which department the drug library over-limit events often occur in, etc.
  • the method further includes: based on the drug infusion analysis results, performing medication predictions on patients within the location range corresponding to the location information, obtaining medication prediction information, and outputting the medication prediction information.
  • the drug infusion analysis results may include information such as the actual infusion speed, actual infusion volume, number of alarms, alarm time, and drugs corresponding to the alarms of the drug infusion pump within the location range corresponding to the position information.
  • the medication usage situation of the location information in the future period can be predicted, the medication prediction information is obtained, and the medication prediction information is output to the client.
  • the medication prediction information can be the numerical distribution range of the actual infusion rate for medical staff to adjust according to this range. It can also count the commonly used drugs in each department and the infusion volume of various drugs used in each department, so as to predict the drugs and infusion volume that the department will prepare in the future.
  • the beneficial effect of this setting is that it can automatically predict the subsequent medication use, recommend reasonable thresholds and default values of infusion information to medical staff, avoid medical staff from artificially determining the wrong thresholds and default values of infusion parameters, and reduce the number of medical staff. Personnel workload. Based on the visual analysis results, medical staff can be guided to improve the drug library settings and improve clinical practice activities to improve the adjustment accuracy and efficiency of the drug library.
  • a drug infusion analysis method automatically analyzes the drug infusion situation by acquiring the infusion data generated by the drug infusion pump within a set time interval, as well as patient information and/or attribute information. , determine whether the infusion parameters set for different patients and/or different departments are reasonable, whether the infusion parameters need to be adjusted, etc., and obtain the drug infusion analysis results. This solves the problem of analysis errors caused by the medical staff manually checking the infusion situation of the drug infusion pump and manually analyzing the drug infusion situation in the existing technology. Comprehensive infusion information can be obtained through infusion data, saving manpower and time, and effectively improving the efficiency and accuracy of drug infusion analysis.
  • Figure 4 is a schematic flow chart of a drug infusion analysis method provided by an embodiment of the present application. This embodiment is an optional embodiment based on the above embodiment. As shown in Figure 4, the method includes the following steps:
  • this step can refer to the above-mentioned step S101, which will not be described again.
  • S402 Analyze the drug infusion according to the infusion data and the patient information corresponding to the drug infusion pump to obtain the drug infusion analysis result.
  • drug infusion analysis results for various diseases can be obtained based on the infusion data of each drug infusion pump and the disease information of each patient, or a certain disease can be selected for drug infusion analysis. For example, based on patient information, the type of disease suffered by the patient can be determined, and based on the infusion log of the drug infusion pump corresponding to the disease type, the actual drug infusion situation when treating the disease type can be determined. According to the medication analysis rules corresponding to the disease type preset in the server, the infusion situation of the disease type is analyzed to obtain the drug infusion analysis results.
  • the drug infusion is analyzed to obtain the drug infusion analysis results, including: obtaining the patient's disease information from the patient information; according to the infusion data and disease information, perform disease medication analysis, and obtain drug infusion analysis results.
  • the patient information may include disease information
  • the disease information may include the name of the disease and the degree of disease, etc., used to represent the patient's disease type.
  • Different disease information corresponds to different medication analysis rules.
  • the medication analysis rules associated with each disease information can be determined based on the preset association between the disease information and the medication analysis rules as the target medication analysis rules. . Analyze the infusion data according to the target medication analysis rules. For example, for disease A, the severity of the disease is mild, and the target medication analysis rule is to determine the drugs whose infusion rate exceeds the limit, and determine the drugs whose infusion rate exceeds the limit as drugs that need to adjust the infusion rate threshold. These can be The drug is written into the drug infusion analysis results.
  • Each drug infusion pump corresponds to infusion to a patient, and each patient corresponds to patient information. That is, one drug infusion pump corresponds to patient information.
  • the association relationship between the disease information and the medication analysis rules is set in advance, which may be the association relationship between the disease name and the medication analysis rules, or the association relationship between the disease degree and the medication analysis rules.
  • the infusion logs of various drug infusion pumps are analyzed to obtain the drugs of various drug infusion pumps.
  • Infusion analysis results The drug infusion analysis results of various drug infusion pumps are used as the drug infusion analysis results corresponding to each disease information.
  • the drug infusion pump Before sending the infusion log, the drug infusion pump can first conduct a preliminary analysis of its own infusion information. For example, it can determine the infusion speed difference, infusion volume difference and infusion rate of each drug based on the preset drug library. Note the alarm information, etc.
  • the server may also determine the infusion speed difference and the infusion volume difference according to the preset drug library after obtaining the actual infusion speed and infusion volume of the drug infusion pump.
  • the beneficial effect of this setting is that the infusion log can be analyzed in a targeted manner based on disease information, avoiding the impact of other information on the analysis, improving the efficiency and accuracy of medication analysis, and realizing the automation of medication analysis.
  • drug infusion analysis is performed based on the infusion data and the patient information corresponding to the drug infusion pump, and the drug infusion analysis results are obtained, including: obtaining the patient type from the patient information; based on the infusion data and patient type , based on the patient's disease information, perform patient medication analysis and obtain drug infusion analysis results.
  • the patient information may also include a patient type, and the patient type may be used to represent the age group of the patient.
  • the patient type may be children, young people, middle-aged people, old people, etc.
  • Values for infusion parameters such as drug infusion rate and infusion volume can differ when treating different patient types, for example, in pediatric patients, the drug may be infused in smaller volumes than in middle-aged patients. Therefore, there will be differences in the values of infusion information recorded by drug infusion pumps used by patients of different patient types.
  • the unique number of the drug infusion pump can be associated with the patient information.
  • the patient information of the patient who is using the drug infusion pump can be obtained.
  • the server can pre-store the association between each patient type and the medication analysis rules, and determine the medication analysis rules corresponding to each patient type according to the preset patient type and medication analysis rules.
  • the medication analysis rules corresponding to each patient type analyze the infusion logs corresponding to each patient type. For example, the average infusion speed of a patient type can be determined, and the average infusion speed can be written into the drug infusion analysis results. It is also possible to determine the commonly used drugs for a patient type, and write the names of the commonly used drugs into the drug infusion analysis results. It is also possible to combine the patient type and the patient's disease information to perform medication analysis on the patient.
  • the drug infusion pump is an analgesic pump, it can be determined based on the infusion data of the analgesic pump which drug treatment plan has a better analgesic effect to facilitate subsequent treatment of the patient.
  • the beneficial effect of this setting is that the infusion data can be analyzed in a targeted manner according to the patient type, avoiding the impact of other information on the analysis, improving the efficiency and accuracy of medication when treating different types of patients, and realizing the automation of medication analysis.
  • drug infusion analysis is performed based on the infusion data, and the patient information and/or attribute information corresponding to the drug infusion pump to obtain drug infusion analysis results, including: based on the infusion data, and the patient information and attribute information corresponding to the drug infusion pump, medication analysis is performed on the disease corresponding to the patient to obtain drug infusion analysis results.
  • patient information and location information can be combined. Specifically, patient information and department information can be combined. Determine the medication usage of each patient in different departments. For example, it can be determined whether the infusion rate of patients with the same disease information in different departments exceeds the infusion rate threshold. If so, it can be stated in the drug infusion analysis results that the infusion rate corresponding to the disease information needs to be adjusted.
  • the server can send the drug infusion analysis results to the client, where the drug infusion analysis results include the results obtained by analyzing each information in the infusion log.
  • the drug infusion analysis results can be whether the drug infusion pump infuses according to the preset drug library, or whether the drug infusion pump alarms most often occur during the infusion process of which disease.
  • the method further includes: performing medication prediction on the patient corresponding to the patient information based on the drug infusion analysis results, obtaining medication prediction information, and outputting the medication prediction information.
  • the drug infusion analysis results may include the actual infusion speed, actual infusion volume, number of infusion speed overruns, number of infusion volume overruns, number of alarms, alarm time, and Information such as medications corresponding to the alarm.
  • the future medication use of different patients can be predicted, the medication prediction information is obtained, and the medication prediction information is output to the client. For example, determine the drug with the most alarms and make a key prediction on the drug's use. You can calculate the average infusion rate and average infusion volume of the drug within the set interval. Based on the average infusion rate and average infusion volume, etc. , predict the future infusion rate of the drug and the possible infusion rate and infusion volume, and remind medical staff to prepare sufficient amounts of the drug for subsequent infusions.
  • the recommended value of the infusion rate threshold can be determined based on the actual infusion rate and written into the medication prediction information.
  • the recommended value of the infusion volume threshold can also be determined based on the actual infusion volume and written into the medication prediction information for reference by medical staff.
  • the beneficial effect of this setting is that it can automatically predict the subsequent medication use, recommend reasonable thresholds and default values for infusion parameters to medical staff, avoid medical staff from artificially determining the wrong thresholds and default values for infusion information, and reduce medical care.
  • the infusion parameters can include infusion speed, preset volume, fast forward volume, etc.
  • the infusion parameters can also include background flow rate, first dose, self-control volume, limit volume, etc. Based on the visual analysis results, the improvement of the drug library and clinical practice activities can be guided to improve the adjustment accuracy and efficiency of the drug library.
  • the drug infusion analysis results after outputting the drug infusion analysis results, it also includes: in response to the received drug library update instruction, obtaining the infusion parameters to be updated input by the user from the drug library update instruction; determining the infusion parameters to be updated in the drug library.
  • the infusion parameters of the drug corresponding to the updated infusion parameters are used as the current infusion parameters, and the current infusion parameters are replaced with the infusion parameters to be updated.
  • the medical staff can update the drug library based on the drug infusion analysis results.
  • the medical staff can issue a drug library update instruction on the client.
  • the drug library update instruction can include the infusion parameters to be updated and the infusion parameters to be updated. New default values and thresholds can be included. Determine the infusion parameter corresponding to the infusion parameter to be updated in the drug library, use the infusion parameter threshold and default value as the current infusion parameter in the drug library, and replace the current infusion parameter with the infusion to be updated parameters to complete the update of the drug library.
  • the drug infusion analysis results may include recommended thresholds and recommended default values of the infusion parameters, use the recommended thresholds and recommended default values as infusion parameters to be updated, and update the drug library so that the infusion parameters in the drug library are updated to new ones. thresholds and default values.
  • a drug infusion analysis method automatically analyzes the drug infusion situation by acquiring the infusion data generated by the drug infusion pump within a set time interval, as well as patient information and/or attribute information. , determine whether the infusion parameters set for different patients and/or different departments are reasonable, whether the infusion parameters need to be adjusted, etc., and obtain the drug infusion analysis results. This solves the problem of analysis errors caused by the medical staff manually checking the infusion situation of the drug infusion pump and manually analyzing the drug infusion situation in the existing technology. Comprehensive infusion information can be obtained through infusion data, saving manpower and time, and effectively improving the efficiency and accuracy of drug infusion analysis.
  • FIG. 5 is a structural block diagram of a drug infusion analysis device provided by an embodiment of the present application. For convenience of explanation, only parts related to the embodiments of the present disclosure are shown.
  • the device includes: a data acquisition module 501, a data analysis module 502 and a result output module 503.
  • the data acquisition module 501 is used to acquire the infusion data of the drug infusion pump within the set time interval, as well as the patient information and/or attribute information corresponding to the drug infusion pump;
  • the data analysis module 502 is used to analyze the drug infusion according to the infusion data and the patient information and/or attribute information corresponding to the drug infusion pump, and obtain the drug infusion analysis results;
  • the result output module 503 is used to output the drug infusion analysis results.
  • Figure 6 is a structural block diagram of a drug infusion analysis device provided by an embodiment of the present application. Based on the embodiment shown in Figure 5, as shown in Figure 6, the data analysis module 502 includes an alarm event analysis unit 5021, a drug usage Analysis unit 5022 and pump usage analysis unit 5023.
  • the alarm event analysis unit 5021 is configured to perform alarm event analysis based on the infusion alarm information and alarm processing information in the infusion data, as well as the patient information and/or attribute information corresponding to the drug infusion pump; wherein, The above alarm event analysis includes analysis of alarm type and/or alarm response time;
  • the drug usage analysis unit 5022 is used to perform drug usage analysis based on the infusion information and drug information in the infusion data, and the patient information and/or attribute information corresponding to the drug infusion pump; wherein, the drug Usage analysis includes analysis of drug usage rates and/or usage volumes;
  • the pump usage analysis unit 5023 is used to perform pump usage analysis based on the pump information and control information in the infusion data, and the patient information and/or attribute information corresponding to the drug infusion pump; wherein, the pump usage Analysis includes one or more of infusion pattern, pump type, pump usage, pump usage time, pump status, and consumable usage analysis.
  • the infusion data includes at least one of the infusion information of the drug infusion pump, pump information, drug information, control information, infusion alarm information, alarm processing information, operator type, and operator authority.
  • the patient information includes at least one of patient type, patient physical information, physiological parameter information, patient alarm information, physiological alarm information, disease information, medical history, doctor's orders, and treatment history.
  • the attribute information includes location information of a drug infusion pump
  • Data analysis module 502 includes:
  • a drug library analysis unit configured to perform a drug library usage analysis on the drug library preset in the drug infusion pump according to the infusion data and the position information corresponding to the drug infusion pump; wherein, the drug The library includes infusion parameters of at least one drug, the infusion parameters including one or more of infusion rate, fast forward dose and infusion volume.
  • the drug library analysis unit is specifically used for:
  • the infusion data of the drug infusion pump within the position range corresponding to the position information determine the infusion parameters of the drug infused within the position range corresponding to the position information
  • the infusion parameters of the medicine infused within the location range corresponding to the location information and the infusion parameters of the medicine in the medicine library determine the medicine library event within the location range corresponding to the location information; wherein, the drug library
  • the events include at least one of drug library usage rate, infusion parameter over-limit events, user operation statistics after over-limiting, and over-limit value distribution.
  • the location information includes department information
  • Data analysis module 502 is specifically used for:
  • department medication analysis is performed to obtain the drug infusion analysis results.
  • the data analysis module 502 is specifically used to:
  • disease medication analysis is performed to obtain the drug infusion analysis results.
  • the data analysis module 502 is specifically used to:
  • a patient medication analysis is performed to obtain the drug infusion analysis result.
  • the data analysis module 502 is specifically used to:
  • medication analysis is performed on the disease corresponding to the patient, and the drug infusion analysis result is obtained.
  • the device also includes:
  • the location medication prediction module is used to predict medication for patients within the location range corresponding to the location information based on the medication infusion analysis results after obtaining the medication infusion analysis results, obtain medication prediction information, and output the Medication prediction information.
  • the device also includes:
  • the patient medication prediction module is configured to perform medication prediction on the patient corresponding to the patient information based on the drug infusion analysis result after obtaining the drug infusion analysis result, obtain medication prediction information, and output the medication prediction information.
  • the device also includes:
  • a drug library update module configured to, after outputting the drug infusion analysis results, respond to the received drug library update instruction and obtain the infusion parameters to be updated input by the user from the drug library update instruction;
  • Figure 7 is a structural block diagram of an electronic device provided by an embodiment of the present application. As shown in Figure 7, the electronic device includes: a memory 71, a processor 72; the memory 71; and a memory used to store instructions executable by the processor 72.
  • the processor 72 is configured to execute the method provided in the above embodiment.
  • the electronic device also includes a receiver 73 and a transmitter 74 .
  • the receiver 73 is used to receive instructions and data sent by other devices, and the transmitter 74 is used to send instructions and data to external devices.
  • Figure 8 is a block diagram of an electronic device according to an exemplary embodiment.
  • the device may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital device. Assistant etc.
  • Device 800 may include one or more of the following components: processing component 802 , memory 804 , power supply component 806 , multimedia component 808 , audio component 810 , input/output (I/O) interface 812 , sensor component 814 , and communications component 816 .
  • Processing component 802 generally controls the overall operations of device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method.
  • processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components.
  • processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operations at device 800 . Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory, magnetic or optical disk.
  • Power supply component 806 provides power to the various components of device 800 .
  • Power supply components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 800 .
  • Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action.
  • multimedia component 808 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • the audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 804 or sent via the communication component 816.
  • the audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • Sensor component 814 includes one or more sensors that provide various aspects of status assessment for device 800 .
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor component 814 can also detect a change in position of the device 800 or a component of the device 800. , the presence or absence of user contact with device 800 , device 800 orientation or acceleration/deceleration and temperature changes of device 800 .
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communications between device 800 and other devices.
  • Device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 800 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable Gate array
  • controller microcontroller, microprocessor or other electronic components are implemented for executing the above method.
  • a non-transitory computer-readable storage medium including instructions such as a memory 804 including instructions, which are executable by the processor 820 of the device 800 to complete the above method is also provided.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • a non-transitory computer-readable storage medium when instructions in the storage medium are executed by a processor of a terminal device, enable the terminal device to execute the above-mentioned drug infusion analysis method of the terminal device.
  • This application also discloses a computer program product, which includes a computer program that implements the method described in this embodiment when executed by a processor.
  • Various implementations of the systems and techniques described above may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip implemented in a system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or a combination thereof.
  • FPGAs field programmable gate arrays
  • ASICs application specific integrated circuits
  • ASSPs application specific standard products
  • SOC system
  • CPLD load programmable logic device
  • computer hardware firmware, software, and/or a combination thereof.
  • These various embodiments may include implementation in one or more computer programs executable and/or interpreted on a programmable system including at least one programmable processor, the programmable processor
  • the processor which may be a special purpose or general purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
  • An output device may be a special purpose or general purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
  • An output device may be a special purpose or general purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
  • Program code for implementing the methods of the present application may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that the program codes, when executed by the processor or controller, cause the functions specified in the flowcharts and/or block diagrams/ The operation is implemented.
  • the program code may execute entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine or entirely on the remote machine or electronic device.
  • a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing.
  • machine-readable storage media would include one or more wire-based electrical connections, laptop disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash memory erasable programmable read only memory
  • CD-ROM portable compact disk read-only memory
  • magnetic storage device or any suitable combination of the above.
  • the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or a trackball) through which a user can provide input to the computer.
  • a display device eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • a keyboard and pointing device eg, a mouse or a trackball
  • Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and may be provided in any form, including Acoustic input, voice input or tactile input) to receive input from the user.
  • the systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data electronics device), or a computing system that includes middleware components (e.g., an application electronics device), or a computing system that includes a front-end component (e.g., as a data electronics device).
  • back-end components e.g., as a data electronics device
  • middleware components e.g., an application electronics device
  • a front-end component e.g., as a data electronics device.
  • a user computer having a graphical user interface or a web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system.
  • the components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.
  • LAN local area network
  • Computer systems may include clients and electronic devices. Clients and electronic devices are generally remote from each other and typically interact through a communications network. The relationship of client and electronic device is created by computer programs running on respective computers and having a client-electronic device relationship with each other.
  • Electronic equipment can be cloud electronic equipment, also known as cloud computing electronic equipment or cloud host. It is a host product in the cloud computing service system to solve the problem of traditional physical host and VPS service ("Virtual Private Server", or "Virtual Private Server” for short) VPS”) has the disadvantages of difficult management and weak business scalability.
  • the electronic device can also be an electronic device of a distributed system, or an electronic device combined with a blockchain.

Abstract

一种药物输注分析方法、装置、电子设备及存储介质。该方法包括：获取设定时间区间内药物输注泵的输注数据（S101），以及药物输注泵对应的患者信息和/或属性信息；根据输注数据，以及药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果（S102）；输出药物输注分析结果（S103）。通过获取药物输注泵的输注数据，对药物的输注情况进行自动分析，得到分析结果，提高药物输注的分析效率和精度，便于用户对药物的输注情况进行调整，改进药物输注过程，实现药物输注的安全、可靠性。

Description

药物输注分析方法、装置、电子设备及存储介质 技术领域
本申请涉及数据处理技术，尤其涉及一种药物输注分析方法、装置、电子设备及存储介质。
背景技术
在对病人进行输液或注射时，可以使用药物的输注泵给病人执行输注医嘱，实现药物的自动输注。医护人员需要在输注泵上手动输入输液参数，比如输注速度，使输注泵按照输注参数进行药物的输注。
在输注泵工作时，医护人员需要人工查看输注泵的工作情况，确定输注泵是否正常工作，并根据实际输注情况调整输注参数。但是，这种人工分析的方式容易导致对药物输注的分析出现错误，不能及时识别风险，从而带来病人的用药风险。
发明内容
本申请提供一种药物输注分析方法、装置、电子设备及存储介质，用以提高药物输注的分析效率和精度。
第一方面，本申请提供一种药物输注分析方法，包括：
获取设定时间区间内药物输注泵的输注数据，以及所述药物输注泵对应的患者信息和/或属性信息；
根据所述输注数据，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果；
输出所述药物输注分析结果。
第二方面，本申请提供一种药物输注分析装置，包括：
数据获取模块，用于获取设定时间区间内药物输注泵的输注数据，以及所述药物输注泵对应的患者信息和/或属性信息；
数据分析模块，用于根据所述输注数据，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果；
结果输出模块，用于输出所述药物输注分析结果。
第三方面，本申请提供一种药物输注分析系统，包括：处理器，以及与所述处理器通信连接的存储器；
所述存储器存储计算机执行指令；
所述处理器执行所述存储器存储的计算机执行指令，以实现如本申请第一方面所述的药物输注分析方法。
第四方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机执行指令，所述计算机执行指令被处理器执行时用于实现如本申请第一方面所述的 药物输注分析方法。
第五方面，本申请提供一种计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现如本申请第一方面所述的药物输注分析方法。
本申请提供的一种药物输注分析方法、装置、电子设备及存储介质，通过获取药物输注泵在设定时间区间内产生的输注数据，以及患者信息和/或属性信息，对药物的输注情况进行自动分析，确定针对不同患者和/或不同科室所设定的输注参数是否合理，是否需要调整输注参数等，得到药物输注分析结果。解决了现有技术中，由医护人员人工查看药物输注泵的输注情况，并人工对药物输注情况进行分析，所造成的分析错误的问题。通过输注数据可以获取全面的输注信息，节约人力和时间，有效提高药物输注分析的效率和精度。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。
图1为本申请实施例提供的一种药物输注分析方法的流程示意图；
图2为本申请实施例提供的药物输注分析的数据传输过程示意图；
图3为本申请实施例提供的一种药物输注分析方法的流程示意图；
图4为本申请实施例提供的一种药物输注分析方法的流程示意图；
图5为本申请实施例提供的一种药物输注分析装置的结构框图；
图6为本申请实施例提供的一种药物输注分析装置的结构框图；
图7为本申请实施例提供的一种电子设备的结构框图；
图8为本申请实施例提供的一种电子设备的结构框图。
通过上述附图，已示出本申请明确的实施例，后文中将有更详细的描述。这些附图和文字描述并不是为了通过任何方式限制本申请构思的范围，而是通过参考特定实施例为本领域技术人员说明本申请的概念。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例方式作进一步地详细描述。
应当明确，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请的描述中，需要理解的是，术语“第一”、“第二”、“第三”等仅用于区别类似的对象，而不必用于描述特定的顺序或先后次序，也不能理解为指示或暗示相对重要性。对于本领域的普通技术人员而言，可以根据具体情况理解上述术语在本申请中的具体含义。此外，在本申请的描述中，除非另有说明，“多个”是指两个或两个以上。“和/或”， 描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
需要注意的是，由于篇幅所限，本申请说明书没有穷举所有可选的实施方式，本领域技术人员在阅读本申请说明书后，应该能够想到，只要技术特征不互相矛盾，那么技术特征的任意组合均可以构成可选的实施方式。下面对各实施例进行详细说明。
在临床上，医护人员可以使用药物的输注泵给病人执行输液医嘱，药物的输注泵可以包括输液泵、注射泵、营养泵和镇痛泵等。医护人员需要在输注泵上手动输入输液参数，例如，输液参数可以是输注速度、输注时间和输注量等。这样不可避免的存在手动输入错误的输注参数，使病人用药过量或不足，从而带来病人的用药风险。
目前，药物输注泵可以通过集成DERS(Dose Error Reduction System，剂量误差减小系统)来减少手动输入输注参数所造成的病人用药安全风险。DERS可以通过制定科室药物库，确定与科室或病人类型等相关的不同药物输注预设阈值，并将制定的药物库烧录到输注泵中。输注泵可以检查医护人员手动输入的输注参数的值是否超出药物输注预设阈值，如果超出阈值，输注泵可以提醒临床医生。可以在开始输液之前要求确认输入的阈值或不允许输入阈值。
但是，现有的DERS技术，是利用已有经验数据制定出药物库，输注泵根据药物库制定的阈值对手动输入的输注参数的值进行检查，对临床用户进行相应提示，防止输液泵手动输入错误而导致药物或液体供应不足或过量，解决临床上输注剂量使用错误而造成对患者的伤害的问题。后续除非人工主动分析，否则无法知道科室制定的阈值及其他配置是否符合临床实际情况，不能对临床实践过程中的数据进行持续监控、分析和改进。只能人为进行分析，但是人为分析需要消费大量的时间和人力，且分析结果容易出现错误，药物输注的分析效率和精度较低。
本申请提供的一种药物输注分析方法、装置、电子设备及存储介质，旨在解决现有技术的如上技术问题。
下面以具体地实施例对本申请的技术方案以及本申请的技术方案如何解决上述技术问题进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。下面将结合附图，对本申请的实施例进行描述。
图1是根据本申请实施例提供的一种药物输注分析方法的流程示意图，该方法由一种药物输注分析装置执行。如图1所示，该方法包括以下步骤：
S101、获取设定时间区间内药物输注泵的输注数据，以及药物输注泵对应的患者信息和/或属性信息。
示例性地，药物输注泵可以用于为患者自动输注药物，监控患者的情况，例如，药物输注泵可以包括输液泵、注射泵、营养泵和镇痛泵等。药物输注泵中可以烧录有预先制定的药物库，药物库是由医护人员确定的，与科室或患者相关的不同药物的输注参数的阈值或默认值的配置文件，输注参数可以包括药物名称、输注速度、输注量和输注时间等。例如，药物库中可以设置有需要被输注的药物和预设的输注速度阈值等。药物输注泵可以通过药物库自动进行输注工作。且药物输注泵可以实时记录自身的输注情况，根据自身的输注情况生成输注日志。自身的输注情况可以是自身在工作时的输注速度和输注量等。
可以获取药物输注泵的实时输注数据和输注日志等作为输注数据，获取药物输注泵的输注日志可以是定期获取的，比如一分钟获取一次。获得输注日志后，可以进过一次分析转换，将输注日志的原格式转换为另外一个预设格式的数据存储在服务器上。
输注数据可以包括药物输注泵的输注信息、泵信息、药物信息、操控信息、输注报警信息、报警处理信息、操作人员类型、操作人员权限和药物库的使用情况等中的至少一项。输注信息表示相应输注参数及其对应的数值，例如，可以包括实际的输注速度、输注量、输注时长和输注时间等中的一项或多项；泵信息可以包括药物输注泵的基本信息、使用信息和耗材信息等中的一项或多项，药物输注泵的基本信息可以包括泵的型号、出厂时间和生产商等中的一项或多项，使用信息可以包括泵的历史使用时间等；药物信息可以包括药物种类和药物量等；操控信息可以包括医护人员在药物输注泵上进行操作的动作等；输注报警信息可以包括药物输注泵进行自动报警的时间以及报警时正在输注的药物、报警时药物输注泵所在的科室和报警时进行输注的患者等，例如，药物输注泵可以在输注异常时进行报警，输注异常可以包括输注阻塞和输注即将完成等情况，也可以包括设备异常的情况，例如设备异常可以是推头异常。当出现报警后，可以停止泵输注，医护人员可以确认报警情况并解除报警产生的条件，然后报警会消失；操作人员类型可以是医护人员，例如，可以是医生或护士等；操作人员权限为预先为各类操作人员设置的权限；药物库的使用情况可以是当次输注是否使用了药物库模式，以及使用的是哪个药物库。
预先设定时间区间，时间区间可以是一个时间段。服务器可以随时获取药物输注泵在预设时间区间内的输注日志，例如，可以获取药物输注泵在过去六个小时内的输注日志。也可以将预设两个时刻之间的时间段作为时间区间，获取药物输注泵在预设两个时刻之间的输注日志，例如，可以每天获取药物输注泵在上午9点至下午10点之间所产生的输注日志。或者，输注泵也可以实时或者定期将输注日志传输到服务器，由服务器保存，在需要进行分析时，服务器获取预设时间区间内已存储的数据进行分析。当然，还可以根据需要进行设置，本申请不做限制。
服务器除了获取输注数据，还可以获取药物输注泵对应的患者信息和/或属性信息。属性信息可以包括位置信息和输注级别等中的一项或多项，位置信息可以是表示地理位置的信息，也可以是管辖信息，管辖信息可以是表示药物输注泵所归属的信息，可以为科室、分院和管辖区域等，输注级别可以是预先对输注进行级别的划分。例如，位置信息可以是药物输注泵所在的地理位置，也可以是药物输注泵所在的医院信息、科室信息、病区信息或床位等，也可以是根据实际需要划分的其他管辖范围。患者信息表示药物输注泵的输注对象的信息，例如，患者信息可以包括患者基本信息、生理参数信息、患者报警信息、生理报警信息、疾病信息、病史、医嘱和治疗史等中的至少一项。患者基本信息可以包括患者的年龄和姓名等个人信息，也可以包括患者的身高和体重等基本生理信息；生理参数信息可以包括血压、心率、心电、血氧饱和度、体温和辐射能量等一项或多项参数信息，生理参数信息可以通过监测生理参数的设备或泵进行获取；患者报警信息是指患者主动进行报警的信息，可以包括报警类型、报警信息和报警级别等中的至少一项，患者报警信息可以由泵发出，也可以由预设的移动终端等独立设备发出；生理报警信息是指针对患者生理参数的报警信息，可以由对患者生理参数进行监控的电子设备监测到患者的生理参数出现异常而进行报警，生理报警信息可以包括生理报警类型、报警信息、报警级别等中的至少 一项；疾病信息可以包括此次或历史患病的疾病名称、患病程度和患病的持续时间等中的至少一项。患者信息可以由医护人员上传至服务器进行存储，也可以由服务器主动获取和/或被动接收，例如，服务器可以随时接收对患者生理参数进行监控的电子设备所产生的生理报警信息。
服务器还可以获取科室信息，科室信息可以包括药物输注泵所在的科室名称、科室地点和科室人员等中的至少一项。一个药物输注泵在一个时刻下只能在一个科室中工作，可以在药物输注泵工作之前，医护人员将该药物输注泵所在科室的科室信息发送给服务器。服务器中也可以预先存储各个科室的科室信息，医护人员将药物输注泵所在的科室发送给服务器，由服务器查找与该科室对应的科室信息。服务器中可以预先存储科室与药物输注泵之间的关联关系。
S102、根据输注数据，以及药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果。
示例性地，可以根据输注数据，以及药物输注泵对应的患者信息和/或属性信息，基于预设的用药分析规则，对药物的输注情况进行分析，确定药物输注泵的药物输注情况是否需要调整。可以针对患者信息，对输注日志进行分析，确定该患者信息所对应的患者的输注过程是否合理；也可以针对科室信息，对输注日志进行分析，确定在该科室信息所对应的科室中，药物输注泵的输注过程是否合理；也可以结合患者信息和科室信息，对输注日志进行分析，确定在科室信息对应的科室中，各个患者的输注过程是否合理，分析得到的结果即为药物输注分析结果。
不同患者信息和/或属性信息可以对应有不同的用药分析规则，服务器可以将输注日志中的输注信息与患者信息对应的用药分析规则进行匹配，实现药物输注的分析；也可以将输注日志中的输注信息与科室信息对应的用药分析规则进行匹配，实现药物输注的分析。
在药物输注泵中还可以预先烧录有药物库，服务器中也可以预先存储药物库。药物库中包括与科室或患者相关的不同药物的输注参数的阈值或默认值，不同属性信息和/或不同患者信息可以对应有不同的药物库，可以根据属性信息和/或患者信息，从对应的药物库中获取输注参数的阈值或默认值。用药分析规则可以是将确定出的输注参数的阈值和默认值，与输注日志中记录的实际的输注信息进行比较，得到药物输注分析结果。例如，在输注泵中，将输注时人工设置的输注参数的期望值与下发到输注泵上的药物库中输注参数阈值比较，并给出相应的输注参数超限事件，输注参数超限事件即为药物库超限事件。具体的，医护人员在实际使用药物输注泵进行输注时，对输注参数的设置超出药物库预设的阈值或默认值，这种情况可以称为药物库超限事件。药物库超限事件发生时可以不进行报警，而是弹出提示，例如，可以在输注界面显示状态提示，标识出当前的输注速度超出了预设的输注速度阈值。
输注日志中可以记录输注参数超限的事件，分析这些输注参数超限事件，以及超限后用户的操作行为，例如，操作行为可以包括确认超限、修改参数期望值、不使用参数期望值以及继续进行输注等。
药物库可以是针对某个科室、某个病种或某类型病人所设置的标准的药物输注数据库，可以根据实际的用药情况分析，药物库是否合理。例如，患者信息中包括患者的疾病信息，表示该患者所患的疾病和患病程度。不同疾病和不同的患病程度，所需的药物和药物剂量 的输注要求均可能不同。药物库中记录有不同疾病和/或不同患病程度下，所需的药物和药物剂量阈值和默认值。例如，输注要求可以包括输注速度默认值和输注量默认值等。在得到输注日志后，可以获取输注日志中所输注的药物名称和药物剂量等信息，根据用药分析规则，确定所输注的药物名称和药物与库中的药物名称是否一致，以及所输注的药物剂量和药物剂量默认值是否一致，从而实现对药物输注情况的分析。若输注日志中记录的所输注的药物和药物剂量均与药物库中的药物名称和药物剂量默认值一致，则确定药物输注分析结果为输注情况与药物库相符，无需调整药物库；若输注日志中记录的所输注的药物和药物剂量与药物库不一致，则可以根据输注日志中实际所需的药物名称和药物剂量，确定需要调整的药物名称，以及需要调整的药物剂量值，可以将需要调整的药物名称和需要调整的药物剂量值确定为药物输注分析结果。
本实施例中，可以从多维度得出预期的衡量指标，例如，可以按科室、药物库名称、时间段、泵类型、泵编号、病人住院号和药物名称等进行统计分析，提高分析的灵活性和精度。对大量输注日志进行分析，可以得出具体的衡量指标，例如，可以得到各个科室使用药物库的比例，以及发生报警事件前十名的药物是哪些等，作为药物输注分析结果。
本实施例中，根据输注数据，以及药物输注泵对应的患者信息和/属性信息，进行药物输注分析，包括：根据输注数据中的输注报警信息和报警处理信息，以及药物输注泵对应的患者信息和/或属性信息，进行报警事件分析；其中，报警事件分析包括报警类型和/或报警响应时间的分析；根据输注数据中的输注信息和药物信息，以及药物输注泵对应的患者信息和/或属性信息，进行药物使用分析；其中，药物使用分析包括药物的使用率和/或使用量分析；根据输注数据中的泵信息和操控信息，以及药物输注泵对应的患者信息和/或属性信息，进行泵使用分析；其中，泵使用分析包括输注模式、泵类型、泵使用率、泵使用时间、泵状态和耗材使用分析中的一项或多项。
具体的，根据输注数据中的输注报警信息和报警处理信息，以及药物输注泵对应的患者信息，可以确定在对应的患者信息情况下，容易出现报警的报警类型，以及对报警响应时间等。例如，患者信息为重症患者，在为重症患者输注时，根据输注报警信息，可以确定报警级别大多为三级报警，根据报警处理信息可以确定对三级报警的报警响应时间大多为1分钟。还可以根据位置信息，确定患者所在科室，对不同科室下的报警时间进行分析。例如，患者都是重症患者，但是不同科室下对重症患者的报警响应时间可能不同。
还可以根据输注数据中的输注信息和药物信息，以及药物输注泵对应的患者信息和/或属性信息，对不同患者和/或不同科室进行用药分析，确定不同患者和/或不同科室对各种药物的使用率和/或使用量。例如，对于同一种药物，科室一的使用率比科室二的使用率频繁；对于同一年龄段的患者，疾病A的患者的药物使用量比疾病B的患者的药物使用量多。
还可以根据输注数据中的泵信息和操控信息，以及药物输注泵对应的患者信息和/或属性信息，对泵的使用进行分析。例如，可以确定不同患者和/或不同科室下，所使用的的药物输注泵的输注模式，输注模式可以包括使用药物库的模式和自定义模式等，自定义模式可以是不使用药物库，由医护人员自定义输注参数的模式。还可以分析不同患者和/或不同科室下，药物输注泵的类型、使用率、使用时间、泵状态和耗材等。实现对不同患者信息和/或科室信息的多维度分析，提高药物输注分析的精度和全面性。
S103、输出药物输注分析结果。
示例性地，服务器得到药物输注分析结果后，可以将药物输注分析结果输出到客户端的浏览器进行展示，供医护人员进行查看。药物输注分析结果可以是一种CQI(continuous quality improvement，持续质量改进)报告，医护人员可以参考药物输注分析结果，对药物输注泵的药物库进行调整，提高药物库的确定精度和效率。
图2为本申请实施例中药物输注分析的数据传输过程示意图。图2中，药物输注泵可以通过有线或无线网络向服务器发送输注日志，服务器可以通过有线或无线网络将药物输注分析结果输出给客户端浏览器。例如，可以是通过网络的方式收集输注日志，也可以通过U盘导出输注日志。输注日志中可以包括患者信息，患者信息和科室信息也可以预先存储在服务器中，或通过客户端发送给服务器。
可以通过图形或表格的方式展示出药物输注分析结果，并且可以将药物输注分析结果导出为文本或表格等形式的文件。
本申请实施例提供的一种药物输注分析方法，通过获取药物输注泵在设定时间区间内产生的输注数据，以及患者信息和/或属性信息，对药物的输注情况进行自动分析，确定针对不同患者和/或不同科室所设定的输注参数是否合理，是否需要调整输注参数等，得到药物输注分析结果。解决了现有技术中，由医护人员人工查看药物输注泵的输注情况，并人工对药物输注情况进行分析，所造成的分析错误的问题。通过输注数据可以获取全面的输注信息，节约人力和时间，有效提高药物输注分析的效率和精度。
图3为本申请实施例提供的一种药物输注分析方法的流程示意图，该实施例是在上述实施例基础上的可选实施例。
本实施例中，属性信息包括药物输注泵的位置信息；根据输注数据，以及药物输注泵对应的属性信息，进行药物输注的分析，可细化为：根据输注数据，以及药物输注泵对应的位置信息，对所述药物输注泵中预设的药物库进行药物库使用分析；其中，药物库中包括至少一种药物的输注参数，输注参数包括输注速度、快进剂量和输注量中的一项或多项。
如图3所示，该方法包括以下步骤：
S301、获取设定时间区间内药物输注泵的输注数据，以及药物输注泵对应的患者信息和/或属性信息。
示例性地，本步骤可以参见上述步骤S101，不再赘述。
S302、根据输注数据，以及药物输注泵对应的位置信息，对药物输注泵中预设的药物库进行药物库使用分析，得到药物输注分析结果。
示例性地，确定位置信息所对应的位置范围，例如，位置信息可以包括科室信息，可以是科室信息所对应的科室。位置信息可以是选定的某一个或某几个科室的科室信息，也可以是医院范围内的所有科室的位置信息。
本实施例中，根据输注数据，以及药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果，包括：根据输注数据，以及药物输注泵对应的科室信息，进行科室用药分析，得到药物输注分析结果。
具体的，位置信息可以包括科室信息，在确定药物输注泵所在科室的科室信息后，可以根据该药物输注泵的输注日志和科室信息，针对科室信息对应的科室里的输注情况进行用药分析，确定该科室中的药物输注是否需要调整。
不同科室所治疗的疾病不同，针对不同科室所要治疗的疾病，药物库中可以预先设置各个科室的患者在进行输注时，各输注参数的阈值和默认值，即不同科室间同一输注参数的阈值可能不同，不同科室间同一输注参数的默认值也可能不同。将药物库烧录到药物输注泵中，药物输注泵可以实时获取实际的输注信息，并将实际的输注信息与药物库中的输注参数的阈值进行比较，若实际的输注信息不符合输注参数的阈值的要求，则药物输注泵可以进行报警，报警的时间、地点以及报警所针对的药物和科室等都可以记录在输注日志中。
药物库可以给定输注参数默认值或者输注参数的阈值范围，医护人员在启动输注前，要在药物输注泵上设置输注参数的期望值，即在实际的输注中，以该期望值进行输注。药物库预设值可以包括输注参数的默认值和阈值，阈值是指的一个数值范围，即阈值范围。阈值范围可以包括软上限、软下限、硬上限和硬下限，若医护人员设置的期望值超出软上限或软下限，会有提示信息，提示医护人员是否要用这个超限的期望值，而硬上限和硬下限是不允许超限的。如果多数情况下不更改默认值，那表示预设的默认值是合适的，治疗方案是符合科室使用的。如果医护人员更改默认值，那说明默认值不合适，或者科室不同情况下使用的输注参数可能不一样。若更改的期望值不在阈值范围内，比如经常超出软上限，那么表示设置的软上限值不合适，可以将软上限的输注参数修改为更大的值。
药物库给定输注参数的阈值范围，是为了避免医院人员设置参数时，手误输入值太小或者太大的情况，减少用药的风险。
在得到输注数据后，可以根据科室信息，确定在某个科室中的药物输注泵的输注日志。根据该科室的输注日志，对该科室的用药情况进行用药分析。服务器中可以预先存储有用药分析规则，例如，用药分析规则可以是从输注日志的输注报警信息中查找每一次报警的发生时间段，确定报警发生次数最多的时间段；还可以确定在输注各种药物时的报警次数，确定报警次数最多的药物。输注报警信息可以是药物库超限报警，药物库超限报警可以表明药物库的超限事件在一天当中所发生的的时间段，或者容易发生超限事件药物等。输注报警还可以只统计一段时间内，每个报警类型的发生次数和/或比例，得到经常发生的报警的类型。具体的，使用药物库的模式进行输注，可以认为是更安全的方式，因此，可以确定全院各个科室，使用药物库进行输注的次数和/或比例。还可以按科室统计药物库超限事件的次数，药物库超限事件指的是医护人员设置的输注参数超过了药物库中预设的输注参数阈值，或者是医护人员设置的输注参数超过了药物库中预设的输注参数的阈值范围。了解各科室发生的药物库超限事件的次数，如果超限事件比较多，则表明这个科室的药物库设置可能不合适，或者输注参数的阈值范围预设太小。还可以通过实际输注的药物和该药物的实际输注参数，确定哪种药物最容易发生超限事件，从而确定这个药物的药物库设置可能不合适，需要改进。还可以对医护人员设置的输注速度的分布区间进行分析，了解医护人员进行设置的药物输注速度的范围。
服务器中可以存储有与输注日志中的各种输注参数对应的用药分析规则，还可以存储有与各科室对应的用药分析规则，便于对输注日志进行全面分析，得到完整的药物输注分析结果。
本实施例中，根据输注数据，以及药物输注泵对应的位置信息，对药物输注泵中预设的药物库进行药物库使用分析，包括：根据位置信息对应的位置范围内药物输注泵的输注 数据，确定位置信息对应的位置范围内所输注的药物的输注参数；根据位置信息对应的位置范围内所输注的药物的输注参数和药物库中药物的输注参数，确定位置信息对应的位置范围内的药物库事件；其中，药物库事件包括药物库使用率、输注参数超限事件、超限后用户操作统计和超限值分布中的至少一种。
具体的，获取位置信息对应的位置范围内药物输注泵的输注数据，例如，可以获取药物输注泵的输注日志，从输注日志中可以确定药物的输注参数，该输注参数是医院人员设置的进行药物输注时的实际输注参数，实际输注参数为医护人员手动设置的输注参数的期望值。确定药物库中药物的输注参数，即输注参数默认值和/或输注参数的阈值范围，根据实际输注参数，以及输注参数默认值和/或输注参数的阈值范围，确定位置信息对应的位置范围内的药物库事件。例如，可以确定医护人员进行输注时，是否选择使用预设的药物库。通过确定是否使用药物库，可以确定药物库的使用率。通过位置信息，还可以确定使用药物库的科室。还可以确定药物库使用时间区间，以及输注参数超限事件的次数和时间等。还可以根据超限后医护人员的操作，进行超限后用户操作的统计。超限值分布可以是指医护人员设置的期望值的数值分布范围。
药物库中预设的输注参数的阈值还可以包括药物的输注量阈值，输注日志的输注信息中可以包括药物的实际输注量。药物输注泵可以从输注数据中获取各药物的实际输注量，并从药物库中获取各科室所对应的药物的输注量阈值。判断实际输注量是否超过预设的输注量阈值，若是，则确定该药物的输注量超限。或者，可以判断实际输注量是否超过输注量阈值范围，若是，则确定该药物的输注量超限。可以将输注量超限作为药物库超限时间，记录在输注日志中，也可以进行超限时间报警。
本实施例中，根据输注数据，以及药物输注泵对应的科室信息，对科室信息对应的科室进行用药分析，得到药物输注分析结果，包括：根据输注数据，以及药物输注泵对应的患者信息和科室信息，对科室信息对应的科室进行用药分析，得到药物输注分析结果。
具体的，在针对科室信息对应的科室中的用药情况进行用药分析时，可以结合患者信息和科室信息。例如，可以确定在科室信息对应的科室中患者的患者信息，根据科室中各个患者的患者信息，确定该科室的各个药物输注泵中的药物库与各患者的适配度。例如，确定在一个科室下，各患者的生理报警信息、疾病信息和病史等患者信息，确定不同患者信息下，各药物输注泵的输注情况，例如，可以确定病史一致的患者，确定一个科室中，病史一致的患者的药物输注泵的实际输注信息是否与药物库的输注参数的默认值一致，若不一致，可以确定实际输注信息与输注信息默认值之间的差值。即，得到一个科室下，针对各种患者信息的药物输注分析结果。
服务器中可以针对科室信息和患者信息制定多种用药分析规则，不同科室的用药分析规则可以不同，同一科室下不同患者信息所对应的用药分析规则也可以不同。例如，在同一科室下，患者信息为有病史，用药分析规则可以是分析出输注速度超限的药物；患者信息为有治疗史，用药分析规则可以是分析出输注量超限的药物。
这样设置的有益效果在于，通过结合患者信息和科室信息，可以对不同科室下，不同患者信息的输注日志进行分析，提高药物输注分析的精度，便于对药物库的精准改进。
S303、输出药物输注分析结果。
示例性地，服务器可以将药物输注分析结果发送给客户端，药物输注分析结果中包括 对输注日志中的各个信息进行分析得到的结果。例如，药物输注分析结果可以是药物输注泵是否按照预设的药物库进行输注，或者药物库超限事件经常发生在哪个科室等。
本实施例中，在得到药物输注分析结果之后，还包括：根据药物输注分析结果，对位置信息对应的位置范围内的患者进行用药预测，得到用药预测信息，并输出用药预测信息。
具体的，药物输注分析结果中可以包括位置信息对应的位置范围内，药物输注泵的实际输注速度、实际输注量、报警次数、报警时间和报警对应的药物等信息。根据药物输注分析结果可以对该位置信息的未来一段时间的用药情况进行预测，得到用药预测信息，并将用药预测信息输出给客户端。例如，可以确定发生药物库超限事件的科室是哪个，确定该科室经常发生超限事件的药物，该药物发生超限时主要是输注参数的数值分布范围等。如果是输注速度超限，则用药预测信息可以实际的输注速度的数值分布范围，供医护人员根据该范围进行调整。还可以统计各个科室的常用药物以及各科室使用的各种药物的输注量，从而预测科室后续要准备的药物及输注量。
这样设置的有益效果在于，可以自动预测药物之后的用药情况，为医护人员推荐合理的输注信息的阈值和默认值，避免医护人员人为确定出错误的输注参数的阈值和默认值，减少医护人员的工作量。可以根据视觉化的分析结果，指导医护人员改进药物库设置，以及临床实践活动的改进，提高药物库的调整精度和效率。
本申请实施例提供的一种药物输注分析方法，通过获取药物输注泵在设定时间区间内产生的输注数据，以及患者信息和/或属性信息，对药物的输注情况进行自动分析，确定针对不同患者和/或不同科室所设定的输注参数是否合理，是否需要调整输注参数等，得到药物输注分析结果。解决了现有技术中，由医护人员人工查看药物输注泵的输注情况，并人工对药物输注情况进行分析，所造成的分析错误的问题。通过输注数据可以获取全面的输注信息，节约人力和时间，有效提高药物输注分析的效率和精度。
图4为本申请实施例提供的一种药物输注分析方法的流程示意图，该实施例是在上述实施例基础上的可选实施例。如图4所示，该方法包括以下步骤：
S401、获取设定时间区间内药物输注泵的输注数据，以及药物输注泵对应的患者信息。
示例性地，本步骤可以参见上述步骤S101，不再赘述。
S402、根据输注数据，以及药物输注泵对应的患者信息，进行药物输注的分析，得到药物输注分析结果。
示例性地，可以根据各个药物输注泵的输注数据和各个患者的疾病信息，得到针对各种疾病的药物输注分析结果，也可以选定某种疾病进行药物输注分析。例如，根据患者信息，可以确定患者所患的疾病类型，根据该疾病类型对应的药物输注泵的输注日志，确定在治疗该疾病类型时，实际的药物输注情况。根据服务器中预设的该疾病类型对应的用药分析规则，对该疾病类型的输注情况进行分析，得到药物输注分析结果。
本实施例中，根据输注数据，以及药物输注泵对应的患者信息，进行药物输注的分析，得到药物输注分析结果，包括：从患者信息中获取患者的疾病信息；根据输注数据和疾病信息，进行疾病用药分析，得到药物输注分析结果。
具体的，患者信息中可以包括疾病信息，疾病信息可以包括疾病名称和患病程度等，用于表示患者的疾病类型。不同疾病信息对应有不同的用药分析规则，在确定疾病信息后，可以根据预设的疾病信息与用药分析规则之间的关联关系，确定与各疾病信息关联的用药 分析规则，作为目标用药分析规则。根据目标用药分析规则，对输注数据进行分析。例如，对于疾病A，患病程度为轻症，目标用药分析规则为对确定输注速度超限的药物，将输注速度超限的药物确定为需要调整输注速度阈值的药物，可以将这些药物写入药物输注分析结果中。
每个药物输注泵对应给一个患者进行输注，每个患者都对应有患者信息，即，一个药物输注泵对应有患者信息。确定各药物输注泵所对应的患者信息中的疾病信息，根据疾病名称和/或患病程度，对药物输注泵进行分类，可以将同一疾病名称和/或同一患病程度的药物输注泵划分为一类。获取各类药物输注泵的输注日志，对各类药物输注泵的输注日志进行独立分析。预先设置疾病信息与用药分析规则之间的关联关系，可以是疾病名称与用药分析规则之间的关联关系，也可以是患病程度与用药分析规则之间的关联关系。根据疾病名称与用药分析规则之间的关联关系，以及患病程度与用药分析规则之间的关联关系，对各类药物输注泵的输注日志进行分析，得到各类药物输注泵的药物输注分析结果。将各类药物输注泵的药物输注分析结果，作为各疾病信息对应的药物输注分析结果。
药物输注泵在发送输注日志之前，可以先对自身的输注信息进行初步分析，例如，可以根据预设的药物库，确定各药物的输注速度差值、输注量差值以及输注报警信息等。也可以由服务器在获取药物输注泵的实际的输注速度和输注量后，根据预设的药物库，确定输注速度差值和输注量差值。
这样设置的有益效果在于，可以针对疾病信息对输注日志进行针对性分析，避免其他信息对分析造成影响，提高用药分析的效率和精度，实现用药分析的自动化。
本实施例中，根据输注数据，以及药物输注泵对应的患者信息，进行药物输注分析，得到药物输注分析结果，包括：从患者信息中获取患者类型；根据输注数据和患者类型，基于患者的疾病信息，进行患者用药分析，得到药物输注分析结果。
具体的，患者信息中还可以包括患者类型，患者类型可以用于表示患者的年龄段，例如，患者类型可以是儿童、青年、中年和老年等。在治疗不同患者类型时，药物的输注速度和输注量等输注参数的值可以不同，例如，对于儿童患者，药物的输注量要比中年患者的输注量少。因此，不同患者类型的患者所使用的药物输注泵所记录的输注信息的值会存在差异。
在使用药物输注泵时，可以将药物输注泵的唯一编号与患者信息进行关联，根据药物输注泵的编号，可以得到正在使用该药物输注泵患者的患者信息。获取不同患者类型的患者所使用的药物输注泵的输注日志，对各患者类型所对应的输注日志进行分析。服务器中可以预先存储有各患者类型与用药分析规则之间的关联关系，根据预设的患者类型与用药分析规则，确定与各患者类型对应的用药分析规则。根据与各患者类型对应的用药分析规则，对各患者类型对应的输注日志进行分析。例如，可以确定一种患者类型的输注速度平均值，将该输注速度平均值写入药物输注分析结果。也可以确定一种患者类型的常用药物，将常用药物的名称写入药物输注分析结果。还可以结合患者类型和患者的疾病信息，对患者进行用药分析。
若药物输注泵为镇痛泵，则可以根据镇痛泵的输注数据，确定哪种药物治疗方案的镇痛效果较好，便于后续对患者的治疗。
这样设置的有益效果在于，可以针对患者类型对输注数据进行针对性分析，避免其他 信息对分析造成影响，提高治疗不同类型的患者时，用药的效率和精度，实现用药分析的自动化。
本实施例中，根据输注数据，以及药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果，包括：根据输注数据，以及药物输注泵对应的患者信息和属性信息，对患者对应的疾病进行用药分析，得到药物输注分析结果。
在对患者对应的疾病进行用药分析时，可以结合患者信息和位置信息，具体的，可以结合患者信息和科室信息。确定不同科室下，各患者的用药情况。例如，可以确定不同科室下，同样疾病信息的患者的输注速度是否均超过输注速度阈值，若是，则可以在药物输注分析结果中写明该疾病信息对应的输注速度需要调整。
S403、输出药物输注分析结果。
示例性地，服务器可以将药物输注分析结果发送给客户端，药物输注分析结果中包括对输注日志中的各个信息进行分析得到的结果。例如，药物输注分析结果可以是药物输注泵是否按照预设的药物库进行输注，或者药物输注泵报警最常发生在哪种疾病的输注过程中。
本实施例中，在得到药物输注分析结果之后，还包括：根据药物输注分析结果，对患者信息对应的患者进行用药预测，得到用药预测信息，并输出用药预测信息。
具体的，药物输注分析结果中可以包括患者信息对应的药物输注泵的实际输注速度、实际输注量、输注速度超限次数、输注量超限次数、报警次数、报警时间和报警对应的药物等信息。根据药物输注分析结果可以对不同患者在未来的用药情况进行预测，得到用药预测信息，并将用药预测信息输出给客户端。例如，确定报警次数最多的药物，对该药物的用药进行重点预测，可以计算该药物在设定区间内的平均输注速度和平均输注量，根据平均输注速度和平均输注量等信息，预测该药物在未来的输注速度和可能达到的输注速度和输注量，提醒医护人员准备足量的药物进行后续的输注。
可以根据实际的输注速度，确定输注速度阈值的推荐值，并写入用药预测信息中。还可以根据实际的输注量，确定输注量阈值的推荐值，并写入用药预测信息中，供医护人员进行参考。
这样设置的有益效果在于，可以自动预测药物之后的用药情况，为医护人员推荐合理的输注参数的阈值和默认值，避免医护人员人为确定出错误的输注信息的阈值和默认值，减少医护人员的工作量。其中，输注参数可以包括输注速度、预置量和快进量等，对于镇痛泵，输注参数还可以包括背景流速、首剂量、自控量和极限量等。可以根据视觉化的分析结果，指导对药物库的改进，以及临床实践活动的改进，提高药物库的调整精度和效率。
本实施例中，在输出药物输注分析结果之后，还包括：响应于接收到的药物库更新指令，从药物库更新指令中获取用户输入的待更新的输注参数；确定药物库中，待更新的输注参数对应的药物的输注参数，作为当前输注参数，并将当前输注参数替换为待更新的输注参数。
具体的，医护人员可以根据药物输注分析结果进行药物库更新，医护人员可以在客户端上发出药物库更新指令，药物库更新指令中可以包括待更新的输注参数，待更新的输注参数可以包括新的默认值和阈值。确定药物库中，待更新的输注参数所对应的输注参数，将该输注参数阈值和默认值作为药物库中的当前输注参数，并将当前输注参数替换为待更 新的输注参数，完成药物库的更新。
还可以在接收到药物库更新指令后，获取药物输注分析中得到的新的阈值或默认值。即，药物输注分析结果可以包括输注参数的推荐阈值和推荐默认值，将推荐阈值和推荐默认值作为待更新的输注参数，更新药物库，使药物库中的输注参数更新为新的阈值和默认值。
本申请实施例提供的一种药物输注分析方法，通过获取药物输注泵在设定时间区间内产生的输注数据，以及患者信息和/或属性信息，对药物的输注情况进行自动分析，确定针对不同患者和/或不同科室所设定的输注参数是否合理，是否需要调整输注参数等，得到药物输注分析结果。解决了现有技术中，由医护人员人工查看药物输注泵的输注情况，并人工对药物输注情况进行分析，所造成的分析错误的问题。通过输注数据可以获取全面的输注信息，节约人力和时间，有效提高药物输注分析的效率和精度。
图5为本申请实施例提供的一种药物输注分析装置的结构框图。为了便于说明，仅示出了与本公开实施例相关的部分。参照图5，所述装置包括：数据获取模块501、数据分析模块502和结果输出模块503。
数据获取模块501，用于获取设定时间区间内药物输注泵的输注数据，以及所述药物输注泵对应的患者信息和/或属性信息；
数据分析模块502，用于根据所述输注数据，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果；
结果输出模块503，用于输出所述药物输注分析结果。
图6为本申请实施例提供的一种药物输注分析装置的结构框图，在图5所示实施例的基础上，如图6所示，数据分析模块502包括报警事件分析单元5021、药物使用分析单元5022和泵使用分析单元5023。
报警事件分析单元5021，用于根据所述输注数据中的输注报警信息和报警处理信息，以及所述药物输注泵对应的患者信息和/或属性信息，进行报警事件分析；其中，所述报警事件分析包括报警类型和/或报警响应时间的分析；
药物使用分析单元5022，用于根据所述输注数据中的输注信息和药物信息，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物使用分析；其中，所述药物使用分析包括药物的使用率和/或使用量分析；
泵使用分析单元5023，用于根据所述输注数据中的泵信息和操控信息，以及所述药物输注泵对应的患者信息和/或属性信息，进行泵使用分析；其中，所述泵使用分析包括输注模式、泵类型、泵使用率、泵使用时间、泵状态和耗材使用分析中的一项或多项。
一个示例中，输注数据包括所述药物输注泵的输注信息、泵信息、药物信息、操控信息、输注报警信息、报警处理信息、操作人员类型和操作人员权限中的至少一项。
一个示例中，患者信息包括患者类型、患者身体信息、生理参数信息、患者报警信息、生理报警信息、疾病信息、病史、医嘱和治疗史中的至少一项。
一个示例中，属性信息包括药物输注泵的位置信息；
数据分析模块502，包括：
药物库分析单元，用于根据所述输注数据，以及所述药物输注泵对应的位置信息，对所述药物输注泵中预设的药物库进行药物库使用分析；其中，所述药物库中包括至少一种 药物的输注参数，所述输注参数包括输注速度、快进剂量和输注量中的一项或多项。
一个示例中，药物库分析单元，具体用于：
根据所述位置信息对应的位置范围内药物输注泵的输注数据，确定所述位置信息对应的位置范围内所输注的药物的输注参数；
根据所述位置信息对应的位置范围内所输注的药物的输注参数和药物库中药物的输注参数，确定所述位置信息对应的位置范围内的药物库事件；其中，所述药物库事件包括药物库使用率、输注参数超限事件、超限后用户操作统计和超限值分布中的至少一种。
一个示例中，位置信息包括科室信息；
数据分析模块502，具体用于：
根据所述输注数据，以及所述药物输注泵对应的科室信息，进行科室用药分析，得到所述药物输注分析结果。
一个示例中，数据分析模块502，具体用于：
从所述患者信息中获取患者的疾病信息；
根据所述输注数据和所述疾病信息，进行疾病用药分析，得到所述药物输注分析结果。
一个示例中，数据分析模块502，具体用于：
从所述患者信息中获取患者类型；
根据所述输注数据和所述患者类型，基于患者的疾病信息，进行患者用药分析，得到所述药物输注分析结果。
一个示例中，数据分析模块502，具体用于：
根据所述输注数据，以及所述药物输注泵对应的患者信息和位置信息，对患者对应的疾病进行用药分析，得到所述药物输注分析结果。
一个示例中，该装置还包括：
位置用药预测模块，用于在得到药物输注分析结果之后，根据所述药物输注分析结果，对所述位置信息对应的位置范围内的患者进行用药预测，得到用药预测信息，并输出所述用药预测信息。
一个示例中，该装置还包括：
患者用药预测模块，用于在得到药物输注分析结果之后，根据所述药物输注分析结果，对所述患者信息对应的患者进行用药预测，得到用药预测信息，并输出所述用药预测信息。
一个示例中，该装置还包括：
药物库更新模块，用于在输出所述药物输注分析结果之后，响应于接收到的药物库更新指令，从所述药物库更新指令中获取用户输入的待更新的输注参数；
确定所述药物库中，所述待更新的输注参数对应的药物的输注参数，作为当前输注参数，并将所述当前输注参数替换为所述待更新的输注参数。
图7为本申请实施例提供的一种电子设备的结构框图，如图7所示，电子设备包括：存储器71，处理器72；存储器71；用于存储处理器72可执行指令的存储器。
其中，处理器72被配置为执行如上述实施例提供的方法。
电子设备还包括接收器73和发送器74。接收器73用于接收其他设备发送的指令和数据，发送器74用于向外部设备发送指令和数据。
图8是根据一示例性实施例示出的一种电子设备的框图，该设备可以是移动电话，计 算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
设备800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)接口812，传感器组件814，以及通信组件816。
处理组件802通常控制设备800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在设备800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为设备800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为设备800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述设备800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当设备800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为设备800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为设备800的显示器和小键盘，传感器组件814还可以检测设备800或设备800一个组件的位置改变，用户与设备800接触的存在或不存在，设备800方位或加速/减速和设备800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像 传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于设备800和其他设备之间有线或无线方式的通信。设备800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，设备800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由设备800的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
一种非临时性计算机可读存储介质，当该存储介质中的指令由终端设备的处理器执行时，使得终端设备能够执行上述终端设备的药物输注分析方法。
本申请还公开了一种计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现如本实施例中所述的方法。
本申请以上描述的系统和技术的各种实施方式可以在数字电子电路系统、集成电路系统、场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准产品(ASSP)、芯片上系统的系统(SOC)、负载可编程逻辑设备(CPLD)、计算机硬件、固件、软件、和/或它们的组合中实现。这些各种实施方式可以包括：实施在一个或者多个计算机程序中，该一个或者多个计算机程序可在包括至少一个可编程处理器的可编程系统上执行和/或解释，该可编程处理器可以是专用或者通用可编程处理器，可以从存储系统、至少一个输入装置、和至少一个输出装置接收数据和指令，并且将数据和指令传输至该存储系统、该至少一个输入装置、和该至少一个输出装置。
用于实施本申请的方法的程序代码可以采用一个或多个编程语言的任何组合来编写。这些程序代码可以提供给通用计算机、专用计算机或其他可编程数据处理装置的处理器或控制器，使得程序代码当由处理器或控制器执行时使流程图和/或框图中所规定的功能/操作被实施。程序代码可以完全在机器上执行、部分地在机器上执行，作为独立软件包部分地在机器上执行且部分地在远程机器上执行或完全在远程机器或电子设备上执行。
在本申请的上下文中，机器可读介质可以是有形的介质，其可以包含或存储以供指令执行系统、装置或设备使用或与指令执行系统、装置或设备结合地使用的程序。机器可读介质可以是机器可读信号介质或机器可读储存介质。机器可读介质可以包括但不限于电子的、磁性的、光学的、电磁的、红外的、或半导体系统、装置或设备，或者上述内容的任何合适组合。机器可读存储介质的更具体示例会包括基于一个或多个线的电气连接、便携式计算机盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或快闪存储器)、光纤、便捷式紧凑盘只读存储器(CD-ROM)、光学储 存设备、磁储存设备、或上述内容的任何合适组合。
为了提供与用户的交互，可以在计算机上实施此处描述的系统和技术，该计算机具有：用于向用户显示信息的显示装置(例如，CRT(阴极射线管)或者LCD(液晶显示器)监视器)；以及键盘和指向装置(例如，鼠标或者轨迹球)，用户可以通过该键盘和该指向装置来将输入提供给计算机。其它种类的装置还可以用于提供与用户的交互；例如，提供给用户的反馈可以是任何形式的传感反馈(例如，视觉反馈、听觉反馈、或者触觉反馈)；并且可以用任何形式(包括声输入、语音输入或者、触觉输入)来接收来自用户的输入。
可以将此处描述的系统和技术实施在包括后台部件的计算系统(例如，作为数据电子设备)、或者包括中间件部件的计算系统(例如，应用电子设备)、或者包括前端部件的计算系统(例如，具有图形用户界面或者网络浏览器的用户计算机，用户可以通过该图形用户界面或者该网络浏览器来与此处描述的系统和技术的实施方式交互)、或者包括这种后台部件、中间件部件、或者前端部件的任何组合的计算系统中。可以通过任何形式或者介质的数字数据通信(例如，通信网络)来将系统的部件相互连接。通信网络的示例包括：局域网(LAN)、广域网(WAN)和互联网。
计算机系统可以包括客户端和电子设备。客户端和电子设备一般远离彼此并且通常通过通信网络进行交互。通过在相应的计算机上运行并且彼此具有客户端-电子设备关系的计算机程序来产生客户端和电子设备的关系。电子设备可以是云电子设备，又称为云计算电子设备或云主机，是云计算服务体系中的一项主机产品，以解决了传统物理主机与VPS服务("Virtual Private Server"，或简称"VPS")中，存在的管理难度大，业务扩展性弱的缺陷。电子设备也可以为分布式系统的电子设备，或者是结合了区块链的电子设备。应该理解，可以使用上面所示的各种形式的流程，重新排序、增加或删除步骤。例如，本申请中记载的各步骤可以并行地执行也可以顺序地执行也可以不同的次序执行，只要能够实现本申请公开的技术方案所期望的结果，本文在此不进行限制。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本申请的真正范围和精神由下面的权利要求书指出。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求书来限制。

Claims (16)

  1. 一种药物输注分析方法，其特征在于，包括：
    获取设定时间区间内药物输注泵的输注数据，以及所述药物输注泵对应的患者信息和/或属性信息；
    根据所述输注数据，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物输注分析，得到药物输注分析结果；
    输出所述药物输注分析结果。
  2. 根据权利要求1所述的方法，其特征在于，所述输注数据包括所述药物输注泵的输注信息、泵信息、药物信息、操控信息、输注报警信息、报警处理信息、操作人员类型和操作人员权限中的至少一项。
  3. 根据权利要求1所述的方法，其特征在于，所述患者信息包括患者类型、患者身体信息、生理参数信息、患者报警信息、生理报警信息、疾病信息、病史、医嘱和治疗史中的至少一项。
  4. 根据权利要求2所述的方法，其特征在于，根据所述输注数据，以及所述药物输注泵对应的患者信息和/属性信息，进行药物输注分析，包括：
    根据所述输注数据中的输注报警信息和报警处理信息，以及所述药物输注泵对应的患者信息和/或属性信息，进行报警事件分析；其中，所述报警事件分析包括报警类型和/或报警响应时间的分析；
    根据所述输注数据中的输注信息和药物信息，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物使用分析；其中，所述药物使用分析包括药物的使用率和/或使用量分析；
    根据所述输注数据中的泵信息和操控信息，以及所述药物输注泵对应的患者信息和/或属性信息，进行泵使用分析；其中，所述泵使用分析包括输注模式、泵类型、泵使用率、泵使用时间、泵状态和耗材使用分析中的一项或多项。
  5. 根据权利要求4所述的方法，其特征在于，所述属性信息包括药物输注泵的位置信息；
    根据所述输注数据，以及所述药物输注泵对应的属性信息，进行药物输注分析，包括：
    根据所述输注数据，以及所述药物输注泵对应的位置信息，对所述药物输注泵中预设的药物库进行药物库使用分析；其中，所述药物库中包括至少一种药物的输注参数，所述输注参数包括输注速度、快进剂量和输注量中的一项或多项。
  6. 根据权利要求5所述的方法，其特征在于，根据所述输注数据，以及所述药物输注泵对应的位置信息，对所述药物输注泵中预设的药物库进行药物库使用分析，包括：
    根据所述位置信息对应的位置范围内药物输注泵的输注数据，确定所述位置信息对应的位置范围内所输注的药物的输注参数；
    根据所述位置信息对应的位置范围内所输注的药物的输注参数和药物库中药物的输注参数，确定所述位置信息对应的位置范围内的药物库事件；其中，所述药物库事件包括药物库使用率、输注参数超限事件、超限后用户操作统计和超限值分布中的至少一种。
  7. 根据权利要求6所述的方法，其特征在于，所述位置信息包括科室信息；
    根据所述输注数据，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果，包括：
    根据所述输注数据，以及所述药物输注泵对应的科室信息，进行科室用药分析，得到所述药物输注分析结果。
  8. 根据权利要求1-6中任一所述的方法，其特征在于，根据所述输注数据，以及所述药物输注泵对应的患者信息，进行药物输注的分析，得到药物输注分析结果，包括：
    从所述患者信息中获取患者的疾病信息；
    根据所述输注数据和所述疾病信息，进行疾病用药分析，得到所述药物输注分析结果。
  9. 根据权利8所述的方法，其特征在于，根据所述输注数据，以及所述药物输注泵对应的患者信息，进行药物输注的分析，得到药物输注分析结果，包括：
    从所述患者信息中获取患者类型；
    根据所述输注数据和所述患者类型，基于患者的疾病信息，进行患者用药分析，得到所述药物输注分析结果。
  10. 根据权利要求7所述的方法，其特征在于，在得到药物输注分析结果之后，还包括：
    根据所述药物输注分析结果，对所述位置信息对应的位置范围内的患者进行用药预测，得到用药预测信息，并输出所述用药预测信息。
  11. 根据权利要求1-6中任一所述的方法，其特征在于，在得到药物输注分析结果之后，还包括：
    根据所述药物输注分析结果，对所述患者信息对应的患者进行用药预测，得到用药预测信息，并输出所述用药预测信息。
  12. 根据权利要求7所述的方法，其特征在于，在输出所述药物输注分析结果之后，还包括：
    响应于接收到的药物库更新指令，从所述药物库更新指令中获取用户输入的待更新的输注参数；
    确定所述药物库中，所述待更新的输注参数对应的药物的输注参数，作为当前输注参数，并将所述当前输注参数替换为所述待更新的输注参数。
  13. 一种药物输注分析装置，其特征在于，包括：
    数据获取模块，用于获取设定时间区间内药物输注泵的输注数据，以及所述药物输注泵对应的患者信息和/或属性信息；
    数据分析模块，用于根据所述输注数据，以及所述药物输注泵对应的患者信息和/或属性信息，进行药物输注的分析，得到药物输注分析结果；
    结果输出模块，用于输出所述药物输注分析结果。
  14. 一种药物输注分析系统，其特征在于，包括：处理器，以及与所述处理器通信连接的存储器；
    所述存储器存储计算机执行指令；
    所述处理器执行所述存储器存储的计算机执行指令，以实现如权利要求1-12中任一项所述的药物输注分析方法。
  15. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机执行指令，所述计算机执行指令被处理器执行时用于实现如权利要求1-12中任一项所述的药物输注分析方法。
  16. 一种计算机程序产品，其特征在于，包括计算机程序，该计算机程序被处理器执行时实现如权利要求1-12中任一项所述的药物输注分析方法。
PCT/CN2022/120345 2022-09-21 2022-09-21 药物输注分析方法、装置、电子设备及存储介质 WO2024060090A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280004924.1A CN116097368A (zh) 2022-09-21 2022-09-21 药物输注分析方法、装置、电子设备及存储介质
PCT/CN2022/120345 WO2024060090A1 (zh) 2022-09-21 2022-09-21 药物输注分析方法、装置、电子设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/120345 WO2024060090A1 (zh) 2022-09-21 2022-09-21 药物输注分析方法、装置、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024060090A1 true WO2024060090A1 (zh) 2024-03-28

Family

ID=86197753

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120345 WO2024060090A1 (zh) 2022-09-21 2022-09-21 药物输注分析方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN116097368A (zh)
WO (1) WO2024060090A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030009244A1 (en) * 1995-05-15 2003-01-09 Engleson Joseph J. System and method for collecting data and managing patient care
US20050055242A1 (en) * 2002-04-30 2005-03-10 Bryan Bello System and method for medical data tracking, analysis and reporting for healthcare system
CN106964014A (zh) * 2017-02-13 2017-07-21 深圳麦科田生物医疗技术有限公司 一种输液管理方法及系统
CN110787337A (zh) * 2019-10-28 2020-02-14 珠海福尼亚医疗设备有限公司 药液输注装置、监控系统及监控方法
CN112368037A (zh) * 2018-08-20 2021-02-12 深圳迈瑞科技有限公司 一种监测信息输出方法、输注泵、显示设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030009244A1 (en) * 1995-05-15 2003-01-09 Engleson Joseph J. System and method for collecting data and managing patient care
US20050055242A1 (en) * 2002-04-30 2005-03-10 Bryan Bello System and method for medical data tracking, analysis and reporting for healthcare system
CN106964014A (zh) * 2017-02-13 2017-07-21 深圳麦科田生物医疗技术有限公司 一种输液管理方法及系统
CN112368037A (zh) * 2018-08-20 2021-02-12 深圳迈瑞科技有限公司 一种监测信息输出方法、输注泵、显示设备及存储介质
CN110787337A (zh) * 2019-10-28 2020-02-14 珠海福尼亚医疗设备有限公司 药液输注装置、监控系统及监控方法

Also Published As

Publication number Publication date
CN116097368A (zh) 2023-05-09

Similar Documents

Publication Publication Date Title
US11383027B2 (en) Integration of infusion pump with remote electronic device
US20230010638A1 (en) User interface improvements for medical devices
Giuliano Intravenous smart pumps: usability issues, intravenous medication administration error, and patient safety
US20240087731A1 (en) Context-aware healthcare notification system
CN114341998A (zh) 用于医疗设备监测的系统和方法
CN114342000A (zh) 用于监督应用程序的图形用户界面的系统和方法
JP2022539040A (ja) 臨床家のインタラクションに基づいた医療用デバイスの適応制御
CN114341999A (zh) 用于医疗设备趋势的图形用户界面的系统和方法
WO2024060090A1 (zh) 药物输注分析方法、装置、电子设备及存储介质
CN115485004A (zh) 用于对生命攸关医疗设备进行远程控制的系统和方法
AU2020203449A1 (en) Context-aware healthcare notification system
US20240062866A1 (en) Alert management in fluid delivery system
CN115938551A (zh) 信息处理方法、设备及存储介质
WO2024039748A1 (en) Multi-pump closed-loop management system
US20140282091A1 (en) Collaborative Review and Approval of Medical Device Data Sets

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22959100

Country of ref document: EP

Kind code of ref document: A1