JP5568112B2 - Drug mixture preparation management device, control method and control program - Google Patents

Description

  Embodiments described herein relate generally to a drug mixture preparation management device, a control method, and a control program.

2. Description of the Related Art Conventionally, in a pharmacy department of a hospital or a nurse room in a hospital ward, a preparation of a medicine prescribed by a pharmacist or nurse based on an instruction such as a prescription or an injection prescription (hereinafter referred to as mixed injection). Had gone.
When performing mixed injection, first of all, a plurality of medicines that are prescription drugs are prepared by referring to the instruction sheet, and the prepared plurality of medicines are weighed, dissolved, mixed, etc. in an appropriate procedure.

  In order to ensure this mixed injection, prior to mixed injection, an audit work was performed to check whether or not a plurality of prepared drugs are drugs to be prescribed by checking the labels and instructions of the drugs.

By the way, there are various reasons why the prescription of drugs before mixed injection may be inappropriate. Specifically, various human errors such as misreading of similar drug names and mistakes in checking the expiration date of use. It is often caused by. Even if the above-described audit work is performed, it is not easy to prevent the stock from becoming inappropriate.
Thus, several systems have been proposed that support dispensing operations in order to minimize the occurrence of dispensing errors as much as possible.

  For example, in the dispensing support system described in Patent Document 1, in a mobile terminal, a plurality of prescription drugs indicated by a barcode read from a barcode-added form and the quantity thereof are stored in a data storage unit and displayed on a display unit, Each time the barcode displayed on a plurality of medicine containers prepared for each prescription for each patient is read, the medicine information indicated by the barcode and the information on the plurality of prescription medicines stored in the data storage unit are displayed. On the basis of this, what can be checked whether the drug is a prescription drug has been proposed.

  However, in the above prior art, on the screen displayed before the audit, the necessary drugs and the required number are simply displayed as a list in text, and it is possible to work efficiently when performing the audit process continuously. Was not limited.

The drug mixture preparation management apparatus according to the embodiment is a drug mixture preparation management apparatus that requires a log-in process by inputting an ID code for each audit process when performing an audit process of a drug used for mixing preparation .
The acquisition unit acquires the contents of one order per one audit process.
The process control unit skips the login process by inputting the ID code after the end of one audit process and proceeds to the next audit process when the predetermined condition is satisfied when performing the audit process continuously. Ru is.

FIG. 1 is a schematic configuration block diagram of a drug mixture preparation management system. FIG. 2 is an external front view of the mixed injection terminal device. FIG. 3 is a schematic configuration block diagram of the mixed injection terminal device 14. FIG. 4 is a process flowchart of the mixed injection terminal device of the embodiment. FIG. 5 is an explanatory diagram of an example of a login instruction screen. FIG. 6 is an explanatory diagram of an example of an order number input screen. FIG. 7 is an explanatory diagram of an example of a display example of the order content display screen. FIG. 8 is a process flowchart of the medicine inspection process. FIG. 9 is an explanatory diagram of an example of an audit completion screen. FIG. 10 is an explanatory diagram of an example of an audit result display screen. FIG. 11 is an explanatory diagram illustrating an example of a display screen of an audit result when all drugs are prepared. FIG. 12 is an explanatory diagram of an example of the expiration date notification screen. FIG. 13 is an explanatory diagram of an example of an excessive quantity notification screen. FIG. 14 is an explanatory diagram of an example of a medicine error preparation notification screen. FIG. 15 is an explanatory diagram of an example of the implementation information confirmation instruction screen. FIG. 16 is an explanatory diagram of an example of a chart confirmation instruction screen. FIG. 17 is an explanatory diagram of an example of a reorder confirmation screen. FIG. 18 is an explanatory diagram of an example of a display example of an order content display screen when reordering is desired. FIG. 19 is a process flowchart of a button tap process performed as an interrupt process. FIG. 20 is an explanatory diagram of an example of a cancellation confirmation screen. FIG. 21 is an explanatory diagram of an example of a logout confirmation screen. FIG. 22 is an explanatory diagram of an example of the comment screen. FIG. 23 is an explanatory diagram of an example of the medicine detail information screen. FIG. 24 is an explanatory diagram of an example of an initial screen of the temporary order input process. FIG. 25 is a schematic process flowchart of the first modification. FIG. 26 is an explanatory diagram of an example of an order number input screen in the second and subsequent audit processes. FIG. 27 is a schematic process flowchart of the second modification. FIG. 28 is an explanatory diagram of an example of a sorting operation completion screen of the second modification.

Next, preferred aspects of the embodiment will be described with reference to the drawings.
FIG. 1 is a schematic configuration block diagram of a drug mixture preparation management system.
The drug mixture preparation management system 10 manages an electronic medical record, stores an electronic medical record server 11, an information processing terminal device 12 for a doctor for filling in the electronic medical record, and the electronic medical record server 11 manages the electronic medical record Information terminal device 13 for nurses for referring to and confirming, and a plurality of co-infusion terminal devices for supporting co-infusion such as preparation of medicines based on instruction information (for example, prescription information) included in the electronic medical record 14, a portable information processing terminal device 18 for doctors connected to the communication network 17 through the wireless base station 15 and the public communication network 16, a drug part server 19 that is disposed in the drug part and manages drug dispensing and the like, It has.
In the above configuration, the electronic medical record server 11, the information processing terminal device 12, the information processing terminal device 13, and the mixed injection terminal device 14 are connected to the communication network 17.

