Method and system for automatic remote programming of infusion pump
By automatically remote programming using short confirmation codes in medical facilities, canceling the scanning process, simplifying the infusion workflow, solving the problems of time-consuming and drug errors in the existing technology of nurses scanning patients' bedsides, achieving faster and safer infusion process.
Patent Information
- Application Number
- CN202410928811.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-07-11
- Filing Date
- 2024-07-11
- Publication Date
- 2025-01-14
AI Technical Summary
Automatic programming workflows in existing medical facilities rely on the user interface of scanners and EMR systems, resulting in nurses requiring multiple scans at the patient’s bedside, which is time-consuming and complex, leading to low acceptance and risk of medication errors.
By introducing multiple beds and multiple infusion pumps into the patient data management system of medical facilities, automatic remote programming is performed using short confirmation codes, canceling the scanning process, all users interact and transferring to the infusion pump, simplifying workflow, and in the EMR system and infusion pump system for distribution and verification.
It significantly reduces the time-consuming workflow, improves user-friendliness, reduces the risk of misdistribution of drugs, and achieves a faster and safer infusion process.
Smart Images
Figure CN119314648A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a method and a system for automatic remote programming of an infusion pump by means of an infusion order provided in / by a patient data management system of the medical facility. Background Art
[0002] Automatic programming or BCMA workflows that have been used since many years in parts of the world are prior art, where BCMA stands for Bar Code Medication Management, ie roughly Bar Code Assisted Medication Management.
[0003] Electronic Medical Record (EMR) systems or patient data management systems are required in medical facilities such as hospitals, nursing homes, etc. Based on a medication order created in the EMR system for a specific patient, with a specific medication and precise specifications for use, a machine-readable (barcode) label is first created by the system for the medication container and—if not already present—for the patient.
[0004] At the patient's bed, the nurse scans the patient's wristband equipped with a barcode, the medication container equipped with a corresponding barcode in preparation, and finally the infusion pump to be used, which is also equipped with a barcode, using a scanner that is connected to the EMR system. There, the patient ID and medication ID scanned on site are now compared with the current medication order (right patient? right medication? etc.) and, in the case of a successful check, are sent to the previously scanned infusion pump.
[0005] The pump is further checked by comparing the drug and the pre-set specifications for the application (dose or flow rate, volume to be infused, limits, . . . ) with the data and pre-set specifications stored in the drug library of the infusion pump.
[0006] Finally, the infusion pump displays the received data on the display for final confirmation; then the infusion therapy can begin. The ongoing infusion data, including the order ID, is then sent back to the EMR system so that the infusion data can be automatically assigned to the corresponding medication order and / or the patient's electronic medical record.
[0007] The disadvantages of this approach can be summarized as follows:
[0008] • A barcode scanner and user interface with the EMR system must be available and ready to run at the bedside for each infusion therapy to be started, or carried by each nurse.
[0009] Going through the scanning process required separately at the patient bedside and the corresponding confirmation in the EMR system is time consuming simply from a process perspective.
[0010] • The physical distances between the EMR system's user interface, patient wristbands, medication containers, and infusion pumps require multiple spatial transformations in some cases, which complicate the workflow and cause additional time consumption.
[0011] • The points mentioned above lead to low acceptance not only for the workflow owners but also for the nurses / nursing staff, especially when it comes to reintroducing the BCMA workflow.
[0012] · An important part of the BCMA workflow (including scanner-based verification of infusion orders) can be implemented on the EMR system side; the infusion pump system only obtains the completed check infusion order for display on the pump / execution by the pump. This has resulted in only a few EMR systems currently supporting the BCMA workflow.
[0013] • All of this may ultimately lead to medication and medical errors that overload patients, which could have been safely avoided using the BCMA workflow. Summary of the invention
[0014] The object of the present invention is to provide a workflow (method) and a corresponding system (device) for simple, confusable remote programming of an infusion pump via an EMR system, which at least partially avoids or mitigates the disadvantages of the prior art and in particular does not require a laborious scanning process by nursing staff at the patient's bedside.
[0015] According to the invention, the stated object is achieved by a method according to the features of claim 1 and by a system (device) having the features of claim 10 .
[0016] Therefore, a method is provided for automatically remotely programming an infusion pump by means of an infusion order provided in / by a patient data management system of a medical facility, wherein the medical facility
[0017] having a plurality of beds, each of which can be occupied by a patient,
[0018] There are multiple infusion pumps, each of which is connected to the back end of the infusion pump system.
[0019] The patient data management system transmits the infusion order to the backend via the first electronic interface for intermediate storage,
[0020] The corresponding infusion pump receives the intermediate stored infusion order from the back end via the second electronic interface,
[0021] In addition
[0022] A human-readable short confirmation code is directly assigned to the corresponding infusion order as a unique identifier and is provided together when it is consistent,
[0023] a medication container is assigned to the corresponding infusion order, said medication container being equipped with an information carrier containing the assigned short confirmation code,
[0024] The corresponding infusion pump has a receptacle or connection for one of the drug containers,
[0025] an input device is assigned to the respective infusion pump for inputting the associated short identification code which can be extracted from the information carrier of the medication container,
[0026] The last
[0027] In a verification step, the short confirmation code entered at the input device is compared with a short confirmation code directly assigned to the infusion order received from the infusion pump, and the infusion order is executed by the infusion pump or executable upon request only if the short confirmation codes match.
[0028] The term "bed" or "bed space" should preferably be understood in the present application in a broad sense and encompass any infusion location at which an infusion can be dispensed to a patient or customer.
[0029] This significantly simplifies the workflow for secure remote programming of infusion pumps via the EMR system. By eliminating up to three scanning processes and transferring all user interactions to the infusion pump, the entire process becomes significantly faster, more user-friendly and more easily implemented, while retaining all the benefits of the classic automatic programming / BCMA workflow, in particular, eliminating the mis-dispensing of medication to patients.
[0030] In this case, in a basic version, it is necessary that the EMR system contains the (current) assignment of beds to patients and / or that the backend contains the assignment of beds to infusion pumps. Both can be implemented, for example, in the form of an assignment table.
[0031] In other words, in the basic version, an error-free and current assignment of patients and beds (in EMR systems) and beds and pumps (in infusion pump systems) at the time of transmitting the infusion order is an obligatory prerequisite for the described method.
[0032] An alternative would be to additionally enter a second patient-related code at the pump (i.e. a code preferably also greatly shortened by alphanumeric coding), which is created and managed by the EMR system and identifies the patient. This code would either be printed additionally on the patient's wristband or would replace the usually rather long and purely numeric patient ID. This would therefore be an additional input step for the caregiver, which on the other hand eliminates the necessity for bed allocation of the pump.
[0033] The comparison of the short confirmation code is preferably carried out in a decentralized manner outside the EMR and outside the back end, that is, preferably in a control device integrated into the corresponding infusion pump. However, alternatively or additionally, the comparison can also occur in the back end / IOM.
[0034] Furthermore, it is preferred that the corresponding infusion pump queries and receives the infusion order assigned to the infusion pump from the back end via the second electronic interface by pull communication, while the patient data management system preferably transmits the infusion order to the back end via the first electronic interface by push communication. In the first-mentioned case, this is typically an indirect assignment, since the drug order is preferably not explicitly assigned to the pump, but to the patient, to whom the pump is indirectly (i.e., via the bed) assigned.
[0035] In an advantageous variant, a validity period or expiration date is assigned to the respective infusion order and is taken into account in the verification step. Thus, even in the case of larger medical facilities with many infusions, a relatively short verification code may be sufficient.
[0036] If the short confirmation code is an alphanumeric code, it can be manipulated particularly easily by the nursing staff and entered via the input field of the infusion pump. Currently, the term "alphanumeric" should include not only purely numeric codes (especially from the numbers 0 to 9) but also purely letter-based codes (preferably from the Latin capital letters A to Z, if necessary without O and / or without I) and the possibility of codes mixed or combined from the mentioned components. In the last-mentioned case, a three-digit alphanumeric code can map approximately 42,000 variants and is therefore generally sufficient even in view of the limited validity period.
[0037] Instead of or in addition to input via an input field / touch display at the infusion pump, the code can be entered via an input device assigned to the infusion pump, such as an input field at the stand, or via a mobile device (smartphone, tablet, etc.).
[0038] In a preferred simple case, the information carrier is a readable mark, in particular an embossed mark, for example in the form of a stickable label with a short identification code written on it, which is affixed to the medicament container, or in the form of a written sheet, strip, label or other written medium connected to the medicament carrier. However, it is also conceivable that the information carrier contains other forms of short identification codes and is read out, for example, machine-wise / automatically to be fed to an input device.
[0039] The features and advantages mentioned for the method apply analogously to the device.
[0040] The system concept / workflow for validated management of infusion processes or validated infusion management (VIA) described within the scope of the present invention achieves the same purpose as the known BCMA workflow, but is significantly more user-friendly and therefore simpler in implementation and everyday application.
[0041] The main difference is that the entire process is controlled via the infusion pump by combined push / pull communication and all scanning processes are eliminated by using already existing data on the one hand and short confirmation codes or verification codes that can be manipulated by humans on the other hand. Here, the VIA concept requires some innovations not only on the side of the EMR system but also on the side of the infusion pump system.
[0042] Innovations Inspired by VIA
[0043] Preferably an alphanumeric short confirmation code or short verification code (SVC) specific to an Infusion Order is applied, instead of a classic barcode (one-dimensional) or QR code (two-dimensional), which can be simply read from the label of the drug container by the caregiver and can be entered through the user interface of the pump.
[0044] With preferably only three alphanumeric characters (Latin capital letters without "O" and numbers 0 to 9), SVC offers approximately 42,000 code variants, which should be sufficient to create a unique code for each infusion order at the latest when limiting the validity period. Thus, no scanner or other reading device (e.g. smart device) may be required when verifying the drug container.
[0045] VIA-Induced Innovations on the EMR System Side
[0046] • The infusion order contains only a non-specific pump ID activating the VIA mode, since the entire process is controlled by the pump selected by the user and therefore the pump no longer has to be actively addressed in the preparation phase.
[0047] To authenticate the medication container, a unique three-digit SVC is generated and provided with the infusion order either in addition to or instead of the order ID set during the BCMA process.
[0048] Optionally, an infusion order is provided with an earliest start time and / or a limited time validity, which can be evaluated accordingly by the receiving infusion pump system.
[0049] Spatial or logistical restrictions, for example to specific nursing units or specific user groups (on-duty nurses, nurses at corresponding stations, etc.) are also conceivable.
[0050] In this case, the permissible representation must also be included in the infusion order and an additional caregiver-specific SVC must be entered at the pump within the scope of the order verification.
[0051] Innovations Induced by VIA in Infusion Pump Systems
[0052] As long as the infusion order sent by the EMR system contains a special pump ID that triggers the VIA mode, the pump ID is temporarily stored in an additional system component, the Infusion Order Manager (IOM), in the form of an Infusion Order Backlog.
[0053] Pull communication can be actively triggered by the user at each infusion pump to call up the infusion order that exists for the bed or patient.
[0054] • The Infusion Order Manager identifies when a pull communication is triggered at a pump / the pump is placed in receive mode for an infusion order. Given a bed assignment for a pump, the IOM then automatically sends the existing infusion orders assigned to that bed to exactly that pump.
[0055] After receiving the infusion order, the pump requests the user to enter the medication SVC and compares it with the SVC contained in the infusion order received from the IOM. In case of a successful check, all the data of the infusion order are displayed on the display of the pump for final confirmation; otherwise the process is aborted with a corresponding error message.
[0056] If there are multiple infusion orders for a bed for the infusion order manager, a list selection of these orders is generated taking into account any time limits (has the earliest start time not yet been reached? Has the permitted time window expired?) and displayed on the pump that has been switched to reception readiness. After an infusion order has been selected via the user interface of the pump, the infusion order manager sends this order to the pump. If an available infusion order is called up at another pump assigned to the same bed, the infusion order that has already been sent to the other pump is at most still displayed but can no longer be selected.
[0057] The list optionally also contains a delete function for infusion orders that have not yet been started (if necessary, only executable after entering a temporarily valid delete SVC).
[0058] Desirable prerequisites
[0059] The EMR system can uniquely assign patients to beds at each point in time.
[0060] In an infusion pump system, the pump can also be assigned to a single bed.
[0061] When restricted to three-digit alphanumeric codes, approximately 42,000 possible representations (if necessary additionally with a limited validity period) are sufficient to reliably map the number of infusions accumulated simultaneously within this validity period (according to beds, pumps and number of infusions per pump).
[0062] Typical process of VIA programming
[0063] 1. The EMR system sends the infusion order for patient X to the infusion pump system.
[0064] 2. The hospital pharmacy or caregiver prepares the corresponding medication container.
[0065] 3. The hospital pharmacy or caregiver equips the corresponding medication container with a removable label containing a short verification code specific to the order.
[0066] 4. The caregiver places the drug container into any infusion pump assigned to the current bed of patient X and activates pull communication.
[0067] 5. The infusion pump receives the infusion order and needs to enter a short verification code.
[0068] 6. Alternatively: The pump receives a list of existing infusion orders and displays the list on the display for selection. After the corresponding selection, the pump receives the order and requires the entry of a short verification code associated therewith.
[0069] 7. The caregiver enters the code, checks the subsequently displayed order data against the display on the EMR system's user interface (alternatively against an imprint of the medication order), and starts the infusion.
[0070] Advantages of the VIA system concept
[0071] No scanner or smart device is required to program the pump.
[0072] • The caregiver only has to enter a simple three-digit code at the pump, instead of performing three scanning procedures at different locations and controlling through the EMR system's user interface.
[0073] • The user interface of the EMR system is needed at most once, for the final comparison between programming and medication orders.
[0074] · Implementation can be significantly simpler and faster not only from the EMR system perspective but also from the hospital perspective.
[0075] In the event that there are multiple infusion orders for one patient, these infusion orders can be selected and executed individually by each pump assigned to the patient's bed.
[0076] • Infusion orders for a later point in time can also be sent from the EMR system to the infusion pump system and then selected and executed within a predefined time window on each pump assigned to the corresponding patient bed.
[0077] The predetermined execution order of infusion orders can be automatically monitored (for example, infusion order B can only be selected when infusion order A has been started or completed).
[0078] The VIA concept is also based on the known and established automatic programming / BCMA workflows in some parts of the world for many years, advantageously using HL7 communication and IHE transaction profiles. These can be easily supplemented with the additionally required descriptions for the VIA workflow. BRIEF DESCRIPTION OF THE DRAWINGS
[0079] Embodiments of the present invention are explained in more detail with reference to the accompanying drawings, in which:
[0080] Figure 1 shows a schematic overview of a medical facility in which a patient is given an infusion, wherein the various process flows are illustrated by arrows, and
[0081] Figure 2 A schematic diagram showing an infusion pump for use in such a facility. DETAILED DESCRIPTION
[0082] Figure 1 A schematic overview of a medical facility ME in which patients are infused is given. For example, this can be a hospital or a nursing home. The medical facility has a plurality of beds that can be uniquely identified, wherein here in this example, they are simply identified by consecutive bed numbers (bed 1, bed 2 ...). In general, they can be identified by bed IDs. Each bed can be occupied by a patient who can be identified by a unique patient ID and / or his personal data. Here in this example, for simplicity, these are patient X occupying bed 1 and patient Y occupying bed 2, etc. The currently valid allocation Z1 between beds and patients is stored as a data record in an electronic patient data management system (English: Electronic Medical Record-System (electronic medical record system)) EMR.
[0083] At any given point in time, each of the beds is assigned a plurality of infusion pump IPs, where the number can take values of 0, 1, 2, ... That is, the possible cases of "none" or "multiple" infusion pump IPs are included, where each of the infusion pump IPs is assigned to exactly (and to the maximum) one bed. The infusion pump IP can be uniquely identified according to the pump ID, here in this example in the form of consecutive numbers (IP1, IP2, ...). In the current state shown, infusion pumps IP 1 and IP 2 are assigned to bed 1 (and therefore assigned to patient X), while infusion pump IP 3 is assigned to bed 2 (and therefore assigned to patient Y). The current allocation Z2 between the bed and the infusion pump is stored as a data record in the back end of the infusion pump system IPS, and the infusion pump system includes infusion pumps IP 1, IP 2, ...
[0084] In order to implement the queued infusion efficiently and safely, remote programming of the assigned infusion pump IP is facilitated and controlled by the EMR for the corresponding specific infusion process settings. To this end, the EMR generates multiple infusion orders (English: Infusion order) IO according to the presets of the treating physician. Each infusion order IO is assigned to exactly one patient on the bed occupied by the patient and contains instructions about the medication to be dispatched or about the infusion solution, amount, flow rate, etc. Optionally, the infusion order IO can be equipped with an expiration date or an expiration date. In the case of multiple infusions for the same patient, the dispatch order can also be optionally integrated into the infusion order IO.
[0085] In addition, each infusion order IO is assigned a unique short verification code (English: Short Verification Code) SVC, which is a three-digit alphanumeric code in this example. For example, each of these three digits can be selected from all uppercase letters A to Z and the numbers 0 to 9, wherein O (and possibly I) is preferably not required to avoid confusion. For example, this results in (25+10)∧3=42,875 different marking possibilities, which are significantly more in the case of alternative possible four-digit codes and / or when lowercase letters are allowed. Here in this example, SVC "AAA" is assigned to the infusion order IO for patient X on bed 1, while the infusion order IO for patient Y on bed 2 carries SVC "AAB". The SVCs can be integrated into the infusion order IO respectively, or assigned or added as separate elements.
[0086] A medication order (English: Medication Order) MO is derived or generated from the infusion order IO, which is transmitted to a (hospital) pharmacy APO or a drug supplier via a suitable interface SS, preferably electronically. In this example, the pharmacy APO prepares the required infusion according to individual pre-sets regarding ingredients, quantities, etc. and / or provides the infusion solution in the form of ready-to-dispatch bags, syringes, etc., also generally referred to as drug containers MC.
[0087] When the medication order MO is transmitted, the assigned short confirmation code SVC is also transmitted as a mark (label) and assigned to the corresponding medication container, for example by placing a correspondingly printed adhesive label or label. In this example, in particular, medication containers MC with short confirmation codes "AAA" and "AAB" are seen, which are assigned to the infusion order IO discussed above in a unique manner. In addition to the short confirmation code SVC, the marking of the medication container MC can still also include other instructions, such as such instructions contained in the assigned infusion order IO.
[0088] Immediately after creating each infusion order IO, the patient data management system EMR transmits the respective infusion order to the backend of the infusion pump system IPS via a suitable electronic interface SS1 by means of push communication, where the infusion order is stored in a program module called the infusion order manager (English: Infusion Order Manager) IOM. There, the transmitted infusion order IO is available for calling by the infusion pump IP, as explained in more detail further below.
[0089] For example, the caregiver PK or other user extracts the information from the user interface of the EMR: the infusion order IO (with the short confirmation code "AAA") is ready for the patient X on bed 1 and (with the short confirmation code "AAB") is ready for the patient Y on bed 2 accordingly. He / she takes the drug containers MC assigned to the infusion order IO and labeled accordingly from the pharmacy APO, and brings them in turn to the assigned beds and thus to the assigned patients. For example, the caregiver knows or sees: the drug container MC with SVC "AAA" is assigned to the patient X on bed 1. There two infusion pumps IP 1 and IP 2 are ready, and as long as both are not occupied, the caregiver usually chooses freely between the two. For example, the caregiver decides that the infusion pump IP 1 is used for infusion at bed 1. In other cases, the freedom of choice may be limited by the number of infusion pumps and / or other criteria that already exist for occupation and / or at the bed. For example, at bed 2, only the infusion pump IP 3 can be used to execute the infusion order IO with SVC "AAB".
[0090] For example, the caregiver PK inserts a medication container MC with SVC "AAA" into the receptacle of the infusion pump IP 1 at the bed 1 and activates pull communication by entering in an input field (keyboard or touch display), wherein the infusion pump fetches the infusion order IO assigned to the infusion pump from the back end of the infusion pump system IPS via the interface SS2. For example, the infusion pump IP1 notifies the back end of its pump ID for this purpose. Based on the known assignment Z2 between the infusion pump and the bed, the back end recognizes the dependency of the infusion pump IP 1 with the bed 1 and checks the existence of the infusion order IO assigned to the bed 1 in the infusion order manager 10M. In the case of success, the corresponding infusion order IO (here with SVC "AAA") or the ID assigned to the infusion order only once is transmitted from the back end to the infusion pump (here IP 1) via the electronic interface SS2.
[0091] In order to verify that the correct drug container MC has been inserted into the receiving place of the infusion pump IP, the caregiver PK is requested to enter the SVC read from the drug container MC by the caregiver via the input field via the display at the infusion pump IP. In the case of correct input (here "AAA"), the infusion pump IP is programmed according to the infusion order IO obtained or received from the back end, or the infusion order IO previously obtained or the programming performed is released for execution. Otherwise, an error message is output.
[0092] If in the example mentioned multiple infusion orders are queued for bed 1, the method can be carried out so that a selection list of the orders is displayed on the display of the infusion pump IP used, if necessary in combination with the sequence, followed by the user or caregiver making a selection and subsequently (as already described previously) verifying the correct medication by entering the SVC located on the medication container and thus releasing the infusion order for execution.
[0093] In a modification of the method, it can be provided that when or after inserting the medication container MC into the receptacle, the user directly enters the associated SVC in the input field of the infusion pump IP, and thereby prompts the infusion pump IP to ask the back end whether an infusion order IO assigned to this SVC is stored there. In the case of success, the infusion pump IP "pulls" exactly that infusion order from the IOM in the back end. However, in this case, the selection from the list of open medication orders described further above is not possible, because the selection has already been made by entering the SVC - in this regard, a list of other orders for these patients can be displayed here only for information.
[0094] The IP for the infusion pump used in the described scenario is in Figure 2Schematically shown in FIG. The infusion pump IP has a receiving place 10 for a drug container MC and a pump 20 that can be connected to the drug container MC, and the pump is controlled by an integrated control device 30. The infusion order IO that is coordinated with the drug container MC and the medical situation individually is stored in a writable memory 40 according to the type of the control program, or can be stored by loading. The infusion order IO can be received from the back end of the infusion pump system IPS via the interface module 50 that is a component of the interface SS2 through "pull" communication. The short confirmation code SVC printed on the drug container MC or added as a label is read by the caregiver PK for this purpose, inputted via the input field 60, and then compared with the short confirmation code SVC directly assigned to the infusion order IO by the verification unit 70 of the control device 30 and verified when consistent. The input field 60 can be realized by a touch-sensitive keyboard on a touch display, which is used to guide the user and output the verification result. In this case, the keyboard can be optimized specifically for inputting SVC. Alternatively, a separate display 80 can be provided.
[0095] In summary, by using and querying the short confirmation code SVC in the manner described, confusion can be avoided in a surprisingly simple manner when transporting the medication container MC from the pharmacy or from the supplier to the assigned bed, without requiring cumbersome scanning procedures or the like.
[0096] Reference numerals list
[0097] APO Pharmacy
[0098] Backend
[0099] Bett Bed
[0100] EMR Electronic Patient Data Management System
[0101] IO Infusion Orders
[0102] IOM Infusion Order Manager
[0103] IP Infusion Pumps
[0104] IPS Infusion Pump System
[0105] MC Drug Container
[0106] ME Medical Facilities
[0107] MO Drug Orders
[0108] PK Guardian
[0109] SVC Short Confirmation Code
[0110] SS interface
[0111] Z allocation
[0112] 10 Accommodation
[0113] 20 Pumps
[0114] 30 Control device
[0115] 40 Memory
[0116] 50 Interface module
[0117] 60 Input Fields
[0118] 70 Verification Units
[0119] 80 displays.
Claims
1. A method for automatically remotely programming an infusion pump (IP) by means of an infusion order (IO) provided in / by a patient data management system (EMR) of a medical facility (ME), wherein the medical facility (ME) having a plurality of beds, each of which can be occupied by a patient, There are multiple infusion pumps (IP), each of which is connected to the back end of the infusion pump system (IPS). in The patient data management system (EMR) transmits the infusion order (IO) to the backend for intermediate storage via the first electronic interface (SS1), The corresponding infusion pump (IP) receives the intermediate stored infusion order (IO) from the back end via the second electronic interface (SS2), In addition A human-readable Short Confirmation Code (SVC) is directly assigned to the corresponding Infusion Order (IO) as a unique identifier and is provided together when consistent, a medication container (MC) is assigned to a corresponding infusion order (IO), said medication container being equipped with or connected to an information carrier containing an assigned short confirmation code (SVC), The corresponding infusion pump (IP) has a receptacle (10) or a connection for one of the medicament containers (MC), an input device, in particular an input field (60) arranged on the infusion pump (IP), is assigned to the respective infusion pump (IP) for inputting an associated short verification code (SVC) which can be extracted from the information carrier of the medication container (MC), The last In the verification step, the short confirmation code (SVC) entered at the input device is compared with the short confirmation code (SVC) directly assigned to the infusion order (IO) received from the infusion pump (IP), and only when the short confirmation codes (SVC) are consistent, the infusion order (IO) is executed by the infusion pump (IP) or can be executed upon request.
2. The method according to claim 1, wherein the patient data management system (EMR) contains the allocation of beds to patients (Z1).
3. A method according to claim 1 or 2, wherein the back end comprises an allocation (Z2) of the bed to the infusion pump.
4. The method according to any of the preceding claims, wherein the comparison of the short confirmation codes (SVC) is performed in a control device (30) integrated into the respective infusion pump (IP).
5. The method according to any one of the preceding claims, wherein the corresponding infusion pump (IP) queries the infusion order indirectly assigned to the infusion pump from the back end via the second electronic interface (SS2) through pull communication.
6. The method according to any of the preceding claims, wherein the patient data management system (EMR) transmits the infusion order (IO) to the back end by push communication via the first electronic interface (SS1).
7. Method according to any of the preceding claims, wherein a validity period or an expiry period is assigned to the respective infusion order (IO) and is taken into account in the verification step.
8. A method according to any one of the preceding claims, wherein the short confirmation code (SVC) is an alphanumeric code.
9. Method according to any of the preceding claims, wherein the drug container (MC) is written on or marked with an assigned short verification code (SVC).
10. A system for automatically remotely programming an infusion pump (IP) by means of an infusion order (IO), the infusion order being provided in a patient data management system (EMR) of a medical facility (ME), wherein the medical facility (ME) having a plurality of beds, each of which can be occupied by a patient, There are multiple infusion pumps (IP), each of which is connected to the back end of the infusion pump system (IPS). in The patient data management system (EMR) is designed or programmed to transmit the infusion order (IO) to the backend for intermediate storage via the first electronic interface (SS1), The corresponding infusion pump (IP) is designed or programmed to receive the intermediately stored infusion order (IO) from the backend via the second electronic interface (SS2), In addition A human-readable Short Confirmation Code (SVC) is used as a unique identifier directly assigned to the corresponding Infusion Order (IO), a medication container (MC) is assigned to a corresponding infusion order (IO), said medication container being equipped with or connected to an information carrier containing an assigned short confirmation code (SVC), The corresponding infusion pump (IP) has a receptacle (10) or a connection for one of the medicament containers (MC), an input device, in particular an input field (60) arranged on the infusion pump (IP), is assigned to the respective infusion pump (IP) for inputting an associated short verification code (SVC) which can be extracted from the information carrier of the medication container (MC), The last The system comprises a verification unit (70) which is designed or programmed to compare a short confirmation code (SVC) input at an input device with a short confirmation code (SVC) directly assigned to an infusion order (IO) received from the infusion pump (IP), so that the infusion order (IO) is executed by the infusion pump (IP) or can be executed upon request only when the short confirmation codes (SVC) are consistent.