JP4330238B2 - Dispensing control device and dispensing control method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention relates to a dispensing control device that operates and controls each dispensing device used in dispensing operations such as a medicine bag printing machine and a medicine packaging machine used in medical facilities such as hospitals and dispensing pharmacies based on prescription data.And dispensing control methodIn particular, a dispensing control device that can be connected to a host computer that transmits prescription data to an external deviceAnd dispensing control methodIt is about.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, there are some dispensing devices such as medicine bag printers that are driven and controlled by receiving prescription data from a host computer.
[0003]
Japanese Examined Patent Publication No. 4-57348 discloses a dispensing control device that assigns data from a host computer to an input device of a dispensing machine suitable for the type of dispensing.
[0004]
Japanese Examined Patent Publication No. 6-9600 describes a prescription dispensing system that generates dispensing data based on a prescription, operates a dispensing device, and displays the execution status of the dispensing data.
[0005]
Japanese Examined Patent Publication No. 6-9601 describes a prescription dispensing medicine bag creation system that generates dispensing data based on a prescription, operates a dispensing device, and generates display contents of the medicine bag based on the dispensing data.
[0006]
Japanese Examined Patent Publication No. 7-71575 discloses a dispensing control device that operates a dispensing machine using data from a host computer to create a medicine bag.
[0007]
Japanese Examined Patent Publication No. 7-71576 describes a dispensing control device that operates a dispensing machine using data from a host computer to notify the progress of a medication operation.
[0008]
Japanese Examined Patent Publication No. 8-124 describes a dispensing control apparatus that operates data on a dispensing machine using data from a host computer and generates management information for the entire dispensing operation.
[0009]
Japanese Patent No. 2623010 describes a medicine packaging device that operates a plurality of medicine packaging machines based on prescription data and monitors the operation status of the medicine packaging machine.
[0010]
Japanese Patent No. 2691859 describes a dispensing control method that accepts data relating to medicines from a host computer, classifies them according to the kind of dispensing, and assigns them to a suitable dispensing machine.
[0011]
[Problems to be solved by the invention]
However, in any of the control devices described above, the control method differs depending on the type of dispensing device, and it is necessary to design and manufacture for each facility where these control devices are installed. In addition, only the dispensing device can perform medicine bag printing, reissuance of medicine packaging, and operation cancellation due to defective printing or packaging failure. For this reason, the pharmacist must move to each dispensing device each time reissuance or cancellation of operation occurs.
[0012]
In addition, even if it is necessary to cancel the prescription or change the contents due to an input error or instruction change, if the communication is made after the dispensing, the medicine is already packaged and must be disposed of. .
[0013]
Moreover, the countermeasure when the dispensing device stops due to an error is insufficient. For example, Japanese Examined Patent Publication No. 4-57348 simply outputs the type of dispensing data that cannot be dispensed as a dispensing instruction. For this reason, operation commands that cannot be processed increase and stay, and dispensing may be delayed. In this case, in order to distribute the operation command to other dispensing devices, a complicated processing operation is required. This problem becomes more apparent as the number and type of dispensing devices increase.
[0014]
Further, even when it is necessary to reissue due to a defective printing of a medicine bag or a medicine packaging failure, the reissuing operation method differs depending on the type of dispensing device, so the operation is complicated.
[0015]
Also, when abnormal prescription data is received due to a problem on the host computer side, or when an abnormal situation occurs such as when the dispensing device fails and switches to manual dispensing, the dispensing device side resets or powers off. By cutting and re-inserting, it is necessary to cancel the execution of the dispensing, which requires a complicated processing operation and takes a considerable amount of time.
[0016]
Further, when dispensing for a specific patient is forgotten, or when reprinting medicine bag printing or medicine packaging, the patient's waiting time becomes extremely long.
[0017]
Then, this invention makes it a subject to provide the dispensing control apparatus which can carry out drive control by centralized management of the several dispensing apparatus easily by the same method based on prescription data.
[0018]
[Means for Solving the Problems]
  As a means for solving the above problems, the present invention provides:
  In a dispensing control device that drives and controls a plurality of dispensing devices to dispense the prescription based on the prescription data,
  Management target including each dispensing deviceIncluding “Prescription reception” used for receiving prescription data from the host computer and “Prescription audit input” used for auditing prescription dataDispensing execution management target setting fileA prescription file storing prescription data received from the host computer,A hard disk device for storing
Means for generating prescription reception management data and an execution process for prescription reception processing based on "prescription reception" of the dispensing execution management object setting file;
Means for generating prescription audit management data for managing execution of “prescription audit input” and an execution process for prescription audit input processing based on “prescription audit input” of the dispensing execution management object setting file; ,
Based on the management target of the dispensing execution management target setting file, means for generating execution management data for each dispensing device and an execution process for dispensing device execution processing;
  A central processing unit that drives and controls the corresponding dispensing device based on the management data and the execution process;
It is equipped with.
[0019]
  With this configuration, each dispensing device or the like can be managed using only a single dispensing execution management target setting file. Even when a new management target is added, it is only necessary to set the management target in the dispensing execution management target setting file.Also, prescription reception and prescription audit input can be managed and controlled in the same manner as the type of dispensing device.
[0021]
It should be noted that there are three possible combinations of prescription reception and prescription audit input: “Yes / Yes”, “Yes / No”, and “No / Yes”. “Yes / Yes” corresponds to the case where prescription data is received and a prescription audit is entered. “Yes / No” corresponds to the case where the prescription data is received and the prescription audit is not input and the dispensing device is operated directly. “None / Yes” corresponds to the case where prescription data is input in the prescription audit input.
[0022]
The data received from the host computer includes a host command,
The hard disk device stores the received host command as prescription reception management data in a prescription file,
The central processing unit uses the host command of the prescription reception management data stored in the prescription file.If a correction command is included, the corresponding pre-correction prescription data is searched and deleted and corrected prescription data is added. If the host command includes a deletion command, the corresponding execution management data It is preferable to set to cancel.
  Thereby, it is possible to delete or correct the dispensing operation automatically and immediately, and to reduce labor and drug loss due to wasteful dispensing.