FIG. 2 is an external front view of the mixed injection terminal device.
The mixed injection terminal device 14 can be broadly divided into a touch panel display 21 capable of displaying various information such as a list of drugs to be mixed injection and an audit status of the prepared drugs, and a nurse ID as a user. In addition, an apparatus main body 22 having a scanner 37 configured as an object scanner that scans and identifies drug barcodes, drug images, and the like, a printer 23 for printing out various information, and an operator's work state are photographed. And a scale 25 for weighing the medicine to be mixed.

FIG. 3 is a schematic configuration block diagram of the mixed injection terminal device 14.
The mixed injection terminal device 14 includes an MPU 31 that controls the entire mixed injection terminal device, a ROM 32 that stores various data including a control program in a nonvolatile manner, a RAM 33 that functions as a work area and temporarily stores various data, and a database. Such as a hard disk drive capable of storing a large amount of data, an external storage device 34 configured as an SSD (Solid State Drive), a display 35 and a touch panel 36 constituting the touch panel display 21, a scanner 37, a printer 23, A communication interface 38 for performing a communication interface operation.

Here, the touch panel display 21, the scanner 37, the printer 23, and the communication interface 38 are connected to the bus 40 via the input / output I / O 39.
The external storage device 34 stores images (movies) taken from the login to logout taken by the camera 24 as work records, and data on the weight before and after the mixed injection work of the medicine measured by the scale 25 and the difference data thereof. Is saved as a work record.
In addition to the communication interface 38, the MPU 31, ROM 32, RAM 33, and external storage device 34 are connected to the bus 40.

Next, the operation of the embodiment will be described.
Prior to performing mixed injection, the doctor creates an electronic medical record including drug instruction data (for example, prescription data) using the information processing terminal device 12 and registers it in the electronic medical record server 11.
In this case, the instruction sheet data (for example, prescription data) includes information for specifying the drug to be mixed and information regarding the necessary number of each drug, and an order number for specifying the instruction sheet data. This order number is given to pharmacists and nurses who have drugs for mixed injection together with instructions (so-called mixed injection instructions), or printed as symbol codes such as barcodes on the instructions. To do.

On the other hand, when an operator such as a nurse who actually arranges the medicines to be mixed is received the order number, the medicine to be mixed is prepared.
Here, the process at the time of preparation of mixed injection medicine is demonstrated.

FIG. 4 is a process flowchart of the mixed injection terminal device of the embodiment.
In the following description, it is assumed that each operator who is permitted to operate the mixed injection terminal device 14 has an ID card and can operate the mixed injection terminal device 14 by authenticating the ID card.
On the display 35 of the touch panel display 21 of the mixed injection terminal device 14, a login screen is displayed in the initial state.

FIG. 5 is an explanatory diagram of an example of a login instruction screen.
As shown in FIG. 5, a guide comment “Please let me read the ID card” and a guide image G <b> 1 that prompts the scanner 37 to read the ID card are displayed on the login instruction screen.
Therefore, in order to perform the login process, the operator holds his / her ID card in front of the scanner 37 and reads the ID code (step S11).

FIG. 6 is an explanatory diagram of an example of an order number input screen.
When the ID code is authenticated by the login process, the MPU 31 of the co-injection terminal device 14 prompts the display screen of the display 35 to read the order number for specifying the contents of the medicine to be co-injected. G2 is displayed (step S12).

  As shown in FIG. 6, a guide comment “Please read the order number” and a guide image that prompts the scanner 37 to read the order number are displayed on the order number input screen G2. Further, when the guide image is displayed, an order number is not assigned, and a temporary order button B1 for placing an order temporarily is displayed.

As a result, when the operator causes the scanner 37 to read the order number, the MPU 31 of the mixed injection terminal device 14 inquires about the order contents to the electronic medical record server 11 or the medicine unit server 19 via the communication interface 38 and the communication network 17. Is performed (step S13).
Subsequently, the MPU 31 of the mixed injection terminal device 14 determines whether or not there is an error in the order contents based on the response of the electronic medical record server 11 or the medicine unit server 19 to the inquiry of the order contents (Step S14).

  In the determination in step S14, if the response of the electronic medical record server 11 or the medicine unit server 19 is the transmission of the list data of the mixed injection target drug corresponding to the order number, there is no error in the order contents. (Step S14; No), MPU31 displays the order content display screen G3 based on the list | wrist data of the acquired chemical | drug | medicine target drug (step S15).

FIG. 7 is an explanatory diagram of an example of a display example of the order content display screen.
The order content display screen G3 is roughly divided into a date information display area 41, an operator name display area 42, a logout button 43, a patient information display area 44, an order number display area 45, and an application date display area 46. The patient-related information display area 47, the medicine list display area 48, the list scroll button display area 49, the stop button 50, the completion button 51, and the comment display area 52 are provided.

The date information display area 41 is an area in which the date of the audit process for the medicine to be mixed is displayed.
The operator name display area 42 is an area where the name of the operator of the audit processing of the medicine to be mixed is displayed.
The logout button 43 is a button for the operator to log out.

