JP4580456B2 - Dispensing equipment controller - Google Patents

Description

  The present invention relates to a dispensing device control device for controlling various dispensing devices for dispensing operations based on prescription data, such as a medicine packaging machine and a medicine bag printer used in medical institutions such as hospitals and dispensing pharmacies. is there.

  Conventionally, in a control device that operates a medicine packaging machine for inputting prescription data and dividing and packaging medicines in the form of tablets or powders into wrapping paper, it controls a plurality of medicine packaging machines. Control of a medicine bag printing machine for creating a medicine bag for storing medicines with a name and a method of taking the medicine.

  For example, Patent Document 1 describes a medicine packaging apparatus that can operate a plurality of medicine packaging machines with one console using a medicine data table.

  Patent Document 2 describes a tablet packaging device that transmits prescription data to a non-operating tablet packaging machine and centrally controls a number of tablet packaging machines with a single controller.

  Furthermore, Patent Document 3 describes a dispensing control device that assigns data from a host computer to an input device of a dispensing machine that is suitable for the type of dispensing.

  Furthermore, Patent Document 4 describes a dispensing system control device that reduces the dispensing time by reducing the additional input of chemicals manually and averaging the operation of each machine when using a plurality of tablet packaging machines. ing.

  However, in any of the above control devices, it is necessary to change the control method for each type of dispensing device. In addition, since the types and number of dispensing devices differ from facility to facility, it is necessary to design and manufacture according to individual specifications for each facility. In addition, the equipment and the monitoring method are different for each model, and the operation at the time of use is complicated. In particular, in a medicine packaging machine and a medicine bag printing machine, it is desired to specialize each machine in hospital / outpatient classification, but none of the above-mentioned control devices can cope with it.

  Further, in any of the above control devices, measures are not sufficient when the dispensing device stops due to an error. 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, in a busy dispensing room, there is a problem that partial work (tablet / capsule packaging work, medicine bag creation work, etc.) stays without anyone noticing. This problem becomes more apparent as the number and type of dispensing devices increase. Accordingly, it is desired to disable the corresponding dispensing device in order to intensively monitor the usage status and take time to recover, in order to avoid the retention of partial work. In addition, in order to investigate the cause of the failure, it is also desired to be able to grasp information about the error occurrence status.

Japanese Patent Publication No. 64-9201 Japanese Patent Publication No. 3-59 Japanese Patent Publication No. 4-57348 JP-A-6-312010

  Then, this invention makes it the 1st subject to provide the control apparatus for dispensing apparatuses which can set easily multiple types or multiple dispensing apparatuses with the same method.

  Moreover, this invention makes it the 2nd subject to provide the control apparatus for dispensing apparatuses which can unify and manage the occurrence condition of the error of a dispensing apparatus accurately.

