Medicinal solution administration system and information processing method

Abstract

To provide a medicinal solution administration system capable of preventing a terminal device from transmitting incorrect order information for a patient to a medicinal solution administration pump used by the patient.SOLUTION: A server device stores multiple pieces of order information each including a prescription order for an injection, first order identification information for identifying the order information, and first patient identification information for identifying a patient. When the terminal device acquires second patient identification information and second order identification information, the terminal device transmits the second patient identification information and the second order information to the server device. The server device extracts order information including the first order identification information that matches the second order identification information from the multiple pieces of order information. The server device transmits the extracted order information to the terminal device on condition that the first patient identification information included in the extracted order information matches the second patient identification information. The terminal device transmits the order information received from the server device to a medicinal solution administration pump.SELECTED DRAWING: Figure 8

Description

[Technical field]

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

[0002] Conventionally, systems for administering a medicinal liquid to a patient have been known. For example, Japanese Patent Laid-Open Publication No. 2002-117144 (Patent Document 1) discloses, as such a system, a management system for administering medicines, etc., which includes a management system for managing patient information and administration information of medicines, etc., and a portable terminal device with a reading function capable of communicating with the management system.

[0003] The management system included in the drug administration management system disclosed in Patent Document 1 has an input means for inputting information including patient information and drug administration instructions, and a registration means for registering basic information for identifying a patient and information including administration instructions for the drug to be administered to the patient in a portable terminal device. The portable terminal device has a reading means for reading the basic information given to the patient and information given to the drug to be administered to the patient, and a comparison means for comparing the read information with information including administration instructions registered in the management system. If the result of the determination by the comparison means is a mismatch, the portable terminal device warns the person administering the drug. [Prior art documents] [Patent documents]

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

[0005] In Patent Document 1, the above-mentioned matching process is executed in the mobile terminal device. Therefore, prior to the matching, the mobile terminal device needs to obtain in advance from the management system basic information for identifying the patient and information including administration instructions regarding medicines and the like to be administered to the patient.

[0006] Furthermore, the drug administration management system of Patent Document 1 does not include liquid drug administration pumps such as infusion pumps and syringe pumps as linked devices. Therefore, in Patent Document 1, when the result of the determination by the collation means is a match, and a drug or blood product is administered to a patient based on the collation result, the mobile terminal device only transmits administration result information to the management system and stores it.

[0007] In a system including a liquid medicine administration pump as described above, if a terminal device can obtain order information, including a prescription order for an injection for a patient, from a server and send the order information to the liquid medicine administration pump, convenience can be improved through device linkage.

[0008] The present disclosure provides a medical fluid administration system and an information processing method that can prevent a terminal device from transmitting incorrect order information for a patient to a medical fluid administration pump used by the patient. [Means for solving the problem]

[0009] 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 server device stores a plurality of order information, each of which includes a prescription order for an injection for a patient. Each order information further includes first order identification information that identifies the order information and first patient identification information that identifies the patient. When the terminal device acquires the second patient identification information, the terminal device transmits the second patient identification information to the server device. When the terminal device acquires the second order identification information, the terminal device transmits the second order identification information to the server device. The server device extracts order information including first order identification information that matches the second order identification information from the plurality of order information. The server device transmits the extracted order information to the terminal device on condition that the first patient identification information included in the extracted order information matches the second patient identification information. The terminal device transmits the order information received from the server device to the medicinal liquid administration pump.

[0010] According to another aspect of the present disclosure, an information processing method includes a step of storing a plurality of order information items, each of which includes a prescription order for an injection for a patient, in a server device. Each of the order information items further includes first order identification information for identifying the order information item and first patient identification information for identifying the patient. The information processing method further includes a step of transmitting the second patient identification information to the server device when a terminal device capable of communicating with the server device acquires the second patient identification information, a step of transmitting the second order identification information to the server device when the terminal device acquires the second order identification information, a step of the server device extracting order information including the first order identification information that matches the second order identification information from the plurality of order information items, a step of the server device transmitting the extracted order information to the terminal device on condition that the first patient identification information included in the extracted order information matches the second patient identification information, and a step of the terminal device transmitting the order information received from the server device to a drug solution administration pump. Effect of the Invention

[0011] According to the above disclosure, it is possible to prevent a terminal device from transmitting incorrect order information for a patient to a drug solution administration pump used by that patient. [Brief description of the drawings]

[0012] [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] FIG. 2 is a block diagram of each device that constitutes the drug solution administration system. [Figure 8] 10 is a sequence diagram for explaining the flow of data processing in the drug solution administration system. FIG. [Figure 9] A diagram showing the reading of an injection prescription using a smartphone. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

[0018] The server 30 is configured to be able to communicate with the smartphone 40 and 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).

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

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

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

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

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

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

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

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

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

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

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

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

[0031] 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. 6. Fig. 3 is a diagram showing the transition of screens on the smartphone 40.

[0032] With reference to Fig. 3, when the smartphone 40 starts a predetermined application program by an operation of a staff member, the smartphone 40 displays a screen G41 on the touch screen 43 as shown in state (A) of Fig. 3. The screen G41 is a login screen. The screen G41 includes an image object 471. In this example, the application program has a function of reading one-dimensional codes (i.e., barcodes) and two-dimensional codes such as QR codes (registered trademark).

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

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

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

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

[0037] When the staff member selects image object 473 with his / her finger, 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.

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

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

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

