Systems and methods

Abstract

To enable the first operation to start administering liquid medicine in a pump to be recorded with good accuracy.SOLUTION: An infusion pump 70A starts, upon accepting a first operation, administering liquid medicine and recording logs related to administration, and finishes, upon accepting a second operation, administering liquid medicine and recording logs. The logs are used for recording administration states in an electronic medical chart. A terminal device 60 transmits, upon accepting prescribed input, a prescription order to the infusion pump 70A. When the prescription order is received, the infusion pump 70A administers liquid medicine to a patient on the basis of the prescription order, on condition that the first operation has been accepted. Each time the first operation is accepted, the infusion pump 70A inquires of a user whether or not the first operation is a first start operation in the prescription order to administer liquid medicine. Upon accepting a third operation after inquiring, the infusion pump 70A stores the first operation as a first start operation in the prescription order to administer liquid medicine.SELECTED DRAWING: Figure 14

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] After the drug solution is loaded into the pump and the button to start the pump is pressed, the pump may be stopped due to an abnormality or the like. In this case, the button to start the pump is pressed again to resume medication. In this way, the button to start the pump may be pressed multiple times.

[0006] There is also a demand for an operation log (also called an "execution record") relating to the administration of medicinal fluids by a pump to be automatically written to an electronic medical record stored in a server via an information processing device.

[0007] Therefore, in order to improve the accuracy of the contents recorded in the electronic medical record, it is necessary to accurately record the initial administration start operation for the drug solution in the pump.