As a means for solving the above problems, the present invention provides:
In a dispensing device control device that drives and controls multiple types or multiple dispensing devices based on prescription data,
Before each Sulfur butterfly agent device, a hard disk device that stores use condition setting file consisting of conditions, including a limited-time zone to limit the dedicated prescription segment in the time zone set,
A central processing unit that selects a usable dispensing device based on the use conditions for each dispensing device stored in the prescription data and the use condition setting file;
With
The use condition setting file stored in the hard disk device includes a model ID number assigned to each model, and a machine number assigned to each machine for each model,
The central processing unit determines whether or not the limitation / time zone is valid as a use condition, and if it is determined to be valid, the use of the corresponding dispensing device in the set time zone according to the limited prescription category The condition is determined.

  With this configuration, when prescription data is input, a usable dispensing device can be automatically selected based on the use condition setting file. In addition, since the usage condition setting file stores data related to the usage conditions of each dispensing device, it is possible to manage all the dispensing devices in an integrated manner. That is, it is no longer necessary to design and manufacture each facility for each specification, and even when dispensing equipment is added, there is no need to modify the control device, and the operation at the time of use is simplified.

  In this case, if the usage condition setting file stored in the hard disk device includes a prescription classification indicating either an outpatient prescription, an inpatient prescription, or no designation, a plurality of each unit is dedicated to the inpatient / outpatient classification. This is preferable in that it can be used and the efficiency of the entire dispensing operation can be improved.

  Each model includes a medicine packaging machine, a medicine bag printing machine, a powder dispensing inspection machine, a liquid medicine dispensing inspection machine, and a liquid medicine packaging machine. When a new model is added, a use condition setting file stored in the hard disk device It is preferable to add a model ID number and increase the number if the number of units increases.

  The central processing unit specifies the dispensing device to be operated based on the form code included in the prescription data, obtains the use condition from the machine number of the specified dispensing device, determines the machine that matches the use condition, It is preferable to send an operation command unique to each model to the machine.

  In addition, it is preferable that the use status of each dispensing device is displayed in a list on the monitor screen by the central processing unit, so that early detection of errors can be made and retention of partial work of dispensing can be prevented.

  Further, when it is determined by the central processing unit that there is no usable dispensing device based on the prescription data and the use condition setting file, the prescription data is temporarily stored and the error status is displayed on the monitor screen. This is preferable in that the retention of partial work of the preparation can be prevented more effectively.

Further, the present invention provides a means for solving the second problem, wherein a serious error setting file comprising serious errors that can be arbitrarily set among errors generated in the respective dispensing devices by the hard disk device. Remember,
The central processing unit determines whether an error signal input from one of the dispensing devices corresponds to a serious error in the serious error setting file.

  With this configuration, it is possible to arbitrarily set a serious error for each dispensing device, and it is possible to perform unified management using a serious error setting file.

  Then, if the error signal input from one of the dispensing devices corresponds to a serious error in the serious error setting file by the central processing unit, the user is allowed to display the serious error status on the monitor screen. It is preferable in that the error situation can be easily grasped, and the corresponding dispensing device can be disabled, so that it is possible to respond accurately and promptly.

  If the error signal input from one of the dispensing devices corresponds to a serious error in the serious error setting file by the central processing unit, an error countermeasure is displayed on the monitor screen. It is preferable in that the error can be accurately and promptly repaired without checking the operation manual.

  Furthermore, if the error signal input from any one of the dispensing devices corresponds to a serious error in the serious error setting file by the central processing unit, the dispensing device is disabled and allocation of prescription data is stopped. It is preferable in that the retention of partial work can be automatically avoided.

  In addition, if the error signal input from one of the dispensing devices corresponds to a serious error in the serious error setting file by the central processing unit, the serious error status is recorded in the serious error recording file. It is preferable in that it can be easily grasped.

  According to the present invention, it is possible to easily handle a plurality of types or a plurality of dispensing devices in the same method. In other words, the control device design and production can be simplified and the operation at the time of use can be unified in the facility corresponding to various facilities with different dispensing equipment. Furthermore, it is possible to smoothly deal with errors.