[0023]
  The central processing unit displays an audit input of prescription data received from a host computer on a monitor screen, and an audit result input on the monitor screenIf there is no problem, proceed to the prescription audit management data “end” setting, operate each dispensing device by the processing of the dispensing device execution, and if there is a problem in the audit result, proceed to the prescription audit management data “cancel” setting and apply After setting the prescription file for prescription data to “Cancel audit NG”,You may make it transmit to a host computer. As a result, a system in which the pharmacist audits the contents of the prescription data received from the host computer and starts the medical accounting process according to the audit result (OK / NG) or requests the doctor to change the prescription is established on the host computer side. It can also be constructed.
[0024]
Moreover, it is preferable that the execution status of each management target stored in the dispensing execution management target setting file is displayed on the monitor screen by the central processing unit. As a result, it is possible to centrally manage each management object, that is, prescription reception, prescription audit input, and execution status in each dispensing device. Here, the execution status refers to the preprocessing data unprocessed / finished status, the waiting / running / ending status of operations in each dispensing device in the prescription data, the number of waiting operations in each dispensing device, It means the status of stopping, error status.
[0025]
The central processing unit monitors the execution time of each management object stored in the dispensing execution management object setting file, that is, prescription reception, prescription audit input, and each dispensing device, and notifies the user when a predetermined time is exceeded. And it is preferable at the point which can prevent that a patient's waiting time becomes long by carelessness etc.
[0026]
Further, when the central processing unit re-issues input from the input device, based on the re-issue input, when the operation is resumed for the corresponding management target stored in the dispensing execution management target setting file, each dispensing device It is preferable in that it can be commanded in a concentrated manner without moving up to. Reissued items include medicine bag printing, tablet packaging, powder packaging, and the like.
[0027]
In this case, the reissuing operation is preferably prioritized over the normal operation.
[0028]
In addition, when canceled by the input device by the central processing unit, the management data stored in the dispensing execution management target setting file, only if the execution status of the canceled prescription data is "waiting", The operation of the corresponding management target may be canceled. Further, when a stop or start input is performed by the input device, a stop or start signal may be transmitted to an execution process corresponding to the selected management target based on the stop or start input. As a result, the operation on each management target can be immediately canceled, stopped, or started by a simple operation.
[0029]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments according to the present invention will be described below with reference to the accompanying drawings.
[0030]
FIG. 1 shows a dispensing control device 1 according to the present embodiment and a dispensing device 2 that is driven and controlled by the control device 1.
[0031]
The dispensing control device 1 includes a central processing unit 3 (CPU), a hard disk device 4, a multi-channel communication unit 5, and a terminal device 6.
[0032]
Based on the prescription data, the dispensing control device 1 sends an operation command to each dispensing device 2 and receives a status from each dispensing device 2 to drive and control all the dispensing devices 2 to automatically perform dispensing operations. Make it progress. It should be noted that the status includes information on whether operation is possible, operation end, and error.
[0033]
The central processing unit 3 (CPU) stores a memory 7 (RAM) for storing various data, a control program 8 (ROM) for controlling the entire dispensing control device 1, and a battery to backup the date and time. A calendar clock 9 is incorporated. The memory 7 (RAM) is used as a prescription data memory for storing prescription data, an execution management data memory for storing execution management data, and other memories (working areas, variables, etc. on processing). The calendar clock 9 is used for date and time acquisition in various processes.
[0034]
The terminal device 6 includes a prescription inspection input terminal device 6a including a display, a keyboard, a mouse, and a notification buzzer, and a dispensing execution management terminal device 6b. These terminal devices 6 are used for data input of various files in addition to the specific uses of “prescription audit input” and “dispensing execution management”. Note that two of the terminal devices 6 may be integrated into one. In this case, various screens are displayed in multiple windows.
[0035]
The hard disk device 4 stores a dispensing execution management target setting file 10 for setting and storing a management target, a prescription file 11 for storing prescription data, and various master files for storing related information when inputting prescription data. ing. The hard disk device 4 can be a rewritable nonvolatile storage device such as a flash memory.
[0036]
As shown in FIG. 2, the dispensing execution management target setting file 10 stores each dispensing device 2 as a management target in addition to prescription reception and prescription audit input. Each management target is represented by a model, and an ID number is assigned to each model. Here, “prescription reception” is 1, “prescription inspection input” is 2, “medicine bag printing machine” is 3, “tablet packaging machine” is 4, and “powder packaging machine” is 5. When a new management target is added, an ID number is added to cope with it. When a plurality of the same model is included in the management target, the target is specified by assigning a machine number. The parameters are various kinds of information unique to each management target. In “prescription audit input”, 1 means “transmission of audit results / necessary”.
[0037]
Figure 3 is equipped with model 1 “Prescription reception”, model 2 “Prescription audit input”, model 3 “medicine bag printing machine”, model 4 “tablet packaging machine”, model 5 “powder packaging machine” It is an example of the storage content of the dispensing execution management object setting file 10 in this case.
[0038]
The prescription file 11 is a data file for storing prescription data, and the stored contents are as shown in FIG. The prescription data is written into the prescription file when the prescription data is received from the host computer 12 in the “prescription reception” process (FIG. 13) described later and in the “prescription audit input” process (FIG. 16) described later. This is done when new data is entered.
[0039]
In FIG. 4, prescription data No. indicates a serial number for identifying prescription data. The category indicates a category of prescription data. The contents of the classification are contents obtained by adding “Cancel audit NG” to the host command accompanying the prescription data. Here, “Normal” is 0, “Delete” is 1, “Correction” is 2, and “Audit NG Cancellation” is 3. The prescription data indicates the main body of the prescription data. It consists of various codes, and names such as department names and drug names are read from various master files and displayed.
[0040]
Various master files include drug master, patient master, usage master, medical department master, doctor master, ward master, and prescription category master, but the diagram is omitted because it is a simple file that stores codes and names. To do.
[0041]
The dispensing device 2 is mainly a medicine bag printing machine or a medicine packaging machine. In addition to this, a dispensing agent inspection machine for recording and confirming the normality of taking out of the medicine bottle and weighing in the dispensing of the powder, dispensing of the liquid medicine This includes equipment such as a liquid medicine dispensing inspection machine that audits liquid medicine and a liquid medicine packaging machine that divides and packs liquid medicine. The number of each dispensing device 2 varies from facility to facility, and one or more models or one or more devices are connected to the dispensing control device 1. An ID number is assigned to each model of the dispensing device 2, and a machine number is assigned to each machine for each model. These are used for identification and control. When a new model is added, an ID number is added. When the number of units increases, the unit number is increased. The dispensing control device 1 and the dispensing device 2 are connected by high-speed serial communication, but any connection / communication method such as general-purpose bus connection or network (LAN) connection may be used.
[0042]
A host computer 12 is used to receive prescription data from an external system. However, since the prescription data can be newly input only with the display, keyboard and mouse of the terminal device 6, the host computer 12 is not necessarily required. In addition, the prescription inspection input terminal device 6a may not be provided in a facility that does not audit the prescription data received on the dispensing control device 1 side in order to perform the prescription audit on the host computer 12 side. Further, the cooperation system requirement specifications required from the host computer 12 side for connecting and coordinating the host computer 12 and the dispensing control device 1 are different for each facility.
[0043]
The central processing unit 3 (CPU), the terminal device 6 (consisting of a display, a keyboard, a mouse, and a notification buzzer) and the hard disk device 4 may be personal computers.
[0044]
The hard disk device 4 is an independent file server device (CPU built-in), and the central processing device 3 (CPU) and the terminal device (CPU built-in) are connected as client terminals to the server device via a network (LAN). -A server configuration may be used.
[0045]
Further, for communication with each unit of the dispensing device 2, instead of using the multi-channel communication unit 5, the communication may be performed by connecting to the same network (LAN) including each unit of the dispensing device 2.
[0046]
Next, dispensing execution management processed by the control device 1 will be described with reference to the flowchart of FIG.
[0047]
Dispensing execution management processing is started by generating a process when the “Dispensing execution management” start button is clicked with the mouse on the menu screen (the screen is just a start button, not shown). Return to screen.)
[0048]
When the dispensing execution management process is started, first, execution management data and an execution process are sequentially generated for each set management target (unit) based on the dispensing execution management target setting file (FIG. 2) (step S1). It should be noted that immediately after the execution management data is generated, it is an empty initial state, and immediately after the execution process is generated, it is an idle state waiting for the occurrence of an event to be processed. A specific example of generation will be described later.
[0049]
Subsequently, a “dispensing execution status monitor” screen shown in FIG. 6 is displayed on the dispensing execution management terminal device 6b with the set management target as a column item (step S2). The “Dispensing execution status monitor” screen lists “Prescription reception”, “Prescription audit input”, and dispensing equipment 2 which are set as management targets based on the dispensing execution management target setting file (FIG. 2). The items include items, prescription data as line items, and execution status of each dispensing in column items such as “waiting”, “running”, “HH: MM (end time)”, and the like. “Prescription reception” does not have “waiting” and “running” states. In FIG. 6, "Prescription data No.", "Patient number", "Patient name", "Host command (prescription data category)", "Prescription (classification)", "Department of medicine", "Draw / Construction (exchange number / ward) ")" Is read from the prescription data in the prescription file (FIG. 4) and displayed. Names such as medical department names are read from various master files. In the “Drawer / Building” column, if the prescription category is outpatient, the exchange number (the number of the “replacement voucher”) is displayed, and if hospitalized, the ward name is displayed. The prescription data No. indicates a serial number for identifying prescription data. The host command indicates a command for the prescription data from the host computer 12, and includes “normal”, “delete”, and “correct”. Here, “Normal” is 0, “Delete” is 1, and “Correction” is 2. If there are too many management targets to fit within the horizontal width of the screen, a horizontal scroll bar can be displayed and column items can be displayed in a horizontal scroll. Further, immediately after the display of the screen, there is no prescription data that is a line item, which is empty. After step S2, the process proceeds by display / operation on the “Dispensing execution status monitor” screen (FIG. 6), and the dispensing device 2 and the like are centrally monitored.
[0050]
Next, the contents in the display range on the “Dispensing execution status monitor” screen (FIG. 6) are updated to the latest data contents (step S3), and the prescription reception, prescription audit input as column items, and the management data of each dispensing device The contents shown in FIGS. 7, 8, 9, 10, 11, and 12 are displayed on the screen.
[0051]
The prescription reception management data (FIG. 7) is data for managing the execution of “prescription reception”. In the prescription reception management data (FIG. 7), the prescription data No. indicates a serial number for identifying prescription data. The execution status indicates the execution status of “prescription reception” as a management target. Here, the end time of receiving the prescription data is set to HHMMSS (hour, minute and second are each in two-digit format), and “none” is set to 90000. The host command indicates a command for prescription data from the host computer 12. Here, “Normal” is 0, “Delete” is 1, and “Correction” is 2.
[0052]
The prescription audit management data (FIG. 8) is data for managing the execution of “prescription audit input”. In the prescription audit management data (FIG. 8), the prescription data No. indicates a serial number for identifying prescription data. The execution status indicates the execution status of the “prescription audit input” that is the management target. Here, the end time of the prescription audit input is HHMMSS, “waiting” is 600000, “in progress” is 700000, and “cancel” is 800000. The audit result indicates the audit result of the prescription data. Here, “OK” is 0 and “NG” is 1.
[0053]
The dispensing device execution management data (FIGS. 9 to 12) is data for managing the execution of the dispensing device 2. In the dispensing device execution management data (FIGS. 9 to 12), the prescription data No. indicates a serial number for identifying the prescription data. The execution status indicates the execution status of the dispensing device 2 to be managed. Here, the end time of execution is HHMMSS, “waiting” is 600000, “executing” is 700000, “cancel” is 800000, and “none” is 900000. The reissue flag indicates whether or not the dispensing device output needs to be reissued. Here, “ON” is 1 and “OFF” is 0. The contents of each execution management data are displayed in each column of the dispensing device 2 on the dispensing execution status monitor screen (FIG. 6).
[0054]
In addition, when prescription data (row data) is added to each management data, or when the execution status changes, the contents are immediately displayed on the “Dispensing execution status monitor” screen (FIG. 6). Update to the latest status. Even when the vertical / horizontal scroll bar is operated to change the display range, the contents are displayed accordingly. The new prescription data is displayed by scrolling up from the bottom line one after another unless the operator is performing any selection operation.
[0055]
At this time, “not” is displayed for unprocessed prescription data in which any dispensing process remains in the prescription data (row data), and “★” is displayed for prescription data that exceeds the arbitrarily set monitoring time. Display the mark. If this time is exceeded, the buzzer will sound. The monitoring start time is the end time of “prescription reception” or “prescription audit input”, which is the management target set first in the dispensing execution management target setting file (FIG. 2). Compare the current time and monitor the time.
[0056]
In the “cell” in the matrix of “column” such as “row” of prescription data and “prescription reception” and “prescription audit input”, each management data corresponding to “column” (FIGS. 7 to 12) Displays the "execution status" of line data. If there is no dispensing corresponding to “cell”, it is blank, and “waiting”, “running”, “HH: MM (end time)” or “cancel” is displayed.
[0057]
Here, it is determined whether or not the operation target has been selected by the operator (step S4). Prescription data “row” and “prescription reception”, “prescription audit input”, “cell” in matrix of “column” of each “dispensing device”, or column items “prescription reception” “prescription audit input” When each “dispensing device” is clicked with the mouse (in the “Dispensing execution status monitor” screen (FIG. 6), for example, the “09:05” cell in the prescription data No. “0007” row and the “medicine bag 1” column) Is clicked or the column item “medicine bag 1” is clicked), it is determined that the operation target has been selected, and the selected item is highlighted (step S5).
[0058]
When the “reissue” button is clicked with the mouse while the operation target is selected (step S6), the reissue flag of the execution management data is turned ON (step S7). Here, in the execution management data (FIGS. 9 to 12) of the dispensing device 2 corresponding to the selected “cell”, the “reissue flag” of the corresponding row data is set to “ON”. And it returns to step S3 and repeats from the update of the display of a dispensing execution condition.
[0059]
When the “cancel” button is clicked with the mouse (step S8), the execution management data is set to “cancel” (step S9). That is, only when the “execution status” of the corresponding row data in the prescription audit management data (FIG. 8) and the dispensing device execution management data (FIGS. 9 to 12) corresponding to the selected “cell” is “waiting”. “Cancel” is set (for example, when the “waiting” cell in the prescription data No. “0012” row and the “prescription audit” column is selected and canceled, the prescription data No. “0012” is set in the prescription audit management data (FIG. 8). “Waiting” in the “execution status” of the row is set to “cancel”.) As described above, the process returns to step S3 and repeats from the update of the dispensation execution status display. However, if the “execution status” is “execution in progress” or has ended, it cannot be canceled.
[0060]
When the “stop / start” button is clicked with the mouse (step S10), a stop / start signal is transmitted to the execution process (step S11). That is, the process is stopped / started by transmitting a stop / start signal to the execution process (FIGS. 13, 16, and 18) corresponding to the selected prescription reception, prescription inspection input, and dispensing device 2 (for example, column item “ When selecting and stopping the “medicine bag No. 1”, a stop signal is transmitted to the execution process (FIG. 18) corresponding to the first medicine bag printing machine. Then, in the status display columns of the selected “prescription reception”, “prescription audit input”, and “dispensing device”, “stopping” (for example, when stopping the column item “medicine bag 1”) "In operation" display ("○" mark) is changed to "stopped" display) or "in operation" is displayed (step S12), and similarly to the above, the process returns to step S3 to update the display of the dispensing execution status Repeat from. By displaying the number of waiting in the “prescription audit input” and “dispensing device”, the degree of retention of each dispensing process is known, and it is possible to determine whether or not countermeasures such as increasing the number of pharmacists are necessary.
[0061]
When the “end” button is clicked with the mouse (step S13), an end signal is sent to all of the execution processes (FIGS. 13, 16, and 18) generated based on the dispensing execution management target setting file (FIG. 2). Is transmitted to end the process (step S14), the dispensing execution management process is ended, and the menu screen (not shown) is returned.
[0062]
With reference to the dispensing execution situation of each prescription data shown in FIG. 6, what kind of operation was performed is demonstrated concretely. In the prescription data No. “0006”, after receiving the prescription data, when the “prescription audit input” is in the “waiting” state, a deletion command is received from the host computer 12 and automatically dispensed after the “prescription audit input”. It shows that the process has been canceled. The prescription data No. “0007” is received as correction data of the prescription data No. “0006”, and indicates that each dispensing process in the dispensing device 2 is completed at each time indicated by “MM: HH”. The prescription data No. “0009” indicates that “NG” is input in “prescription audit input” and the subsequent dispensing process is not executed. The audit NG is transmitted to the host computer 12 and then receives the prescription data No. “0012” as the correction data of the same patient number “93027561”. In the prescription data No. “0010”, the “unprocessed” mark indicates that the process is unprocessed, and the “★” mark indicates that the monitoring time exceeds 10 minutes. In each dispensing process, it is understood that the tablet packaging No. 1 is “running” and has a “★” mark, and that the cause is a stop due to error No. 02 “Out of wrapping paper”. The error information is acquired by the status received from the dispensing device 2.
[0063]
By the way, the generation of the execution management data in the step S1 is specifically performed as follows.
[0064]
First, prescription reception management data (FIG. 7) which is data for managing execution of “prescription reception” based on management object 1 “prescription reception” in an example of the dispensing execution management object setting file (FIG. 3). Generate. The stored contents of the prescription reception management data are displayed in the “Prescription reception” column of the “Dispensing execution status monitor” screen shown in FIG.
[0065]
Further, based on the management object 2 “prescription audit input”, prescription audit management data (FIG. 8) that is data for managing the execution of “prescription audit input” is generated, and the “Dispensing execution status monitor” screen (FIG. 8) It is displayed in the column of “Prescription inspection” in 6).
[0066]
Furthermore, based on the management object 3 “medicine bag printing machine” (1 unit), the first medicine bag printing machine execution management data (FIG. 9) is generated, and based on the management object 4 “tablet packaging machine” (2 units) Unit 1 execution management data (Fig. 10) and tablet packaging unit 2 execution management data (Fig. 11) are generated, and based on the management target 5 "powder packaging machine" (1 unit), powder packaging unit 1 unit execution management data ( FIG. 12) is generated. Note that each execution management data immediately after generation is empty with no row data.
[0067]
Further, the generation of the execution process in the step S1 is the same as the generation of the execution management data. The management object 1 “prescription reception”, the management object 2 “prescription audit input”, and the management object 3 “medicine bag printing machine”. (1 unit), management target 4 “tablet packaging machine” (2 units), and management target 5 “powder packaging machine” (1 unit). Then, the following processes of “prescription reception”, “prescription audit input”, and “dispensing device execution” are started.
[0068]
In the “prescription reception” process, when the management object 1 “prescription reception” is set in the dispensing execution management target setting file (FIG. 2), the execution process shown in FIG. 13 is generated and the “prescription reception” process is started. .
[0069]
In the prescription receiving process, first, it is determined whether or not prescription data has been received from the host computer 12 (step S100). If prescription data has not been received from the host computer 12, an “execution management signal reception” procedure is called (step S101).
[0070]
In “execution management signal reception”, as shown in FIG. 14, first, whether or not a stop signal has been received, that is, whether or not the “stop” button has been clicked with the mouse on the dispensing execution status monitor screen (FIG. 6). Judgment is made (step S200). If a stop signal is received, after waiting for a start signal from dispensing execution management (FIG. 5) (step S201), it will return to step S100. That is, if a stop signal is received in a state where no prescription data is received, prescription reception is not resumed unless an activation signal is received. If a stop signal has not been received, it is determined whether an end signal has been received (step S202). If the end signal has not been received, the process returns to step S100 as described above. That is, prescription reception is terminated only when an end signal is received in a state where prescription data is not received. The “execution management signal reception” is a common process for receiving a signal from the dispensing execution management. The “prescription audit input” process (FIG. 16) and the “dispensing device execution” process (see FIG. Similarly in 18), the process shown in FIG. 14 is performed.
[0071]
On the other hand, if the prescription data is received from the host computer 12 in the step S100, the received prescription data is written in the prescription file (FIG. 4) (step S102). The data received from the host computer 12 is composed of only various codes in order to reduce the amount of communication data. Therefore, when displaying the contents of the prescription data, various master files with various codes as search keys are displayed. The name data and the like are read out. For example, since only the drug code “Shioe” is stored in the received data, the drug name “Tablet A” must be read from the drug master file. Further, the drug code is a unique code for each drug that is contracted by removing the muddy point from the abbreviation of the drug so that the pharmacist can easily input (for example, “Joizaie” is “Shioe”). The format of the prescription data is as shown in FIG. 4, and the host command accompanying the prescription data is set to “classification”. The contents of the prescription data can be arbitrarily changed by inputting with a keyboard or a mouse on the prescription data audit input screen (FIG. 19), and the changed contents are written in the prescription file (FIG. 4).
[0072]
Subsequently, the type of the host command is determined (step S103). If the host command is “correct”, the prescription data before correction is searched from the prescription file (FIG. 4), and if the prescription data has not received the “delete” command from the host, the deletion process is performed. Is performed (step S104). That is, “delete” is set in “category” of the prescription file (FIG. 4), and “waiting” is set to “cancel” in “execution status” of the execution management data (FIGS. 8 to 12). Then, at the end of the prescription reception management data (FIG. 7), the correction processing is completed by adding the row data in which the end time in the HHMMSS format is set to the “execution status” (step S106). Also, if the host command is “delete”, the execution management data (FIGS. 8 to 12) when the “execution status” of the row data corresponding to the prescription data commanded to be deleted is in a “waiting” state that can be canceled. ) Is set to “Cancel” to complete the deletion process (step S105). And it returns to step S100 and repeats from reception of prescription data. Further, if the host command is “normal”, the process proceeds to step S106 without performing step S104.
[0073]
As described above, since the execution management data can be rewritten automatically and quickly in accordance with the contents of the host command, wasteful dispensing is immediately stopped without being continued, and drug loss is suppressed.
[0074]
Next, it is determined whether or not there is a management object 2 “prescription audit input” in the dispensing execution management object setting file (FIG. 2) (step S107). If there is “prescription audit input”, prescription audit management data is added (step S108). That is, row data (for example, refer to prescription data No. “0012” in FIG. 8) in which “execution status” is set to “waiting” is added to the last of the prescription audit management data (FIG. 8), and the above-described step S100. Return to and repeat from receiving prescription data. On the other hand, if the management object 2 “prescription audit input” is not set, the procedure “add dispensing device execution management data” is called to add dispensing device execution management data (step S109), and then the process returns to step S100. Repeat from receiving prescription data.
[0075]
In the process of “adding dispensing device execution management data”, it is first determined whether or not there is a medicine bag printer as shown in the flowchart of FIG. 15 (step S300). If at least one management object 3 “medicine bag printing machine” is set in the dispensing execution management object setting file (FIG. 2), it is determined that there is a medicine bag printing machine, and the medicine bag printing machine / execution management data is added (step S301). When there are a plurality of medicine bag printing machines, the number of machines is determined so as to equalize the processing load and avoid the machines in the “stopped” state. Then, row data in which “execution status” is set to “waiting” is added to the last of the medicine bag printing machine execution management data (FIG. 9) corresponding to the number machine. However, when called in the case of audit NG (step S406) in the prescription audit input process (FIG. 16), which will be described later, line data with “execution status” set to “none” is added (for example, in FIG. 9). And prescription data No. “0009”).
[0076]
On the other hand, if it is determined in step S300 that there is no medicine bag printing machine (when no management target 3 “medicine bag printing machine” is set), it is judged whether or not there is a tablet packaging machine (step S300). S302). If one or more management targets 4 “tablet packaging machines” are set in the dispensing execution management target setting file (FIG. 2), it is determined that there is a tablet packaging machine and added to the tablet packaging machine execution management data (step S303). ). If there is data to be packaged by the tablet packaging machine in the prescription data drug (determined by whether the drug's form code is “packaging with tablets” or “packaging with capsules”), there are multiple tablet packaging machines At the end of the tablet packaging machine execution management data (FIGS. 10 and 11) corresponding to the machine, the machine is determined so as to equalize the processing load and avoiding the machine in the “stopped” state. Add row data with "Execution status" set to "Waiting". If there is no corresponding data in the medicine of the prescription data, row data (for example, FIG. 10) with “execution status” set to “none” at the end of the tablet packaging machine execution management data (FIGS. 10 and 11). Add prescription data No. “0011”). The “execution status” is also set to “none” when called from the “prescription audit input” audit NG process (FIG. 16: step S406) described later.
[0077]
On the other hand, if it is determined in step S302 that there is no tablet packaging machine (when no management target 4 “tablet packaging machine” is set), it is determined whether there is a powder packaging machine (step S304). ). If at least one management object 5 “powder packaging machine” is set in the dispensing execution management target setting file (FIG. 2), it is determined that there is a powder packaging machine and added to the powder packaging machine execution management data (step S305). ). If no management object 5 “powder dispenser” is set, the process returns to step S100 without performing step S305. In addition to the powder packaging machine execution management data, if there is data to be packaged by the powder packaging machine in the drug of the prescription data (determined by the form code of the drug is “packaging with powder”), When there are multiple packaging machines, determine the number so that the processing load is equal and avoid the number of machines that are in the “stopped” state, and the final state of the powder packaging machine execution management data (Fig. 12) corresponding to that number In addition, row data (for example, refer to prescription data No. “0011” in FIG. 12) in which “execution status” is set to “waiting” is added. When there is no corresponding data in the medicine of the prescription data, or when it is called from the auditing NG process of the prescription audit input, the “execution status” is set to “none” at the end of the powder dispenser execution management data (FIG. 12). Add the line data set to "".
[0078]
The “addition of dispensing device execution management data” is a common process for adding row data to the dispensing device execution management data (FIGS. 9 to 12) as judged from the equipment status of the dispensing device 2 and will be described below. The same process is performed in the “prescription audit input” process (FIG. 16). When other models are equipped, a step for determining whether or not the model is present and a step for adding to the execution management data of the model are added as a set.
[0079]
The “prescription audit input” process is performed when the management target 2 “prescription audit input” is set in the dispensing execution management target setting file (FIG. 2), and the execution process shown in FIG. To start.
[0080]
In the “prescription audit input” process, first, the “prescription audit input” screen (FIG. 19) is displayed on the prescription audit input terminal device 6a in an initial state in which all data input fields are empty (step S400). It should be noted that today's date engraved by the calendar clock 9 is displayed on the dispensing date.
[0081]
Then, the prescription audit management data (FIG. 8) is searched for the line data in which the “execution status” is in the “waiting” state (step S401), and the line data is processed. If there is no corresponding line data, the process proceeds to new input determination (step S413) described later. If there is corresponding line data, the "execution status" of the line data is set to "in execution" (step S402).
[0082]
Subsequently, the prescription data is read from the prescription file (FIG. 4) using the “prescription data No.” of the retrieved line data, and the content is displayed on the “prescription audit input” screen (FIG. 19) (step S403). . The displayed contents are used by a pharmacist to audit from a pharmacological point of view.
[0083]
If there is no problem as a result of the audit, by clicking the “audit OK” button with the mouse (step S404), the process proceeds to the prescription audit management data “end” setting, and the “execution status” of the retrieved line data is displayed in the HHMMSS format. An end time is set (step S405). For the prescription data of the audit OK, each dispensing device 2 is operated by a dispensing device execution process (FIG. 18) described later. If there is a problem as a result of the audit, by clicking the “audit NG” button with the mouse (step S406), the prescription audit management data “cancel” is set, and the “execution status” of the retrieved row data is set to “execution status”. “Cancel” is set, and “Category” in the prescription file (FIG. 4) of the corresponding prescription data is set to “Audit NG Cancel” (step S407).
[0084]
Next, the “adding dispensing device execution management data” procedure (FIG. 15) is called and the same processing as described above is performed (step S408). Then, it is determined whether or not the audit result needs to be transmitted (step S409). When the “parameter” of the management object 2 “prescription audit input” in the dispensing execution management object setting file (FIG. 2) is 1, it is determined that the audit result needs to be transmitted, and the audit result of the prescription data is sent to the host computer 12 (OK / NG) is transmitted (step S410), and the process returns to step S401 to repeat from the prescription audit management data “wait” determination.
[0085]
As described above, by transmitting the audit result to the host computer 12, it is possible to construct a system for starting the medical accounting process on the host computer 12 side or requesting the doctor to change the prescription.
[0086]
As a result of the audit, when the “Cancel” button is clicked without clicking either the “Audit OK” button or the “Audit NG” button (step S411), the “execution status” of the searched row data is displayed. By setting “waiting” (step S412), postponing this prescription data, returning to the step S401 and repeating from the prescription audit management data “waiting” determination, the content of another prescription data in the “waiting” state is Is displayed.
[0087]
Thereafter, in step S401, when there is no row data whose “execution status” is in the “waiting” state and the “new input” button is clicked (step S413), arbitrary prescription data is newly input from the patient number ( Step S415).
[0088]
In this case, for example, when the patient number “93027561” is input from the keyboard, the patient name (kana, kanji), gender, and date of birth are read from the patient master file and displayed. The age is automatically calculated from the date of birth and today's date and displayed. The exchange number is the number of the “return ticket” that is handed over at the end of the transaction only for outpatients. In the example of the prescription data (FIG. 19), the prescription classification is “03” temporary admission (inpatient), and the exchange number is meaningless, so “0000” is input. When each code is entered, the name data is read from the corresponding master files and displayed for the department, doctor, ward, and prescription category (for example, if the code “01” is entered in the department, “internal medicine” is displayed. Is displayed). The “Prescription No.” column is a serial number of “Prescription” in which the drug (s) and usage are combined. This “prescription” can be entered in multiple numbers. The “code” input field is a field for inputting a drug code or a usage code. When a code is entered, name data is read from the medicine master file or usage master file and displayed. In the “code” input field, a drug code is normally input (for example, “Shioe”), but when a “/” symbol is input at the beginning, a usage code is input thereafter (for example, “301”). The usage name corresponding to “301” is “minute 3 morning, noon, after dinner”). In the usage line in which the usage code is input, after the usage name is displayed, the “days” input field is displayed and the number of days is input (for example, “7 days”). The “Dose” column is a column for inputting the daily dose of the drug. The unit (tablet, CAP: capsule, g, ml, etc.) is read from the medicine master file and displayed. The “dosage time” column is a column for inputting a single dose obtained by dividing a daily dose by dose. The single dose is the number (number of tablets) in the case of solid preparations such as tablets, capsules and pills, but the number of grams in the case of powders. The form code in the “form” column is read from the medicine master file and displayed. The form code is a code for classifying medicines by form in the dispensing operation. “Separation” means that the medicine feeder automatically supplies and packages, and “heat seal” means that the heat-sealed package packaged by the pharmaceutical manufacturer is delivered to the patient. "Packaging with tablets" = 11, "Heat sealing with tablets" = 13, "Packaging with capsules" = 14, "Heat sealing with capsules" = 16, "Packaging with powders" = 17, "With powders" Enter “heat seal” = 19 or the like.
[0089]
Next, when the “audit OK” button is clicked (step S416), the inputted prescription data is written in the prescription file (FIG. 4) (step S418). For the prescription data of the audit OK, each dispensing device 2 is operated by a dispensing device execution process (FIG. 18) described later. If the management object 1 “prescription reception” is set in the dispensing execution management object setting file (FIG. 2) (step S420), the “execution status” is set to “none” at the end of the prescription reception management data (FIG. 7). The line data set in (2) is added (step S421). And the line data which set the end time of a HHMMSS format are added to the last of prescription audit management data (FIG. 8) (step S422). On the other hand, if the “audit OK” button is not clicked in step S416 and the “cancel” button is clicked (step S417), the display of the prescription data being input is deleted (step S419), and the process returns to step S401. The prescription audit management data “waiting” is repeated, and the contents of the prescription data received from the host computer 12 and in the “waiting” state are displayed.
[0090]
If no button is clicked, the “execution management signal reception” procedure (FIG. 14) is called (step S414), and the process returns to step S401 and repeats from the prescription audit management data “wait” determination.
[0091]
In the “dispensing device execution” process, the management object 3 “medicine bag printing machine”, the management object 4 “tablet packaging machine”, or the management object 5 “powder packaging machine” is set in the dispensing execution management object setting file (FIG. 2). If there is, the execution process shown in FIG. 18 is generated and the “dispensing device execution” process is started. In an example of the dispensing execution management target setting file (FIG. 3), a total of four dispensing device execution processes are generated for each dispensing device, and the execution status is written in each piece of execution management data to be processed.
[0092]
In the “dispensing device execution” process, first, search is made for row data whose “reissue flag” is “ON” in the execution management data (FIGS. 9 to 12) (step S500). Then, the “reissue flag” of the retrieved row data is set to “OFF” (step S501). If there is no corresponding row data, search is made for row data in which the “execution status” is in the “waiting” state in the execution management data (FIGS. 9 to 12) (step S502). If there is no corresponding row data, the "execution management signal reception" procedure (FIG. 14) is called (step S503), and the process returns to step S500 to repeat from the execution management data reissue flag determination.
[0093]
Subsequently, the “execution status” of the retrieved row data is set to “being executed” (step S504). Then, the prescription data is read from the prescription file (FIG. 4) using “prescription data No.” of the retrieved row data (step S505).
[0094]
Here, after receiving the status of the dispensing device 2 and waiting until it becomes an “operable” state (step S506), the operation command created based on the prescription data is transmitted to the dispensing device 2 to be operated (step S507). ).
[0095]
Thereafter, it waits until it receives the status of the dispensing device 2 and enters the “operation end” state (step S508). Then, after setting the end time in the HHMMSS format in the “execution status” of the retrieved row data (step S509), the process returns to step S500 and repeats from the execution management data reissue flag determination.
[0096]
In this way, the reissue operation can be centrally managed simply by setting the “reissue flag” to “ON” or “OFF” in the execution management data. In addition, by first searching for row data whose “reissue flag” is “ON” and then searching for row data whose “execution status” is in the “waiting” state, the execution priority is changed. As a result, the patient's waiting time can be minimized.
[0097]
【The invention's effect】
As is clear from the above description, according to the dispensing control device according to the present invention, it is possible to manage and control a large number of dispensing devices by the same method. For this reason, even in a facility where the number and types of dispensing devices are variously different, it is not necessary to design and manufacture according to individual specifications, and it is possible to easily cope with an increase in dispensing devices. Moreover, since the dispensing device can be operated by centralized monitoring, operation is simplified. Furthermore, the same effect can be obtained in cooperation with a host computer or in a facility having different equipment conditions for prescription reception and prescription audit input.
[0098]
Furthermore, since the “Prescription reception” and “Prescription audit input” can be managed in the same manner as the dispensing device in the dispensing execution management target setting file, the operation becomes even easier.
[0099]
Dispensing operations are automatically / immediately deleted / corrected according to prescription data deletion and correction commands from the host computer, so even if prescription cancellation or content change occurs, labor and drug loss due to unnecessary dispensing are minimized. Can be held down.
[0100]
Since the audit result is transmitted to the host computer, the host computer can easily cope with the construction of a system for starting medical accounting processing or requesting a doctor to change the prescription.
[0101]
Prescription reception, prescription audit input, and the dispensing execution status of each dispensing device are displayed on the monitor screen, so that all dispensing devices are centrally monitored in the same way to prevent each dispensing from stagnating due to an error etc. Can do.
[0102]
Since the prescription inspection input and the execution time in each dispensing device are monitored and a notification is made when a predetermined time is exceeded, it is possible to prevent the patient's waiting time from becoming extremely long.
[0103]
Since reissuing can be commanded centrally, it is possible to reduce the time and effort of operation.
[0104]
Since the reissuing operation is prioritized over the normal operation, it is possible to minimize the extension of the waiting time of the patient.
[0105]
Prescription audit input and operations on each dispensing device can be canceled with a simple operation, so it is possible to flexibly handle abnormal situations such as switching to manual dispensing due to a failure on the host computer side or a dispensing device failure. I can deal with it.
[0106]
Prescription reception, prescription audit input, and operations on each dispensing device can be stopped / started with simple operations, so that the operation commands that cannot be processed, such as when the medicine packaging machine has stopped due to running out of packaging paper, will stay and stay. The situation can be prevented. Also, it can flexibly cope with abnormal situations.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a device configuration of a dispensing control device according to the present embodiment.
FIG. 2 is a diagram showing storage contents of a dispensing execution management target setting file.
FIG. 3 is a diagram illustrating an example of FIG. 2;
FIG. 4 is a diagram showing stored contents of a prescription file.
FIG. 5 is a flowchart showing a dispensing execution management process.
FIG. 6 is a diagram showing a dispensing execution status monitor screen.
FIG. 7 is a diagram showing storage contents of prescription reception management data.
FIG. 8 is a diagram showing storage contents of prescription audit management data.
FIG. 9 is a diagram showing storage contents of medicine bag printing first machine execution management data.
FIG. 10 is a diagram showing the storage contents of tablet packaging No. 1 execution management data.
FIG. 11 is a view showing the storage contents of tablet packaging No. 2 execution management data.
FIG. 12 is a diagram showing storage contents of powder packaging unit 1 execution management data.
FIG. 13 is a flowchart showing prescription reception processing;
FIG. 14 is a flowchart showing execution management signal reception processing;
FIG. 15 is a flowchart showing processing for adding dispensing device execution management data.
FIG. 16 is a flowchart showing a prescription audit input process.
FIG. 17 is a flowchart showing a prescription audit input process.
FIG. 18 is a flowchart showing processing of dispensing device execution.
FIG. 19 is a diagram showing a prescription data audit input screen.
[Explanation of symbols]
1 ... Control device
2. Dispensing equipment
3 Central processing unit
4. Hard disk device
5. Multi-channel communication part
6 ... Terminal device
7 ... Memory
8 ... Control program
10. Dispensing execution management target setting file
11 ... Prescription file
12 ... Host computer

