Liquid medicine administration system and information processing method

Abstract

To provide a liquid medicine administration system capable of preventing inappropriate order information from being set in a liquid medicine administration pump due to an error of a medical worker.SOLUTION: A liquid medicine administration system includes a server device, a terminal device, and a liquid medicine administration pump. The liquid medicine administration pump has a memory for storing order information including an injection prescription order to a patient. The terminal device acquires the order information from the server device, and transfers the order information to the liquid medicine administration pump. The liquid medicine administration pump overwrites second order information with first order information on condition that prescribed first operation is received if the second order information as order information has been already stored when the first order information as order information transmitted from the terminal device is received. The liquid medicine administration pump operates on the basis of the first order information on condition that prescribed second operation is received after the first operation.SELECTED DRAWING: Figure 10

Description

[Technical field]

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

[0002] Conventionally, as shown in JP 2006-51244 A (Patent Document 1), a system is known in which a drug solution is injected into a patient using a drug solution administration pump such as an infusion pump. In Patent Document 1, a nurse visits the home of a patient at home and reads the IC tag of the infusion bag using a barcode reader of the infusion pump while the infusion bag is attached to the infusion pump. Furthermore, the nurse uses the barcode reader to read information on the IC tag attached to the wristband worn by the patient at home and the IC tag attached to the nurse. Note that drug recognition data such as the upper and lower limits of the flow rate during continuous infusion, the upper and lower limits of the flow rate during one-shot administration, and both or either of the time and flow rate are stored in an unrewritable manner in the IC tag of the infusion bag.

[0003] The infusion pump displays the information read by the barcode reader on the display unit of the infusion pump. Furthermore, the infusion pump transmits the information to a computer or mobile terminal used by the doctor in charge (primary physician) via an information and communication network. The doctor checks the content of the information sent from the infusion pump on the computer or mobile terminal. The doctor checks whether the set infusion amount is appropriate, whether there is an error in the medication, and whether the patient at home is correct. If there are no problems, the doctor transmits a message to that effect to the nurse's mobile terminal and inputs an infusion start command to the infusion pump from the computer or mobile terminal. Upon receiving the infusion start command, the infusion pump starts the infusion based on the input conditions that have been set. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2006-51244 A Summary of the Invention [Problem to be solved by the invention]

[0005] In Patent Document 1, the infusion pump's barcode reader is used to read the IC tag of the infusion bag attached to the infusion pump. However, if the infusion pump or other liquid medicine administration pump does not have a barcode as described above, for example, a terminal device that externally acquires order information such as that stored in the IC tag of the infusion bag in Patent Document 1 may notify the liquid medicine administration pump of the order information by wireless communication or the like. In such a configuration, the liquid medicine administration pump is required to acquire and store appropriate order information and operate based on the order information.

[0006] The present disclosure provides a medical fluid administration system and an information processing method that can prevent inappropriate order information from being set in a medical fluid administration pump due to an error by a medical professional. [Means for solving the problem]

[0007] According to an aspect of the present disclosure, a medicinal liquid administration system includes a server device, a terminal device that communicates with the server device, and a medicinal liquid administration pump that communicates with the terminal device. The medicinal liquid administration pump has a memory for storing order information including a prescription order for an injection for a patient. The terminal device acquires the order information from the server device and transfers the order information to the medicinal liquid administration pump. When the medicinal liquid administration pump receives first order information as the order information transmitted from the terminal device and second order information as the order information is already stored in the memory, the medicinal liquid administration pump overwrites the second order information with the first order information on condition that a predetermined first operation is received. The medicinal liquid administration pump operates based on the first order information on condition that a predetermined second operation is received after the first operation.

[0008] According to another aspect of the present disclosure, an information processing method includes a step of a terminal device obtaining order information including a prescription order for an injection for a patient from a server device, a step of the terminal device transferring the order information to a medicinal liquid administration pump, a step of the medicinal liquid administration pump overwriting the second order information with the first order information when second order information is already stored in a memory for storing order information upon receiving first order information as the order information transmitted from the terminal device, on condition that a predetermined first operation is received, and a step of operating based on the first order information on condition that a predetermined second operation is received after the first operation. Effect of the Invention