[0041] When the smartphone 40 transmits the patient ID to the server 30, authentication is performed by the server 30 using the patient ID, and the smartphone 40 displays a screen G44 on the touch screen 43 as shown in state (D) of FIG. 3. The screen G44 includes an image object 478 and an image object 477.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0070] 8 is a sequence diagram for explaining the flow of data processing in medicinal solution administration system 5. As shown in FIG. 8, 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.

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

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

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

[0074] <Summary> 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, as shown in Fig. 1. The server 30 stores a plurality of order information #1, #2, ... #N, each of which includes a prescription order for an injection for a patient, as shown in Fig. 2. Each order information further includes an order ID (first order identification information) that identifies the order information, and a patient ID (first patient identification information) that identifies the patient, as shown in Fig. 2.

[0075] When the smartphone 40 acquires a patient ID (second patient identification information) by scanning a barcode 811 (first code) printed on a patient's wristband 810 using the scanner 44 (FIG. 7) as shown in FIG. 4, the smartphone 40 transmits the patient ID to the server 30. When the smartphone 40 acquires an order ID (second order identification information) by scanning a barcode 821 (second code) printed on a medicine label 820 using the scanner 44 as shown in FIG. 5, the smartphone 40 transmits the order ID to the server 30.

[0076] As shown in sequence SQ5 of Fig. 8, the server 30 extracts order information including an order ID that matches the order ID received from the smartphone 40 from among the multiple pieces of order information #1, #2, ... #N. As shown in sequences SQ6 to SQ8 of Fig. 8, 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. As shown in sequence SQ10 of Fig. 8, the smartphone 40 transmits the order information received from the server 30 to the infusion pump 50.

[0077] According to this configuration, even if the order information includes the order ID written in the barcode 821 of the medicine label 820, if the order information does not include the same patient ID as the patient ID written in the barcode 811 of the wristband 810, the order information will not be transmitted from the server 30 to the smartphone 40. 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.

[0078] As shown in state (E) of Fig. 3, the smartphone 40 simultaneously displays, on the display 431 (Fig. 7) of the touch screen 43, at least the prescription order (part of the display in the image object 481 in Fig. 2) included in the order information (Fig. 2) and an image object 481 for receiving an instruction to transmit the order information to the infusion pump 50. Based on the selection of the image object 481, the smartphone 40 transmits the order information to the infusion pump 50 via short-range wireless communication.

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

[0080] <Modification> (1) In the above, as shown in FIG. 5, the smartphone 40 acquires the order ID by reading the barcode 821 on the medicine label 820. However, this is not limited to this. Below, two other examples of acquiring the order ID will be described.

[0081] Fig. 9 is a diagram showing the reading of an injection prescription by the smartphone 40. As shown in Fig. 9, information such as the patient ID, name, age, and two-dimensional code 831 is printed on an injection prescription 830 of a target patient. A staff member reads the two-dimensional code 831 using the smartphone 40. In this example, the two-dimensional code 831 is a QR code. The order ID is expressed (written) in the two-dimensional code 831.

[0082] In this example, the order ID is read by the smartphone 40 in this manner. The smartphone 40 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 830.

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

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

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

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

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

[0088] As with the drug label 820, the order ID is written in numbers or the like (not shown) on the injection prescription 830 in Fig. 9 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.

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

[0090] 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 Contactless IC 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, 491, 493, 495 Image object, 590 Felica mark, 591 Start button, 810 Wristband, 811,821 barcode, 820 medication label, 830 injection prescription, 831 2D code, 901 hand, 951 wrist, 4781,4801 reset button, 4811 cancel button, G41,G42,G43,G44,G45,G46,G47,G49,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 server device stores a plurality of pieces of order information each including a prescription order for an injection for a patient; Each of the order information further includes first order identification information that identifies the order information and first patient identification information that identifies the patient; The terminal device When acquiring second patient identification information, transmitting the second patient identification information to the server device; When acquiring second order identification information, transmitting the second order identification information to the server device; The server device includes: extracting, from the plurality of pieces of order information, the order information including the first order identification information that matches the second order identification information; transmitting the extracted order information to the terminal device on condition that the first patient identification information included in the extracted order information matches the second patient identification information; The terminal device transmits the order information received from the server device to the liquid administration pump.

2. The terminal device A scanner is provided. The medical solution administration system according to claim 1 , wherein the second patient identification information is obtained by scanning a first code printed on a wristband of the patient using the scanner.

3. The medicinal solution administration system according to claim 2 , wherein the terminal device acquires the second order identification information by scanning a second code printed on a medicine label or an injection prescription using the scanner.

4. The terminal device A display is provided. displaying, on the display, the prescription order included in the order information and an image object for receiving an instruction to transmit the order information to the drug solution administration pump at the same time; The liquid medicine administration system according to claim 1 , further comprising: a controller configured to transmit the order information to the liquid medicine administration pump via short-range wireless communication based on the selection of the image object.

5. storing a plurality of order information items, each of which includes a prescription order for an injection for a patient, in a server device, each of the order information items further including first order identification information for identifying the order information item and first patient identification information for identifying the patient; a step of transmitting, when a terminal device capable of communicating with the server device acquires second patient identification information, the second patient identification information to the server device; When the terminal device acquires second order identification information, the terminal device transmits the second order identification information to the server device; The server device extracts, from the plurality of pieces of order information, the order information including the first order identification information that matches the second order identification information; the server device transmitting the extracted order information to the terminal device on condition that the first patient identification information included in the extracted order information matches the second patient identification information; The information processing method further comprises a step of transmitting, by the terminal device, the order information received from the server device to a liquid medicine administration pump.

Images