JP6769089B2 - 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 perform dispensing processing based on prescription data are known. For example, there is known a dispensing device in which a robot executes a dispensing process fully automatically based on prescription data.

Japanese Unexamined Patent Publication No. 2013-052250

Among the above-mentioned dispensing devices, there is a dispensing device capable of automatically starting the dispensing process when the prescription data is input or received. Some users of such dispensing devices want to start the dispensing process automatically, while others want to start the dispensing process after the predetermined authority confirms the prescription information. There are also users. Further, in a specific case, there is a user who wants to start the dispensing process after the predetermined authority confirms the prescription information, and in other cases, the dispensing process is automatically started. In this respect, in the past, the method of starting the dispensing process may not meet the user's request, and there was a point that it was not sufficient in terms of user convenience.

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 the convenience of a user.

In order to solve the above problems, the dispensing control system according to the present invention acquires target prescription data to be the target of the dispensing process in the dispensing control system capable of automatically starting the dispensing process by the dispensing executing means. The prescription data acquisition means to be used, the setting data storage means for storing the setting data set for determining whether to limit the automatic start of the dispensing process, and the automatic dispensing process based on the setting data. A means for determining whether or not to limit the start, and when it is determined that the automatic start of the dispensing process is not restricted, the first means for automatically causing the dispensing execution means to start the dispensing process of the target prescription data. 1 When it is determined that the start control means and the automatic start of the dispensing process are restricted, and when the start instruction of the dispensing process is received from a predetermined authority, the dispensing process of the target prescription data is performed by the dispensing execution means. Includes a second start control means to start.

Further, the dispensing control method according to the present invention is a setting set for determining whether or not to limit the automatic start of the dispensing process and the prescription data acquisition step for acquiring the target prescription data to be the target of the dispensing process. Based on the data, a determination step for determining whether or not to limit the automatic start of the dispensing process, and when it is determined that the automatic start of the dispensing process is not restricted, the dispensing of the target prescription data is automatically performed. The target prescription data when it is determined that the first start control step for causing the dispensing execution means to start the process and the automatic start of the dispensing process are restricted, and when the start instruction of the dispensing process is received from a predetermined authority. The present invention includes a second start control step of causing the dispensing execution means to start the dispensing process.

Further, in one aspect of the present invention, the setting data includes a condition relating to prescription data in which the automatic start of the dispensing process needs to be restricted, or a condition relating to prescription data in which the automatic start of the dispensing process does not need to be restricted. May be set. The dispensing control system may include a target prescription data determination means for determining whether or not the target prescription data satisfies the above 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.

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

Further, in one aspect of the present invention, the condition may include a condition relating to patient data included in the target prescription data.

Further, in one aspect of the present invention, the prescription data acquisition means may acquire prescription data input by another system as the target prescription data. The other system may allow an audit of prescription data to be performed. The condition may include a condition as to whether or not the result of the audit on the target prescription data is a predetermined result.

Further, in one aspect of the present invention, a display control means for displaying an input screen for accepting input of prescription data on the display means may be included. The prescription data acquisition means acquires the first prescription data acquisition means that acquires the prescription data input via the input screen as the target prescription data, and the prescription data input by another system as the target prescription data. The second prescription data acquisition means to be used may be included. The condition may include a condition as to whether the target prescription data is the prescription data input via the input screen or the prescription data input by the other system.

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

Further, in one aspect of the present invention, the condition may include a condition as to whether or not the dispensing process of the same or similar prescription data as the target prescription data has been executed by the dispensing execution means in the past. Good.

Further, in one aspect of the present invention, the determination means means that even if the target prescription data is the same or similar prescription data as the prescription data that has been prescribed to the same patient in the past, the target prescription If the dispensing process of the same or similar prescription data as the data has not 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 the dispensing process of the same or similar prescription data as the target prescription data by the dispensing execution means. At that time, the condition of whether or not the person is the same as the person logged in to the dispensing control system may be included.

Further, in one aspect of the present invention, the condition may include a condition relating 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 a condition relating to prescription data in which the automatic start of the dispensing process needs to be restricted, or a condition relating to prescription data in which the automatic start of the dispensing process does not need to be restricted. May be set. The dispensing control system may include a immediately preceding prescription data determining means for determining whether or not the prescription data that was the target of the dispensing process executed immediately before satisfies the above 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 immediately preceding prescription data determination means.

Further, in one aspect of the present invention, the setting data includes a condition relating to a date or time when the automatic start of the dispensing process needs to be restricted, or a date or time when the automatic start of the dispensing process does not need to be restricted. Conditions may be set. The dispensing control system may include a date and time determining means for determining whether or not the present condition is satisfied. The determination means may determine whether or not to limit the automatic start of the dispensing process based on the determination result of the date and time determination means.

Moreover, in one aspect of the present invention, the authority setting means for setting the authority may be included based on the target prescription data.

Further, in one aspect of the present invention, an authorized person who stores the authorized person identification data for specifying the authorized person who can instruct the start of the dispensing process of the prescription data in association with the condition concerning the prescription data. It may include a specific data storage means. When the target prescription data to be the target of the dispensing process satisfies the condition, the authority setting means sets the authority based on the authority identification data associated with the condition. May be good.

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

Further, in one aspect of the present invention, the target prescription data to be the target of the dispensing process, the authority data regarding the authority who has instructed to start the dispensing process, and the comment data input by the authority are associated with each other. It may include a registration means to be registered in a predetermined storage means.

Further, in one aspect of the present invention, the dispensing executing means is (a) an automatic dispensing / packaging device or system for powders, (b) an automatic dispensing / packaging device or system for tablets, and (c) an automatic dispensing device or system. Dispensing / dispensing device or system, (d) automatic mixed dispensing device or system of anticancer drug, (e) dispensing inspection device or system, (f) a plurality of devices or systems of any one of these devices are connected. It may be either an embodiment or (g) an aspect 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 limit the automatic start of the dispensing process, and as a result, it is possible to improve the convenience of the user.

It is a figure for demonstrating the structure of the dispensing control system which concerns on embodiment of this invention. It is a figure which shows an example of a list screen. It is a figure which shows an example of an instruction screen. It is a functional block diagram of the dispensing control system which concerns on embodiment of this invention. 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 the prescription data table. It is a figure which shows an example of the execution history table. It is a figure which shows an example of the automatic start function flag. It is a figure which shows an example of the exception condition table. It is a figure which shows an example of the authority person identification table. It is a flow chart which shows an example of the process executed by a dispensing control system. It is a flow chart which shows another example of the process executed by a dispensing control system. It is a figure for demonstrating the structure of the dispensing control system which concerns on other embodiment of this invention. It is a figure which shows another example of the exception condition table. It is a figure which shows another example of the exception condition table. It is a functional block diagram of the dispensing control system which concerns on other embodiment of this invention. It is a flow chart which shows an example of the process executed by the dispensing control system which concerns on other embodiment of this invention.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or equivalent elements are designated by the same reference numerals, and duplicate description is omitted. In the dispensing industry, the terms "dispensing" and "preparation" may be used separately, but in this specification, "dispensing" is used in a broad sense, and "dispensing" in the present specification is used. , Both "dispensing" in the narrow sense (that is, "dispensing" distinguished from "preparation") and "preparation" are included.

