JP7276536B2 - Dispensing control system and dispensing control method - Google Patents

Description

The present invention relates to a dispensing control system and a dispensing control method.

Dispensing devices that execute dispensing processing based on prescription data are known. For example, there is known a dispensing device in which a robot fully automatically executes dispensing processing based on prescription data.

JP 2013-052250 A

Among the dispensing devices as described above, there are dispensing devices that can automatically start a dispensing process when prescription data is entered or received. Some users of such dispensing devices want the dispensing process to start automatically, while others want the dispensing process to start after a prescribed authority has confirmed the prescription information. There are users. Also, some users may wish to initiate the dispensing process in certain cases after the prescription information has been verified by a predetermined authority, and in other cases to initiate the dispensing process automatically. In this respect, conventionally, the method of starting dispensing processing sometimes does not match the user's desire, and the user's convenience is not sufficient.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and an object of the present invention is to provide a dispensing control system and a dispensing control method capable of improving user convenience.

In order to solve the above-mentioned problems, a dispensing control system according to the present invention is a dispensing control system capable of automatically starting dispensing processing by dispensing execution means, in which target prescription data to be subjected to the dispensing processing is acquired. setting data storage means for storing setting data set for determining whether to restrict the automatic start of the dispensing process; setting data for automatically starting the dispensing process based on the setting data; judgment means for judging whether or not to restrict the start; and, when it is judged that the automatic start of the dispensing process is not to be restricted, the dispensing executing means automatically starts the dispensing process of the target prescription data. (1) a start control means for executing the dispensing process of the target prescription data when it is determined that the automatic start of the dispensing process is to be restricted, and when an instruction to start the dispensing process is received from a predetermined authorized person; and a second start control means for starting at.

Further, a dispensing control method according to the present invention includes a prescription data obtaining step of obtaining target prescription data to be subjected to dispensing processing, and a setting set for determining whether or not to restrict automatic start of the dispensing processing. a judgment step of judging whether or not to restrict the automatic start of the dispensing process based on the data; a first start control step for causing the dispensing execution means to start the process; and when it is determined that the automatic start of the dispensing process is to be restricted, and when an instruction to start the dispensing process is received from a predetermined authorized person, the target prescription data. and a second start control step of causing the dispensing execution means to start the dispensing process of.

Further, in one aspect of the present invention, the setting data includes conditions related to prescription data that require restriction of the automatic start of the dispensing process, or conditions related to prescription data that do not need to restrict the automatic start of the dispensing process. may be set. The dispensing control system may include target prescription data determination means for determining whether or not the target prescription data satisfies the conditions. The determination means may determine whether or not to limit the automatic start of the dispensing process based on the determination result of the target prescription data determination means.

In one aspect of the present invention, the condition may include a condition regarding whether or not the target prescription data includes a specific drug as a drug to be provided to the patient.

In one aspect of the present invention, the conditions may include conditions related to patient data included in the target prescription data.

In one aspect of the present invention, the prescription data acquisition means may acquire prescription data input from another system as the target prescription data. The other system may be audited against prescription data. The condition may include a condition as to whether or not the result of the inspection of the target prescription data is a predetermined result.

Further, one aspect of the present invention may include display control means for causing the display means to display an input screen for accepting input of prescription data. The prescription data acquisition means includes first prescription data acquisition means for acquiring prescription data input through the input screen as the target prescription data, and acquisition of prescription data input by another system as the target prescription data. and a second prescription data obtaining means for obtaining the prescription data. The condition may include a condition as to whether the target prescription data is prescription data input via the input screen or prescription data input by the other system.

In one aspect of the present invention, the condition includes a condition as to whether or not the target prescription data is prescription data identical or similar to prescription data that has been prescribed to the same patient in the past. good too.

In one aspect of the present invention, the condition may include a condition as to whether or not dispensing processing of prescription data identical or similar to the target prescription data has been executed by the dispensing executing means in the past. good.

Further, in one aspect of the present invention, the determination means determines whether the target prescription data is the same or similar to prescription data that has been prescribed to the same patient in the past. If the dispensing process of prescription data identical or similar to the data has never been executed by the dispensing executing means in the past, it may be determined that the automatic start of the dispensing process is restricted.

Further, in one aspect of the present invention, the condition is that a person who is currently logged in to the dispensing control system has previously executed dispensing processing of prescription data identical or similar to the target prescription data by the dispensing executing means. A condition may be included as to whether or not the user is the same as the person who logged in to the dispensing control system when the user entered the dispensing control system.

Further, in one aspect of the present invention, the conditions may include conditions related to the time required to execute the dispensing process predicted based on the target prescription data.

Further, in one aspect of the present invention, the setting data includes conditions related to prescription data that require restriction of the automatic start of the dispensing process, or conditions related to prescription data that do not need to restrict the automatic start of the dispensing process. may be set. The dispensing control system may include immediately preceding prescription data determination means for determining whether or not the prescription data that was the object of the dispensing process executed immediately before satisfies the conditions. The judging means may judge whether or not to limit the automatic start of the dispensing process based on the judgment result of the immediately preceding prescription data judging means.

Further, in one aspect of the present invention, the setting data includes a condition related to a day or time when the automatic start of the dispensing process needs to be restricted, or a day or time when the automatic start of the dispensing process does not need to be restricted. may be set. The dispensing control system may include date and time determination means for determining whether or not the conditions are satisfied at present. The judgment means may judge whether or not to restrict the automatic start of the dispensing process based on the judgment result of the date and time judgment means.

Further, one aspect of the present invention may include an authorized person setting means for setting the authorized person based on the target prescription data.

Further, in one aspect of the present invention, an authorized person storing authorized person specifying data for specifying an authorized person capable of instructing the start of the dispensing process of the prescription data in association with the conditions related to the prescription data. A specific data storage means may be included. The authorized person setting means sets the authorized person based on the authorized person specifying data associated with the condition when the target prescription data that is the target of the dispensing process satisfies the condition. good too.

Further, in one aspect of the present invention, the authorized person setting means may include means for setting the authorized person based on the prescription data that was the object of the dispensing process executed immediately before.

Further, in one aspect of the present invention, the target prescription data that is the target of the dispensing process, the authority data related to the authority who instructed the start of the dispensing process, and the comment data input by the authority are associated. A registration means for registering the information in a predetermined storage means may be included.

In one aspect of the present invention, the dispensing execution means includes (a) an automatic dispensing/splitting device or system for powder medicine, (b) an automatic dispensing/splitting device or system for tablets, (c) an automatic Dispensing/dispensing device or system, (d) automatic co-injection device or system for anticancer drugs, (e) dispensing inspection device or system, (f) any one of these devices or systems connected in plurality or (g) a mode in which a plurality of types of devices or systems among these devices are connected.

According to the present invention, it is possible to set whether or not to restrict the automatic start of dispensing processing, and as a result, it is possible to improve convenience for the user.

1 is a diagram for explaining the configuration of a dispensing control system according to an embodiment of the present invention; FIG. It is a figure which shows an example of a list screen. It is a figure which shows an example of an instruction screen. 1 is a functional block diagram of a dispensing control system according to an embodiment of the present invention; FIG. It is a figure which shows an example of a user table. It is a figure which shows an example of a patient table. It is a figure which shows an example of a prescription data table. FIG. 10 illustrates an example of an execution history table; FIG. It is a figure which shows an example of an automatic start function flag. It is a figure which shows an example of an exception condition table. It is a figure which shows an example of an authority specific table. FIG. 4 is a flow chart showing an example of processing executed by the dispensing control system; FIG. 4 is a flowchart showing another example of processing executed by the dispensing control system; FIG. 3 is a diagram for explaining the configuration of a dispensing control system according to another embodiment of the present invention; FIG. FIG. 10 is a diagram showing another example of an exception condition table; FIG. 10 is a diagram showing another example of an exception condition table; FIG. 3 is a functional block diagram of a dispensing control system according to another embodiment of the present invention; FIG. 10 is a flowchart showing an example of processing executed by a dispensing control system according to another embodiment of the present invention;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or equivalent elements are denoted by the same reference numerals, and overlapping descriptions are omitted. In the pharmaceutical industry, the terms "preparation" and "preparation" may be used separately, but in this specification, "preparation" is used in a broad sense, and "preparation" in this specification includes , "preparation" in the narrow sense (that is, "preparation" as distinguished from "preparation") and "preparation".

[1. Overall Configuration] FIG. 1 is a diagram for explaining the configuration of a dispensing control system according to an embodiment of the present invention. FIG. 1 shows a dispensing control system 1 and a host system 2 according to an embodiment of the present invention.

As shown in FIG. 1, the dispensing control system 1 includes a control device 10, a database 17, and a dispensing device 20, and is a system that controls the dispensing device 20 to execute dispensing processing.

The control device 10 is implemented by one or more computers. As shown in FIG. 1 , the control device 10 includes a control section 11 , a storage section 12 , a communication section 13 , an operation section 14 , a display section 15 and a printing section 16 .

The control unit 11 includes one or more microprocessors and executes processing according to programs stored in the storage unit 12 . The storage unit 12 includes information storage media such as main memory (RAM, etc.) and auxiliary memory (hard disk drive, solid state drive, etc.), and stores programs executed by the control unit 11 . The storage unit 12 also operates as a work memory for the control unit 11 . The communication unit 13 is for data communication with other devices via a communication network.

