Computer network and information processing method

Abstract

To provide a computer network that dispenses with operation for address allocation to a chemical solution dosing pump by a hospital staff.SOLUTION: A server device stores a plurality of order information pieces. The server device stores the pump identification information of a chemical solution dosing pump and the address allocated to the chemical solution dosing pump in association for each chemical solution dosing pump. A terminal device acquires order identification information on the basis of data input operation and transmits order identification information to the server device so as to acquire order information corresponding to order identification information from the server device. The terminal device transfers the order information to a designated chemical solution dosing pump. The terminal device acquires pump identification information of the designated chemical solution dosing pump and transmits the pump identification information to the server device. The server device identifies the address correlated to the received pump identification information, and establishes wireless communication to the identified and address-allocated chemical solution dosing pump.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present disclosure relates to computer networks and information processing methods. [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 operating rooms and the like, multiple liquid medicine administration pumps are used simultaneously. In such an environment, in the case of a system configuration in which an information processing device (terminal device) can transmit order information including flow rate, planned amount, etc. to each of multiple liquid medicine administration pumps, it is necessary to transmit order information of the drug to the liquid medicine administration pump in which the drug (liquid medicine) such as an infusion pack is placed. In such a configuration, it is desirable for the server device to wirelessly obtain and store data indicating the operating status of each liquid medicine administration pump based on the order information in order to record the implementation.

[0005] In order to execute wireless communication between the liquid administration pump that has acquired the order information and the server device, the hospital staff must assign an address on a computer network, such as an IP (Internet Protocol) address, to the liquid administration pump in advance. This assignment of addresses for communication is extremely time-consuming, as it must be done correctly for each liquid administration pump.

[0006] The present disclosure provides a computer network and an information processing method that eliminate the need for hospital staff to assign addresses to drug solution administration pumps. [Means for solving the problem]

[0007] According to an aspect of the present disclosure, a computer network includes a server device, a plurality of liquid medicine administration pumps, and a terminal device capable of wireless communication between the server device and each of the plurality of liquid medicine administration pumps. The server device stores a plurality of pieces of order information, each of which includes a prescription order for an injection for a patient, and data in which pump identification information of the liquid medicine administration pump and an address on a computer network assigned to the liquid medicine administration pump are associated with each liquid medicine administration pump. Each piece of order information further includes order identification information for identifying the order information. The terminal device acquires the order identification information based on a data input operation, and transmits the order identification information to the server device, thereby acquiring the order information corresponding to the order identification information from the server device. The terminal device transfers the order information to a designated liquid medicine administration pump among the plurality of liquid medicine administration pumps. The terminal device further acquires pump identification information of the designated liquid medicine administration pump, and transmits the acquired pump identification information to the server device. The computer network includes a server device that identifies an address associated with the pump identification information received from the terminal device based on the data, and establishes wireless communication with a liquid medicine administration pump to which the identified address is assigned.

[0008] According to another aspect of the present disclosure, an information processing method is executed in a computer network including a server device, a plurality of drug solution administration pumps, and a terminal device capable of wireless communication between the server device and each of the plurality of drug solution administration pumps. The information processing method includes a step of the server device acquiring a plurality of order information each including a prescription order for an injection for a patient. Each order information further includes order identification information for identifying the order information. The information processing method further includes a step of the server device accepting an operation to associate an address on a computer network with pump identification information of each drug solution administration pump; a step of the terminal device acquiring order identification information based on a data input operation and transmitting the order identification information to the server device, thereby acquiring order information corresponding to the order identification information from the server device; a step of the terminal device transferring the order information to a specified drug solution administration pump among the multiple drug solution administration pumps; a step of the terminal device further acquiring pump identification information of the specified drug solution administration pump and transmitting the acquired pump identification information to the server device; and a step of the server device identifying an address associated with the pump identification information received from the terminal device and establishing wireless communication with the drug solution administration pump to which the identified address is assigned. Effect of the Invention

[0009] According to the present disclosure, there is no need for hospital staff to assign addresses to drug solution administration pumps. [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 reading a barcode of an infusion pump using a smartphone. [Figure 8] FIG. 13 illustrates reading of a medicine label using a smartphone. [Figure 9] 13 is a diagram showing the state of the smartphone and the infusion pump immediately after the transfer of order information is completed. FIG. [Figure 10] FIG. 2 is a block diagram of each device that constitutes the drug solution administration system. [Figure 11] FIG. 11 is a sequence diagram for explaining the flow of a first part of data processing in the drug solution administration system. [Figure 12] 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 13] FIG. 11 is a sequence diagram for explaining the flow of a third part of the data processing in the drug solution administration system. [Figure 14] FIG. 2 is a diagram showing a modified example of the drug solution administration pump group shown in FIG. 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. The medical system 1 is a computer network. The medicinal liquid administration system 5 is a computer network included in the medical system 1.

[0013] 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, any one of the infusion pumps 50A, 50B, and 50C is also referred to as an "infusion pump 50" for convenience of explanation. 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.

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

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

[0016] 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 a type of wireless LAN communication method. Wi-Fi is an abbreviation for "Wireless Fidelity."

[0017] The smartphone 40 communicates with the infusion pump 50. The smartphone 40 performs wireless communication 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 a Type-F of NFC.

[0018] 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."

[0019] In this example, by bringing the smartphone 40 operating as a reader / writer close to the infusion pump 50 operating as a tag, short-range wireless communication is performed between the smartphone 40 and the infusion pump 50. For example, by bringing the smartphone 40 close to the infusion pump 50A, short-range wireless communication is performed between the smartphone 40 and the infusion pump 50A. The reason why 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.

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

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

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

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

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

[0025] 1, staff master data, patient master data, the latest drug library data, and a plurality of pieces of order information #1, #2, ... #N are stored in the memory unit 32 of the server 30. The memory unit 32 of the server 30 further stores an address table 321 and implementation record data 322.

[0026] Each piece of 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), a set value for the dosage (mL), etc. Furthermore, the order information includes information such as the scheduled date and time of administration, and the date and time of order creation.

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

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

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