[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 accurately record the initial administration start operation of a medicinal liquid in a pump. [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, starts administering the medicinal liquid to the patient and recording a log related to the administration, and, upon receiving a second operation, ends administering the medicinal liquid to the patient and recording the log. 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 predetermined input, the information processing device executes a process to send a prescription order to the pump. When the pump receives the prescription order, the pump administers the medicinal liquid to the patient based on the prescription order, provided that the first operation has been accepted. Each time the pump accepts the first operation, the pump issues a first notification to inquire of the user whether the first operation is the first administration start operation for the medicinal liquid in the prescription order. Upon accepting a third operation after the first notification, the pump stores the first operation as the first administration start operation for the medicinal liquid in the prescription order.

[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, and, upon receiving a second operation, ends administering the medicinal liquid to the patient and recording the log. The log is 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 executing a process to send a prescription order to a pump based on receipt of a predetermined input; when the pump receives the prescription order, administering the medicinal liquid to the patient based on the prescription order on the condition that a first operation has been received; each time the pump receives the first operation, issuing a first notification to inquire about whether the first operation is the first administration start operation for the medicinal liquid in the prescription order; and, based on receipt of a third operation after the first notification, the pump storing the first operation as the first administration start operation for the medicinal liquid in the prescription order. [Effects of the Invention]

[0011] According to the present disclosure, it is possible to accurately record the initial administration start operation of a medicinal liquid in a pump. [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 diagram for explaining the flow of processing when the start button and the stop button are each operated twice during treatment based on a prescription order. [Figure 14] FIG. 2 is a flow chart for explaining the processing performed by the infusion pump. [Figure 15] FIG. 10 is a diagram showing an example of a screen prompting a confirmation operation regarding the start of administration. [Figure 16] FIG. 10 is a diagram showing an example of a screen prompting a confirmation operation regarding the end of administration. [Figure 17] FIG. 10 is a flowchart illustrating a process performed by an infusion pump in a modified example. [Figure 18] FIG. 10 is a diagram showing an example of a menu screen displayed on the infusion pump. [Figure 19] FIG. 10 is a diagram illustrating an operation screen that is displayed after one item is selected on the menu screen. [Figure 20] FIG. 10 is a flowchart illustrating the process performed by the infusion pump in another modified example. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present disclosure will be described while referring 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.

[0014] Hereinafter, each embodiment of the present disclosure will be described while referring 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 a network system 1 according to the present embodiment.

[0016] As shown in FIG. 1, the network system 1 includes a terminal device 10, a server 20 that records electronic medical records, 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 and 70B, and a plurality of syringe pumps 70C, 70D, and 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 in a wired manner so as to be communicable. The server 20 is typically connected to the terminal device 10 and the server 30 in a wired manner so as to be communicable. The server 30 is typically connected to the server 20 and the server 50 in a wired manner so as to be communicable.

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

[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 will soon 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 the prescription orders #1, #2, #3... includes drug identification information, a set value of the flow rate, and a set value of the dosage. The set value of the flow rate and the set value of the dosage are the set values specified by the doctor. The set values are the values input in the terminal device 10. Each of the prescription orders #1, #2, #3... may include a set value of the administration rate.

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

[0038] The pharmacy 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 requests the doctor in charge (the doctor who created the prescription list data) to confirm the numerical value and urges the doctor in charge 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 the lower limit value and the upper limit value. In the drug library data D3 (see Figure 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 Figure 1) will be described.

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

[0042] 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 mounted on 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 amount clear button 771D is a button for erasing the 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, it becomes possible to select various items (items within the menu) displayed on the displays 772 and 773 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. Record the start and end times of administration) Incidentally, medication is started when the nurse 9 or the like presses the start button 771H (sequences SQ13 and SQ15 in FIG. 10), and the nurse 9 or the like may press the stop or mute button 771I (FIG. 9) for some reason (for example, the occurrence of an abnormality). In this case, to resume medication, the nurse 9 or the like will press the start button 771H again. For ease of explanation, the stop or mute button 771I will also be referred to as the "stop button 771I" below.

[0113] FIG. 13 is a diagram for explaining the flow of processing when the start button 771H and the stop button 771I are each operated twice during treatment based on prescription order #1.

[0114] As shown in Figure 13, after the medicinal liquid #1 is set in the infusion pump 70A, the start button 771H is pressed. This causes the infusion pump 70A to start administering the medicinal liquid #1. When the infusion pump 70A issues an alarm, the nurse 9 or the like presses the stop button 771I. Then, processing to eliminate the cause of the alarm is performed.

[0115] Once the alarm has been dealt with, the nurse 9 or the like presses the start button 771H again. Thereafter, when the nurse 9 or the like determines that the administration of medicinal liquid #1 is complete, the nurse 9 or the like presses the stop button 771I again. After pressing the stop button 771I, the nurse 9 or the like removes medicinal liquid #1 from the infusion pump 70A. Typically, the nurse 9 or the like removes the container containing medicinal liquid #1 from the infusion pump 70A.

[0116] In this way, when the infusion pump 70A administers a medication based on one prescription order, the start button 771H of the infusion pump 70A may be operated multiple times. Similarly, when the infusion pump 70A administers a medication based on one prescription order, the stop button 771I of the infusion pump 70A may be operated multiple times.

[0117] If the start button 771H is pressed multiple times, the infusion pump 70A stores an administration start operation log for each press of the start button 771H. That is, for one prescription order #1 associated with the infusion pump 70A, the infusion pump 70A stores multiple administration start operation logs in the memory 712.

[0118] Therefore, in order to store accurate logs in the electronic medical record, the infusion pump 70A must record which of multiple administration start operation logs represents the actual administration start. That is, the infusion pump 70A must keep a record so that it can be determined later when the "initial administration start operation for medicinal fluid #1" was performed.

[0119] Similarly, for prescription order #1, infusion pump 70A stores multiple administration completion operation logs in memory 712. Therefore, in order to store accurate logs in the electronic medical record, infusion pump 70A must record which of the multiple administration completion operation logs represents the true administration completion. In other words, infusion pump 70A must keep a record so that it can be determined later when the "final administration completion operation for medicinal liquid #1" was performed.

[0120] In particular, if the association of prescription order #1 with the infusion pump 70A is established after the start button 771H is pressed (FIG. 12), the initial administration start operation of the administered medicinal fluid is performed before the infusion pump 70A receives prescription order #1. Therefore, the terminal device 60 and the like cannot determine when the initial administration start operation of medicinal fluid #1 was performed.

[0121] Furthermore, it is difficult for the terminal device 60 etc. to determine at what timing the pressing of the stop button 771I is the final operation to end administration of the medicinal liquid #1, because there is a possibility that the start button 771H will be pressed again after the pressing of the stop button 771I.

[0122] Therefore, the infusion pump 70A of this embodiment executes the following process.

[0123] FIG. 14 is a flow chart for explaining the process performed by the infusion pump 70A.

[0124] As shown in FIG. 14, in step S1, the infusion pump 70A determines whether or not a press of the start button 771H has been received. If it is determined that a press of the start button 771H has been received (YES in step S1), the infusion pump 70A inquires of the user of the infusion pump 70A in step S2 whether or not the press of the start button 771H is the first operation to start administration of the administered medicinal liquid in prescription order #1. Typically, the infusion pump 70A displays a screen on the display 773 (FIG. 9) requesting a confirmation operation regarding the start of administration. Specifically, if a positive determination is made in step S1, the infusion pump 70A automatically proceeds to step S2 without any user operation. If it is determined that a press of the start button 771H has not been received (NO in step S1), the infusion pump 70A returns the process to step S1.

[0125] In step S3, the infusion pump 70A determines whether an operation specifying that this is the first administration start operation has been received. Specifically, the infusion pump 70A determines whether an item (typically, an image) for specifying that this is the first administration start operation has been selected on the screen requesting a confirmation operation.

[0126] If it is determined that the operation has been accepted (YES in step S3), in step S4, the infusion pump 70A records the pressing of the start button 771H as the initial operation to start administration of the administered medicinal liquid. Specifically, the infusion pump 70A records an operation log based on the pressing operation as an operation log for starting administration in the memory 712. If it is determined that the operation has not been accepted (NO in step S3), the infusion pump 70A proceeds to step S6.

[0127] In step S5, the infusion pump 70A starts administering the liquid medicinal fluid #1 at the flow rate specified in prescription order #1. In step S6, the infusion pump 70A periodically records the cumulative dose of the liquid medicinal fluid #1 in association with the time. That is, as described above, the infusion pump 70A periodically records the cumulative dose log Ta.

[0128] In step S7, the infusion pump 70A determines whether or not the user of the infusion pump 70A has pressed the stop button 771I. If it is determined that the pressing operation has been received (YES in step S7), the infusion pump 70A inquires of the user of the infusion pump 70A in step S8 whether or not the pressing of the stop button 771I is the final operation to terminate administration of the administered medicinal liquid in prescription order #1. Typically, the infusion pump 70A displays a screen on the display 773 (FIG. 9) requesting a confirmation operation regarding the termination of administration. Specifically, if a positive determination is made in step S7, the infusion pump 70A automatically proceeds to step S8 without any user operation. If it is determined that the pressing operation has not been received (NO in step S7), the infusion pump 70A proceeds to step S6.

[0129] In step S9, the infusion pump 70A determines whether an operation specifying that this is the final administration end operation has been accepted. Specifically, the infusion pump 70A determines whether an item (typically, an image) for specifying that this is the final administration end operation has been selected on the screen prompting for a confirmation operation.

[0130] If it is determined that the operation has been accepted (YES in step S9), in step S10, the infusion pump 70A records the pressing of the start button 771H as the final administration termination operation of the administered medicinal liquid. Specifically, the infusion pump 70A records an operation log based on the pressing operation as an administration termination operation log in the memory 712. If it is determined that the operation has not been accepted (NO in step S9), the infusion pump 70A proceeds to step S1.

[0131] 15 is a diagram showing an example of a screen prompting a user to confirm the start of administration. As shown in FIG. 15, the infusion pump 70A displays a screen 7010 on the display 773 upon receiving a press of the start button 771H. The screen 7010 includes selectable object images 7011 and 7012. The screen 7010 is typically displayed as a pop-up.

[0132] When the object image 7011 is selected by a user operation (YES in step S3 in FIG. 14), the infusion pump 70A records the pressing of the start button 771H as the first administration start operation of the administered medicinal liquid (step S4 in FIG. 14). When the object image 7012 is selected by a user operation (NO in step S3 in FIG. 14), the infusion pump 70A does not record the pressing of the start button 771H as the first administration start operation of the administered medicinal liquid.

[0133] 16 is a diagram showing an example of a screen prompting a user to confirm the end of administration. As shown in FIG. 16, the infusion pump 70A displays a screen 7020 on the display 773 upon receiving a press of the stop button 771I. The screen 7020 includes selectable object images 7021 and 7022. The screen 7020 is typically displayed as a pop-up.

[0134] When the object image 7021 is selected by a user operation (YES in step S9 in FIG. 14), the infusion pump 70A records the pressing of the stop button 771I as the final administration end operation of the administered medicinal liquid (step S10 in FIG. 14). When the object image 7022 is selected by a user operation (NO in step S9 in FIG. 14), the infusion pump 70A does not record the pressing of the stop button 771I as the final administration end operation of the administered medicinal liquid.

[0135] The infusion pump 70A may display the screens 7010 and 7020 on the display 772 instead of the display 773.

[0136] (d4. Summary) The processing described above with reference to FIGS. 1 to 16 (particularly FIGS. 13 to 16) can be summarized as follows.

[0137] 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 records a log related to the administration, and, upon receiving a second operation (in this example, pressing the stop button 771I), ends administering the medicinal liquid to the patient and recording the log. 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 so that the administration status of the medicinal liquid can be recorded in the electronic medical record. The log is transmitted to the server 20 that stores the electronic medical record via the server 50.

[0138] The terminal device 60 executes a process of transmitting prescription order #1 to the infusion pump 70A based on receiving a predetermined input (in this example, an input by the nurse 9). Specifically, the "third operation" includes, for example, an operation by the nurse 9 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) displaying an image of a plurality of pumps 70, and an operation to send prescription order #1.

[0139] When the infusion pump 70A receives prescription order #1, it administers the medicinal liquid to the patient based on prescription order #1, provided that the first operation has been accepted. Each time the infusion pump 70A accepts the first operation, it issues a first notification (displaying screen 7010 in this example) to inquire of the user whether the first operation is the first administration start operation for the medicinal liquid in prescription order #1. Upon accepting a third operation (an input operation to select object image 7011 in this example) after the first notification, the infusion pump 70A stores the first operation as the first administration start operation for the medicinal liquid in prescription order #1.

[0140] In this way, the infusion pump 70A inquires of the user of the infusion pump 70A whether or not this is the first administration start operation of the administered medicinal liquid, thereby enabling the infusion pump 70A to accurately record the first administration start operation of the medicinal liquid #1, thereby improving the accuracy of the contents recorded in the electronic medical record.

[0141] Furthermore, based on receiving a fourth operation (in this example, an input to select object image 7021) after receiving the second operation, the infusion pump 70A determines that the second operation is the final administration completion operation for the administered medicinal liquid in prescription order #1.

[0142] Specifically, each time the infusion pump 70A receives the second operation, it performs a second notification (in this example, the display on the screen 7020) to ask the user whether the second operation is the last administration end operation of the administered drug solution in the prescription order #1. Based on receiving the fourth operation after the second notification, the infusion pump 70A stores the second operation as the last administration end operation of the administered drug solution in the prescription order #1.

[0143] In this way, since the infusion pump 70A asks the user of the infusion pump 70A whether it is the last administration end operation of the administered drug solution, it can accurately record the last administration end operation of the drug solution #1 in the infusion pump 70A. Therefore, the accuracy of the content described in the electronic medical record can be improved.

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

[0145] <E. Modified Example> (e1. First Modified Example) A modified example of recording the administration start timing and the administration end timing will be described. Specifically, the modified examples in FIGS. 14 and 15 will be described.

[0146] In the above embodiment, an example has been shown in which when the pressing operation of the stop button 771I is received in the sequence SQ7 in FIG. 14, the screen 7020 (FIG. 16) is automatically displayed. In this modified example, a configuration will be described in which, instead of automatically, a menu screen for requesting a confirmation operation regarding the end of administration is displayed based on a user operation.

[0147] FIG. 17 is a flowchart for explaining the process performed by the infusion pump 70A in the first modified example. As shown in FIG. 17, the processes in steps S1 to S7 and S10 are the same as the processes shown in FIG. 14. Therefore, hereinafter, the description will focus on the four processes in steps S101 to S104.

[0148] If the determination in step S7 is affirmative (YES in step S7), the infusion pump 70A determines in step S101 whether an operation to open a predetermined menu screen has been accepted. If it is determined that the operation has been accepted (YES in step S101), the infusion pump 70A displays the menu screen on the display 773, and determines in step S102 whether an operation to specify that this is the final administration end operation has been accepted on the menu screen or on the operation screen displayed based on the operation on the menu screen.

[0149] If it is determined that the operation to open a predetermined menu screen has not been accepted (NO in step S101), the infusion pump 70A determines in step S103 whether the operation to press the start button 771H has been accepted. If it is determined that the operation to press the start button 771H has been accepted (YES in step S103), the infusion pump 70A proceeds to step S2. If it is determined that the operation to press the start button 771H has not been accepted (NO in step S103), the infusion pump 70A proceeds to step S101.

[0150] If it is determined that an operation specifying that this is the final administration end operation has been received (YES in step S102), the infusion pump 70A proceeds to step S10. If it is determined that this operation has not been received (NO in step S102), the infusion pump 70A determines in step S104 whether an operation to close the menu screen has been received. That is, the infusion pump 70A determines whether an operation to hide the menu screen has been received.

[0151] If it is determined that the operation to close the menu screen has been accepted (YES in step S104), the infusion pump 70A proceeds to step S103. If it is determined that the operation to close the menu screen has not been accepted (NO in step S104), the infusion pump 70A proceeds to step S102.

[0152] FIG. 18 is a diagram showing an example of a menu screen displayed on the infusion pump 70A.

[0153] As shown in FIG. 18, the infusion pump 70A displays a menu screen 7030 on the display 773. The menu screen 7030 includes a plurality of items. Each of the plurality of items includes a number and a process. For example, the fifth item 7031 describes a process such as "End." When the nurse 9 or the like selects the fifth item (YES in step S102 of FIG. 17), the screen transitions.

[0154] 19 is a diagram showing operation screen 7040 that is displayed after the fifth item is selected on menu screen 7030. That is, operation screen 7040 is a screen that is displayed based on an operation on the menu screen.

[0155] As shown in FIG. 19, the operation screen 7040 is a screen that asks the user whether or not to truly terminate the operation. The operation screen 7040 includes two selectable object images 7041 and 7042. When the object image 7041 is selected, the infusion pump 70A records the pressing of the start button 771H as the final administration termination operation for the administered medicinal liquid (step S10 in FIG. 17). When the object image 7042 is selected, the operation screen 7040 and the menu screen 7030 are closed. That is, the infusion pump 70A hides the operation screen 7040 and the menu screen 7030.

[0156] In this way, the infusion pump 70A displays an operation screen (in this example, operation screen 7040) for confirming that the second operation is the final administration termination operation for the administered medicinal liquid in prescription order #1 based on accepting the fourth operation (in this example, the operation of pressing the stop button 771I) after accepting the second operation (in this example, the operation of selecting the "End" item on the menu screen 7030). Based on the confirmation operation (in this example, the operation of selecting the object image 7041) on the operation screen, the infusion pump 70A stores the second operation as the final administration termination operation for the administered medicinal liquid in prescription order #1.

[0157] The infusion pump 70A inquires of the user of the infusion pump 70A whether or not this is the final administration completion operation for the administered medicinal liquid, thereby enabling the final administration completion operation for the medicinal liquid #1 in the infusion pump 70A to be recorded with high accuracy, thereby improving the accuracy of the contents recorded in the electronic medical record.

[0158] Furthermore, in this modification, even if the stop button 771I is pressed, the screen 7020 (FIG. 16) requesting a confirmation operation for the end of administration does not automatically pop up. Therefore, the processing of this modification is suitable for users who find pop-up displays bothersome.

[0159] As described above, it is also possible to determine that the operation to end administration of the medicinal liquid is the final operation to end administration of the medicinal liquid for prescription order #1 without displaying the menu screen 7030. For example, the infusion pump 70A may determine that the operation to press the stop button 771I is the final operation to end administration of the medicinal liquid for prescription order #1 on the condition that the operation to press the stop button 771I (second operation) is accepted and then the operation to press another operation button (fourth operation) is accepted. Alternatively, the infusion pump 70A may determine that the operation to press the stop button 771I is the final operation to end administration of the medicinal liquid for prescription order #1 on the condition that the operation to press the stop button 771I (second operation) is accepted and at the same time the operation to press the stop button 771I (fourth operation) is accepted.

[0160] When the item 7031 (FIG. 18) indicating "End" is selected, the infusion pump 70A may store the second operation (in this example, pressing the stop button 771I) as the final administration end operation for the administered medicinal liquid in prescription order #1 without displaying the operation screen 7040 (FIG. 19). In this case, the infusion pump 70A can be said to have the following configuration.

[0161] The infusion pump 70A receives the second operation (in this example, pressing the stop button 771I) and then receives a fourth operation (in this example, an operation to display the menu screen 7030), and based on this, displays an operation screen (in this example, the menu screen 7030) for confirming that the second operation is the final administration end operation for the administered medicinal liquid in prescription order #1. Based on the confirmation operation (in this example, an operation to select item 7031) performed on the operation screen, the infusion pump 70A stores the second operation as the final administration end operation for the administered medicinal liquid in prescription order #1.

[0162] Although the above description has been given taking the infusion pump 70A as an example, the processes of FIGS. 10 to 16 are performed in the other pumps 70 (infusion pump 70B, syringe pumps 70C, 70D, 70E) in the same manner as infusion pump 70A.

[0163] (e2. Second modified example) In this modification, as in the first modification, a modification of recording the injection start timing and injection end timing will be described. Specifically, the modification shown in FIG. 14 will be described.

[0164] Fig. 20 is a flow chart for explaining the processing performed by the infusion pump 70A in the second modified example. As shown in Fig. 20, the processing in steps S1 to S7 is the same as the processing shown in Fig. 14. Therefore, the following description will focus on the two processing steps of steps S201 and S10A.

[0165] If the determination in step S7 is affirmative (YES in step S7), the infusion pump 70A determines in step S201 whether an operation to power off the infusion pump 70A has been received. If it is determined that the operation has been received (YES in step S201), the infusion pump 70A records in step S10A the pressing of the stop button 771I immediately before powering off as the final administration termination operation of the administered medicinal liquid. Specifically, the infusion pump 70A records an operation log based on the pressing operation in the memory 712 as an administration termination operation log.

[0166] With this configuration, when the infusion pump 70A is turned off, the nurse 9 or the like does not need to perform the operation for recording the final administration end operation of the administered medicinal liquid. Therefore, compared with the infusion pump 70A described in the above embodiment and the infusion pump 70A described in the first modified example, the user of the infusion pump 70A can save time and effort.

[0167] (e3. Third variant) When the pumps (70A, 70B, 70C, 70D, 70E) automatically stop due to an abnormality, it is preferable to configure the pumps (70A, 70B, 70C, 70D, 70E) so that the administration of the administered medicinal liquid to the patient and the recording of the log are terminated even if the second operation described above (in this example, pressing the stop button 771I) is not accepted.

[0168] An example of a trigger for automatic shutdown due to an abnormality is the output of an air bubble alarm or empty liquid alarm when the chemical solution runs out.

[0169] (e4. Fourth Modification) 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.

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

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

[0172] 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]

[0173] 1 Network system, 2 Communication system, 3 Rack system, 4 0, 9 Nurse, 10, 60 Terminal device, 20, 30, 40, 50 Server, 51, 61, 71 Control unit, 53, 64, 73 Clock, 62 Touch screen, 70 Pump, 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 volume clear button, 771E, 771F flow rate setting button, 771G bolus button, 771H start button, 771I stop or mute button, 921 flange, 7010, 7020 screen, 7011, 7012, 7021, 7022, 7041, 7042 object image, 7030 menu screen, 7040 operation screen, 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, based on receiving a first operation, starts administering the medicinal liquid to the patient and records a log related to the administration, and, based on receiving a second operation, ends administering the medicinal liquid to the patient and recording the log, and 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; The information processing device executes a process of transmitting the prescription order to the pump based on the reception of a predetermined input; 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; every time the first operation is received, a first notification is made to inquire of the user whether the first operation is the first administration start operation of the medicinal liquid in the prescription order; The system stores the first operation as the first administration start operation of the medicinal liquid in the prescription order based on receiving a third operation after the first notification.

2. The system of claim 1, wherein the pump determines that the second operation is the final administration completion operation for the administered medicinal liquid in the prescription order based on receiving a fourth operation after receiving the second operation.

3. The pump every time the second operation is received, a second notification is made to inquire of the user whether the second operation is the final administration end operation of the medicinal liquid in the prescription order; The system according to claim 2, wherein, based on receiving the fourth operation after the second notification, the second operation is stored as a final administration end operation for the administered medicinal liquid in the prescription order.

4. The pump displaying an operation screen for confirming that the second operation is a final administration end operation of the administered medicinal liquid in the prescription order, based on the fact that the fourth operation has been accepted after the second operation has been accepted; The system according to claim 2 , wherein the second operation is stored as a final administration end operation of the medicinal liquid in the prescription order based on a confirmation operation being performed on the operation screen.

5. The system of claim 1, wherein the pump determines that the second operation is the final administration completion operation for the administered medicinal liquid in the prescription order based on receiving a fourth operation simultaneously with the second operation.

6. The pump a power supply and a switch for turning the power supply on and off; The system according to claim 1, wherein when the power supply is turned off by the switch, the second operation performed immediately before the power supply is turned off is stored as a final administration end operation for the administered medicinal liquid in the prescription order.

7. 5. The system according to claim 2, wherein when the pump automatically stops due to an abnormality, the pump terminates administration of the medicinal solution to the patient and recording of the log even if the second operation is not accepted.

8. 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, based on receiving a first operation, starts administering the medicinal liquid to the patient and recording a log related to the administration, and, based on receiving a second operation, ends administering the medicinal liquid to the patient and recording the log, 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 a process by the information processing device to transmit the prescription order to the pump based on receipt of a predetermined input; 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; a step of making a first notification by the pump each time the pump receives the first operation, inquiring to a user whether the first operation is a first administration start operation of the medicinal liquid in the prescription order; The method includes a step in which the pump stores the first operation as the first administration start operation of the administered medicinal liquid in the prescription order based on receiving a third operation after the first notification.

Images