[1. Overall Configuration] FIG. 1 is a diagram for explaining a configuration of a dispensing control system according to an embodiment of the present invention. FIG. 1 shows a dispensing control system 1 and a higher-level 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 a dispensing process.

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

The control unit 11 includes one or a plurality of microprocessors, and executes processing according to a program stored in the storage unit 12. The storage unit 12 includes, for example, information storage media for main storage (RAM or the like) and auxiliary storage (hard disk drive or solid state drive or the like), and stores a program executed by the control unit 11. The storage unit 12 also operates as a work memory of the control unit 11. The communication unit 13 is for data communication with another device via a communication network.

For example, the program or data is provided to the control device 10 via a communication network. The control device 10 may include a component for reading a program 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 the information storage medium.

The operation unit 14 is for receiving a user's operation, and is, for example, a keyboard, a mouse, a touch pad, a touch panel, or the like. The display unit 15 displays a screen according to an instruction from the control unit 11, and is, for example, a liquid crystal display or an organic EL display. The printing unit 16 prints according to an instruction from the control unit 11, and is, for example, a printer device or the like.

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

The dispensing device 20 (an example of a dispensing execution means) is a device that executes a dispensing process. For example, the dispensing process can be executed fully automatically based on prescription data without requiring human operation (work). It is a device. The dispensing device 20 may be referred to as a “dispensing system”.

Dispensing treatment includes, for example, at least one of dispensing / sacheting of powder (powder), dispensing / sacheting of tablets, dispensing / dispensing of liquid medicine, mixed injection of anticancer drug, or inspection of various dispensed drugs. Including. Further, the dispensing device 20 is, for example, an automatic dispensing / dispensing device for powders (powder), an automatic dispensing / packaging device for tablets, an automatic dispensing / dispensing device for liquid medicine, an automatic mixed dispensing device for anticancer agents, or a dispensing inspection. Equipment, etc. Alternatively, the dispensing device 20 may be a device in which a plurality of devices of any one of these devices are connected. Alternatively, the dispensing device 20 may be one in which a plurality of types of devices among these devices are connected.

For example, the dispensing device 20 is a dispensing device that includes a single-armed or double-armed robot, and the dispensing process is executed by the robot. More specifically, for example, automatic dispensing / dispensing of powders such that a robot weighs and packages powders using powders stored in a plurality of drug containers installed in the housing of the device for each type. The packaging device corresponds to an example of the dispensing device 20. Further, for example, an automatic mixed injection device for an anticancer drug in which a robot mixes a plurality of drugs installed in the housing of the device to dispense the anticancer drug also corresponds to an example of the dispensing device 20.

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

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 integrally configured. 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 function of the control device 10.

Prescription data is input in the higher system 2, and the prescription data input in the higher 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 medical care department in the hospital, and the dispensing control system 1 is installed in the dispensing department in the hospital. Further, for example, the host system 2 is installed in a hospital, and the dispensing control system 1 is installed in a dispensing pharmacy.

It is also possible to input prescription data in the dispensing control system 1. That is, in the dispensing control system 1, an input screen (not shown) for accepting the input of prescription data is displayed on the display unit 15, and the user of the dispensing control system 1 is issued on paper. It is possible to receive a prescription from a patient and enter prescription data while referring to the prescription. That is, in the dispensing control system 1, it is possible to cause the dispensing device 20 to execute the dispensing process based on the prescription data input by the higher-level system 2, and the dispensing process is based on the prescription data input by the dispensing control system 1. It is also possible to have the dispensing device 20 perform the treatment. The upper system 2 is not indispensable, and the upper system 2 does not have to be installed.

[2. Function overview] The dispensing control system 1 has an automatic start function capable of automatically starting the dispensing process in the dispensing device 20. 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 a user (authorized person) having a predetermined authority to receive an instruction to start the dispensing process, 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, the list screen G1 as shown in FIG. 2 is displayed on the display unit 15. The login to the dispensing control system 1 may be performed by the user entering the user ID and password on the login screen (not shown), or the ID card distributed in advance by the user. May be done by having the card reader read the. However, in the latter case, the control device 10 needs to be provided with a card reading unit for reading the information recorded on the card by a contact method or a non-contact method.

As shown in FIG. 2, the list screen G1 displays a list of prescription data in which the dispensing process has not been executed. In the example shown in FIG. 2, the prescription data A, B, and C are displayed on the list screen G1. In FIG. 2, for the sake of simplicity 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 the prescription content will be displayed as information indicating each prescription data.

When the user selects any of the prescription data displayed on the list screen G1, the 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 the dispensing process of the prescription data.

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

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

On the other hand, when the automatic start function is set to ON, the prescription data input in the host system 2 is supplied to the dispensing control system 1, or the prescription data is input in the dispensing control system 1 via the input screen. In such a case, the dispensing control system 1 automatically causes the dispensing device 20 to start the dispensing process based on the prescription data, in principle. 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 the user (authorized person) having a predetermined authority to receive the instruction to start the dispensing process. ..

In the dispensing control system 1, by providing such a function, when the user wishes to start the dispensing process after the prescription information is confirmed by a predetermined authority, the user turns off the automatic start function. By setting to, you will be able to use the dispensing control system as you wish. On the other hand, when the user desires to automatically start the dispensing process, the user can use the dispensing control system as requested 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, the automatic start of the dispensing process can be exceptionally restricted in a specific case. Therefore, in a specific case (for example, when a drug requiring special attention is included in the prescription data), the dispensing process is started after the prescription information is confirmed by a predetermined authority, and in other cases. If the user wishes to start the dispensing process automatically, the user can use this function to use the dispensing control system as he / she desires.

There are laws such as the Pharmacists Act regarding dispensing operations, but as a result of the functions described above being provided in the dispensing control system 1, users are considering legality and efficiency of dispensing operations through automation. The method of using the dispensing control system 1 can be determined, and the dispensing control system 1 can be used according to the method of use.

In addition, in the dispensing control system 1, since a person takes a “medicine” that is directly related to life, it is necessary to ensure sufficient safety by intervening a person, and the dispensing work is automated. The boundary with the case of improving efficiency is very important, but as a result of the functions described above being provided in the dispensing control system 1, in principle, the dispensing process is automatically started to improve efficiency. At the same time, in a specific case where a person should intervene to execute the dispensing process in order to sufficiently ensure safety, it is possible to ensure that the dispensing process is executed through the person.

[3. Function block] A configuration that realizes 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.

[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 realized by the database 17. The data storage unit 100 stores various data. FIGS. 5 to 11 show an example of data stored in the data storage unit 100.

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 in to the dispensing control system 1). The user table D1 shown in FIG. 5 includes "user ID", "name", "password", and "authority level" fields.

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

The Authority Level field indicates the authority level of the user. The authority level set for the user limits the operations that the user can perform in the dispensing control system 1. For example, values from "1" to "6" are set as the authority level. "6" is the highest authority level and "1" is the lowest authority level.

