KR20010062645A - Dispensing control device - Google Patents

Abstract

PURPOSE: To easily integrate driving and controlling plural dispensing machines based on prescription data in the same manner. CONSTITUTION: Plural dispensing machines are driven and controlled to dispense the prescription based on prescription data. A file 10 for setting a dispensing control object to set a controlled object including the dispensing machines is stored in a fixed disk 4. Execution control data and execution processes are generated respectively for control objects in the file 10 stored in the fixed disc 4 based on the dispensing data to drive and control corresponding dispensing machines 2.

Description

Pharmacy Control Unit {DISPENSING CONTROL DEVICE}

The present invention utilizes each preparation device used for preparation work, such as a medicine bag printing machine used in medical facilities, such as a hospital and a pharmaceutical pharmacy, and a chemical | medical agent division packaging machine (henceforth a distribution machine). The present invention relates to a preparation control device that operates by controlling in accordance with prescription data, and more particularly, to a preparation control device that can be connected to a host computer that transmits prescription data to an external device.

Background Art Conventionally, various preparation devices such as a medicine bag printing machine and the like receive prescription data from a host computer and are driven to be controlled.

Japanese Patent Application Laid-Open No. 4-57348 describes a preparation control device for allocating data from a host computer to an input device of a preparation device suitable for the type of preparation.

Japanese Unexamined Patent Publication No. 6-9600 discloses a dosage system for prescription preparation, which generates preparation data in accordance with a prescription, operates a preparation device, and displays the execution status of the preparation data.

Japanese Unexamined Patent Application Publication No. 6-9601 describes a medicine bag preparation system for prescription preparation, which generates preparation data according to a prescription to operate a preparation device, and generates display contents of a medicine bag in accordance with the preparation data.

Japanese Patent Application Laid-Open No. 7-71575 discloses a preparation control device that operates a dispenser using data from a host computer and creates a medicine bag.

Japanese Patent Application Laid-Open No. 7-71576 discloses a preparation control device that operates a dispenser using data from a host computer and notifies the progress of the medication operation.

Japanese Patent Application Laid-Open No. 8-124 discloses a preparation control device that operates a preparation machine using data from a host computer and generates management information for the entire preparation operation.

Patent No. 2623010 discloses a drug packaging device which operates a plurality of drug packaging machines in accordance with prescription data, and monitors the operating state of the drug packaging machine.

Japanese Patent No. 2691859 discloses a preparation control method for receiving data on a medicine from a host computer, classifying it according to the type of medicine, and assigning it to a suitable medicine.

However, in any of the above-described control apparatuses, the control method is different for each kind of the preparation equipment, and it is necessary to design and manufacture for each facility in which these control apparatuses are installed. Moreover, the operation of reissuing the printing of the medicine bag and the dividing packaging of the medicine and canceling the operation due to the printing failure and the poor packaging can be performed only on the preparation device side. For this reason, whenever a pharmacist needs to reissue and cancel an operation, the pharmacist must move to each preparation device.

In addition, even if it is necessary to cancel the prescription and change the contents in accordance with an input error, an instruction change, or the like, if the contact is executed after the end of the preparation, the medicine is already packaged and forced to be disposed of.

In addition, the countermeasures when the preparation equipment is stopped due to an error are insufficient. For example, Japanese Patent Application Laid-Open No. 4-57348 only outputs preparation data of a type that cannot be prepared as a preparation instruction sheet. For this reason, the operation instruction which cannot be processed increases and stays, and preparation may be delayed. In this case, a complicated processing operation is required for distributing the operation command to other preparation devices. This problem occurs as the type and number of preparation devices increase.

In addition, even when it is necessary to reissue because of poor printing or divided packaging of the medicine bag, the reissue operation method is different for each model of the preparation device, which makes operation complicated.

When abnormal prescription data is received due to a problem on the host computer side, or when an abnormality such as a failure occurs in the dispensing device and the manual preparation is performed, the dispensing device may be reset or turned off again. In some cases, the execution of the preparation must be canceled, a complicated processing operation is required, and a large amount of response time is required.

In addition, in the case of forgetting the preparation for a particular patient, or re-issuing medicine bag printing and drug division packaging, the patient's waiting time becomes extremely long.

Therefore, an object of the present invention is to provide a preparation control device capable of simply controlling and controlling driving of a plurality of preparation devices in the same manner according to prescription data.

BRIEF DESCRIPTION OF THE DRAWINGS The block diagram which shows the apparatus structure of the preparation control apparatus which concerns on this embodiment.

Fig. 2 is a diagram showing the contents of storage of a preparation execution management target setting file.

3 shows an example of FIG. 2;

4 is a diagram showing the contents of a prescription file.

5 is a flowchart showing a process of preparation execution management;

6 is a diagram showing a screen of a preparation execution status monitor;

Fig. 7 is a diagram showing the stored contents of prescription reception management data.

Fig. 8 is a diagram showing the stored contents of prescription audit management data.

Fig. 9 is a diagram showing the contents of the medicine bag printing No. 1 execution management data.

Fig. 10 is a diagram showing the stored contents of tablet distribution # 1 execution management data.

Fig. 11 is a diagram showing the stored contents of tablet distribution # 2 execution management data.

Fig. 12 is a diagram showing the stored contents of powder distribution 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 of the preparation machine execution management data.

16 is a flowchart illustrating processing of prescription audit input.

Fig. 17 is a flowchart showing processing of prescription audit input.

18 is a flowchart illustrating processing of a dispenser execution.

19 shows a screen of prescription data audit input.

(Explanation of the sign)

1: control device 2: dispenser

3: central processing unit 4: hard disk unit