[0030] In the address table 321, a pump ID (serial number) for identifying the infusion pump 50 and an address on the computer network (medicinal fluid administration system 5) assigned to the infusion pump 50 are associated with each infusion pump 50. In this example, an IP (Internet Protocol) address is used as the address.

[0031] For example, the pump ID "02105015" shown in the figure is the pump ID of the infusion pump 50B. The pump ID of the infusion pump 50B is associated with the IP address "192.168.0.1." Different IP addresses are also assigned to the pump IDs of the infusion pumps 50A and 50B.

[0032] The IP addresses are assigned in advance by hospital staff. Specifically, the pump ID and the IP address to be assigned to the pump ID are input in advance by the staff into address table 321. Thus, in this example, the IP address is not automatically assigned.

[0033] The implementation record data 322 stores implementation records for each patient. The implementation record includes a patient ID, a pump ID, an order ID, and data indicating the operation status of the infusion pump 50 (hereinafter, also referred to as "operation status information"), which will be described later. The implementation record data 322 is updated whenever the server 30 acquires the operation status information from the infusion pump 50.

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

[0035] 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).

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

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

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

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

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

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

[0042] 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 811 is printed on wristband 810 wrapped around wrist 951 of a subject patient. Staff reads barcode 811 using smartphone 40. Barcode 811 indicates (describes) the patient ID. In this manner, the patient ID is read by smartphone 40.

[0043] As shown as "(i) Photographing barcode on wristband" in Fig. 5, when the smartphone 40 reads the barcode 811, 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).

[0044] 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 pump ID reading process.

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

[0046] Thereafter, the staff sets the medicine (infusion pack) in a predetermined infusion pump 50 among the multiple infusion pumps 50. In this example, as shown in FIG. 5 as "(iii) Setting of 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 predetermined application program on the smartphone 40.

[0047] When the staff member selects with his / her finger the image object 491 shown in state (D) in Fig. 3, 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.

[0048] Fig. 7 is a diagram showing the reading of the barcode of the infusion pump 50B by the smartphone 40. As shown in Fig. 7, the staff member reads the barcode 511 printed on the seal 510 using a scanning screen G51 displayed on the smartphone 40. The barcode 511 includes a pump ID (serial number) for identifying the infusion pump 50B.