The patient information display area 44 is an area for displaying information for specifying a patient who should prescribe the drug. Specifically, the patient name, patient ID, date of birth and gender are displayed.
The order number display area 45 is an area in which the order number acquired in step S12 is displayed.
The application date display area 46 is an area in which an application date that is a date for applying (prescribing) the medicine to a patient is displayed. This application date is specified in the electronic medical record.
The patient related information display area 47 is an area where information related to the patient is displayed. Specifically, ward information, ward information, clinical department information, and a doctor name in charge are displayed.

  In the medicine list display area 48, a medicine name display area 61 for displaying the name of the medicine to be mixed and a prescription amount of the medicine are designated by a unit representing a titer (amount that the medicine shows a certain biological action). A unit number display area 62 in which the number of units to be prescribed is displayed, and an indicated amount in which the amount (weight or volume) to be prescribed when the prescribed amount (weight or volume) of the drug is designated The number of medicines (ampule number, vial number, etc.) required to satisfy the number of units specified in the display area 63 and the unit number display area 62 or the indicated quantity specified in the indicated quantity display area 63 is the same as the number of drugs. A mark (icon, pattern) M1 is displayed side by side, and a necessary number display area 64 in which the number of medicines is displayed as a numerical value is provided. In the example of FIG. 7, the marks M1 of all the drugs are displayed with the same size, but when the number of drugs is large, the display can be made smaller. In addition, when the number exceeds a predetermined number (for example, five), the line may be displayed again every predetermined number (for example, every five).

  In the case of the example in FIG. 7, for example, as shown at the top of the list, the drug name = “1.5 g for AAA intravenous injection” (container type: vial) is necessary because the indicated amount is 1.5 g. In the number display area 64, one mark M1 indicating that it is necessary to prepare one vial is arranged, and “/ 1 V” indicating that the total number is one vial is displayed. Also, as shown at the bottom of the list, the drug name = “DDD injection solution 10 mL” (container type: ampoule bottle) indicates that it is necessary to prepare three ampoule bottles because the indicated amount is 30 mL. Two marks M1 are arranged side by side, and “/ 3A” indicating that the total number is 3 ampule bottles is displayed.

The list scroll button display area 49 includes an up scroll button 49U for scrolling the list upward and a list scroll for scrolling the list downward when all medicine lists cannot be displayed at once in the medicine list display area 48. A bottom scroll button 49D is arranged. In the example of FIG. 7, since it is not possible to scroll upward, the up scroll button 49 </ b> U represents a state where it cannot be grayed out and operated.
The cancel button 50 is a button for instructing to cancel the audit processing of the medicine to be mixed.

The completion button 51 is a button that can be operated when all the auditing processes for the mixed injection target drug are completed. In FIG. 7, the auditing process has not been completed yet, and is grayed out. Cannot be operated.
The comment display area 52 is an area in which a comment is displayed when a comment to be noted at the time of mixed injection of a drug to be mixed is registered.

In the state in which the order content display screen G3 in FIG. 7 is displayed, the operator displays the GS1 data bar displayed on the container or packaging of the mixed injection target drugs in order to perform the audit processing of the mixed injection target drugs. (GS1-RSS code: bar code for ethical drugs) is read by the scanner 37 (step S16).
Thereby, the MPU 31 performs a medicine inspection process based on the medicine list and the contents of the GS1 data bar read in Step S16 (Step S17).

FIG. 8 is a process flowchart of the medicine inspection process.
First, the MPU 31 determines whether or not a medicine corresponding to the read GS1 data bar is included in the order (step S41).
If it is determined in step S41 that the medicine corresponding to the read GS1 data bar is not included in the order (step S41; No), the MPU 31 prepares the wrong medicine not included in the order. It is determined that there is an erroneous preparation drug audit abnormality (step S42), the drug audit process is terminated, and the process proceeds to step S18.

If it is determined in step S41 that the medicine corresponding to the read GS1 data bar is included in the order (step S41; Yes), the MPU 31 determines that the quantity of medicine corresponding to the read GS1 data bar is the specified number. It is discriminate | determined whether it is in (step S43).
In the determination of step S43, when the quantity of the drug corresponding to the read GS1 data bar is not within the specified number, that is, when the quantity of the drug exceeds the specified number (step S43; No), the MPU 31 It is determined that there is a drug audit abnormality exceeding the number of drugs in which a larger amount of the drug to be prescribed is prepared (step S44), the drug audit process is terminated, and the process proceeds to step S18.

If it is determined in step S43 that the number of drugs corresponding to the read GS1 data bar is within the specified number (step S43; Yes), the MPU 31 determines that the drug corresponding to the read GS1 data bar is within the expiration date. It is determined whether or not there is (step S45).
In the determination of step S45, when the medicine corresponding to the read GS1 data bar is not within the expiration date, that is, when the expiration date of the medicine has expired (step S45; No), the MPU 31 Therefore, it is determined that the medicine inspection abnormality has expired and cannot be used for mixed injection (step S46), the medicine inspection process is terminated, and the process proceeds to step S18.

If it is determined in step S45 that the medicine corresponding to the read GS1 data bar is within the expiration date (step S45; Yes), the MPU 31 determines whether or not all medicines have been prepared in the process so far. A determination is made (step S47).
If it is determined in step S47 that all medicines have been prepared (step S47; Yes), an audit completion screen is displayed (step S48), and the process proceeds to step S18.
FIG. 9 is an explanatory diagram of an example of an audit completion screen.
On the audit completion screen G4, a message “Assembly work has been completed” is displayed, and the operator can easily confirm that the preparation work for the drugs to be mixed and the audit process for the drugs to be mixed are definitely completed. Can grasp.

On the other hand, if it is determined in step S47 that all of the medicines have not been completed yet (step S47; No), the MPU 31 indicates that the medicine audit result of the medicine currently being subjected to the medicine audit processing is normal. It is determined whether or not there has been (step S18).
If it is determined in step S18 that the medicine audit result is normal (step S18; Yes), a screen display process when the audit result is normal is performed (step S19), and the process proceeds to step S15 again to check the audit result. The display screen is reflected in the order details display screen.