[0009] According to the above disclosure, it is possible to prevent inappropriate order information from being set in a liquid medicine administration pump due to a mistake by a medical professional. [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 screen transitions on a smartphone. [Figure 4] FIG. 13 is a diagram showing reading of a wristband by a smartphone. [Diagram 5] FIG. 13 illustrates reading of a medicine label using a smartphone. [Figure 6] 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 7] 13 is a diagram showing the state of an infusion pump when the infusion pump receives new order information in a case where order information is stored in the infusion pump; FIG. [Figure 8] FIG. 2 is a block diagram of each device that constitutes the drug solution administration system. [Figure 9]10 is a sequence diagram for explaining the flow of data processing in the drug solution administration system. FIG. [Figure 10] FIG. 11 is a flow chart for explaining the process flow of the infusion pump. 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] 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, and an infusion pump 50 as an example of a medicinal liquid administration pump.

[0013] The terminal device is not limited to the smartphone 40, but may be a portable device (mobile terminal device) such as a tablet terminal. The liquid administration pump is not limited to the infusion pump 50, but may be another pump such as a syringe pump. In this example, the monitoring terminal 60 is a PC (Personal Computer).

[0014] The smartphone 40 can also function as a terminal for monitoring the condition. Although only one infusion pump 50 is shown in Fig. 1, the liquid administration system 5 may include a plurality of liquid administration pumps.

[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 the infusion pump 50. Typically, the server 30 can establish communication between the smartphone 40 and the infusion pump 50 via a wireless local area network (LAN).

[0017] The smartphone 40 communicates with the infusion pump 50. The smartphone 40 communicates wirelessly with the infusion pump. The smartphone 40 communicates with the infusion pump 50 via near field communication (NFC). In this example, the smartphone 40 communicates with the infusion pump 50 via 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. The reason why the smartphone 40, rather than the infusion pump 50, has a built-in reader / writer is because it is assumed that the smartphone 40 will also perform short-range wireless communication with a plurality of other pumps (not shown) in the same manner as with 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] 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, 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 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 of the liquid flow rate (mL / h), a set value of the dosage (mL), etc. Furthermore, the order information includes information such as the scheduled date and time of administration, the date and time of order creation, etc.

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

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

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

[0029] Next, data transmission and reception within the drug solution administration system 5 shown in Fig. 1 will be described with reference to Fig. 1 and Fig. 3 to Fig. 7. Fig. 3 is a diagram showing the transition of screens on the smartphone 40.

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

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

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

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

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

[0035] 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 G46 described below are screens for transferring order information. Screen G43 includes image objects 476 and 477. In state (C), of image objects 476 and 477, only image object 476 is selectable. Image object 476 is an object for transitioning to a selection process (reading process) of a patient ID. Image object 477 is an object for transitioning to a selection process (reading process) of an order ID.

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

[0037] Fig. 4 is a diagram showing reading of a wristband by smartphone 40. As shown in Fig. 4, 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.

[0038] When the smartphone 40 reads the barcode 811, it transmits the patient ID to the server 30. Typically, the smartphone 40 transmits the patient ID to the server 30 via wireless LAN after confirmation input by a staff member (selection of an image object such as a send button). That is, the smartphone 40 transmits "(i) Patient ID" shown in FIG. 1 to the server 30.

[0039] 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 and an image object 477.

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

[0041] When the staff member selects the image object 477 with his / her finger, the smartphone 40 resumes reading the barcode using the camera. The staff member captures an image of the barcode printed on the drug label of the target patient with the camera of the smartphone 40. The order ID is written in the barcode.

[0042] Fig. 5 is a diagram showing reading of a medicine label by smartphone 40. As shown in Fig. 5, 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.

[0043] When the smartphone 40 reads the barcode 821, it transmits the order ID to the server 30. 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). That is, the smartphone 40 transmits "(ii) Order ID" shown in FIG. 1 to the server 30.