For example, programs or data are provided to the control device 10 via a communication network. Note that the control device 10 may include components for reading programs or data stored in a computer-readable information storage medium such as a memory card or an optical disk. Then, the program or data may be provided to the control device 10 via an information storage medium.

The operation unit 14 is for accepting user operations, and is, for example, a keyboard, mouse, touch pad, or touch panel. The display unit 15 displays a screen according to instructions from the control unit 11, and is, for example, a liquid crystal display or an organic EL display. The printing unit 16 performs printing according to instructions from the control unit 11, and is, for example, a printer device.

Controller 10 can access database 17 . The database 17 may be realized by the control device 10 or may be realized by a computer separate from the control device 10 . The data stored in the database 17 will be described later (see FIGS. 5-11, 15 and 16).

The dispensing device 20 (an example of dispensing executing means) is a device that executes dispensing processing, and can, for example, fully automatically execute dispensing processing based on prescription data without requiring human operation (work). device. Note that the dispensing device 20 may be referred to as a "dispensing system".

Dispensing processing includes at least one of, for example, dispensing/packaging of powdered medicine (powder), dispensing/packaging of tablets, dispensing/dispensing of liquid medicine, co-administration of anticancer drugs, or inspection of various dispensed drugs. include. In addition, the dispensing device 20 is, for example, an automatic dispensing/splitting device for powder medicine (powder), an automatic dispensing/splitting device for tablets, an automatic dispensing/dispensing device for liquid medicines, an automatic mixed injection device for anticancer drugs, or a dispensing inspection device. equipment and the like. Alternatively, dispensing device 20 may be one in which a plurality of devices of any one of these devices are connected. Alternatively, dispensing device 20 may be one in which a plurality of types of these devices are connected.

For example, the dispensing device 20 is a dispensing device that includes a single-arm or double-arm robot, and the robot executes dispensing processing. More specifically, for example, a robot automatically prepares and distributes powdered medicines by weighing and dispensing powdered medicines by using powdered medicines stored by type in a plurality of medicine containers installed in the housing of the device. A packaging device corresponds to an example of the dispensing device 20 . Further, for example, an automatic co-injection device for anticancer drugs in which a robot mixes a plurality of drugs installed in a housing of the device to dispense an anticancer drug also corresponds to an example of the dispensing device 20 .

The dispensing device 20 is not limited to one using a robot. For example, an automatic tablet dispensing/splitting device in which target tablets are automatically taken out from a plurality of drug containers installed in the housing of the device and packaged by a specific mechanism other than a robot is also a dispensing device. 20 example.

In addition, although the control device 10 and the dispensing device 20 are shown as separate devices in FIG. 1, the control device 10 and the dispensing device 20 may be configured integrally. That is, the control device 10 may be provided with the dispensing execution function of the dispensing device 20 . In other words, the dispensing device 20 may have the functions of the control device 10 .

Prescription data is input to the host system 2 , and the prescription data input by the host system 2 is inspected and then provided to the dispensing control system 1 . For example, the terminal of the host system 2 is installed in the clinical department in the hospital, and the dispensing control system 1 is installed in the dispensing department in the hospital. Also, for example, the host system 2 is installed in a hospital, and the dispensing control system 1 is installed in a dispensing pharmacy.

Prescription data can also be entered in the dispensing control system 1 . That is, in the dispensing control system 1, an input screen (not shown) for accepting input of prescription data is displayed on the display unit 15, and the user of the dispensing control system 1 can receive a paper-issued prescription. It is possible to receive a prescription from a patient and input prescription data while referring to the prescription. That is, the dispensing control system 1 can cause the dispensing device 20 to execute dispensing processing based on the prescription data input by the host system 2, and can also cause the dispensing device 20 to perform dispensing processing based on the prescription data input by the dispensing control system 1. It is also possible to cause the dispensing device 20 to perform the processing. Note that the host system 2 is not essential, and the host system 2 may not be installed.

[2. Overview of Function] The dispensing control system 1 has an automatic start function that enables the dispensing device 20 to automatically start dispensing processing. In the dispensing control system 1, the user can arbitrarily turn ON/OFF the automatic start function.

When the automatic start function is set to OFF, the control device 10 waits for an instruction to start the dispensing process from a user (authorized person) having a predetermined authority, and causes the dispensing device 20 to start the dispensing process. .

In the dispensing control system 1, when the user logs in and performs a predetermined operation, for example, a list screen G1 as shown in FIG. The login to the dispensing control system 1 may be performed by the user entering the user ID and password on a login screen (not shown), or by the user entering an ID card distributed in advance. may be read by the card reader. However, in the latter case, the control device 10 needs to have a card reader for reading the information recorded on the card in a contact or non-contact manner.

As shown in FIG. 2, the list screen G1 displays a list of prescription data for which dispensing processing has not been performed. In the example shown in FIG. 2, prescription data A, B, and C are displayed on the list screen G1. In FIG. 2, for convenience of explanation, texts such as "prescription data A", "prescription data B", and "prescription data C" are displayed as information indicating each prescription data, but the actual list screen G1 , for example, a patient name and a part of prescription content are displayed as information indicating each prescription data.

When the user selects one of the prescription data displayed on the list screen G1, an instruction screen G2 as shown in FIG. 3, for example, is displayed. The instruction screen G2 is a screen for receiving an instruction to start dispensing processing of prescription data.

As shown in FIG. 3, the instruction screen G2 displays details of the prescription data selected on the list screen G1. For example, patient information (eg, name, sex, age, date of birth, medication history, etc.) and prescription details (eg, medical institution, clinical department, drug, usage, dosage, number of days, and quantity) are displayed.

The instruction screen G2 also includes a comment field P21 for accepting input of comments. The user can input comments in the comment column P21 as necessary. Further, the instruction screen G2 includes an execute button P22 and a return button P23. The return button P23 is a button for returning to the list screen G1. The execution button P22 is a button for instructing the start of dispensing processing. When the user presses the execution button P22, the dispensing device 20 starts dispensing processing of the prescription data displayed on the instruction screen G2.

On the other hand, if the automatic start function is set to ON, the prescription data input by the host system 2 is supplied to the dispensing control system 1, or the prescription data is input via the input screen in the dispensing control system 1. In principle, the dispensing control system 1 automatically causes the dispensing device 20 to start dispensing processing based on the prescription data. That is, in principle, the dispensing control system 1 causes the dispensing device 20 to start the dispensing process based on the prescription data without waiting for an instruction to start the dispensing process from a user having a predetermined authority (authorized person). .

In the dispensing control system 1, by providing such a function, the user can turn off the automatic start function when the user desires to start dispensing processing after prescription information is confirmed by a predetermined authorized person. , you can use the dispensing control system as you wish. On the other hand, when the user desires to have the dispensing process automatically started, the user can use the dispensing control system as desired by setting the automatic start function to ON.

Further, in the dispensing control system 1, even when the automatic start function is set to ON, in a specific case, the automatic start of the dispensing process can be exceptionally restricted. For this reason, in certain cases (for example, when the prescription data contains a drug that requires special attention), the dispensing process is started after the prescription information is confirmed by a predetermined authorized person, and in other cases This feature allows the user to use the dispensing control system as desired if the user wishes to have the dispensing process automatically initiated.

Although there are laws such as the Pharmacist Law regarding dispensing work, as a result of the functions described above being provided in the dispensing control system 1, the user can take into consideration the legality and efficiency of dispensing work through automation. It is possible to determine how to use the dispensing control system 1 and use the dispensing control system 1 according to that usage.

In addition, the dispensing control system 1 generates "medicine" that is taken by people, which is directly linked to life. However, as a result of having the functions described above in the dispensing control system 1, in principle, dispensing processing can be started automatically to improve efficiency. On the other hand, it is also possible to ensure that the dispensing process is performed manually through human intervention in specific cases where the dispensing process should be performed with human intervention in order to sufficiently ensure safety.

[3. Functional Block] A configuration for realizing the functions described above will be described. FIG. 4 is a functional block diagram mainly showing functions related to the above functions among the functions realized by the dispensing control system 1. As shown in FIG.

[3-1. Data Storage Unit] As shown in FIG. 4, the dispensing control system 1 includes a data storage unit 100 . For example, the data storage unit 100 is mainly implemented by the database 17 . The data storage unit 100 stores various data. 5 to 11 show examples of data stored in the data storage unit 100. FIG.

FIG. 5 shows an example of the user table D1. The user table D1 shows a list of persons who can use the dispensing control system 1 (in other words, persons who can log into the dispensing control system 1). The user table D1 shown in FIG. 5 includes “user ID”, “name”, “password”, and “authority level” fields.

A "user ID" field indicates identification information that uniquely identifies a user. The "Name" field indicates the user's name. The "Password" field indicates the user's password. For example, an encrypted password set by the user or system administrator is registered in the "password" field. When using the dispensing control system 1, the user must be authenticated by entering his or her own user ID and password on the login screen. The user may be authenticated or specified by causing the card reader to read an ID card distributed in advance by the user.

The "privilege level" field indicates the user's privilege level. Depending on the authority level set for the user, the operations that the user can perform in the dispensing control system 1 are restricted. For example, values from "1" to "6" are set as authority levels. "6" is the highest privilege level and "1" is the lowest privilege level.

A user with an authority level of “6” can perform any operation on the dispensing control system 1 . For example, only users with authority level "6" are permitted to edit the master data (user table D1, etc.) stored in the data storage unit 100. FIG. That is, only users with authority level "6" are permitted to register new users in the user table and to set and change the authority level of each user.

