JP2025068372A - Liquid medicine administration system and communication control method - Google Patents

Abstract

To provide a liquid medicine administration system capable of preventing operation state information based on order information after change from being associated with the order information transmitted from a server device to a liquid medicine administration pump.SOLUTION: A liquid medicine administration system includes a server device, a terminal device for communicating with the server device, and a liquid medicine administration pump capable of communicating with the server device and the terminal device. The terminal device acquires order information including an injection prescription order for a patient from the server device, and transmits the order information to the liquid medicine administration pump. The prescription order includes a setting value for stipulating the operation of the liquid medicine administration pump. The liquid medicine administration pump can receive change operation for the setting value, and transmits the setting value at the start of the liquid medicine administration to the server device. When the setting value included in the order information transmitted to the terminal device is not matched to the setting value at the start of the liquid medicine administration received from the liquid medicine administration pump, the server device interrupts the communication with the liquid medicine administration pump.SELECTED DRAWING: Figure 5

Description

This disclosure relates to a drug solution administration system and a communication control method.

Heretofore, in hospitals and the like have used infusion pumps, syringe pumps, and other liquid drug administration pumps. JP 2011-87678 A (Patent Document 1) discloses an infusion pump in which a portable setting terminal equipped with an operation unit for setting designated values for the planned amount and flow rate and a memory unit for storing command values set by the operation unit is provided separately from the pump body. A command value receiver (reader) for short-range wireless communication with the setting terminal is provided on the top surface of the pump body. When the setting terminal is held over the command value receiver, the designated values for the planned amount and flow rate stored in the memory unit of the setting terminal are read into the pump body. The pump body performs pumping according to the read designated values for the planned amount and flow rate.

JP 2011-87678 A

In a system configuration in which a terminal device obtains order information including flow rate, planned amount, etc. from a server device and the terminal device can transfer the order information to a liquid medicine administration pump, it is desirable for the server device to wirelessly obtain and store operating status information indicating the operating status of the liquid medicine administration pump based on the order information in order to record the implementation.

In the above configuration, various settings, such as the flow rate, included in the order information may be changed by an unintended user operation on the drug administration pump. If the drug administration pump starts administering drug with the settings changed in this way, the server device will store an implementation record based on order information different from the original order information, linked to the original order information.

The present disclosure has been made in consideration of the above problems, and provides a liquid medicine administration system and a communication control method that can prevent operation status information based on changed order information from being linked to order information sent from a server device to a liquid medicine administration pump.

According to an aspect of the present disclosure, a medicinal liquid administration system includes a server device, a terminal device that communicates with the server device, and a medicinal liquid administration pump that can communicate between the server device and the terminal device. The terminal device acquires order information including a prescription order for an injection for a patient from the server device, and transmits the order information to the medicinal liquid administration pump. The prescription order includes a setting value that specifies the operation of the medicinal liquid administration pump. The medicinal liquid administration pump can accept an operation to change the setting value, and transmits the setting value at the start of medicinal liquid administration to the server device. If the setting value included in the order information transmitted to the terminal device does not match the setting value received from the medicinal liquid administration pump at the start of medicinal liquid administration, the server device cuts off communication with the medicinal liquid administration pump.

According to another aspect of the present disclosure, the communication control method includes a step in which a terminal device acquires order information including a prescription order for an injection for a patient from a server device, and a step in which the terminal device transmits the order information to a liquid medicine administration pump. The prescription order includes a setting value that specifies the operation of the liquid medicine administration pump. The setting value of the liquid medicine administration pump can be changed based on an operator's operation. The communication control method further includes a step in which the liquid medicine administration pump establishes communication with the server device, a step in which the liquid medicine administration pump transmits a setting value at the start of liquid medicine administration to the server device, and a step in which the server device cuts off communication with the liquid medicine administration pump if the setting value included in the order information transmitted to the terminal device does not match the setting value received from the liquid medicine administration pump at the start of liquid medicine administration.

According to the present disclosure, it is possible to prevent the order information sent from the server device to the drug solution administration pump from being linked to operating status information based on changed order information.

1 is a diagram showing a configuration of a medical system including a drug solution administration system. FIG. 2 is a diagram for explaining information stored in a server. FIG. 13 is a diagram showing the first half of the screen transition of the smartphone. FIG. 13 shows the latter half of the screen transition on the smartphone. FIG. 2 is a diagram showing the flow of data in the drug solution administration system. FIG. 13 is a diagram showing reading of a wristband by a smartphone. FIG. 13 is a diagram showing reading a barcode of an infusion pump using a smartphone. FIG. 13 illustrates reading of a medicine label using a smartphone. 13 is a diagram showing the state of the smartphone and the infusion pump immediately after the transfer of order information is completed. FIG. FIG. 2 is a block diagram of each device that constitutes the drug solution administration system. 11 is a sequence diagram for explaining the flow of a first part of data processing in the drug solution administration system. FIG. FIG. 11 is a sequence diagram for explaining the flow of a second part of data processing in the drug solution administration system. FIG. 11 is a sequence diagram for explaining the flow of a third part of data processing in the drug solution administration system. FIG. 2 is a diagram showing a modified example of the drug solution administration pump group shown in FIG. 1 .

Below, an embodiment of the present disclosure will be described with reference to the drawings. In the following description, the same components are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

A. System Configuration
Fig. 1 is a diagram showing the configuration of a medical system including a medicinal liquid administration system. As shown in Fig. 1, the medical system 1 includes a medicinal liquid administration system 5, a server 10 that records electronic medical records, a pharmacy department server 20, and a monitoring terminal 60. The medicinal liquid administration system 5 includes a server 30, a smartphone 40 as an example of an information processing device (terminal device), and a group of medicinal liquid administration pumps 500.

In this example, the group of drug solution administration pumps 500 includes a plurality of infusion pumps 50A, 50B, and 50C, each of which is an example of a drug solution administration pump. In the following, for convenience of explanation, any one of the infusion pumps 50A, 50B, and 50C is also referred to as an "infusion pump 50". The infusion pumps 50A, 50B, and 50C are installed in an operating room or the like. In this example, the infusion pumps 50A, 50B, and 50C are arranged in positions close to each other. In this example, three infusion pumps 50A, 50B, and 50C are given as an example, but the number of infusion pumps is not limited to this. Furthermore, the group of drug solution administration pumps 500 may include one or more syringe pumps. The drug solution administration pump is not limited to the infusion pump 50, and may be another pump such as a syringe pump.