[0049] In this example, the seal 510 is attached to the upper part of the front surface of the infusion pump 50B. However, the position of the seal 510 is not limited thereto. The position of the seal 510 is not particularly limited as long as the barcode 511 can be easily scanned by the smartphone 40.

[0050] The smartphone 40 acquires the pump ID of the infusion pump 50 (in this example, the infusion pump 50B) by reading the barcode 511. The smartphone 40 temporarily stores the acquired pump ID. For convenience of explanation, the pump ID is also referred to as "pump ID_BAR" below.

[0051] When the smartphone 40 acquires the pump ID by scanning, 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, an image object 492, and an image object 477. In state (E), the image object 477 is selectable. The image object 477 is an object for transitioning to a selection process (reading process) of an order ID.

[0052] Image object 492 indicates the pump ID obtained by reading barcode 511. Note that by selecting a reset button 4901 in object 492, the pump ID can be reset.

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

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

[0055] 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 wireless LAN after confirmation input by the staff member (selection of an image object such as a send button).

[0056] When the server 30 acquires the order ID from the smartphone 40 after the patient ID, the server 30 executes the following process. The server 30 extracts order information including an order ID that matches the order ID sent from the smartphone 40 from among the multiple order information #1, #2, ..., #3 stored in the storage unit 32 (FIG. 2). That is, the server 30 extracts order information including an order ID that matches the order ID obtained by reading the barcode 821 of the medicine label 820 by the smartphone 40 from among the multiple order information #1, #2, ..., #3. Note that since there are no duplicate order IDs, the server 30 extracts one order information.

[0057] Next, the server 30 determines whether or not 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 or not the patient ID included in the extracted order information matches the patient ID obtained by reading the barcode 811 of the wristband 810 by the smartphone 40.

[0058] On condition that it is determined that the patient IDs match, the server 30 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 by using communication via wireless LAN.

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

[0060] When the smartphone 40 acquires (receives) the order information from the server 30, as shown in state (F) of FIG. 3, the smartphone 40 displays a screen G46 on the touch screen 43. The screen G46 includes an image object 478, an image object 480, and an image object 481.

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

[0062] The image object 481 is an object for accepting the start of order transfer. When the staff member selects the 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.

[0063] The screen G47 includes an image object 478, an image object 480, and an image object 482. The image object 482 includes a guidance display that prompts the staff to move the smartphone 40 closer to the infusion pump 50B. The 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 selects the cancel button 4821, the smartphone 40 switches the screen from the screen G47 to the screen G45, for example.

[0064] When the staff 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 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.

[0065] By establishing the short-range wireless communication, 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. Upon receiving the request signal, the infusion pump 50B transmits the pump ID of the infusion pump 50B to the smartphone 40 with which the short-range wireless communication has been established, as shown as "(ix) pump ID" in Fig. 5. For ease of explanation, hereinafter, the pump ID thus acquired by short-range wireless communication is also referred to as "pump ID_NFC."

[0066] When the smartphone 40 receives the pump ID_NFC from the infusion pump 50B, as shown as "(x) Comparison of pump IDs" in Fig. 5, 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, the infusion pump 50B) that transmitted the pump ID_NFC and the infusion pump 50 (in the case of Fig. 7, the infusion pump 50B) of the pump ID_BAR written in the barcode 511 are the same infusion pump 50.

[0067] 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 transmits order information to the infusion pump 50 with which short-range wireless communication has been established (in this example, infusion pump 50B), as shown as "(xi) Order information" in Figure 5.

[0068] That is, the smartphone 40 transmits the order information to the infusion pump 50 by short-range wireless communication, on condition 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 transmitted. In detail, the smartphone 40 transfers the order information acquired from the server 30 to the infusion pump 50 (in this example, the infusion pump 50B). With this configuration, it becomes possible to transmit the order information of the drug to the infusion pump 50 in which the drug is set.

[0069] 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 an image object 483 and an image object 484.

[0070] 9 is a diagram showing the states of the smartphone 40 and the infusion pump 50 immediately after the transfer of the order information is completed. As shown in FIG. 9, the smartphone 40 displays the above-mentioned screen G48 on the touch screen 43.

[0071] Image object 483 indicates that the transfer of the order information is complete. Image object 483 further includes a notification urging the staff to press a setting completion button represented as image object 484 and to press a start button 591 of the infusion pump 50 after pressing the setting completion button.