[0044] When the server 30 acquires the patient ID and the order ID from the smartphone 40, 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.

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

[0046] The server 30 transmits the extracted order information to the smartphone 40 on the condition that it is determined that the patient IDs match. That is, the server 30 transmits "(iii) order information" shown in Fig. 1 to the smartphone 40. Specifically, the server 30 transmits the extracted order information to the smartphone 40 by using communication via wireless LAN.

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

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

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

[0050] 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 G45 to screen G46 as shown in state (F) of FIG. 3, and prepares for short-range wireless communication with the infusion pump 50.

[0051] The screen G46 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 bring the smartphone 40 closer to the infusion pump 50. The image object 482 further includes a cancel button 4821 for canceling the transfer of the order information to the infusion pump 50. When the staff selects the cancel button 4821, the smartphone 40 switches the screen from the screen G46 to the screen G45, for example.

[0052] When the staff brings the smartphone 40 close to the infusion pump 50, short-range wireless communication is established between the smartphone 40 and the infusion pump 50. In more detail, when the staff holds the smartphone 40 over a FeliCa mark 590 (see FIG. 6 ) printed on the surface of the infusion pump 50, short-range wireless communication is established between the smartphone 40 and the infusion pump 50. When short-range wireless communication is established, the smartphone 40 transmits order information to the infusion pump 50. That is, the smartphone 40 transfers the order information acquired from the server 30 to the infusion pump 50.

[0053] The infusion pump 50 stores the order information transmitted from the smartphone 40 in the storage unit 52 (FIG. 8). The storage unit 52 corresponds to the "memory" of the present invention. The storage unit 52 includes a volatile memory and a non-volatile memory. In this example, the infusion pump 50 stores the order information in the volatile memory. However, this is not limited thereto, and the infusion pump 50 may store the order information in the non-volatile memory.

[0054] Fig. 6 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. 6, the smartphone 40 switches the screen of the touch screen 43 from screen G46 to screen G47. Screen G47 includes an image object 483 and an image object 484.

[0055] The image object 483 indicates that the transfer of the order information has been completed. The image object 483 further includes a notification urging the staff member to press a setting completion button represented as an image object 484 and to press a start button 591 of the infusion pump 50 after pressing the setting completion button. When the staff member presses the setting completion button, for example, the smartphone 40 switches the screen from the screen G47 to the screen G42 (FIG. 3).

[0056] 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 G51 on the display 55. The screen G51 includes information that the operation of the infusion pump 50 is stopped. The screen G51 further includes information on the drug name, planned amount, and flow rate included in the order information. The screen G51 includes an item for the accumulated amount.

[0057] When the staff member presses the start button 591 of the infusion pump 50 while the screen G51 is displayed on the display 55 of the infusion pump 50, administration of the medicinal fluid by the infusion pump 50 begins.

[0058] When the power of the infusion pump 50 is turned off by the staff member pressing the power button 592, the order information stored in the storage unit 52 (i.e., memory) of the infusion pump 50 is erased. When the infusion pump 50 receives a predetermined operation (third operation) by the staff member, the infusion pump 50 erases the order information from the storage unit 52. The "predetermined operation" is, for example, a series of operations such as selecting the menu button 593 and selecting an image object (not shown) that instructs the deletion of the order information.

[0059] Incidentally, when the order information is transmitted from the smartphone 40 to the infusion pump 50, the order information may already be stored in the storage unit 52 of the infusion pump 50. For example, if the staff member forgets to turn off the infusion pump 50, the previously received order information remains without being erased. Another example of a case where the order information already exists in the infusion pump 50 is when the staff member properly transfers the order information to the infusion pump 50, and then mistakenly transfers other order information to be used in another infusion pump (not shown) to the infusion pump 50. In the former case, the order information should be overwritten, but in the latter case, the order information should not be overwritten.

[0060] Therefore, when order information (hereinafter also referred to as "order information_old") is stored in the memory unit 52, the infusion pump 50 has a function of inquiring of a staff member who is using the smartphone 40 to transmit order information (hereinafter also referred to as "order information_new") to the infusion pump 50 whether or not the order information needs to be overwritten. The order information_new corresponds to the "first order information" of the present invention. The order information_old corresponds to the "second order information" of the present invention.

