Systems and methods

Abstract

To enable operation logs regarding administration to be transmitted to an information processing device without omissions, even when a pump and a prescription order are associated after administration of liquid medicine is begun.SOLUTION: A infusion pump 70A starts, upon accepting a first operation, administering liquid medicine in conformity with a processing order and recording logs related to administration. The logs are used for recording administration states in an electronic medical chart. A terminal device 60 associates, upon accepting a second operation, a prescription order with a pump and transmits the prescription order to the infusion pump 70A. The infusion pump 70A initiates processing to periodically transmit logs in first operation and afterward to the terminal device 60 when the second operation is performed before the first operation, and initiates processing to transmit logs prior to the second operation to the terminal device 60 and periodically transmit logs after the second operation onward to the terminal device 60 on condition that the second operation has been performed, when the first operation is performed before the second operation.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present disclosure relates to systems and methods. [Background technology]

[0002] 2. Description of the Related Art Various medical pumps for administering medicinal fluids to patients have been known in the past.

[0003] International Publication No. 2017 / 150480 (Patent Document 1) discloses a medical pump that includes an operation unit, an infusion unit that performs infusion based on the operation of the operation unit, a switching operation determination unit that determines whether a switching operation to implement a prescription different from the one at the start of the infusion has been performed before the infusion is completed, and an infusion history recording unit that records the infusion history of the infusion unit. The infusion history recording unit is configured to be able to record the infusion history when a switching operation is performed. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2017 / 150480 Summary of the Invention [Problem to be solved by the invention]

[0005] There is a need to automatically write operational logs (also called "execution records") related to the administration of medicinal fluids by pumps to electronic medical records stored on a server via an information processing device. Furthermore, multiple pumps are used simultaneously in medical settings.

[0006] In such cases, if the pump and the prescription order for the medicinal liquid to be administered to the patient are not associated in the information processing device, even if the information processing device receives a log, it will not be able to determine which prescription order the log belongs to. Therefore, in order to record correct information in the electronic medical record, it is essential to associate the pump with the prescription order.

[0007] Therefore, this association should be performed before the drug solution is administered by the pump. However, it is conceivable that such an association process may be overlooked and the association may be performed after the drug solution has started to be administered.

[0008] The present disclosure has been made in consideration of the above-mentioned problems, and its purpose is to provide a system and method that can transmit logs related to the administration of medicinal liquid to an information processing device without omission, even if the pump and prescription order are associated after the administration of medicinal liquid has begun. [Means for solving the problem]

[0009] According to one aspect of the present disclosure, a system includes an information processing device that stores a prescription order for a medicinal liquid to be administered to a patient, and a pump that, upon receiving a first operation, begins administering the medicinal liquid to the patient and recording a log related to the administration. The log is transmitted to an external device that stores an electronic medical record to record the administration status of the medicinal liquid in the electronic medical record. Upon receiving a second operation, the information processing device executes a process of associating the prescription order with the pump and a process of transmitting the prescription order to the pump. When the pump receives the prescription order, it administers the medicinal liquid to the patient based on the prescription order, provided that the first operation has been accepted. If the second operation is performed before the first operation, the pump initiates a process of periodically transmitting logs from the first operation onwards to the information processing device. If the first operation is performed before the second operation, the pump initiates a process of transmitting logs from before the second operation onwards to the information processing device, provided that the second operation has been performed, and periodically transmitting logs from the second operation onwards to the information processing device.

[0010] According to another aspect of the present disclosure, there is provided a method for a system including an information processing device storing a prescription order for a medicinal liquid to be administered to a patient, and a pump that, upon receiving a first operation, starts administering the medicinal liquid to the patient and recording a log related to the administration, the log being transmitted to an external device storing an electronic medical record to record the administration status of the medicinal liquid in the electronic medical record. The method includes the steps of: an information processing device, upon receiving a second operation, executing a process of associating a prescription order with a pump and a process of transmitting the prescription order to the pump; a step of, upon receiving the prescription order, administering the medicinal liquid to the patient based on the prescription order, provided that the first operation has been received; a step of, if the second operation is performed before the first operation, starting a process of, if the pump, periodically transmitting logs from the first operation onwards to the information processing device; and a step of, if the first operation is performed before the second operation, starting a process of, if the pump, periodically transmitting logs from the second operation onwards to the information processing device, provided that the second operation has been performed. [Effects of the Invention]

[0011] According to the present disclosure, even if the pump and prescription order are associated with each other after the administration of the medicinal liquid has started, it is possible to transmit all logs related to the administration of the medicinal liquid to the information processing device. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating a schematic configuration of a network system. [Figure 2] FIG. 1 is a diagram illustrating an overview of communication in a communication system. [Figure 3] FIG. 2 is a diagram showing a schematic configuration of drug library data. [Figure 4] FIG. 2 is a diagram showing a schematic configuration of prescription list data. [Figure 5] FIG. 2 illustrates an example of a hardware configuration of a server. [Figure 6]FIG. 2 is a diagram illustrating an example of a hardware configuration of a terminal device. [Figure 7] FIG. 2 is a diagram illustrating an example of a hardware configuration of a pump. [Figure 8] FIG. 2 is a diagram showing an example of an operation panel of a pump. [Figure 9] FIG. 2 is a sequence diagram illustrating a flow of processing executed in the communication system. [Figure 10] FIG. 10 is a sequence diagram illustrating the recording and transmission of a log when a prescription order is associated with an infusion pump before the start button is pressed. [Figure 11] FIG. 10 is a diagram illustrating a period for recording a log and a period for transmitting the log. [Figure 12] FIG. 10 is a sequence diagram illustrating the recording and transmission of a log when a prescription order is associated with an infusion pump after the start button is pressed. [Figure 13] FIG. 10 is a sequence diagram illustrating the transmission of a log from an infusion pump to a terminal device. [Figure 14] FIG. 10 is a flow chart for explaining correction of time information of a log. [Figure 15] 15 is a diagram for explaining the processing in steps S7 and S8 in FIG. 14. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, identical components are designated by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated. Furthermore, in the embodiments described below, when numbers, quantities, etc. are mentioned, the scope of the present invention is not necessarily limited to those numbers, quantities, etc., unless otherwise specified.

[0014] Hereinafter, each embodiment of the present disclosure will be described with reference to the drawings. In the following description, the same members are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated. Further, in the embodiments described below, when referring to the number, amount, etc., unless otherwise specified, the scope of the present invention is not necessarily limited to the number, amount, etc.