[0072] When the staff member presses the setting completion button, as shown as "(xii) Pump ID" in Fig. 5, the smartphone 40 transmits the pump ID_NFC acquired from the infusion pump 50 to the server 30. Furthermore, as shown in state (J) in Fig. 4, the smartphone 40 switches the screen displayed on the touch screen 43 from screen G48 to screen G50.

[0073] In addition, in the state (H) of FIG. 4, since the pump ID_NFC and the pump ID_BAR match, the smartphone 40 may transmit the pump ID_BAR to the server 30 instead of the pump ID_NFC.

[0074] The smartphone 40 may transmit the pump ID together with at least one of the previously acquired order ID and patient ID to the server 30. That is, the smartphone 40 may resend one of the order ID and the patient ID.

[0075] The screen G50 includes an image object 495. In the screen G50, the image object 495 is superimposed on the image objects 480, 483, and 484. The image object 495 notifies the user (staff member) that the pump ID has been transmitted to the server.

[0076] The image objects 495 include an image object 4903. When the staff member selects the image object 4903, in this example, the smartphone 40 switches the screen displayed on the touch screen 43 from the screen G50 to the screen G42 (FIG. 3).

[0077] Next, a process of the server 30 after receiving the pump ID from the smartphone 40 will be described. The server 30 stores the received pump ID in association with the previously received patient ID (state (ii) in FIG. 5) and order ID (state (vi) in FIG. 5). As described above, in the case where the smartphone 40 is configured to transmit the pump ID to the server 30 together with at least one of the order ID and the patient ID, the server 30 can easily associate the pump ID, the order ID, and the patient ID.

[0078] As shown in FIG. 5 as "(xiii) Identification of IP address," the server 30 identifies the IP address assigned to the infusion pump 50 having the pump ID based on the received pump ID. Specifically, the server 30 refers to the address table 321 (FIG. 2) to identify the IP address associated with the received pump ID. For example, when the server 30 receives "02405015" (see FIG. 2) of the infusion pump 50B as the pump ID from the smartphone 40, the server 30 identifies the IP address as "192.168.0.1."

[0079] The server 30 uses the identified IP address to establish wireless communication via Wi-Fi with the infusion pump 50 having the IP address. In the above example, as shown in “(xiv) Establishment of wireless communication” in FIG. 5, the server 30 establishes wireless communication via Wi-Fi with the infusion pump 50B.

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

[0081] When the staff member presses the start button 591 of the infusion pump 50 while the screen G61 is displayed on the display 55 of the infusion pump 50, administration of the medicinal fluid by the infusion pump 50 is started. In this case, the infusion pump 50 periodically transmits operating status information of the infusion pump 50 to the server 30.

[0082] In the above example, wireless communication by Wi-Fi is established between the infusion pump 50B and the server 30. Therefore, the infusion pump 50B periodically transmits operation status information of the infusion pump 50B to the server 30, as shown as "(xv) Operation Status Information" in Fig. 5. The operation status information includes the state of the pump, the operation contents by the staff, etc. in chronological order.

[0083] When the server 30 receives the operation status information, it updates the performance record data 322 (FIG. 2). The server 30 adds the newly received time series data to the data (time series data) stored in the performance record data 322. In this way, the server 30 stores the operation status information in association with the patient ID, order ID, and pump ID that have been associated in advance. When the server 30 receives a request to send the performance record data 322 from an external device, it can send the performance record data 322 to that device.

[0084] The staff can later check the contents of the implementation record data 322 to know what treatment was performed for which patient, which infusion pump 50 was used, and based on what order information. Furthermore, the staff does not need to take notes on the implementation record by hand or the like.

[0085] 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 the short-range wireless communication does not match the pump ID_BAR acquired by reading the barcode 511.

[0086] 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). Furthermore, the smartphone 40 switches the screen displayed on the touch screen 43 from screen G47 to screen G49, as shown in state (I) of FIG.