[0061] FIG. 7 is a diagram showing the state of the infusion pump 50 when the infusion pump 50 receives new order information _new in a case where order information is stored in the memory unit 52 (specifically, a predetermined memory area) of the infusion pump 50. The "predetermined memory area" is an area in which order information referenced by the processor of the infusion pump 50 is stored when the infusion pump 50 performs a medication administration operation. Hereinafter, the memory area in which information is stored in this manner is also referred to as a "temporary area PA" (FIG. 8). The temporary area is also referred to as a work area or a working area.

[0062] When short-range wireless communication between the smartphone 40 and the infusion pump 50 is established, the order information _new is transferred to the infusion pump 50. The transferred order information _new is temporarily stored in a buffer area BA (FIG. 8) of the storage unit 52. The buffer area BA is a memory area different from the temporary area PA described above.

[0063] In this case, since the order information_old has already been stored in the temporary area PA, the infusion pump 50 displays a warning on the display 55 as shown in Fig. 7. Specifically, the infusion pump 50 displays an image object 550 on the display 55. The image object 550 includes an image object 551 that instructs the order information to be overwritten and an image object 552 that does not instruct the order information to be overwritten.

[0064] When the staff member selects the image object 551, the order information _old already stored in the storage unit 52 of the infusion pump 50 is overwritten with the order information _new newly received from the smartphone 40. That is, when the infusion pump 50 accepts an operation (first operation) of selecting the image object 551, the order information _old stored in the temporary area PA is overwritten with the order information _new stored in the buffer area BA. In addition, with the overwriting, the order information _new stored in the buffer area BA is erased.

[0065] By such a selection operation of the image object 551, the order information in the storage unit 52 is updated. Thereafter, when the staff member presses the start button 591 of the infusion pump 50, the infusion pump 50 starts administration of the medicinal fluid based on the updated order information_new.

[0066] It should be noted that if the staff member selects the image object 552, the above-mentioned overwriting process is not executed. In this case, in this example, the order information _new temporarily stored in the buffer area BA is deleted without being used.

[0067] When the order information _old is not stored in the storage unit 52, the infusion pump 50 writes the order information _new sent from the smartphone 40 into the storage unit 52 (specifically, into the temporary area PA) without displaying the image object 550. That is, the infusion pump 50 automatically writes the order information _new into the temporary area PA of the storage unit 52 without accepting an operation to select the image object 551 described above.

[0068] For example, when the file name of the order information _new stored in the buffer area BA matches the file name of the order information _old stored in the temporary area PA, the infusion pump 50 checks whether to overwrite the file as shown in Fig. 7. Alternatively, when predetermined information (typically, a command number) included in the header information of the order information _new stored in the buffer area BA matches the predetermined information included in the header information of the order information _old stored in the temporary area PA, the infusion pump 50 checks whether to overwrite the file as shown in Fig. 7. Note that the "command number" is a number indicating a command (in this example, an order information transfer request from the smartphone 40 to the infusion pump 50, or an order information transfer response from the infusion pump 50 to the smartphone 40).

[0069] 8 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.

[0070] 8, the smartphone 40 includes a control unit 41, a storage unit 42, a touch screen 43, a scanner 44, a Wi-Fi (registered trademark) 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).

[0071] 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. 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 and an order ID to the control unit 41.

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

[0073] 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 infusion pump 50 using the reader / writer 46. The smartphone 40 transmits (transfers) the order information acquired from the server 30 to the infusion pump 50, as shown as "(iv) order information" in FIG. 1.

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

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

[0076] The server 30 transmits the extracted order information to the smartphone 40 on the condition that the patient ID included in the extracted order information matches the patient ID received from the smartphone 40. Specifically, as shown as "(iii) Order Information" in FIG. 1, the server 30 transmits the order information to the smartphone 40 using the Wi-Fi communication unit 34. Upon receiving the order information from the server 30, the smartphone 40 transmits the order information to the infusion pump 50 ("(iv) Order Information" in FIG. 1). In this manner, the smartphone 40 transfers the order information acquired from the server 30 to the infusion pump 50.