FIG. 10 is an explanatory diagram of an example of an audit result display screen.
In the case of the example of the audit result display screen G5 in FIG. 10, for example, when the read medicine code is the medicine name = “5% glucose solution 100 mL”, the medicine name in the second column from the top of the list = In the indicated amount display area 63 in the column of “5% glucose solution 100 mL”, instead of one mark M1 indicating that it is necessary to prepare one bag in total at the time shown in FIG. A mark M2 (indicated by “◯” in FIG. 10) indicating that the bags have been prepared will be displayed. Furthermore, the column of drug name = “5% glucose solution 100 mL” indicates that all the drugs corresponding to the column are prepared, for example, blue line display BL.

  If the read drug code corresponds to the drug name = “DDD injection solution 10 mL”, the indication amount display in the column of drug name = “DDD injection solution 10 mL” in the sixth column from the top of the list In the area 63, at the time shown in FIG. 7, out of the three marks M1 indicating that it is necessary to prepare a total of three ampule bottles, one ampule bottle bag is used instead of the first mark M1. A mark M2 (indicated by “◯” in FIG. 10) indicating that the items are arranged is displayed. In this case, since the required number of drugs is not available, the color in the column of drug name = “DDD injection” is not changed at this time as compared with the case of FIG.

As described above, when the required number of medicines are collected from the medicines displayed in the medicine list, the corresponding column is in a state indicating that (in this example, blue line display BL). The operator can easily determine whether or not preparation has been completed for each medicine.
In addition, in the indication amount display area 63, only the number of marks already arranged (number) is displayed by being replaced with a mark different from that before the arrangement, so that the operator can easily arrange how many more are visually prepared. You can see if it ’s good.

FIG. 11 is an explanatory diagram illustrating an example of a display screen of an audit result when all drugs are prepared.
As shown in FIG. 11, when all the audit processes are normal and all the medicines are prepared, the mark M1 is displayed at the time point shown in FIG. 7 in the instruction amount display area 63 corresponding to all the medicines. The mark M2 (indicated by “◯” in FIG. 11) indicating that the medicine has been arranged is displayed in the portion where the medicine has been prepared. Further, the column of all medicines is a blue line display BL indicating that all medicines corresponding to the field are prepared.

  When the screen display when the audit result is normal is completed, the MPU 31 shifts the process to step S15 again, and the operator performs the audit process of the medicine to be mixed with the order content display screen G3 displayed at that time. In order to perform this, the scanner 37 reads the GS1 data bar (GS1-RSS code: bar code for ethical drugs) displayed on the container or packaging of the medicines to be mixed and mixed (step S16), and so on. Will be repeated.

On the other hand, if the drug audit result is abnormal in the determination in step S18 (step S18; No), the MPU 31 determines whether or not the reason for determining that the drug audit result is abnormal is an expiration date. It discriminate | determines (step S20).
In the determination of step S20, if the reason for determining that the medicine audit result is abnormal is that the usage period has expired (step S20; Yes), the MPU 31 performs a usage period expiration notification screen display process (step S21).

FIG. 12 is an explanatory diagram of an example of the expiration date notification screen.
In the expiration date notification screen G5, for example, when the drug name of the expired drug = “CCC injection 10 mg” is displayed together with the message “This drug has expired”, for example, The name “CCC Injection 10 mg”, lot number and expiration date are displayed.
When the operator confirms the content and taps the “close” button 71 displayed on the expiration date notification screen G5, the process proceeds to step S25.

Further, in the determination of step S20, when the reason for determining that the drug audit result is abnormal is not expired (step S20; No), the MPU 31 determines that the drug audit result is abnormal. It is determined whether or not the quantity exceeds the quantity (the number of medicines collected exceeds the necessary quantity) (step S22).
In the determination of step S22, when the reason why it is determined that the medicine audit result is abnormal is an excessive quantity (step S22; Yes), the MPU 31 performs an excessive quantity notification screen display process (step S23).

FIG. 13 is an explanatory diagram of an example of an excessive quantity notification screen.
On the excess quantity notification screen G6, a message “The number exceeds the indicated quantity” is displayed.
When the operator confirms the content and taps the “close” button 71 displayed on the excess quantity notification screen G6, the process proceeds to step S25.

  Further, in the determination of step S22, when the reason why the drug audit result is determined to be abnormal is not excessive (step S20; No), the MPU 31 determines that the drug audit result is determined to be abnormal. Is a medicine mispreparation notification screen display process (step S24), assuming that the medicine code of a medicine not in the instruction (prescription) is erroneously read.

FIG. 14 is an explanatory diagram of an example of a medicine error preparation notification screen.
On the wrong drug preparation notice screen G7, for example, the drug name of the wrongly prepared drug = “ZZZ intravenous infusion 100 mg” is displayed together with a message “Making mistake. Please reconfirm the prescription contents.” In this case, the drug name “ZZZ intravenous infusion 100 mg”, lot number and expiration date are displayed.

  When the operator confirms the content and taps the “close” button 71 displayed on the medicine error preparation notification screen G7, the MPU 31 performs screen display processing when the audit result is abnormal (step S25), and again performs processing. In step S15, the audit result display screen is reflected in the order content display screen display.

Here, description will be made again with reference to the audit result display screen of FIG.
In the case of the example of the audit result display screen G5 in FIG. 10, for example, if the read medicine code is “medicine name =“ CCC injection 10 mg ”and the expiration date has expired, the fourth column from the top of the list” In the indicated amount display area 63 in the column of drug name of eye = “CCC injection solution 10 mg”, one mark M1 indicating that it is necessary to prepare one ampule bottle in total at the time shown in FIG. Instead of this, a mark M3 (indicated by “x” in FIG. 10) indicating that an abnormality occurred in the audit, that is, the same medicine that has expired, is displayed. Further, the column of drug name = “CCC injection solution 10 mg” is, for example, a red line display RL indicating that the drug corresponding to the column is abnormal in audit.

  As described above, when there is an abnormality in the medicine displayed in the medicine list, the column is in a state indicating that (in this example, a red line display RL). Therefore, it can be easily understood that there is an audit abnormality.