[0087] The screen G49 includes an image object 494. The image object 494 notifies the user (staff member) of a warning. In the image object 494, the pump ID_BAR is represented as a "destination ID" and the pump ID_NFC is represented as a "destination ID". Since the smartphone 40 displays such a warning on the touch screen 43, the staff member can realize that "the order information is about to be sent to the wrong infusion pump 50". In addition, since at least the "destination ID" is displayed, the staff member can easily determine which infusion pump 50 the order information should be sent to.

[0088] The image object 494 includes an image object 4902 for resetting. When the image object 4902 is selected, the screen displayed on the touch screen 43 is switched from G49 to screen G47. Thereafter, the staff member can transmit the order information to the infusion pump 50 (in this example, the infusion pump 50B) by bringing the smartphone 40 close to the infusion pump 50 in which the above-mentioned drug is set.

[0089] (D. Small summary) (1) As described above, the medicinal solution administration system 5, which is a computer network, includes a server 30, a plurality of infusion pumps 50 (50A, 50B, 50C), and a smartphone 40 capable of wireless communication between the server 30 and each of the plurality of infusion pumps 50, as shown in FIG.

[0090] The server 30 stores a plurality of order information pieces, each of which includes a prescription order for an injection for a patient, as shown in Fig. 2. The server 30 further stores an address table 321, as shown in Fig. 2, in which the pump ID of the infusion pump 50 and an IP address on the computer network (medicinal solution administration system 5) assigned to the infusion pump 50 are associated with each infusion pump 50. Each order information piece further includes an order ID for identifying the order information, as shown in Fig. 2.

[0091] The smartphone 40 acquires the order ID based on the data input operation, and transmits the order ID to the server 30 to acquire order information corresponding to the order ID from the server 30 (processes (v) and (vii) in FIG. 5). Note that in this example, the operation of reading the barcode 821 of the medicine label 820 by the smartphone 40 shown in FIG. 8 corresponds to an example of a "data input operation."

[0092] The smartphone 40 transfers the order information to a specified infusion pump 50 among the multiple infusion pumps 50 (see process (xi) in FIG. 5). The smartphone 40 further acquires a pump ID of the specified infusion pump 50, and transmits the acquired pump ID to the server 30 (see process (iv) and / or process (ix) and process (xii) in FIG. 5).

[0093] The server 30 identifies the IP address associated with the pump ID received from the smartphone 40 based on the address table 321 (Figure 2), and establishes wireless communication with the infusion pump 50 (infusion pump 50B in the example of Figure 5) to which the identified IP address is assigned (processing (xiii) and (xiv) in Figure 5).

[0094] According to such a configuration, the server 30 automatically identifies an IP address associated with a pump ID in the address table 321 based on the pump ID received from the smartphone 40. Furthermore, based on the identified IP address, the server 30 establishes wireless communication with the infusion pump 50 to which the IP address is assigned (i.e., the infusion pump having the pump ID).

[0095] Therefore, the staff does not need to perform the operation (task) of assigning an IP address to the infusion pump 50 to which the order information is to be sent. Furthermore, the staff does not need to perform the operation of performing wireless communication (Wi-Fi standard communication in this example) using the IP address between the server 30 and the infusion pump 50. In this way, the medicinal solution administration system 5 can save the staff time and effort.

[0096] (2) Each order information further includes a patient ID for identifying a patient, as shown in Fig. 2. The smartphone 40 acquires the patient ID in addition to the order ID, and acquires the order information from the server 30 based on the order ID and the patient ID transmitted to the server 30 (see processes (i), (ii), and (v) to (vii) in Fig. 5).

[0097] According to this configuration, the server 30 can extract order information based on not only the order ID but also the patient ID from among a plurality of pieces of order information. Therefore, the smartphone 40 can obtain order information according to the order ID and the patient ID from the server 30. Therefore, according to the medicinal solution administration system 5, it is possible to prevent the smartphone 40 from transmitting incorrect order information for a patient to the infusion pump 50 used by the patient.

[0098] (3) The server 30 stores the pump ID, the order ID, and the patient ID received from the smartphone 40 in association with one another. With this configuration, it is possible to manage which pump is being used, which order information is being used, and which patient is being administered with the medicinal liquid.

[0099] (4) When the infusion pump 50, which has established wireless communication with the server 30, accepts a predetermined operation of pressing the start button 591, the infusion pump 50 starts operation based on the order information transferred from the smartphone 40. After starting operation, the infusion pump 50 periodically transmits operation status information indicating the operation status to the server 30 via the established wireless communication. The server 30 stores the operation status information in association with the patient ID.

