Chemical solution dosing system, terminal device, and information processing method

Abstract

To provide a chemical solution dosing system with which it is possible to simplify the operation of correlating a chemical solution dosing pump and a medicine to each other.SOLUTION: The chemical solution dosing system comprises a server device, a terminal device, and a plurality of chemical solution dosing pumps in each of which a medicine-containing container is set. Order identification information is written to each container. Pump identification information is written in a position on each chemical solution dosing pump where the information is recognizable simultaneously with the order identification information of medicine. The terminal device scans each pump identification information and each order identification information at a time so as to collectively acquire each pump identification information and each order identification information. The terminal device associates, for each chemical solution dosing pump, the pump identification information of the chemical solution dosing pump and the order identification information of medicine set to the chemical solution dosing pump with each other and transmits each pump identification information and each order identification information in a mutually associated state to the server device.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present disclosure relates to a drug solution administration system, a terminal device, and an information processing method. [Background technology]

[0002] Conventionally, in hospitals and the like, liquid medicine administration pumps such as infusion pumps and syringe pumps are used. Japanese Patent Application Laid-Open Publication No. 2011-87678 (Patent Document 1) discloses an infusion pump in which a portable setting terminal having an operation unit for setting designated values ​​of a planned amount and a 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-distance 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 ​​of 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 ​​of the planned amount and flow rate. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-87678 A Summary of the Invention [Problem to be solved by the invention]

[0004] In a hospital, multiple liquid administration pumps are used simultaneously. In an operating room, multiple liquid administration pumps are used for one patient. In such an environment, when remote status monitoring of each liquid administration pump is performed using a network, a server device capable of communicating with each liquid administration pump needs to know in advance which drug is installed in which liquid administration pump. That is, the liquid administration pump and the drug need to be stored in association with each other in the server device. Therefore, it is desirable to simplify the operation of associating (linking) the liquid administration pump and the drug.

[0005] The present disclosure provides a medical solution administration system, a terminal device, and an information processing method that can simplify the operation of associating a medical solution administration pump with a drug. [Means for solving the problem]

[0006] According to an aspect of the present disclosure, a liquid administration system includes a server device, a terminal device, and a plurality of liquid administration pumps, each of which is set with a container containing a drug. Each container is marked with order identification information for identifying order information including a prescription order for the drug. Each liquid administration pump is marked with pump identification information for identifying the liquid administration pump, at a position where the pump identification information and the order identification information for the drug contained in the set container can be viewed at the same time. The terminal device acquires each pump identification information and each order identification information at once by scanning each pump identification information and each order identification information at once. The terminal device associates, for each liquid administration pump, the pump identification information of the liquid administration pump with the order identification information of the drug contained in the container set in the liquid administration pump, based on the positional relationship between each pump identification information and each order identification information acquired. The terminal device transmits each pump identification information and each order identification information in the associated state to the server device.

[0007] According to another aspect of the present disclosure, an information processing device is an information processing device constituting the above-mentioned medicinal liquid administration system.

[0008] According to yet another aspect of the present disclosure, an information processing method includes a step of acquiring each pump identification information and each order identification information at once by simultaneously scanning order identification information written on a container containing a drug set in each of a plurality of drug solution administration pumps and pump identification information written in a position on each of the plurality of drug solution administration pumps that is visible simultaneously with the order identification information; a step of associating, for each drug solution administration pump, the pump identification information of the drug solution administration pump with the order identification information of the drug in a container set in the drug solution administration pump based on a positional relationship between each of the acquired pump identification information and each order identification information; and a step of transmitting each pump identification information and each order identification information in an associated state to a server device. Effect of the Invention

[0009] According to the present disclosure, it is possible to simplify the operation of associating a drug with a drug solution administration pump. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing a configuration of a medical system including a drug solution administration system. [Diagram 2] FIG. 2 is a diagram for explaining information stored in a server. [Diagram 3] FIG. 13 is a diagram showing the first half of the screen transition of the smartphone. [Figure 4] FIG. 13 shows the latter half of the screen transition on the smartphone. [Diagram 5] FIG. 2 is a diagram showing the flow of data in the drug solution administration system. [Figure 6] FIG. 13 is a diagram showing reading of a wristband by a smartphone. [Figure 7] FIG. 13 is a diagram showing an image of a group of drug solution administration pumps taken with a smartphone. [Figure 8] FIG. 13 is a diagram showing a device label. [Figure 9] FIG. 13 shows a drug label. [Figure 10]FIG. 13 is a diagram showing a staff member touching a drug solution administration pump using a smartphone. [Figure 11] FIG. 2 is a block diagram of each device that constitutes the drug solution administration system. [Figure 12] FIG. 11 is a sequence diagram for explaining the flow of a first part of data processing in the drug solution administration system. [Figure 13] FIG. 11 is a sequence diagram for explaining the flow of a second part of the data processing in the drug solution administration system. [Figure 14] FIG. 11 is a sequence diagram for explaining the flow of a third part of the data processing in the drug solution administration system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In the following description, the same members are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

