JP7355992B2 - Dispensing management system, dispensing management program - Google Patents

Description

The present invention relates to a dispensing management system for managing drug dispensing operations in medical institutions such as hospitals.

In medical institutions such as hospitals, prescription data is issued by inputting prescription details into an electronic medical record system or the like by a doctor. Then, the medicine dispensed based on the prescription data is given to the patient at the medication counter. Note that a dispensing management system for managing dispensing operations performed in medical institutions has been known for some time (for example, see Patent Document 1).

JP 2017-130226 Publication

By the way, if the patient does not come to the medication counter to pick up the medicine on the day the prescription data is issued, the medicine will be stored at the medical institution as a leftover medicine that was not given to the patient. Note that it is desirable that the leftover medication be handed over to the patient the next time he/she comes to the medication counter. However, there is a problem in that the person in charge of the medication counter cannot easily know whether there is any leftover medication for each patient, resulting in poor operational efficiency at the medication counter.

An object of the present invention is to provide a dispensing management system and a dispensing management program that can easily determine the presence or absence of leftover medicines for a patient.

The dispensing management system according to the present invention includes a reception processing unit that receives processed input of drug delivery regarding prescription data, a selection processing unit that selects the prescription data to be processed, and a selection processing unit that selects the prescription data to be processed. First prescription data issued within a predetermined specific period and information regarding prescription data for which the prescription data and the patient are the same and for which the processed input has not been accepted by the reception processing unit, and the first prescription data issued within a predetermined specific period and the specific period and a display processing unit that displays the second prescription data in a distinguishable manner from the externally issued second prescription data.

The dispensing management program according to the present invention includes the steps of accepting a processed input of drug delivery related to prescription data, selecting the prescription data to be processed, and if the selected prescription data and the patient have the same prescription data. Information regarding prescription data for which the processed input has not been accepted can be distinguished from first prescription data issued within a predetermined specific period and second prescription data issued outside the specific period. This is a program for causing a computer to execute the steps of displaying in the form of a computer.

Advantageous Effects of Invention According to the present invention, there is provided a dispensing management system and a dispensing management program that can easily determine the presence or absence of leftover medicine for a patient.

FIG. 1 is a block diagram showing a schematic configuration of a dispensing management system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of prescription management information used in the dispensing management system according to the embodiment of the present invention. FIG. 3 is a flowchart showing an example of a prescription management process used in the prescription management system according to the embodiment of the present invention. FIG. 4 is a diagram showing an example of a medicine bag issued by the dispensing management system according to the embodiment of the present invention. FIG. 5 is a diagram showing an example of an exchange ticket issued by the dispensing management system according to the embodiment of the present invention. FIG. 6A is a flowchart illustrating an example of medication window support processing executed by the dispensing management system according to the embodiment of the present invention. FIG. 6B is a flowchart illustrating an example of medication window support processing executed by the dispensing management system according to the embodiment of the present invention. FIG. 7 is a diagram illustrating a display example of a medication window screen in the dispensing management system according to the embodiment of the present invention. FIG. 8 is a diagram showing a display example of a medication window screen in the dispensing management system according to the embodiment of the present invention. FIG. 9 is a diagram showing a display example of a medication window screen in the dispensing management system according to the embodiment of the present invention.

Embodiments of the present invention will be described below with reference to the accompanying drawings to provide an understanding of the present invention. Note that the following embodiments are examples of embodying the present invention, and are not intended to limit the technical scope of the present invention.

[Dispensing management system 1]
As shown in FIG. 1, a dispensing management system 1 according to an embodiment of the present invention includes a server 2, a client terminal 3, and the like. The server 2 and the client terminal 3 are connected to be able to communicate wirelessly or by wire via a communication network N1 such as a LAN, WAN, the Internet, or an intranet. Further, a host system 6, a dispensing device 7, a printer 8, etc. are connected to the server 2 via a communication network N1.

The host system 6 is an electronic medical record system or a prescription input terminal that inputs prescription data registered by a doctor into the server 2. The prescription data includes, for example, "prescription ID", "patient ID", "voucher number", "order number", "prescription classification", "barcode information", "prescription issue date", and "patient name". , "Patient date of birth", "Drug information (drug code, drug name, dose, etc.)", "Dosage form information (oral use, external use, etc.)", "Dosage information (three times a day after each meal, etc.)", " Information such as "type of treatment (outpatient, inpatient, etc.)," "department," "ward," and "room" is included. In addition, in the host system 6, the exchange ticket numbers are assigned consecutive numbers on the prescription issue date of the prescription data. That is, the prescription data can be identified by a combination of the prescription issue date and the voucher number. In addition, as another embodiment, a voucher number may be assigned by the control unit 21 on the server 2 side for each prescription issue date and added to the prescription data.

The dispensing device 7 is used to dispense drugs based on dispensing data input from the server 2. For example, the dispensing equipment 7 includes a tablet packaging machine, a powder medicine packaging machine, a liquid medicine dispensing machine, a sheet dispensing device, a picking auxiliary device, an anticancer drug preparation support system, a mixed injection device, a drug weighing device, a preparation inspection device, and a discrimination device. equipment, etc.

The printer 8 is used to print various types of information based on print data received from the server 2 or client terminal 3. Specifically, a printer 8 placed in a dispensing room where medicines are dispensed stores prescriptions containing information for dispensing medicines based on the prescription data, and medicines that have been dispensed based on the prescription data. Used for printing printed materials such as medicine bags. Further, the printer 8 placed at the accounting counter where patients pay is used to print printed materials such as vouchers necessary for patients to receive medicine at the medication counter.