A user with authority level "6" can perform any operation with the dispensing control system 1. For example, editing of master data (user table D1, etc.) stored in the data storage unit 100 is permitted only to users with authority level "6". That is, registering a new user in the user table and setting / changing the authority level of each user are permitted only to the user of the authority level "6".

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

In addition, the user of authority level "4" can perform operations other than editing the master data and filling the drug. For example, specific operations that require special attention (referred to here as "special operations") are permitted only to users with authority levels "4" to "6".

In addition, the user of authority level "3" can edit the master data, fill the medicine, and perform operations other than special operations. For example, a specific operation requiring attention (referred to here as "operation requiring attention") is permitted only to users of authority levels "3" to "6".

In addition, the user of authority level "2" can perform operations other than editing of master data, filling of chemicals, special operations, and operations requiring caution. In addition, the user of the authority level "1" can perform only limited simple operations.

For example, an authority level "6" is set for a person (system administrator) who plays a role of managing the dispensing control system 1. Further, any of the authority levels "2" to "5" is set for the pharmacist other than the system administrator. Specifically, the authority level "2" is set for pharmacists who are relatively inexperienced, and the authority level "3" is set for pharmacists who have some experience. In addition, an authority level "4" is set for an experienced pharmacist who plays a role of managing a pharmacist with an authority level "2" or "3". The pharmacist with the authority level "4" also plays a role of managing, and the authority level "5" is set for the pharmacist with a great deal of experience. For example, the authority level "4" is set for a pharmacist (local manager) who plays a role of managing a pharmacist who works at the dispensing site at each dispensing site. The authority level "5" is set for the pharmacist (administrator) who has the role of overall management over a plurality of dispensing sites, that is, the role of managing all pharmacists working at each of the plurality of dispensing sites. Will be done. 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. The patient table D2 shows a list of patients. The patient table D2 shown in FIG. 6 includes fields for "patient ID", "name", "gender", "age", "date of birth", and "drug history". 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, gender, age, and date of birth, respectively. The "Drug History" field shows the history of medications previously prescribed to the patient. For example, when a patient first visits a dispensing pharmacy, the patient's data is registered in 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 higher-level 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", and "automatic start". Includes Flags, Execution Status Flags fields.

The "Prescription Data ID" field indicates identification information that uniquely identifies the 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 on which the prescription data was entered. Specifically, the "input system" field indicates whether the prescription data was input by the dispensing control system 1 or the host system 2. For example, if the prescription data was entered in 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 higher 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 upper system 2. In the upper system 2, the prescription data is inspected before the prescription data is provided to the dispensing control system 1. For example, conditions for prescription data that require attention are predetermined, and a warning is issued for prescription data that satisfies the conditions. After reconfirmation by the pharmacist, the prescription data subject to the warning is provided to the dispensing control system 1 as it is if there is no particular problem, and if there is a problem, it is corrected and then the dispensing control system 1 Provided to. For example, if the prescription data is input in the upper system 2 and the inspection result in the upper system 2 is "warning", the value "1" is registered in the "inspection result flag" field. If the inspection result in the higher system 2 is not "with warning", the value "0" is registered in the "inspection result flag" field.

The "DO prescription flag" field indicates whether or not the prescription data is input (generated) using the DO prescription function. The dispensing control system 1 and the upper system 2 have a DO prescription function. The DO prescription function is a function that makes it possible to easily input prescription data having 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, the value "1" is registered in the "DO prescription flag" field, otherwise the value "0" is "DO". Registered in the Prescription Flag field.

The "Patient" field indicates the patient (patient ID) that is the subject of the prescription data. The "Prescription Content" field indicates the prescription content (eg, medical institution, department, drug, dosage, dosage, number of days, and quantity).

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

The Execution Status Flag field indicates the execution status of the dispensing process of the prescription data. For example, for the prescription data in the state before the start of the dispensing process, the value "0" is registered in the "execution status flag" field. Further, for the prescription data in the state where the dispensing process is being executed, the value "1" is registered in the "execution status flag" field, and for the prescription data in the state where the dispensing process is completed, the value "2" is ". Registered in the "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 shows "execution history ID", "target prescription data", "automatic start flag", "start instructor", "authority level", "comment", "start date and time", and "end". Includes Date and Time field.

The "execution history ID" field indicates identification information that uniquely identifies each execution history. The Target Prescription Data field indicates the prescription data that was the target of the dispensing process. For example, the prescription data ID of the prescription data targeted for the dispensing process is registered in the "target prescription data" field.

The "Auto-start flag" field indicates whether or not the dispensing process has been automatically started. For example, when 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, if the dispensing process is not automatically started by the automatic start function but is executed by the start instruction given by a predetermined authority, the value "0" is the "automatic start flag". Registered in the field.

In addition, the "start instructor" field indicates the person who has given the start instruction of the dispensing process (start instructor), and the "authority level" field is the authority level of the start instructor at the time when the start instruction of the dispensing process is given. Is shown. For example, the user ID of the start instructor is registered in the "start instructor" field. Further, the authority level of the start instructor at that time is registered in the "authority level" field. In addition, the "comment" field indicates the comment entered by the start instructor. That is, the comment input in the comment field P21 of the instruction screen G2 is registered in the "comment" field. If the dispensing process is automatically started by the automatic start function, the "start instructor", "authority level", and "comment" fields are blank. Further, the "start date and time" and "end date and time" fields indicate the date and time when the dispensing process was started and ended.

As shown in FIG. 4, the data storage unit 100 includes the setting data storage unit 101. The setting data storage unit 101 stores the setting data. The setting data is data set for determining whether or not to limit the automatic start of the dispensing process. 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 capable of automatically starting the dispensing process in the dispensing device 20. The automatic start function flag D5 indicates whether this automatic start function is set to ON or OFF. For example, the auto-start function flag takes a value of "0" or "1". A value of "1" indicates that the automatic start function is set to ON. On the other hand, the value "0" indicates that the automatic start function is set to OFF. Therefore, when the automatic start function flag is set to "0", the dispensing control system 1 does not automatically start the dispensing process to the dispensing device 20, but gives a predetermined authority to instruct the start of the dispensing process. The dispensing device 20 is started to perform the dispensing process after waiting for the reception from the person.

For example, the initial value of the automatic start function flag D5 is set to "0", and the user of the authority level "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, the dispensing control system 1 causes the dispensing device 20 to automatically start the dispensing process in principle. In this regard, even when the automatic start function is set to ON, the condition (exception condition) when the automatic start of the dispensing process should be exceptionally restricted is registered in the exception condition table. For example, a user with authority level "6" can set an exception condition in the exception condition table via a predetermined setting screen.

The exception condition table D6 shown in FIG. 10 includes an "exception condition ID" and an "exception condition" field. The "exception condition ID" field indicates identification information that uniquely identifies the exception condition registered in the exception condition table D6. The Exception Condition field indicates the exception condition. In the "Exception condition" field, the exception condition is registered in a format recognizable by the computer (control unit 11). In the following, for convenience, the exception condition whose exception condition ID is "ECn" will be referred to as "exception condition ECn".