The information processing device is not limited to the smartphone 40, but may be any portable device such as a tablet terminal. In this example, the monitoring terminal 60 is a PC (Personal Computer). The smartphone 40 can also function as a terminal for status monitoring.

Server 30 is communicatively connected to server 10, server 20, and monitoring terminal 60. Typically, server 30 is connected to servers 10 and 20, and monitoring terminal 60 by wire. Server 10 is communicatively connected to server 20. Typically, server 10 is connected to server 20 by wire. Note that server 30 may be communicatively connected to monitoring terminal 60 wirelessly.

The server 30 is configured to be able to communicate with the smartphone 40 and each infusion pump 50. Typically, the server 30 can establish communication between the smartphone 40 and the infusion pump 50 via a wireless LAN (Local Area Network). In this example, Wi-Fi (registered trademark) is used as one type of wireless LAN communication method.

The smartphone 40 communicates with the infusion pump 50. The smartphone 40 communicates wirelessly with the infusion pump 50. The smartphone 40 performs near field communication (NFC) with the infusion pump 50. In this example, the smartphone 40 communicates with the infusion pump 50 using Felica (registered trademark), which is Type-F of NFC. The near field communication is an example of communication based on a predetermined protocol in the present invention.

The smartphone 40 has a built-in reader/writer for Felica. The reader/writer has a control board and an antenna. The infusion pump 50 is equipped with Felica Link. The infusion pump 50 has a built-in contactless integrated circuit card for Felica (FeliCa Plug). The contactless integrated circuit card has an integrated circuit chip and an antenna. In the following, the contactless integrated circuit card is also referred to as a "contactless IC card."

In this example, short-range wireless communication is performed between the smartphone 40, which operates as a reader/writer, and the infusion pump 50, which operates as a tag, by bringing the smartphone 40 close to the infusion pump 50. For example, short-range wireless communication is performed between the smartphone 40 and the infusion pump 50A by bringing the smartphone 40 close to the infusion pump 50A. The reason that the smartphone 40, rather than the infusion pump 50, has a built-in reader/writer is that it is assumed that the smartphone 40 will also perform short-range wireless communication with multiple other pumps (not shown) in the same way as the infusion pump 50.

Server 10 prestores staff master data that stores personal information of each staff member (hereinafter referred to as "staff") who belongs to the hospital, such as nurses, and patient master data that stores personal information of each patient. The staff master data and patient master data are updated successively. Server 10 transmits the staff master data and patient master data to server 30. Server 10 typically transmits the staff master data and patient master data to server 30 in response to a request from server 30 or based on the above-mentioned updates.

When the server 10 acquires order information including a prescription order for an injection for a patient created by a doctor, it records the contents of the received order information in the patient's electronic medical record. The prescription order is created using a terminal (not shown) used by the doctor. During one treatment, the doctor generates a prescription order for each medicinal liquid. Therefore, when multiple medicinal liquids are administered to one patient, multiple pieces of order information are created and recorded in the electronic medical record.

The server 20 stores the drug library data in advance. The server 20 transmits the drug library data to the server 30. When the drug library is updated in the server 20, the server 20 transmits update data for updating the drug library of the server 30 to the server 30. The server 20 may transmit the updated drug library data itself as the update data, or may transmit data of only the updated parts.

Based on input operations by a pharmacist or the like, server 20 acquires order information for a specified patient from server 10. Server 20 transmits order information for a patient about to begin treatment (hereinafter also referred to as the "target patient") to server 30. Servers 10 and 20 may handle multiple order information for the target patient as a single list of information. Staff in the pharmacy department judge whether the order information acquired by server 20 from server 10 is appropriate.

(B. Data)
Fig. 2 is a diagram for explaining information stored in the server 30. As shown in Fig. 2, the server 30 includes a control unit 31 and a storage unit 32. The control unit 31 is a functional block realized by a processor executing an operating system and various programs stored in the storage unit 32. The storage unit 32 is specifically a memory. The memory includes a volatile memory and a non-volatile memory.

The memory unit 32 of the server 30 stores staff master data, patient master data, the latest drug library data, and multiple order information #1, #2, ... #N through the data processing described based on FIG. 1. Each order information #1, #2, ... #N includes information such as an order ID for identifying the order information, a patient ID for identifying the patient, a drug name (medicinal solution name), a drug ID for identifying the drug, a set value for the flow rate of the medical solution (mL/h), and a set value for the dosage (mL). Furthermore, the order information includes information such as the scheduled date and time of administration and the date and time of order creation.