[Client terminal 3]
As shown in FIG. 1, the client terminal 3 is a personal computer that includes a control section 31, a data storage section 32, a communication interface 33, a display section 34, an operation section 35, a barcode reader 36, and the like. Each component provided in the client terminal 3 is connected by a bus 30.

The client terminal 3 is installed in a medical institution where the dispensing management system 1 is used, such as a dispensing room where drugs are dispensed, a medication counter where drugs are given to patients, and an accounting counter where payments are made. Hereinafter, when distinguishing the client terminals 3 installed at the dispensing room, the medication counter, and the accounting counter, they may be referred to as a client terminal 3A, a client terminal 3B, and a client terminal 3C. Further, in the server 2, information (for example, IP address, etc.) indicating the installation location of each client terminal 3 is set in advance, and the control unit 21 can recognize the installation location of each client terminal 3 accessing the server 2. . Note that each client terminal 3 may store different application programs depending on the installation location.

The control unit 31 includes control devices such as a CPU, ROM, RAM, and EEPROM (registered trademark, hereinafter the same). The CPU is a processor that executes various types of arithmetic processing. The ROM is a non-volatile storage section in which information such as control programs for causing the CPU to execute various processes is stored in advance. The RAM is a volatile storage section, and the EEPROM is a nonvolatile storage section. The RAM and the EEPROM are used as temporary storage memory (work area) for various processes executed by the CPU. Then, the control unit 21 uses the CPU to execute various processes according to various control programs stored in advance in the ROM, the EEPROM, or the data storage unit 32.

The communication interface 33 includes a network card or the like that performs wireless or wired data communication with the server 2 or the like via the communication network N1 according to a predetermined communication protocol.

The display unit 34 is a display means such as a liquid crystal display or an organic EL display that displays various information according to control instructions from the control unit 31. The display unit 34 also includes a speaker, etc. that outputs audio according to control instructions from the control unit 31.

The operating unit 35 is operating means such as a keyboard and a mouse (pointing device) that are operated by the user to input various information to the client terminal 3. Further, the operation unit 35 may be a touch panel that accepts touch operations on the display screen of the display unit 34, or a voice input device that accepts input of various information through voice recognition. In the client terminal 3, operations such as "operation", "selection", and "input" by a user such as a pharmacist are performed using the operation unit 35.

The barcode reader 36 is an example of a code reading unit that reads code information such as a one-dimensional code such as a barcode or a two-dimensional code such as a QR code (registered trademark). Specifically, in the client terminal 3, the barcode reader 36 is used to read code information indicating prescription identification information that can identify prescription data from a prescription, the medicine bag, the exchange ticket, or the like. The code information read by the barcode reader 36 is input to the control unit 31 and transmitted to the server 2 by the control unit 31.

[Server 2]
As shown in FIG. 1, the server 2 is a personal computer that includes a control section 21, a data storage section 22, a communication interface 23, a display section 24, an operation section 25, a drive device 26, and the like. Each component provided in the server 2 is connected by a bus 20. Note that the server 2 may be provided outside the medical institution where the dispensing management system 1 is used.

The communication interface 23 includes a network card or the like that performs wireless or wired data communication according to a predetermined communication protocol between the client terminal 3, the host system 6, the dispensing device 7, etc. via the communication network N1. .

The display unit 24 is a display means such as a liquid crystal display or an organic EL display that displays various information according to control instructions from the control unit 21. The operation unit 25 is an operation means such as a keyboard, a mouse (pointing device), a touch panel, etc. that is operated by the user to input various information to the server 2.

The drive device 26 is capable of reading a dispensing management program from a computer-readable recording medium 27 in which a dispensing management program for causing the control unit 21 to execute a medication counter support process (see FIG. 5), which will be described later, is recorded. It is. The recording medium 27 is a CD, DVD, BD, USB memory, or the like. In the server 2, the control unit 21 installs the prescription management program read from the recording medium 27 by the drive device 26 into the data storage unit 22.

The control unit 21 includes control devices such as a CPU, ROM, RAM, and EEPROM (registered trademark, hereinafter the same). The CPU is a processor that executes various types of arithmetic processing. The ROM is a non-volatile storage section in which information such as control programs for causing the CPU to execute various processes is stored in advance. The RAM is a volatile storage section, and the EEPROM is a nonvolatile storage section. The RAM and the EEPROM are used as temporary storage memory (work area) for various processes executed by the CPU. The control unit 21 uses the CPU to execute various processes according to various control programs stored in the ROM, the EEPROM, or the data storage unit 22 in advance.

The data storage section 22 is a nonvolatile storage means such as a hard disk or SSD that stores various application programs and various data executed by the control section 21. Specifically, the data storage unit 22 stores the dispensing management program.

The data storage unit 22 also stores various databases such as a drug master, a patient master, a pharmacist master, a prescription classification master, a clinical department master, and a ward master. For example, the drug master includes drug code, drug name, JAN code (or RSS), drug bottle code, category (dosage form: powder, tablet, solution, topical drug, etc.), specific gravity, drug type (regular drug, Contains information such as poisonous drugs, narcotics, powerful drugs, antipsychotics, therapeutic drugs, etc.), combination changes, excipient drugs, and precautions. Further, the patient master includes information such as the patient ID, name, gender, age, medical history, family information, medical department, ward, and room of each patient.

Further, the data storage section 22 includes a prescription data storage section 221 and a management data storage section 222. The control unit 21 stores prescription data acquired from the host system 6 in the prescription data storage unit 221, and stores prescription management information D1 regarding the progress of dispensing work based on each of the prescription data in the management data storage unit 222.