In addition, in the indication amount display area 63, only the number of marks already arranged (number) is displayed by being replaced with a mark different from that before the arrangement, so that the operator can easily arrange how many more are visually prepared. You can see if it ’s good.
In this case, the mark M3 is linked to the reason for the abnormality in the audit, and by tapping the mark M3, the reason (display corresponding to any of FIGS. 12 to 14) is displayed. It may be.

  In the determination in step S14, if the response of the electronic medical record server 11 or the medicine unit server 19 is not the transmission of the list data of the medicines to be co-injected corresponding to the order number, there is an error in the order contents. (Step S14; Yes), MPU31 discriminate | determines whether the content of an error is an error that the medicine arrangement has already been implemented (step S26).

  If it is determined in step S26 that the content of the error has already been provided (step S26; Yes), the MPU 31 performs an execution information confirmation instruction screen display process (step S27).

FIG. 15 is an explanatory diagram of an example of the implementation information confirmation instruction screen.
On the execution information check instruction screen G8, a message “Prescription already executed. Check the execution information.” Is displayed.
When the operator confirms the content and taps the “close” button 71 displayed on the execution information confirmation instruction screen G8, the process proceeds to step S11 to display the login screen G1. Process.

If it is determined in step S26 that the content of the error has not already been prepared (step S26; No), the MPU 31 indicates that the content of the error is the prescription content, that is, the order content has been changed. It is determined whether or not there is (step S28).
If it is determined in step S28 that the error content is a change in the order content (step S28; Yes), the MPU 31 performs a chart confirmation instruction screen display process (step S29).

FIG. 16 is an explanatory diagram of an example of a chart confirmation instruction screen.
On the medical chart confirmation instruction screen G9, a message “There is the latest order. Please check the medical chart.” Is displayed.
When the operator confirms the content and taps the “close” button 71 displayed on the medical chart confirmation instruction screen G9, the process proceeds to step S11 to display the login screen G1. I do.

  If it is determined in step S28 that the error content is not a change in the order content (step S28; No), the MPU 31 displays a re-order confirmation screen because the error is a re-ordering error after the medicines are ordered. Display processing is performed (step S30).

FIG. 17 is an explanatory diagram of an example of a reorder confirmation screen.
On the reorder confirmation screen G10, a message “Arrangement is complete. Do you want to reorder?” Is displayed.
Further, on the reorder confirmation screen G10, a “Yes” button 72 that is tapped when the operator desires reordering and a “No” button 73 that is tapped when the operator does not desire reordering are displayed. .

Therefore, the MPU 31 determines which of the “Yes” button 72 or the “No” button 73 has been tapped, that is, whether the operator desires re-arrangement (step S31).
In the determination of step S31, if the operator taps the “No” button 73, that is, if the operator does not desire re-arrangement (step S31; No), the process proceeds to step S11 again. Similar processing is repeated.

FIG. 18 is an explanatory diagram of an example of a display example of an order content display screen when reordering is desired.
In step S31, when the operator taps the “Yes” button 72, that is, when the operator desires reordering (step S31; Yes), the order details display screen as the reordering execution screen is displayed. The re-arrangement execution screen display process is performed (step S32), and the order content display screen G3 is displayed (step S15).

Here, when the display screen G5 of FIG. 18 is displayed, since the preparation (medicine auditing process) has already been completed, the audit result display screen G5 when all the medicines shown in FIG. 11 are prepared is displayed. In addition, a re-sort button 75 is displayed, and the previous time of sorting is displayed in the last time of sorting time display area 76, and the name of the person in charge of previous sorting (name of the last person in charge of drug audit) is displayed in the last-time staff name display area 77. Is displayed.
Therefore, when the operator taps the reorder button 75, the order content display screen G3 in the initial state shown in FIG. 7 is displayed again, and thereafter, the medicine inspection process is similarly performed.

Next, a button tap process performed in parallel with the above process will be described.
FIG. 19 is a process flowchart of a button tap process performed as an interrupt process.
The MPU 31 constantly monitors the button tap, and when the button tap is performed, first, it is determined whether or not the stop button 50 shown in FIG. 7 has been tapped (step S51).
In step S51, when the cancel button 50 is tapped (step S51; Yes), the MPU 31 performs a cancel confirmation screen display process (step S52).
FIG. 20 is an explanatory diagram of an example of a cancellation confirmation screen.
On the cancellation confirmation screen G11, a message “Cancel. Are you sure?” Is displayed.
Further, on the cancellation confirmation screen G11, a “Yes” button 72 that is tapped when the operator desires to cancel the medicine inspection process, and a “No” button 73 that is tapped when the operator does not want to reorder are displayed. ing.

Therefore, if the “Yes” button 72 is tapped, that is, if the operator wishes to cancel the medicine inspection process, the MPU 31 proceeds to Step S11, displays the login screen G1 again, and stands by. It becomes.
On the other hand, when the “No” button 73 is tapped, the display is returned to the display screen where the stop button 50 is tapped, and the subsequent processing is continued.

If it is determined in step S51 that the cancel button 50 has not been tapped (step S51; No), the MPU 31 determines whether or not the logout button 43 shown in FIG. 7 has been tapped (step S53). .
In step S53, if the logout button 43 is tapped (step S53; Yes), the MPU 31 performs logout confirmation screen display processing (step S54).

FIG. 21 is an explanatory diagram of an example of a logout confirmation screen.
On the logout confirmation screen G12, a message “Logout. Are you sure?” Is displayed.
Further, on the logout confirmation screen G12, a “Yes” button 72 that is tapped when the operator desires to logout and a “No” button 73 that is tapped when the operator does not wish to logout are displayed.

  Therefore, when the “Yes” button 72 is tapped, that is, when the operator desires to log out, the MPU 31 proceeds to Step S11 and displays the login screen G1 again and enters a standby state.