Claims (10)

In a dispensing control device that drives and controls a plurality of dispensing devices to dispense the prescription based on the prescription data,
Dispensing execution management target setting file including a management object including each dispensing device, “prescription reception” used for receiving prescription data from the host computer, and “prescription audit input” used for prescription data audit, and host A hard disk device for storing a prescription file in which prescription data received from a computer is stored ;
Means for generating prescription reception management data and an execution process for prescription reception processing based on "prescription reception" of the dispensing execution management object setting file;
Means for generating prescription audit management data for managing execution of “prescription audit input” and an execution process for prescription audit input processing based on “prescription audit input” of the dispensing execution management object setting file; ,
Based on the management target of the dispensing execution management target setting file, means for generating execution management data for each dispensing device and an execution process for dispensing device execution processing;
A central processing unit that drives and controls the corresponding dispensing device based on the management data and the execution process;
A dispensing control device comprising: The data received from the host computer includes a host command,
The hard disk device stores the received host command as prescription reception management data in a prescription file,
If the correction instruction is included in the host instruction of the prescription reception management data stored in the prescription file, the central processing unit searches and deletes the corresponding prescription data before correction and deletes the corrected prescription data. 2. The dispensing control device according to claim 1, wherein if the host command includes a deletion command, the corresponding execution management data is set to cancel. The central processing unit displays the audit input of the prescription data received from the host computer on the monitor screen, and if there is no problem with the audit result input on the monitor screen, proceed to the prescription audit management data “end” setting and execute the dispensing device If there is a problem in the audit results by operating each dispensing device by the process of, proceed to the prescription audit management data “Cancel” setting, set the prescription file of the corresponding prescription data to “Cancel NG Cancel”, and The dispensing control device according to claim 1, wherein the dispensing control device transmits.   4. The dispensing control device according to claim 1, wherein the central processing unit displays an execution status on a monitor screen for each management object stored in the dispensing execution management object setting file. 5.   The said central processing unit monitors execution time about each management object memorize | stored in the said dispensing execution management object setting file, and will alert | report if this execution time exceeds monitoring time. The dispensing control apparatus of any one of Claims.   The central processing unit, when reissued from the input device, resumes the operation of the reissued management object among the management objects stored in the dispensing execution management object setting file. The dispensing control device according to any one of 1 to 5.   The dispensing control device according to claim 6, wherein the central processing unit prioritizes the reissue operation over a normal operation.   The central processing unit is applicable only when the execution status of the prescription data that has been input for cancellation is “waiting” for the management target stored in the dispensing execution management target setting file when the input is canceled from the input device. The dispensing control device according to any one of claims 1 to 7, wherein an operation to be managed is canceled.   The central processing unit transmits a stop or start signal to an execution process corresponding to a selected management object based on the stop or start input when the stop or start is input from the input device. The dispensing control device according to any one of 1 to 8.   In a dispensing control method for driving and controlling a plurality of dispensing devices to dispense the prescription based on the prescription data,
  Dispensing execution management target setting file including a management object including each dispensing device, “prescription reception” used for receiving prescription data from the host computer, and “prescription audit input” used for prescription data audit, and host A prescription file storing prescription data received from a computer,
  Based on the “prescription reception” of the dispensing execution management object setting file, prescription reception management data and an execution process for prescription reception processing are generated,
  Based on the “prescription audit input” of the dispensing execution management object setting file, generate prescription audit management data for managing the execution of “prescription audit input”, and an execution process for prescription audit input processing,
  Based on the management target of the dispensing execution management target setting file, generate execution management data for each dispensing device and an execution process for dispensing device execution processing,
  A dispensing control method, comprising: driving-controlling a corresponding dispensing device based on the management data and an execution process.

Images