Here, FIG. 2 is a diagram showing an example of the prescription management information D1. As shown in FIG. 2, the prescription management information D1 includes "patient ID", "voucher number", "order number", "prescription classification", "barcode information", "prescription issue" among the prescription data. Information such as "day" is stored. In addition, the prescription management information D1 includes information indicating that the dispensing based on the prescription data has been completed and the date and time, and information indicating that the drug dispensed based on the prescription data has been handed to the patient. "Medication completion date and time" is also recorded as information indicating the date and time. In this embodiment, the prescription data and the prescription management information D1 are separate information, but in other embodiments, the prescription management information D1 may be treated as part of the prescription data. good.

By the way, if the patient does not come to the medication counter to pick up the medicine on the day the prescription data is issued, the medicine will be stored at the medical institution as a leftover medicine that was not given to the patient. Note that it is desirable that the leftover medication be handed over to the patient the next time he/she comes to the medication counter. However, there is a problem in that the person in charge of the medication counter cannot easily know whether there is any leftover medication for each patient, resulting in poor operational efficiency at the medication counter. On the other hand, in the dispensing management system 1 according to the present embodiment, it is possible to easily determine whether there are any remaining medicines for a patient.

Specifically, as shown in FIG. 1, the control unit 21 of the server 2 includes an acceptance processing unit 211, a selection processing unit 212, a display processing unit 213, an issuance processing unit 214, a print processing unit 215, and the like. Note that the control unit 21 functions as various processing units by executing various processes according to the dispensing management program stored in the data storage unit 22. Further, the functions of the various processing units described above may be realized by the server 2 and the client terminal 3 working together in the dispensing management system 1. Note that the various processing units described above may be constituted by individual electronic circuits.

The reception processing unit 211 receives processed input of medicine delivery related to prescription data. For example, if the code information read from the medicine bag by the barcode reader 36 and the code information read by the barcode reader 36 from the exchange ticket indicate the same prescription data, the reception processing unit 211 may process the prescription data. It is determined that the processed input has been accepted. Note that when the code information printed on the drug bag and the exchange ticket are the same, the reception processing unit 211 uses the code information to indicate that the same code information is read twice by the barcode reader 36 in succession. may be accepted as a processed operation for the prescription data corresponding to.

The selection processing unit 212 selects the prescription data to be processed. Specifically, the selection processing unit 212 selects the prescription data indicated by the exchange barcode D3 as a processing target when the exchange barcode D3, which will be described later, is read from the exchange ticket by the barcode reader 36. Further, when the selection processing unit 212 receives an operation for selecting the prescription data through a predetermined user operation on the operation unit 35, the selection processing unit 212 may select the prescription data as a processing target.

The display processing unit 213 displays information regarding prescription data for which the patient is the same as the prescription data selected by the selection processing unit 212 and for which the processed input has not been accepted by the reception processing unit 211. The first prescription data issued within the specific period and the second prescription data issued outside the specific period are displayed in a distinguishable manner. Specifically, the display processing unit 213 uses the client terminal to display display data for displaying first prescription data whose issue date is within the specific period and second prescription data whose issue date is outside the specific period in a distinguishable manner. 3B, it is displayed on the display section 34 of the client terminal 3B. In the present embodiment, an example will be described in which the specific period is the day on which display by the display processing unit 213 is executed. Note that hereinafter, the day on which display by the display processing unit 213 is performed may be simply referred to as "the current day."

The issue processing unit 214 issues code information that can identify the prescription data. Specifically, the issue processing unit 214 issues code information including the prescription issue date and voucher number corresponding to the prescription data. Note that the code information is not limited to this, and may be other information such as a prescription ID and a patient ID corresponding to the prescription data, as long as the code information can identify the prescription data.

The print processing unit 215 prints a label containing information regarding the prescription data when the reception processing unit 211 receives processed input for all of the prescription data issued within the specific period for one patient. . In other words, if the reception processing unit 211 has not received processed input for all of the prescription data issued within the specific period for one patient, the print processing unit 215 prints information regarding the prescription data. Do not print labels that include Note that the label is used for the purpose of being attached to a notebook, also called a medicine notebook, which is used to manage a patient's medication history and the like. In addition, the print processing unit 215 determines whether the prescription data is for a medicine notebook that requires the label to be issued at a medication counter, and prints the label only if the prescription data is for a medicine notebook to be issued. You may.

[Dispensing management processing]
Hereinafter, an example of the procedure of the dispensing management process executed by the control unit 21 of the server 2 will be described with reference to FIG. 3.

<Step S11>
In step S11, the control unit 21 determines whether prescription data has been acquired from the host system 6. Here, if it is determined that the prescription data has been acquired (S11: Yes)
Then, the process moves to step S12, and if it is determined that the prescription data has not been acquired (S11: No), the process moves to step S14.

<Step S12>
In step S12, the control unit 21 stores the prescription data determined to have been acquired in the step S11 in the prescription data storage unit 221, generates prescription management information D1 corresponding to the prescription data, and stores the management data. 222. Note that, at this point, no information is recorded on the dispensing completion date and time and the medication completion date and time in the prescription management information D1.

<Step S13>
In step S13, the control unit 21 executes a process of issuing a prescription and the medicine bag in which code information that can identify the prescription data determined to have been obtained in step S11 is written. Note that this processing is executed by the issuing processing unit 214 of the control unit 21.

Specifically, the control unit 21 generates print data for the prescription and the drug bag in which code information corresponding to the prescription data is written, and sends the print data to the printer 8 installed in the dispensing room or the like. 8 to print the prescription and the medicine bag. Note that the control unit 21 may transmit the print data to the client terminal 3A in the dispensing room, and cause the client terminal 3A to execute processing for printing the print data.