It is a block diagram which shows the apparatus structure of the control apparatus of a dispensing apparatus. It is a table | surface which shows the memory content of a use condition setting file. It is a graph which shows the memory content of a serious error setting file. It is a chart which shows the storage contents of a serious error record file. It is a flowchart which shows the process of control of a dispensing apparatus. It is a figure which shows the screen of prescription data input. It is a figure which shows the screen of a usage condition monitor. It is a flowchart which shows the process of monitoring a dispensing apparatus and an error condition. It is a flowchart which shows the process of execution of dispensing apparatus and operation | movement. It is a flowchart which shows the process of execution of dispensing apparatus and operation | movement.

  Embodiments according to the present invention will be described below with reference to the accompanying drawings.

  FIG. 1 shows a dispensing device control device 1 according to the present embodiment and a plurality of dispensing devices 2 that are driven and controlled by the control device 1.

  The dispensing device control device 1 includes a central processing unit 3 (CPU), a hard disk device 4, a multi-channel communication unit 5, a CRT display 6, a keyboard 7, and a mouse 8.

  The central processing unit 3 (CPU) incorporates a memory 9 (RAM) for storing various data and a control program 10 (ROM) for controlling the entire control device. The memory 9 (RAM) is used as a prescription data memory for storing prescription data and other memories (a work area, variables, etc. in processing).

  The hard disk device 4 includes a use condition setting file 11 for setting use conditions for each model / unit, a serious error setting file 12 for setting a serious error for each model, and a serious error recording file 13 for recording occurrence of a serious error. It consists of various master files that store relevant information when inputting prescription data. The hard disk device 4 can be any rewritable nonvolatile storage device such as a flash memory.

  The use condition setting file 11 is a data file that registers various data such as unusable, exclusive / prescription classification, etc. for each equipped model / unit as the use conditions of a plurality of models or a plurality of dispensing devices 2. The stored contents of the use condition setting file 11 are as shown in FIG.

  In FIG. 2, the model indicates the ID number of the model of the dispensing device 2. For example, 1 is input for the “tablet packaging machine” and 2 is input for the “medicine bag printing machine”. When a new model is added, a model ID number is added to deal with it. The unit number indicates the number of the unit for each model of the dispensing device 2. If the number of units increases, respond by increasing the unit number. In the unusable flag, 0 is input if the use of the car is “permitted”, and 1 is input if it is “unusable”. The dedicated / prescription category indicates a dedicated prescription category in the allocation of the prescription data of the machine. For example, 0 is input for “not specified” (all prescriptions), 1 for “hospital prescription / exclusive”, and 2 for “outpatient prescription / exclusive”. The prescription classification is not limited to the inpatient / outpatient classification, and the inpatient prescription may be further classified into details such as a regular inpatient prescription, a temporary admission prescription, and a discharge prescription. The limitation / time zone indicates a time zone that limits the specialization of the “dedicated / prescription category”. To specify “limited / time zone”, select the “valid” check box (marked with □) (click on it with a mouse to mark it) and enter the limited time range.

  Specifically, in the No. 1 tablet packaging machine, since “limited / time zone” is effective as a use condition, it is only for outpatient use (outpatient prescription / exclusive use) within the range of “8:00 to 13:00”. At other times, it is outside the range of “Limited / Time zone”, so it is a dedicated “No designation” (that is, hospital prescription is also possible). On the other hand, the first use of the medicine bag printing machine is dedicated for outpatient use for 24 hours at all times because the “limitation / time zone” is not effective.

  If the limitation is not effective, it means “always, 24 hours”. The stored contents correspond to the device configuration of FIG. 1, model 1 “tablet packaging machine” is connected to M units, model 2 “medicine bag printing machine” is connected to L units, and other models N continue. . Also, the data of the use condition setting file 11 (FIG. 2) is a use condition setting registration screen that is activated from a menu screen (not shown because it is a screen that only has start buttons) (not shown because it has the same screen structure as the file structure). Enter in.

  The serious error setting file 12 is a data file for arbitrarily registering a serious error that is different for each model of the dispensing device 2. The stored contents of the serious error setting file 12 are as shown in FIG. In FIG. 3, the model indicates the ID number of the model of the dispensing device 2. Enter 1 if it is a “tablet packaging machine” and 2 if it is a “medicine bag printing machine”. The severe error number indicates a serious error number that is different for each model. Of the error numbers received from the dispensing device 2, only the error numbers judged to be serious are input. The severe error status is obtained by inputting the status of the severe error with an arbitrary character string. The error countermeasure is a method for inputting a countermeasure method for a serious error in an arbitrary character string. Severe error status and error countermeasure data are displayed on a “use status monitor” screen (FIG. 7) to be described later. The data of the serious error setting file 12 (FIG. 3) is input on a serious error setting registration screen (not shown) because it is the same as the file structure, which is activated from a menu screen (not shown).

  The serious error recording file 13 is a file for recording the occurrence status of a serious error. As shown in FIG. 4, the data of the serious error recording file 13 is recorded with a serious error number for each occurrence date / time / model / unit. The contents of the serious error recording file 13 are checked by a maintenance service person by converting it into a CSV (comma delimited) format file and displaying it in a list format using spreadsheet software.

  Various master files include drug master, patient master, usage master, 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.

  The multi-channel communication unit 5 is used for communication with each unit of the dispensing device 2. The CRT display 6, the keyboard 7, and the mouse 8 are used for inputting prescription data and various files.

  The dispensing device 2 is mainly a medicine packaging machine or a medicine bag printing machine. Besides this, a dispensing medicine inspection machine for auditing powder dispensing, a medicine dispensing inspection machine for auditing medicine dispensing, a medicine dispensing machine, etc. Devices are included, and one or more models or one or more devices are connected to the control device 1. A model ID number is assigned to each model of the dispensing device 2 and a machine number is assigned to each model for each model, which is used for identification and control. When a new model is added, a model ID number is added to deal with it. If the number of units increases, respond by increasing the unit number. The 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 can be employed.

  Reference numeral 14 denotes a host computer used for receiving prescription data from an external system. However, since the prescription data can be newly input only with the CRT display 6, the keyboard 7, and the mouse 8, the host computer 14 is not necessarily required.

  Further, the central processing unit 3 (CPU), the CRT display 6, the keyboard 7, the mouse 8, and the hard disk device 4 may be constituted by a personal computer. The hard disk device 4 may be an independent file server device (built-in CPU), and the central processing device 3 (CPU) may be connected to the server device as a client terminal via a network (LAN). 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.

  Next, the case where the control device 1 controls the drive of the tablet packaging machine and the medicine bag printing machine will be described with reference to the flowchart shown in FIG.

  First, a control screen is displayed on the CRT display 6 from a menu screen (not shown because it is a screen where only start buttons are arranged) (step S1). The control screen refers to the “prescription data input” screen shown in FIG. 6 and the “usage status monitor” screen shown in FIG. 7, which are displayed in separate windows. In addition, the CRT display 6 may be provided separately for the usage status monitor screen for monitoring the dispensing device 2 and displayed there.

  Therefore, the display screen to be operated is set as an “input prescription data” screen (FIG. 6). On the “input prescription data” screen, all the data input fields are in an empty initial state, so prescription data is input (step S2). The prescription data is input by receiving data from the host computer 14 or inputting from the keyboard 7 and mouse 8. On the dispensing date, today's date engraved by a calendar clock built in the central processing unit 3 (CPU) is displayed. Further, the contents of the prescription data received from the host computer 14 are displayed in other blanks. Since the data received from the host computer 14 is composed only of various codes in order to reduce the amount of communication data, when displaying the contents of the prescription data, the names from the various master files are used with the various codes as search keys. Data is read out. For example, since only the drug code “Shioe” is stored in the received data, the drug name “Tablet A” is read from the drug master file. Note that the drug code is a unique code for each drug, for example, shortened from the abbreviation of the drug by removing the cloud point so that the pharmacist can easily input the drug code (for example, “Jouzaie” is “Shioe”). If the pharmacist audits the contents of the displayed prescription data and there is no problem, the pharmacist clicks the “input OK” button with the mouse 8. The contents of the prescription data can be arbitrarily changed using the keyboard 7 and the mouse 8.

  In the “prescription data input” screen, the exchange number indicates the number of the “subscription voucher” that is handed over in advance at the end of the transaction only for outpatients. In the example of this prescription data (FIG. 6), the prescription classification is “02” hospitalized (inpatient), and the exchange number is meaningless, so “0000” is displayed. When each code is input, the name data is read from the corresponding various master files and displayed in the clinical department, doctor, ward, and prescription category. (For example, when the code “01” is entered in the clinical department, “Internal Medicine” is displayed.) The “Prescription No.” field is a serial number of “Prescription” in which a drug (multiple) 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, “201”. The usage name corresponding to “201” is “minute 2 morning / 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. Units (tablets, capsules, g, ml, etc.) are read from the drug 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, “Sealing with tablets” = 13, “Packaging with capsules” = 14, “Sealing with capsules” = 16, “Packaging with powders” = 17, “With powders” Enter “heat seal” = 19. When the “new input” button is clicked, the prescription data being displayed at that time is saved to save later, the display is erased, and arbitrary prescription data can be newly input from the patient number. In this case, for example, when the patient number “93026571” 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. When the “input OK” button is operated, a “dispensing device / error status monitoring” process is performed (step S3).

  In the dispensing device 2 / error status monitoring process, as shown in the flowchart of FIG. 8, first, use condition setting data (row record) is obtained from the use condition setting file 11 (FIG. 2) (step S11).

  Then, it is determined whether or not the unusable flag is 1 (unusable) (step S12). If the unusable flag in the use condition setting data is “unusable”, the model No. M of the model N is unusable, and the process proceeds to the end determination (step S18). On the other hand, if the unusable flag in the use condition setting data is “permitted”, an error status signal (error number) is received from the model No. M of the model N set in the use condition setting data (step S13).

  Subsequently, it is determined whether or not a serious error has occurred (step S14). That is, the data of the model N in the serious error setting file (FIG. 3) is searched to determine whether or not the received error number is set as a serious error number. If it is not set as a serious error number, it is a normal error and the process proceeds to the end determination (step S18).

  On the other hand, if it is set as a serious error number, the unusable flag of the use condition setting data in the use condition setting file 11 (FIG. 2) is set to “impossible” (step S15). Then, as shown in FIG. 7, “unusable” is displayed in the “unusable flag” column of the “usage status monitor” screen, and the severe error number and the severe error status are displayed in the “serious error” column (step S16). .

  In the “Usage Status Monitor” screen, the contents of the usage condition setting file 11 (FIG. 2) are displayed as they are in the “Model”, “Unit Number”, and “Unusable Flag” fields. In the next “dedicated / prescription category” field, the status at the current time is displayed based on the contents of the use condition setting file 11 (FIG. 2). For example, the first time of the tablet packaging machine in FIG. 7 is “09:05” and is within the range of “limited / time zone” in the use condition setting file 11 (FIG. 2). In the “Prescription category” field, “2 (external only)” is displayed as the current situation. Then, “0 (no designation)” is displayed when it is out of the range of “limited / time zone”. Further, the “severe error” column displays the error occurrence number and status based on the contents of the serious error setting file (FIG. 3). The “★” mark and the highlighted line indicate line data to be processed, and the line can be arbitrarily moved by clicking the up / down arrow keys or the mouse 8. In the “error countermeasure” column, if a serious error is included in the row data, the countermeasure is displayed. The error countermeasure is the content set in the severe error setting file (FIG. 3). The “unusable / unusable” button is used to switch the contents of the unusable flag of the row data alternately between “1 = unavailable” and “0 = enabled” each time it is clicked, and to set / cancel the uselessness arbitrarily It is. The “Cancel” button is for deleting the window.

  Further, the occurrence status of the serious error is recorded in the serious error recording file 13 (FIG. 4) (step S17). This recorded content can be confirmed later by a maintenance service person, and it is possible to accurately grasp the operating status of the dispensing device 2 and take appropriate measures.

  Thereafter, it is determined whether or not the use condition setting data acquired from the use condition setting file 11 (FIG. 2) has ended (step S18). If completed, the process returns to step S4 in FIG. 5, and if not completed, the next use condition setting data is retrieved (step S19), and the process returns to step S11 to repeat from the data acquisition.

  When the “dispensing device / error status monitoring” process is completed, the process returns to step S4 in FIG. 5 to determine whether or not to operate the tablet packaging machine. This is performed by determining whether or not “tablet” or “capsule” to be automatically packaged by the tablet packaging machine is present in the drug of the prescription data based on the form code of the drug.

  If there is a corresponding form code of the medicine, it is determined that the tablet packaging machine is operated, and the operation of the dispensing device (argument: model = 1 “tablet packaging machine”) is executed (step S5). Specifically, as shown in the flowchart of FIG. 5, the “dispensing device / execution execution” procedure is executed by calling “1” (tablet packaging machine) with the argument model set to “1”.

  In the “execution of dispensing device / operation” process, as shown in the flowcharts of FIGS. 9 and 10, first, the model of the argument is set to the variable N (model) (step S21), and the variable M (unit number) is set to “ 1 ”is initialized (step S22). Then, the usage condition setting data (row record) of “M model No. M” is acquired from the usage condition setting file 11 (FIG. 2) (step S23).

  Here, it is determined whether or not the unusable flag is 1 (unusable) (step S24). If the unusable flag of the use condition setting data is “unusable”, the model N / M is unusable, and the process proceeds to the end determination of the car (step S29). On the other hand, if the unusable flag in the use condition setting data is “permitted”, it is determined whether the “prescription category” in the prescription data (FIG. 6) matches the “dedicated / prescription category” in the use condition setting data (step S25). ). If “dedicated / prescription category” is “not specified” (all prescriptions), it is determined that they match.

  If the “prescription category” matches the “dedicated / prescription category” in the use condition setting data, the M machine is set as a usable candidate in step S28, and then the end of the machine is determined (step S29). However, the final number is determined in a later processing step (step S32). On the other hand, if it does not match the “dedicated / prescription category”, it is determined whether or not the time zone is valid (step S26). The time zone is valid if the “valid” check box (□) in the “limited / time zone” of the use condition setting data is on (∨), and is invalid if it is off (no tick). .

  If the time zone is valid, it is determined whether or not the current time is within the time zone range (step S27). This determination is made based on whether or not the current time recorded by the calendar clock built in the central processing unit 3 (CPU) is within the “limited / time zone” range of the use condition setting data. If the current time is within the range of the time zone, the process proceeds to the end determination of the unit (step S29). If not, the unit M is set as a usable candidate in step S28, and then proceeds to the end determination of the unit ( Step S29).

  In the end determination of the number machine, it is determined whether or not the model number N is ended in the use condition setting data acquired from the use condition setting file 11 (FIG. 2). If the number has not ended, the variable M (the number of the number) is set to “+1” (M ← M + 1) (step S30), and the process is repeated from the acquisition of the next use condition setting data. On the other hand, if the number machine has been completed, it is determined whether or not there is a usable candidate (step S31).

  If there is an available candidate, the actual number to be used is determined from the usable candidate numbers (step S32). As a determination method, there are a method for equalizing the number of prescription data assigned to the number machine, a method for assigning to an appropriate number machine according to the type of medicine in the prescription data, and the like. Then, an operation command unique to each model is transmitted to the machine determined in model N (step S33). For example, if the model is a tablet packaging machine, it is a packaging command, and if it is a medicine bag printing machine, it is a printing command.

  On the other hand, if there is no usable candidate, the prescription data is saved so as not to be erased (step S34). The saved prescription data is again displayed on the “input prescription data” screen (FIG. 6). Then, an error status indicating that there is no unit that can be operated is displayed on the usage status monitor screen (FIG. 7) (step S35).

  When the “dispensing device / operation execution” process is completed as described above, the dispensing device 2 / operation execution (argument: model = 2 “medicine bag printing machine” is executed in step S6 of “dispensing device control” (FIG. 5). ")I do. This processing is performed by calling the “dispensing device / execution execution” procedure (FIG. 9) by setting “2” (medicine bag printing machine) as the argument model.

  Thereafter, it is determined whether or not the prescription data is completed (step S7). When the “Cancel” button is clicked on the prescription data input screen (FIG. 6), the prescription data input screen is terminated and the screen returns to the menu screen (not shown). If the “cancel” button is not clicked, the process returns to step S2 and repeats from the prescription data input.

  When connecting other models, the determination step for determining whether or not to operate the model is combined with a step for calling the “Execute Dispensing Equipment / Operation” procedure with the model ID number of the model as an argument. to add. However, the medicine bag printing machine is exceptionally required to be operated for any prescription data, so that the step of determining whether or not to operate is not necessary.

DESCRIPTION OF SYMBOLS 1 ... Control apparatus 2 ... Dispensing apparatus 3 ... Central processing unit 4 ... Hard disk apparatus 5 ... Multichannel communication part 6 ... CRT display 9 ... Memory 10 ... Control program 11 ... Use condition setting file 12 ... Severe error setting file 13 ... Severe error Recording file 14 ... Host computer

Claims (11)

In a dispensing device control device that drives and controls multiple types or multiple dispensing devices based on prescription data,
Before each Sulfur butterfly agent device, a hard disk device that stores use condition setting file consisting of conditions, including a limited-time zone to limit the dedicated prescription segment in the time zone set,
A central processing unit that selects a usable dispensing device based on the use conditions for each dispensing device stored in the prescription data and the use condition setting file;
With
The use condition setting file stored in the hard disk device includes a model ID number assigned to each model, and a machine number assigned to each machine for each model,
The central processing unit determines whether or not the limitation / time zone is valid as a use condition, and if it is determined to be valid, the use of the corresponding dispensing device in the set time zone according to the limited prescription category A controller for a dispensing device, characterized in that a condition is determined.   2. The dispensing device control device according to claim 1, wherein the use condition setting file stored in the hard disk device includes a prescription section indicating any one of an outpatient prescription, an inpatient prescription, and no designation. Wherein the each model, medicine packing machine, medicine bag printing machine, powder dispensing audit machines, liquid medication dispensing auditing machine, contains liquid medication packing machine, when you add a new model, the hard disk drive using condition setting file to be stored in 3. The dispensing device control device according to claim 1 or 2 , wherein a model ID number is added, and the number of the machine is increased when the number of machines is increased. The central processing unit specifies the dispensing device to be operated based on the form code included in the prescription data, obtains the use condition from the machine number of the specified dispensing device, determines the machine that matches the use condition, 4. The dispensing device control device according to claim 3, wherein an operation command unique to each model is transmitted to the machine. The said central processing unit displays the usage condition of each dispensing apparatus as a list on a monitor screen, The control apparatus for dispensing apparatuses of any one of Claim 1 to 4 characterized by the above-mentioned. When the central processing unit determines that there is no usable dispensing device based on the prescription data and the use condition setting file, the central processing unit temporarily stores prescription data and displays an error status on the monitor screen. The control apparatus for dispensing apparatuses according to any one of claims 1 to 5 , wherein: The hard disk device stores a serious error setting file including a serious error that can be arbitrarily set among errors generated in each dispensing device,
The central processing unit, the error signal input from any one of the dispensing device, either the claim 1, characterized in that determining whether corresponds to severe error serious error set in the file 6 The control apparatus for dispensing apparatuses of Claim 1. The central processing unit, if applicable to serious error in the one in the error signal serious error setting file inputted from the dispensing device, in claim 7, characterized in that to display the critical error conditions on a monitor screen The controller for dispensing equipment as described. The central processing unit, according to claim 7 where the error signal inputted from any one of the dispensing devices if applicable to serious error in serious error setting file, and wherein the displaying the error measures the monitor screen Dispensing equipment controller. If the error signal input from one of the dispensing devices corresponds to a serious error in the serious error setting file, the central processing unit sets the dispensing device to be unusable, and after setting the unusable, 8. The dispensing device control device according to claim 7 , wherein assignment of prescription data to the dispensing device is stopped. The central processing unit, if an error signal input from one of the dispensing devices corresponds to a serious error in a serious error setting file, records the serious error situation in a serious error recording file. Item 8. A dispensing device control device according to Item 7 .

Images