[0015] <A. System Configuration> FIG. 1 is a diagram showing a schematic configuration of the network system 1 of the present embodiment.

[0016] As shown in FIG. 1, the network system 1 includes a terminal device 10, a server 20 for recording an electronic medical record, a server 30 of a pharmacy department, a server 40 of a department different from the pharmacy department, and a communication system 2. The communication system 2 includes a server 50 and a rack system (system) 3. The rack system 3 has a terminal device (information processing device) 60, a plurality of infusion pumps 70A, 70B, and a plurality of syringe pumps 70C, 70D, 70E. The rack system 3 is operated by a nurse 9 or a doctor.

[0017] The terminal device 10 is typically connected to the server 20 communicably by wire. The server 20 is typically connected to the terminal device 10 and the server 30 communicably by wire. The server 30 is typically connected to the server 20 and the server 50 communicably by wire.

[0018] The server 50 is typically connected to the server 30 and the server 40 communicably by wire. The server 50 is typically further connected to the terminal device 60 of the rack system 3 communicably by wireless.

[0019] The terminal device 10 is typically used by a doctor. The terminal device 10 accepts input of information on one or more drugs prescribed for the patient for each patient. Hereinafter, for convenience, information input for one patient using the terminal device 10 (information on one or more prescribed drugs) will also be referred to as "prescription list data." In other words, the terminal device 10 accepts input of prescription list data for each patient. The terminal device 10 transmits the input prescription list data to the server 20. The specific configuration of the prescription list data will be described later (FIG. 4).

[0020] The server 20 receives the prescription list data from the terminal device 10. The server 20 records the contents of the received prescription list data in the patient's electronic medical record.

[0021] Server 30 stores drug library data (medicinal liquid data) in advance. Server 30 transmits the drug library data to server 50. When the drug library is updated in server 30, server 30 transmits update data for updating the drug library of server 50 to server 50. Server 30 may transmit the updated drug library data itself as the update data, or may transmit data of only the updated parts.

[0022] The server 30 acquires prescription list data of a designated patient from the server 20 based on an input operation by a pharmacist or the like. The server 30 transmits prescription list data of a patient who is about to start treatment (hereinafter also referred to as a "target patient") to the server 50.

[0023] Through the above processing, the prescription list data of the target patient and the latest drug library data are stored in the server 50. The server 50 also acquires various other data from the server 40. For example, the server 50 acquires data related to anesthesia for the target patient from the server 40.

[0024] In this example, syringe 90 is set in syringe pumps 70C and 70E. Syringe 90 includes a barrel 91 and a plunger rod 92. Plunger rod 92 has a flange 921. Syringe pumps 70C, 70D, and 70E include a drive unit 74 having a pressing surface 741. Infusion pumps 70A and 70B and syringe pumps 70C, 70D, and 70E each have a display 772, 773.

[0025] FIG. 2 is a diagram for explaining an outline of communication in the communication system 2 shown in FIG.

[0026] 2, in this example, the server 50 communicates wirelessly with the terminal device 60. Typically, the server 50 communicates with the terminal device 60 via a wireless LAN (Local Area Network).

[0027] In this example, the terminal device 60 communicates wirelessly with the infusion pumps 70A and 70B and the syringe pumps 70C, 70D, and 70E. Specifically, the terminal device 60 communicates with the infusion pumps 70A and 70B and the syringe pumps 70C, 70D, and 70E via wireless LAN or near field communication (NFC). Note that, hereinafter, any one pump (medical pump) among the infusion pumps 70A and 70B and the syringe pumps 70C, 70D, and 70E will also be referred to as the "pump 70."

[0028] The server 50 transmits the drug library data and the prescription list data of the target patient acquired from the server 20 to the terminal device 60. As a result, the drug library data and the prescription list data of the target patient are stored in the terminal device 60 of the rack system 3.

[0029] When the drug library data in server 50 is updated, the drug library data in terminal device 60 is also updated. As a result, the same drug library data is stored in each of server 20 (FIG. 1), server 50, and terminal device 60. The drug library data in server 20 is master data.

[0030] <B.データ> FIG. 3 is a diagram showing a schematic configuration of the drug library data shown in FIG.

[0031] 3, the drug library data D3 stores at least a flow rate (mL / h) threshold, a dose (mL) threshold, and an administration rate (μg / kg / min) threshold in association with drug identification information. The dose is also referred to as a "planned dose."

[0032] The drug identification information includes, for example, a drug number and a drug name (medicinal liquid name). The flow rate threshold includes an upper limit value for the flow rate and a lower limit value for the flow rate. The dosage threshold includes an upper limit value for the dosage and a lower limit value for the dosage. The administration rate threshold includes an upper limit value for the administration rate and a lower limit value for the administration rate. Note that the drug library data D3 does not necessarily need to store all of the upper limit values ​​and lower limit values ​​for each medicinal liquid.

[0033] As described above, such drug library data D3 is stored in the server 20, the server 50, and the terminal device 60. As described above, when the drug library data D3 of the server 20 is updated, the drug library data D3 of the server 50 and the drug library data D3 of the terminal device 60 are updated.

[0034] FIG. 4 is a diagram showing a schematic configuration of the prescription list data shown in FIG.

[0035] As shown in FIG. 4, the prescription list data D41 includes a patient ID for identifying a target patient and one or more prescription orders #1, #2, #3, . . .

[0036] In this example, each of prescription orders #1, #2, #3, etc. includes drug identification information, a flow rate setting value, and a dosage setting value. The flow rate setting value and dosage setting value are setting values ​​specified by a doctor. These setting values ​​are values ​​input into terminal device 10. Each of prescription orders #1, #2, #3, etc. may also include a dosage rate setting value.

[0037] Examples of a prescription order include "administer 500 mL of physiological saline at 20 mL / h". In this case, the prescription order includes "physiological saline" as drug identification information, "20 mL / h" as the set value of the flow rate, and "500 mL" as the set value of the dosage.

[0038] The pharmacy department checks whether each of the set value of the flow rate (or the set value of the administration rate) and the set value of the dosage is within a predetermined range. If the set value is inappropriate, the pharmacy department requests the responsible physician (the physician who created the prescription list data) to confirm the numerical value and prompts the responsible physician to correct the set value. Therefore, the set value of the flow rate (or the set value of the administration rate) and the set value of the dosage transmitted to the server 50 and the terminal device 60 are usually within the above-mentioned predetermined range.