For example, in the exception condition table D6, a condition related to prescription data for which it is necessary to limit the automatic execution of the dispensing process is registered as an exception condition. The exception conditions EC1 to EC6 shown in FIG. 10 are conditions relating to prescription data for which it is necessary to limit the automatic execution of the dispensing process. Further, the exception conditions EC1 to EC5 are conditions related to the target prescription data that is the target of the dispensing process, and the exception condition EC6 is a condition related to the prescription data that was the target of the dispensing process executed immediately before. .. The exception conditions EC1 to EC6 will be described below.

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

Here, the “drug A” is, for example, a drug that requires special care in handling. Further, "drug B" is a drug that requires 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, but a prescription containing drug A or drug B is provided by setting the exception conditions EC1 and EC2. Regarding 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 authority.

The exception condition EC3 is a condition relating to 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".

Generally, caution is required when the patient is young, but by setting the exception condition EC3, the automatic start function was set to ON for prescription data in which the patient is under 10 years old. Even so, the dispensing process is not automatically started, and the dispensing process will not be started unless the start instruction is given by a predetermined authority. In addition, the condition regarding the sex of the patient or the drug history may be set as an exception condition.

The exception condition EC4 is a condition as to whether the target prescription data is the prescription data manually input by the dispensing control system 1 via the input screen or the prescription data provided by the higher-level system 2. Specifically, the exception condition EC4 is a condition that "the target prescription data is manually input".

Compared to the prescription data provided after being inspected by the higher system 2, the prescription data manually input via the input screen in the dispensing control system 1 may contain errors, so caution is required. However, by setting the exception condition EC4, the dispensing process is automatically performed for the prescription data manually input via the input screen in the dispensing control system 1 even if the automatic start function is set to ON. It will not be started and the dispensing process will not be started unless there is a start instruction from a predetermined authority.

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

Care must be taken when the inspection result of the target prescription data in the upper system 2 is "with warning", but by setting the exception condition EC5, the inspection result in the upper system 2 is "with warning". With respect to the prescription 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 authority.

The exception condition EC6 is a condition relating to the prescription data that was the subject of the dispensing process executed immediately before. Specifically, the exception condition EC6 is a condition that "drug C is included in the immediately preceding prescription data".

Here, the “drug C” is, for example, a drug that requires special attention so that the drug does not remain in the portion (drug injection section or the like) of the dispensing device 20 that comes into contact with the drug during the dispensing process. 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 section, etc., but the exception condition EC6 is set. Therefore, when the 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, and the predetermined value. The dispensing process will not start unless the authority gives a start instruction.

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

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

When the automatic start function is set to OFF, the authorized person who can give the start instruction of the dispensing process is specified based on the authorized person identification table D7, and waits for the start instruction from the authorized person. The dispensing process is performed. Similarly, even when the automatic start function is set to ON, if the automatic start function is exceptionally restricted by satisfying the exception condition of the exception condition table D6, the authorized person identification table D7 Based on the above, an authorized person who can give an instruction to start the dispensing process is specified, and the dispensing process is executed after waiting for the 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 condition registered in the authority identification table D7. The Condition field indicates the condition. In the "condition" field, the condition is registered in a format recognizable by the computer (control unit 11). The "Required Authority Level" field indicates the authority level (required authority level) required to give an instruction to start the dispensing process. In the following, for convenience, the condition whose condition ID is "Cn" will be referred to as "condition Cn".

In the authority identification table D7 shown in FIG. 11, the conditions C1 to C6 are the same as the exception conditions EC1 to EC6 in the exception condition table D6 shown in FIG. 10, and thus the description thereof will be omitted here. The conditions registered in the authorized person identification table D7 may be different from the exception conditions registered in the exception condition table D6.

In the authority identification table D7 shown in FIG. 11, conditions C7 and C8 are set in addition to the conditions C1 to C6. Of these, condition C7 is a condition that "drug D is included in the target prescription data". Here, the “drug D” is, for example, a drug that requires a certain degree of care in handling, although the degree of caution is lower than that of the drugs A and B. Further, the condition C8 is a case other than the conditions C1 to C7.

In the authority identification table D7 shown in FIG. 11, "3 to 6" is associated with the condition C7 as the required authority level. This indicates that, when the condition C7 is satisfied, the user of the authority level "3" to "6" is set as the authority person (the person who can give the start instruction of the dispensing process). Further, the conditions C2 to C5 are associated with "4 to 6" as the required authority level. 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.

Further, the conditions C1 and C6 are associated with "5 to 6" as the required authority level. This indicates that if the condition C1 or C6 is satisfied, the user of the authority level "5" to "6" is set as the authority person. 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, the condition C8 is associated with "2 to 6" as the required authority level. This indicates that if none of the conditions C1 to C7 is satisfied, the user of the authority level "2" to "6" is set as the authority person.

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, since the condition C1 is associated with the required authority level "5 to 6", the exception condition EC1 is substantially associated with the required authority level "5 to 6". Will be there. When the exception condition EC1 is satisfied, even if the automatic start function is set to ON, the automatic start function is exceptionally restricted, and the dispensing process is performed after waiting for a start instruction by a predetermined authorized person. It will be started, but in this case, users with authority levels "5" to "6" will be set as authorized persons.

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

[3-2. Functional blocks other than the data storage unit] As shown in FIG. 4, the dispensing control system 1 has an input screen display control unit 103, a prescription data acquisition unit 104, a determination unit 107, a target prescription data determination unit 108, and a immediately preceding prescription data determination unit 109. , The start control unit 110, the authorized person setting unit 113, the start instruction reception unit 114, and the execution history registration unit 115. These functional blocks are mainly realized by the control unit 11. That is, when the control unit 11 executes the process according to the program, the control unit 11 functions as these functional blocks.

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. The user of the dispensing control system 1 receives a prescription issued on paper from the patient, and while referring to the prescription, 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 the target prescription data to be the target of the dispensing process. As shown in FIG. 4, the prescription data acquisition unit 104 includes the first prescription data acquisition unit 105 and the second prescription data acquisition unit 106.

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

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

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

For example, the determination unit 107 determines whether or not to limit 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 that the automatic start of the dispensing process is restricted. On the other hand, when the automatic start function flag is "1", in principle, the determination unit 107 determines that the automatic start of the dispensing process is not restricted.

Further, for example, the determination unit 107 determines whether or not to limit the automatic start of the dispensing process based on the determination result of the target prescription data determination unit 108 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 relates to the condition regarding the prescription data for which the automatic start of the dispensing process needs to be restricted, or the prescription data for which the automatic start of the dispensing process does not need to be restricted. The conditions are set, and the target prescription data determination unit 108 determines whether or not the target prescription data satisfies the conditions.

For example, the target prescription data determination unit 108 determines whether or not the target prescription data satisfies any 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 of the exception conditions EC1 to EC5, the determination unit 107 determines that the dispensing process is performed. Judge that automatic start is restricted.

Further, for example, the determination unit 107 determines whether or not to limit the automatic start of the dispensing process based on the determination result of the immediately preceding prescription data determination unit 109 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 relates to the condition regarding the prescription data for which the automatic start of the dispensing process needs to be restricted, or the prescription data for which the automatic start of the dispensing process does not need to be restricted. The conditions are set, and the immediately preceding prescription data determination unit 109 determines whether or not the immediately preceding prescription data satisfies the conditions.