5: multi-channel communication unit 6: terminal device

7: memory 8: control program

10: setting file for managing execution of preparation 11: prescription file

12: host computer

In the preparation control device which drives-control a plurality of preparation devices in order to prepare the prescription according to the prescription data, the present invention provides a means for solving the above problems. A hard disk device storing the preparation execution management object setting file and a management process and an execution process for each management object of the preparation execution management object setting file stored in the hard disk device according to the prescription data; It is provided with a central processing unit for driving control of the corresponding preparation device in accordance with the execution management data and the execution process.

With this configuration, each preparation device or the like can be managed by only a single preparation execution management target setting file. In addition, even when a new management object is added, it is only necessary to set the management object in the preparation management object setting file.

The hard disk device preferably includes a "prescription reception" used for reception of prescription data from a host computer and a "prescription audit input" used for auditing prescription data in the preparation execution management object setting file. Accordingly, the prescription reception and the prescription audit input can be managed and controlled similarly to the model of the preparation device.

In addition, the structure of the combination of prescription reception and prescription audit input can consider three types, "Y / Y", "Y / Y", "Y / Y". "Y / Y" corresponds to a case of receiving prescription data and inputting a prescription audit. "Yes / no" corresponds to a case where the preparation device is directly operated without receiving prescription data and inputting a prescription audit. "N / Y" corresponds to the case where prescription data is input as a prescription audit input.

In the central processing unit, when a host command is input from a host computer, if a correction command is included in the host command, the prescription data after correction is searched for and deleted, and the corrected prescription data is added to the host command. In the case where the delete instruction is included, it is preferable to set the corresponding execution management data to cancel. Accordingly, it is possible to delete or modify the operation of the preparation automatically and instantly, and to reduce the labor and drug loss caused by useless preparation.

The central processing unit may display the audit input of the prescription data received from the host computer on the monitor screen and transmit the audit result input on the monitor screen to the host computer. Accordingly, the pharmacist conducts an audit on the contents of the prescription data received from the host computer, initiates the doctor accounting process according to the audit result (OK / NG), or requests the doctor to change the prescription. It is also possible to build the system on the host computer side.

In the central processing unit, it is preferable to display the execution status on the monitor screen for each management object stored in the preparation execution management object setting file. Accordingly, it is possible to centrally manage the management status of each management object, that is, prescription reception, prescription audit input, and each preparation device. Here, the execution status includes the status of unprocessed / ended of prescription data, the status of waiting / during / ending of operation in each preparation device in the prescription data, the number of operations waiting in each preparation device, and the operation. It means the status of middle / stopped, error.

Further, the central processing unit monitors the execution time for each management object stored in the preparation execution management object setting file, that is, prescription reception, prescription audit input, and each preparation device, and notifies as the predetermined time is exceeded. It is preferable at the point which can prevent long waiting time of a patient by carelessness etc.

In the central processing unit, if a reissue is input from an input device, the operation is resumed with respect to the corresponding management object stored in the preparation execution management object setting file according to the corresponding reissue input. It is preferable at the point which can concentrate and order. The reissue targets include medicine bag printing, tablet divided packaging, powder divided packaging and the like.

In this case, it is preferable to give priority to the reissue operation above the normal operation.

Further, in the central processing unit, if the input is canceled by the input device, only the case where the execution status of the canceled input prescription data is "waiting" for the management object stored in the preparation execution management object setting file is applicable. You may cancel the operation of the object. In addition, when a stop or start is input by the input device, a stop or start signal may be transmitted to the execution process corresponding to the selected management object in accordance with the stop or start input. As a result, the operation on each management object can be immediately canceled, stopped or started by a simple operation.

Embodiment of the Invention

EMBODIMENT OF THE INVENTION Hereinafter, embodiment which concerns on this invention is described according to an accompanying drawing.

1 shows a preparation control device 1 according to the present embodiment and a preparation device 2 which is driven and controlled according to the control device 1.

The preparation control device 1 includes a central processing unit 3 (CPU), a hard disk device 4, a multichannel communication unit 5, and a terminal device 6.

The preparation control device 1 drives and controls all the preparation devices 2 by sending an operation command to each preparation device 2 in accordance with the prescription data and receiving a situation from each preparation device 2. Automatically proceed with the preparation work. In addition, the situation includes information on the operation availability, operation termination, and error.

The central processing unit 3 (CPU) includes a memory 7 (RAM) for storing various data, a control program 8 (ROM) for controlling the entire preparation control device 1, and a backup with a battery. A calendar clock 9 which is (backup) and shows a date and time is built-in. The memory 7 (RAM) is used as a prescription data memory for storing prescription data, a execution management data memory for storing execution management data, and other memories (work area for processing, variables, etc.). The calendar clock 9 is used for date and time acquisition in various processes.

The terminal device 6 includes a prescription audit input terminal device 6a composed of a display, a keyboard, a mouse, and a notification buzzer, and a preparation execution management terminal device 6b. These terminal devices 6 are also used for data input of various files, etc. in addition to specific applications such as "prescription audit input" and "preparation execution management." In addition, two of the terminal devices 6 may be aggregated into one. In this case, the various screens are displayed in a multiwindow.

The hard disk device 4 includes a preparation execution management object setting file 10 for setting and storing a management object, a prescription file 11 for storing prescription data, and various masters for storing related information when inputting prescription data. The file is memorized. As the hard disk device 4, a rewritable nonvolatile memory device such as a flash memory can be used.