[0039] Specifically, the above-mentioned predetermined range is defined by at least one of a lower limit value and an upper limit value. In the drug library data D3 (see FIG. 3), such upper limit values and lower limit values are recorded for each drug solution.

[0040] <C. Device Configuration> The specific configurations of the server 50, the terminal device 60, and the pump 70 that constitute the communication system 2 (see FIG. 1) will be described.

[0041] (c1. Server) FIG. 5 is a diagram showing an example of the hardware configuration of the server 50.

[0042] As shown in FIG. 5, the server 50 includes a control unit 51, a communication IF (Interface) 52, and a clock 53. The control unit 51 includes a processor 511 and a memory 512. The processor 511, the memory 512, the communication IF 52, and the clock 53 are typically attached to a motherboard (not shown).

[0043] The memory 512 is configured with a storage medium such as a RAM (Random Access Memory), a ROM (Read Only Memory), an SSD (Solid State Drive), an HDD (Hard Disk Drive), etc. The memory 512 stores prescription list data D41, D42, D43, D44, etc. created for each target patient.

[0044] The prescription list data D41 is data of a patient whose patient ID is "0001." Similarly, the prescription list data D42 is data of a patient whose patient ID is "0002," for example. The prescription list data D43 is data of a patient whose patient ID is "0003," for example.

[0045] The communication IF 52 is an interface for communicating with the servers 30, 40 and the terminal device 60. The communication IF 52 enables the server 50 to acquire the drug library data D3, the prescription list data D41, and the like.

[0046] The clock 53 keeps time. Information on the kept time is sent to the control unit 51.

[0047] The control unit 51 controls the overall operation of the server 50. Specifically, the processor 511 executes an operating system (not shown) and various application programs (not shown) stored in the memory 512, thereby causing the server 50 to perform various operations.

[0048] (c2. Terminal device) FIG. 6 is a diagram showing an example of the hardware configuration of the terminal device 60. As shown in FIG.

[0049] 6, terminal device 60 includes a control unit 61, a touch screen 62, a communication IF (Interface) 63, and a clock 64. Control unit 61 includes a processor 611 and a memory 612. Touch screen 62 includes a touch panel 621 and a display 622. Touch panel 621 is installed on display 622. Processor 611, memory 612, communication IF 63, and clock 64 are typically attached to a motherboard (not shown).

[0050] The memory 612 is configured with a storage medium such as RAM, ROM, flash memory, etc. The memory 612 stores prescription list data D43 for one target patient (in this example, the patient with the patient ID "0003"). In detail, the nurse 9 performs an operation on the terminal device 60 to acquire the prescription list data D43 for the patient with the patient ID "0003" from the server 50, and therefore the prescription list data D43 is stored in the memory 612 of the terminal device 60.

[0051] The terminal device 60 does not need to acquire the prescription list data D43 itself, and may acquire prescription order #1 and prescription order #2 separately in association with the patient ID. At least, the terminal device 60 needs to be able to acquire prescription order #1 and prescription order #2 from the server 50. There are no particular limitations on the user operation during acquisition. In the following explanation, an example will be given in which the terminal device 60 acquires prescription order #1 and prescription order #2 separately.

[0052] The communication IF 63 is an interface for communicating between the server 50 and the plurality of pumps 70. The communication IF 63 enables the terminal device 60 to acquire the drug library data D3 and the prescription list data D43.

[0053] The clock 64 keeps time. Information on the kept time is sent to the control unit 61.

[0054] The touch screen 62 accepts user input and displays various information. The display 622 displays various screens based on the output from the processor 611. When the touch panel 621 accepts user input (typically, a touch operation by the nurse 9) while the screen is displayed, it transmits a signal based on the input to the processor 611.

[0055] The control unit 61 controls the overall operation of the terminal device 60. Specifically, the processor 611 executes an operating system (not shown) and various application programs (not shown) stored in the memory 612, causing the terminal device 60 to perform various operations.

[0056] (c3. Pump) FIG. 7 is a diagram showing an example of the hardware configuration of the pump 70.

[0057] 7, the device includes a control unit 71, a communication IF 72, a clock 73, a drive unit 74, a speaker 75, an alarm lamp 76, and an operation panel 77. The control unit 71 includes a processor 711 and a memory 712. The operation panel 77 includes an operation button 771 and displays 772 and 773. The processor 711, the memory 712, the communication IF 72, and the clock 73 are typically mounted on a motherboard (not shown).

[0058] The memory 712 is composed of a storage medium such as RAM, ROM, flash memory, etc. The memory 712 stores prescription order #1 (see FIG. 6) included in prescription list data D43 for one target patient (in this example, the patient with patient ID "0003"). More specifically, the nurse 9 performed an operation on the terminal device 60 to transmit prescription order #1 of the prescription list data D43 to the pump 70, and therefore prescription order #1 of the prescription list data D43 is stored in the memory 712 of the pump 70.

[0059] Furthermore, the memory 712 stores a flow rate threshold for the medicinal liquid (hereinafter also referred to as "administered medicinal liquid") described in prescription order #1 of the prescription list data D43 and a dosage threshold for the administered medicinal liquid. Note that, as described above, information on one medicinal liquid is described in one prescription order.

[0060] In detail, based on nurse 9 performing an operation on terminal device 60 to send prescription order #1 of prescription list data D43 to pump 70, the threshold flow rate of the administered medicinal liquid and the threshold dosage of the administered medicinal liquid described in prescription order #1 are sent from terminal device 60 to pump 70 and stored in memory 712.

[0061] The control unit 71 controls the overall operation of the pump 70. Specifically, the processor 711 executes an operating system (not shown) and various application programs (not shown) stored in the memory 712, thereby causing the pump 70 to perform various operations.

[0062] The communication IF 72 is an interface for communicating with the terminal device 60. The communication IF 72 enables the pump 70 to acquire prescription order #1, a flow rate threshold, and a dosage threshold.

[0063] The clock 73 keeps time. Information on the kept time is sent to the control unit 71.

[0064] The driving unit 74 is a mechanism for administering the medicinal liquid set in the pump 70 to the patient. The driving unit 74 operates in response to commands from the control unit 71. When the pump 70 is a syringe pump, the driving unit 74 is a mechanism for moving the plunger rod 92 of the syringe 90 (see FIG. 1) within the barrel 91 of the syringe 90. More specifically, the driving unit 74 moves the plunger rod 92 toward the barrel 91 by pressing the flange 921 with the pressing surface 741. This causes the medicinal liquid to be administered to the patient.