Also, a user with an authority level of "5" can perform operations other than editing master data. For example, only users with authority level "5" or "6" are permitted to fill a drug container in the dispensing device 20 with a drug.

Also, a user with an authority level of "4" can perform operations other than editing master data and filling medicines. For example, specific operations that require special attention (herein referred to as "special operations") are permitted only to users with authority levels "4" to "6".

Also, a user with authority level "3" can perform operations other than editing master data, filling drugs, and performing special operations. For example, a specific operation that requires caution (herein referred to as a “caution-requiring operation”) is permitted only to users with authority levels “3” to “6”.

A user with authority level "2" can perform operations other than editing master data, filling medicine, special operations, and operations requiring caution. Also, a user with an authority level of "1" can only perform limited simple operations.

For example, an authority level of "6" is set for a person (system administrator) who is responsible for managing the dispensing control system 1. FIG. Any of authority levels "2" to "5" is set for pharmacists other than the system administrator. Specifically, authority level "2" is set for pharmacists with relatively little experience, and authority level "3" is set for pharmacists with some experience. In addition, an authority level of "4" is set for an experienced pharmacist who takes on the role of managing pharmacists with an authority level of "2" or "3". A pharmacist with an authority level of "4" also plays a role of management, and an authority level of "5" is set for an extremely experienced pharmacist. For example, an authority level of "4" is set for a pharmacist (local manager) responsible for managing the pharmacists who work at each dispensing site. An authority level of "5" is set for a pharmacist (administrator) who has a role to perform overall management over a plurality of dispensing sites, that is, a role to manage all pharmacists working at each of the plurality of dispensing sites. be done. Note that an authority level "1" is set for a user other than the pharmacist, for example, a person (operator) who plays a role of performing a simple operation to assist the pharmacist.

FIG. 6 shows an example of the patient table D2. A patient table D2 shows a list of patients. The patient table D2 shown in FIG. 6 includes “patient ID”, “name”, “sex”, “age”, “date of birth”, and “medicine history” fields. The "Patient ID" field indicates identification information that uniquely identifies the patient. The "Name", "Gender", "Age", and "Date of Birth" fields indicate the patient's name, sex, age, and date of birth, respectively. The "medicine history" field shows the history of drugs that have been prescribed to the patient so far. For example, when a patient visits a dispensing pharmacy for the first time, the patient's data is registered in the patient table D2.

FIG. 7 shows an example of the prescription data table D3. The prescription data table D3 shows a list of prescription data input by the dispensing control system 1 and prescription data input by the host system 2 and provided to the dispensing control system 1 . The prescription data table D3 shown in FIG. 7 includes “prescription data ID”, “registration date and time”, “input system flag”, “inspection result flag”, “DO prescription flag”, “patient”, “prescription content”, “auto start flags”, and “execution status flags” fields.

The “prescription data ID” field indicates identification information that uniquely identifies prescription data. The "registration date and time" field indicates the date and time when the prescription data was registered in the prescription data table D3.

The "input system flag" field indicates the system into which the prescription data was entered. Specifically, the "input system" field indicates whether the prescription data was input from the dispensing control system 1 or from the host system 2 . For example, if the prescription data is input by the dispensing control system 1, the value "0" is registered in the "input system flag" field. On the other hand, when the prescription data is input by the host system 2, the value "1" is registered in the "input system flag" field.

The “inspection result flag” field indicates the inspection result of the prescription data in the host system 2 . The host system 2 inspects the prescription data before providing the prescription data to the dispensing control system 1 . For example, conditions for prescription data requiring attention are predetermined, and a warning is issued for prescription data that satisfies the conditions. Regarding the prescription data subject to warning, after reconfirmation by the pharmacist, if there is no particular problem, it is provided to the dispensing control system 1 as it is, and if there is a problem, the dispensing control system 1 is corrected. provided to For example, if the prescription data is input by the host system 2 and the inspection result of the host system 2 is "with warning", the value "1" is registered in the "inspection result flag" field, If the inspection result in the host system 2 is not "warning", the value "0" is registered in the "inspection result flag" field.

The "DO Prescription Flag" field indicates whether the prescription data was entered (generated) using the DO prescription function. The dispensing control system 1 and host system 2 have a DO prescription function. The DO prescription function is a function that makes it possible to easily input prescription data of the same content by duplicating past prescription data for the same patient. For example, if the prescription data was entered using the DO prescription function, a value of "1" is registered in the "DO prescription flag" field; prescription flag” field.

The "patient" field indicates the patient (patient ID) that is the target of the prescription data. The "prescription content" field indicates the prescription content (for example, medical institution, clinical department, drug, usage, dose, number of days, and quantity).

The "auto start flag" field indicates whether or not it is possible to automatically start the dispensing process of the prescription data. For example, if it is possible to automatically start the dispensing process, the value "1" is registered in the "automatic start flag" field, and if it is not possible to automatically start the dispensing process, A value of "0" is registered in the "auto start flag" field.

The "execution status flag" field indicates the execution status of dispensing processing of prescription data. For example, a value of "0" is registered in the "execution status flag" field for prescription data in a state prior to the start of dispensing processing. Further, the value "1" is registered in the "execution status flag" field for prescription data whose dispensing process is in progress, and the value "2" is registered for prescription data whose dispensing process is completed. Execution status flag” field.

FIG. 8 shows an example of the execution history table D4. The execution history table D4 shows the execution history of the dispensing process. The execution history table D4 shown in FIG. 8 includes “execution history ID”, “target prescription data”, “automatic start flag”, “start instruction person”, “authority level”, “comment”, “start date and time”, and “end Include date and time fields.

The “execution history ID” field indicates identification information that uniquely identifies each execution history. The "target prescription data" field indicates the prescription data that is the target of dispensing processing. For example, the prescription data ID of the prescription data subject to dispensing processing is registered in the "target prescription data" field.

The "automatic start flag" field indicates whether or not the dispensing process has been automatically started. For example, if the dispensing process is automatically started by the automatic start function, the value "1" is registered in the "automatic start flag" field. On the other hand, when the dispensing process is not automatically started by the automatic start function, but is executed by a start instruction given by a predetermined authorized person, the value "0" is the "automatic start flag". registered in the field.

The "start instruction person" field indicates the person (start instruction person) who instructed the start of the dispensing process, and the "authority level" field indicates the authority level of the start instruction at the time when the instruction to start the dispensing process was given. indicates For example, the user ID of the start instructor is registered in the "start instructor" field. Furthermore, the authority level of the start instructor at that time is registered in the "authority level" field. Also, the "comment" field indicates the comment entered by the start designator. That is, the comment entered in the comment field P21 of the instruction screen G2 is registered in the "comment" field. Note that when the dispensing process is automatically started by the automatic start function, the "start instruction person", "authority level", and "comment" fields are blank. The "start date and time" and "end date and time" fields indicate the dates and times when the dispensing process was started and ended.

As shown in FIG. 4, data storage unit 100 includes setting data storage unit 101 . The setting data storage unit 101 stores setting data. The setting data is data set for determining whether to restrict the automatic start of dispensing processing. 9 and 10 show an example of setting data.

FIG. 9 shows an example of the automatic start function flag D5. As described above, the dispensing control system 1 has an automatic start function that allows the dispensing device 20 to automatically start dispensing processing. The automatic start function flag D5 indicates whether the automatic start function is set ON or OFF. For example, the autostart feature flag takes the value "0" or "1". A value of "1" indicates that the autostart feature is set to ON. On the other hand, a value of "0" indicates that the auto-start feature is set to OFF. For this reason, when the automatic start function flag is set to "0", the dispensing control system 1 does not cause the dispensing device 20 to automatically start the dispensing process, but instructs to start the dispensing process with a predetermined authority. After waiting for the receipt from the person, the dispensing device 20 is caused to start dispensing processing.

For example, the initial value of the automatic start function flag D5 is set to "0", and a user with an authority level of "6" can change the automatic start function flag D5 to "1" via a predetermined setting screen. The initial value of the automatic start function flag D5 may be set to "1".

FIG. 10 shows an example of the exception condition table D6. As described above, when the automatic start function is set to ON, in principle, the dispensing control system 1 causes the dispensing device 20 to automatically start dispensing processing. In this regard, the exception condition table registers a condition (exception condition) for exceptionally restricting the automatic start of the dispensing process even when the automatic start function is set to ON. For example, a user with authority level "6" can set exception conditions in the exception condition table via a predetermined setting screen.

The exception condition table D6 shown in FIG. 10 includes “exception condition ID” and “exception condition” fields. The "exceptional condition ID" field indicates identification information that uniquely identifies an exceptional condition registered in the exceptional condition table D6. The "exception condition" field indicates an exception condition. Exceptional conditions are registered in the "exceptional condition" field in a form recognizable by the computer (control unit 11). In the following, for the sake of convenience, an exceptional condition whose exceptional condition ID is "ECn" will be referred to as an "exceptional condition ECn".

For example, in the exception condition table D6, conditions related to prescription data that require restriction of automatic execution of dispensing processing are registered as exception conditions. Exceptional conditions EC1 to EC6 shown in FIG. 10 are conditions related to prescription data that require restriction of automatic execution of dispensing processing. Exceptional conditions EC1 to EC5 are conditions related to target prescription data that is the target of dispensing processing, and exceptional condition EC6 is a condition related to prescription data that was the target of dispensing processing executed immediately before. . Exceptional conditions EC1 to EC6 will be described below.