As shown in FIG. 2, the preparation execution management object setting file 10 stores each preparation device 2 as a management object, in addition to the prescription reception and prescription audit input. Each management object is displayed as a model, and an ID number is attached to each model. Here, the "prescription reception" is 1, the "prescription audit input" is 2, the "medicine bag printing machine" is 3, the "tablet dispenser" is 4, and the "powder dispenser" is 5. When a new management object is added, an ID number is added to respond. In the case where the management target includes a plurality of the same model, the target is identified by attaching a device number. In addition, the parameter is various information unique to each management object, and in "prescription audit input", 1 means "necessity of transmission of an audit result".

Fig. 3 shows a type 1 "prescription reception", a type 2 "prescription audit input", a type 3 "medicine bag printing machine", a type 4 "tablet distribution machine" and a type 5 "powder distribution machine". This is an example of the contents of the preparation execution management target setting file 10 in the case.

The prescription file 11 is a data file that stores prescription data, the contents of which are as shown in FIG. The recording of prescription data in the prescription file is performed when the prescription data is received from the host computer 12 in the processing of "prescription reception" (FIG. 13) described later, and the processing of "prescription audit input" described later. It is executed when new prescription data is input in FIG.

In Fig. 4, the prescription data number indicates a sequential number for identifying the prescription data. The division represents the division of prescription data. The content of the division is the addition of "audit NG cancellation" to the host instruction according to the prescription data. Here, "normal" is set to 0, "delete" is set to 1, "modification" is set to 2, and "audit NG canceled" is set to 3. Prescription data represents the present content of the prescription data. It consists of various codes, and names such as medical department names and drug names are read and displayed from various master files.

The various master files include a medicine master file, a patient master file, a usage master file, a medical treatment master file, a doctor master file, and a prescription classification master file. However, the drawings are omitted because they are files of a simple structure for storing codes and names.

The dispensing machine 2 is mainly a medicine bag printing machine and a drug dispensing machine, and the powder preparation inspection machine which records while checking the normality of taking out and weighing of the medicine bottle in preparation of powder is other than that. And the like, such as a handmade distribution machine for dividing and packaging the handmade water. The number of units of each preparation device 2 also varies from facility to facility, and one or more models or more than one device are connected to the preparation control device 1. Each model of the preparation device 2 is assigned an ID number, and a device number is assigned to each device for each model. These are used for identification and control. When a new model is added, an ID number is added, and when a device increases, it responds by increasing a device number. Although the preparation control device 1 and the preparation device 2 are connected by high speed serial communication, a connection / communication method such as general-purpose bus connection and network LAN connection may be used.

In addition, 12 is a host computer and is used to receive prescription data from an external system. However, since the prescription data can be newly input only by the display, the keyboard, and the mouse of the terminal device 6, the host computer is not necessary. In addition, the prescription audit input terminal 6a may not be required in the facility which does not audit prescription data received on the preparation control device 1 in order to execute the prescription audit on the host computer 12 side. In addition, the linkage system requirement specification that can be obtained from the host computer 12 side in order to connect and link the host computer 12 and the preparation control device 1 also varies from facility to facility.

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.

In addition, the hard disk device 4 is an independent file server device (CPU built-in), and the central processing unit 3 (CPU) and a terminal device (CPU built-in) are server devices as client terminals, The client server may be connected via a network (LAN).

In addition, instead of using the multichannel communication unit 5, the communication with each device of the preparation device 2 may be connected to the same network (LAN), including each device of the preparation device 2, to communicate with each other. .

Next, the preparation execution management processed by the said control apparatus 1 is demonstrated according to the flowchart of FIG.

The process of preparation execution management is executed when a start button of "preparation execution management" is clicked with a mouse on the menu screen (it is a screen with only start buttons arranged). Return to).

When the process of preparation execution management starts, first, execution management data and an execution process are generated sequentially for each set management object (device) according to the preparation execution management object setting file (FIG. 2) (step S1). In addition, immediately after the execution management data is generated, the initial state is blank, and immediately after the execution process is generated, the standby state is waited for the occurrence of events to be processed. Examples of generation are described later.

Subsequently, the "Management execution status monitor" screen shown in FIG. 6 is displayed on the preparation execution management terminal device 6b with the set management object as a column item (step S2). The "Preparation Execution Status Monitor" screen is a column item for each device of the "prescription reception", "prescription audit input", and the preparation device 2, which are the management targets set according to the formulation execution management target setting file (FIG. 2), With the prescription data as a row item, "waiting", "running", "HH: MM (end time)" and the like are displayed as the respective preparation execution states in the column item. There is no status of "waiting" and "real" in "prescription reception". In Fig. 6, "prescription data No.", "patient number", "patient name", "host command (prescription data classification)", "prescription (classification)", "medical department", "school / dong" in the prescription data column (Exchange number / ward) "is read from the prescription data in a prescription file (FIG. 4), and is displayed. The name of the department and the like arises from various master files. In the case of a prescription division, the exchange number (the number of the "drug exchange ticket") is indicated when the prescription is outpatient, and the ward name is displayed in the case of hospitalization. Prescription data No. shows a serial number for identifying prescription data. The host command indicates a command for prescription data from the host computer 12, and is classified into "normal", "delete", and "correction". Here, "normal" is 0, "delete" is 1, and "modification" is 2. In addition, when there are many management objects and do not fit in the width of the screen, a horizontal scroll bar can be displayed and the column items can be horizontally scrolled. In addition, immediately after the screen is displayed, there is a blank state without prescription data as a line item. After this step S2, the processing proceeds by displaying and operating on the "Processing execution status monitor" screen (FIG. 6), and the monitoring apparatus 2 concentrates and monitors.