[0065] The speaker 75 issues a predetermined notification (audio notification) in response to a command from the control unit 71.

[0066] The alarm lamp 76 issues a predetermined notification (by emitting light) in response to a command from the control unit 71. The alarm lamp 76 is also called an indicator.

[0067] The operation panel 77 accepts operations by the nurse 9 and displays various information. Specifically, the operation buttons 771 accept operations by the nurse 9. The operation buttons 771 typically include multiple operation buttons. An instruction corresponding to the content of the accepted operation is sent from the operation panel 77 to the control unit 71.

[0068] Displays 772, 773 (see FIG. 1) display various screens based on the output from processor 711. For example, the administration rate is displayed on display 772. For example, information such as the flow rate is displayed on display 773.

[0069] FIG. 8 is a diagram showing an example of the operation panel 77 of the pump 70.

[0070] 8, operation panel 77 includes a power button 771A, menu buttons 771B and 771C, a clear accumulated amount button 771D, flow rate setting buttons 771E and 771F, a bolus button 771G, a start button 771H, and a stop or mute button 771I as specific examples of the above-mentioned operation buttons 771. As described above, operation panel 77 includes display 772 and display 773.

[0071] Pump 70 is provided with two alarm lamps 76, one on each side of operation panel 77. The position of alarm lamp 76 is not limited to this position, and may be any position that allows the pump user to see that the lamp is emitting light.

[0072] The power button 771A is a button for turning on and off the power of the pump 70. The menu button 771B is a button for displaying various menus on the display 772. The menu button 771C is a button for displaying various menus on the display 773.

[0073] The integrated quantity clear button 771D is a button for erasing data (log data) of the integrated value of the administered amount of the administered chemical solution from the memory of the pump. The flow rate setting button 771E is a button for increasing the set value of the flow rate of the chemical solution. The flow rate setting button 771F is a button for decreasing the set value of the flow rate of the chemical solution. It is a button for causing the pump 70 to perform a bolus administration.

[0074] The start button 771H is a button for starting the administration of the chemical solution by the pump. When the start button 771H is pressed, the drive unit 74 (FIG. 7) operates. The stop or mute button 771I is a button for stopping the administration of the chemical solution or making the speaker 75 not emit sound. Which function is executed by pressing the stop or mute button 771I is based on the state of the pump 70.

[0075] A touch panel may be installed on the displays 772 and 773. That is, the operation panel 77 may include a touch screen having the display 772 and a touch panel, and a touch screen having the display 773 and a touch panel. According to such a configuration, various items (items within the menu) displayed on the displays 772 and 773 can be selected by a touch operation. Further, the operation panel 77 may separately include physical buttons for selecting items within the menu.

[0076] <D. Flow of Processing> (d1. Transmission of Processing Order and Flow Rate Threshold Value) For ease of explanation, the following description focuses on the prescription list data D43 of a patient whose patient ID is "0003." Also, for ease of explanation, the following description focuses on the infusion pump 70A and the infusion pump 70B among the five pumps 70. The prescription list data D43 and the infusion pumps 70A and 70B are merely examples and are not intended to be limiting.

[0077] In the following example, for the sake of simplicity, the explanation will be focused on the flow rate threshold among the flow rate threshold, dosage threshold, and administration rate threshold shown in Figure 3. Note that the terminal device 60 may also perform similar processing for the lower limit of the flow rate, the dosage threshold, and the administration rate threshold.

[0078] FIG. 9 is a sequence diagram for explaining the flow of processing executed in the communication system 2.

[0079] 9, in sequence SQ1, the server 50 transmits prescription order #1 included in prescription list data D43 to the terminal device 60. As described above, prescription order #1 includes at least the drug identification information and the flow rate setting value (the value set by the doctor).

[0080] In sequence SQ2, the terminal device 60 reads the flow rate threshold of the liquid medicinal #1 described in the received prescription order #1 from the memory 612. Specifically, the terminal device 60 reads the flow rate threshold of the liquid medicinal #1 from the drug library data D3 (see FIG. 6) stored in the memory 612.

[0081] In sequence SQ3, the terminal device 60 associates prescription order #1 with the infusion pump 70A based on the input operation of the nurse 9. That is, the terminal device 60 links prescription order #1 with the infusion pump 70A. In sequence SQ4, the terminal device 60 transmits prescription order #1 and the flow rate threshold of liquid medicine #1 to the infusion pump 70A associated with prescription order #1 based on the input operation of the nurse 9.

[0082] As a result, prescription order #1 and the flow rate threshold for medicinal fluid #1 described in prescription order #1 are set in infusion pump 70A. Pressing the start button triggers infusion pump 70A to start administering medicinal fluid #1 to the patient based on the flow rate setting for medicinal fluid #1, unless the flow rate setting for medicinal fluid #1 is changed by nurse 9 or the like.

[0083] In sequence SQ5, the server 50 transmits prescription order #2 included in the prescription list data D43 to the terminal device 60. As described above, prescription order #2 includes at least the drug identification information and the set value of the flow rate.

[0084] In sequence SQ6, the terminal device 60 reads the flow rate threshold of the liquid medicinal #2 described in the received prescription order #2 from the memory 612. Specifically, the terminal device 60 reads the flow rate threshold of the liquid medicinal #2 from the drug library data D3 stored in the memory 612.

[0085] In sequence SQ7, the terminal device 60 associates prescription order #2 with the infusion pump 70B based on the input operation of the nurse 9. That is, the terminal device 60 links prescription order #2 with the infusion pump 70B. In sequence SQ8, the terminal device 60 transmits prescription order #2 and the flow rate threshold of liquid medicine #2 to the infusion pump 70B associated with prescription order #2 based on the input operation of the nurse 9.

[0086] As a result, prescription order #2 and the flow rate threshold of medicinal fluid #2 described in prescription order #2 are set in infusion pump 70B. Pressing the start button triggers infusion pump 70B to start administering medicinal fluid #2 to the patient based on the flow rate setting of medicinal fluid #2, unless the flow rate setting of medicinal fluid #2 is changed by nurse 9 or the like.