Here, FIG. 4 is a diagram showing an example of the printing result of the medicine bag in step S13. As shown in FIG. 4, information such as the patient's name, usage, dose, and prescription medicine is printed on the medicine bag. Further, the medicine bag includes a medicine bag code that is code information that can identify prescription data corresponding to the medicine contained in the medicine bag, and that includes information indicating that the code information is printed on the medicine bag. A medicine bag barcode D2 is printed as information. Specifically, the medicine bag barcode D2 includes the prescription issue date and voucher number of the prescription data. For example, the medicine bag barcode D2 includes an 8-digit number (for example, 20180101) indicating the prescription issue date of the prescription data, a 4-digit number (for example, 0001) indicating the exchange ticket number, and a 1-digit number indicating that it is a medicine bag. It is conceivable that the information includes a character (for example, "Y"). In addition, the medicine bag barcode D2 includes the issuer in place of the characters indicating that it is a medicine bag, as information to distinguish between the medicine bag barcode D2 and the exchange barcode D3, which will be described later and is printed on the exchange ticket. It may also include information indicating.

<Step S14>
In step S14, the control unit 21 determines whether dispensing based on the prescription data has been completed. Here, if it is determined that the dispensing is completed (S14: Yes), the process moves to step S15, and if it is determined that the dispensing is not completed (S14: No), the process moves to step S16. .

For example, when the control unit 21 receives a notification of completion of dispensing based on the prescription data from the dispensing device 7, it may be considered that the control unit 21 determines that dispensing based on the prescription data has been completed. In addition, for prescription data that cannot be automatically dispensed by the dispensing device 7, the dispensing is done manually by the pharmacist, so the notification of completion of dispensing based on the prescription data is sent according to the user's operation on the client terminal 3A. It is possible that it will be sent. In this case, the control unit 21 determines that the dispensing based on the prescription data has been completed in response to receiving the completion notification from the client terminal 3A. Note that the completion notification may be sent in response to a user operation on the client terminal 3A when the drug after dispensing is inspected.

<Step S15>
In step S15, the control unit 21 updates the prescription management information D1 corresponding to the prescription data for which it is determined that dispensing has been completed in step S14. Specifically, the control unit 21 records the current date and time of dispensing completion date and time in the prescription management information D1 corresponding to the prescription data. Thereby, the control unit 21 can determine whether or not dispensing has been completed for each of the prescription data based on the prescription management information D1.

<Step S16>
In step S16, the control unit 21 determines whether the patient has completed the payment. Here, if it is determined that the checkout is completed (S16: Yes), the process moves to step S17, and if it is determined that the checkout is not completed (S16: No), the process moves to step S18. .

<Step S17>
In step S17, the control unit 21 executes a process of issuing a voucher including code information that can identify the prescription data of the patient whose payment has been determined to have been completed in step S16. Such processing is executed by the issuance processing unit 214 of the control unit 21. In addition, if there is an unprinted exchange ticket for the patient for whom it is determined that the payment has been completed in step S16, the control unit 21 prints the exchange ticket for the patient whose payment has been determined to have been completed. If the voucher does not exist, the voucher will not be printed. For example, a voucher will not be printed for a patient for whom the prescription data has not been issued.

Specifically, the control unit 21 generates print data of a voucher including code information corresponding to the prescription data, and sends it to the printer 8 provided at the accounting counter, so that the printer 8 can be used to exchange the voucher. Print the ticket. Note that the control unit 21 may transmit the print data to the client terminal 3C at the accounting counter, and cause the client terminal 3C to execute processing for printing the print data.

Here, FIG. 5 is a diagram showing an example of the printing result of the exchange ticket in step S13. As shown in FIG. 5, information such as the patient's name and the voucher number is printed on the voucher. Further, an exchange barcode D3 is printed on the exchange ticket as exchange code information that can identify the prescription data corresponding to the exchange ticket. Specifically, the exchange barcode D3 includes the prescription issue date and exchange ticket number of the prescription data. For example, the exchange barcode D3 may be information including an 8-digit number (for example, 20180101) indicating the prescription issue of the prescription data and a 4-digit number (for example, 0001) of the exchange ticket number. That is, the exchange barcode D3 does not contain any characters (for example, "Y") indicating that it is a medicine bag included in the medicine bag barcode D2, indicating that the exchange barcode D3 is the code information printed on the exchange ticket. shows. Note that the exchange barcode D3 may include characters indicating that it is an exchange ticket as information for distinguishing between the exchange barcode D3 and the drug bag barcode D2, and the issuer of the exchange barcode D3. may also include information indicating.

<Step S18>
In step S18, the control unit 21 determines whether the medicine dispensed based on the prescription data can be administered at the medication counter. For example, when the drug bag barcode D2 is read from the medicine bag using the barcode reader 36 on the client terminal 3B provided at the medication counter, the control unit 21 determines that it is possible to administer medication at the medication counter. is possible. Here, if it is determined that the medicine bag has arrived at the medication counter (S18: Yes), the process moves to step S19, and if it is not determined that the medicine bag has arrived at the medication window (S18: No), the process proceeds to step S19. is returned to step S11.

<Step S19>
In step S19, the control unit 21 notifies the patient of the voucher number corresponding to the prescription data for which it was determined in step S18 that the medicine bag had arrived. Specifically, the control unit 21 notifies the patient of the voucher number using a display device, an audio playback device, or the like disposed at the patient's waiting area. As a result, the patient who has the voucher number corresponding to the notified voucher number receives the medicine at the medication counter.