[0100] According to this configuration, the server 30 can periodically obtain operation status information from the infusion pump 50 with which wireless communication has been established using the IP address. That is, the server 30 can obtain the implementation record data 322 (more specifically, updated data) from the infusion pump 50.

[0101] (5) In response to an operation of transferring the acquired order information to a specified infusion pump 50 among the multiple infusion pumps 50, the smartphone 40 acquires the pump ID of the specified infusion pump 50 from the specified infusion pump 50 and transmits the acquired pump ID to the server 30 (see the series of processes (viii) to (xii) in Figure 5).

[0102] According to this configuration, the smartphone 40 can obtain the pump ID from the infusion pump 50 to which the order information is to be transferred. Therefore, the server 30 can establish wireless communication with the infusion pump 50 to which the order information is to be transmitted. In other words, the server 30 can prevent wireless communication from being established with an infusion pump 50 other than the infusion pump 50 to which the order information is to be transmitted.

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

[0104] 10, 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).

[0105] 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, the order ID, and the pump ID_BAR to the control unit 41.

[0106] The Wi-Fi communication unit 45 is a communication interface that performs wireless communication via Wi-Fi. As shown as “(ii) Patient ID” and “(vi) Order ID” in FIG. 5, the smartphone 40 transmits a patient ID and an order ID to the server 30 using the Wi-Fi communication unit 45.

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

[0108] The server 30 includes 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 control unit 31 has an address identification unit 311. The memory unit 32 includes an operating system and various programs. These are executed by the control unit 31 (more specifically, a processor). The memory unit 32 further stores an address table 321 (FIG. 2). The wired communication unit 33 is a communication interface for communicating with the servers 10, 20 and the monitoring terminal 60.

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

[0110] The server 30 transmits the extracted order information to the smartphone 40 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 the order information to the smartphone 40 using the Wi-Fi communication unit 34, as shown as “(vii) Order information” in FIG.

[0111] The infusion 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 infusion 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).

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

[0113] When the pump ID_NFC matches the pump ID_BAR, the smartphone 40 transmits the pump ID_NFC to the server 30 using the Wi-Fi communication unit 45. The server 30 receives the pump ID_NFC via the Wi-Fi communication unit .

[0114] The address specification unit 311 of the server 30 specifies the IP address associated with the received pump ID_NFC by referring to the address table 321. Thereafter, the control unit 31 of the server 30 uses the specified IP address to establish wireless communication according to the Wi-Fi standard with the infusion pump 50 that is the sender of the pump ID_NFC.

[0115] The infusion pump 50, which has established wireless communication with the server 30, communicates with the server 30 using the Wi-Fi communication unit 54. The infusion pump 50 transmits operation status information to the server 30 using the Wi-Fi communication unit 54 ("(xv) Operation Status Information" in FIG. 5). Thereafter, the server 30 receives the operation status information periodically transmitted from the infusion pump 50. Specifically, the server 30 receives the operation status information via the Wi-Fi communication unit 34.

[0116] 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 infusion pump 50 using the monitoring terminal 60.

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

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

[0119] In sequence SQ3, the staff sets the medicine (infusion pack) in the infusion pump 50 (in this example, the infusion pump 50B). In sequence SQ4, the smartphone 40 reads the barcode 511 printed on the sticker 510 of the infusion pump 50B with the scanner 44.

[0120] 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 reading result of the barcode 821, to the server 30.

[0121] In sequence SQ7, the server 30 extracts, from among a plurality of pre-stored pieces of order information, order information that includes the same order ID as the order ID received from the smartphone 40. In sequence SQ8, the server 30 extracts the patient ID included 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.

[0122] 12, in sequence SQ10, the server 30 transmits the order information extracted in sequence SQ7 to the smartphone 40. In sequence SQ11, the smartphone 40 accepts a transfer operation of the order information received from the server 30. The transfer operation refers to the selection of the image object 481 and the holding of the smartphone 40 over the infusion pump 50.

[0123] 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, requesting transmission of a pump ID via short-range wireless communication. In sequence SQ14, the infusion pump 50B transmits a pump ID_NFC to the smartphone 40 as a response signal.

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