On the other hand, when the “No” button 73 is tapped, the display returns to the display screen where the logout button 43 is tapped, and the subsequent processing is continued.
If it is determined in step S53 that the logout button 43 has not been tapped (step S53; No), the MPU 31 determines whether the completion button 51 shown in FIG. 11 has been tapped (step S55).

  If the completion button 51 is tapped in the determination in step S55 (step S55; Yes), the MPU 31 performs an audit completion screen display process for displaying the audit completion screen G4 shown in FIG. 9, and in step S11. Then, it is determined whether or not the read ID code is an ID code corresponding to an operator to be continuously read (step S56).

  Here, an operator (nurse or pharmacist) who should perform continuous reading is an operator who has been designated in advance to perform a drug audit exclusively on the day or time of the drug audit process. It is. More specifically, in the case of a nurse in charge of a ward, the nurse is a nurse who does not have a patient in charge and is assigned to work related to the entire ward.

  In the above determination, if the read ID code is not the ID code corresponding to the operator to be continuously read, the MPU 31 shifts the process to step S11, displays the login screen G1 again, and enters the standby state. Become.

  On the other hand, when the read ID code is an ID code corresponding to an operator that should perform continuous reading, the MPU 31 shifts the process to step S12 and continuously performs a medicine inspection process. .

  Therefore, even when it is necessary to perform a medicine inspection process corresponding to a plurality of order numbers, it is not necessary to perform the process from the login screen one by one, so that the work can be performed efficiently.

If the completion button 51 has not been tapped in the determination in step S55 (step S55; No), the MPU 31 determines whether or not the comment display area 52 shown in FIG. 7 has been tapped (step S57). .
If the comment display area 52 shown in FIG. 7 is tapped in the determination in step S57 (step S57; Yes), the MPU 31 performs a comment screen display process (step S58).

FIG. 22 is an explanatory diagram of an example of the comment screen.
The comment screen G13 is a screen on which an instruction comment from the drug part in the corresponding prescription is displayed.
On the comment screen G13, a message “There is an instruction from the pharmacy for this order” is displayed.

  Further, the comment screen G13 includes a comment display portion 81 for displaying an instruction from the medicine portion, a “close” button 82 for closing the comment screen G13, an up scroll button 83 for scrolling the comment upward, and a comment. And a scroll button 84 for scrolling down the screen.

Accordingly, when the up scroll button 83 or the down scroll button 84 is tapped, the MPU 31 scrolls the comment upward or downward in the comment display unit 81.
Further, when the “close” button 82 is tapped, the MPU 31 returns to the display screen where the comment display area 52 is tapped, and continues processing thereafter.

If the comment display area 52 has not been tapped in the determination in step S57 (step S57; No), the MPU 31 has tapped the mark M2 corresponding to the medicine for which the medicine inspection shown in FIG. It is determined whether or not (step S59).
When the mark M2 corresponding to the medicine for which the medicine inspection shown in FIG. 10 has been successfully completed is tapped in the determination in step S59 (step S59; Yes), the MPU 31 details the medicine corresponding to the mark M2. A detailed drug information screen display process for displaying information is performed (step S60).

FIG. 23 is an explanatory diagram of an example of the medicine detail information screen.
On the detailed drug information screen G14, a message “detailed information confirmation” is displayed. Further, on the detailed drug information screen G14, as detailed information of the drug corresponding to the mark M2, detailed information display for displaying the drug name (in the example of FIG. 23, “5% glucose solution 500 mL”), the lot number, and the expiration date is displayed. And a “close” button 82 for closing the detailed drug information screen G14.

  Therefore, when the “close” button 82 is tapped, the MPU 31 returns to the display screen where the mark M2 is tapped, and continues processing thereafter.

If it is determined in step S59 that the mark M2 corresponding to the medicine for which medicine inspection has been completed successfully has not been tapped (step S59; No), the MPU 31 has tapped the temporary order button B1 shown in FIG. It is determined whether or not (step S61).
If it is determined in step S61 that the temporary order button B1 shown in FIG. 6 has not been tapped (step S61; No), the MPU 31 ends the process.
If the temporary order button B1 shown in FIG. 6 is tapped in the determination in step S61 (step S61; Yes), the MPU 31 performs a temporary order input process (step S62).

FIG. 24 is an explanatory diagram of an example of an initial screen of the temporary order input process.
On the initial screen G15 of the temporary order input process, a message “Please select the patient” is displayed.

  Furthermore, on the initial screen G15 of the temporary order input process, the patient list display selection area 91 in which the patient name list to be input for the temporary order is displayed so as to be selectable, and the patient list in the patient list display selection area 91 is scrolled up. Up scroll button 92, down scroll button 93 for scrolling down the patient list in patient list display selection area 91, button 94 for returning to order number input screen G2 shown in FIG. 6, and selection in patient list display selection area 91 A determination button 95 for determining any one of the patients is displayed.

  Accordingly, when the MPU 31 determines to select any patient by the determination button 95, the MPU 31 shifts to a temporary order input process for the patient.

  As described above, according to the present embodiment, even when an operator having a specific ID code has to continuously perform a medicine inspection process corresponding to a plurality of order numbers in a dedicated manner, the order number is read. At this time, it is not necessary to perform login processing one by one, and work can be performed efficiently.

Next, a modification of the embodiment will be described.
In the above description, the case where an operator having a specific ID code performs a medicine audit process corresponding to a plurality of order numbers continuously in a dedicated manner has been described as an example. In this embodiment, when the completion button 51 is tapped for completion of the medicine audit corresponding to, the order number reading process is immediately performed.