[Medication counter support processing]
Next, an example of the procedure of the medication window support process executed by the control unit 21 of the server 2 will be described with reference to FIGS. 6A and 6B. Specifically, the control unit 21 executes the medication window support process when accessed from the client terminal 3B located at the medication window. In another embodiment, the medication window support process may be executed when the client terminal 3 is accessed from the client terminal 3 while a user previously set as the person in charge of the medication window is logged in to the client terminal 3. Note that the login process may be performed by the control unit 21 of the server 2.

By the way, in this embodiment, the case where the dispensing management system 1 is a server-client system that executes the medication counter support process by executing various data communications between the server 2 and the client terminal 3 is taken as an example. List and explain. That is, various operations such as inputting, selecting, and reading various information in the medication counter support process are performed using the operation unit 35 or barcode reader 36 of the client terminal 3B, and the details of the operations are transmitted from the control unit 31. By being transmitted to the control unit 21, various operations are accepted by the control unit 21. Furthermore, the content of display of various information in the medication window support process is transmitted from the control unit 21 to the control unit 31, so that the control unit 31 displays the information on the display unit 34. On the other hand, as another embodiment, it is also conceivable that the control unit 31 of the client terminal 3 executes the medication window support process while acquiring necessary information from the server 2. In this case, the client terminal 3 can also be regarded as a dispensing management system according to the present invention.

<Step S30>
In step S30, the control unit 21 displays a medication window screen P1 used to support work at the medication window. Specifically, the control unit 21 causes the medication window screen P1 to be displayed on the display unit 34 of the client terminal 3B by transmitting display data corresponding to the medication window screen P1 to the client terminal 3B.

Here, FIG. 7 is a diagram showing an example of the medication window screen P1. As shown in FIG. 7, the control unit 21 displays display areas A11, A12, A13, A21, A22, operation keys K11, K12, K13, etc. on the medication window screen P1. Note that, as shown in FIG. 7, various display items are blank on the medication window screen P1 displayed in step S30.

Display area A11 displays an input field in which a voucher number and patient ID can be entered. In the display area A12, the patient name corresponding to the patient ID displayed in the display area A11 is displayed. In the display area A13, date information of the execution day of the medication counter support process is displayed.

Further, the control unit 21 can input the voucher number and the patient ID into the input fields of the display area A11, respectively, in accordance with the operation of the operation unit 35 of the client terminal 3B. In addition, when the exchange barcode D3 is read from the exchange ticket by the barcode reader 36 of the client terminal 3B, the control unit 21 also controls the exchange ticket number corresponding to the prescription data indicated by the exchange barcode D3, and the exchange ticket number corresponding to the prescription data indicated by the exchange barcode D3. Patient IDs corresponding to the numbers can be input into the input fields. Furthermore, when the barcode D2 is read from the drug bag by the barcode reader 36 of the client terminal 3B, the control unit 21 controls the exchange ticket number corresponding to the prescription data indicated by the barcode D2, and the exchange ticket number corresponding to the prescription data indicated by the barcode D2. Each patient ID can be entered in the input field.

The display area A21 and the display area A22 are displayed side by side on the medication window screen P1. Display area A21 displays first prescription data whose prescription issue date is the current day among the prescription data issued for the patients displayed in display areas A11 and A12. Further, in the display area A22, second prescription data whose prescription issue date is the previous day or earlier is displayed, among the prescription data issued for the patients displayed in the display areas A11 and A12. Note that the display example of the display areas A21 and A22 (see FIG. 13) will be explained together with the subsequent step S36.

Further, the control unit 21 is capable of accepting operations of the operation keys K11, K12, and K13 performed by the user on the operation unit 35, and executing corresponding processing. Specifically, in response to the operation of the operation key K11, the control unit 21 executes a reception process of accepting a processed input for the prescription data selected as the processing target. In addition, in response to the operation of the operation key K12, the control unit 21 executes a cancellation process in which the prescription data to be processed is already in the processed state, by canceling the acceptance of the prescription data and making it into the unprocessed state. Specifically, the control unit 21 erases the medication completion date and time information recorded in the prescription management information D1 corresponding to the prescription data, thereby setting the prescription data in an unprocessed state. Further, the control unit 21 executes an interruption process of canceling the process of the prescription data to be processed and interrupting the process in response to the operation of the operation key K13. In addition, when the control unit 21 receives an operation for selecting prescription data in the display areas A21 and A22, the control unit 21 may select the prescription data as a processing target.

<Step S31>
In step S31, the control unit 21 determines whether the barcode reader 36 has read the code information of the exchange barcode D3 from the exchange ticket. Specifically, the control unit 21 determines that the code information includes the prescription issue date and the exchange ticket number, and also includes the information of the letter (Y) indicating that the code information is the code information of the medicine bag. If not, it is determined that the exchange barcode D3 has been read. Here, if it is determined that the code information has not been read from the voucher (S31: No), the process moves to step S32, and if it is determined that the code information has been read from the voucher (S31: (Yes), the process moves to step S34.

Further, the processing state of the prescription data includes, in addition to the processed state and the unprocessed state, a pre-delivered state in which the medicine corresponding to the prescription data has been previously delivered to the patient. For example, when a predetermined forward transfer operation regarding arbitrary prescription data is performed on the client terminal 3C, etc., the control unit 21 causes the prescription data to transition to the forward transfer completed state. Then, if the exchange barcode D3 read in step S31 corresponds to prescription data in a pre-delivered state in which the medicine has already been given to the patient, the control unit 21 determines whether the exchange barcode D3 corresponds to the prescription data in the pre-delivery state where the medicine has already been given to the patient. After displaying on the display unit 34 of the client terminal 3C that the medicine to be delivered has already been delivered and making a predetermined warning sound sound on the display unit 34, the process returns to step S31.

<Step S32>
In step S32, the control unit 21 determines whether the barcode reader 36 has read the code information of the medicine bag barcode D2 from the medicine bag. Specifically, the control unit 21 determines that the code information includes the prescription issue date and the exchange ticket number, and that the code information includes the letter (Y) indicating that the code information is the code information of the medicine bag. If the medicine bag barcode D2 is included, it is determined that the medicine bag barcode D2 has been read. Here, if it is determined that the code information has not been read from the medicine bag (S32: No), the process returns to the step S31, and if it is determined that the code information has been read from the medicine bag (S32: Yes). ), the process moves to step S33.