[0077] 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). The storage unit 52 includes a buffer area BA and a temporary area PA. The operation button 53 includes various buttons such as a start button 591, a power button 592, and a menu button 593 shown in FIG. 7 and the like.

[0078] The infusion pump 50 acquires the order information from the smartphone 40 using the non-contact IC card 56. This enables the infusion pump 50 to perform settings and operations based on the order information.

[0079] The infusion pump 50 communicates with the server 30 using the Wi-Fi communication unit 54. The infusion pump 50 transmits the operation status of the infusion pump 50 to the server 30 using the Wi-Fi communication unit 54. The monitoring terminal 60 can obtain information indicating the operation status from the server 30 and display the operation status on a display. This allows staff to monitor the operation status of the infusion pump 50 using the monitoring terminal 60.

[0080] The control unit 51 of the infusion pump 50 controls the screen display on the display 55. The control unit 51 accepts a selection operation of image objects 551, 552 shown in FIG. 7 by a staff member using the operation buttons 53. The control unit 51 controls writing of data to the storage unit 52 and reading of data. For example, the control unit 51 writes order information to the storage unit 52 and erases (deletes) order information from the storage unit 52. The control unit 51 also executes a process of overwriting order information_old with order information_new, as described above.

[0081] 9 is a sequence diagram for explaining the flow of data processing in medicinal solution administration system 5. As shown in FIG. 9, in sequence SQ1, smartphone 40 reads barcode 811 printed on wristband 810 of a target patient with scanner 44. In sequence SQ2, smartphone 40 transmits the patient ID, which is the result of reading barcode 811, to server 30.

[0082] In sequence SQ3, the smartphone 40 reads the barcode 821 printed on the medicine label 820 of the target patient with the scanner 44. In sequence SQ4, the smartphone 40 transmits the order ID, which is the reading result of the barcode 821, to the server 30.

[0083] In sequence SQ5, 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 SQ6, the server 30 extracts the patient ID included in the extracted order information. In sequence SQ7, the server 30 checks whether the patient ID received from the smartphone 40 matches the patient ID extracted from the order information.

[0084] If the two patient IDs match, in sequence SQ8, the server 30 transmits the order information extracted in sequence SQ5 to the smartphone 40. In sequence SQ9, the smartphone 40 accepts a transfer operation of the order information received from the server 30. Upon accepting the transfer operation, in sequence SQ10, the smartphone 40 transmits the order information to the infusion pump 50 by short-range wireless communication. The transfer operation refers to the selection of the image object 481 and holding the smartphone 40 over the infusion pump 50.

[0085] 10 is a flow diagram for explaining the flow of processing of the infusion pump 50. FIG 10 shows processing following sequence SQ10 in FIG 9.

[0086] As shown in FIG. 10, in step S1, the infusion pump 50 temporarily receives the order information _new by short-range wireless communication. Specifically, the infusion pump 50 temporarily stores all of the received order information _new in a buffer area BA of the memory unit 52. In step S2, the infusion pump 50 determines whether the order information _old already exists in the memory unit 52. The infusion pump 50 determines whether the previously received order information _old remains in the memory unit 52 without being deleted. Specifically, the infusion pump 50 determines whether the order information _old already exists in the temporary area PA.

[0087] If it is determined that the order information_old exists in the memory unit 52 (YES in step S2), the infusion pump 50 displays a warning screen on the display 55 in step S3, as shown in Fig. 7. In step S4, the infusion pump 50 determines whether or not an operation to permit overwriting of the order information has been accepted. Specifically, the infusion pump 50 determines whether or not the image object 551 shown in Fig. 7 has been selected.