Subsequently, the contents in the display range on the "Preparation Execution Status Monitor" screen (FIG. 6) are updated with the latest data contents (step S3), and the prescription items, the prescription audit inputs, which are the column items, respectively, of each preparation device The contents of the management data (FIGS. 7, 8, 9, 10, 11, 12) are displayed on the screen.

Prescription reception management data (FIG. 7) is data for managing execution of "prescription reception." In prescription reception management data (FIG. 7), prescription data No. shows the serial number for identifying prescription data. The execution status indicates the execution status of "prescription reception" which is a management target. In this example, the reception end time of the prescription data is set to HHMMSS (hour, minute, second, respectively, two-digit format), and “none” is 90000. The host command indicates a command for prescription data from the host computer 12. Here, "normal" is 0, "delete" is 1, and "modification" is 2.

Prescription audit management data (FIG. 8) is data for managing execution of "prescription audit input". In prescription audit management data (FIG. 8), prescription data No. shows the serial number for identifying prescription data. The execution status indicates the execution status of "prescription audit input" which is a management target. Here, the end time of the prescription audit input is HHMMSS, "wait" is 600000, "running" is 700000, and "cancel" is 800000. An audit result shows the audit result of prescription data. Here, "OK" is set to 0 and "NG" is set to 1.

The preparation apparatus execution management data (FIGS. 9-12) are data for managing the execution of the preparation apparatus 2. As shown in FIG. In the preparation machine execution management data (FIGS. 9-12), prescription data No. shows the serial number for identifying prescription data. The execution status indicates the execution status of the preparation device 2 that is the management target. Here, the execution end time is set to HHMMSS, "Wait" to 600000, "Running" to 700000, "Cancel" to 800000, and "None" to 900000. The reissue flag indicates whether re-issuance of the dispenser output is necessary. Here, "ON" is set to 1 and "OFF" is set to 0. In addition, the content of each execution management data is displayed in each column of the preparation device 2 on the screen of the preparation execution status monitor (FIG. 6).

In addition, prescription data (row data) is added to each management data, and when the execution status is changed, the contents are immediately displayed on the preparation execution status monitor screen (Fig. 6), and the number display and error display are performed. It is also updated to the latest state. Even when the vertical and horizontal scroll bars are operated to change the display range, the contents are displayed accordingly. The new prescription data is continuously scrolled up from the bottom row and displayed unless there is some selection operation by the operator.

At this time, "un" character is displayed on the unprocessed prescription data in which some preparation process remains among the prescription data (row data), and a "★" table is displayed on the prescription data exceeding the monitoring time which can be arbitrarily set. In case of such timeout, a notification buzzer also sounds. The time to start monitoring is the end time of "prescription reception" or "prescription monitoring input" which is the management target initially set in the preparation execution management object setting file (FIG. 2), and this monitoring start time is compared with the present time. Time monitoring.

In the "cell" in the matrix of "row" of prescription data and "column" such as "prescription reception" and "prescription audit input", each management data corresponding to "column" (FIGS. 7 to FIG. The execution status of the row data in 12) is displayed. If there is no preparation corresponding to "cell", it is blank and displays "waiting", "running", "HH: MM (end time)" or "cancel".

Here, it is determined whether or not an operation target has been selected by the operator (step S4). "Cell" in the matrix with "row" of prescription data, "prescription reception", "prescription audit input", "column" of each "preparation device", or "prescription reception" and "prescription" Audit entry ", when each" dispensing apparatus "is clicked with a mouse (" Preparation execution status monitor "screen (FIG. 6), for example, the" 09: row of prescription data No. "0007" and the column of "medicine bag 1" 05 " cell is clicked, and column item " drug bag No. 1 " is clicked), it is determined that the operation target is selected, and the selected item is displayed in reverse (step S5).

If the "reissue" button is clicked with a mouse in the state where the operation target is selected (step S6), the reissue flag of the execution management data is turned ON (step S7). Here, the "reissue flag" of the corresponding row data in the execution management data (FIGS. 9 to 12) of the preparation device 2 corresponding to the selected "cell" is set to "ON". Then, the process returns to step S3 and is repeated from the update of the display of the preparation execution status.