[0087] The rack system 3 can be summarized as follows: The rack system 3 includes a pump 70 (for example, an infusion pump 70A) capable of administering a medicinal liquid to a patient, and a terminal device 60 capable of communicating with the pump 70 and storing drug library data D3 in which a flow rate threshold is associated with identification information for each of a plurality of medicinal liquids.

[0088] The terminal device 60 acquires a prescription order (e.g., prescription order #1) from the server 50, which is an external device of the rack system 3, including identification information of an administration liquid (e.g., liquid #1) to be administered to a patient (e.g., a patient with patient ID "0003") from among the plurality of administration liquids, and a set value of the flow rate of the administration liquid set for the patient. The terminal device 60 acquires a flow rate threshold of the administration liquid from the drug library data D3 (specifically, reads out the threshold). The terminal device 60 transmits the prescription order and the flow rate threshold of the administration liquid to the pump 70.

[0089] With this configuration, there is no need to transmit the drug library data D3 to each pump 70. Therefore, there is no need to update the medicinal liquid data in each pump 70. Furthermore, each pump 70 can obtain not only the prescription order but also the flow rate threshold of the administered medicinal liquid set in the pump 70.

[0090] (d2. Log Acquisition) For convenience of explanation, the following description will be given taking the infusion pump 70A as an example among the multiple pumps 70. In this example, as shown in sequence SQ3 of FIG. 9, prescription order #1 and the infusion pump 70A are associated (linked) with each other based on the input operation of the nurse 9.

[0091] In the following, first, a case where such association is made before the infusion pump 70A is operated will be described with reference to FIGS. 10 and 11. That is, a case where administration is started after association is made will be described. Specifically, a case where the start button 771H (see FIG. 9) is pressed after association is made will be described. Next, a case where association is made after the infusion pump 70A is operated will be described with reference to FIG. 12. In more detail, a case where the above association is made in the terminal device 60 during administration will be described.

[0092] In this embodiment, the log includes time information. The log includes, for example, information on the time when an event such as pressing a button occurred. In this example, the log includes at least an operation log based on user operations and a log of the above-mentioned integrated values. The operation log includes at least an operation log indicating the start of medicinal liquid administration, an operation log indicating the completion of medicinal liquid administration, and an operation log related to an operation to change the flow rate setting value. The integrated value is the total amount of medicinal liquid administered from immediately after the start of medicinal liquid administration to the time the log is taken.

[0093] 10 is a sequence diagram illustrating the recording and transmission of logs when prescription order #1 is associated with the infusion pump 70A before the start button 771H is pressed. That is, FIG. 10 illustrates a case where medication is administered according to the correct procedure.

[0094] 10, in sequence SQ11, the terminal device 60 associates prescription order #1 with the infusion pump 70A based on a user operation. The process of sequence SQ11 corresponds to sequence SQ3 in FIG.

[0095] In sequence SQ12, the terminal device 60 sends prescription order #1 to the infusion pump 70A. Specifically, the terminal device 60 also sends the flow rate threshold of liquid medicine #1 to the infusion pump 70A, as shown in sequence SQ4 of FIG.

[0096] In sequence SQ13, the infusion pump 70A accepts pressing of the start button 771H on the operation panel 77. Upon accepting the pressing of the start button 771H, the infusion pump 70A stores an administration start operation log in the memory 712 in sequence SQ14, and starts administration at the flow rate (i.e., the set value) specified in prescription order #1 in sequence SQ15.

[0097] When infusion pump 70A starts administering medication, in sequence SQ16 it periodically records the integrated value of the administered amount of medicinal fluid #1 as a log, correlating it with the time. In this example, infusion pump 70A records the log of the integrated value at a predetermined cycle Ta. After infusion of medicinal fluid starts at sequence SQ15, when a predetermined period (cycle Tb) has elapsed, in sequence SQ17, infusion pump 70A transmits the operation log of the start of administration and the log of the integrated value that has not yet been transmitted to terminal device 60. Thereafter, as shown in sequences SQ17, SQ18, SQ19, and SQ20, infusion pump 70A transmits the log of the integrated value that has not yet been transmitted to terminal device 60 at predetermined cycles Tb (Tb≧Ta).

[0098] Fig. 11 is a diagram for explaining the period Ta for recording logs and the period Tb for transmitting logs, in which the period Tb is longer than the period Ta.

[0099] 11, when the start button 771H is pressed at time t0, the infusion pump 70A stores an operation log of the start of administration. After a time Ta has elapsed from time t0, the integrated value of the administered dose at that timing is recorded. Thereafter, the integrated value of the administered dose at that timing is recorded each time the cycle Ta arrives.

[0100] After a time Tb has elapsed since time t0, the infusion pump 70A transmits the logs recorded between time t0 and time t0+Tb to the terminal device 60. Thereafter, every time the cycle Tb arrives, the infusion pump 70A transmits any unsent logs to the terminal device 60.

[0101] When Ta and Tb are set to the same value, a log of one integrated value is transmitted in one data transmission to the terminal device 60. Ta and Tb are set appropriately.

[0102] The terminal device 60 can know the time when the administration of the medicinal liquid #1 started by obtaining the administration start operation log from the infusion pump 70A, and can therefore notify the server 20, which records the electronic medical record, of the time when the administration started.

[0103] Furthermore, the terminal device 60 can periodically acquire a log of the integrated value from the infusion pump 70A. The log of the integrated value includes time information. Therefore, the terminal device 60 can determine the administration status (progression of the integrated value) of the medicinal fluid #1 in the infusion pump 70A. For example, the terminal device 60 can determine the actual flow rate even when the set value of the flow rate is changed. The terminal device 60 can notify the server 20, which records the electronic medical records, of this information.

[0104] 12 is a sequence diagram illustrating the recording and transmission of logs when prescription order #1 is associated with the infusion pump 70A after the start button 771H is pressed. That is, FIG. 12 illustrates a case where medication is administered in an incorrect procedure.

[0105] 12, in sequence SQ101, the infusion pump 70A accepts pressing of the start button 771H on the operation panel 77. Upon accepting the pressing of the start button 771H, the infusion pump 70A stores an administration start operation log in the memory 712 in sequence SQ102, and starts administration at a set flow rate in sequence SQ103. Typically, the infusion pump 70A starts administration at a flow rate value directly input into the infusion pump 70A by the nurse 9 or the like.

[0106] When the infusion pump 70A starts administering medication, in sequence SQ104, it periodically records the cumulative dose of the medicinal fluid #1 as a log, correlating it with the time. The infusion pump 70A records the log of the cumulative dose at a predetermined interval, Ta. At this point, the infusion pump 70A is not associated with prescription order #1. Therefore, the infusion pump 70A has not received any prescription orders, including prescription order #1, from the terminal device 60. Therefore, the infusion pump 70A does not transmit the stored log.

[0107] In sequence SQ105, the terminal device 60 associates prescription order #1 with the infusion pump 70A based on user operation. In sequence SQ106, the terminal device 60 sends prescription order #1 to the infusion pump 70A. As a result, the infusion pump 70A acquires prescription order #1. Thereafter, in sequence SQ107, medication begins at the flow rate specified in prescription order #1.

[0108] After starting administration at the flow rate specified in prescription order #1 in sequence SQ107, and a predetermined period (cycle Tb) has elapsed, in sequence SQ108, the infusion pump 70A transmits an operation log of the administration start and a log of the untransmitted integrated value to the terminal device 60. As a result of associating the infusion pump 70A with prescription order #1, the infusion pump 70A begins transmitting logs.

[0109] More specifically, in sequence SQ108, all logs that have not been transmitted in the past are transmitted to the terminal device 60. Specifically, the infusion pump 70A transmits to the terminal device 60 the operation log recorded in sequence SQ102, the log of integrated values ​​of 1 or more recorded in sequence SQ104, the log of integrated values ​​from sequence SQ107 onwards, etc.

[0110] Thereafter, as shown by sequences SQ109, SQ110, and SQ111, the infusion pump 70A transmits the log of the untransmitted integrated values ​​to the terminal device 60 at predetermined intervals Tb (Tb≧Ta).

[0111] In this way, the infusion pump 70A starts sending the log on the condition that the terminal device 60 has associated the prescription order #1 with the infusion pump 70A.

[0112] (d3. Summary) The processing described above with reference to FIGS. 1 to 12 (particularly FIGS. 10 to 12) can be summarized as follows.

[0113] The rack system 3 further includes a terminal device 60 that stores prescription order #1 for a medicinal liquid to be administered to a patient, and an infusion pump 70A that, upon receiving a first operation (in this example, pressing the start button 771H), starts administering the medicinal liquid (in this example, medicinal liquid #1) to the patient and recording a log related to the administration. The log is used to record the administration status of the medicinal liquid in the electronic medical record of the server 20. The log is transmitted to the server 20 that stores the electronic medical record in order to record the administration status of the medicinal liquid in the electronic medical record. The log is transmitted to the server 20 that stores the electronic medical record via the server 50.

[0114] Upon receiving the second operation (input operation by the nurse 9 in this example), the terminal device 60 executes a process of associating prescription order #1 with the infusion pump 70A and a process of transmitting prescription order #1 to the infusion pump 70A. Specifically, the "second operation" includes, for example, an operation by a nurse or the like to designate the infusion pump 70A as the pump 70 to which prescription order #1 is to be sent on a pump selection screen (a screen displayed on the terminal device 60) on which an image showing a plurality of pumps 70 is displayed, and an operation to transmit prescription order #1.

[0115] When the infusion pump 70A receives the prescription order #1, it administers the drug solution to the patient based on the prescription order #1 on the condition that it has received the above first operation. When the second operation is performed before the first operation (in the case of FIG. 10), the infusion pump 70A starts the process of periodically transmitting the log after the first operation to the terminal device 60. When the first operation is performed before the second operation (in the case of FIG. 12), the infusion pump 70A transmits the log before the second operation to the terminal device 60 on the condition that the second operation has been performed, and starts the process of periodically transmitting the log after the second operation to the terminal device 60.

[0116] According to such a configuration, even when the association between the infusion pump 70A and the prescription order #1 is performed in the terminal device 60 after the administration of the drug solution #1 is started in the infusion pump 70A, the infusion pump 70A can transmit the log regarding the administration of the drug solution #1 to the terminal device 60 without omission.

[0117] Note that the log includes at least one of the reception process of the first operation, the integrated value of the administered amount of the administered drug solution, and the change information of the flow rate of the administered drug solution.

[0118] In the above, the infusion pump 70A has been described as an example, but the processes in FIGS. 10 to 12 are also performed in the same manner as the infusion pump 70A in other pumps 70 (infusion pump 70B, syringe pumps 70C, 70D, 70E).

[0119] <E. Modified Example> (e1. First Modified Example) In addition to each process shown in the above embodiment, the rack system 3 may further execute the following process.

[0120] As described above, the pump 70 communicates with the terminal device 60 wirelessly. Therefore, the communication may be more unstable than in a wired communication. Therefore, in this modification, a case where communication between the infusion pump 70A and the terminal device 60 is temporarily interrupted while the infusion pump 70A is administering medication will be described. In detail, a log transmission process when the infusion pump 70A is unable to communicate with the terminal device 60 will be described.

[0121] FIG. 13 is a sequence diagram for explaining the transmission of a log from the infusion pump 70A to the terminal device 60. In FIG.

[0122] 13, in sequence SQ201, the infusion pump 70A transmits a log of untransmitted integrated values ​​to the terminal device 60. Thereafter, in sequences SQ202 and SQ203, the infusion pump 70A transmits a log of untransmitted integrated values ​​to the terminal device 60 at a period Tb.

[0123] Assume that a communication failure occurs between the infusion pump 70A and the terminal device 60 after sequence SQ203. During the period from when the communication failure occurs until communication is restored (the period during which communication is interrupted), the terminal device 60 cannot receive the log from the infusion pump 70A. That is, the terminal device 60 cannot obtain the log of the integrated value transmitted by the infusion pump 70A in sequences SQ204 to SQ207.

[0124] In this case, the infusion pump 70A does not receive a notification (response) indicating that the log has been received from the terminal device 60. Therefore, the infusion pump 70A can determine that the log has not been received by the terminal device 60.

[0125] When communication is restored, in sequence SQ208, the infusion pump 70A transmits to the terminal device 60 the log of the integrated values ​​for the current cycle in addition to the logs of the integrated values ​​that it attempted to transmit in sequences SQ204 to SQ207 (logs that the terminal device 60 was unable to receive). Thereafter, in sequences SQ209 and S210, the infusion pump 70A transmits the logs of the integrated values ​​that have not yet been transmitted to the terminal device 60 according to the cycle Tb.

[0126] As described above, the infusion pump 70A wirelessly communicates with the terminal device 60. If communication with the terminal device 60 is interrupted after the infusion pump 70A starts a process of periodically transmitting logs to the terminal device 60, the infusion pump 70A transmits the logs for the period during which communication was interrupted to the terminal device 60 when the communication is restored.

[0127] With this configuration, the terminal device 60 can acquire a log of the time when communication is interrupted. Therefore, according to the network system 1, even if communication between the terminal device 60 and the infusion pump 70A is interrupted, the log of the time can be transmitted to the electronic medical record server 20. Therefore, by using the rack system 3, it is possible to record information in the electronic medical record without omission.

[0128] Although the above description has been given using the infusion pump 70A as an example, the processing of Figure 13 is also performed in the other pumps 70 (infusion pump 70B, syringe pumps 70C, 70D, 70E) in the same manner as infusion pump 70A.

[0129] (e2. Second modified example) When the infusion pump 70A transmits a log of an integrated value or the like to the terminal device 60 immediately after recording the log in the memory 712, it is preferable that the terminal device 60 executes the following process. Specifically, when the cycles Ta and Tb are the same and the infusion pump 70A is configured to transmit the log immediately after obtaining it, it is preferable that the terminal device 60 be configured as follows.

[0130] (1) The terminal device 60 changes the time information included in the log received from the infusion pump 70A from the time information based on the clock 73 of the infusion pump 70A to the time information of the reception time of the log based on the clock 64 of the terminal device 60. The terminal device 60 replaces the time information of the log with the time information of the terminal device 60. In this way, the time of the log is updated (adjusted) with the time based on the clock of the terminal device 60.

[0131] As a result, even if the times on the clocks of the pumps 70 do not match (for example, they are not synchronized), the variations in time relative to the reference time (in this example, the time of the clock 64 of the terminal device 60) caused by the individual clocks 73 can be ignored. Therefore, the rack system 3 can improve the accuracy of the time information in the log.

[0132] (2) However, when communication is temporarily interrupted as in the first modified example, the terminal device 60 does not change the time information of the log of the integrated value received immediately after communication is restored (specifically, the time information of the log of the integrated value received in sequence SQ208) from the time information based on the clock 73 of the infusion pump 70A to the time information of the log reception time based on the clock 64 of the terminal device 60. The reason for this is as follows.

[0133] If the time information of the log of the integrated value received in sequence SQ208 is updated to the time information of the reception time of that log based on the clock 64 of the terminal device 60, all of the time information of the logs transmitted in sequence SQ208 will be the same. The logs transmitted in sequence SQ208 include the logs of the integrated value that were attempted to be transmitted in sequences SQ204 to SQ207 (logs that the terminal device 60 was unable to receive). Therefore, if the time information of the logs is updated based on the reception time, the accuracy of the time information of the logs will decrease. For this reason, the terminal device 60 does not change the time information of the log of the integrated value received in sequence SQ208 to the time information of the reception time of that log.

[0134] (3) The time information of the log received immediately after communication is restored (in the example of FIG. 13, the time information of the log of the integrated value received in sequence SQ208) may be corrected using the following method. Specifically, part of the time information of the log received immediately after communication is restored may be corrected using the following method.

[0135] FIG. 14 is a flow diagram for explaining correction of time information of a log.

[0136] 14, in step S1, the terminal device 60 starts acquiring (receiving) the log transmitted from the infusion pump 70A. In step S2, the terminal device 60 determines whether a communication failure has occurred between the terminal device 60 and the infusion pump 70A.

[0137] If no communication failure has occurred (NO in step S2), in step S3, the terminal device 60 changes the time information included in the newly acquired log to a time method based on the clock 64 of the terminal device 60. That is, the terminal device 60 changes the time information of the log as described in the above embodiment.

[0138] If it is determined that a communication failure has occurred (YES in step S2), the terminal device 60 determines in step S5 whether communication with the infusion pump 70A has been restored. If it is determined that communication has not been restored (NO in step S5), the terminal device 60 proceeds to step S5. If it is determined that communication has been restored (YES in step S5), the terminal device 60 acquires a log of the period during which communication was interrupted from the infusion pump 70A in step S6.

[0139] In step S7, the terminal device 60 calculates the difference Δt between the time indicated by the clock 73 of the infusion pump 70A and the time indicated by the clock 64 of the terminal device 60 based on the time information included in the log received immediately after recovery. In step S8, the terminal device 60 corrects the time information included in the log for the period when communication with the infusion pump 70A was interrupted based on the difference Δt.

[0140] In step S4, the terminal device 60 determines whether or not a log of operation completion has been acquired from the infusion pump 70A. The terminal device 60 acquires the log of operation completion based on pressing the stop or mute button 771I on the infusion pump 70A. If the terminal device 60 determines that the log of operation completion has been acquired (YES in step S4), it terminates the series of processes. If the terminal device 60 determines that the log of operation completion has not been acquired (NO in step S4), it proceeds to step S2.

[0141] FIG. 15 is a diagram for explaining the processes in steps S7 and S8 in FIG.

[0142] As shown in Figure 15, if the communication status with the infusion pump 70A is good at the time the infusion pump 70A sends the log, the terminal device 60 changes the time information of the received log to information about the time the log was received based on the clock 64 of the terminal device 60.

[0143] For example, for a log with log identification information "0001", the terminal device 60 changes the time information of the log from time t1 to time t1', which is the time when the terminal device 60 received the log. Similarly, the terminal device 60 changes times t2 to t7 to times t2' to t7', respectively.

[0144] It is assumed that a communication failure occurs between the terminal device 60 and the infusion pump 70A after that, and that the communication failure is resolved after the log with log identification information “0010” is sent and before the log with log identification information “0011” is sent.

[0145] In this case, the terminal device 60 receives the log with log identification information "0008", the log with log identification information "0009", the log with log identification information "0010", and the log with log identification information "0011" at the same time. In this example, the terminal device 60 receives four logs simultaneously at time t11'. In this example, the time information included in the log with log identification information "0008", the time information included in the log with log identification information "0009", the time information included in the log with log identification information "0010", and the time information included in the log with log identification information "0011" are t8, t9, t10, and t11, respectively.

[0146] The terminal device 60 calculates the difference Δt between the time indicated by the clock 73 of the infusion pump 70A and the time indicated by the clock 64 of the terminal device 60 based on the time information (t11) included in the log received immediately after the recovery (corresponding to step S7 in FIG. 14). Typically, the terminal device 60 calculates the difference Δt by subtracting the time t11 from the time t11'.

[0147] Furthermore, the terminal device 60 corrects the time information included in the log for the period when communication with the infusion pump 70A was interrupted based on the deviation Δt (corresponding to step S8 in FIG. 14). Typically, the terminal device 60 adds the calculated deviation Δt (= t11' - t11) to each of the times t8, t9, and t10. As a result, for example, for the log with log identification information "0008," the terminal device 60 changes the time information of the log from time t8 to time t8 + (t11' - t11).

[0148] Among the logs transmitted in sequence SQ208, the time information (t11) included in the log with log identification information "0011" is changed to information (t11') of the reception time at the terminal device 60 as usual.

[0149] As described above, when communication with the infusion pump 70A is not interrupted, the terminal device 60 changes the time information included in the log received from the infusion pump 70A from the time information based on the clock 73 of the infusion pump 70A to the time information of the log reception time based on the clock 64 of the terminal device 60. When communication with the infusion pump 70A is interrupted and the communication is restored, the terminal device 60 calculates the difference Δt between the time indicated by the clock 73 of the infusion pump 70A and the time indicated by the clock 64 of the terminal device 60 based on the time information included in the log received immediately after the recovery and the time information of the log reception time based on the clock 64 of the terminal device 60. The terminal device 60 corrects the time information included in the log for the period when communication was interrupted based on the difference Δt.

[0150] This configuration improves the accuracy of the time information in the log received immediately after communication is restored. This correction includes not only the correction of the time information in the log of the integrated value but also the correction of the time information in the operation log.

[0151] Although the above description has been given using the infusion pump 70A as an example, the processing of Figure 14 is also performed in the other pumps 70 (infusion pump 70B, syringe pumps 70C, 70D, 70E) in the same manner as infusion pump 70A.

[0152] (e3. Third variant) Although FIG. 9 illustrates an example in which the upper and lower limit values ​​of the flow rate are transmitted to the pump 70, the terminal device 60 may be configured to transmit either one of the upper and lower limit values.

[0153] 9 has been described with reference to an example in which only the flow rate threshold is transmitted to the pump 70 out of the three thresholds, namely, the "flow rate threshold," the "dosage threshold," and the "administration rate threshold." However, the present invention is not limited to this. It is sufficient that the terminal device 60 is configured to transmit at least one of the three thresholds to the pump 70. For example, the terminal device 60 may be configured to transmit the flow rate threshold and the dosage threshold to the pump 70.

[0154] Similar to the flow rate threshold, the terminal device 60 may be configured to transmit at least one of the upper and lower limit values ​​of the dosage threshold to the pump 70. Similarly, the terminal device 60 may be configured to transmit at least one of the upper and lower limit values ​​of the administration rate threshold to the pump 70.

[0155] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the scope of the claims, and it is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0156] 1 network system, 2 communication system, 3 rack system, 10, 60 terminal device, 20, 30, 40, 50 server, 51, 61, 71 control unit, 53, 64, 73 clock, 62 touch screen, 70A, 70B infusion pump, 70C, 70D, 70E syringe pump, 74 drive unit, 75 speaker, 76 alarm lamp, 77 operation panel, 90 syringe, 91 barrel, 92 plunger rod, 511, 611, 711 processor, 512, 612, 712 memory, 621 touch panel, 622, 772, 773 display, 741 pressing surface, 771 operation button, 771A power button, 771B, 771C menu button, 771D accumulated amount clear button, 771E, 771F Flow rate setting button, 771G Bolus button, 771H Start button, 771I Stop or Mute button, 921 Flange, D3 Drug Library data, D41, D42, D43, D44 Prescription list data.

Claims

1. an information processing device that stores prescription orders for medicinal liquids to be administered to patients; a pump that starts administering the medicinal liquid to the patient and recording a log related to the administration based on receiving a first operation, the log being transmitted to an external device that stores an electronic medical record in order to record the administration status of the medicinal liquid in the electronic medical record; the information processing device executes a process of associating the prescription order with the pump and a process of transmitting the prescription order to the pump based on the reception of the second operation; The pump When the prescription order is received, the administration liquid is administered to the patient based on the prescription order, on condition that the first operation has been accepted; If the second operation is performed before the first operation, a process of periodically transmitting the log from the first operation onward to the information processing device is started; A system that, if the first operation is performed before the second operation, sends the log before the second operation to the information processing device on the condition that the second operation has been performed, and starts a process of periodically sending the log from the second operation onwards to the information processing device.

2. The system according to claim 1 , wherein the log includes at least one of a process of accepting the first operation, an integrated value of the administered amount of the administered medicinal liquid, and information on a change in the flow rate or administration rate of the administered medicinal liquid.

3. the pump wirelessly communicates with the information processing device; The system described in claim 1 or 2, wherein if communication with the information processing device is interrupted after the pump starts the process of periodically sending the log to the information processing device, when the communication is restored, the pump sends the log for the period during which communication was interrupted to the information processing device.

4. the pump includes a first clock; the log includes time information based on the time indicated by the first clock; The information processing device includes: a second clock; If the communication is not interrupted, the time information included in the log received from the pump is changed from the time information based on the first clock to the time information of the reception time of the log based on the second clock; When the communication is interrupted and then restored, a difference between the time indicated by the first clock and the time indicated by the second clock is calculated based on time information included in the log received immediately after the restoration and time information of the reception time of the log based on the second clock; The system according to claim 3 , wherein time information included in the log for the period during which communication was interrupted is corrected based on the discontinuity.

5. A method for a system including an information processing device that stores a prescription order for a medicinal liquid to be administered to a patient, and a pump that starts administering the medicinal liquid to the patient and recording a log related to the administration based on receiving a first operation, wherein the log is transmitted to an external device that stores an electronic medical record in order to record the administration status of the medicinal liquid in the electronic medical record; a step of executing, by the information processing device, a process of associating the prescription order with the pump and a process of transmitting the prescription order to the pump based on reception of a second operation; When the pump receives the prescription order, administering the medicinal liquid to the patient based on the prescription order on condition that the first operation has been accepted; When the second operation is performed before the first operation, the pump starts a process of periodically transmitting the log from the first operation onward to the information processing device; A method comprising a step in which, if the first operation is performed before the second operation, the pump sends the log before the second operation to the information processing device, on the condition that the second operation has been performed, and starts a process of periodically sending the log from the second operation onwards to the information processing device.

Images