[0088] When the infusion pump 50 receives an operation to permit overwriting (YES in step S4), the infusion pump 50 overwrites the order information in step S5. More specifically, when the infusion pump 50 receives an operation to permit overwriting, the infusion pump 50 overwrites the order information_old stored in the above-mentioned temporary area PA in the memory unit 52 with the order information_new stored in the buffer area BA. When the infusion pump 50 has not received an operation to permit overwriting (NO in step S4), the infusion pump 50 determines in step S6 whether or not an operation to prohibit overwriting of the order information has been received. More specifically, the infusion pump 50 determines whether or not the image object 552 shown in FIG. 7 has been selected.

[0089] If the infusion pump 50 receives an operation to not allow overwriting (YES in step S6), the infusion pump 50 ends the series of transfer processes of the order information without overwriting the order information. In detail, if the infusion pump 50 receives an operation to not allow overwriting, the infusion pump 50 erases the order information_new stored in the buffer area BA without performing the above-mentioned overwriting process. If the infusion pump 50 does not receive an operation to not allow overwriting (NO in step S6), the process proceeds to step S4.

[0090] If it is determined that the order information _old does not exist in the temporary area PA of the storage unit 52 (NO in step S2), the infusion pump 50 stores the order information _new in the temporary area PA of the storage unit 52 in step S7. That is, the infusion pump 50 writes the order information _new temporarily stored in the buffer area BA to the temporary area PA without accepting any operation from the staff. This completes the series of transfer processes of the order information.

[0091] <Summary> (1) As described above, the medicinal solution administration system 5 includes the server 30, the smartphone 40 that communicates with the server 30, and the infusion pump 50 that communicates with the smartphone 40. The infusion pump 50 has a storage unit 52 (i.e., a memory) for storing order information (see FIG. 2) including a prescription order for an injection for a patient. As shown as "(iii) Order Information" and "(iv) Order Information" in FIG. 1, the smartphone 40 obtains the order information from the server 30 and transfers the order information to the infusion pump 50.

[0092] When the infusion pump 50 receives the order information _new (first order information) transmitted from the smartphone 40 and the order information _old (second order information) is already stored in the storage unit 52, the infusion pump 50 overwrites the order information _old with the order information _new on condition that a selection operation (overwrite permission operation, first operation) of the image object 551 in Fig. 7 is accepted. The infusion pump 50 operates based on the order information _new on condition that an operation (second operation) of pressing the start button 591 (Fig. 7) after the above selection operation is accepted.

[0093] According to this configuration, the infusion pump 50 does not overwrite the order information _old with the order information _new unless a selection operation (overwrite permission operation) is received from the staff. In this way, the infusion pump 50 gives the staff an opportunity to check the suitability of the order information _new when overwriting the order information.

[0094] Therefore, when the order information _old is appropriate for the infusion pump 50 and the order information _new is inappropriate for the infusion pump 50, it is possible to prevent (suppress) inappropriate order information from being set for the infusion pump 50. In this way, the medicinal solution administration system 5 can prevent inappropriate (unintended) order information from being set for the infusion pump 50 due to staff error.

[0095] (2) If the infusion pump 50 is turned off or if the infusion pump 50 accepts a predetermined operation (third operation) before receiving the order information _new, the infusion pump 50 erases the order information _old from the storage unit 52. If the infusion pump 50 receives the order information _new from the smartphone 40 after the order information _old is erased from the storage unit 52, the infusion pump 50 writes the order information _new to the storage unit 52 without accepting the above-mentioned selection operation (first operation).

[0096] According to this configuration, in the first place, it is impossible for the order information _old to be erroneously overwritten by the order information _new when the order information _old is not stored in the infusion pump 50. Therefore, by omitting the selection operation (overwrite permission operation) by the staff when writing the order information to the memory unit 52 of the infusion pump 50, it is possible to improve the convenience for the staff.

[0097] (3) The smartphone 40 has a display 431 as shown in Fig. 8. When the smartphone 40 receives the order information _new from the server 30, as shown in state (E) of Fig. 3, the smartphone 40 simultaneously displays the prescription order (Fig. 2) included in the order information _new and an image object 481 for receiving an instruction to transmit the order information _new to the infusion pump 50 on the display 431 of the touch screen 43. Based on the selection of the image object 481, the smartphone 40 transmits the order information _new to the infusion pump 50 via short-range wireless communication.