<Step S33>
In step S33, the control unit 21 notifies the user that the code information read by the barcode reader 36 has been read from the medicine bag by displaying it on the display unit 34.

<Step S34>
In step S34, the control unit 21 selects the prescription data corresponding to the exchange barcode D3 or medicine bag barcode D2 determined to have been read in step S31 or S32 as a processing target. Here, such processing is executed by the selection processing section 212 of the control section 21. In addition, as another embodiment, only when the exchange barcode D3 is read, the prescription data corresponding to the exchange barcode D3 is selected as the processing target, and only when the medicine bag barcode D2 is read, the prescription data corresponding to the exchange barcode D3 is selected as the processing target. It is also conceivable that the prescription data corresponding to the medicine bag barcode D2 is not selected as a processing target.

<Step S35>
In step S35, the control unit 21 performs a search process to search for prescription data having the same patient as the prescription data selected in step S34, among the prescription data stored in the prescription data storage unit 221 of the data storage unit 22. Execute. The search targets in the search process include prescription data whose prescription issue date is the current day, and prescription data whose prescription issue date is before the current day. Furthermore, the search targets include unprocessed prescription data for which processed input has not yet been accepted by the reception processing unit 211, and processed prescription data for which processed input has already been accepted.

<Step S36>
In step S36, the control unit 21 executes processing for displaying the search results obtained in step S35. Here, the control unit 21 provides information regarding prescription data for which the patient is the same as the prescription data selected by the selection processing unit 212 and whose processed input has not been accepted by the reception processing unit 211 as the search result. are displayed in such a manner that the first prescription data issued on that day and the second prescription data issued before that day can be distinguished. Specifically, the control unit 21 causes the search result to be displayed on the medication window screen P1 of the display unit 34 of the client terminal 3B by transmitting display data for displaying the search result to the client terminal 3B. Here, FIG. 8 is a diagram showing an example of the medication window screen P1 on which the search results are displayed.

As shown in FIG. 8, display areas A11 and A12 display the exchange ticket number, patient ID, and patient name of the prescription data corresponding to the exchange barcode D3 or medicine bag barcode D2 read in step S31 or S32. is displayed.

As shown in FIG. 8, the display areas A21 and A22 also display prescription data for which processed input has not yet been accepted among the prescription data issued for the patients displayed in the display areas A11 and A12. is displayed. That is, a list of unissued prescription data for which the patient has not received the medicine is displayed. In particular, in the display area A21, among the prescription data issued for the patients displayed in the display areas A11 and A12, first prescription data whose prescription issue date is the current day is displayed. On the other hand, in the display area A22, among the prescription data issued for the patients displayed in the display areas A11 and A12, second prescription data whose prescription issue date is earlier than the current day is displayed. Further, in the display areas A21 and A22, the background color of the prescription data is displayed in a predetermined specific color such as blue so that the prescription data currently selected as the processing target can be identified, or , characters, symbols, marks, etc. indicating that the prescription data is selected are displayed in association with the prescription data. In addition, in the display areas A21 and A22, the total number of unissued prescription data is displayed at the top of the list of unissued prescription data, and in the display areas A21 and A22, the display of the total number is fixed. At the same time, it is possible to change the prescription data to be displayed by scrolling the display. In addition, in the display area A22, among unissued prescription data for which medicine bags are stored as leftover medicines, prescription data that has exceeded a predetermined storage period (for example, 3 months or 6 months) from the prescription issue date is displayed. is not displayed. The predetermined storage period may be a fixed period, or may be presettable for each user or patient.

In this way, on the medication window screen P1, for prescription data for which processed input has not yet been accepted for the patient corresponding to the prescription data to be processed, information regarding the first prescription data issued on that day is displayed in the display area A21. At the same time, information regarding the second prescription data issued before the current day is displayed in the display area A22. Thereby, the user can easily distinguish and confirm the two depending on the display position. Furthermore, for patients who come to pick up medicine based on prescription data issued on the same day, it is possible to easily determine whether there are any leftover medicines that were not delivered in the past. Note that the method for displaying the first prescription data and the second prescription data in a distinguishable manner on the medication window screen P1 is not limited to the method described here, but may be any one of the font color, background color, size, display position, etc. One or more combinations may be displayed in different display modes.