When the "Cancel" button is clicked with a mouse (step S8), the execution management data is set to "Cancel" (step S9), that is, the prescription audit management data (Fig. 8) corresponding to the selected "cell", Set "Cancel" only when the "execution status" of the corresponding row data in the preparation device execution management data (FIGS. 9 to 12) is "waiting" [for example, the prescription data No. When canceling by selecting the "wait" cell in the "0012" row and the "Prescription audit" column, the prescription data No. "Wait" in "execution status" in line "0012" is set to "cancel". Similarly to the above, the process returns to step S3 and is repeated from the updating of the display of the preparation execution status. However, if the "execution status" is "executing" and the end, it cannot be canceled.

In addition, when the "stop / start" button is clicked with a mouse (step S10), the stop / start signal is transmitted to the execution process (step S11). That is, a stop / start signal is sent to the execution process (FIGS. 13, 16, 18) corresponding to the selected prescription reception, prescription audit input, and the preparation device 2 to stop / start the process (e.g., the column item When " Drug Bag No. 1 " is selected and stopped, a stop signal is sent to the execution process (Fig. 18) corresponding to the Drug Bag Printing No. 1). Then, in the status fields of the selected "prescription reception", "prescription audit input" and "preparation device", "stopping" (for example, if the column item "medicine bag No. 1" is stopped, the column of "medicine bag No. 1""Active" display (" "Table" is changed to "stopping" display) or "operating" is displayed (step S12), and the process returns to step S3 as described above and is repeated from the update of the display of the preparation execution status. By the display of the number of waiting times in the "input" and "preparation device", the degree of stay of each preparation process can be known, and it is possible to judge whether or not a countermeasure such as increasing the number of pharmacists is necessary.

When the "end" button is clicked with a mouse (step S13), the end signal is sent to all of the execution processes (FIGS. 13, 16, 18) generated according to the preparation execution management target setting file (FIG. 2). The process ends (step S14), and the process of preparation execution management ends, returning to a menu screen (not shown).

With reference to the preparation execution status of each prescription data shown in FIG. 6, what kind of operation was performed concretely is demonstrated. Prescription data No. &Quot; 0006 ", after receiving prescription data, received a delete instruction from the host computer 12 when " prescription audit input " was in the " standby " state and automatically canceled the dispensing process after " prescription audit input ". Is indicated. Prescription data No. "0007" includes prescription data No. It is received as correction data of "0006", and it shows that each preparation process in the preparation apparatus 2 was complete | finished at each time of the "MM: HH" display. Prescription data No. In "0009", NG is input as "prescription audit input", and it is displayed that the preparation process after that is not performed. In addition, the audit NG is transmitted to the host computer 12, and thereafter, the prescription data No. is used as correction data of the same patient number "93027561". "0012" is being received. Prescription data No. In "0010", the unprocessed by the "US" character and the thing exceeding 10 minutes of monitoring time are shown by the "*" table, respectively. In each preparation process, it is found that the purification distribution unit 1 has a "★" mark as "running", and the cause thereof is a stop due to error number 02 "lack of distribution paper". In addition, the error information is obtained in a state of receiving from the preparation device 2.

By the way, the generation of the execution management data in the step S1 is specifically executed as follows.

First, among the example of the preparation execution management object setting file (FIG. 3), according to "prescription reception" of the management object 1, prescription reception management data (FIG. 7) which is data for managing execution of "prescription reception" is produced | generated. do. The stored contents of the prescription reception management data are displayed in the column of "Prescription reception" on the "Preparation execution status monitor" screen shown in FIG.

In addition, according to "prescription audit input" of management object 2, prescription audit management data (FIG. 8) which is data for managing execution of "prescription audit input" is generated, and the "preparation execution status monitor" screen (FIG. 6). In the column of "prescription audit".

In addition, the medicine bag printing machine # 1 execution management data (FIG. 9) is produced | generated according to the "medicine bag printing machine" (1 unit) of management object 3, and tablet distribution 1 according to the "tablet distribution machine" (2 units) of management object 4 Generates aerobic execution management data (FIG. 10) and refined distribution unit 2 execution management data (FIG. 11), and according to the "powder distribution machine" (one unit) of management target 5, the powder distribution unit 1 execution management data (FIG. 12) Create Each execution management data immediately after creation is left blank with no row data.

The generation of the execution process in step S1 is similar to the generation of the execution management data, with management object 3 "prescription reception input" and management object 2 "prescription audit input", and management object 3 "medicine bag printing machine" ( 1 unit), management target 4 "tablet distributor" (2 units), and management target 5 "powder distributor" (1 unit). And each process of "prescription reception", "prescription audit input", and "execution apparatus execution" shown below is started.

In the "prescription reception" process, when "prescription reception" which is management object 1 is set in the preparation execution management object setting file (FIG. 2), the execution process shown in FIG. 13 is produced | generated, and a process of "prescription reception" is started.

In the prescription reception process, first, it is judged whether or not prescription data has been received from the host computer 12 (step S100). If the prescription data has not been received from the host computer 12, the procedure of "receiving execution management signal" is called (step S101).

In " execution management signal reception ", first, as shown in Fig. 14, it is first judged whether or not a stop signal has been received, that is, whether or not the " Stop " button has been clicked on by the mouse on the preparation execution status monitor screen (Fig. 6) ( Step S200). When the stop signal is received, the process waits until the start signal is received from the preparation execution management (Fig. 5) (step S201), and returns to step S100. In other words, if a stop signal is received without receiving prescription data, prescription reception is not resumed unless a start signal is received. If the stop signal has not been received, it is determined whether or not the end signal has been received (step S202). If the end signal has not been received, the process returns to step S100 as above. As a result, prescription reception is terminated only when an end signal is received without receiving prescription data. In addition, "execution management signal reception" is a common process for receiving a signal from preparation execution management, the processing of "prescription audit input" (FIG. 16) and the "execution apparatus execution" process described below (FIG. 18) In the same manner, the processing shown in FIG. 14 is executed.

On the other hand, if the prescription data is received from the host computer 12 in step S100, the received prescription data is recorded in the prescription file (FIG. 4) (step S102). In addition, since the received data from the host computer 12 is composed of only various codes in order to reduce the amount of communication data, when displaying the contents of prescription data, name data from various master files using various codes as search keys. Read processing such as the above is executed. For example, since only the drug code "Shiwe" is stored in the reception data, the drug name "Tablet A" must be read out from the drug master file. The drug code is one code for each drug that is shortened from the abbreviation of the drug to remove the turbidity point so that the pharmacist can easily enter it (for example, "Joo Wye- (tablet A)" is "Shi Wee"). The format of the prescription data is as shown in Fig. 4, and the host command following the prescription data is set to " division ". The contents of the prescription data can be arbitrarily changed by input by the keyboard and mouse on the prescription data audit input screen (FIG. 19), and the changes are recorded in the prescription file (FIG. 4).

Next, the type of host command is determined (step S103). If the host command is " modified ", the prescription data before correction is searched from within the prescription file (FIG. 4), and if the prescription data has not received the "delete" command from the host in advance, the delete process is executed (step S104). . That is, "delete" is set to "division" of the prescription file (FIG. 4), and "wait" is set to "cancellation" 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 of the HHMMSS format is set to the "execution status" (step S106). If the host command is "delete", the execution management data (Figs. 8 to 12) is "cancelled" in the case of the "waiting" state where the "execution status" of the row data corresponding to the prescription data commanded to be deleted is cancelable. The deletion processing is completed by setting to (step S105). The process then returns to step S100 to repeat from the reception of the prescription data. If the host command is " normal ", the process proceeds to the step S106 without executing the step S104.

In this way, the execution management data can be rewritten automatically and quickly in accordance with the contents of the host command, so that wasteful preparation is immediately stopped without continuing, and drug loss is suppressed.

Subsequently, it is judged whether or not there is "prescribed audit input" of two management targets in the preparation execution management target setting file (FIG. 2) (step S107). If there is "prescription audit input", prescription audit management data is added (step S108). That is, at the end of the prescription audit management data (FIG. 8), the row data (for example, refer to the prescription data No. " 0012 " in FIG. 8) in which " execution status " is set to " wait " The process returns to and repeats from receiving prescription data. On the other hand, if "prescription audit input", which is the management target 2, is not set, the procedure "Adding the preparation equipment execution management data" is called to add the preparation equipment execution management data (step S109), and then returns to the step S100. Repeat from the prescription data reception.

In the process of " addition of preparation equipment execution management data ", as shown in the flowchart of Fig. 15, it is first judged whether or not there is a medicine bag printing machine (step S300). If one or more "medicine bag printing presses" of management target 3 are set in the preparation execution management object setting file (FIG. 2), it is determined that there is a medicine bag printing machine, and the medicine bag printing machine and execution management data are added (step S301). In the case of multiple medicine bag printing machines, the machine is determined by avoiding the "stopping" machine in order to equalize the processing load. Then, at the end of the medicine bag printing machine execution management data (Fig. 9) corresponding to the device, the line data in which "execution status" is set to "wait" is added. However, in the case of the audit NG (step S406) in the process of processing the prescription audit input described later (step S406), when called, the row data in which "execution status" is set to "none" is added (for example, FIG. 9 see prescription data No. "0009").

On the other hand, if it is determined in step S300 that there is no medicine bag printing machine (when one "medicine bag printing machine" which is the management target 3 is not set), it is determined whether there is a tablet distribution machine (step S302). If one or more "tablet distributors" of four management targets are set in the preparation execution management target setting file (FIG. 2), it is determined that there is a tablet distributor and added to the tablet distributor execution management data (step S303). . If the drug in the prescription data contains data that is divided and packaged with a tablet dispenser (determined by the type distribution of the drug as "tablet" or "capsule"), the processing load is equal when there are several tablets. Furthermore, the device is determined to avoid the device in the "stopping" state, and the "execution status" is set to "standby" at the end of the tablet distributor execution management data (Figs. 10 and 11) corresponding to the device. Add one row of data. If there is no corresponding data in the medicine of the prescription data, the row data ("for example, in FIG. 10") set "execution status" to "none" at the end of the tablet distribution machine execution management data (FIGS. 10 and 11). Add prescription data No. "0011"). The "execution status" is also set to "none" even when called in the process of audit NG of "prescription audit input" described later (Fig. 16; step S406).

On the other hand, if it is determined in step S302 that there is no tablet distributor (when one "tablet distributor" which is the management target 4 is not set), it is determined whether there is a powder distributor (step S304). If one or more "powder distributors" which are the management targets 5 are set in the preparation execution management target setting file (FIG. 2), it is determined that there is a powder distribution machine, and it is added to the powder distribution machine execution management data (step S305). If one "product powder distributor" of management target 5 is not set, the process returns to step S100 without executing step S305. In addition to the powder dispenser execution management data, when there is data to be separately packaged with the powder dispenser in the medicine of the prescription data (determined by the type code of the drug is "distributed to the powder"), the powder spreader is divided into several units. In addition, the device is determined to avoid the device in the "stopping" state so as to equalize the processing load, and at the end of the powder dispenser execution management data (Fig. 12) corresponding to the device, the " waiting state " ", And add the row data (for example, refer to prescription data No." 0011 "in FIG. 12). When there is no corresponding data in the medicine of the prescription data, and when it is called in the process of the audit NG of "prescription audit input", the "execution status" is "none" at the end of the powder dispenser execution management data (FIG. 12). Add the row data set in.

The "addition of the preparation equipment execution management data" is a common process of adding row data to the preparation equipment execution management data (FIGS. 9 to 12) by judging from the equipment status of the preparation equipment 2, and will be described below. The same processing is also performed in the process of "prescribed audit input" (FIG. 16). When other models are provided, a determination step of whether there is a model and a step of adding to the execution management data of the model are added as one combination.

The "prescribed audit input" process is performed when the "prescribed audit input" of 2 to be managed is set in the preparation execution management target setting file (FIG. 2), and generates the execution process shown in FIG. To start.

In the process of "prescription audit input", first, the prescription audit input terminal apparatus 6a displays the "prescription audit input" screen (FIG. 19) in the initial state in which all data input fields are blank (step S400). In addition, on the preparation date, today's date indicated by the calendar clock 9 is displayed.

Then, in the prescription audit management data (FIG. 8), the row data in which the " execution status " is " standby " If there is no corresponding row data, it proceeds to the new input judgment (step S413) described later, and if there is corresponding row data, the "execution status" of the row data is set to "running" (step S402).

Next, the prescription data is read from the prescription file (FIG. 4) using the "prescription data No." of the retrieved row data, and the content is displayed on the "prescription audit input" screen (FIG. 19) (step S403). The labeling information is used by a pharmacist to thank from a pharmacological point of view.

As a result of the audit, if there is no problem, by clicking on the "Audit OK" button with a mouse (step S404), the procedure proceeds to the setting of the prescription audit management data "end", and the end time of the HHMMSS format is set in the "execution status" of the retrieved row data. (Step S405). Regarding the prescription data for the audit OK, each of the preparation devices 2 is operated according to the preparation device execution process (FIG. 18) described later. In addition, if there is a problem as a result of the audit, by clicking on the "Audit NG" button with a mouse (step S406), the procedure proceeds to "Cancel" of prescription audit management data, and "Cancel" in the "execution status" of the retrieved row data. Is set, and the "division" in the prescription file (FIG. 4) of the corresponding prescription data is set to "audit NG." (Step S407).

Subsequently, a procedure of "adding the preparation device execution management data" (FIG. 15) is called, and the same processing as above is executed (step S408). Then, it is judged whether or not the transmission of the audit result is necessary (step S409). When the "parameter" of "prescribed audit input" that is the management target 2 of the preparation execution management target setting file (FIG. 2) is 1, it is determined that transmission of the audit result is necessary, and the audit result of prescription data is transmitted to the host computer 12. (OK / NG) is transmitted (step S410), and the process returns to step S401 and is repeated from the prescription audit management data " wait " determination.

In this way, by sending the audit result to the host computer 12, the host computer 12 may initiate a pseudo accounting process, and a system for requesting a doctor to change the prescription may be constructed on the host computer side. Do.

Also, as a result of auditing, if neither the "Audit OK" button nor the "Audit NG" button is clicked but the "Cancel" button is clicked (step S411), the "execution status" of the retrieved row data is set to "wait". (Step S412), the prescription data is turned back and the process returns to the above-mentioned step S401 to be repeated from the prescription audit management data "wait" judgment, whereby the contents of the separate prescription data in the "wait" state are displayed.

Subsequently, if the "execution status" is not the row data of the "wait" state in step S401 and the "new input" button is clicked (step S413), arbitrary prescription data is newly inputted from the patient number (step S415). .

In this case, for example, if the keyboard is inputted with the patient number "93027561", the patient name (Kana, Kanji), sex, and date of birth are read and displayed from the patient master file. The age is automatically calculated and displayed from the date of birth and today's date. The exchange number is the number of the "drug exchange ticket" handed in advance at the end of the accounting only in the case of an outpatient. In the example of this prescription data (FIG. 19), since prescription classification is "03" hospitalization admitted (inpatient), and exchange number is meaningless, it inputs "0000". In the department of medical treatment, a doctor, a ward, and a prescription, name code is read and displayed from various corresponding master files when each code is input (for example, when the code "01" is input as a department of medical treatment, "medical" is displayed). The "prescription No." is a sequential number of "prescription" in which a chemical | medical agent (plural number) and a usage are combined. This "prescription" may be a plurality of inputs. The "code" input box is a column for inputting a medicine code or a usage code. If a code is entered, name data is read and displayed from the medicine master file or the usage master file. In the "code" input box, normally, a medicine code is input (for example, "シ ヨ ウ エ"), but when a "/" symbol is input at the head, a usage code is input later (for example, "301". The usage name corresponding to "301" is "three minutes, three weeks, one meal 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 amount of the medicine. Units (tablets, CAP; capsules, g, ml, etc.) are read and displayed from the drug master file. The "dose time" column is a column for recording the 1-time amount divided | segmented into every dose time which is a daily amount. In the case of solid preparations such as tablets, capsules, pills, and the like, the amount is once (integer), but in the case of powder, it is grams. The form code in the "Form" column is read from the medication master file and displayed. The form code is a code for classifying drugs into forms in the preparation operation. "Distribution" means automatically feeding and packaging from a drug supply. "Heat seal" means delivery to a patient as a packed heat seal package at a pharmaceutical manufacturer. "Distribution as a tablet" = 11, "Heat seal as a tablet" = 13, "Distribution as a capsule" = 14, "Heat seal as a capsule" = 16, "Distribution as a powder" = 17, "Heat seal as a powder" Enter == 19.

Next, when the "audit OK" button is clicked (step S416), the input prescription data is recorded in the prescription file (FIG. 4) (step S418). Regarding the prescription data of the audit OK, each of the preparation devices 2 is operated according to the preparation device execution process (Fig. 18) described later. If "prescription reception" as the management target 1 is set in the preparation execution management target setting file (FIG. 2) (step S420), the "execution status" is set to "none" at the end of the prescription reception management data (FIG. 7). One row of data is added (step S421). Then, at the end of the prescription audit management data (Fig. 8), the row data in which the end time of the HHMMSS format is set is added (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 erased (step S419), and the step returns to step S401, and the prescription audit is performed. From the management data " waiting " determination, the contents of the prescription data in the " waiting " state are displayed from the host computer 12. FIG.

If no button is clicked on, the procedure of "receiving execution management signal" (FIG. 14) is called (step S414), and the process returns to the step S401 and repeats from the determination of the management data "waiting".

The "execution machine execution" processing is set in the preparation execution management target setting file (FIG. 2) by the "medicine bag printing machine" of 3 managed objects, the "tablet dispenser" of 4 managed objects, or the "powder dispenser" of 5 managed objects. If so, the execution process shown in FIG. 18 is generated and the process of "executing apparatus execution" is started. In an example of the preparation execution management object setting file (FIG. 3), four preparation device execution processes are generated for each preparation device, and the execution status is recorded in each execution management data to be processed.

In the "manufacturing apparatus execution" process, first, the row data whose "reissue flag" is ON is retrieved from 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, the row data whose " execution status " is " standby " is retrieved from the execution management data (Figs. 9 to 12) (step S502). If there is no corresponding row data, the procedure " receive execution management signal " (FIG. 14) is called (step S503), and the process returns to step S500 to repeat from the execution management data reissue flag determination.

Subsequently, the "execution status" of the retrieved row data is set to "executing" (step S504). The prescription data is read from the prescription file (FIG. 4) using the "prescription data No." of the retrieved row data (step S505).

Here, after receiving the state of the preparation device 2 and waiting until it becomes "operable" state (step S506), the operation command created according to prescription data is transmitted to the preparation device 2, and it operates (step S507). ).

Thereafter, the state of the preparation device 2 is received and waited until the state of the "operation ends" (step S508). After setting the end time of the HHMMSS format in the "execution status" of the retrieved row data (step S509), the process returns to the step S500 and repeats from the execution management data reissue flag determination.

In this way, the reissue operation can be centrally managed by simply setting the "reissue flag" to "ON" or "OFF" in the execution management data. In addition, the priority of execution of the patient is changed by retrieving the row data in which the "reissue flag" is set to "ON" and then retrieving the row data in which the "execution status" is "wait". Can be minimized.

As apparent from the above description, according to the preparation control device according to the present invention, it is possible to manage and control a large number of preparation devices in the same manner. For this reason, it is not necessary to design and manufacture to an individual specification even if the facility differs in the number and model of preparation equipment, and it can cope easily also when adding more preparation equipment. In addition, the operation can be simplified because the preparation equipment can be monitored and operated. In addition, the same effect can be obtained in connection with a host computer and in response to a facility where equipment conditions of prescription reception and prescription audit input are different.

In the preparation execution management target setting file, data can be managed in the same manner as the preparation device by "prescription reception" and "prescription audit input", which further simplifies operation.

In accordance with the instructions for deleting prescription data and correction instructions from the host computer, automatically and immediately delete / modify the operation of the preparation, minimizing the effort and drug loss caused by useless preparation even in the event of cancellation or change of prescription. It can be suppressed.

By sending the audit result to the host computer 12, it is possible to easily cope with the case of constructing a system in which the host computer side starts a medical system process or requests a doctor to change the prescription.

By displaying the prescription reception, the prescription audit input, and the execution status of each preparation device on the monitor screen, the entire preparation device can be monitored in the same manner, and each preparation can be prevented from staying due to an error or the like.

By monitoring the prescription audit input and the execution time of each preparation device and notifying when the predetermined time is exceeded, it is possible to prevent the patient's waiting time from becoming extremely long.

Since the reissue is concentrated and the instruction can be made, the trouble of operation can be reduced.

Then, the reissue operation can be given priority over the normal operation, and the extension of the waiting time of the patient can be minimized.

By making it possible to cancel the prescription audit input and the operation of each preparation device with a simple operation, it is possible to flexibly cope with an abnormal situation such as a failure caused by the host computer's cause and a failure of the preparation device and changing to manual preparation. .

Receipt of prescriptions, input of prescription audits, and the operation of each dispensing device can be stopped / started with a simple operation to prevent an increase in the number of operation commands that cannot be processed, such as when the drug distributor stops due to insufficient distribution sites. can do. In addition, it is possible to flexibly cope with abnormal situations.

Claims (10)

In the preparation control device for driving control of a plurality of preparation devices in order to prepare the prescription according to the prescription data, A hard disk device for storing a preparation execution management object setting file which sets a management object including the preparation device; According to the prescription data, execution management data and an execution process are generated for each management object of the preparation execution management object setting file stored in the hard disk device, and drive control of the corresponding preparation device is performed in accordance with the execution management data and the execution process. Formulation control device comprising a central processing unit. The prescription prescription according to claim 1, wherein said hard disk device is a management object stored in a preparation execution management object setting file, and includes "prescription reception" used for reception of prescription data from a host computer and a "prescription audit input" used for auditing prescription data. Pharmacy control device comprising a. The processor according to claim 1 or 2, wherein when the host command is input from the host computer, the central processing unit searches for and deletes the prescription data prior to the correction and deletes the correction data when the host command includes the correction command. And adding the prescription data, and setting the corresponding execution management data to cancel when the delete command is included in the host command. The processor according to any one of claims 1 to 3, wherein the central processing unit displays the audit input of the prescription data received from the host computer on the monitor screen, and transmits the audit result input from the monitor screen to the host computer. Formulation control device, characterized in that. 5. The preparation control device according to any one of claims 1 to 4, wherein the central processing unit displays the execution status on a monitor screen for each management object stored in the preparation execution management object setting file. . 6. The CPU according to any one of claims 1 to 5, wherein the central processing unit monitors execution time for each management object stored in the preparation execution management object setting file, and if the execution time exceeds the monitoring time. The preparation control device characterized by the notification. The central processing unit according to any one of claims 1 to 6, wherein, when a reissue is input from an input device, the central processing unit resumes the operation of the reissued management object among the management objects stored in the preparation execution management object setting file. Formulation control device, characterized in that. 8. The preparation control device according to claim 7, wherein said central processing unit gives priority to said reissue operation over normal operation. The method according to any one of claims 1 to 8, wherein, when the central processing unit cancels input from the input device, the execution status of the canceled input prescription data for the management target stored in the preparation execution management target setting file is changed. Only in the case of "waiting", the preparation control device characterized in that the operation of the corresponding management object is canceled. The stop or start signal according to any one of claims 1 to 9, wherein the central processing unit transmits a stop or start signal to an execution process corresponding to the selected management object according to the stop or start input when the stop or start input is performed from an input device. Formulation control device, characterized in that.