FIG. 25 is a schematic process flowchart of the first modification.
First, when performing the first medicine inspection process, the operator performs a login process (step S11) and causes the order number to be read (step S12), as in the above-described embodiment.
Thereby, the auditing process as shown in FIGS. 4 and 8 is performed (step S70).

When the audit process is completed and the operator taps the completion button 51 as shown in FIG. 25 (step S55; Yes), the MPU 31 shifts the process to step S12 again.
On the other hand, when the operator has not tapped the completion button 51 (step S55; No), the MPU 31 determines whether or not the operator has performed a logout operation for tapping the logout button 43 (step S71).
If it is determined in step S71 that the operator has not tapped the logout button 43 (step S71; No), the process returns to step S55 to determine whether the operator has tapped the completion button 51 or not. Thereafter, the same processing is performed.
On the other hand, when the operator taps the logout button 43 in the determination of step S71 (step S71; Yes), the process again proceeds to step S11 and waits for the login process.

FIG. 26 is an explanatory diagram of an example of an order number input screen in the second and subsequent audit processes.
The order number input screen G2A of FIG. 26 differs from the embodiment of FIG. 6 in that a message “You can read the order number continuously” is displayed, and a logout button 43A is displayed. Until the logout button 43A is tapped, the order number formed as a symbol code can be immediately read by the scanner 37, and the process can be immediately transferred to an audit process by actually reading the order number. It is.

  Therefore, according to the first modification, even when the operator has to continuously perform medicine inspection processing corresponding to a plurality of order numbers, it is not necessary to perform login processing one by one when reading the order numbers. Work can be done efficiently.

  In the first modification, when the completion button 51 is tapped for the completion of the medicine inspection corresponding to one order number, the process immediately shifts to the order number reading process. Is an embodiment in which the operator can select whether or not to perform continuous reading on the sorting operation completion screen.

FIG. 27 is a schematic process flowchart of the second modification.
Also in the second modification, when the operator performs the first medicine inspection process, the operator performs the login process (step S11) and reads the order number (step S11) as in the above-described embodiment. S12).
Thereby, the auditing process as shown in FIGS. 4 and 8 is performed (step S70).

FIG. 28 is an explanatory diagram of an example of a sorting operation completion screen of the second modification.
When the audit process is completed and the operator taps the completion button 51 as shown in FIG. 27 (step S55; Yes), the MPU 31 displays an audit completion (sorting work completion) screen G4 shown in FIG.

  As shown in FIG. 28, in addition to the logout button 43A, the “Continue” button 101 for continuously performing the medicine inspection process (medicine preparation work) is displayed on the audit completion screen G4. When performing a medicine inspection process (medicine preparation work), it is possible to shift to the order number reading process (step S12) simply by tapping the “Continue” button 101, and there is no need to perform a login process one by one. Work can be performed.

That is, the MPU 31 determines whether or not an operation of the “Continue” button 101, that is, a continuous reading instruction operation has been performed on the audit completion screen G4 shown in FIG. 28 (step S72).
If it is determined in step S72 that the “continue” button 101 is operated, that is, if a continuous reading instruction operation is performed (step S72; Yes), the process proceeds to step S12, and the medicine inspection process (medicine) is continuously performed. Assortment work), and it is not necessary to perform login processing one by one.

  In step S72, if the operation of the “continue” button 101, that is, the continuous reading instruction operation is not performed (step S; No), the MPU 31 performs a logout operation in which the operator taps the logout button 43. It is determined whether or not (step S73).

If it is determined in step S73 that the operator has not tapped the logout button 43 (step S73; No), the process proceeds to step S72 again, and the same process is performed thereafter.
On the other hand, when the operator taps the logout button 43 in the determination of step S73 (step S73; Yes), the process again proceeds to step S11 and waits for the login process.

On the other hand, if it is determined in step S55 that the operator has not tapped the completion button 51 (step S55; No), the MPU 31 has performed a stop operation for tapping the stop button 50 for instructing to stop the audit. Is determined (step S74).
If it is determined in step S74 that the operator has not tapped the stop button 50 (step S74; No), the process proceeds to step S55 again, and the same process is performed thereafter.

  If it is determined in step S74 that the operator taps the cancel button 50 (step S74; Yes), the process proceeds to step S11 again to wait for the login process.

  In the above description, the case where the electronic medical record server 11 stores the electronic medical record including the medical instruction data (for example, prescription data) has been described. However, the medical instruction server 19 manages this medical instruction data. It is also possible to configure such that a management server for separately managing prescription data is provided.

In the above description, the electronic medical record server 11 and the medicine unit server 19 have been described as being a single information processing apparatus, but can be configured as a cloud including a plurality of information processing apparatuses.
In the above description, the doctor's portable information processing terminal device 18 has not been described in detail, but the portable information processing terminal device 18 is connected to the communication network 17 via the wireless base station 15 and the public communication network 16. Furthermore, it is possible to connect to the electronic medical record server 11 or the medicine unit server 19 so that the electronic medical record can be edited.

In the above explanation, in order to identify nurses as users and drugs to be mixed (sorted), scan the nurse ID, drug barcode (identification code), drug image, etc. However, when an identification RFID is used, an RFID reader (or RFID reader / writer) that reads the identification code included in the RFID tag is provided instead of the scanner 37. It is also possible. In this case, it is also possible to read the RFID tags of a plurality of medicines at once. Furthermore, if the identification information (identification code) is associated with a nurse ID or a medicine, a reader (or reader / writer) that reads the identification information can be provided.
Further, identification codes such as the above-described barcodes and identification codes included in RFID tags can be used for the disposal management of medicines including blood for blood transfusion and the like.