When multiple medicinal liquids are administered to the same patient at the same time, multiple order information (e.g., order information #1, #2) are prepared for that patient. In this case, the same patient ID is associated with different order IDs. Server 30 also stores past order information that has already been used as history.

The drug library data stores at least a flow rate (mL/h) threshold, a dosage (mL) threshold, and an administration rate (μg/kg/min) threshold in association with a drug name or drug ID. The dosage is also called the "planned amount."

The flow rate threshold includes an upper flow rate limit and a lower flow rate limit. The dosage threshold includes an upper dosage limit and a lower dosage limit. The administration rate threshold includes an upper administration rate limit and a lower administration rate limit. Note that the drug library data does not necessarily need to store all of the upper and lower limits for each drug solution.

(C. User Operation and Data Transmission and Reception)
Fig. 3 is a diagram showing the first half of the screen transition of the smartphone 40. Fig. 4 is a diagram showing the second half of the screen transition of the smartphone 40. Fig. 5 is a diagram showing the flow of data in the medicinal solution administration system 5. Below, the operations of the staff will be explained with reference to Figs. 3 and 4, and the data exchanged by the operations will be explained with reference to Fig. 5 as appropriate.

In this example, for ease of explanation, it is assumed that the power of the infusion pump 50 is on and that wireless communication is possible between the infusion pump 50 and the server 30. However, this is not limited to the above, and the server 30 may be configured to establish wireless communication with the infusion pump 50 at a predetermined timing.

Referring to FIG. 3, when the smartphone 40 starts a specific application program by the staff member's operation, the smartphone 40 displays screen G41 on the touch screen 43 as shown in state (A) of FIG. 3. Screen G41 is a login screen. Screen G41 includes an image object 471. Note that in this example, the application program has a function of reading one-dimensional codes (i.e., barcodes) and two-dimensional codes such as QR codes (registered trademark).

When a staff member selects image object 471 with the fingers of his/her hand 901, reading of the barcode using the camera begins. For example, the staff member uses the camera of smartphone 40 to capture an image of the barcode on a name tag worn by the staff member. The barcode contains the staff ID. In this manner, the staff ID is read by smartphone 40.

After the smartphone 40 reads the barcode, the staff member inputs the password into the smartphone 40. The staff member then selects a specific image object, which causes the smartphone 40 to send the staff member ID and password to the server 30. Through this process, the server 30 authenticates the staff member using the staff master data.

When staff authentication is performed, the smartphone 40 displays screen G42 on the touch screen 43 as shown in state (B). Screen G42 is a menu screen. Screen G42 includes image objects 472, 473, 474, and 475.

Image object 472 is an object for transitioning to a vital sign management screen. Image object 473 is an object for transitioning to an order transfer screen. Image object 474 is an object for transitioning to a monitoring device registration screen (i.e., monitoring device registration). Image object 475 is an object for transitioning to a screen showing a list of registered monitoring devices.

When the staff member selects image object 473 with his/her finger, the smartphone 40 displays screen G43 on the touch screen 43 as shown in state (C). Screen G43 and screens G44 to G47, which will be described later, are screens for transferring order information. Screen G43 includes image objects 476 and 491. In state (C), of image objects 476 and 491, only image object 476 is selectable. Image object 476 is an object for transitioning to a patient ID selection process (reading process).

When the staff member selects image object 476 with his/her finger, smartphone 40 starts reading the barcode using the camera. The staff member uses the camera of smartphone 40 to capture an image of the barcode on the wristband attached to the wrist of the target patient. The patient ID is written on the barcode.

Figure 6 is a diagram showing the reading of a wristband by a smartphone 40. As shown in Figure 6, information such as the name, date of birth, blood type, and a barcode 811 is printed on a wristband 810 wrapped around the wrist 951 of the target patient. A staff member reads the barcode 811 using the smartphone 40. The patient ID is expressed (written) on the barcode 811. In this manner, the patient ID is read by the smartphone 40.

When the smartphone 40 reads the barcode 811 as shown in FIG. 5 as "(i) Photographing the barcode on the wristband," the smartphone 40 transmits the patient ID to the server 30 as shown in FIG. 5 as "(ii) Patient ID." Typically, the smartphone 40 transmits the patient ID to the server 30 via wireless LAN after confirmation input by the staff member (selection of an image object such as a send button).

When the smartphone 40 transmits the patient ID to the server 30, authentication is performed by the server 30 using the patient ID, and the smartphone 40 displays screen G44 on the touch screen 43 as shown in state (D) of FIG. 3. Screen G44 includes image objects 478, 491, and 477. In state (D), of image objects 491 and 477, only image object 491 is selectable. Image object 491 is an object for transitioning to a pump ID reading process.

Image object 478 shows the patient ID obtained by reading barcode 811. Note that the patient ID can be reset by selecting reset button 4781 in object 478.

Then, the staff sets the medicine (infusion pack) in a specified infusion pump 50 out of the multiple infusion pumps 50. In this example, as shown in FIG. 5 as "(iii) Setting the medicine (infusion pack)," the staff sets the medicine in the infusion pump 50B. Note that the timing of setting the medicine in the infusion pump 50 is not limited to this. For example, the medicine may be set in the infusion pump 50 before the staff starts the specified application program on the smartphone 40.

When the staff member selects the image object 491 shown in state (D) of FIG. 3 with his/her finger, the smartphone 40 resumes reading the barcode using the camera. As shown in FIG. 5 as "(iv) Photographing the barcode on the infusion pump," the staff member photographs the barcode printed on the sticker (label) attached to the infusion pump 50B with the camera of the smartphone 40.

Figure 7 shows how the smartphone 40 reads the barcode of the infusion pump 50B. As shown in Figure 7, the staff member uses the scanning screen G51 displayed on the smartphone 40 to read the barcode 511 printed on the sticker 510. The barcode 511 contains a pump ID (serial number) that identifies the infusion pump 50B.

In this example, the sticker 510 is attached to the upper front surface of the infusion pump 50B. However, the location of the sticker 510 is not limited to this. The location of the sticker 510 is not particularly limited as long as it is a location where the barcode 511 can be easily scanned by the smartphone 40.

The smartphone 40 obtains the pump ID of the infusion pump 50 (in this example, infusion pump 50B) by reading the barcode 511. The smartphone 40 temporarily stores the obtained pump ID. For ease of explanation, the pump ID is also referred to as "pump ID_BAR" below.

When the smartphone 40 acquires the pump ID by scanning, the smartphone 40 displays screen G45 on the touch screen 43 as shown in state (E) of FIG. 3. Screen G45 includes image objects 478, 492, and 477. In state (E), image object 477 is selectable. Image object 477 is an object for transitioning to the selection process (reading process) of the order ID.

Image object 492 shows the pump ID obtained by reading barcode 511. Note that the pump ID can be reset by selecting the reset button 4901 in object 492.

When the staff member selects image object 477 with his/her finger, smartphone 40 resumes reading the barcode using the camera. As shown in FIG. 5 as "(v) Photographing the barcode on the drug label," the staff member photographs the barcode printed on the drug label of the target patient with the camera of smartphone 40.

Figure 8 is a diagram showing the reading of a medication label by smartphone 40. As shown in Figure 8, information such as the patient ID, name, age, and barcode 821 is printed on the medication label 820 of the target patient. The staff member reads the barcode 821 using smartphone 40. The order ID is expressed (written) on the barcode 821. In this manner, the order ID is read by smartphone 40.

When the smartphone 40 reads the barcode 821, it transmits the order ID to the server 30 as shown as "(vi) Order ID" in FIG. 5. Typically, the smartphone 40 transmits the order ID to the server 30 via the wireless LAN after confirmation input by the staff member (selection of an image object such as a send button).

When the server 30 obtains the patient ID and then the order ID from the smartphone 40, it executes the following process. From among the multiple order information #1, #2, ... #3 stored in the memory unit 32 (Figure 2), the server 30 extracts order information including an order ID that matches the order ID sent from the smartphone 40. That is, from among the multiple order information #1, #2, ... #3, the server 30 extracts order information including an order ID that matches the order ID obtained by reading the barcode 821 on the medication label 820 by the smartphone 40. Note that since there are no duplicate order IDs, the server 30 extracts one order information.

Next, the server 30 determines whether the patient ID (see FIG. 2) included in the extracted order information matches the patient ID sent from the smartphone 40. In other words, the server 30 determines whether the patient ID included in the extracted order information matches the patient ID obtained by reading the barcode 811 on the wristband 810 with the smartphone 40.

If the server 30 determines that the patient IDs match, it transmits the extracted order information to the smartphone 40, as shown as "(vii) Order information" in FIG. 5. Specifically, the server 30 transmits the extracted order information to the smartphone 40 using wireless LAN communication.

If the server 30 determines that the patient IDs do not match, it does not send the extracted order information to the smartphone 40. In this case, the server 30 typically sends information indicating an error or warning to the smartphone 40.

When the smartphone 40 acquires (receives) the order information from the server 30, it displays screen G46 on the touch screen 43 as shown in state (F) of FIG. 4. Screen G46 includes image objects 478, 480, and 481.

Image object 480 shows the order information (excluding the patient ID) obtained from server 30. Staff can confirm the prescription order for an injection for the target patient by visually checking the order information contained in image object 480. Note that the order information can be reset (changed) by selecting the reset button 4801 in image object 480.

Image object 481 is an object for accepting the start of order transfer. When the staff member selects image object 481 with his/her finger, the smartphone 40 switches the screen displayed on the touch screen 43 from screen G46 to screen G47, as shown in state (G) of FIG. 4, and prepares for short-range wireless communication with the infusion pump 50B.

Screen G47 includes image objects 478, 480, and 482. Image object 482 includes a guidance display that prompts the staff member to move the smartphone 40 closer to the infusion pump 50B. Image object 482 further includes a cancel button 4821 for canceling the transfer of the order information to the infusion pump 50B. When the staff member selects the cancel button 4821, the smartphone 40 switches the screen from screen G47 to screen G46, for example.

When the staff member brings the smartphone 40 close to the infusion pump 50B, short-range wireless communication is established between the smartphone 40 and the infusion pump 50B. In more detail, when the staff member holds the smartphone 40 over the FeliCa mark 590 (see FIG. 7) printed on the surface of the infusion pump 50B, short-range wireless communication is established between the smartphone 40 and the infusion pump 50B.

When short-range wireless communication is established, the smartphone 40 transmits a request signal requesting transmission of the pump ID to the infusion pump 50B, as shown as "(viii) Request signal" in FIG. 5. When the infusion pump 50B receives the request signal, it transmits the pump ID of the infusion pump 50B to the smartphone 40 with which short-range wireless communication has been established, as shown as "(ix) Pump ID" in FIG. 5. For ease of explanation, the pump ID thus obtained by short-range wireless communication is also referred to as "Pump ID_NFC" below.

When the smartphone 40 receives the pump ID_NFC from the infusion pump 50B, as shown in FIG. 5 as "(x) Comparison of pump IDs," the smartphone 40 determines whether the pump ID_NFC matches the pump ID_BAR obtained by reading the barcode 511 (FIG. 7). That is, the smartphone 40 determines whether the infusion pump 50 (in this example, infusion pump 50B) that sent the pump ID_NFC and the infusion pump 50 (infusion pump 50B in the case of FIG. 7) with the pump ID_BAR written on the barcode 511 are the same infusion pump 50.

When the smartphone 40 determines that the infusion pump 50 with pump ID_BAR and the infusion pump 50 with pump ID_NFC are the same, it stores the pump ID_BAR (or pump ID_NFC) in association with the order ID, as shown in FIG. 5 as "(xi) Store pump ID and order ID in association." The order ID to be associated may be the order ID sent from the smartphone 40 to the server 30 ((vi) in FIG. 5), or the order ID included in the order information received from the server 30 ((vii) in FIG. 5). Specifically, the smartphone 40 manages the pump ID and the order ID in an associated state, as shown as data table D4 in FIG. 5.

Furthermore, as shown in FIG. 5 as "(xii) Order Information", the smartphone 40 transmits the order information to the infusion pump 50 (infusion pump 50B in this example) with which short-range wireless communication has been established. That is, the smartphone 40 transmits the order information to the infusion pump 50 by short-range wireless communication, provided that the infusion pump 50 in which the drug is set is the same as the infusion pump 50 to which the order information is to be sent. In detail, the smartphone 40 transfers the order information acquired from the server 30 to the infusion pump 50 (infusion pump 50B in this example). With this configuration, it becomes possible to transmit the order information of the drug to the infusion pump 50 in which the above-mentioned drug is set.

When the order information is transferred, the smartphone 40 switches the screen displayed on the touch screen 43 from screen G47 to screen G48, as shown in state (H) of FIG. 4. Screen G48 includes image object 483 and image object 484.

Now, suppose that the staff member mistakenly brings the smartphone 40 closer to the infusion pump 50A or the infusion pump 50C instead of the infusion pump 50B. In this case, the pump ID_NFC acquired by short-range wireless communication does not match the pump ID_BAR acquired by reading the barcode 511. In this case, the smartphone 40 does not transmit the order information to the infusion pump 50 with which the short-range wireless communication has been established (the infusion pump 50 having the pump ID_NFC).

Figure 9 shows the state of the smartphone 40 and the infusion pump 50 immediately after the transfer of the order information is completed. As shown in Figure 9, the smartphone 40 displays the above-mentioned screen G48 on the touch screen 43.

Image object 483 shown in FIG. 9 and FIG. 4 indicates that the transfer of the order information has been completed. Image object 483 further includes a notification urging the staff member to press a setting completion button represented as image object 484 and to press start button 591 of infusion pump 50 after pressing the setting completion button.

The infusion pump 50 is equipped with a display 55. When the infusion pump 50 receives order information from the smartphone 40, it displays screen G61 on the display 55. Screen G61 includes information that the operation of the infusion pump 50 is stopped. Screen G61 further includes information on the drug name, planned amount, and flow rate included in the order information. Screen G61 includes an item for the accumulated amount.

As shown in FIG. 5 as "(xiii) Start button on," when the staff member presses the start button 591 (FIG. 9) of the infusion pump 50 while screen G61 is displayed on the display 55 of the infusion pump 50, administration of medicinal fluid by the infusion pump 50 begins.

When the start button 591 of the infusion pump 50 is pressed, the following process is further executed. As shown in FIG. 5 as "(xiv) Setting value at the start of drug administration + pump ID", the infusion pump 50 transmits to the server 30 the setting value at the start of drug administration (when the start button 591 is pressed) and the pump ID in a mutually associated state. In the example of FIG. 5, the pump ID "02405015" of the infusion pump 50 is transmitted to the server 30.

When the staff operates the infusion pump 50 to change the setting values (such as the flow rate setting value and the dosage setting value shown in FIG. 2) included in the order information received from the smartphone 40, the changed setting values are sent to the server 30. If the staff has not changed the setting values included in the order information before pressing the start button 591, the setting values included in the order information received from the smartphone 40 are sent (i.e., transferred) to the server 30.

In this example, the infusion pump 50 transmits one or more setting values included in the order information to the server 30, but this is not limited to the example. The infusion pump 50 may transmit the order information itself to the server 30 when the start button 591 is pressed.

As shown in FIG. 5 as "(xv) Setting value at start of drug administration + pump ID," the server 30 transfers the setting value at start of drug administration and the pump ID acquired from the infusion pump 50 to the smartphone 40. As shown in FIG. 5 as "(xvi) Extraction of order information," the smartphone 40 refers to the data table D4 and selects the order ID associated with the pump ID received from the server 30. As a result, the smartphone 40 extracts one piece of order information from the multiple pieces of order information. Specifically, the smartphone 40 identifies the order information sent to the infusion pump 50 (infusion pump 50B in the example of FIG. 5).

Next, as shown in FIG. 5 as "(xvii) Comparison of setting values at the start of drug solution administration with setting values in order information," the smartphone 40 compares whether the setting values at the start of drug solution administration received from the server 30 match the setting values included in the extracted order information. The smartphone 40 determines whether the setting values match for each type of setting value, such as the flow rate setting value, the dosage setting value, and the like. The smartphone 40 determines whether the setting values match completely for all types.

As shown in FIG. 5 as "(xviii) Comparison result," the smartphone 40 transmits the comparison result between the above-mentioned setting values to the server 30. If the setting values for all types match, the smartphone 40 transmits information (signals) to the server 30 indicating that they match. If the setting values for all types do not match completely, the smartphone 40 transmits information (signals) to the server 30 indicating that they do not match.

When the setting values for all types match, the smartphone 40 further switches the screen to screen G49 shown in state (I) of FIG. 4. Screen G49 includes image objects 491, 477, and 485. On screen G49, like screen G44 in FIG. 3, the staff member cannot select image object 477.

If the order needs to be transferred to the remaining infusion pumps 50, the staff member selects image object 491 and repeats the above-mentioned processes of reading the pump ID and selecting the order ID. If no further order transfers are required, the staff member selects image object 485. When image object 485 is selected, the smartphone 40 switches the screen from screen G49 to screen G50 shown in state (J).

Screen G50 includes image object 486 and image object 487. Image object 486 includes an order ID, a pump ID, and a notification that no changes have been made to the setting values. By selecting image object 487, the staff member can transition the screen from screen G49 to screen G42 (Figure 3).

If the setting values do not match, the smartphone 40 switches the screen from screen 49 to a screen (not shown) indicating that the setting value has been changed. The smartphone 40 displays a warning.

When the server 30 receives information indicating a match from the smartphone 40, it continues wireless communication with the infusion pump 50. In this case, as shown as "(xix) Operational status information (when the setting values match)" in FIG. 5, the server 30 periodically obtains data indicating the operational status of the infusion pump 50 from the infusion pump 50.

On the other hand, when the server 30 receives information from the smartphone 40 indicating that they do not match, it blocks wireless communication with the infusion pump 50. This prevents the server 30 from receiving data indicating the operating status periodically transmitted from the infusion pump 50. This prevents the server 30 from recording operating status information when the infusion pump 50 is operated based on order information different from the order information transmitted to the infusion pump 50 via the smartphone 40 (hereinafter, "original order information") as an implementation record linked to the original order information. Furthermore, it prevents the operating status information from being used as monitoring data. The operating status information includes various information such as start and stop of the infusion pump 50 in addition to administration information (flow rate, etc.).

If the server 30 receives information from the smartphone 40 indicating that there is no match, the server 30 further registers the correspondence between the order ID and the pump ID. Specifically, the server 30 associates and manages the order ID of the order information ((vii) in FIG. 5) sent to the smartphone 40 based on the order ID ((vi) in FIG. 5) from the smartphone 40 with the pump ID ((xiv) in FIG. 4) received from the infusion pump 50.

(D. Summary)
(1) As shown in FIG. 1 , the medicinal solution administration system 5 includes a server 30, a smartphone 40 that communicates with the server 30, and an infusion pump 50 that can communicate between the server 30 and the smartphone 40.

The smartphone 40 obtains order information including a prescription order for an injection for the patient from the server 30 and transmits the order information to the infusion pump 50 ((vii) and (xii) in FIG. 5). As shown in FIG. 2, the prescription order includes setting values that specify the operation of the infusion pump 50. The infusion pump 50 can accept an operation to change the setting values and transmits the setting values at the start of drug administration to the server 30 ((xiv) in FIG. 5). If the setting values included in the order information transmitted to the smartphone 40 do not match the setting values received from the infusion pump 50 at the start of drug administration, the server 30 cuts off communication with the infusion pump 50 (sequence SQ24 in FIG. 13).

According to this configuration, if the setting value included in the order information sent to the smartphone 40 does not match the setting value received from the infusion pump 50 at the start of drug solution administration, the server 30 will not receive operating status information indicating the operating status of the infusion pump 50 from the infusion pump 50. Therefore, according to the drug solution administration system 5, it is possible to prevent operating status information based on the changed order information from being linked to the order information sent from the server 30 to the infusion pump 50.

As described above, the entity that determines whether the setting values included in the order information sent to the smartphone 40 match the setting values received from the infusion pump 50 at the start of drug administration is the smartphone 40, but this is not limited to this and may be the server 30.

(2) The smartphone 40 obtains from the server 30 the setting value at the start of liquid administration ((xv) in FIG. 5). If the setting value at the start of liquid administration is not the same as the setting value included in the order information, the smartphone 40 transmits a predetermined signal to the server 30 ((xviii) in FIG. 5). Upon receiving the predetermined signal, the server 30 cuts off communication with the infusion pump 50 (sequence SQ24 in FIG. 13). In this way, the liquid administration system 5 can be configured to determine whether the setting values match in the smartphone 40.

(3) As shown in FIG. 2, the smartphone 40 stores multiple different order information. When the smartphone 40 transmits one piece of order information to the infusion pump 50, the smartphone 40 acquires a pump ID for identifying the infusion pump 50 from the infusion pump 50 (e.g., (ix) in FIG. 5). The smartphone 40 associates the acquired pump ID with the order information transmitted to the infusion pump 50 and stores it ((xi) in FIG. 5). The infusion pump 50 transmits the setting value at the start of drug administration to the server 30, associated with the pump ID ((xiv) in FIG. 5).

The smartphone 40 obtains the setting value at the start of drug solution administration from the server 30 in association with the pump ID ((xv) in FIG. 5). The smartphone 40 extracts, from among the multiple pieces of order information, order information associated with the same pump ID as the pump ID associated with the setting value at the start of drug solution administration ((xvi) in FIG. 5). If the setting value at the start of drug solution administration is not the same as the setting value included in the extracted order information, the smartphone 40 transmits a predetermined signal to the server 30 ((xviii) in FIG. 5).

In this configuration, in a configuration in which order information corresponding to drugs installed in each of multiple infusion pumps 50 is transmitted to the smartphone 40, the smartphone 40 can compare the setting value included in the order information transmitted from the server 30 to the smartphone 40 to the target infusion pump 50 (in the above example, infusion pump 50B) with the setting value received from the target infusion pump 50 at the start of drug administration.

(4) As shown in FIG. 2, each piece of order information includes an order ID that identifies the order information. The smartphone 40 associates the acquired pump ID with the order ID of the order information sent to the infusion pump 50 by associating the acquired pump ID with the order information sent to the infusion pump 50 ((xi) in FIG. 5). The smartphone 40 extracts, from among the multiple pieces of order information, order information that includes an order ID associated with the same pump ID as the pump ID associated with the setting value at the start of drug solution administration ((xvi) in FIG. 5).

With this configuration, it is possible to extract, from among multiple pieces of order information, order information associated with the same pump ID as the pump ID associated with the setting value at the start of drug solution administration.

(5) If the setting value included in the order information sent to the smartphone 40 matches the setting value received from the infusion pump 50 at the start of drug administration, the server 30 periodically acquires information indicating the operating status of the infusion pump 50 from the infusion pump 50 (xix in FIG. 5). With this configuration, the server 30 acquires information indicating the operating status from the infusion pump 50 on the condition that the setting values match.

(E. Internal Structure)
10 is a block diagram of each device constituting the medicinal liquid administration system 5. As described above, the medicinal liquid administration system 5 is composed of the server 30, the smartphone 40, and the infusion pump 50.

As shown in FIG. 10, the smartphone 40 includes a control unit 41, a memory unit 42, a touch screen 43, a scanner 44, a Wi-Fi communication unit 45, and a reader/writer 46. The control unit 41 controls the overall operation of the smartphone 40. For example, the control unit 41 controls the screen display on the touch screen 43. The memory unit 42 stores an operating system and various application programs including the above-mentioned specific application programs. These are executed by the control unit 41 (more specifically, the processor).

The touch screen 43 includes a display 431 and a touch panel 432. The touch panel 432 is superimposed on the display 431. The scanner 44 includes a camera 441 and a data processing unit 442. The camera 441 includes an image sensor (not shown). The data processing unit 442 performs various types of data processing. In this example, the data processing unit 442 functions as a barcode reader. The scanner 44 sends the patient ID, order ID, and pump ID_BAR to the control unit 41.

The Wi-Fi communication unit 45 is a communication interface that performs wireless communication via Wi-Fi. As shown in FIG. 5 as "(ii) Patient ID," "(vi) Order ID," and "(xviii) Comparison result," the smartphone 40 uses the Wi-Fi communication unit 45 to transmit the patient ID, the order ID, and the comparison result between the setting values to the server 30.

The reader/writer 46 includes a transmitter 461 and a receiver 462. As described above, the smartphone 40 uses the reader/writer 46 to perform short-range wireless communication with the infusion pump 50. As shown as "(viii) Request signal" in FIG. 5, the smartphone 40 transmits (transfers) a request signal requesting transmission of the pump ID_NFC to the infusion pump 50. As shown as "(xii) Order information" in FIG. 5, the smartphone 40 transmits (transfers) the order information acquired from the server 30 to the infusion pump 50.

The control unit 41 of the smartphone 40 compares the pump ID_BAR with the pump ID_NFC, as shown in FIG. 5 as "(x) Comparison of pump IDs." The control unit 41 associates the pump ID_BAR (or pump ID_NFC) with the order ID and stores them in the storage unit 42, as shown in FIG. 5 as "(xi) Store pump ID and order ID in association."

The control unit 41 extracts order information from the multiple pieces of order information based on the pump ID and data table D4 received from the server 30, as shown in FIG. 5 as "(xvi) Extraction of order information." The data table D4 is stored in the storage unit 32. The control unit 41 compares the setting value at the start of drug solution administration with the setting value included in the order information, as shown in FIG. 5 as "(xvii) Comparison of setting value at start of drug solution administration with setting value included in order information." The comparison result is sent to the server 30 by the Wi-Fi communication unit 45, as described above.

The server 30 comprises a control unit 31, a memory unit 32, a wired communication unit 33, and a Wi-Fi communication unit 34. The control unit 31 controls the overall operation of the server 30. The memory unit 32 includes an operating system and various programs. These are executed by the control unit 31 (more specifically, a processor). The wired communication unit 33 is a communication interface for communicating with the servers 10 and 20 and the monitoring terminal 60.

When the server 30 receives the patient ID and order ID from the smartphone 40, as described above, it extracts order information containing an order ID that matches the received order ID from among the multiple order information #1, #2, ... #N.

The server 30 transmits the extracted order information to the smartphone 40 on the condition that the patient ID included in the extracted order information matches the patient ID received from the smartphone 40. Specifically, the server 30 transmits the order information to the smartphone 40 using the Wi-Fi communication unit 34, as shown as "(vii) Order information" in FIG. 5. Furthermore, the server 30 transmits the setting value at the start of drug solution administration and the pump ID received from the infusion pump 50 to the smartphone 40 using the Wi-Fi communication unit 34, as shown as "(xv) Setting value at the start of drug solution administration + pump ID" in FIG. 5.

The infusion pump 50 comprises a control unit 51, a memory unit 52, an operation button 53, a Wi-Fi communication unit 54, a display 55, and a non-contact IC card 56. The control unit 51 controls the overall operation of the infusion pump 50. The memory unit 52 stores an operating system and various programs. These are executed by the control unit 51 (more specifically, a processor).

The infusion pump 50 receives a request signal from the smartphone 40 via the non-contact IC card 56. Upon receiving the request signal, the infusion pump 50 transmits the pump ID_NFC of the infusion pump 50 to the smartphone 40. When the pump ID_NFC matches the pump ID_BAR, the smartphone 40 transmits the order information acquired from the server 30 to the infusion pump 50 ("(xi) Order information" in FIG. 5). The infusion pump 50 receives the order information via the non-contact IC card 56. This enables the infusion pump 50 to perform settings and operations based on the order information.

The infusion pump 50 communicates with the server 30 using the Wi-Fi communication unit 54. As shown in FIG. 5 as "(xiv) Setting value at start of drug administration + pump ID," the infusion pump 50 transmits the setting value at the start of drug administration and the pump ID to the smartphone 40 using the Wi-Fi communication unit 34. The infusion pump 50 transmits the operation status information of the infusion pump 50 to the server 30 using the Wi-Fi communication unit 54 ("(xix) Operation status information" in FIG. 5). The monitoring terminal 60 can obtain the operation status information from the server 30 and display the operation status information on a display. This allows staff to monitor the operation status of the infusion pump 50 using the monitoring terminal 60.

(F. Sequence)
Fig. 11 is a sequence diagram for explaining the flow of the data processing in the medicinal liquid administration system 5 in the first half. Fig. 12 is a sequence diagram for explaining the flow of the data processing in the medicinal liquid administration system 5 in the second half.

As shown in FIG. 11, in sequence SQ1, the smartphone 40 reads the barcode 811 printed on the wristband 810 of the target patient with the scanner 44. In sequence SQ2, the smartphone 40 transmits the patient ID, which is the result of reading the barcode 811, to the server 30.

In sequence SQ3, the staff sets the medication (infusion pack) in the infusion pump 50 (in this example, infusion pump 50B). In sequence SQ4, the smartphone 40 uses the scanner 44 to read the barcode 511 printed on the sticker 510 of the infusion pump 50B.

In sequence SQ5, the smartphone 40 reads the barcode 821 printed on the drug label 820 of the target patient with the scanner 44. In sequence SQ6, the smartphone 40 transmits the order ID, which is the result of reading the barcode 821, to the server 30.

In sequence SQ7, the server 30 extracts order information that contains the same order ID as the order ID received from the smartphone 40 from among multiple pre-stored order information. In sequence SQ8, the server 30 extracts the patient ID contained in the extracted order information. In sequence SQ9, the server 30 checks whether the patient ID received from the smartphone 40 matches the patient ID extracted from the order information.

If the two patient IDs match, in sequence SQ10, the server 30 transmits the order information extracted in sequence SQ7 to the smartphone 40, as shown in FIG. 12. In sequence SQ11, the smartphone 40 accepts a transfer operation of the order information received from the server 30. Note that the transfer operation refers to the selection of the image object 481 and the holding of the smartphone 40 over the infusion pump 50.

When the smartphone 40 is held over the infusion pump 50B, communication between the smartphone 40 and the infusion pump 50B is established in sequence SQ12. In sequence SQ13, the smartphone 40 transmits a request signal to the infusion pump 50B with which communication has been established, via short-range wireless communication, requesting transmission of the pump ID. In sequence SQ14, the infusion pump 50B transmits a pump ID_NFC to the smartphone 40 as a response signal.

In sequence SQ15, the smartphone 40 determines whether the received pump ID_NFC matches the pump ID_NFC obtained by scanning the barcode 511. If the two pump IDs match, in sequence SQ16, the smartphone 40 transmits the order information to the infusion pump 50B by short-range wireless communication.

In sequence SQ17, the infusion pump 50B starts administering the medicinal fluid based on the received order information upon receiving a press of the start button 591. In sequence SQ18, the smartphone 40 stores the pump ID and the order ID in association with each other.

As shown in FIG. 13, after sequence SQ17, in sequence SQ19, the infusion pump 50B transmits the setting values at the start of drug administration and the pump ID to the server 30. In sequence SQ20, the server 30 transfers the setting values at the start of drug administration and the pump ID to the smartphone 40.

In sequence SQ21, the smartphone 40 has a pump ID and data table D4, and extracts one piece of order information from among the multiple pieces of order information stored in the smartphone 40. In sequence SQ22, the smartphone 40 compares the setting value at the start of drug solution administration with the setting value included in the extracted order information.

In sequence SQ23, the smartphone 40 notifies the server 30 of the comparison result. In sequence SQ24, the server 30 executes processing according to the comparison result. Specifically, if the setting values match, the server 30 continues wireless communication with the infusion pump 50B and acquires operating status information from the infusion pump 50B. If the setting values do not match, the server 30 cuts off wireless communication with the infusion pump 50B.

If wireless communication between the server 30 and the infusion pump 50B is not interrupted, the infusion pump 50B periodically transmits operating status information of the infusion pump 50B to the server 30, as shown in sequence SQ25.

If the settings do not match, the smartphone 40 displays a screen indicating that the settings have been changed, as described above. This display allows staff to notice that an unintended change has been made to the settings of the infusion pump 50.

The server 30 may be configured to send a command to the infusion pump 50 to stop operation of the infusion pump 50 before cutting off wireless communication.

G. Modifications
(1) Fig. 14 is a diagram showing a modification of the group of drug solution administration pumps 500 shown in Fig. 1. As shown in Fig. 14, the drug solution administration system 5 may include a group of drug solution administration pumps 500A instead of the group of drug solution administration pumps 500. The group of drug solution administration pumps 500A includes, as an example, a plurality of infusion pumps 55A, 55B and a plurality of syringe pumps 56A, 56B, 56C.

The multiple infusion pumps 55A, 55B and the multiple syringe pumps 56A, 56B, 56C are housed in a rack. The multiple infusion pumps 55A, 55B and the multiple syringe pumps 56A, 56B, 56C are arranged in a vertical line in the rack. When such drug administration pumps are arranged in close proximity, it is preferable to have a configuration in which the order information is transmitted after determining whether the pump IDs match as described above.

(2) In the above, as shown in FIG. 8, the smartphone 40 obtains the order ID by reading the barcode 821 on the medication label 820. However, this is not limited to this. The order ID may be obtained by reading the injection prescription with the smartphone 40. Information such as the patient ID, name, age, and two-dimensional code is printed on the injection prescription. The staff member can use the smartphone 40 to read the two-dimensional code (e.g., a QR code) in which the order ID is expressed (written).

(3) In the above, an example has been described in which the barcode 811 on the wristband 810 is scanned, and then the barcode 821 on the medication label 820, etc. is scanned. That is, an example has been described in which the smartphone 40 first acquires the patient ID, and then acquires the order ID. However, this is not limited to this. The smartphone 40 may acquire the patient ID after acquiring the order ID.

(4) The order of steps (iii), (iv), and the series of steps (v) to (vii) shown in FIG. 5 is not limited to the order described above.

(5) In the above, the smartphone 40 is described as transmitting a request signal to the infusion pump 50, but the present invention is not limited to this. The medical fluid administration system 5 may be configured so that the infusion pump 50 transmits the pump ID_NFC to the smartphone 40 without receiving a request signal. For example, the medical fluid administration system 5 may be configured so that the infusion pump 50 transmits the pump ID_NFC to the smartphone 40 when the establishment of short-range wireless communication is triggered.

(6) In the above, an example has been described in which the smartphone 40 acquires a staff ID, a patient ID, a pump ID, and an order ID by scanning each code, such as a barcode, with the smartphone 40. However, this is not limited to this. The staff member may manually or by voice input these IDs into the smartphone 40, which causes the smartphone 40 to acquire these IDs.

If a staff member remembers his/her staff ID, he/she can simply input the staff ID into smartphone 40 based on that memory. Normally, the staff member has a staff ID attached to the name tag they wear. Therefore, if a staff member forgets his/her staff ID, he/she can simply check his/her name tag and input his/her staff ID into smartphone 40.

As shown in FIG. 6, the patient ID is written on the wristband 810 in numbers or the like (in the example of FIG. 6, "00000045") so that it can be read by staff. The staff may input the numbers or the like into the smartphone 40. By performing such an operation, the smartphone 40 can obtain the patient ID.

As shown in FIG. 7, the pump ID is written on the sticker 510 in numbers or the like (in the example of FIG. 7, "02405015") so that it can be read by staff. The staff may input the numbers or the like into the smartphone 40. By performing such an operation, the smartphone 40 can obtain the pump ID_BAR.

As shown in FIG. 8, the order ID is written on the medication label 820 in numbers or the like (in the example of FIG. 8, "3000055040671010100") so that it can be read by staff. The staff may input the numbers or the like into the smartphone 40. By performing such an operation, the smartphone 40 can obtain the order ID.

As with the drug label 820, the order ID is written on the injection prescription in numbers or the like (not shown) so that it can be read by staff. Therefore, the staff may input the numbers or the like into the smartphone 40. This operation also allows the smartphone 40 to obtain the order ID.

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 claims, and is intended to include all modifications within the meaning and scope of the claims.

1 Medical system, 5 Drug administration system, 10, 20, 30 Server, 31, 41, 51 Control unit, 32, 42, 52 Memory unit, 33 Wired communication unit, 34, 45, 54 Communication unit, 40 Smartphone, 43 Touch screen, 44 Scanner, 46 Reader/writer, 49, G41, G42, G43, G44, G45, G46, G47, G48, G49, G50, G51, G61 Screen, 50, 50A, 50B, 50C, 55A, 55B Infusion pump, 53 Operation button, 55, 431 Display, 56 Card, 56A, 56B, 56C Syringe pump, 60 Monitoring terminal, 432 Touch panel, 441 Camera, 442 Data processing unit, 461 Transmission unit, 462 Receiving unit, 471, 472, 473, 474, 475, 476, 477, 478, 480, 481, 482, 483, 484, 485, 486, 491, 492 Image object, 500, 500A Drug administration pump group, 510 Sticker, 511, 811, 821 Barcode, 590 Felica mark, 591 Start button, 810 Wristband, 820 Drug label, 901 Hand, 951 Wrist, 4781, 4801, 4901 Reset button, 4821 Cancel button, D4 Data table.

Claims (6)

A server device;
A terminal device that communicates with the server device;
a liquid administration pump capable of communicating between the server device and the terminal device;
The terminal device acquires order information including a prescription order for an injection for a patient from the server device, and transmits the order information to the drug solution administration pump;
The prescription order includes a set value that specifies the operation of the drug solution administration pump;
The drug solution administration pump is capable of accepting a change operation of the set value and transmits the set value at the start of drug solution administration to the server device;
A drug solution administration system in which, if a setting value included in the order information sent to the terminal device does not match a setting value received from the drug solution administration pump at the start of drug solution administration, the server device cuts off communication with the drug solution administration pump. The terminal device
Acquire from the server device a set value at the start of administration of the medicinal liquid;
transmitting a predetermined signal to the server device when the set value at the start of the medicinal liquid administration is not the same as the set value included in the order information;
The chemical liquid administration system according to claim 1 , wherein the server device cuts off the communication with the chemical liquid administration pump when the server device receives the predetermined signal. The terminal device
A plurality of pieces of order information different from each other are stored,
When transmitting one of the order information to the liquid administration pump, pump identification information for identifying the liquid administration pump is acquired from the liquid administration pump;
The acquired pump identification information is stored in association with the order information transmitted to the drug solution administration pump;
The liquid administration pump transmits a set value at the start of the liquid administration to the server device in association with the pump identification information;
The terminal device
acquiring, from the server device, a setting value at the start of administration of the medicinal liquid in a state associated with the pump identification information;
extracting, from the plurality of pieces of order information, the order information associated with the same pump identification information as the pump identification information associated with the set value at the start of the medicinal liquid administration;
The medicinal liquid administration system according to claim 2 , wherein the predetermined signal is transmitted to the server device when the setting value at the start of the medicinal liquid administration is not the same as the setting value included in the extracted order information. Each of the order information includes order identification information for identifying the order information,
The terminal device
Associating the acquired pump identification information with the order identification information of the order information transmitted to the liquid administration pump, thereby associating the acquired pump identification information with the order information transmitted to the liquid administration pump;
The medical solution administration system according to claim 3, further comprising: extracting, from the plurality of order information, order information including the order identification information associated with the same pump identification information as the pump identification information associated with the setting value at the start of the medical solution administration. The liquid medicine administration system according to any one of claims 1 to 4, wherein, when a setting value included in the order information transmitted to the terminal device matches a setting value received from the liquid medicine administration pump at the start of the liquid medicine administration, the server device periodically acquires information indicating the operating status of the liquid medicine administration pump from the liquid medicine administration pump. A step in which the terminal device acquires order information including a prescription order for an injection for a patient from the server device;
The terminal device transmits the order information to a liquid administration pump;
The prescription order includes a set value that specifies the operation of the drug solution administration pump;
In the liquid administration pump, the set value can be changed based on an operator's operation,
Establishing communication between the drug solution administration pump and the server device;
a step of transmitting the setting value at the start of drug solution administration by the drug solution administration pump to the server device;
the server device cutting off the communication with the liquid drug administration pump if a setting value included in the order information sent to the terminal device does not match a setting value received from the liquid drug administration pump at the start of the liquid drug administration.

Images