Exceptional conditions EC1 and EC2 are conditions regarding whether or not a specific drug is included as a drug to be provided to the patient in the target prescription data to be dispensed. Specifically, the exceptional condition EC1 is a condition that "medicine A is included in the target prescription data". On the other hand, the exceptional condition EC2 is a condition that "medicine B is included in the target prescription data".

Here, "medicine A" is, for example, a drug that requires special care in handling. Also, "medicine B" is a drug requiring caution in handling, although the degree of caution is lower than that of drug A, for example. Care must be taken when such drug A or drug B is included in the target prescription data. As for the data, even if the automatic start function is set to ON, the dispensing process is not automatically started, and the dispensing process is not started unless a start instruction is given by a predetermined authorized person.

The exceptional condition EC3 is a condition regarding patient data included in the target prescription data. Specifically, the exception condition EC3 is a condition that "the patient of the target prescription data is under 10 years old".

In general, caution is required when the patient is young, but by setting the exceptional condition EC3, the automatic start function was set to ON for prescription data for patients under the age of 10. Even so, the dispensing process is not automatically started, and the dispensing process is not started without a start instruction from a predetermined authorized person. Conditions related to the patient's gender, medication history, etc. may be set as exceptional conditions.

Exceptional condition EC4 is a condition as to whether the target prescription data is prescription data manually input via an input screen in dispensing control system 1 or prescription data provided by host system 2 . Specifically, the exceptional condition EC4 is a condition that "target prescription data is manually input."

Prescription data manually input via the input screen in the dispensing control system 1 may contain errors compared to the prescription data provided after being inspected by the host system 2, and caution is required. However, by setting the exceptional condition EC4, the prescription data manually input via the input screen in the dispensing control system 1 can be automatically processed even if the automatic start function is set to ON. Dispensing processing is not started unless a predetermined authorized person gives a start instruction.

The exception condition EC5 is a condition as to whether or not the inspection result for the target prescription data in the host system 2 is a predetermined result. Specifically, the exceptional condition EC5 is a condition that "the inspection result of the target prescription data in the host system 2 is 'with warning'".

Care must be taken when the inspection result of the target prescription data in the host system 2 is "warning", but by setting the exception condition EC5, the inspection result in the host system 2 is "warning". With regard to the prescription data, the dispensing process is not automatically started even if the automatic start function is set to ON, and the dispensing process is not started unless a start instruction is given by a predetermined authorized person.

Exceptional condition EC6 is a condition relating to prescription data that was the object of dispensing processing executed immediately before. Specifically, the exceptional condition EC6 is a condition that "medicine C is included in the immediately preceding prescription data".

Here, "medicine C" is, for example, a drug that requires particular attention so as not to leave any drug in a portion of the dispensing device 20 that comes into contact with the drug during dispensing processing (such as a drug input portion). If drug C is included in the target prescription data of the dispensing process executed immediately before, it is necessary to confirm that drug C does not remain in the drug input unit or the like, but exception condition EC6 is set. Therefore, when drug C is included in the target prescription data of the dispensing process executed immediately before, the dispensing process is not automatically started even if the automatic start function is set to ON. Dispensing processing will not be started without a start instruction from an authorized person.

Further, as shown in FIG. 4, the data storage unit 100 includes an authorized person identification data storage unit 102 . The authorized person identification data storage unit 102 stores the authorized person identification data in association with conditions related to prescription data. The authorized person identification data is data for identifying an authorized person who can instruct the start of dispensing processing of prescription data.

FIG. 11 shows an example of an authority identification table D7, which is an example of authority identification data. The authorized person identification table D7 is a table for identifying an authorized person who can instruct the start of dispensing processing. For example, a user with an authority level of "6" can set the authority specifying table D7 via a predetermined setting screen.

When the automatic start function is set to OFF, an authorized person who can give an instruction to start the dispensing process is identified based on the authorized person identification table D7, and a start instruction from the authorized person is waited for. A dispensing process is performed. Similarly, even if the automatic start function is set to ON, if the automatic start function is exceptionally limited by satisfying the exception condition of the exception condition table D6, the authorized person identification table D7 , an authorized person who can instruct the start of the dispensing process is specified, and the dispensing process is executed after waiting for a start instruction from the authorized person.

The authority identification table D7 shown in FIG. 11 includes "condition ID", "condition", and "required authority level" fields. The "condition ID" field indicates identification information that uniquely identifies the conditions registered in the authority identification table D7. The "Condition" field indicates the condition. Conditions are registered in the "condition" field in a form recognizable by the computer (control unit 11). The "required authority level" field indicates the authority level (required authority level) required to instruct the start of dispensing processing. In the following, for the sake of convenience, the condition whose condition ID is "Cn" will be referred to as "condition Cn".

In the authorized person identification table D7 shown in FIG. 11, the conditions C1 to C6 are the same as the exception conditions EC1 to EC6 of the exception condition table D6 shown in FIG. 10, so the explanation is omitted here. The conditions registered in the authority identification table D7 may be different from the exception conditions registered in the exception condition table D6.

In the authorized person identification table D7 shown in FIG. 11, conditions C7 and C8 are set in addition to the conditions C1 to C6. Among these, the condition C7 is a condition that "medicine D is included in the target prescription data". Here, "medicine D" is, for example, a drug requiring a certain degree of caution in handling, although the degree of caution is lower than that of drugs A and B. Condition C8 is a case other than conditions C1 to C7.

In the authority identification table D7 shown in FIG. 11, the condition C7 is associated with "3 to 6" as the necessary authority level. This indicates that when condition C7 is satisfied, users with authority levels "3" to "6" are set as authorized persons (persons who can instruct the start of dispensing processing). Also, the conditions C2 to C5 are associated with "4 to 6" as required authority levels. This indicates that users with authority levels "4" to "6" are set as authorized persons. For example, since drug B requires more care in handling than drug D, condition C2 is associated with a higher required authority level than condition C7.

Also, the conditions C1 and C6 are associated with "5 to 6" as the required authority level. This indicates that users with authority levels "5" to "6" are set as authorized persons when condition C1 or C6 is satisfied. Since drugs A and C require more care in handling than drug B, conditions C1 and C6 are associated with a higher required authority level than condition C2.

Further, condition C8 is associated with "2 to 6" as the required authority level. This indicates that users with authority levels "2" to "6" are set as authorized persons when none of the conditions C1 to C7 are satisfied.

As described above, the conditions C1 to C6 of the authority identification table D7 are the same as the exception conditions EC1 to EC6 of the exception condition table D6. In this regard, in the authority identification table D7, the condition C1 is associated with the required authority level of "5-6". There will be When the exception condition EC1 is satisfied, even if the automatic start function is set to ON, the automatic start function is exceptionally limited, and the dispensing process is started after waiting for a start instruction from a predetermined authorized person. In this case, users with authority levels "5" to "6" are set as authorized persons.

Although the exception condition table D6 and the authority identification table D7 are provided separately in this embodiment, they may be provided integrally. For example, the exception condition table D6 may be omitted and only the authority identification table D7 may be provided. In this case, for example, a condition associated with a required authority level of "4 to 6" or "5 to 6" may be regarded as an "exceptional condition".

[3-2. Functional Blocks Other Than Data Storage Unit] As shown in FIG. , a start control unit 110 , an authorized person setting unit 113 , a start instruction reception unit 114 , and an execution history registration unit 115 . These functional blocks are mainly implemented by the control unit 11 . That is, the control unit 11 functions as these functional blocks by executing processing according to the program.

The input screen display control unit 103 causes the display unit 15 to display the input screen. The input screen is a screen for accepting input of prescription data. A user of the dispensing control system 1 receives a paper-issued prescription from a patient, and while referring to the prescription, obtains patient information and prescription information (medical institution, clinical department, doctor, drug, usage, dose, number of days, quantity, etc.). ) can be entered on the input screen.

The prescription data acquisition unit 104 acquires target prescription data for dispensing processing. As shown in FIG. 4 , the prescription data acquisition section 104 includes a first prescription data acquisition section 105 and a second prescription data acquisition section 106 .

The first prescription data acquisition unit 105 acquires prescription data input via the input screen as target prescription data.

The second prescription data acquisition unit 106 acquires prescription data input from the host system 2 (an example of another system) as target prescription data. For example, the second prescription data acquisition unit 106 receives prescription data transmitted from the host system 2 and acquires it as target prescription data. Alternatively, the second prescription data acquisition unit 106 accesses the storage device in which the prescription data input by the host system 2 is stored, and acquires the prescription data as target prescription data.

Based on the setting data stored in the setting data storage unit 101, the determination unit 107 determines whether to restrict the automatic start of the dispensing process (in other words, whether to allow the automatic start of the dispensing process). .

For example, the determination unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the automatic start function flag D5 (an example of setting data) shown in FIG. Specifically, when the automatic start function flag is "0", the determination unit 107 determines to limit the automatic start of the dispensing process. On the other hand, when the automatic start function flag is "1", in principle, the judgment unit 107 judges that the automatic start of dispensing processing is not restricted.

Further, for example, the determination unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the determination result of the target prescription data determination unit 108, which will be described later.

The target prescription data determination unit 108 determines whether or not the target prescription data satisfies the conditions set in the setting data stored in the setting data storage unit 101 . As described above, the setting data stored in the setting data storage unit 101 includes conditions related to prescription data that require restriction of automatic start of dispensing processing, or conditions related to prescription data that do not require restriction of automatic start of dispensing processing. A condition is set, and the target prescription data determination unit 108 determines whether or not the target prescription data satisfies the condition.