For example, the immediately preceding prescription data determination unit 109 determines whether or not the immediately preceding prescription data satisfies the exception condition EC6 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 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 the dispensing process. to decide.

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

When the determination unit 107 determines that the automatic start of the dispensing process is not restricted, the first start control unit 111 automatically causes the dispensing device 20 to start the dispensing process of the target prescription data. That is, when the target prescription data is acquired, the first start control unit 111 transmits the dispensing process of the target prescription data to the dispensing device 20 without waiting for receiving the start instruction of the dispensing process from the predetermined authority. Let's get started.

On the other hand, when the determination unit 107 determines that the automatic start of the dispensing process is restricted, the second start control unit 112 receives the dispensing process start instruction from a predetermined authority, and the dispensing process of the target prescription data. Is started in the dispensing device 20. That is, when the target prescription data is acquired, the second start control unit 112 does not immediately start the dispensing process to the dispensing device 20, and whether or not the dispensing process start instruction is received from a predetermined authority. This is monitored, and after waiting for the instruction to start the dispensing process to be received from the predetermined authorized person, the dispensing process is started by the dispensing device 20. In this case, the "authorized person" is set by the authorized person setting unit 113 described later in accordance with the target prescription data or the immediately preceding prescription data.

The authority setting unit 113 sets an authority (that is, a person who can give an instruction to start the dispensing process) based on the target prescription data. For example, the authority setting unit 113 sets the authority based on the target prescription data and the authority identification data stored in the authority identification data storage unit 102. As described above, the authority-specific data storage unit 102 stores the authority-specific data in association with the conditions related to the prescription data. The authority setting unit 113 sets the authority based on the authority identification data associated with the conditions under which the target prescription data is satisfied.

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

The authority setting unit 113 may set the authority based on the prescription data (immediately preceding prescription data) that was the target of the dispensing process executed immediately before. For example, the authority setting unit 113 may set the authority based on the immediately preceding prescription data and the authority identification data stored in the authority identification data storage unit 102. As described above, the authority-specific data storage unit 102 stores the authority-specific data in association with the conditions related to the prescription data. The authority setting unit 113 may set the authority based on the authority identification data associated with the condition that the immediately preceding prescription data is satisfied.

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

Although it has been described here 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, the authorized person may be a specific user set in advance. For example, regardless of the target prescription data or the immediately preceding prescription data, the user of the authority level "5" to "6" may be predetermined as the authority person.

The start instruction reception unit 114 receives a start instruction for the dispensing process. 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 receiving an instruction to start the dispensing process. When the execution button P22 on the instruction screen G2 is pressed, the start instruction reception unit 114 determines that the start instruction for the dispensing process has been accepted.

As described above, the second start control unit 112 causes the dispensing device 20 to start the dispensing process when the authority person set by the authority setting unit 113 receives the instruction to start the dispensing process. That is, when the execution button P22 of the instruction screen G2 is pressed by the authorized person set by the authorized person setting unit 113, 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 second start control unit 112 starts the dispensing process to the dispensing device 20. I won't let you. That is, even if the execution button P22 on the instruction screen G2 is pressed by an unauthorized person, the second start control unit 112 does not cause the dispensing device 20 to start the dispensing process. In this case, an error message indicating that you do not have the authority to give the start instruction is displayed.

The start instruction reception unit 114 may not accept the start instruction of the dispensing process from an unauthorized person. For example, the execute button P22 may be pressed 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 execute button P22 may not be displayed, or the execute button P22 may be displayed in a state where it cannot be pressed (for example, in a grayed out state). You may. Alternatively, if the logged-in user is an unauthorized person, the screen transition from the list screen G1 to the instruction screen G2 or the screen transition from another screen (menu screen, etc.) to the list screen G1 is prohibited. You may try to do so.

The execution history registration unit 115 registers the execution history of the dispensing process in the data storage unit 100 (an example of a 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 authority data regarding the authority who has instructed to start the dispensing process, and the comment data input by the authority. Register in the storage unit 100. More specifically, the execution history registration unit 115 registers the execution history of the dispensing process in the 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. The functional blocks (excluding the data storage unit 100) shown in FIG. 4 are realized by the control unit 11 executing the processes shown in FIGS. 12 and 13 according to the program.

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

As shown in FIG. 12, first, the control unit 11 registers the 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 the 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 of the exception conditions is satisfied (S102).

If none of the exceptional conditions is satisfied, the control unit 11 causes the dispensing device 20 to start the dispensing process of the target prescription data (S103). For example, the control unit 11 causes the dispensing device 20 to start the dispensing process by transmitting the request data requesting the start of the dispensing process of the target prescription data to the dispensing device 20. 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 "1", respectively.

After that, the control unit 11 monitors whether or not the dispensing process is completed (S104). For example, the dispensing device 20 notifies the control unit 11 of the completion of the dispensing process, 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 execution result of the current 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 ( That is, this process is completed 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 the execution status flag of the target prescription data to “0”, respectively.

Further, even when it is determined in step S102 that any of the exception conditions is 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). This process ends. 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”, respectively.

[4-2] FIG. 13 is a flow chart 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 in which the automatic start flag and the execution status flag are "0" on the list screen G1. Here, the prescription data in which the automatic start flag and the execution status flag are "0" is the prescription data in which the dispensing process is not automatically started.

While the list screen G1 is 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 of the prescription data is selected by the user, the control unit 11 identifies an authorized person who can give an instruction to start the dispensing process of the selected prescription data (S112). Specifically, the control unit 11 refers to the authority identification table D7 and acquires the authority level (necessary authority level) necessary for instructing 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 of the conditions C1 to C7 is satisfied. If any 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 is 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 above-mentioned authority.

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

When the current user is not an authorized person, the control unit 11 displays the instruction screen G2 on the display unit 15 (S119). However, in this case, the control unit 11 does not display the execution button P22 on the instruction screen G2. 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, when the current user is an authorized person, the control unit 11 displays the instruction screen G2 on the display unit 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 is pressed by the user (S115). When the execution button P22 is pressed, the control unit 11 causes the dispensing device 20 to start the dispensing process 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 to S118 are the same as steps S103 to S105 of 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 instructor" and "authority level" fields of the execution history table D4. Further, the comment input in the comment field P21 of the instruction screen G2 is registered in the "comment" field of the execution history table D4. Further, 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, but the process of step S113 is not executed before step S114, but the execute button P22 is pressed in step S115. It may be executed when it is determined, and the process of step S119 may be omitted. If the process of step S113 in this case determines that the current user is an authorized user, the process of step S116 is executed, and if it is determined that the current user is not an authorized user, an error message to that effect is displayed. May end the process.

While the instruction screen G2 is displayed, a process of displaying the comment input by the user in the comment field P21, a process of monitoring whether or not the back button P23 is pressed, and a process of pressing the back button P23 are pressed. If this is the case, a process is also executed to display the list screen G1 on the display unit 15, but this is omitted in FIG. 13 for the sake of simplicity.

[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 a predetermined authority can provide prescription information. After confirmation, it becomes possible to select whether to start the dispensing process. That is, it becomes possible to match the method of starting the dispensing process to the user's request. As a result, it becomes possible to improve the convenience of 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 the dispensing process can be provided. It is possible to set it to ON and, exceptionally, to start the dispensing process after the predetermined authority confirms the prescription information without automatically starting the dispensing process only in a specific case.

For example, when a specific drug requiring attention is included in the target prescription data (exception condition EC1, EC2), or when the patient in the target prescription data is a specific patient requiring attention (exception condition EC3). Exceptionally, it is possible to prevent the dispensing process from starting without a start instruction by a predetermined authority. That is, it becomes possible for a predetermined authority to sufficiently confirm the patient information and the prescription contents before the dispensing process is executed.

Further, 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 upper system 2 is "warning" (exception condition). In EC5) as well, exceptionally, it is possible to prevent the dispensing process from starting unless a start instruction is given by a predetermined authority. That is, it becomes possible for a predetermined authority to reconfirm that there is no problem in the prescription information and then execute the dispensing process.

Further, when the immediately preceding prescription data contains a drug that requires special attention so that the drug does not remain in the part of the dispensing device 20 (drug input section, etc.) that comes into contact with the drug during the dispensing process (exception condition). In EC6) as well, exceptionally, it is possible to prevent the dispensing process from starting unless a start instruction is given by a predetermined authority. That is, it is possible for a predetermined authorized person to sufficiently confirm that no drug remains in the drug input section or the like before the dispensing process is executed.