[0098] According to this configuration, the staff can quickly check the prescription order included in the order information _new when transmitting the order information _new to the infusion pump 50. Therefore, a user interface with excellent convenience can be provided to the staff.

[0099] <Modification> (1) In the above, as shown in Fig. 5, the smartphone 40 obtains the order ID by reading the barcode 821 on the medicine label 820. However, this is not limited to this. Instead of the medicine label 820, an injection prescription on which the order ID is written as a barcode and numbers, etc. may be used.

[0100] Information such as the patient ID, name, age, and two-dimensional code is printed on the injection prescription of the target patient. The staff member reads the two-dimensional code using the smartphone 40. The two-dimensional code is typically a QR code. The order ID is expressed (written) in the two-dimensional code.

[0101] In this example, the order ID is read by the smartphone 40 in this manner. The smartphone 40 then transmits the order ID to the server 30. The smartphone 40 may obtain the order ID in this manner. Instead of the QR code, a barcode containing the order ID may be printed on the injection prescription.

[0102] (2) 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 limiting. The smartphone 40 may acquire the patient ID after acquiring the order ID.

[0103] (3) In the above, an example has been described in which the smartphone 40 acquires a staff ID, a patient ID, and an order ID by scanning each code, such as a barcode, using the smartphone 40. However, this is not limited to this. The staff member may manually input these IDs into the smartphone 40, so that the smartphone 40 acquires these IDs.

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

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

[0106] As shown in Fig. 6, the order ID is written on the medicine label 820 in numbers or the like (in the example of Fig. 6, "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.

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

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

[0109] 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 Infusion pump, 53 Operation button, 55, 431 Display, 56 Card, 60 Monitoring terminal, 432 Touch panel, 441 Camera, 442 Data processing unit, 461 Transmitter, 462 Receiver, 471, 472, 473, 474, 475, 476, 477, 478, 480, 481, 482, 483, 484, 485, 486, 550, 551, 552 Image object, 590 Felica mark, 591 Start button, 592 Power button, 593 Menu button, 810 Wristband, 811,821 Barcode, 820 Medication label, 901 Hand, 951 Wrist, 2006 Patent, 4781,4801 Reset button, 4821 Cancel button, G41,G42,G43,G44,G45,G46,G47,G48,G51 Screen.

Claims

1. A server device; A terminal device that communicates with the server device; A liquid medicine administration pump that communicates with the terminal device, the drug delivery pump having a memory for storing order information including a prescription order for an injection for a patient; The terminal device acquires the order information from the server device and transfers the order information to the drug solution administration pump; The drug solution administration pump includes: when first order information is received as the order information transmitted from the terminal device, if second order information as the order information is already stored in the memory, overwriting the second order information with the first order information on condition that a predetermined first operation is accepted; A medicinal liquid administration system that operates based on the first order information on condition that a predetermined second operation is received after the first operation.

2. The drug solution administration pump includes: If the liquid administration pump is turned off or receives a third predetermined operation before receiving the first order information, the second order information is erased from the memory; 2. The medical solution administration system according to claim 1, wherein when the first order information is received from the terminal device after the second order information is erased from the memory, the first order information is written to the memory without accepting the first operation.

3. The terminal device A display is provided. when the first order information is received from the server device, the prescription order included in the first order information and an image object for receiving an instruction to transmit the first order information to the drug solution administration pump are simultaneously displayed on the display; 3. The medical solution administration system according to claim 1, further comprising: a device for transmitting the first order information to the medical solution administration pump via short-range wireless communication based on the selection of the image object.

4. A step in which the terminal device acquires order information including a prescription order for an injection for a patient from the server device; The terminal device transmits the order information to a liquid medicine administration pump; when first order information as the order information transmitted from the terminal device is received, if second order information as the order information is already stored in a memory for storing the order information, the drug solution administration pump overwrites the second order information with the first order information on condition that a predetermined first operation is received by the drug solution administration pump; and performing an operation based on the first order information on condition that a predetermined second operation is received after the first operation.

Images