For example, the target prescription data determination unit 108 determines whether or not the target prescription data satisfies any one of the exception conditions EC1 to EC5 set in the exception condition table D6 (an example of setting data) shown in FIG. . Even if the automatic start function flag is "1", if the target prescription data determination unit 108 determines that the target prescription data satisfies any one of the exception conditions EC1 to EC5, the determination unit 107 performs dispensing processing. Determine to restrict automatic start.

Further, for example, the determination unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the determination result of the immediately preceding prescription data determination unit 109, which will be described later.

The immediately preceding prescription data determination unit 109 determines whether the prescription data (immediately preceding prescription data) that was the target of the dispensing process executed immediately before satisfies the conditions set in the setting data stored in the setting data storage unit 101. judge. As described above, the setting data stored in the setting data storage unit 101 includes conditions related to prescription data that require restriction of automatic start of dispensing processing, or conditions related to prescription data that do not require restriction of automatic start of dispensing processing. A condition is set, and the immediately preceding prescription data determination unit 109 determines whether or not the immediately preceding prescription data satisfies the condition.

For example, the immediately preceding prescription data determination unit 109 determines whether or not the immediately preceding prescription data satisfies the exceptional condition EC6 set in the exceptional condition table D6 (an example of setting data) shown in FIG. Even if the automatic start function flag is "1", if the immediately preceding prescription data determination unit 109 determines that the immediately preceding prescription data satisfies the exception condition EC6, the determination unit 107 limits the automatic start of dispensing processing. to decide.

The start control unit 110 causes the dispensing device 20 (an example of dispensing executing means) to start dispensing processing for target prescription data. As shown in FIG. 4 , start control section 110 includes first start control section 111 and second start control section 112 .

When the determination unit 107 determines that the automatic start of dispensing processing is not to be restricted, the first start control unit 111 automatically causes the dispensing device 20 to start dispensing processing of the target prescription data. That is, when the target prescription data is acquired, the first start control unit 111 causes the dispensing device 20 to perform the dispensing process of the target prescription data without waiting for an instruction to start the dispensing process from a predetermined authorized person. let it start.

On the other hand, if the determining unit 107 determines that the automatic start of dispensing processing is to be restricted, the second start control unit 112 receives an instruction to start dispensing processing from a predetermined authorized person, and performs the dispensing processing of the target prescription data. is initiated by dispensing device 20 . That is, when the target prescription data is acquired, the second start control unit 112 does not cause the dispensing device 20 to immediately start the dispensing process, but determines whether or not the instruction to start the dispensing process is received from the predetermined authorized person. Then, after receiving an instruction to start the dispensing process from a predetermined authorized person, the dispensing apparatus 20 is made to start the dispensing process. In this case, the "authorized person" is set by the authorized person setting unit 113, which will be described later, in accordance with the target prescription data or the immediately preceding prescription data.

The authorized person setting unit 113 sets an authorized person (that is, a person who can instruct the start of dispensing processing) based on the target prescription data. For example, the authorized person setting unit 113 sets the authorized person based on the target prescription data and the authorized person specifying data stored in the authorized person specifying data storage unit 102 . As described above, the authorized person specifying data storage unit 102 stores authorized person specifying data in association with conditions related to prescription data. The authorized person setting unit 113 sets an authorized person based on the authorized person specifying data associated with the condition satisfied by the target prescription data.

For example, in the authority identification table D7 shown in FIG. 11, the required authority level "5-6" is associated with the condition C1. Therefore, when the target prescription data satisfies the condition C1, the authorized person setting unit 113 sets users with authority levels "5" to "6" as authorized persons.

Note that the authorized person setting unit 113 may set the authorized person based on the prescription data (immediately preceding prescription data) that was the object of the dispensing process executed immediately before. For example, the authorized person setting unit 113 may set the authorized person based on the immediately preceding prescription data and the authorized person specifying data stored in the authorized person specifying data storage unit 102 . As described above, the authorized person specifying data storage unit 102 stores authorized person specifying data in association with conditions related to prescription data. The authorized person setting unit 113 may set the authorized person based on the authorized person specifying data associated with the conditions satisfied by the immediately preceding prescription data.

For example, in the authority identification table D7 shown in FIG. 11, the required authority level "5-6" is associated with the condition C6. Therefore, when the immediately preceding prescription data satisfies the condition C6, the authorized person setting unit 113 sets users with authority levels "5" to "6" as authorized persons.

In addition, here, it is explained that the authorized person is set by the authorized person setting unit 113 according to the target prescription data or the immediately preceding prescription data, but the authorized person may be a preset specific user. For example, regardless of the target prescription data or the immediately preceding prescription data, users with authority levels "5" to "6" may be determined in advance as authorized persons.

The start instruction accepting unit 114 accepts an instruction to start dispensing processing. For example, the start instruction receiving unit 114 causes the display unit 15 to display the instruction screen G2 shown in FIG. 3, for example. As described above, the instruction screen G2 is a screen for accepting an instruction to start dispensing processing. When the execution button P22 of the instruction screen G2 is pressed, the start instruction receiving unit 114 determines that the start instruction of dispensing processing has been received.

As described above, the second start control unit 112 causes the dispensing device 20 to start the dispensing process when an instruction to start the dispensing process is received from the authorized person set by the authorized person setting unit 113 . That is, when the authorized person set by the authorized person setting unit 113 presses the execution button P22 on the instruction screen G2, the second start control unit 112 causes the dispensing device 20 to start the dispensing process.

On the other hand, when the second start control unit 112 receives an instruction to start the dispensing process from a user (non-authorized person) other than the authorized person set by the authorized person setting unit 113, the dispensing device 20 starts the dispensing process. don't let That is, even if an unauthorized person presses the execution button P22 on the instruction screen G2, the second start control unit 112 does not cause the dispensing device 20 to start the dispensing process. In this case, an error message is displayed to the effect that there is no authority to issue a start instruction.

Note that the start instruction receiving unit 114 may not receive an instruction to start dispensing processing from an unauthorized person. For example, the execution button P22 may be enabled only when the authorized person set by the authorized person setting unit 113 is logged in. Specifically, when the logged-in user is an unauthorized person, the execution button P22 may not be displayed, or may be displayed in a state in which the execution button P22 cannot be pressed (for example, in a grayed out state). You may Alternatively, when the logged-in user is an unauthorized person, screen transition from the list screen G1 to the instruction screen G2 or screen transition from another screen (such as a menu screen) to the list screen G1 is prohibited. You may make it

Execution history registration unit 115 registers the execution history of dispensing processing in data storage unit 100 (an example of predetermined storage means). That is, the execution history registration unit 115 associates the target prescription data that is the target of the dispensing process, the authorized person data related to the authorized person who instructed the start of the dispensing process, and the comment data input by the authorized person. Register in the storage unit 100 . More specifically, execution history registration unit 115 registers the execution history of dispensing processing in execution history table D4 shown in FIG.

[4. Processing] An example of processing executed by the dispensing control system 1 will be described. 12 and 13 are flow charts showing an example of processing executed by the dispensing control system 1. FIG. The control unit 11 executes the processes shown in FIGS. 12 and 13 according to the program, thereby realizing the functional blocks shown in FIG. 4 (excluding the data storage unit 100).

[4-1] FIG. 12 shows the dispensing control system when prescription data is input by the dispensing control system 1 (input screen) or when prescription data input by the host system 2 is supplied to the dispensing control system 1. 1 is a flow diagram showing an example of a process performed in 1. FIG.

As shown in FIG. 12, first, the control unit 11 registers target prescription data in the prescription data table D3 (S100). For example, the control unit 11 adds a new record to the prescription data table D3, and registers target prescription data in the new record.

After executing step S100, the control unit 11 refers to the automatic start function flag D5 and determines whether or not the automatic start function is set to ON (S101). That is, the control unit 11 determines whether or not the automatic start function flag is "1".

When the automatic start function is set to ON, the control unit 11 refers to the exception condition table D6 and determines whether or not any exception condition is satisfied (S102).

If none of the exceptional conditions are satisfied, the control unit 11 causes the dispensing device 20 to start dispensing processing of the target prescription data (S103). For example, the control unit 11 causes the dispensing device 20 to start the dispensing process by transmitting to the dispensing device 20 request data requesting the start of dispensing processing of the target prescription data. In this case, the control unit 11 accesses the prescription data table D3 and sets the automatic start flag and execution status flag of the target prescription data to "1".

After that, the control unit 11 monitors whether or not the dispensing process is completed (S104). For example, when dispensing processing is completed, the dispensing device 20 notifies the control unit 11 of the fact, and the control unit 11 monitors whether or not the notification has been received from the dispensing device 20 .

When the dispensing process is completed, the control unit 11 registers the execution result of the dispensing process in the execution history table D4 (S105). For example, the control unit 11 adds a new record to the execution history table D4, and registers the current execution result of the dispensing process in the new record. In this case, the control unit 11 also accesses the prescription data table D3 and updates the execution status flag of the target prescription data to "2".