Moreover, as another embodiment, prescription data for which processed input has already been accepted may be further displayed on the medication window screen P1 for a patient corresponding to the prescription data to be processed. Furthermore, it may be possible to switch between displaying and displaying prescription data for which processed input has already been accepted. Here, FIG. 9 is a diagram showing another example of the medication window screen P1. As shown in FIG. 9, in the display areas A21 and A22, the first prescription data and the second prescription data are divided into data for which processed input has not yet been accepted and data for which processed input has already been accepted. It is conceivable that the prescription data may be further displayed in a distinguishable manner. For example, in each of the display areas A21 and A22, prescription data for which processed input has not yet been accepted is displayed with a white background, and prescription data for which processed input has already been accepted is displayed with a gray background. . Here, in each of the display areas A21 and A22, the background color of the prescription data is displayed in a predetermined specific color such as blue so that the prescription data currently selected as the processing target can be identified. , or characters, symbols, marks, etc. indicating that the prescription data is selected are displayed in association with the prescription data. That is, in each of the display areas A21 and A22, prescription data for which processed input has not yet been accepted and which is currently selected as a processing target, and other prescription data for which processed input has not been accepted yet. , and prescription data for which processed input has already been accepted are displayed in a distinguishable manner. Note that the method of displaying the presence or absence of processed input in a distinguishable manner on the medication window screen P1 is not limited to this, and for example, different display modes may be used for any one or a combination of font color, background color, size, display position, etc. It may be displayed as . In this case as well, in the display areas A21 and A22, the total number of unissued prescription data is displayed at the top of the list of unissued prescription data, and in the display areas A21 and A22, the total number of unissued prescription data is displayed. While the display is fixed, it is possible to change the prescription data to be displayed by scrolling. In addition, in the display area A22, among unissued prescription data for which medicine bags are stored as leftover medicines, prescription data that has exceeded a predetermined storage period that is set in advance is not displayed. The predetermined storage period may be a fixed period, or may be presettable for each user or patient.

Furthermore, as another embodiment, for unprocessed prescription data for which processed input has not been accepted among the prescription data displayed on the medication window screen P1, whether or not dispensing for the prescription data has been completed is determined. It is conceivable that the progress status, such as whether or not the drug has arrived at the medication counter, is displayed based on the prescription management information D1.

<Step S37>
In step S37, the control unit 21 determines whether the exchange barcode D3 has been read. Here, if it is determined that the exchange barcode D3 has been read (S37: Yes), the process moves to step S38, and if it is determined that the exchange barcode D3 has not been read (S37: No), the process The process moves to step S39.

<Step S38>
In step S38, the control unit 21 updates the prescription data selected as the processing target. Specifically, the control unit 21 selects, as a processing target, the prescription data corresponding to the exchange barcode D3 determined to have been read in step S37. In addition, the control unit 21 causes the prescription data to be processed after the update in step S38 to be identifiably displayed in the display areas A21 and A22 of the medication window screen P1.

<Step S39>
In step S39, the control unit 21 determines whether the medicine bag barcode D2 has been read. Here, if it is determined that the medicine bag barcode D2 has been read (S39: Yes), the process moves to step S40, and if it is determined that the medicine bag barcode D2 has not been read (S39: No), the process The process moves to step S391.

<Step S391>
In step S391, the control unit 21 determines whether a manual operation has been performed to receive processed input for prescription data to be processed. Specifically, the control unit 21 determines that the manual operation has been performed when the operation key K11 displayed on the medication window screen P1 is operated by the operation unit 35. Here, if it is determined that the manual operation has been performed (S391: Yes), the process moves to step S42, and if it is determined that the manual operation has not been performed (S391: No), the process moves to step S42. The process returns to step S37.

<Step S40>
In step S40, the control unit 21 performs a matching process to determine whether or not the prescription data currently being processed matches the prescription data corresponding to the drug bag barcode D2 determined to have been read in step S39. Execute.

In addition, in this embodiment, a case will be described as an example in which a medicine bag barcode D2 and an exchange barcode D3 that are different from each other are printed on the medicine bag and the exchange ticket, respectively. On the other hand, in another embodiment, the same code information is printed on the medicine bag and the exchange ticket, and the same code information is read twice in succession in the verification process in step S40 of the medication counter support process. It is also conceivable that a match may be determined if the

<Step S41>
In step S41, the control unit 21 determines whether or not the matching result in step S40 is a match. Here, if it is determined that the comparison result is a match (S41: Yes), the process moves to step 42. On the other hand, if the control unit 21 determines that the matching results do not match (S41: No), the control unit 21 causes the display unit 34 to display an error message or emit an error notification sound, and then resumes the process described above. Return to step S37. That is, in steps S40 to S41, the exchange ticket held by the patient is compared with the medicine bag to be given to the patient, thereby preventing the wrong medicine from being given to the patient.

<Step S42>
In step S42, the control unit 21 updates the processing state of the prescription data to be processed. Specifically, the control unit 21 records the current date and time in the “medication completion date and time” in the prescription management information D1 corresponding to the prescription data stored in the prescription data storage unit 221, thereby indicating that the prescription data has been processed. Make it.

<Step S43>
In step S43, the control unit 21 determines whether there is unprocessed prescription data for the current day among other prescription data for the same patient as the prescription data to be processed. Specifically, the control unit 21 selects other prescription data, among the prescription data stored in the prescription data storage unit 221, for which the patient is the same as the prescription data to be processed and the prescription issue date is the same day, It is determined whether there is prescription data whose processing state is an unprocessed state. Here, if it is determined that there is unprocessed prescription data for the current day (S43: Yes), a message such as "There is unprocessed prescription data" is displayed, and then the process returns to step S35. . On the other hand, if it is determined that there is no unprocessed prescription data for the current day (S43: No), a message such as "Prescription for the current day has been completed" is displayed, and then the process moves to step S44.

<Step S44>
In step S44, the control unit 21 executes a printing process to print the label as necessary. Note that this processing is executed by the print processing section 215 of the control section 21. For example, the control unit 21 determines whether the prescription data to be processed includes issuance target information indicating that the prescription data is a medicine notebook issuance target, and determines whether the issuance target information is included. In this case, the label corresponding to the one or more prescription data for which the matching result was determined in step S41 is printed. On the other hand, if no issuance target information indicating that the prescription data is a medicine notebook issuance target is recorded, the label is not printed. Note that the control unit 21 may print the label not only for the prescription data whose issue date is the current day but also for the prescription data whose issue date is before the current day.