[0125] In sequence SQ17, the smartphone 40 transmits the pump ID (in this example, pump ID_NFC) to the server 30. In sequence SQ18, the server 30 refers to the address table 321 (FIG. 2) and identifies an IP address associated with the pump ID. In sequence SQ19, the server 30 establishes wireless communication according to the Wi-Fi standard with the infusion pump 50 (in this example, infusion pump 50B) to which the identified IP address is assigned.

[0126] In sequence SQ20, the infusion pump 50B accepts pressing of the start button 591. In sequence SQ21, the infusion pump 50B starts operation based on the received order information. Note that the processing of sequences SQ20 and SQ21 may be performed after the processing of sequence SQ16, and is not limited to being performed after the processing of sequence SQ19, for example.

[0127] As shown in sequences SQ22, SQ24, and SQ26, the infusion pump 50B transmits operation status information to the server 30 at a predetermined cycle Tc using WiFi-standard wireless communication. Every time the server 30 receives operation status information, it updates the contents of the performance record data 322 as shown in sequences SQ23 and SQ25. The transmission of operation status information and the update of the performance record data 322 are continued until the administration of medication by the infusion pump 50B is completed.

[0128] (G. Variation) (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 one example, a plurality of infusion pumps 55A, 55B and a plurality of syringe pumps 56A, 56B, 56C.

[0129] The infusion pumps 55A, 55B and the syringe pumps 56A, 56B, 56C are housed in a rack. The infusion pumps 55A, 55B and the syringe pumps 56A, 56B, 56C are arranged vertically in a line in the rack. When such liquid administration pumps are arranged close to each other, it is preferable to transmit order information after determining whether the pump IDs match each other.

[0130] (2) In the above, the smartphone 40 obtained the pump ID_NFC from the infusion pump 50 and determined whether the pump ID_NFC matched the pump ID_BAR obtained by reading the barcode 511 (FIG. 7). Furthermore, the smartphone 40 transmitted the order information to the infusion pump 50 that transmitted the pump ID_NFC, on the condition that the pump ID_NFC matched the pump ID_BAR.

[0131] However, the medicinal liquid administration system 5 is not limited to such a configuration. Acquisition of the pump ID_NFC is not necessarily required. The smartphone 40 may simply be configured to transmit the pump ID_BAR to the server 30. The server 30 may refer to the address table 321 and identify the IP address based on the pump ID_BAR.

[0132] In this configuration, the smartphone 40 does not acquire the pump ID_NFC, and therefore only needs to transmit the order information to the infusion pump 50 on the condition that short-range wireless communication with the infusion pump 50 is established.

[0133] (3) In the above, as shown in FIG. 8, the smartphone 40 obtains the order ID by reading the barcode 821 on the medicine label 820. However, this is not limited to this. The order ID may be obtained by reading an 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 may use the smartphone 40 to read a two-dimensional code (e.g., a QR code) on which the order ID is expressed (written).

[0134] (4) 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 medicine label 820 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.

[0135] (5) The order of the process (iii), the process (iv), and the series of processes (v) to (vii) shown in FIG. 5 is not limited to the order described above.

[0136] (6) In the above, the smartphone 40 transmits a request signal to the infusion pump 50, but the present invention is not limited to this. The medical solution 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 solution 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.

[0137] (7) 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 may manually or by voice input these IDs into the smartphone 40, so that the smartphone 40 acquires these IDs.

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

[0139] As shown in Fig. 6, the patient ID is written on the wristband 810 in numbers or the like ("00000045" in the example of Fig. 6) 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.

[0140] 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 the staff can read it. The staff may input the numbers or the like into the smartphone 40. By such an operation, the smartphone 40 can obtain the pump ID_BAR.

[0141] As shown in FIG. 8, the order ID is written on the medicine label 820 in numbers or the like (in the example of FIG. 8, "3000055040671010100") so that the staff can read it. The staff may input the numbers or the like into the smartphone 40. By such an operation, the smartphone 40 can obtain the order ID. Inputting the numbers or the like corresponds to another example of a "data input operation."

[0142] As with the drug label 820, the order ID is written on the injection prescription in numbers or the like (not shown) so that the staff can read it. Therefore, the staff may input the numbers or the like into the smartphone 40. By such an operation, the smartphone 40 can also obtain the order ID.

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

[0144] 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, 55A, 55B Infusion pump, 53 Operation button, 55, 431 Display, 56 Card, 56A, 56B, 56C Syringe pump, 60 Monitoring terminal, 311 Address identification unit, 321 Address table, 322 Implementation record data, 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,491,492,494,4902 Image objects, 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, G41,G42,G43,G44,G45,G46,G47,G48,G49,G50,G51,G61 Screen.

Claims

1. 1. A computer network comprising: A server device; A plurality of drug administration pumps; a terminal device capable of wireless communication between the server device and each of the plurality of drug administration pumps, The server device includes: a plurality of order information each including a prescription order for an injection for a patient; The pump identification information of the liquid administration pump and the address on the computer network assigned to the liquid administration pump are associated with each of the liquid administration pumps, and data is stored; Each of the order information further includes order identification information for identifying the order information; The terminal device acquiring the order identification information based on a data input operation, and transmitting the order identification information to the server device, thereby acquiring the order information corresponding to the order identification information from the server device; Transferring the order information to a designated one of the plurality of drug administration pumps; Further acquiring pump identification information of the specified liquid administration pump, and transmitting the acquired pump identification information to the server device; A computer network in which the server device identifies the address associated with the pump identification information received from the terminal device based on the data, and establishes wireless communication with the drug solution administration pump to which the identified address is assigned.

2. Each of the order information further includes patient identification information that identifies the patient; 2. The computer network of claim 1, wherein the terminal device further acquires the patient identification information in addition to the order identification information, and acquires the order information from the server device based on transmitting the order identification information and the patient identification information to the server device.

3. 3. The computer network according to claim 2, wherein the server device stores the pump identification information, the order identification information, and the patient identification information received from the terminal device in association with each other.

4. The drug solution administration pump that has established wireless communication with the server device, When a predetermined operation is received, an operation is started based on the order information transferred from the terminal device, After the operation is started, periodically transmitting operation status information indicating a status of the operation to the server device via the established wireless communication; The computer network of claim 3 , wherein the server device stores the operating status information in association with the patient identification information.

5. The terminal device is capable of short-range wireless communication with each of the plurality of drug solution administration pumps, The server device is capable of wireless communication according to the Wi-Fi (Wireless Fidelity) standard, The address is an Internet Protocol (IP) address, the terminal device transmits the order information to the liquid administration pump via the short-range wireless communication, and acquires the pump identification information from the liquid administration pump via the short-range wireless communication; The computer network according to claim 4 , wherein the server device receives the operation status information from the liquid administration pump to which the specified IP address is assigned via wireless communication conforming to the Wi-Fi standard.

6. 2. The computer network of claim 1, wherein the data entry operation is an operation of reading a first code printed on a medication label.

7. 7. The computer network according to claim 6, wherein the terminal device acquires the pump identification information of the specified liquid administration pump from the specified liquid administration pump in response to an operation of transferring the order information to the specified liquid administration pump.

8. 7. The computer network according to claim 6, wherein the terminal device acquires the pump identification information by reading a second code printed on a sticker attached to the liquid administration pump.

9. 1. An information processing method in a computer network including a server device, a plurality of drug solution administration pumps, and a terminal device capable of wireless communication between the server device and each of the plurality of drug solution administration pumps, comprising: The method includes a step of: the server device acquiring a plurality of pieces of order information each including a prescription order for an injection for a patient, each of the pieces of order information further including order identification information for identifying the order information; The server device receives an operation for associating an address on the computer network with pump identification information of each of the liquid administration pumps; the terminal device acquiring the order identification information based on a data input operation, and transmitting the order identification information to the server device, thereby acquiring the order information corresponding to the order identification information from the server device; the terminal device transferring the order information to a designated one of the plurality of drug injection pumps; The terminal device further acquires pump identification information of the specified drug solution administration pump, and transmits the acquired pump identification information to the server device; The information processing method further includes a step in which the server device identifies the address associated with the pump identification information received from the terminal device, and establishes wireless communication with the drug solution administration pump to which the identified address is assigned.

Images