If it is determined in step S101 that the automatic start function is not set to ON, that is, if the automatic start function is set to OFF, the control unit 11 does not execute steps S102 to S105 ( In other words, the present process ends without causing the dispensing device 20 to start the dispensing process. In this case, the control unit 11 accesses the prescription data table D3 and sets the automatic start flag and execution status flag of the target prescription data to "0".

Further, even if it is determined in step S102 that any of the exception conditions are satisfied, the control unit 11 does not execute steps S103 to S105 (that is, without causing the dispensing device 20 to start the dispensing process). End this process. Also in this case, the control unit 11 accesses the prescription data table D3 and sets the automatic start flag and the execution status flag of the target prescription data to "0".

[4-2] FIG. 13 is a flowchart showing an example of processing executed by the dispensing control system 1 when an operation for displaying the list screen G1 is performed.

As shown in FIG. 13, first, the control unit 11 displays the list screen G1 on the display unit 15 (S110). In this case, the control unit 11 accesses the prescription data table D3 and displays a list of prescription data whose automatic start flag and execution status flag are "0" on the list screen G1. Here, the prescription data for which the automatic start flag and the execution status flag are "0" are the prescription data for which the dispensing process was not automatically started.

While the list screen G1 is being displayed, the control unit 11 monitors whether or not any of the prescription data displayed on the list screen G1 is selected by the user (S111).

When any prescription data is selected by the user, the control unit 11 identifies an authorized person who can instruct the start of dispensing processing of the selected prescription data (S112). Specifically, the control unit 11 refers to the authority identification table D7 and acquires the authority level (required authority level) required to instruct the start of the dispensing process of the selected prescription data. For example, in the case of the authority identification table D7 shown in FIG. 11, the control unit 11 determines whether or not any one of the conditions C1 to C7 is satisfied. If any one of the conditions C1 to C7 is satisfied, the control unit 11 acquires the required authority level associated with the condition. On the other hand, if none of the conditions C1 to C7 are satisfied, the control unit 11 acquires the required authority level associated with the condition C8. Then, the user having the acquired required authority level is specified as the authority.

After executing step S112, the control unit 11 determines whether or not the current user (logged-in user) is the authorized person identified in step S112 (S113). Specifically, the control unit 11 determines whether or not the current authority level of the user is the required authority level acquired in step S112. In this case, if the current user's authority level is the required authority level, the current user is determined to be an authorized person.

If the current user is not the authorized person, the control section 11 displays the instruction screen G2 on the display section 15 (S119). However, in this case, the control unit 11 does not display the execution button P22 on the instruction screen G2. Note that the control unit 11 may display the execution button P22 on the instruction screen G2 in a state in which it cannot be pressed (for example, in a grayed out state).

On the other hand, if the current user is the authorized person, the control section 11 displays the instruction screen G2 on the display section 15 (S114). In this case, the control unit 11 displays the execution button P22 on the instruction screen G2. Then, the control unit 11 monitors whether or not the execution button P22 has been pressed by the user (S115). When the execution button P22 is pressed, the control unit 11 causes the dispensing device 20 to start dispensing processing of the prescription data selected in step S111 (S116). After that, the control unit 11 monitors whether or not the dispensing process is completed (S117), and when the dispensing process is completed, the control unit 11 registers the execution result of the dispensing process in the execution history table D4 (S118).

Steps S116-S118 are the same as steps S103-S105 in FIG. However, in step S118, the user ID and authority level of the user who pressed the execution button P22 are registered in the "start instruction person" and "authority level" fields of the execution history table D4. Also, the comment entered in the comment column P21 of the instruction screen G2 is registered in the "comment" field of the execution history table D4. Furthermore, the value "0" is registered in the "automatic start flag" field of the execution history table D4.

In FIG. 13, the process of step S113 is executed before step S114. The process of step S119 may be omitted so that it is executed when it is determined. If the current user is determined to be the authorized person in the process of step S113 in this case, the process of step S116 is executed, and if the current user is determined not to be the authorized person, an error message to that effect is displayed. and the processing may be terminated.

Note that while the instruction screen G2 is being displayed, a process of displaying a comment input by the user in the comment column P21, a process of monitoring whether or not the back button P23 has been pressed, and a process of monitoring whether or not the back button P23 has been pressed are executed. A process is also executed to display the list screen G1 on the display unit 15 when the list screen G1 is displayed, but is omitted in FIG. 13 for simplicity of explanation.

[5. Summary] According to the dispensing control system 1 described above, by providing the automatic start function flag D5 and the determination unit 107, the user can automatically start the dispensing process, or the prescribed authorized person can enter the prescription information. It becomes possible to select whether to start dispensing processing after confirmation. That is, it is possible to match the method of starting dispensing processing to the user's desire. As a result, it becomes possible to improve the convenience for the user.

Further, according to the dispensing control system 1, by providing the exception condition table D6 and the determination unit 107 (and the target prescription data determination unit 108 or the immediately preceding prescription data determination unit 109), in principle, the automatic start function of dispensing processing can be performed. When set to ON, only in a specific case, it is possible to start the dispensing process only after a predetermined authorized person confirms the prescription information without automatically starting the dispensing process exceptionally.

For example, when a specific drug requiring caution is included in the target prescription data (exceptional conditions EC1 and EC2), or when the patient of the target prescription data is a specific patient requiring caution (exceptional condition EC3), Exceptionally, it is possible to prevent the dispensing process from starting without a start instruction from a predetermined authorized person. That is, it is possible to ensure that the dispensing process is executed after the prescribed authorized person has fully confirmed the patient information and prescription details.

In addition, when the target prescription data is manually input via the input screen of the dispensing control system 1 (exception condition EC4), or when the inspection result in the host system 2 is "warning present" (exception condition In EC5) as well, it is possible to exceptionally prevent the dispensing process from starting without a start instruction from a predetermined authorized person. In other words, it is possible to ensure that the dispensing process is executed after the prescribed authorized person confirms that there is no problem with the prescription information.

Furthermore, if the immediately preceding prescription data contains a drug that requires special care so that no drug remains in the portion of the dispensing device 20 that comes into contact with the drug during the dispensing process (such as the drug input unit) (exception condition In EC6) as well, it is possible to exceptionally prevent the dispensing process from starting without a start instruction from a predetermined authorized person. That is, it is possible to ensure that the dispensing process is executed after a predetermined authorized person fully confirms that there is no medicine left in the medicine loading unit or the like.

Although there are laws such as the Pharmacist Law regarding dispensing work, as a result of the functions described above being provided in the dispensing control system 1, the user can take into consideration the legality and efficiency of dispensing work through automation. It is possible to determine how to use the dispensing control system 1 and use the dispensing control system 1 according to that usage.

In addition, the dispensing control system 1 generates "medicine" that is taken by people, which is directly linked to life. It is very important to make the boundary between the case of improving efficiency by In this respect, as a result of providing the dispensing control system 1 with the functions described above, in principle, the dispensing process can be started automatically to improve efficiency, while human intervention is required to sufficiently ensure safety. It is possible to ensure that the dispensing process is performed manually in the specific case where the dispensing process is to be performed manually.

Furthermore, according to the dispensing control system 1, by providing the authorized person identification table D7 and the authorized person setting unit 113, it becomes possible to set an appropriate authorized person according to the target prescription data or the immediately preceding prescription data. . For example, when special attention is required (conditions C1 and C6), only an especially experienced pharmacist can instruct the start of dispensing processing, and in normal cases (condition C8), an especially experienced pharmacist Therefore, even a pharmacist who is not an ordinary pharmacist can give an instruction to start dispensing processing.

As described above, the dispensing control system 1 generates “medicine” that is directly linked to life and is taken by humans. The boundary with the case of automating and improving efficiency becomes very important. In this respect, as a result of the provision of the functions described above in the dispensing control system 1, when dispensing processing should be executed with human intervention in order to sufficiently ensure safety, the situation at that time (target prescription data or the most recent prescription data).

[6. Modifications] The present invention is not limited to the embodiments described above.

[6-1. Modification 1] Regarding the prescription data for which the automatic start of the dispensing process is restricted (suppressed) by any of the exception conditions EC1 to EC6 even though the automatic start function is set to ON, on the list screen G1, Information to that effect and the exception condition may be displayed. By doing so, the user may easily understand that the automatic start of the dispensing process has been restricted (deterred) and the reason thereof.

[6-2. Modification 2] For example, although only one dispensing device 20 is shown in FIG. 1, a plurality of dispensing devices 20 may be controlled by the dispensing control system 1 (control device 10). FIG. 14 shows a modification, in which the dispensing control system 1 includes a first dispensing device 20A and a second dispensing device 20B. In this case, by adding a "dispensing device" field indicating the dispensing device 20 that executed the dispensing process to the execution history table D4, it is possible to later specify which dispensing device 20 executed the dispensing process. good too.

[6-3. Modification 2A] In the dispensing control system 1 shown in FIG. 14, the second dispensing device 20B does not have to perform dispensing processing fully automatically without requiring human operation. That is, the second dispensing device 20B may be such that a person mainly performs dispensing processing while receiving assistance from the device. Exception condition EC7 as shown in FIG. 15 may be set in exception condition table D6 in this case.

Exceptional condition EC7 shown in FIG. 15 is a condition that "predicted dispensing time of target prescription data is 20 minutes or longer". In this case, the target prescription data determination unit 108 executes dispensing processing of the target prescription data by the first dispensing device 20A (that is, a dispensing device that performs dispensing processing fully automatically) based on the prescription contents of the target prescription data. The time required for dispensing is predicted, and it is determined whether or not the time (predicted dispensing time) is 20 minutes or more. Then, when it is determined that the exceptional condition EC7 is satisfied, the determining unit 107 determines to limit the automatic start of dispensing processing for the target prescription data.

For prescription data that takes a long time to execute dispensing processing by the first dispensing device 20A, dispensing can be completed in a shorter time if the user performs the dispensing processing on the second dispensing device 20B. can be efficient. In this regard, in the above-described manner, even if the automatic start function is set to ON in a case where it takes a long time to execute the dispensing process by the first dispensing device 20A, Exceptionally, the first dispensing device 20A is prevented from executing the dispensing process. As a result, the user can perform dispensing processing with the second dispensing device 20B, and the efficiency of dispensing work can be improved.

[6-4. Modification 3] The exception condition table D6 shown in FIGS. 10 and 15 contains data indicating conditions for exceptionally restricting the automatic start of the dispensing process even when the automatic start function is set to ON. However, even if the automatic start function is set to OFF, an exception condition table indicating conditions for exceptionally not restricting the automatic start of the dispensing process is stored in the setting data storage unit 101. You may do so.

FIG. 16 shows an example of the exception condition table D8 in this case. The exceptional condition table D8 may be provided together with the exceptional condition table D6, or may be provided instead of the exceptional condition table D6. Also, FIG. 17 shows a functional block diagram in this case. The functional block diagram shown in FIG. 17 differs from the functional block diagram shown in FIG. 4 in that it includes a date/time determination unit 116 . The date and time determination unit 116 determines whether or not the current conditions set in the setting data stored in the setting data storage unit 101 are satisfied. Details will be described later.

In the exception condition table D8, conditions regarding prescription data that do not need to limit the automatic start of dispensing processing are set. In the exception condition table D8, conditions related to days or times when the automatic start of the dispensing process needs to be restricted, or conditions related to days or times when the automatic start of the dispensing process does not need to be restricted are set. Exceptional conditions EC11, EC12, and EC13 are set in the exceptional condition table D8 shown in FIG. Exceptional conditions EC11 and EC12 correspond to conditions relating to prescription data that do not need to limit the automatic start of dispensing processing. Exceptional condition EC13 corresponds to a condition relating to days (days of the week) on which automatic start of dispensing processing should not be restricted.

The exceptional condition EC11 is a condition that "the target prescription data is the same as the prescription data previously prescribed to the same patient". Here, the case where the target prescription data is the same as the prescription data previously prescribed to the same patient means that the target prescription data is the same as the prescription data previously prescribed to the same patient and the prescription content is the same. be. In addition, for example, if all of the medical institution, clinical department, doctor, drug, usage, dosage, number of days, and quantity are the same, the contents of the prescription may be considered to be the same. If the specific partial items of the two are the same, the prescription contents may be considered to be the same.

When such an exception condition EC11 is set, for example, the target prescription data determination unit 108 refers to the DO prescription flag of the target prescription data to determine whether the target prescription data is input (generated) by the DO prescription function. It is determined whether or not. Then, when the target prescription data is input by the DO prescription function, the target prescription data determination unit 108 determines that the exception condition EC11 is satisfied.

Alternatively, the target prescription data determination unit 108 refers to the prescription data table D3 to determine whether the same prescription data as the target prescription data exists among the prescription data previously prescribed to the same patient. You may do so. Then, when such prescription data exists, the target prescription data determination unit 108 may determine that the exceptional condition EC11 is satisfied.

In addition, for example, when the prescription data prescribed to the patient in the past is stored in a public database constructed by a country or a specific region and shared by the medical and dispensing industries, the target prescription data determination unit 108 determines whether the public database may be accessed to determine whether or not there is prescription data identical to the target prescription data among the prescription data prescribed to the same patient in the past. Then, when such prescription data exists, the target prescription data determination unit 108 may determine that the exceptional condition EC11 is satisfied.

If it is determined that the exception condition EC11 is satisfied, the determining unit 107 exceptionally determines not to restrict the automatic start of dispensing processing of the target prescription data even if the automatic start function is OFF. 1 start control unit 111 automatically causes dispensing device 20 to start dispensing processing of the target prescription data. In general, it is considered that there is little need to reconfirm prescription data that is the same as prescription data that has been prescribed to the same patient in the past. In such a case, exceptionally, it is possible to automatically start dispensing processing.

Note that the exceptional condition EC11 may be a condition that "target prescription data is the same as or similar to prescription data previously prescribed to the same patient." Here, the case where the target prescription data is similar to the prescription data previously prescribed to the same patient means that the target prescription data is not the same as the prescription data prescribed to the same patient in the past, but it is considered to be the same. This is a case where there is no problem even if

Alternatively, instead of the exception condition EC11, an exception condition may be set such that "dispensing processing of prescription data that is the same as or similar to the target prescription data has been executed by the dispensing device 20 in the past." When such an exception condition is set, the target prescription data determination unit 108 refers to the prescription data table D3 (and the execution history table D4) to determine whether prescription data identical or similar to the target prescription data is dispensed. It is only necessary to determine whether or not it has been executed by the dispensing device 20 in the past. Then, when dispensing processing of prescription data identical or similar to the target prescription data has been executed by the dispensing device 20 in the past, the determination unit 107 exceptionally determines that the automatic start of the dispensing processing is not restricted. can be

In addition to the exception conditions as described above, "when the current user (currently logged-in user) has executed dispensing processing of prescription data identical or similar to the target prescription data by the dispensing device 20 in the past, It is also possible to set an exception condition that the user is the same as the user who logged in to the dispensation control system at the time. Dispensing processing of prescription data identical or similar to the target prescription data has been executed by the dispensing device 20 in the past, and the user at that time (the user logged in at that time) is the current The determination unit 107 may exceptionally determine that the automatic start of dispensing processing is not to be restricted when the user is the same as the user.

Further, instead of the exception condition EC11, "the target prescription data is the same or similar to the prescription data prescribed in the past to the same patient, and the dispensing process of the prescription data that is the same or similar to the target prescription data has been performed by the dispensing device in the past" 20 has been executed" may be set as an exception condition. Here, the same prescription data means the same patient and the same prescription. In addition, for example, if all of the medical institution, clinical department, doctor, drug, usage, dosage, number of days, and quantity are the same, the contents of the prescription may be considered to be the same. The prescription contents may be considered to be the same when the specific partial items of the two are the same. Further, the case where the prescription data are similar is a case where there is no problem even if the patient is the same and the prescription contents are not the same, but the prescription contents are considered to be the same.

When such an exception condition is set, the target prescription data determination unit 108 accesses the aforementioned public database to determine whether the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient. You may make it determine whether it is. Alternatively, the target prescription data determination unit 108 refers to the prescription data table D3 (and the execution history table D4) to determine whether dispensing processing of prescription data identical or similar to the target prescription data has been executed by the dispensing device 20 in the past. You may make it determine whether there exists.

and that the target prescription data is the same as or similar to prescription data that has been prescribed to the same patient in the past, and that dispensing processing of prescription data that is the same as or similar to the target prescription data has been executed by the dispensing device 20 in the past Exceptionally, the determination unit 107 may determine not to limit the automatic start of the dispensing process.

On the other hand, even if the target prescription data is identical or similar to the prescription data previously prescribed to the same patient, dispensing processing of prescription data identical or similar to the target prescription data was executed by the dispensing device 20 in the past. If not, the determination unit 107 may determine to restrict the automatic start of dispensing processing. In other words, even if the target prescription data is the same or similar to the prescription data prescribed in the past to the same patient, unless it was dispensed at one's own hospital or dispensing pharmacy (other hospitals or dispensing pharmacies If the medicine has been dispensed), the dispensing process may not be started automatically, and the dispensing process may be started after waiting for a start instruction from a predetermined authorized person.

Exceptional condition EC12 is a condition that "target prescription data is provided from host system 2". When such an exceptional condition E12 is set, for example, the target prescription data determination unit 108 accesses the prescription data table D3 and refers to the input system flag of the target prescription data to determine whether the target prescription data is Determines whether or not it has been provided from Then, when the target prescription data is provided from the host system 2, the target prescription data determination unit 108 determines that the exception condition EC12 is satisfied.

If it is determined that the exception condition EC12 is satisfied, even if the automatic start function is OFF, the determination unit 107 exceptionally determines that the automatic start of the dispensing process for the target prescription data is not restricted. The start control unit 111 automatically causes the dispensing device 20 to start dispensing processing of the target prescription data. Regarding the prescription data provided from the host system 2, since the inspection is also performed on the host system 2 side, it is considered that there is little need to check again. , exceptionally in such cases, it is possible to automatically start the dispensing process.

Exceptional condition EC13 is a condition that "today is Monday." When such an exception condition E13 is set, the date/time determination unit 116 determines whether or not today is Monday, using a clock function provided in the computer, for example. If today is Monday, it is determined that exceptional condition EC13 is satisfied.

Determining unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the determination result of date/time determining unit 116 . For example, when the date/time determination unit 116 determines that the exception condition EC13 is satisfied, the determination unit 107 exceptionally restricts the automatic start of the dispensing process for the target prescription data even if the automatic start function is OFF. It is determined not to, and the first start control unit 111 automatically causes the dispensing device 20 to start dispensing processing of the target prescription data. In general, it is expected that the number of patients visiting hospitals on Mondays will increase and the number of dispensing processes will increase. , it is possible to automatically start the dispensing process.

The exception condition EC13 is merely an example, and a period (busy period) in which the number of dispensing processes is expected to increase may be set as the exception condition. Further, by setting a time period outside business hours as an exception condition, dispensing processing may be automatically started in a time period outside business hours.

When the exception condition table D8 as shown in FIG. 16 is set, the process shown in FIG. 12 is executed as described below.

Specifically, when it is determined in step S101 that the automatic start function is not set to ON (when the automatic start function is set to OFF), for example, the processing shown in FIG. 18 is executed. be. That is, first, the control unit 11 refers to the exception condition table D8 shown in FIG. 16 and determines whether or not any one of the exception conditions EC11 to EC13 is satisfied (S120).

Then, if any one of the exceptional conditions EC11 to EC13 is satisfied, the control unit 11 causes the dispensing device 20 to start dispensing processing of the target prescription data (S121). After that, the control unit 11 monitors whether the dispensing process is completed (S122), and when the dispensing process is completed, the control unit 11 registers the execution result of the dispensing process in the execution history table D4 (S123). These steps S121 to S123 are the same as steps S103 to S105 in FIG.

On the other hand, if none of the exceptional conditions EC11 to EC13 are satisfied, the control unit 11 ends the process without executing steps S121 to S123 (that is, without causing the dispensing device 20 to start the dispensing process). In this case, the control unit 11 accesses the prescription data table D3 and sets the automatic start flag and execution status flag of the target prescription data to "0".

According to the modified example 3, by providing the exception condition table D8, in principle, the automatic start function of the dispensing process is set to OFF, and only in a specific case, the dispensing process is automatically started exceptionally. can be started at

For example, only when the target prescription data is specific prescription data (exception conditions EC11, EC12), it is possible to exceptionally start dispensing processing automatically. Specifically, when the target prescription data is the same as the prescription data previously prescribed to the same patient, or when the target prescription data is provided from the host system 2, the prescription information is reissued. When the need to confirm is low (in other words, when safety is sufficiently ensured without reconfirming the prescription information), it is possible to exceptionally start the dispensing process automatically, As a result, it is possible to improve the efficiency of dispensing work.

In addition, when the number of dispensing processes is expected to increase (exception condition EC13), such as Monday when many patients visit the hospital, the dispensing process should be automatically started as an exception. As a result, it becomes possible to improve the efficiency of dispensing work.

As described above, the dispensing control system 1 generates “medicine” that is directly linked to life and is taken by humans. The boundary with the case of automating and improving efficiency becomes very important. In this respect, according to Modification 3, in principle, the dispensing process is initiated through human intervention to sufficiently ensure safety, and the need for human intervention to execute the dispensing process is low. Only in this case, it is possible to improve efficiency by automatically starting dispensing processing.

[6-5. Modification 4] The dispensing control system 1 (control device 10) has an execution history output control section that displays the execution history of the dispensing process registered in the execution history table D4 on the display section 15 and causes the printing section 16 to print it. may be provided.

For example, the user may specify search conditions, and the execution history output control unit may display or print a list of execution histories that satisfy the search conditions. Alternatively, the execution history output control unit may display or print a total of execution histories that satisfy the search condition. As search conditions, for example, period, patient, start instruction person, authority level, whether or not automatic start, etc. may be specified.

Further, in the case of Modification 2A, the execution history output control unit provides a list and the number of dispensing processes executed by the first dispensing device 20A (that is, dispensing processes fully automatically performed mainly by the device), A list and number of dispensing processes executed by the second dispensing device 20B (that is, dispensing processes mainly performed by a person with the assistance of the device) may be displayed or printed.

Note that not only the execution history of dispensing processing but also the history of various operations performed in the dispensing control system 1 may be registered in the data storage unit 100 . Further, an operation history output control section that displays the operation history on the display section 15 and causes the printing section to print the operation history may be provided.

[6-6. Modification 5] The user may be forcibly logged off each time dispensing processing of one prescription data is executed.

In a system such as the dispensing control system 1, a certain user is logged in and used, so that the user has instructed the start of dispensing processing in the system. , there is a possibility that another user actually instructs the start of dispensing processing. In this regard, if the user is forcibly logged off each time dispensing processing for one prescription data is executed, login is required each time to issue a dispensing processing start instruction. It becomes difficult to operate like

Note that in this modification, logoff may be performed immediately after the dispensing process is completed, or may be performed after a predetermined time has elapsed after the dispensing process is completed. For example, if the user does not perform any operation for a predetermined period of time (for example, 20 seconds) after the dispensing process is completed, the user is logged off. , the dispensing process may be executed continuously. Further, whether or not there is a forced logoff, the method of forced logoff, and the predetermined time may be arbitrarily set by a user having predetermined authority (for example, a user with authority level "6").

1 dispensing control system, 2 host system, 10 control device, 11 control unit, 12 storage unit, 13 communication unit, 14 operation unit, 15 display unit, 16 printing unit, 17 database, 20 dispensing device, 20A first dispensing device, 20B second dispensing device, 100 data storage unit, 101 setting data storage unit, 102 authorized person identification data storage unit, 103 input screen display control unit, 104 prescription data acquisition unit, 105 first prescription data acquisition unit, 106 second prescription data acquisition unit 107 determination unit 108 target prescription data determination unit 109 immediately preceding prescription data determination unit 110 start control unit 111 first start control unit 1121 second start control unit 113 authorized person setting unit 114 start instruction Reception unit 115 Execution history registration unit 116 Date and time determination unit G1 List screen G2 Instruction screen P21 Comment column P22 Execution button P23 Back button D1 User table D2 Patient table D3 Prescription data table D4 Execution History table, D5 Automatic start function flag, D6 Exceptional condition table, D7 Authorized person identification table, D8 Exceptional condition table.

Claims (10)

prescription data acquisition means for acquiring target prescription data to be processed for dispensing;
The conditions of the target prescription data related to the type of drug included in the target prescription data, and the authority level necessary for instructing the start of dispensing processing of the target prescription data and having a different operable range in the dispensing control system a storage unit that stores setting information that associates with each other, for each of the conditions of the plurality of target prescription data;
The user having the authority level associated with the condition corresponding to the type of drug included in the target prescription data acquired by the prescription data acquisition means, among the conditions of the plurality of target prescription data, is selected from the prescription data. an authorized person setting means for setting an authorized person capable of instructing the start of the dispensing process for the target prescription data acquired by the acquiring means ;
A dispensing control system comprising: When the target prescription data acquired by the prescription data acquisition means includes a prescribed drug, the authorized person setting means assigns a user having an authorization level with the operable range set to the prescribed range. and the operable range is set to a range different from the predetermined range when the target prescription data obtained by the prescription data obtaining means includes a drug different from the predetermined drug. setting a user with a level as the authorized person;
The dispensing control system of Claim 1. each of the plurality of conditions of the plurality of target prescription data is associated with a plurality of different authority levels;
3. The dispensing control system according to claim 1 or 2. The authority levels are a first authority level capable of performing predetermined operations in the dispensing control system, and a second authority level capable of performing operations in a more restricted range than the first authority level in the dispensing control system . 2 authority levels and
When the target prescription data acquired by the prescription data acquiring means includes a first medicine, the authorized person setting means sets a user having the first authority level as the authorized person, and When the target prescription data acquired by the acquiring means includes a second drug with a lower degree of caution than the first drug, the user having the first authority level or the second authority level is the authorized person. set as
The dispensing control system according to any one of claims 1-3 . further comprising start instruction receiving means for displaying an instruction screen capable of receiving an instruction to start the dispensing process;
The start instruction receiving means displays the instruction screen so that the authorized person set by the authorized person setting means can issue the start instruction, and the authorized person other than the authorized person set by the authorized person setting means displays the instruction screen. displaying the instruction screen so that the user of is unable to give the start instruction;
The dispensing control system according to any one of claims 1-4 . The dispensing of the target prescription data acquired by the prescription data acquisition means when the start instruction receiving means receives the start instruction from the authorized person set by the authorized person setting means on the instruction screen. further comprising start control means for causing the dispensing execution means to start processing;
A dispensing control system according to claim 5 . On the display screen displaying a plurality of target prescription data to be the target of the dispensing process,
When the target prescription data acquired by the prescription data acquisition means is target prescription data for which automatic start of the dispensing process by the dispensing execution means is restricted, automatic start of the dispensing process is restricted. displaying information indicating that the
The dispensing control system according to any one of claims 1-6 . The authority level includes at least the authority level that allows all operations in the dispensing control system and the ability to perform operations other than the editing operation of the master data stored in the storage unit among all the operations. and an authority level at which each of the master data editing operation, the medicine filling operation, and the dispensing process start instruction is restricted,
The dispensing control system according to any one of claims 1-7 . When the function for causing the dispensing execution means to automatically start the dispensing process is set to ON, and when the target prescription data includes a drug that requires careful handling , the start control means causing the dispensing execution means to start the dispensing process when the start instruction receiving means receives the start instruction from the authorized person set by the authorized person setting means;
A dispensing control system according to claim 6 . the computer
a prescription data acquisition step of acquiring target prescription data to be subjected to dispensing processing, the target prescription data including a plurality of drugs of different types ;
The conditions of the target prescription data related to the type of drug included in the target prescription data, and the authority level necessary for instructing the start of dispensing processing of the target prescription data and having a different operable range in the dispensing control system a storage step of storing setting information associated with each other for each of the conditions of the plurality of target prescription data;
A user having the authority level associated with a condition corresponding to a type of drug included in the target prescription data acquired in the prescription data acquisition step, among the conditions of the plurality of target prescription data, is selected from the prescription data. an authorized person setting step of setting an authorized person capable of instructing the start of the dispensing process of the target prescription data acquired in the acquiring step ;
Dispensing control method to implement.

Images