There are laws such as the Pharmacists Act regarding dispensing operations, but as a result of the functions described above being provided in the dispensing control system 1, users are considering legality and efficiency of dispensing operations through automation. The method of using the dispensing control system 1 is determined, and the dispensing control system 1 can be used according to the method of use.

In addition, since the dispensing control system 1 generates "medicines" that are taken by humans, which are directly related to life, there are cases where sufficient safety should be ensured by intervening humans, and dispensing work is automated. The boundary with the case of improving efficiency becomes very important. In this regard, as a result of the dispensing control system 1 being provided with the functions described above, as a general rule, a person intervenes to ensure sufficient safety while improving efficiency by automatically starting the dispensing process. Then, in a specific case where the dispensing process should be executed, it is possible to ensure that the dispensing process is executed through a person.

Further, according to the dispensing control system 1, by providing the authority identification table D7 and the authority setting unit 113, it is possible to set an appropriate authority 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 experienced pharmacist can give an instruction to start the dispensing process, and in a normal case (condition C8), the pharmacist is particularly experienced. It becomes possible to give an instruction to start a dispensing process even if the pharmacist is not a good pharmacist.

As mentioned above, in the dispensing control system 1, in order to generate "medicines" that are taken by humans, which are directly related to life, there are cases where sufficient safety should be ensured by intervening humans and dispensing work. The boundary with the case of automation and efficiency is very important. In this regard, as a result of the dispensing control system 1 being provided with the functions described above, when the dispensing process should be performed with the intervention of a person in order to sufficiently ensure safety, the situation at that time (target prescription data). Alternatively, it becomes possible to ensure that the dispensing process is performed through an appropriate person who matches the previous prescription data).

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

[6-1. Modification 1] Regarding the prescription data in 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, the list screen G1 displays the prescription data. Information on that fact and the exception condition may be displayed. By doing so, it may be easier for the user to understand that the automatic start of the dispensing process is restricted (suppressed) and the reason.