[0012] (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 a terminal device (information processing device), and a group of medicinal liquid administration pumps 500.

[0013] In this example, the group of chemical liquid administration pumps 500 includes a plurality of chemical liquid administration pumps 50A, 50B, 50C, 50D, and 50E. The chemical liquid administration pumps 50A to 50E are housed in a rack 90. ​​The chemical liquid administration pumps 50A to 50E are arranged adjacent to each other in this order from top to bottom. The chemical liquid administration pumps 50A to 50E are housed in a vertical row within the rack 90.

[0014] The liquid medicine administration pumps 50A and 50B are infusion pumps. The liquid medicine administration pumps 50C, 50D, and 50E are syringe pumps. In this example, a syringe 591 containing a medicine is installed (set) in the liquid medicine administration pump 50C. The liquid medicine administration pumps 50D and 50E are installed with syringes 592 and 593 containing a medicine, respectively. The liquid medicine administration pumps 50C, 50D, and 50E are used for one patient. In the following, for the sake of simplicity of explanation, it is assumed that no infusion bag is installed in the liquid medicine administration pumps 50A and 50B. The syringes 591 to 593 are examples of containers containing a medicine. The part of the infusion bag excluding the medicine is also an example of a container containing a medicine.

[0015] For ease of explanation, any one of the liquid drug administration pumps 50A, 50B, 50C, 50D, and 50E will be referred to below as "liquid drug administration pump 50." In this example, five liquid drug administration pumps 50A to 50E are given as an example, but the number of liquid drug administration pumps is not limited to this.

[0016] The terminal 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.

[0017] The server 30 is communicatively connected to the servers 10, 20, and the monitoring terminal 60. Typically, the server 30 is connected to the servers 10, 20, and the monitoring terminal 60 by wires. The server 10 is communicatively connected to the server 20. Typically, the server 10 is connected to the server 20 by wires. Note that the server 30 may be communicatively connected to the monitoring terminal 60 wirelessly.

[0018] The server 30 is configured to be able to communicate with the smartphone 40 and each of the liquid dispensing pumps 50. Typically, the server 30 can establish communication between the smartphone 40 and the liquid dispensing pumps 50 via a wireless LAN (Local Area Network). In this example, Wi-Fi (registered trademark) is used as a type of wireless LAN communication method. Wi-Fi is an abbreviation for "Wireless Fidelity."

[0019] The smartphone 40 communicates with the liquid dosing pump 50. The smartphone 40 performs wireless communication with the liquid dosing pump 50. The smartphone 40 performs near field communication (NFC) with the liquid dosing pump 50. In this example, the smartphone 40 communicates with the liquid dosing pump 50 using Felica (registered trademark), which is a Type-F of NFC.

[0020] Smartphone 40 has a built-in reader / writer for Felica. The reader / writer has a control board and an antenna. Felica Link is implemented in liquid dosing pump 50. Liquid dosing 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."

[0021] In this example, by bringing smartphone 40 operating as a reader / writer close to liquid dosing pump 50 operating as a tag, short-range wireless communication is performed between smartphone 40 and liquid dosing pump 50. For example, by bringing smartphone 40 close to liquid dosing pump 50A, short-range wireless communication is performed between smartphone 40 and liquid dosing pump 50A. The reason that smartphone 40, rather than liquid dosing pump 50, has a built-in reader / writer is that smartphone 40 is expected to perform short-range wireless communication with multiple other pumps (not shown) in the same way as liquid dosing pump 50.

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

[0023] When the server 10 acquires order information including a prescription order for an injection for a patient created by a doctor, the server records the received order information in the electronic medical record of the patient. The prescription order is created using a terminal (not shown) used by the doctor. During one treatment, the doctor creates 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.

[0024] The server 20 stores 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.

[0025] Server 20 acquires order information of a specified patient from server 10 based on an input operation by a pharmacist or the like. Server 20 transmits order information of a patient about to start treatment (hereinafter also referred to as a "target patient") to server 30. Servers 10 and 20 may handle multiple pieces of order information of the target patient as one list information. Staff in the pharmacy department judge whether the order information acquired by server 20 from server 10 is appropriate.

[0026] (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.

[0027] 1, the storage unit 32 of the server 30 stores staff master data, patient master data, the latest drug library data, and a plurality of pieces of order information #1, #2, ... #N. Each piece of order information #1, #2, ... #N includes information such as an order ID (Identification) 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.

[0028] 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 the 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.

[0029] 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 a "scheduled amount."

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

[0031] (C. User operations and data transmission and reception) Fig. 3 is a diagram showing the first half of the screen transition of smartphone 40. Fig. 4 is a diagram showing the second half of the screen transition of smartphone 40. Fig. 5 is a diagram showing the flow of data in medicinal liquid administration system 5. Below, the operations of the staff will be explained with reference to Figs. 3 and 4, etc., and the data exchanged by the operations will be explained with reference to Fig. 5 as appropriate.

[0032] With reference to Fig. 3, when the smartphone 40 starts a predetermined application program by an operation of a staff member, the smartphone 40 displays a screen G41 on the touch screen 43 as shown in state (A) of Fig. 3. The screen G41 is a login screen. The screen G41 includes an image object 471. 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).

[0033] When the staff member selects image object 471 with the fingers of his / her hand 901, reading of the barcode using the camera is started. 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 has a staff ID written on it. In this manner, the staff ID is read by smartphone 40.

[0034] After the smartphone 40 reads the barcode, the staff member inputs a password into the smartphone 40. The staff member then selects a specific image object, which causes the smartphone 40 to transmit 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.

[0035] When the staff member is authenticated, the smartphone 40 displays a screen G42 on the touch screen 43 as shown in state (B). The screen G42 is a menu screen. The screen G42 includes image objects 472, 473, 474, and 475.

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

[0037] When the staff member selects image object 473 with his / her finger, smartphone 40 displays screen G43 on touch screen 43 as shown in state (C). Screen G43 and screens G44 to G50 described below 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 selection process (reading process) of a patient ID.

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

[0039] Fig. 6 is a diagram showing reading of a wristband by smartphone 40. As shown in Fig. 6, information such as the name, date of birth, blood type, and barcode 711 is printed on wristband 710 wrapped around wrist 951 of a subject patient. Staff reads barcode 711 using smartphone 40. Barcode 711 indicates (describes) the patient ID. In this manner, the patient ID is read by smartphone 40.

[0040] As shown as "(i) Photographing barcode on wristband" in Fig. 5, when the smartphone 40 reads the barcode 711, it transmits the patient ID to the server 30 as shown as "(ii) Patient ID" in Fig. 5. Typically, the smartphone 40 transmits the patient ID to the server 30 via wireless LAN after confirmation input by the staff (selection of an image object such as a send button).

[0041] 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 a screen G44 on the touch screen 43 as shown in state (D) of FIG. 3. The screen G44 includes an image object 478, an image object 491, and an image object 477. In state (D), of the image objects 491 and 477, only the image object 491 is selectable. The image object 491 is an object for transitioning to a process of reading the pump ID and the order ID.

[0042] The image object 478 indicates the patient ID obtained by reading the barcode 711. Note that the patient ID can be reset by selecting a reset button 4781 in the object 478.

[0043] When the staff member selects with his / her finger image object 491 shown in state (D) in Fig. 3, smartphone 40 resumes reading the barcode using the camera. As shown in Fig. 5 as "(iii) Photographing group of drug solution administration pumps 500", the staff member photographs group of drug solution administration pumps 500 housed in rack 90 with the camera of smartphone 40.

[0044] Fig. 7 is a diagram showing an image of a group of liquid drug dispensing pumps 500 captured by a smartphone 40. As shown in Fig. 7, an adhesive device label 510A is attached to liquid drug dispensing pump 50A. Similarly, adhesive device labels 510B, 510C, 510D, and 510E are attached to liquid drug dispensing pumps 50B to 50E, respectively.

[0045] In this example, each of device labels 510A-510E is attached to the front surface of liquid dosing pump 50. Device label 510C is attached at a position that does not interfere with syringe 591 (including the tube attached to the tip) when viewed from the front of liquid dosing pump 50C. In this example, device label 510C is attached at a higher position (above) than syringe 591.

[0046] Similarly, device labels 510D and 510E are affixed at positions that do not interfere with syringes 592 and 593 when viewed from the front of rack 90 (when viewed from the front of drug solution administration pumps 50D and 50E), respectively. Device label 510D is affixed at a position higher than syringe 592. Device label 510D is affixed at a position higher than syringe 593.

[0047] FIG. 8 is a diagram showing device label 510C. As shown in FIG. 8, device label 510C has printed thereon barcode 511 indicating pump ID (serial number) of liquid dosing pump 50C. Furthermore, device label 510C has written thereon the pump ID in numbers ("02405015") so that staff can read it. Similarly, device labels 510A, 510B, 510D, and 510E have printed thereon barcode 511 indicating pump ID of each liquid dosing pump 50A, 50B, 50D, and 50E.

[0048] For ease of explanation, the pump ID of the liquid dosing pump 50A will be referred to as "pump ID_A" below. Similarly, the pump IDs of the liquid dosing pumps 50B, 50C, 50D, and 50E will be referred to as "pump ID_B," "pump ID_C," "pump ID_D," and "pump ID_E," respectively.

[0049] 7, each of syringes 591-593 has a piston (push piece, plunger) and a syringe (syringe barrel, outer barrel) into which the piston is pushed. Drug label 810C is attached to syringe 591 (more specifically, the syringe). Similarly, drug labels 810D and 810E are attached to the syringes of syringes 592 and 593, respectively.

[0050] Syringe 591 is installed in liquid dispensing pump 50C so that drug label 810C faces the front. Syringe 591 is installed in liquid dispensing pump 50C so that drug label 810C is visible when viewed from the front of liquid dispensing pump 50C. Similarly, syringes 592 and 593 are installed in liquid dispensing pumps 50D and 50E so that drug labels 810D and 810E face the front, respectively.

[0051] In this example, device label 510A, device label 510B, device label 510C, medicine label 810C, device label 510D, medicine label 810D, device label 510E, and medicine label 810E are arranged in this order from top (ceiling side) to bottom (floor side).

[0052] Fig. 9 is a diagram showing a drug label 810C. As shown in Fig. 9, information such as a patient ID, name, age, and a barcode 811 is printed on the drug label 810C. The barcode 811 expresses (describes) an order ID that identifies the order information of the drug contained in the syringe 591. Furthermore, the order ID is written in numbers ("3000055040671010100") on the drug label 810C so that it is readable by staff.

[0053] Similarly, information such as the patient ID, name, age, and barcode 811 is printed on drug labels 810D and 810E. The barcode on drug label 810D represents an order ID that identifies the order information of the drug contained in syringe 592. The barcode 811 on drug label 810E represents an order ID that identifies the order information of the drug contained in syringe 593.

[0054] In the following, the order ID printed on the medicine label 810C is also referred to as "order ID_C." Similarly, the order IDs printed on the medicine labels 810D and 810E are also referred to as "order ID_D" and "order ID_E," respectively.

[0055] 7, the display surfaces (printed surfaces) of the barcodes 511, 811, etc. of the device labels 510A-510E and the drug labels 810C-810E face the same direction (the front side of the rack 90 in this example). In more detail, the staff sets the syringes 591-593 in the drug solution administration pumps 50C-50E so that the drug labels 810C-810E face the front side.

[0056] In this manner, each liquid dosing pump 50 (liquid dosing pumps 50C-50E in this example) is marked with a pump ID (barcode 511, numbers) for identifying the liquid dosing pump, in a position that is visible simultaneously with the order ID (barcode 811, numbers) of the drug set in the liquid dosing pump 50. In detail, pump ID_A, pump ID_B, pump ID_C, order ID_C, pump ID_D, order ID_D, pump ID_E, and order ID_E are lined up in this order from top (ceiling side) to bottom (floor side) facing the front side of rack 90.

[0057] The location of each device label 510A-510E is not limited to the front of liquid administration pump 50. It is sufficient that the pump ID for identifying the liquid administration pump is written in a position that is visible at the same time as the order ID of the drug set in liquid administration pump 50.

[0058] The staff member simultaneously captures images of each liquid administration pump 50 using the scanning screen G55 displayed on the smartphone 40. By capturing the images of the liquid administration pumps 50, the barcodes 511 on the device labels 510A-510E and the barcodes 811 on the drug labels 810C-810E are read. The barcodes 511 and 811 are read by a single scanning operation by the staff member.

[0059] In addition, since no drug is set in the liquid medicine administration pumps 50A and 50B, the staff may use the camera of the smartphone 40 to capture images of only the liquid medicine administration pumps 50C, 50D, and 50E among the liquid medicine administration pumps 50A to 50E.

[0060] Smartphone 40 simultaneously obtains pump IDs of five liquid administration pumps 50 by reading five barcodes 511. Smartphone 40 simultaneously obtains order IDs of three drugs by reading three barcodes 811. In more detail, smartphone 40 obtains five pump IDs and three order IDs by one scanning operation by the staff member.

[0061] Based on the above-mentioned positional relationship between each acquired pump ID and each order ID, smartphone 40 associates the pump ID of liquid administration pump 50 with the order ID of the drug set in liquid administration pump 50 for each liquid administration pump 50. In this example, smartphone 40 associates pump ID_C of liquid administration pump 50C with order ID_C of the drug set in liquid administration pump 50C. It associates pump ID_D of liquid administration pump 50D with order ID_D of the drug set in liquid administration pump 50D. It associates pump ID_E of liquid administration pump 50E with order ID_E of the drug set in liquid administration pump 50E.

[0062] In addition, the smartphone 40 determines from the image data obtained by imaging that no medicine is set in the liquid administration pumps 50A and 50B. Therefore, the smartphone 40 does not associate an order ID with each pump ID of the liquid administration pumps 50A and 50B.

[0063] The smartphone 40 may be equipped with a learning program that has previously learned the positional relationship between each pump ID and each order ID. Alternatively, the smartphone 40 may associate the pump ID of the liquid administration pump 50 with the order ID of the drug set in the liquid administration pump 50 for each liquid administration pump 50 based on various information such as the vertical arrangement (disposition) of the printed pump IDs and order IDs, and the vertical separation distance between the pump IDs and order IDs.

[0064] As shown in FIG. 5 as "(iv) order ID, pump ID", smartphone 40 transmits each pump ID and each order ID to server 30 in the above-mentioned association state. Specifically, smartphone 40 transmits pump ID_C of liquid dosing pump 50C and order ID_C of the drug set in liquid dosing pump 50C in an associated state to server 30. Similarly, smartphone 40 transmits pump ID_D of liquid dosing pump 50D and order ID_D of the drug set in liquid dosing pump 50D in an associated state to server 30. Smartphone 40 transmits pump ID_E of liquid dosing pump 50E and order ID_E of the drug set in liquid dosing pump 50E in an associated state to server 30.

[0065] Typically, after confirmation input by the staff (selection of an image object such as a send button), the smartphone 40 transmits the order ID and the pump ID to the server 30 via wireless LAN. Note that in this example, the smartphone 40 does not transmit the pump IDs_A and ID_B of the drug solution administration pumps 50A and 50B to the server 30 because the pump IDs_A and ID_B are not associated with the order ID.

[0066] When the server 30 acquires the patient ID, followed by the order IDs and the pump IDs from the smartphone 40, the server 30 executes the following process. The server 30 extracts, from among the order information #1, #2, ..., #3 stored in the storage unit 32 (FIG. 2), a plurality of pieces of order information including order IDs that match each order ID sent from the smartphone 40. That is, the server 30 extracts, from among the order information #1, #2, ..., #3, three pieces of order information including order IDs that match each order ID obtained by reading the three barcodes 811 on the drug labels 810C-810E with the smartphone 40.

[0067] Next, the server 30 determines whether or not each patient ID (see FIG. 2) included in the extracted three pieces of order information matches the patient ID sent from the smartphone 40. That is, the server 30 determines whether or not each patient ID included in the extracted order information matches the patient ID obtained by reading the barcode 711 of the wristband 710 by the smartphone 40.

[0068] If it is determined that the patient IDs match, the server 30 transmits the extracted order information to the smartphone 40, as shown as "(v) Order Information" in Fig. 5. Specifically, the server 30 transmits the extracted order information to the smartphone 40 by using wireless LAN communication.

[0069] If the server 30 determines that the patient IDs do not match, it does not transmit the extracted order information to the smartphone 40. In this case, typically, the server 30 transmits information indicating an error or a warning to the smartphone 40.

[0070] The transmission of the order information by the server 30 to the smartphone 40 will be described in detail below. Based on the association between the pump ID and the order ID described above, the server 30 transmits each of the extracted three pieces of order information to the smartphone 40 in a state in which the pieces are associated with the pump ID associated with the order ID included in the order information. In particular, based on the association between the three pairs of pump IDs and order IDs described above, the server 30 transmits each of the extracted three pieces of order information to the smartphone 40 in a state in which the pieces are associated with the pump ID associated with the order ID received from the smartphone 40 that is the same as the order ID included in the order information (see FIG. 2).

[0071] In this manner, the association of the pump ID with the order information in the server 30 is performed by selecting, from the above three extracted order information, order information including an order ID (existing order ID) that matches the order ID received from the smartphone 40, and associating the selected order information with the pump ID associated with the order ID received from the smartphone 40. For example, the association of pump ID_C with order information_C is performed by selecting, from the above three order information, order information including an order ID that matches order ID_C received from the smartphone 40, and associating pump ID_C associated with order ID_C with the selected order information.

[0072] As described above, the server 30 transmits to the smartphone 40 order information (hereinafter also referred to as "order information_C") including the order ID_C of the drug set in the liquid administration pump 50C in a state associated with the pump ID_C of the liquid administration pump 50C. Similarly, the server 30 transmits to the smartphone 40 order information (hereinafter also referred to as "order information_D") including the order ID_D of the drug set in the liquid administration pump 50D in a state associated with the pump ID_D of the liquid administration pump 50D. The server 30 transmits to the smartphone 40 order information (hereinafter also referred to as "order information_E") including the order ID_E of the drug set in the liquid administration pump 50E in a state associated with the pump ID_E of the liquid administration pump 50E.

[0073] When the smartphone 40 acquires (receives) each piece of order information from the server 30, the smartphone 40 displays a screen G45 on the touch screen 43, as shown in state (E) of Fig. 3. The screen G45 includes an image object 478 and image objects 4901 to 4905.

[0074] Image object 4901 is an object for selecting liquid administration pump 50A (denoted as "pump #1"). Similarly, image objects 4902-4905 are objects for selecting liquid administration pumps 50B-50E (pumps #2-#5), respectively.

[0075] Smartphone 40 has not acquired order information for liquid administration pumps 50A and 50B. Therefore, in state (E), of image objects 4901 to 4905, only image objects 4903 to 4905 are selectable.

[0076] When the staff member selects the image object 4903, the smartphone 40 displays a screen G46 on the touch screen 43 as shown in state (F) in FIG.

[0077] Image object 480 shows the order information (excluding the patient ID) obtained from server 30. Image object 480 also shows that liquid administration pump 50C (pump #3) has been selected. By visually checking the order information included in image object 480, staff can confirm the prescription order for an injection for the target patient. Note that the order information can be reset (changed) by selecting a reset button 4801 in image object 480.

[0078] 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, smartphone 40 switches the screen displayed on 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 liquid administration pump 50.

[0079] Screen G47 includes an image object 478, an image object 480, and an image object 482. Image object 482 includes a guidance display that prompts the staff to move smartphone 40 closer to liquid administration pump 50C (pump #3). Image object 482 further includes a cancel button 4821 for canceling the transfer of order information to liquid administration pump 50. When the staff selects the cancel button 4821, smartphone 40 switches the screen from screen G47 to screen G45, for example.

[0080] FIG. 10 is a diagram showing a touch operation of the smartphone 40 on the liquid medicine administration pump 50C by the staff. As shown in FIG. 10, when the staff brings the smartphone 40 close to the liquid medicine administration pump 50C, short-range wireless communication is established between the smartphone 40 and the liquid medicine administration pump 50C. In detail, when the staff holds the smartphone 40 over the Felica mark 590 printed on the surface of the liquid medicine administration pump 50C, short-range wireless communication is established between the smartphone 40 and the liquid medicine administration pump 50C. When the wireless communication is established, the smartphone 40 transmits the order information_C to the liquid medicine administration pump 50C with which the short-range wireless communication is established, as shown as "(xi) order information" in FIG. 5.

[0081] When the order information_C 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 an image object 482, an image object 483, and an image object 484.

[0082] Image object 482 shows information about the target patient and the transferred order information. Image object 483 shows that the transfer of the order information has been completed. Image object 483 further includes a notification that prompts the staff member to press a setting completion button represented as image object 484 and to transfer the order information (order information_D, order information_E) to the remaining liquid administration pumps 50D and 50E.

[0083] When the staff member presses the setting completion button in state (H), smartphone 40 switches the screen displayed on touch screen 43 from screen G48 to screen G49, as shown in state (I) of Fig. 4. Screen G49 includes image object 478 and image objects 4901, 4902, 4913, 4904, and 4905. Image object 4913 indicates that the transfer of the order to liquid administration pump 50C (pump #3) has ended.

[0084] The staff member transmits order information_D to liquid administration pump 50D (pump #4) by selecting image object 4904 and repeating the same operations as those described based on state (F) and state (G). In this case, the staff member transmits order information_D to liquid administration pump 50D by holding smartphone 40 over liquid administration pump 50D.

[0085] Thereafter, the staff member selects a setting completion button (an image object similar to image object 484), whereby smartphone 40 switches the screen displayed on touch screen 43 from screen G49 to screen G50, as shown in state (J) of FIG. 4. Screen G49 includes image object 478 and image objects 4901, 4902, 4913, 4914, and 4905. Image object 4914 indicates that transfer of the order to liquid administration pump 50D (pump #4) has been completed.

[0086] The staff member transmits order information_E to liquid administration pump 50E (pump #5) by selecting image object 4905 and repeating the same operations as those described based on state (F) and state (G). In this case, the staff member transmits order information_E to liquid administration pump 50E by holding smartphone 40 over liquid administration pump 50E.

[0087] This completes the transfer of all of the order information_C, order information_D, and order information_E acquired from the server 30. When the smartphone 40 finishes transferring the last order information_E, it switches the screen displayed on the touch screen 43 from screen G50 to screen G51, as shown in state (K) in Fig. 4. Screen G51 includes image objects 485, 486, and 484.

[0088] Image object 485 shows the target patient information and the transferred order information. Image object 486 shows that the transfer of the order information is complete. Image object 486 further includes a notification urging the staff to press the setting completion button represented as image object 484 and to press the start button 515 (see FIG. 10) of each liquid administration pump 50 after pressing the setting completion button.

[0089] When the staff member presses the setting completion button in state (K), smartphone 40 switches the screen displayed on touch screen 43 from screen G51 to screen G42. That is, smartphone 40 transitions from state (K) to state (B), and causes touch screen 43 to display the menu screen.

[0090] As described above, when smartphone 40 receives a plurality of pieces of order information each associated with a pump ID, smartphone 40 transmits to each liquid administration pump 50 the order information associated with the pump ID of liquid administration pump 50. Specifically, smartphone 40 transmits order information_C to liquid administration pump 50C based on the association between order information_C and pump ID_C. Similarly, smartphone 40 transmits order information_D to liquid administration pump 50D based on the association between order information_D and pump ID_D. Smartphone 40 transmits order information_E to liquid administration pump 50E based on the association between order information_E and pump ID_E.

[0091] This allows each liquid administration pump 50 to obtain order information including the prescription order prescribed for the drug set in each liquid administration pump 50. When the start button 515 of each liquid administration pump 50 is pressed, each liquid administration pump 50 operates based on the obtained order information. This allows multiple drugs to be administered to the patient as prescribed by the doctor.

[0092] When the start button 515 of the liquid dosing pump 50C is pressed, the liquid dosing pump 50C periodically transmits operation status information of the liquid dosing pump 50C to the server 30, as shown as "(vii) Operation Status Information" in Fig. 5. The operation status information includes the pump status, the operation details by the staff, etc. in chronological order. Similarly, when the start button 515 of the liquid dosing pumps 50D, 50E is pressed, the liquid dosing pumps 50D, 50E periodically transmit operation status information of the liquid dosing pumps 50D, 50E, respectively, to the server 30.

[0093] In this way, the server 30 stores each piece of operation status information in association with the patient ID, order ID, and pump ID that are associated in advance. When the server 30 receives a transmission request for each piece of operation status information from the monitoring terminal 60, the server 30 transmits each piece of operation status information to the monitoring terminal 60 in real time.

[0094] (D. Small summary) (1) The medicinal liquid administration system 5 includes a server 30, a smartphone 40, and a plurality of medicinal liquid administration pumps 50, each of which is set with a container (specifically, syringes 591-593) containing a drug. An order ID that identifies order information including a prescription order for the drug is written on each container. A pump ID for identifying the medicinal liquid administration pump 50 is written on each medicinal liquid administration pump 50 in a position that can be seen simultaneously with the order ID of the drug contained in the set container.

[0095] Smartphone 40 acquires each pump ID and each order ID at once by scanning each pump ID and each order ID at once. Smartphone 40 associates, for each liquid administration pump 50, the pump ID of liquid administration pump 50 with the order ID of the drug contained in a container set in liquid administration pump 50 based on the positional relationship between each acquired pump ID and each order ID. Smartphone 40 transmits each pump ID and each order ID in an associated state to server 30.

[0096] According to this configuration, by scanning each pump ID and each order ID once with the smartphone 40, the server 30 can know which drug is installed in which liquid administration pump. That is, by a single scanning operation by the staff, the server 30 can store the liquid administration pump 50 and the drug in association with each other. Therefore, according to the liquid administration system 5, it is possible to simplify the operation of associating (linking) the liquid administration pump 50 and the drug by the staff in order to associate the liquid administration pump 50 and the drug and store them in the server 30.

[0097] (2) As shown in FIG. 2, the server 30 stores a plurality of pieces of order information. As shown in FIG. 2, each piece of order information includes an order ID. The server 30 extracts a plurality of pieces of order information including each received order ID from the plurality of pieces of order information. The server 30 transmits each piece of extracted order information to the smartphone 40 in a state in which the piece of order information is further associated with a pump ID associated with the order ID included in the order information based on the association between the pump ID and the order ID. When the smartphone 40 receives a plurality of pieces of order information each associated with a pump ID, the smartphone 40 transmits to each liquid administration pump 50 the order information associated with the pump ID of the liquid administration pump 50. With this configuration, each liquid administration pump can obtain order information corresponding to the set drug.

[0098] (E. Internal structure) 11 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 medicinal liquid administration pump 50.

[0099] 11, the smartphone 40 includes a control unit 41, a storage 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 storage unit 42 stores an operating system and various application programs including the above-mentioned predetermined application programs. These are executed by the control unit 41 (more specifically, a processor).

[0100] 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 a patient ID, multiple order IDs, and multiple pump IDs to the control unit 41.

[0101] The Wi-Fi communication unit 45 is a communication interface that performs wireless communication via Wi-Fi. As shown as "(ii) Patient ID" in Fig. 5, the smartphone 40 transmits a patient ID to the server 30 using the Wi-Fi communication unit 45. As shown as "(iv) Order ID, Pump ID" in Fig. 5, the smartphone 40 transmits a plurality of order IDs and a plurality of pump IDs to the server 30 using the Wi-Fi communication unit 45.

[0102] The reader / writer 46 includes a transmitting unit 461 and a receiving unit 462. As described above, the smartphone 40 performs short-range wireless communication with the liquid administration pump 50 using the reader / writer 46. The smartphone 40 transmits (transfers) the order information acquired from the server 30 to the liquid administration pump 50, as shown as "(xi) Order information" in FIG. 5.

[0103] The server 30 includes a control unit 31, a storage 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 control unit 31 has an extraction unit 311. The storage 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.

[0104] When the control unit 31 of the server 30 receives a set of multiple order IDs and multiple pump IDs from the smartphone 40, the control unit 31 manages the multiple order IDs and multiple pump IDs by associating the order IDs with the pump IDs on a one-to-one basis. The control unit 31 stores each order ID and pump ID received from the smartphone 40 in the storage unit 32 by associating the order IDs with the pump IDs on a one-to-one basis. The extraction unit 311 of the server 30 extracts multiple pieces of order information including order IDs that match each of the received order IDs from among the multiple pieces of order information #1, #2, ... #N, as described above, based on the multiple order IDs received from the smartphone 40.

[0105] The server 30 transmits the extracted multiple pieces of order information to the smartphone 40 in a state in which the multiple pieces of order information are associated with the pump ID as described above, on 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 each piece of order information to the smartphone 40 using the Wi-Fi communication unit 34, as shown as "(v) Order Information" in Fig. 5.

[0106] The liquid dosing pump 50 includes a control unit 51, a storage 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 liquid dosing pump 50. The storage unit 52 stores an operating system and various programs. These are executed by the control unit 51 (more specifically, a processor).

[0107] Smartphone 40 transmits the order information acquired from server 30 to liquid administration pump 50 via reader / writer 46 ("(xi) Order information" in FIG. 5). Liquid administration pump 50 receives the order information via non-contact IC card 56. This enables liquid administration pump 50 to perform settings and operations based on the order information.

[0108] The control unit 31 of the server 30 establishes wireless communication based on the Wi-Fi standard with the liquid dosing pump 50 using an IP address previously associated with each pump ID. The liquid dosing pump 50 that has established wireless communication with the server 30 communicates with the server 30 using the Wi-Fi communication unit 54. The liquid dosing pump 50 transmits operation status information to the server 30 using the Wi-Fi communication unit 54 ("(vii) Operation status information" in FIG. 5). The server 30 then receives the operation status information periodically transmitted from the liquid dosing pump 50. Specifically, the server 30 receives the operation status information via the Wi-Fi communication unit 34.

[0109] The monitoring terminal 60 (see FIG. 1) can obtain information indicating the operating status from the server 30 and display the operating status on a display. This allows staff to monitor the operating status of the liquid administration pump 50 using the monitoring terminal 60.

[0110] (F.Sequence) Fig. 12 is a sequence diagram for explaining the flow of a first part of data processing in the medicinal liquid administration system 5. Fig. 13 is a sequence diagram for explaining the flow of a second part of data processing in the medicinal liquid administration system 5. Fig. 14 is a sequence diagram for explaining the flow of a third part of data processing in the medicinal liquid administration system 5.

[0111] 12, in sequence SQ1, the smartphone 40 reads the barcode 711 printed on the wristband 710 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 711, to the server 30.

[0112] In sequence SQ3, the staff member captures an image of the group of medicinal liquid administration pumps 500 with the smartphone 40. In detail, the smartphone 40 simultaneously scans (collectively scans) the barcodes 511 of the multiple device labels 510 and the barcodes 811 of the multiple medicine labels 810C to 810E.

[0113] In sequence SQ4, in this example, the smartphone 40 transmits five pump IDs resulting from reading the five barcodes 511 and three order IDs resulting from reading the three barcodes 811 to the server 30. In this example, as described above, the smartphone 40 transmits pump ID_C, pump ID_D, and pump ID_E to the server 30 in a state in which they are associated with order ID_C, order ID_D, and order ID_E, respectively. Note that the smartphone 40 does not need to transmit pump ID_A and pump ID_B, which are not associated with an order ID.

[0114] In sequence SQ5, the server 30 extracts, from among a plurality of pre-stored order information, a plurality of order information items that contain the same order ID as each order ID received from the smartphone 40. In sequence SQ6, the server 30 extracts the patient ID included in each of the extracted order information items. In sequence SQ7, the server 30 checks whether the patient ID received from the smartphone 40 matches the patient ID extracted from each order information item.

[0115] If both patient IDs match, in sequence SQ8, the server 30 transmits the plurality of pieces of order information extracted in sequence SQ5 to the smartphone 40. In detail, as described above, the server 30 transmits each of the plurality of pieces of order information (in this example, order information_C, order information_D, and order information_E) to the smartphone 40 in association with one corresponding pump ID (pump ID_C, pump ID_D, and pump ID_E).

[0116] 13, in sequence SQ9, smartphone 40 accepts a transfer operation of order information_C received from server 30. Note that the transfer operation in this case is the selection of image object 481 and holding smartphone 40 over liquid administration pump 50C. When smartphone 40 is held over liquid administration pump 50C, communication between smartphone 40 and liquid administration pump 50C is established in sequence SQ10. In sequence SQ11, smartphone 40 transmits order information_C to liquid administration pump 50C.

[0117] In sequence SQ12, smartphone 40 accepts a transfer operation of order information_D received from server 30. Note that the transfer operation in this case is the selection of image object 481 and holding smartphone 40 over liquid administration pump 50D. When smartphone 40 is held over liquid administration pump 50D, communication between smartphone 40 and liquid administration pump 50D is established in sequence SQ13. In sequence SQ14, smartphone 40 transmits order information_D to liquid administration pump 50D.

[0118] In sequence SQ15, smartphone 40 accepts a transfer operation of order information_E received from server 30. Note that the transfer operation in this case is the selection of image object 481 and holding smartphone 40 over liquid administration pump 50E. When smartphone 40 is held over liquid administration pump 50E, communication between smartphone 40 and liquid administration pump 50E is established in sequence SQ16. In sequence SQ17, smartphone 40 transmits order information_E to liquid administration pump 50E.

[0119] As shown in FIG. 14, in sequence SQ18, liquid administration pump 50C accepts the staff member pressing start button 515. In sequence SQ19, liquid administration pump 50C starts operation based on received order information_C. In sequence SQ20, liquid administration pump 50D accepts the staff member pressing start button 515. In sequence SQ21, liquid administration pump 50D starts operation based on received order information_D. In sequence SQ22, liquid administration pump 50E accepts the staff member pressing start button 515. In sequence SQ23, liquid administration pump 50E starts operation based on received order information_E. The order of sequences SQ18, SQ20, and SQ22 is not limited to the above.

[0120] As shown in sequences SQ24 and SQ27, the liquid administration pump 50C transmits operation status information to the server 30 at a predetermined period Tc using wireless communication based on the WiFi standard. In this case, the server 30 sequentially stores the operation status information from the liquid administration pump 50C in the storage unit 32 in association with, for example, the pump ID_C.

[0121] Similarly, as shown in sequence SQ25, the liquid dosing pump 50D transmits operation status information to the server 30 at a predetermined cycle Tc using WiFi-standard wireless communication. In this case, the server 30 sequentially stores the operation status information from the liquid dosing pump 50D in the storage unit 32, for example, in association with the pump ID_D. As shown in sequence SQ26, the liquid dosing pump 50E transmits operation status information to the server 30 at a predetermined cycle Tc using WiFi-standard wireless communication. In this case, the server 30 sequentially stores the operation status information from the liquid dosing pump 50E in the storage unit 32, for example, in association with the pump ID_E.

[0122] (G. Variation) (1) In the above, the case where multiple chemical liquid dispensing pumps 50 are housed in a rack 90 has been described as an example, but the present invention is not limited to this. Multiple chemical liquid dispensing pumps 50 do not have to be housed in a rack 90.

[0123] (2) Although the configuration in which the multiple drug solution administration pumps 50 are arranged in a vertical row has been described as an example, the configuration is not limited to this. The multiple drug solution administration pumps 50 may be arranged horizontally or vertically and horizontally.

[0124] (3) In the above, an example has been described in which the barcode 711 on the wristband 710 is scanned, and then the barcode 511 on the device label 510 and the barcode 811 on the medicine labels 810C to 810E are scanned. That is, an example has been described in which the smartphone 40 first acquires the patient ID, and then acquires the order ID and the pump ID. However, this is not limited to this. The smartphone 40 may acquire the patient ID after acquiring the order ID and the pump ID.

[0125] (4) 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. A staff member may manually or by voice input the staff ID and the patient ID into the smartphone 40, so that the smartphone 40 acquires the staff ID and the patient ID.

[0126] If the staff member remembers his / her staff ID, he / she can input the staff ID into the smartphone 40 based on the memory. Usually, the staff member has a staff ID attached to the name tag that he / she wears. Therefore, if the staff member forgets his / her staff ID, he / she can check his / her name tag and input his / her staff ID into the smartphone 40.

[0127] As shown in Fig. 6, the patient ID is written on the wristband 710 in numbers or the like (in the example of Fig. 6, "00000045") so that the staff can read it. 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.

[0128] 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 scope and meaning equivalent to the scope of the claims. [Explanation of symbols]

[0129] 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, 50, 50A, 50B, 50C, 50D, 50E, E Drug administration pump, 53 Operation button, 55, 431 Display, 56 Card, 60 Monitoring terminal, 311 Extraction unit, 432 Touch panel, 441 Camera, 442 Data processing unit, 461 Transmission unit, 462 Receiver, 471, 472, 473, 474, 475, 476, 477, 478, 480, 481, 482, 483, 484, 485, 486, 491, 4901, 4902, 4903, 4904, 4905, 4913, 4914 Image object, 500 Drug administration pump group, 510, 510A, 510B, 510C, 510D, 510E Equipment label, 511, 711, 811 Barcode, 515 Start button, 590 Felica mark, 591, 592, 593 Syringe, 710 Wristband, 810C, 810D, 810E Drug label, 900 Rack, 901 Hand, 951 Wrist, 4781, 4801 Reconfigure button, 4821 Cancel button, G41, G42, G43, G44, G45, G46, G47, G48, G49, G50, G51, G55 screens.

Claims

1. 1. A drug solution administration system, comprising: A server device; A terminal device; A plurality of drug solution administration pumps, each of which is set with a container containing a drug, Each of the containers is marked with order identification information that identifies order information including a prescription order for the drug; Each of the liquid administration pumps is provided with pump identification information for identifying the liquid administration pump at a position where the pump identification information can be seen simultaneously with the order identification information of the drug contained in the container set therein; The terminal device By scanning each of the pump identification information and each of the order identification information at once, each of the pump identification information and each of the order identification information are acquired at once; associate, for each of the liquid administration pumps, the pump identification information of the liquid administration pump with the order identification information of the drug contained in the container set in the liquid administration pump based on a positional relationship between each of the acquired pump identification information and each of the acquired order identification information; a medical solution administration system that transmits each of the pump identification information and each of the order identification information to the server device in a state where the association is established.

2. the server device stores a plurality of pieces of order information; Each of the order information includes the order identification information, The server device includes: Extracting a plurality of pieces of order information including each of the received order identification information from the plurality of pieces of order information; transmits, to the terminal device, each of the extracted order information items in a state in which the order information items are associated with the pump identification information associated with the order identification information included in the order information items based on the association between the pump identification information and the order identification information; 2. The medical solution administration system according to claim 1, wherein when the terminal device receives a plurality of pieces of order information each associated with the pump identification information, the terminal device transmits to each of the medical solution administration pumps the order information associated with the pump identification information of the medical solution administration pump.

3. The plurality of drug solution administration pumps include a first drug solution administration pump and a second drug solution administration pump, The terminal device By the scan, first pump identification information which is the pump identification information of the first liquid medicine administration pump, second pump identification information which is the pump identification information of the second liquid medicine administration pump, first order identification information which is the order identification information of a drug set in the first liquid medicine administration pump, and second order identification information which is the order identification information of a drug set in the second liquid medicine administration pump are acquired all at once; Associating the first pump identification information with the first order identification information and associating the second pump identification information with the second order identification information; transmitting the first and second pump identification information and the first and second order identification information to the server device in a state in which the association is established; The server device includes: extracting, from the plurality of pieces of order information, first order information including the first order identification information and second order information including the second order identification information; Transmitting the first order information to the terminal device in a state in which the first order information is associated with the first pump identification information, and transmitting the second order information to the terminal device in a state in which the second order information is associated with the second pump identification information; 3. The medical solution administration system according to claim 2, wherein the terminal device transmits the first order information to the first medical solution administration pump based on an association between the first order information and the first pump identification information, and transmits the second order information to the second medical solution administration pump based on an association between the second order information and the second pump identification information.

4. The chemical liquid administration system according to claim 1 , wherein the plurality of chemical liquid administration pumps are accommodated in a rack in a vertical row.

5. A terminal device included in the drug solution administration system according to claim 1.

6. a step of simultaneously acquiring each of the pump identification information and each of the order identification information by simultaneously scanning order identification information marked on a container containing a drug set in each of a plurality of drug solution administration pumps and pump identification information marked in a position on each of the plurality of drug solution administration pumps that can be viewed simultaneously with the order identification information; a step of associating, for each of the liquid administration pumps, the pump identification information of the liquid administration pump with the order identification information of the drug contained in the container set in the liquid administration pump based on a positional relationship between each of the acquired pump identification information and each of the acquired order identification information; an information processing method comprising a step of transmitting each of the pump identification information and each of the order identification information to a server device in a state in which the association is made.

Images