In the above description, the role of the scale 25 has not been described in detail, but here, a method of using the scale 25 to prevent dispensing errors will be described.
The MPU 31 measures the weight on the balance 25 in a state where the medicine is specified before and after the actual mixed injection operation. The MPU 31 records the difference in weight before and after the mixed injection operation in the external storage device 34 in association with the medicine.

  This is because, for example, when a medicine is placed in a vial, when performing a co-infusion operation corresponding to one instruction sheet, not all of the medicine is used, and a part of the medicine is mixed by a syringe or the like. This is because it may be used for work. As a result, if the difference in weight before and after the use of the medicine is obtained, the amount of the medicine used in the actual mixed injection work can be grasped.

  Then, the MPU 31 compares the medicine with the instruction amount indicated in the instruction data (the amount displayed in the instruction amount display area 63). It is determined that In this case, the MPU 31 performs a process of converting the difference in weight into the capacity when the instruction amount is designated by the capacity.

On the other hand, when the difference from the instruction amount indicated in the instruction data exceeds the allowable difference, it is notified that the mixed injection work is not normally performed.
As a result, the co-infusion terminal device 14 can monitor the co-infusion operation and prevent it from being actually prescribed by the patient in a dispensing error state.

  As another first aspect of the present embodiment, in the medicine mixture preparation management apparatus that requires a login process for each audit process when performing the audit process of the medicine used for the mixture preparation, the audit process is continuously performed. In the case of performing the drug mixing preparation management apparatus, the process control unit is configured to omit the login process after the end of one audit process and shift to the next audit process when a predetermined condition is satisfied.

  In another second aspect of the present embodiment, the predetermined condition is that the operator ID input in the first login process is the same as an operator ID registered in advance as an ID that can be continuously processed. There may be.

  As another third aspect of the present embodiment, the audit process is performed based on the read identification code read from the identification code given in advance to the medicine, and the predetermined condition is: The identification code may be read.

  As another fourth aspect of the present embodiment, the predetermined condition may be a case where the operator gives an instruction to continue the audit process after the end of one audit process.

  In addition, as another fifth aspect of the present embodiment, in the control method executed by the drug mixture preparation management apparatus that requires a login process for each audit process when performing the audit process of the drug used for the mixture preparation. A determination process for determining whether or not a predetermined condition is satisfied when continuously performing the audit process, and a login after completion of one audit process when the predetermined condition is satisfied in the determination And a process control process for skipping the process and moving to the next audit process.

  In addition, as another sixth aspect of the present embodiment, when performing an audit process for a drug used for mixing preparation, a drug mixture preparation management apparatus that requires a login process for each audit process is controlled by a computer. A control program for determining whether or not a predetermined condition is satisfied when the computer continuously performs the audit process; and when the predetermined condition is satisfied in the determination, This is a control program that functions as a process control unit that skips the login process after the end of one audit process and shifts to the next audit process.

  The control program executed by the drug mixture preparation management apparatus of the present embodiment is a file in an installable or executable format, such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), or the like. And recorded on a computer-readable recording medium.

  In addition, the control program executed by the drug mixture preparation management device of the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Further, the control program executed by the drug mixture preparation management device of the present embodiment may be provided or distributed via a network such as the Internet.

Moreover, you may comprise so that the control program of the chemical | medical agent mixing preparation management apparatus of this embodiment may be provided by previously incorporating in ROM etc.
Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

10 Drug Mixing Preparation Management System 11 Electronic Medical Record Server 12 Information Processing Terminal Device (for Doctors)
13 Information processing terminal equipment (for nurses)
14 Mixed injection terminal device (drug mixture preparation management device)
DESCRIPTION OF SYMBOLS 15 Wireless base station 16 Public communication network 17 Communication network 18 Portable information processing terminal device 19 Drug department server 21 Touch panel display 22 Device main body 23 Printer

JP 2005-334056 A

Claims (6)

In the drug mixture preparation management apparatus that requires a log-in process by inputting an ID code for each audit process when performing the audit process of the drug used for mixing preparation,
Acquisition means for acquiring the contents of one order per one audit process;
A process control unit for skipping the login process by inputting the ID code after the end of one audit process and shifting to the next audit process when a predetermined condition is satisfied when performing the audit process continuously; Prepared,
Drug mixing preparation management device. The predetermined condition is a case where the operator ID input in the first login process is the same as an operator ID registered in advance as an ID that can be continuously processed.
The drug mixture preparation management device according to claim 1. The audit process is performed based on the read identification code, reading the identification code attached to the medicine in advance,
The predetermined condition is when the identification code is read.
The drug mixture preparation management device according to claim 1. The predetermined condition is a case where the operator instructs to continue the audit process after the end of one audit process.
The drug mixture preparation management device according to claim 1. In the control method executed by the drug mixture preparation management apparatus that requires a log-in process by ID code input for each audit process when performing the audit process of the drug used for mixing preparation,
An acquisition process to acquire the contents of one order per audit process;
A determination process for determining whether or not a predetermined condition is satisfied when the audit process is continuously performed;
In the determination, when the predetermined condition is satisfied, a process control step of skipping the login process by the ID code input after the end of one audit process and shifting to the next audit process;
Control method with. A control program for controlling a drug mixture preparation management device that requires a log-in process by inputting an ID code for each audit process when performing a drug audit process used for mixing preparation,
The computer,
Acquisition means for acquiring the contents of one order per one audit process;
A discriminating means for discriminating whether or not a predetermined condition is satisfied when the audit process is continuously performed;
In the determination, when the predetermined condition is satisfied, a process control means for skipping the login process by the ID code input after the end of one audit process and shifting to the next audit process;
Control program to function.

Images