[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 modified example. In FIG. 14, 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 identify which dispensing device 20 the dispensing process was executed on. May be good.

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

The exception condition EC7 shown in FIG. 15 is a condition that "the predicted dispensing time of the target prescription data is 20 minutes or more". In this case, when the target prescription data determination unit 108 executes the dispensing process of the target prescription data by the first dispensing device 20A (that is, the dispensing device that performs the dispensing process fully automatically) based on the prescription content of the target prescription data. The time required for this 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 exception condition EC7 is satisfied, the determination unit 107 determines that the automatic start of the dispensing process of the target prescription data is restricted.

For prescription data that would take a lot of time when the first dispensing device 20A executes the dispensing process, it is faster for the user to perform the dispensing process with the second dispensing device 20B. It can be and can be efficient. In this regard, according to the above, if it takes a lot of time to execute the dispensing process on the first dispensing device 20A, even if the automatic start function is set to ON, Exceptionally, the first dispensing device 20A is prevented from executing the dispensing process. As a result, the user can perform the dispensing process with the second dispensing device 20B, and the efficiency of the dispensing business can be improved.

[6-4. Modification 3] The exception condition table D6 shown in FIGS. 10 and 15 is data showing conditions when the automatic start of the dispensing process is exceptionally restricted even when the automatic start function is set to ON. However, even when the automatic start function is set to OFF, an exception condition table showing the conditions when the automatic start of the dispensing process is not exceptionally restricted 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 exception condition table D8 may be provided together with the exception condition table D6, or may be provided in place of the exception condition table D6. Further, 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 the date and time determination unit 116 is included. The date / time determination unit 116 determines whether or not the current condition satisfies the conditions set in the setting data stored in the setting data storage unit 101. 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 the dispensing process are set. Further, in the exception condition table D8, a condition regarding a day or time when it is necessary to restrict the automatic start of the dispensing process or a condition regarding a day or time when it is not necessary to restrict the automatic start of the dispensing process is set. In the exception condition table D8 shown in FIG. 16, exception conditions EC11, EC12, and EC13 are set. Exception conditions EC11 and EC12 correspond to conditions relating to prescription data that do not need to limit the automatic start of dispensing processing. The exception condition EC13 corresponds to a condition relating to a day (day of the week) in which the automatic start of the dispensing process should not be restricted.

The exception 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 is the case where the target prescription data is the same as the prescription data previously prescribed to the same patient. is there. In addition, for example, when the medical institution, clinical department, doctor, drug, usage, dose, number of days, and quantity are all the same, the prescription contents may be regarded as the same, and among these items, If certain specific items of the above are the same, the prescription contents may be regarded as the same.

When such an exception condition EC11 is set, for example, the target prescription data determination unit 108 inputs (generates) the target prescription data by the DO prescription function by referring to the DO prescription flag of the target prescription data. It is determined whether or not it is. 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 determines whether or not the same prescription data as the target prescription data exists in the prescription data previously prescribed to the same patient by referring to the prescription data table D3. You may do so. Then, when the above-mentioned prescription data exists, the target prescription data determination unit 108 may determine that the exception condition EC11 is satisfied.

When prescription data previously prescribed to a patient is stored in a public database constructed by, for example, a country or a specific region and shared by the medical / dispensing industry, the target prescription data determination unit 108 uses the public database. By accessing the above, it may be determined whether or not the same prescription data as the target prescription data exists in the prescription data previously prescribed to the same patient. Then, when the above-mentioned prescription data exists, the target prescription data determination unit 108 may determine that the exception condition EC11 is satisfied.

When it is determined that the exception condition EC11 is satisfied, even if the automatic start function is turned off, the determination unit 107 exceptionally determines that the automatic start of the dispensing process of the target prescription data is not restricted. 1 The start control unit 111 automatically causes the dispensing device 20 to start the dispensing process of the target prescription data. In general, it is considered that there is little need to reconfirm the same prescription data as the prescription data previously prescribed to the same patient, but by setting the exception condition EC11 as described above, it is possible to do so. In exceptional cases, the dispensing process can be started automatically.

The exception condition EC11 may be a condition that "the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient". Here, when the target prescription data is similar to the prescription data previously prescribed to the same patient, the target prescription data is not the same as the prescription data previously prescribed to the same patient, but is regarded as the same. However, there is no problem.

Further, instead of the exception condition EC11, an exception condition may be set such that "the dispensing process of the same or similar prescription data as 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 can perform dispensing processing of the same or similar prescription data as the target prescription data by referring to the prescription data table D3 (and the execution history table D4). It may be determined whether or not it has been executed by the dispensing device 20 in the past. Then, when the dispensing process of the same or similar prescription data as 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 process is not restricted. It may be.

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

Further, instead of the exception condition EC11, "the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient, and the dispensing process of the same or similar prescription data as the target prescription data is a dispensing device in the past. An exception condition such as "has been executed by 20" may be set. Here, the case where the prescription data is the same is the case where the patients are the same and the prescription contents are the same. In addition, for example, when the medical institution, clinical department, doctor, drug, usage, dose, number of days, and quantity are all the same, the prescription contents may be regarded as the same, and among these items, If certain specific items of the above are the same, the prescription contents may be regarded as the same. Further, the case where the prescription data is similar is a case where there is no problem even if the patients are the same and the prescription contents are not the same, even if 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 above-mentioned public database so that the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient. It may be determined whether or not. Alternatively, by referring to the prescription data table D3 (and the execution history table D4), the target prescription data determination unit 108 has executed the dispensing process of the same or similar prescription data as the target prescription data by the dispensing device 20 in the past. It may be determined whether or not there is.

Then, the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient, and the dispensing process of the same or similar prescription data as the target prescription data has been executed by the dispensing device 20 in the past. In some cases, the determination unit 107 may exceptionally determine that the automatic start of the dispensing process is not restricted.

On the other hand, even if the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient, the dispensing process of the same or similar prescription data as the target prescription data was executed by the dispensing device 20 in the past. If this is not the case, the determination unit 107 may determine that the automatic start of the dispensing process is restricted. That is, even if the target prescription data is the same as or similar to the prescription data previously prescribed to the same patient, it is not dispensed at one's own hospital or dispensing pharmacy (at another hospital or dispensing pharmacy). (If it has been dispensed), the dispensing process may not be started automatically, but may be started after waiting for a start instruction from a predetermined authority.

Further, the exception condition EC12 is a condition that "the target prescription data is provided by the higher system 2". When such an exception 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 so that the target prescription data is the higher system 2 Determine if it was provided by. Then, when the target prescription data is provided by the higher-level system 2, the target prescription data determination unit 108 determines that the exception condition EC12 is satisfied.

When it is determined that the exception condition EC12 is satisfied, even if the automatic start function is turned off, the determination unit 107 exceptionally determines that the automatic start of the dispensing process of the target prescription data is not restricted, and the first The start control unit 111 automatically causes the dispensing device 20 to start the dispensing process of the target prescription data. Since the prescription data provided by the upper system 2 is also inspected on the upper system 2 side, it is considered that there is little need to confirm it again. Therefore, by setting the exception condition EC12 as described above, In such cases, exceptionally, the dispensing process can be started automatically.

In addition, the exception 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 by using, for example, a timekeeping function provided in the computer. If today is Monday, it is determined that the exception condition EC13 is satisfied.

The determination unit 107 determines whether or not to limit the automatic start of the dispensing process based on the determination result of the date and time determination unit 116. For example, when the date and time determination unit 116 determines that the exception condition EC13 is satisfied, even if the automatic start function is turned off, the determination unit 107 exceptionally restricts the automatic start of the dispensing process of the target prescription data. The first start control unit 111 automatically causes the dispensing device 20 to start the dispensing process of the target prescription data. In general, it is expected that the number of patients who visit the hospital on Monday will increase and the number of dispensing treatments will increase. By setting the above-mentioned exception condition EC13, in such cases, exceptional cases will occur. , It becomes possible to start the dispensing process automatically.

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

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

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

Then, if any of the exception conditions EC11 to EC13 is satisfied, the control unit 11 causes the dispensing device 20 to start the dispensing process of the target prescription data (S121). After that, the control unit 11 monitors whether or not 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 of FIG.

On the other hand, if none of the exception conditions EC11 to EC13 is 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 the execution status flag of the target prescription data to “0”, respectively.

According to such a modification 3, by providing the exception condition table D8, in principle, the automatic start function of the dispensing process is set to OFF, and the dispensing process is exceptionally automatically performed only in a specific case. It will be possible to start with.

For example, only when the target prescription data is specific prescription data (exception conditions EC11 and EC12), the dispensing process can be automatically started as an exception. Specifically, the prescription information is renewed, such as 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 by the host system 2. Exceptionally, when the need for confirmation is low (in other words, when safety is sufficiently ensured without confirming the prescription information again), the dispensing process can be started automatically. As a result, it becomes possible to improve the efficiency of dispensing operations.

In addition, even when the number of dispensing treatments is expected to increase (exception condition EC13), such as Monday when the number of patients who visit the hospital increases, the dispensing treatment should be started automatically. As a result, it becomes possible to improve the efficiency of dispensing operations.

As mentioned above, in the dispensing control system 1, in order to generate "medicines" that are taken by humans, which are directly related to life, there are cases where sufficient safety should be ensured by intervening humans and dispensing work. The boundary with the case of automation and efficiency is very important. In this regard, according to the third modification, as a general rule, there is little need for a person to intervene in the dispensing process while ensuring sufficient safety by initiating the dispensing process through a person. Only in this case, it is possible to improve efficiency by automatically starting the dispensing process.

[6-5. Modification 4] The dispensing control system 1 (control device 10) is an execution history output control unit that displays the execution history of the dispensing process registered in the execution history table D4 on the display unit 15 or prints it on the printing unit 16. May be provided.

For example, the user may specify the search condition, and the execution history output control unit may display or print a list of execution histories satisfying the search condition. Alternatively, the execution history output control unit may display or print the aggregate of the execution history that satisfies the search condition. As the search condition, for example, a period, a patient, a start instructor, an authority level, whether or not the start is automatic, and the like may be specified.

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

In addition to the execution history of the dispensing process, the history of various operations performed by the dispensing control system 1 may be registered in the data storage unit 100. Further, the operation history output control unit may be provided so that the operation history can be displayed on the display unit 15 or printed by the printing unit.

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

In a system such as the dispensing control system 1, even though a user is used while logged in, the user gives an instruction to start the dispensing process on the system. In reality, there is a risk that another user will give an instruction to start the dispensing process. In this regard, if the user is forcibly logged off each time the dispensing process of one prescription data is executed, it is necessary to log in every time to instruct the start of the dispensing process. It becomes difficult to perform such operations.

In this modification, the log-off may be performed immediately after the completion of the dispensing process, or the log-off may be performed after a predetermined time has elapsed after the completion of the dispensing process. For example, by configuring the configuration so that the log-off is performed when the operation is not performed for a predetermined time (for example, 20 seconds) after the completion of the dispensing process, if the operation is performed within the predetermined time after the completion of the dispensing process, the following It may be possible to continuously execute the dispensing process of. Further, the presence / absence of forced log-off, the method of forced log-off, and the predetermined time may be arbitrarily set by a user having a predetermined authority (for example, a user having the authority level "6").

1 Dispensing control system, 2 Upper 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 1st dispensing device, 20B 2nd dispensing device, 100 data storage unit, 101 setting data storage unit, 102 authorized person specific data storage unit, 103 input screen display control unit, 104 prescription data acquisition unit, 105 1st prescription data acquisition unit, 106 2nd prescription Data acquisition unit, 107 Judgment unit, 108 Target prescription data judgment unit, 109 Immediately before prescription data judgment unit, 110 Start control unit, 111 1st start control unit, 1121 2nd start control unit, 113 Authorized person setting unit, 114 Start instruction Reception department, 115 execution history registration department, 116 date and time judgment unit, G1 list screen, G2 instruction screen, P21 comment field, 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 exception condition table, D7 authorized person identification table, D8 exception condition table.

Claims (17)

In a dispensing control system that allows a dispensing execution means to automatically initiate a dispensing process.
Prescription data acquisition means for acquiring target prescription data to be the target of the dispensing process, and
A target prescription data determination means for determining whether or not the target prescription data satisfies the condition of whether or not to limit the automatic start of the dispensing process, and
Based on the determination result of the target prescription data determination means, the determination means for determining whether or not to limit the automatic start of the dispensing process, and the determination means.
When it is determined that the automatic start of the dispensing process is not restricted, the first start control means for automatically causing the dispensing execution means to start the dispensing process of the target prescription data, and
When it is determined that the automatic start of the dispensing process is restricted, the second start of causing the dispensing executing means to start the dispensing process of the target prescription data when the instruction to start the dispensing process is received from a predetermined authority. Control means and
Only including,
The condition includes a condition as to whether the target prescription data is the prescription data input by the user of the dispensing control system via the input screen or the prescription data transmitted from another system.
The target prescription data determination means determines whether the target prescription data is prescription data input by the user via the input screen or prescription data transmitted from the other system. Including means,
Dispensing control system comprising a call. In the dispensing control system according to claim 1 ,
The conditions include conditions relating to whether or not the subject prescription data includes a particular drug as a drug to be provided to a patient.
Dispensing control system characterized by that. In the dispensing control system according to claim 1 or 2 .
The conditions include conditions relating to patient data included in the subject prescription data.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 3 .
In front SL other systems is performed audit of prescription data,
The condition includes a condition as to whether or not the result of the audit on the target prescription data is a predetermined result.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 4 .
The condition includes a condition of whether or not the target prescription data is the same or similar prescription data as the prescription data that has been previously prescribed to the same patient.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 5 ,
The condition includes a condition as to whether or not the dispensing process of the same or similar prescription data as the target prescription data has been performed by the dispensing execution means in the past.
Dispensing control system characterized by that. In the dispensing control system according to claim 6 , which cites claim 5 .
The determination means is that even if the target prescription data is the same or similar prescription data as the prescription data that has been prescribed to the same patient in the past, the same or similar prescription data as the target prescription data. If the dispensing process has never been performed by the dispensing executing means in the past, it is determined that the automatic start of the dispensing process is restricted.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 7 .
The dispensing control system is used when a person who is currently logged in to the dispensing control system has previously executed a dispensing process of prescription data that is the same as or similar to the target prescription data by the dispensing execution means. look including a determination means for determining whether or not the same as the login to have the person in,
The determination means determines whether or not to limit the automatic start of the dispensing process based on the target prescription data determination means and the determination results of the determination means.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 8 .
The conditions include conditions relating to the time required to perform the dispensing process predicted based on the subject prescription data.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 9 .
Before SL dispensing control system, the prescription data has been the subject of the most recently executed the dispensing process comprises just prior prescription data determining means for determining whether a predetermined condition is satisfied,
The determination means determines whether or not to limit the automatic start of the dispensing process based on the determination results of the target prescription data determination means and the immediately preceding prescription data determination means.
Dispensing control system characterized by that. In dispensing control system according to any one of claims 1 to 1 0,
The dispensing control system, currently, the dispensing process conditions for a certain day or time of the need to limit the automatic start of, or, to satisfy the conditions on the need no day or time to limit the automatic start of the dispensing process Including a date and time determination means for determining whether or not
The determination means determines whether or not to limit the automatic start of the dispensing process based on the determination results of the target prescription data determination means and the date and time determination means.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 1 to 11.
Including the authority setting means for setting the authority based on the target prescription data,
Dispensing control system characterized by that. In dispensing control system of claim 1 2,
Including an authority-specific data storage means for storing authority-specific data for identifying an authority who can instruct the start of the dispensing process of the prescription data in association with conditions relating to the prescription data.
When the target prescription data to be the target of the dispensing process satisfies the condition, the authority setting means sets the authority based on the authority identification data associated with the condition.
Dispensing control system characterized by that. In dispensing control system according to claim 1 2 or 1 3,
The authority setting means includes means for setting the authority based on the prescription data that was the target of the dispensing process executed immediately before.
Dispensing control system characterized by that. In dispensing control system according to any one of claims 1 to 1 4,
Registration that associates the target prescription data that is the target of the dispensing process, the authority data regarding the authority who has instructed to start the dispensing process, and the comment data input by the authority, and registers them in a predetermined storage means. Including means,
Dispensing control system characterized by that. In dispensing control system according to any one of claims 1 to 1 5,
The dispensing execution means is
(A) Automatic dispensing / packaging device or system for powdered medicine,
(B) Automatic tablet dispensing / packaging device or system,
(C) Automatic dispensing / dispensing device or system of liquid medicine,
(D) Automatic mixed injection device or system of anticancer drug,
(E) Dispensing inspection device or system (f) A mode in which a plurality of devices or systems of any one of these devices are connected, or
(G) A mode in which a plurality of types of devices or systems among these devices are connected.
Dispensing control system characterized by being one of the following. Prescription data acquisition step to acquire the target prescription data to be the target of dispensing processing,
A target prescription data determination step for determining whether or not the target prescription data satisfies the condition of whether or not to limit the automatic start of the dispensing process, and
Based on the determination result in the target prescription data determination step, a determination step for determining whether or not to limit the automatic start of the dispensing process, and a determination step.
When it is determined that the automatic start of the dispensing process is not restricted, the first start control step of automatically causing the dispensing executing means to start the dispensing process of the target prescription data, and
When it is determined that the automatic start of the dispensing process is restricted, the second start of causing the dispensing executing means to start the dispensing process of the target prescription data when the instruction to start the dispensing process is received from a predetermined authority. Control steps and
It is a dispensing control method including
The condition is either the prescription data in which the target prescription data is input via the input screen by the user of the dispensing control system that executes the dispensing control method, or the prescription data transmitted from another system. Including the condition of
The target prescription data determination step determines whether the target prescription data is prescription data input by the user via the input screen or prescription data transmitted from the other system. Including steps,
Dispensing control wherein a call.

Images