<Step S45>
In step S45, the control unit 21 determines whether there is unprocessed prescription data whose prescription issue date is earlier than the current day among other prescription data whose patient is the same as the prescription data to be processed. do. Specifically, the control unit 21 selects other prescription data stored in the prescription data storage unit 221 for which the patient is the same as the prescription data to be processed and the prescription issue date is earlier than the current day. Then, it is determined whether there is prescription data whose processing status is unprocessed. Here, if it is determined that there is unprocessed prescription data (S45: Yes), a message such as "There is unprocessed prescription data" is displayed, and then the process returns to step S35. On the other hand, if it is determined that there is no unprocessed prescription data (S45: No), a message such as "There is no unprocessed prescription data" is displayed, and then the selection state of the prescription data to be processed is canceled. Then, the process returns to step S30.

As explained above, according to the dispensing management system 1 according to the present embodiment, when a patient comes to the medication counter to pick up a medicine, the person in charge of the medication counter will tell the patient that the patient has forgotten to pick up the medicine in the past. The presence or absence of leftover medicine can be easily determined. In particular, at a medication counter, the medicine bags for medicines corresponding to prescription data issued on the day and the medicine bags for leftover medicines corresponding to prescription data issued up to the previous day may be stored in different cases. Even in this case, in the dispensing management system 1, when a patient comes to pick up medicine, prescription data issued on that day and prescription data issued up to the previous day are displayed in a distinguishable manner. Therefore, it is possible to easily determine whether the medicine that the patient came to pick up is a leftover medicine or not, and the patient does not have to worry about the storage location where the medicine should be taken out, thereby improving the efficiency of work at the medication counter.

In addition, when the control unit 21 receives a storage period exceeded search request from the client terminal 3C in response to a user operation at an arbitrary timing, the control unit 21 determines which prescription data is unprocessed among the prescription data stored in the prescription data storage unit 221. It has a function to search for prescription data that has exceeded a predetermined storage period from the prescription issue date. Note that the predetermined storage period may be a fixed period, or may be presettable for each user or patient. Then, the control unit 21 causes the display unit 34 of the client terminal 3C to display excess list data showing a list of prescription data that has exceeded the predetermined storage period. Thereafter, when the control unit 21 receives a deletion request for one or more of the prescription data selected from the excess list data in response to a user operation, the control unit 21 removes the prescription data from the display target in the display area A22. Execute the process to exclude. For example, the control unit 21 may store the prescription data that is the target of the deletion request in association with the non-display target information in the prescription data storage unit 221, and exclude the prescription data from the display targets in the display area A22. Conceivable. Further, the control unit 21 may delete the prescription data that is the subject of the deletion request from the prescription data storage unit 221, thereby excluding it from the display target in the display area A22. Furthermore, when the control unit 21 receives a request to delete the prescription data, the control unit 21 may exclude the prescription data from the display target in the display area A22 by marking the prescription data as processed. Note that the control unit 21 may automatically process the prescription data for which the predetermined storage period has exceeded as a subject of a deletion request. It is also conceivable that the control unit 21 prints out a list of the prescription data that is the subject of the deletion request using the printer 8, or sends it to a predetermined destination.

1 Dispensing management system 2 Server 21 Control section 22 Data storage section 221 Prescription data storage section 222 Management data storage section 3 Client terminal 31 Control section 32 Data storage section 36 Barcode reader 6 Host system 7 Dispensing device 8 Printer

Claims (9)

a selection processing unit that selects prescription data to be processed;
a reception processing unit that receives processed input of drug delivery related to prescription data;
Information regarding prescription data for which the patient is the same as the prescription data selected by the selection processing section and for which the processed input has not been accepted by the reception processing section is issued within a predetermined specific period. a display processing unit that displays the first prescription data issued outside the specific period and the second prescription data issued outside the specific period in a distinguishable manner;
A dispensing management system equipped with The display processing unit displays information regarding prescription data for which the patient is the same as the prescription data selected by the selection processing unit, and for which the processed input has already been accepted by the reception processing unit, to the first further displaying the prescription data and the second prescription data in a distinguishable manner;
The dispensing management system according to claim 1. The display processing unit displays prescription data for which the processed input has not been accepted by the reception processing unit, and prescription data for which the processed input has already been accepted by the reception processing unit, in a manner that is distinguishable. ,
The dispensing management system according to claim 2. the specific period is the day on which the display by the display processing unit is executed;
The dispensing management system according to any one of claims 1 to 3. a print processing unit that prints a label containing information regarding the prescription data when the reception processing unit accepts the processed input for all of the prescription data issued within the specific period for one patient; ,
The dispensing management system according to any one of claims 1 to 4. comprising an issuance processing unit that issues printed matter including code information that can identify the prescription data;
The selection processing unit receives selection of the prescription data corresponding to the code information when the code information is read by the code reading unit.
The dispensing management system according to any one of claims 1 to 5. The reception processing unit reads exchange code information printed on a medicine exchange ticket corresponding to the prescription data and medicine bag code information printed on a medicine bag containing a medicine corresponding to the prescription data by a code reading unit. accepting a processed input of the prescription data corresponding to the code information when the code information is read continuously;
The dispensing management system according to claim 6. The second prescription data is data corresponding to leftover medicines that were not delivered to the patient on the date of issue of the second prescription data.
The dispensing management system according to claims 1 to 7. a step of selecting prescription data to be processed;
accepting processed drug delivery input regarding prescription data;
Information regarding prescription data for which the patient is the same as the selected prescription data and for which the processed input has not been accepted is divided into the first prescription data issued within a predetermined specific period and the first prescription data issued outside the specific period. displaying the second prescription data issued in a distinguishable manner;
A dispensing management program that allows a computer to execute