JP2017196260A - Medicine preparation control system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a medicine preparation control system and method capable of improving convenience for a user.SOLUTION: A prescription data acquisition part (104) acquires object prescription data which is an object of medicine preparation processing. A setting data storage part (101) stores set data which is set to determine whether or not automatic start of the medicine preparation processing is restricted. A determination part (107) determines whether or not to restrict the automatic start of the medicine preparation processing on the basis of the set data. A first start control part (111) automatically causes a medicine preparation execution part to start the medicine preparation processing of the object prescription data when it is determined that, the automatic start of the medicine preparation processing is not restricted. A second start control part (112) causes the medicine preparation execution part to start the medicine preparation processing of the object prescription data, when receiving a start instruction of the medicine preparation processing from a prescribed person who has authority, when it is determined that the automatic start of the medicine preparation processing is restricted.SELECTED DRAWING: Figure 4

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, a dispensing device is known in which a robot executes a dispensing process fully automatically based on prescription data.

JP2013-052250A

  Among the dispensing apparatuses as described above, there is a dispensing apparatus that can automatically start the dispensing process when prescription data is input or received. Some users of such a dispensing device want to automatically start the dispensing process, and some users want to start the dispensing process after confirming prescription information. Some users. In certain cases, there are also users who want to start the dispensing process after a predetermined authority confirms the prescription information, and to automatically start the dispensing process in other cases. In this regard, conventionally, there are cases where the method of starting the dispensing process does not meet the user's request and is not sufficient in terms of convenience for the user.

  This invention is made | formed in view of the said subject, The objective is to provide the dispensing control system and the dispensing control method which can improve a user's convenience.

  In order to solve the above-described problems, a dispensing control system according to the present invention acquires target prescription data to be a target of the dispensing process in a dispensing control system capable of automatically starting a dispensing process by a dispensing execution unit. Prescribing data acquisition means, setting data storage means for storing setting data set for determining whether or not to restrict automatic start of the dispensing process, and automatic dispensing process based on the setting data A determination means for determining whether or not to limit the start, and when it is determined not to restrict the automatic start of the dispensing process, the dispensing execution means for automatically starting the dispensing process of the target prescription data. 1 start control means, when it is determined that the automatic start of the dispensing process is restricted, and when the start instruction of the dispensing process is received from a predetermined authority, the target prescription data And a second start control means for starting the dispensing process of data to said dispensing execution unit.

  Further, the dispensing control method according to the present invention includes a prescription data acquisition step for acquiring target prescription data to be subjected to a dispensing process, and a setting set to determine whether or not to restrict the automatic start of the dispensing process A determination step for determining whether or not to limit the automatic start of the dispensing process based on the data; and if it is determined not to limit the automatic start of the dispensing process, the dispensing of the target prescription data is automatically performed A first start control step for causing the dispensing execution means to start processing, and when it is determined to limit the automatic start of the dispensing process, and when an instruction to start the dispensing process is received from a predetermined authority, the target prescription data A second start control step for causing the dispensing execution means to start the dispensing process.

  Moreover, in one aspect of the present invention, the setting data includes a condition relating to prescription data that needs to limit the automatic start of the dispensing process, or a condition related to prescription data that does not need to restrict the automatic start of the dispensing process. May be set. The dispensing control system may include target prescription data determination means for determining whether the target prescription data satisfies the condition. The determination means may determine whether or not to restrict the automatic start of the dispensing process based on the determination result of the target prescription data determination means.

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

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

  Moreover, in one aspect of the present invention, the prescription data acquisition unit may acquire prescription data input by another system as the target prescription data. In the other system, the prescription data may be audited. The condition may include a condition as to whether or not the result of the audit for the target prescription data is a predetermined result.

  Moreover, in one aspect of the present invention, a display control unit that displays an input screen for receiving input of prescription data on the display unit may be included. The prescription data acquisition means acquires first prescription data acquisition means for acquiring prescription data input via the input screen as the target prescription data, and acquires prescription data input by another system as the target prescription data. And a second prescription data acquisition means. The condition may include a condition indicating whether the target prescription data is prescription data input via the input screen or prescription data input by the other system.

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

  In the aspect of the invention, the condition may include a condition as to whether or not a dispensing process of prescription data that is the same as or similar to the target prescription data has been executed by the dispensing execution unit in the past. Good.

  Moreover, in one aspect of the present invention, the determination unit may determine whether the target prescription data is the same or similar prescription data to prescription data that has been previously prescribed to the same patient. When the dispensing process of the prescription data that is the same as or similar to the data has not been executed by the dispensing execution unit in the past, it may be determined that the automatic start of the dispensing process is restricted.

  In one aspect of the present invention, the condition may be that a person who is currently logged in to the dispensing control system executes dispensing processing of prescription data that is the same as or similar to the target prescription data by the dispensing execution means in the past. May include a condition as to whether or not it is the same as the person who has logged into the dispensing control system.

  Moreover, in one aspect of the present invention, the condition may include a condition relating to a time required to execute the dispensing process predicted based on the target prescription data.

  Moreover, in one aspect of the present invention, the setting data includes a condition relating to prescription data that needs to limit the automatic start of the dispensing process, or a condition related to prescription data that does not need to restrict the automatic start of the dispensing process. May be set. The dispensing control system may include immediately preceding prescription data determination means for determining whether or not the prescription data that was the target of the dispensing process executed immediately before satisfies the condition. The determination means may determine whether or not to restrict the automatic start of the dispensing process based on the determination result of the immediately preceding prescription data determination means.

  Moreover, in one aspect of the present invention, the setting data includes a condition relating to a day or time that needs to be limited to the automatic start of the dispensing process, or a date or time that does not need to limit the automatic start of the dispensing process. The condition regarding may be set. The dispensing control system may include date and time determination means for determining whether or not the current condition satisfies the condition. The determination unit may determine whether to restrict the automatic start of the dispensing process based on the determination result of the date / time determination unit.

  Moreover, in 1 aspect of this invention, you may make it include the authorized person setting means to set the authorized person based on the said object prescription data.

  Moreover, in one aspect of the present invention, an authorized person that stores authorized person specifying data for specifying an authorized person who can instruct the start of the dispensing process of the prescribed data in association with the conditions related to the prescribed data. Specific data storage means may be included. The authorized person setting means sets the authorized person based on the authorized person specifying data associated with the condition when the target prescription data that is the target of the dispensing process satisfies the condition. Also good.

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

  Moreover, in one aspect of the present invention, the target prescription data that is the target of the dispensing process, the authority data related to the authority who issued the instruction to start the dispensing process, and the comment data input by the authority are associated with each other. Registration means for registering in a predetermined storage means may be included.

  In one aspect of the present invention, the dispensing execution means includes (a) an automatic dispensing / packaging device or system for powder, (b) an automatic dispensing / packaging device or system for tablets, and (c) an automatic liquid medicine. Dispensing / dispensing device or system, (d) automatic anti-cancer drug injection device or system, (e) dispensing inspection device or system, (f) any one of these devices or systems connected Aspect or (g) Any of the aspects in which a plurality of types of apparatuses or systems among these apparatuses are connected may be used.

  According to the present invention, it is possible to set whether to restrict the automatic start of the dispensing process, and as a result, it is possible to improve the convenience for 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 | indication 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 a prescription data table. It is a figure which shows an example of an execution history table. It is a figure which shows an example of an automatic start function flag. It is a figure which shows an example of an exception condition table. It is a figure which shows an example of an authorized person specific table. It is a flowchart which shows an example of the process performed with a dispensing control system. It is a flowchart which shows another example of the process performed with 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 an exception condition table. It is a figure which shows another example of an 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 flowchart which shows an example of the process performed with 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 denoted by the same reference numerals, and redundant 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 this specification is Both “preparation” in the narrow sense (ie “preparation” distinguished from “preparation”) and “preparation” are included.

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

  As shown in FIG. 1, the dispensing control system 1 includes a control device 10, a database 17, and a dispensing device 20, and performs a control for causing the dispensing device 20 to execute a dispensing process.

  The control device 10 is realized by one or a plurality of 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, an information storage medium such as a main storage (such as a RAM) and an auxiliary storage (such as a hard disk drive or a solid state drive), and stores a program executed by the control unit 11. The storage unit 12 also operates as a work memory for the control unit 11. The communication unit 13 is for data communication with other devices via a communication network.

  For example, 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. 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 operation, and is, for example, a keyboard, a mouse, a touch pad, or a touch panel. 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 performs printing in accordance with an instruction from the control unit 11 and is, for example, a printer device.

  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 unit) is a device that performs dispensing processing. For example, the dispensing processing can be performed fully automatically based on prescription data without requiring a human operation (work). Device. Dispensing device 20 may be called a “dispensing system”.

  Dispensing treatment is, for example, at least one of dispensing (separation) of powder (dispensing), dispensing / separation of tablets, dispensing / dispensing of liquid medicine, mixed injection of anticancer drugs, or inspection of various medicines dispensed. Including. 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 liquids, an automatic mixture dispensing device for anticancer agents, or a dispensing inspection. Device. Alternatively, the dispensing device 20 may be a device in which a plurality of any one of these devices are connected. Alternatively, the dispensing device 20 may be a device to which a plurality of types of devices among these devices are connected.

  For example, the dispensing device 20 includes a single-arm or double-arm robot, and is a dispensing device in which a dispensing process is executed by the robot. More specifically, for example, the automatic dispensing / dispensing of powder such that the robot performs weighing and packaging of the powder using the powder stored for each type in a plurality of drug containers installed in the housing of the apparatus. The packaging device corresponds to an example of the dispensing device 20. In addition, for example, an automatic anti-cancer agent co-infusion apparatus in which a robot mixes a plurality of medicines installed in a housing of the apparatus and dispenses the anti-cancer agent corresponds to an example of the dispensing apparatus 20.

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

  In FIG. 1, the control device 10 and the dispensing device 20 are shown as separate devices, but the control device 10 and the dispensing device 20 may be configured integrally. That is, the control device 10 may have a dispensing execution function of the dispensing device 20. In other words, the dispensing device 20 may have the function of the control device 10.

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

  The dispensing control system 1 can also input prescription data. That is, in the dispensing control system 1, an input screen (not shown) for accepting input of prescription data is displayed on the display unit 15, and the user of the dispensing control system 1 is issued with paper. It is possible to receive a prescription from a patient and input 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 a dispensing process based on the prescription data input in the host system 2, or to dispense based on the prescription data input in the dispensing control system 1. It is also possible to cause the dispensing device 20 to execute the process. The host system 2 is not essential and the host system 2 may not be installed.

  [2. Functional Overview] The dispensing control system 1 has an automatic start function that allows the dispensing device 20 to automatically start dispensing processing. In the dispensing control system 1, the user can arbitrarily turn on / off the automatic start function.

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

  In the dispensing control system 1, when the user logs in and performs a predetermined operation, for example, a list screen G1 as shown in FIG. The login to the dispensing control system 1 may be performed by the user entering a user ID and password on a login screen (not shown), or an ID card distributed by the user in advance. May be performed by causing the card reading unit to read. However, in the latter case, the control device 10 needs to include a card reading unit for reading 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 for which dispensing processing has not been executed. In the example shown in FIG. 2, prescription data A, B, and C are displayed on the list screen G1. In FIG. 2, for convenience of explanation, texts such as “prescription data A”, “prescription data B”, and “prescription data C” are displayed as information indicating each prescription data, but the actual list screen G1 For example, a part of the patient name and prescription content is displayed as information indicating each prescription data.

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

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

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

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

  In the dispensing control system 1, by providing such a function, when the user desires 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, the dispensing control system can be used as desired. On the other hand, when the user desires to automatically start the dispensing process, the user can use the dispensing control system as desired by setting the automatic start function to ON.

  Further, in the dispensing control system 1, even when the automatic start function is set to ON, the automatic start of the dispensing process can be limited exceptionally in a specific case. For this reason, in certain cases (for example, when prescription data contains drugs that require special attention), the dispensing process is started after the prescribing information is confirmed by a predetermined authority. If the user wishes to start the dispensing process automatically, the user can use this function to use the dispensing control system as desired.

  There are laws such as the Pharmacist Law regarding dispensing operations, but as a result that the dispensing control system 1 is equipped with the functions described above, the user considers legality and efficiency of dispensing operations through automation. It is possible to determine how to use the dispensing control system 1 and use the dispensing control system 1 depending on the usage.

  In addition, since the dispensing control system 1 generates a “medicine” that is directly taken by a person, the dispensing control system 1 automates the dispensing operation when safety should be sufficiently ensured by human intervention. However, as a result of the provision of the functions described above in the dispensing control system 1, in principle, the dispensing process is automatically started to improve efficiency. In a specific case where the dispensing process should be executed with human intervention to ensure sufficient safety, the dispensing process can be surely executed via a person.

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

  [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. 5 to 11 show examples 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 for uniquely identifying a user. The “name” field indicates the name of the user. The “password” field indicates the user's password. For example, the password set by the user 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 inputting his / her user ID and password on the login screen. The user may be authenticated or specified by causing the card reader to read the ID card distributed in advance by the user.

  The “authority level” field indicates the authority level of the user. The operations that the user can perform in the dispensing control system 1 are limited by the authority level set for the user. For example, values “1” to “6” are set as the authority level. “6” is the highest authority level, and “1” is the lowest authority level.

  The user with the authority level “6” can perform all operations on the dispensing control system 1. For example, editing of master data (such as the user table D1) stored in the data storage unit 100 is permitted only to users with the authority level “6”. That is, only users with authority level “6” are allowed to register new users in the user table and to set / change authority levels of each user.

  In addition, the user with the authority level “5” can perform operations other than editing the master data. For example, only a user with authority level “5” or “6” is allowed to fill the medicine container in the dispensing device 20 with the medicine.

  In addition, the user with the authority level “4” can perform operations other than editing the master data and filling the medicine. For example, a specific operation requiring special attention (herein referred to as “special operation”) is permitted only to users of authority levels “4” to “6”.

  A user with the authority level “3” can perform operations other than editing of master data, filling of medicines, and special operations. For example, a specific operation requiring attention (herein referred to as “operation requiring attention”) is permitted only to users with authority levels “3” to “6”.

  In addition, a user with the authority level “2” can perform operations other than editing master data, filling medicines, special operations, and operations requiring attention. In addition, the user with the authority level “1” can perform only limited simple operations.

  For example, the authority level “6” is set for a person (system administrator) who plays a role of managing the dispensing control system 1. Also, authority levels “2” to “5” are set for pharmacists other than the system administrator. Specifically, the authority level “2” is set for a pharmacist who has relatively little experience, and the authority level “3” is set for a pharmacist who has some experience. Also, the authority level “4” is set for a pharmacist who has a role of managing a pharmacist having the authority level “2” or “3” and has abundant experience. The pharmacist with the authority level “4” also takes the role of managing, and the authority level “5” is set for the pharmacist who has very rich experience. For example, the authority level “4” is set for a pharmacist (local manager) who plays a role of managing a pharmacist who performs business at the dispensing site at each dispensing site. The authority level “5” is set for the pharmacist (administrator) who performs the overall management over a plurality of dispensing sites, that is, the role of managing all pharmacists working in each of the plurality of dispensing sites. Is done. Note that the authority level “1” is set for a user (operator) who is a user other than the pharmacist and plays a role of performing a simple operation to assist the pharmacist, for example.

  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 “patient ID”, “name”, “sex”, “age”, “date of birth”, and “medicine history” fields. The “patient ID” field indicates identification information that uniquely identifies a patient. The “name”, “sex”, “age”, and “date of birth” fields indicate the name, sex, age, and date of birth of the patient, respectively. The “medicine history” field shows a history of medicines prescribed to the patient so far. For example, when a patient first visits a dispensing pharmacy, the patient's data is registered in the patient table D2.

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

  The “prescription data ID” field indicates identification information for uniquely identifying prescription data. The “registration date / time” field indicates the date and time when the prescription data is registered in the prescription data table D3.

  The “input system flag” field indicates a system in which prescription data is input. Specifically, the “input system” field indicates whether the prescription data is input by the dispensing control system 1 or the host system 2. For example, when the prescription data is input by the dispensing control system 1, the value “0” is registered in the “input system flag” field. On the other hand, when the prescription data is input by the host system 2, the value “1” is registered in the “input system flag” field.

  The “inspection result flag” field indicates the inspection result of the prescription data in the host system 2. In the host system 2, the prescription data is inspected before the prescription data is provided to the dispensing control system 1. For example, prescription data conditions that require attention are predetermined, and a warning is issued for prescription data that satisfies the conditions. After the reconfirmation by the pharmacist, the pharmacist reconfirms the prescription data as the warning target, and if there is no problem, it is provided to the dispensing control system 1 as it is. Provided to. For example, when the prescription data is input by the host system 2 and the inspection result in the host system 2 is “with warning”, the value “1” is registered in the “inspection result flag” field, If the inspection result in the host system 2 is not “with warning”, the value “0” is registered in the “inspection result flag” field.

  The “DO prescription flag” field indicates whether prescription data is input (generated) using the DO prescription function. The dispensing control system 1 and the host 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 is input using the DO prescription function, the value “1” is registered in the “DO prescription flag” field, otherwise the value “0” is “DO”. It is 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 prescription content (for example, medical institution, medical department, drug, usage, dose, number of days, and quantity).

  The “automatic start flag” field indicates whether 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 the dispensing process cannot be started automatically, The value “0” is registered in the “automatic start flag” field.

  The “execution status flag” field indicates the execution status of the prescription data dispensing process. For example, for the prescription data in a state before starting the dispensing process, the value “0” is registered in the “execution status flag” field. For prescription data in a state where the dispensing process is being executed, the value “1” is registered in the “execution status flag” field, and for prescription data in a state where the dispensing process has been completed, the value “2” is “ It 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 includes “execution history ID”, “target prescription data”, “automatic start flag”, “start instructor”, “authority level”, “comment”, “start date / time”, and “end”. Includes a Date / Time field.

  The “execution history ID” field indicates identification information for uniquely identifying each execution history. The “target prescription data” field indicates prescription data that is a 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 “automatic start flag” field indicates whether 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, when the dispensing process is not automatically started by the automatic start function but is executed by a start instruction given by a predetermined authority, the value “0” is “automatic start flag”. Registered in the field.

  In addition, the “start instructor” field indicates a person (start instructor) who has given an instruction to start dispensing processing, and the “authority level” field has the authority level of the start instructor at the time of instructing to start dispensing processing. Indicates. 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. The “comment” field indicates a comment input 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. When the dispensing process is automatically started by the automatic start function, the “start instructor”, “authority level”, and “comment” fields are blank. 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 a setting data storage unit 101. The setting data storage unit 101 stores setting data. The setting data is data set to determine whether or not to restrict 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 that allows the dispensing device 20 to automatically start the dispensing process. The automatic start function flag D5 indicates whether the automatic start function is set to ON or OFF. For example, the automatic start function flag takes a value “0” or “1”. The value “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. For this reason, when “0” is set in the automatic start function flag, the dispensing control system 1 does not automatically start the dispensing process in the dispensing device 20, but issues a dispensing process start instruction with a predetermined authority. The dispensing apparatus 20 is made to start the dispensing process after waiting for acceptance from the person.

  For example, the initial value of the automatic start function flag D5 is set to “0”, and the user with the authority level “6” can change the automatic start function flag D5 to “1” via a predetermined setting screen. Note that 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 dispensing processing in principle. In this regard, in the exception condition table, even when the automatic start function is set to ON, a condition (exception condition) for exceptionally restricting the automatic start of the dispensing process is registered. For example, a user with the 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 “exception condition ID” and “exception condition” fields. The “exception condition ID” field indicates identification information for uniquely identifying an exception condition registered in the exception condition table D6. The “exception condition” field indicates an 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 the sake of convenience, an exception condition whose exception condition ID is “ECn” is referred to as “exception condition ECn”.

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

  The 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 that is the target of the dispensing process. Specifically, the exceptional condition EC1 is a condition that “the drug A is included in the target prescription data”. On the other hand, the exceptional condition EC2 is a condition that “the drug B is included in the target prescription data”.

  Here, “drug A” is a drug that requires special attention in handling, for example. In addition, “drug B” is a drug that requires less care in handling, although the degree of attention is lower than that of drug A, for example. Care is required when such drug A or drug B is included in the target prescription data, but the prescription containing drug A or drug B is set by setting exceptional 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 there is a start instruction by a predetermined authority.

  The exceptional condition EC3 is a condition related to patient data included in the target prescription data. Specifically, the exceptional condition EC3 is a condition that “the patient of the target prescription data is under 10 years old”.

  In general, care is required when the patient is young, but by setting the exceptional condition EC3, the auto-start function was set to ON for prescription data where the patient is less than 10 years old. However, the dispensing process is not automatically started, and the dispensing process is not started without a start instruction from a predetermined authority. In addition, you may make it the conditions regarding a patient's sex, a medical history, etc. be set as an exceptional condition.

  The exceptional condition EC4 is a condition indicating whether the target prescription data is prescription data manually input via the input screen in the dispensing control system 1 or prescription data provided by the host system 2. Specifically, the exceptional condition EC4 is a condition that “the target prescription data is manually input”.

  Compared with the prescription data provided after being inspected by the host system 2, the prescription data manually entered through the input screen in the dispensing control system 1 may contain an error, which requires attention. However, when the exceptional condition EC4 is set, the prescription data manually input via the input screen in the dispensing control system 1 is automatically dispensed even if the automatic start function is set to ON. The dispensing process is not started unless the start instruction is given by a predetermined authority.

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

  Caution is required when the inspection result of the target prescription data in the higher system 2 is “with warning”, but by setting the exception condition EC5, the inspection result in the higher 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 there is a start instruction by a predetermined authority.

  The exceptional condition EC6 is a condition related to prescription data that was the object of the dispensing process executed immediately before. Specifically, the exceptional condition EC6 is a condition that “the drug C is included in the immediately preceding prescription data”.

  Here, the “medicine C” is a drug that requires special attention so that no drug remains in the part of the dispensing device 20 (such as the drug loading unit) that comes into contact with the drug during the dispensing process. When the drug C is included in the prescription data for the dispensing process executed immediately before, it is necessary to confirm that the drug C does not remain in the drug input unit or the like, but the exception condition EC6 is set Thus, in the case where the drug C is included in the target prescription data for the dispensing process executed immediately before, the dispensing process is not automatically started even if the automatic start function is set to ON. If there is no start instruction from the authorized person, the dispensing process will not start.

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

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

  When the automatic start function is set to OFF, an authorized person who can issue a dispensing process start instruction is specified based on the authorized person specifying table D7, and waits for a start instruction from the authorized person. Dispensing processing is executed. Similarly, even if the automatic start function is set to ON, if the automatic start function is exceptionally limited by satisfying the exception condition of the exception condition table D6, the authorized person specifying table D7 Based on the above, an authorized person who can instruct the start of the dispensing process is specified, and the dispensing process is executed after waiting for the start instruction from the authorized person.

  The authorized person identification table D7 shown in FIG. 11 includes “condition ID”, “condition”, and “necessary authority level” fields. The “condition ID” field indicates identification information for uniquely identifying a condition registered in the authorized person identification table D7. The “condition” field indicates a condition. In the “condition” field, the condition is registered in a format recognizable by the computer (control unit 11). The “necessary authority level” field indicates an authority level (necessary authority level) necessary for instructing the start of the dispensing process. Hereinafter, for the sake of convenience, a condition whose condition ID is “Cn” is referred to as “condition Cn”.

  In the authority specifying table D7 shown in FIG. 11, the conditions C1 to C6 are the same as the exception conditions EC1 to EC6 of the exception condition table D6 shown in FIG. Note that 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 authorized person identification table D7 shown in FIG. 11, conditions C7 and C8 are set in addition to the conditions C1 to C6. Among these, the condition C7 is a condition that “the drug D is included in the target prescription data”. Here, “drug D” is, for example, a drug that requires a certain degree of care in handling although it has a lower level of caution than drugs A and B. The condition C8 is a case other than the conditions C1 to C7.

  In the authorized person identification table D7 shown in FIG. 11, "3 to 6" is associated with the condition C7 as the necessary authority level. This indicates that, when the condition C7 is satisfied, the users of the authority levels “3” to “6” are set as the authorized persons (persons who can give instructions for starting the dispensing process). Further, “4 to 6” is associated with the conditions C2 to C5 as the necessary authority level. This indicates that users with authority levels “4” to “6” are set as authorities. For example, since the drug B requires more care than the drug D, the condition C2 is associated with a higher authority level than the condition C7.

  In addition, conditions 5 and 6 are associated with the conditions C1 and C6 as necessary authority levels. This indicates that, when the condition C1 or C6 is satisfied, the users of the authority levels “5” to “6” are set as the authority. Since the medicines A and C require more care than the medicine B, the required authority level higher than the condition C2 is associated with the conditions C1 and C6.

  The condition C8 is associated with “2-6” as the required authority level. This indicates that, when none of the conditions C1 to C7 is satisfied, the users of the authority levels “2” to “6” are set as the authority.

  As described above, the conditions C1 to C6 of the authorized person identification table D7 are the same as the exception conditions EC1 to EC6 of the exception condition table D6. In this respect, in the authorized person specifying table D7, “5-6” is associated with the condition C1 as the necessary authority level, so that “5-6” is substantially associated with the exceptional condition EC1 as the necessary authority level. Will be. When the exception condition EC1 is satisfied, even if the automatic start function is set to ON, the automatic start function is exceptionally limited, and the dispensing process is performed after waiting for a start instruction from a predetermined authority. In this case, users with authority levels “5” to “6” are set as authority persons.

  In the present embodiment, the exceptional condition table D6 and the authorized person identification table D7 are provided separately, but they may be provided integrally. For example, the exception condition table D6 may be omitted and only the authorized person specifying table D7 may be provided. In this case, for example, a condition in which the required authority level is associated with “4-6” or “5-6” may be regarded as an “exception condition”.

  [3-2. Functional Blocks Other than Data Storage Unit] As shown in FIG. 4, the dispensing control system 1 includes 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 previous prescription data determination unit 109. A start control unit 110, an authorized person setting unit 113, a start instruction receiving unit 114, and an execution history registration unit 115. These functional blocks are mainly realized by the control unit 11. That is, the control unit 11 functions as these functional blocks when the control unit 11 executes processing according to a program.

  The input screen display control unit 103 displays the input screen on the display unit 15. The input screen is a screen for accepting input of prescription data. The user of the dispensing control system 1 receives a prescription issued in paper from a patient, and refers to the prescription, and patient information and prescription information (medical institution, medical department, doctor, drug, usage, dose, days, quantity, etc.) ) On the input screen.

  The prescription data acquisition unit 104 acquires target prescription data that is a target of the dispensing process. As shown in FIG. 4, the prescription data acquisition unit 104 includes a first prescription data acquisition unit 105 and a second prescription data acquisition unit 106.

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

  The second prescription data acquisition unit 106 acquires prescription data input by the host system 2 (an example of another system) as target prescription data. For example, the second prescription data acquisition unit 106 receives prescription data transmitted from the host system 2 and acquires it as target prescription data. Or the 2nd prescription data acquisition part 106 accesses the memory | storage device in which the prescription data input by the high-order system 2 was preserve | saved, and acquires the said prescription data as object prescription data.

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

  For example, the determination unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the automatic start function flag D5 (an example of setting data) illustrated 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 limited. On the other hand, when the automatic start function flag is “1”, in principle, the determination unit 107 determines not to restrict the automatic start of the dispensing process.

  Further, for example, the determination unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the determination result of the target prescription data determination unit 108 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 prescription data that needs to restrict the automatic start of the dispensing process or prescription data that does not need to restrict the automatic start of the dispensing process. Conditions are set, and the target prescription data determination unit 108 determines whether the target prescription data satisfies the conditions.

  For example, the target prescription data determination unit 108 determines whether 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) illustrated 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 performs the dispensing process. Judge that the automatic start is limited.

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

  The immediately preceding prescription data determination unit 109 determines whether the prescription data (previous prescription data) that was the target of the dispensing process executed immediately before satisfies the condition 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 prescription data that needs to restrict the automatic start of the dispensing process or prescription data that does not need to restrict the automatic start of the dispensing process. Conditions are set, and the immediately preceding prescription data determination unit 109 determines whether 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) illustrated in FIG. Even if the automatic start function flag is “1”, if the immediately preceding prescription data determining unit 109 determines that the immediately preceding prescription data satisfies the exception condition EC6, the determining unit 107 restricts the automatic start of the dispensing process. to decide.

  The start control unit 110 causes the dispensing device 20 (an example of a dispensing execution unit) to start dispensing processing for 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 apparatus 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 performs the dispensing process of the target prescription data on the dispensing device 20 without waiting for receiving a start instruction for the dispensing process from a predetermined authority. Let it begin.

  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 dispenses the dispensing process of the target prescription data. Causes the dispensing device 20 to start. That is, when the target prescription data is acquired, the second start control unit 112 does not immediately cause the dispensing device 20 to start the dispensing process, but has received an instruction to start the dispensing process from a predetermined authority. This is monitored, and the dispensing apparatus 20 is made to start dispensing processing after waiting for a dispensing instruction start instruction to be received from a predetermined authority. In this case, the “authorized person” is set by the authorized person setting unit 113 described later according to the target prescription data or the immediately preceding prescription data.

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

  For example, in the authorized person identification table D7 shown in FIG. 11, the necessary authority level “5 to 6” is associated with the condition C1. For this reason, when the target prescription data satisfies the condition C1, the authority setting unit 113 sets users with authority levels “5” to “6” as authorities.

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

  For example, in the authority specifying table D7 shown in FIG. 11, the required authority level “5 to 6” is associated with the condition C6. For this reason, 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.

  Here, although it has been described that the authorized person is set according to the target prescription data or the immediately preceding prescription data by the authorized person setting unit 113, the authorized person may be a specific user set in advance. For example, users with authority levels “5” to “6” may be determined in advance as authorized persons regardless of the target prescription data or immediately preceding prescription data.

  The start instruction receiving unit 114 receives a start instruction for dispensing processing. For example, the start instruction reception unit 114 causes the display unit 15 to display the instruction screen G2 illustrated in FIG. As described above, the instruction screen G2 is a screen for receiving a dispensing process start instruction. When the execution button P22 on the instruction screen G2 is pressed, the start instruction receiving unit 114 determines that the dispensing process start instruction has been received.

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

  On the other hand, the second start control unit 112 starts the dispensing process in the dispensing device 20 when an instruction to start the dispensing process is received from a user (non-authorized person) other than the authorized person set by the authorized person setting unit 113. 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 there is no authority to issue a start instruction is displayed.

  The start instruction accepting unit 114 may not accept a dispensing process start instruction from an unauthorized person. For example, the execution button P22 may be pressed only when an authorized person set by the authorized person setting unit 113 is logged in. Specifically, when the logged-in user is an unauthorized person, the execution button P22 is not displayed, or the execution button P22 cannot be pressed (for example, grayed out). May be. Or, when the logged-in user is an unauthorized person, screen transition from the list screen G1 to the instruction screen G2 or screen transition from another screen (menu screen, etc.) to the list screen G1 is prohibited. You may make it do.

  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 unit). That is, the execution history registration unit 115 associates the target prescription data that is the target of the dispensing process, the authority data related to the authority who has instructed the start of 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 in the dispensing control system 1 will be described. 12 and 13 are flowcharts showing an example of processing executed in the dispensing control system 1. When the control unit 11 executes the processes shown in FIGS. 12 and 13 according to the program, the functional blocks (except for the data storage unit 100) shown in FIG. 4 are realized.

  [4-1] FIG. 12 shows a dispensing control system when prescription data is input in the dispensing control system 1 (input screen) or when prescription data input in the host system 2 is supplied to the dispensing control system 1. 2 is a flowchart illustrating an example of processing executed in 1. FIG.

  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 execution of 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 any exception condition is satisfied (S102).

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

  Thereafter, the control unit 11 monitors whether the dispensing process has been completed (S104). For example, the dispensing device 20 notifies the control unit 11 when the dispensing process is completed, and the control unit 11 monitors whether or not the notification is 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, the present process is terminated without causing the dispensing apparatus 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.

  Moreover, also when it is determined in step S102 that any of the exceptional 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 flowchart showing an example of processing executed by the dispensing control system 1 when an operation for displaying the list screen G1 is performed.

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

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

  When any prescription data is selected by the user, the control unit 11 specifies 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 authorized person identification table D7, and obtains the authority level (necessary authority level) necessary for instructing the start of the dispensing process for the selected prescription data. For example, in the case of the authorized person identification table D7 shown in FIG. 11, the control unit 11 determines whether any of the conditions C1 to C7 is satisfied. When any of the conditions C1 to C7 is satisfied, the control unit 11 acquires a necessary authority level associated with the condition. On the other hand, when none of the conditions C1 to C7 is satisfied, the control unit 11 acquires the necessary authority level associated with the condition C8. Then, the user having the acquired necessary authority level is specified as the authority.

  After execution of 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 authority level is the required authority level acquired in step S112. In this case, if the authority level of the current user is the necessary authority level, it is determined that the current user is an authorized person.

  If 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 instruction button G22 on the instruction screen G2 in a state where the execution button P22 cannot be pressed (for example, 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 an execution button P22 on the instruction screen G2. Then, the control unit 11 monitors whether or not the execution button P22 has been pressed by the user (S115). When the execution button P22 is pressed, the control unit 11 causes the dispensing device 20 to start dispensing processing for the prescription data selected in step S111 (S116). Thereafter, the control unit 11 monitors whether or not the dispensing process is completed (S117). 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 in FIG. However, in step S118, the user ID and authority level of the user who pressed the execution button P22 are registered in the “start instructor” and “authority level” fields of the execution history table D4. In addition, 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 execution button P22 is pressed in step S115. If it is determined, the process may be executed, and the process of step S119 may be omitted. If it is determined in step S113 that the current user is an authorized person, the process in step S116 is executed. If it is determined that the current user is not an authorized person, an error message to that effect is displayed. Then, the process may be terminated.

  While the instruction screen G2 is being displayed, a process for displaying a comment input by the user in the comment field P21, a process for monitoring whether or not the return button P23 has been pressed, and a return button P23 being pressed. In such a case, a process for displaying the list screen G1 on the display unit 15 is also executed, but is omitted in FIG.

  [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 obtain the prescription information. It becomes possible to select whether to start the dispensing process after confirmation. In other words, it is possible to match the user's request with the method of starting the dispensing process. As a result, user convenience can be improved.

  Moreover, according to the dispensing control system 1, by providing the exceptional 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 is provided. It is set to ON, and only in a specific case, the dispensing process can be started after a predetermined authority confirms the prescription information, without exceptionally starting the dispensing process automatically.

  For example, when a specific drug requiring attention is included in the target prescription data (exception conditions EC1, EC2), or when a patient of 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 from a predetermined authority. That is, it becomes possible for the prescribed authority to perform the dispensing process after sufficiently confirming the patient information and the prescription content.

  In addition, when the target prescription data is manually input via the input screen of the dispensing control system 1 (exception condition EC4), or when the inspection result in the host system 2 is “with warning” (exception condition) Also in EC5), it becomes possible to prevent the dispensing process from starting unless there is an instruction to start by a predetermined authority. That is, the dispensing process can be executed after a predetermined authority confirms again that there is no problem in the prescription information.

  Further, when the prescription data includes a drug requiring special attention so that the drug does not remain in the part of the dispensing device 20 (drug input part or the like) that comes into contact with the drug during the dispensing process (exception condition) Also in EC6), it becomes possible to prevent the dispensing process from starting unless there is an instruction to start by a predetermined authority. That is, it becomes possible for a predetermined authorized person to execute the dispensing process after sufficiently confirming that no medicine remains in the medicine input unit or the like.

  There are laws such as the Pharmacist Law regarding dispensing operations, but as a result of providing the dispensing control system 1 with the functions described above, the user is taking into account legality and efficiency in dispensing operations through automation. It is possible to determine how to use the dispensing control system 1 and to use the dispensing control system 1 in accordance with the usage.

  In addition, since the dispensing control system 1 generates a “medicine” that is directly taken by a person, the dispensing control system 1 automates the dispensing operation when safety should be sufficiently ensured by human intervention. Therefore, the boundary with efficiency improvement becomes very important. In this respect, as a result of providing the dispensing control system 1 with the above-described functions, in principle, the dispensing process is automatically started so as to improve efficiency and human intervention is required to ensure sufficient safety. Thus, in a specific case where the dispensing process is to be executed, it is possible to ensure that the dispensing process is executed through a person.

  Furthermore, according to the dispensing control system 1, it is possible to set an appropriate authorized person according to the target prescription data or the immediately preceding prescription data by including the authorized person specifying table D7 and the authorized person setting unit 113. . For example, when special attention is required (conditions C1 and C6), only an experienced pharmacist can instruct the start of the dispensing process, and when normal (condition C8), particularly experienced Even if it is not a proper pharmacist, it becomes possible to give an instruction to start the dispensing process.

  As described above, in the dispensing control system 1, a “medicine” that is taken by a person is directly related to life, so that the safety should be sufficiently ensured by human intervention, and the dispensing operation is performed. The boundary with the case of automation and efficiency improvement becomes very important. In this regard, as a result of providing the dispensing control system 1 with the functions described above, if the dispensing process should be executed with human intervention to ensure sufficient safety, the situation at that time (target prescription data) Alternatively, it is possible to perform the dispensing process through an appropriate person matching the previous prescription data.

  [6. Modification] The present invention is not limited to the embodiment 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, in the list screen G1, You may make it display the information regarding that and the said exceptional condition. By doing in this way, you may make it easy for a user to grasp | ascertain and the reason that the automatic start of the dispensing process was restrict | limited (suppressed).

  [6-2. Modification 2] For example, only one dispensing device 20 is shown in FIG. 1, but a plurality of dispensing devices 20 may be controlled by the dispensing control system 1 (control device 10). FIG. 14 shows a modification. In FIG. 14, the dispensing control system 1 includes a first dispensing device 20A and a second dispensing device 20B. In this case, in the execution history table D4, a “dispensing device” field indicating the dispensing device 20 that has executed the dispensing process is added so that the dispensing device 20 in which the dispensing process has been executed can be identified later. Also good.

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

  The exceptional 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, 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. Is predicted, and it is determined whether or not the time (predicted dispensing time) is 20 minutes or more. When it is determined that the exceptional condition EC7 is satisfied, the determination unit 107 determines to limit the automatic start of the dispensing process of the target prescription data.

  Regarding prescription data that takes a long time when the first dispensing device 20A executes the dispensing process, the user performs the dispensing in a shorter time when the user performs the dispensing process in the second dispensing device 20B. It can be efficient. In this regard, as described above, in the case where it takes a long time when the first dispensing device 20A executes the dispensing process, even if the automatic start function is set to ON, Exceptionally, the first dispensing device 20A is not allowed to execute 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 operation can be improved.

  [6-4. Variation 3] The exception condition table D6 shown in FIGS. 10 and 15 is data indicating conditions for exceptionally limiting the automatic start of the dispensing process 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 indicating conditions when the automatic start of dispensing processing is not restricted exceptionally is stored in the setting data storage unit 101. You may do it.

  FIG. 16 shows an example of the exceptional 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 instead of the exception condition table D6. FIG. 17 is a functional block diagram in this case. The functional block diagram shown in FIG. 17 is different from the functional block diagram shown in FIG. The date / time determination unit 116 determines whether or not the current time satisfies the condition set in the setting data stored in the setting data storage unit 101. Details will be described later.

  Conditions relating to prescription data that do not need to limit the automatic start of the dispensing process are set in the exception condition table D8. In the exception condition table D8, a condition related to a day or time when it is necessary to limit the automatic start of the dispensing process, or a condition related to a day or time that does not need to limit the automatic start of the dispensing process is set. In the exceptional condition table D8 shown in FIG. 16, exceptional conditions EC11, EC12, and EC13 are set. The exceptional conditions EC11 and EC12 correspond to conditions relating to prescription data that do not need to limit the automatic start of the dispensing process. The exceptional condition EC13 corresponds to a condition related to a day (day of the week) when it is better not to limit the automatic start of the dispensing process.

  The exceptional condition EC11 is a condition that “the target prescription data is the same as prescription data previously prescribed for the same patient”. Here, the case where the target prescription data is the same as the prescription data previously prescribed for the same patient is the case where the prescription data is the same as the prescription data previously prescribed for the same patient. is there. In addition, for example, when all of the medical institution, medical department, doctor, drug, usage, dose, days, and quantity are the same, the prescription content may be regarded as the same, and among these items If certain specific items are the same, the prescription content may be regarded as the same.

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

  Alternatively, the target prescription data determination unit 108 refers to the prescription data table D3 to determine whether prescription data identical to the target prescription data exists in prescription data previously prescribed for the same patient. You may do it. Then, when the prescription data as described above exists, the target prescription data determination unit 108 may determine that the exceptional condition EC11 is satisfied.

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

  If it is determined that the exception condition EC11 is satisfied, even if the automatic start function is OFF, the determination unit 107 determines that the automatic start of the dispensing process of the target prescription data is not limited, 1 Start control part 111 makes dispensing device 20 start dispensing processing of object prescription data automatically. In general, regarding prescription data identical to prescription data previously prescribed for the same patient, it is considered that there is little need to confirm again. By setting the exceptional condition EC11 as described above, such In exceptional cases, the dispensing process can be started automatically.

  The exceptional condition EC11 may be a condition that “the target prescription data is the same as or similar to prescription data previously prescribed for 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. Even if there is no problem.

  Instead of the exceptional condition EC11, an exceptional condition may be set such that “the dispensing process of prescription data that is the same as or similar to the target prescription data has been executed by the dispensing device 20 in the past”. When such an exceptional condition is set, the target prescription data determination unit 108 refers to the prescription data table D3 (and the execution history table D4), so that the dispensing process of prescription data that is the same as or similar to the target prescription data is performed. What is necessary is just to determine whether it has been performed by the dispensing apparatus 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 apparatus 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, with the exception conditions as described above, “when the current user (the currently logged-in user) has performed dispensing processing of prescription data identical or similar to the target prescription data by the dispensing device 20 in the past. It is also possible to set an exceptional condition of “the same as the user who has logged into the dispensing control system”. And the dispensing process of the prescription data which is the same as or similar to the target prescription data has been executed by the dispensing device 20 in the past, and the user at that time (the user who was logged in at that time) If the user is the same as the user, the determination unit 107 may exceptionally determine that the automatic start of the dispensing process is not restricted.

  Also, instead of the exceptional condition EC11, “the prescription data is the same as or similar to the prescription data previously prescribed for the same patient, and the prescription data that is the same or similar to the target prescription data has been dispensed in the past. An exception condition that “has been executed by 20” may be set. Here, the case where the prescription data is the same is a case where the patient is the same and the prescription content is the same. In addition, for example, when all of the medical institution, medical department, doctor, drug, usage, dose, days, and quantity are the same, the prescription content may be regarded as the same, and among these items If certain specific items are the same, the prescription content may be regarded as the same. The case where the prescription data is similar is a case where there is no problem even if the prescription contents are the same even if the patients are the same and the prescription contents are not the same.

  When such an exceptional condition is set, the target prescription data determination unit 108 accesses the public database described above, so that the target prescription data is the same as or similar to the prescription data previously prescribed for the same patient. It may be determined whether or not. Alternatively, the prescription data determination unit 108 refers to the prescription data table D3 (and the execution history table D4), so that the dispensing process of prescription data that is the same as or similar to the target prescription data has been executed by the dispensing device 20 in the past. You may make it determine whether there exists.

  Then, the prescription data that is the same or similar to the prescription data previously prescribed to the same patient and the prescription data that is the same or similar to the target prescription data has been executed by the dispensing device 20 in the past. If there is an exception, 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 or similar to the prescription data previously prescribed to the same patient, the dispensing device 20 has executed the dispensing process of the same or similar prescription data to the target prescription data in the past. Otherwise, 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 or similar to the prescription data previously prescribed to the same patient, if it is not prepared at the own hospital or dispensing pharmacy (at another hospital or dispensing pharmacy) If it is dispensed), the dispensing process may not be started automatically, but the dispensing process may be started after a start instruction from a predetermined authority.

  The exceptional condition EC12 is a condition that “the target prescription data is provided from the higher system 2”. When such an exceptional condition E12 is set, for example, the target prescription data determination unit 108 accesses the prescription data table D3 and refers to the input system flag of the target prescription data, so that the target prescription data is the upper system 2. It is determined whether or not the information is provided from. When the target prescription data is provided from the host system 2, the target prescription data determination unit 108 determines that the exceptional condition EC12 is satisfied.

  If it is determined that the exception condition EC12 is satisfied, even if the automatic start function is OFF, the determination unit 107 determines that the automatic start of the dispensing process of the target prescription data is not limited, and the first The start control unit 111 automatically causes the dispensing apparatus 20 to start dispensing the target prescription data. Regarding the prescription data provided from the host system 2, the inspection is also performed on the host system 2 side, so it is considered that the necessity for reconfirmation is low. By setting the exception condition EC12 as described above, In such a case, the dispensing process can be started automatically in exceptional cases.

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

  The determination unit 107 determines whether or not to restrict the automatic start of the dispensing process based on the determination result of the date / time determination unit 116. For example, if the date and time determination unit 116 determines that the exception condition EC13 is satisfied, the determination unit 107 exceptionally restricts the automatic start of the dispensing process of the target prescription data even if the automatic start function is OFF. The first start control unit 111 automatically causes the dispensing device 20 to start dispensing the target prescription data. In general, on Monday, there are many patients who visit the hospital and the number of dispensing processes is expected to increase. By setting the exceptional condition EC13 as described above, in such cases, The dispensing process can be automatically started.

  The exceptional condition EC13 is merely an example, and a period (busy period) in which the number of dispensing processes is expected to increase may be set as an exceptional condition. Alternatively, the dispensing process may be automatically started during the non-business hours by setting the non-business hours as an exception condition.

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

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

  If any of the exceptional conditions EC11 to EC13 is satisfied, the control unit 11 causes the dispensing device 20 to start dispensing the target prescription data (S121). Thereafter, 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 in FIG.

  On the other hand, if none of the exceptional 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 the third modified example, by providing the exception condition table D8, in principle, the dispensing process automatic start function is set to OFF, and the dispensing process is automatically performed only in a specific case. Can be started.

  For example, the dispensing process can be automatically started exceptionally only when the target prescription data is specific prescription data (exception conditions EC11 and EC12). Specifically, when the target prescription data is the same as the prescription data previously prescribed to the same patient, or when the target prescription data is provided from the host system 2, the prescription information is updated again. If the need for confirmation is low (in other words, safety is sufficiently ensured without reconfirming prescription information), exceptionally, the dispensing process can be started automatically, As a result, it becomes possible to improve the efficiency of the dispensing operation.

  Also, in cases where the number of dispensing processes is expected to increase (exception condition EC13), such as on Mondays when more patients visit the hospital, the dispensing process should be started automatically. As a result, it becomes possible to improve the efficiency of the dispensing operation.

  As described above, in the dispensing control system 1, a “medicine” that is taken by a person is directly related to life, so that the safety should be sufficiently ensured by human intervention, and the dispensing operation is performed. The boundary with the case of automation and efficiency improvement becomes very important. In this regard, according to the third modification, in principle, when the dispensing process is started through a person and the safety is sufficiently ensured, and the necessity for executing the dispensing process through a person is low. However, it is possible to improve efficiency by automatically starting the dispensing process.

  [6-5. Modification 4] The dispensing control system 1 (the control device 10) displays an execution history of the dispensing process registered in the execution history table D4 on the display unit 15 or causes the printing unit 16 to print the execution history output control unit. You may make it provide.

  For example, the search condition may be specified by the user, and the execution history output control unit may display or print a list of execution histories that satisfy the search condition. Alternatively, the execution history output control unit may display or print the execution history total satisfying the search condition. In addition, as a search condition, for example, a period, a patient, a start instructor, an authority level, whether or not it is automatic start, and the like may be specified.

  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 apparatus 20A (that is, dispensing processes performed fully automatically by the apparatus as a main component), You may make it display or print the list and the number of the dispensing processes (namely, the dispensing process performed mainly by the person with the assistance of the apparatus) executed in the second dispensing apparatus 20B.

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

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

  In a system such as the dispensing control system 1, a certain user is used while logged in, so that the user instructs the dispensing process to start on the system. In actuality, there is a risk that another user is instructing to start the dispensing process. In this regard, if the user is forced to log off each time the dispensing process of one prescription data is executed, login is necessary every time to give an instruction to start the dispensing process. It becomes difficult to operate like this.

  In this modification, logoff may be performed immediately after completion of the dispensing process, or logoff may be performed when a predetermined time has elapsed after completion of the dispensing process. For example, if the operation is not performed for a predetermined time (for example, 20 seconds) after completion of the dispensing process, the log-off is performed. It may be possible to continuously execute the dispensing process. In addition, regarding the presence / absence of forced logoff, the method of forced logoff, and the predetermined time, a user having a predetermined authority (for example, a user with an authority level “6”) may be arbitrarily set.

  DESCRIPTION OF SYMBOLS 1 Dispensing control system, 2 Host system, 10 Control apparatus, 11 Control part, 12 Storage part, 13 Communication part, 14 Operation part, 15 Display part, 16 Printing part, 17 Database, 20 Dispensing apparatus, 20A 1st dispensing apparatus, 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 first prescription data acquisition unit, 106 second prescription Data acquisition unit, 107 determination unit, 108 target prescription data determination unit, 109 immediately preceding prescription data determination unit, 110 start control unit, 111 first start control unit, 1121 second start control unit, 113 authorized person setting unit, 114 start instruction Reception unit, 115 execution history registration unit, 116 date and time determination unit, G1 list screen, G2 instruction screen, P21 Comment field, P22 execution button, P23 return 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 authority person identification table, D8 exception condition table.

Claims (19)

In a dispensing control system capable of automatically starting dispensing processing by the dispensing execution means,
Prescription data acquisition means for acquiring target prescription data to be subjected to the dispensing process;
Setting data storage means for storing setting data set to determine whether or not to restrict the automatic start of the dispensing process;
A determination means for determining whether to restrict automatic start of the dispensing process based on the setting data;
When it is determined not to limit the automatic start of the dispensing process, a first start control unit that automatically causes the dispensing execution unit to start the dispensing process of the target prescription data;
When it is determined that the automatic start of the dispensing process is restricted, a second start for causing the dispensing execution unit to start the dispensing process of the target prescription data when an instruction to start the dispensing process is received from a predetermined authority Control means;
A dispensing control system comprising: The dispensing control system according to claim 1,
In the setting data, conditions related to prescription data that need to limit the automatic start of the dispensing process, or conditions related to prescription data that does not need to limit the automatic start of the dispensing process are set,
The dispensing control system includes target prescription data determination means for determining whether the target prescription data satisfies the condition,
The determination means determines whether to limit the automatic start of the dispensing process based on the determination result of the target prescription data determination means.
Dispensing control system characterized by that. The dispensing control system according to claim 2,
The condition includes a condition regarding whether or not a specific drug is included in the target prescription data as a drug to be provided to a patient.
Dispensing control system characterized by that. In the dispensing control system according to claim 2 or 3,
The conditions include conditions related to patient data included in the target prescription data.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 2 to 4,
The prescription data acquisition means acquires prescription data input in another system as the target prescription data,
In the other system, the prescription data is audited,
The condition includes a condition as to whether or not the result of the audit for the target prescription data was a predetermined result.
Dispensing control system characterized by that. In the dispensing control system according to any one of claims 2 to 5,
Including display control means for causing the display means to display an input screen for accepting input of prescription data,
The prescription data acquisition means includes
First prescription data acquisition means for acquiring prescription data input via the input screen as the target prescription data;
Second prescription data acquisition means for acquiring prescription data input in another system as the target prescription data,
The condition includes a condition as to whether the target prescription data is prescription data input via the input screen or prescription data input by the other system.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 2 to 6,
The condition includes a condition as to whether or not the target prescription data is the same or similar prescription data to prescription data that has been prescribed to the same patient in the past.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 2 to 7,
The conditions include a condition as to whether or not a 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.
Dispensing control system characterized by that. A dispensing control system according to claim 8 quoting claim 7.
Even if the target prescription data is prescription data that is the same or similar to prescription data that was previously prescribed to the same patient, If the dispensing process has not been executed by the dispensing execution means in the past, it is determined to limit the automatic start of the dispensing process.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 2 to 9,
The condition is that a person who is currently logged in to the dispensing control system logs in to the dispensing control system when dispensing processing of prescription data that is the same as or similar to the target prescription data has been executed by the dispensing execution means in the past. Including the condition of whether or not it is the same as the person who was
Dispensing control system characterized by that. The dispensing control system according to any one of claims 2 to 10,
The condition includes a condition related to a time required for execution of the dispensing process predicted based on the target prescription data.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 1 to 11,
In the setting data, prescription data that needs to limit the automatic start of the dispensing process, or conditions for prescription data that does not need to limit the automatic start of the dispensing process is set,
The dispensing control system includes immediately preceding prescription data determination means for determining whether prescription data that was the object of the dispensing process executed immediately before satisfies the condition,
The determination means 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 means.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 1 to 12,
In the setting data, a condition related to a day or time when it is necessary to limit the automatic start of the dispensing process, or a condition related to a day or time that does not need to limit the automatic start of the dispensing process is set,
The dispensing control system includes date and time determination means for determining whether or not the current condition satisfies the condition,
The determination means determines whether to restrict automatic start of the dispensing process based on the determination result of the date determination means.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 1 to 13,
Including an authorized person setting means for setting the authorized person based on the target prescription data;
Dispensing control system characterized by that. The dispensing control system according to claim 14,
An authority specifying data storage means for storing authority specifying data for specifying an authorized person capable of instructing the start of the dispensing process of the prescription data in association with the condition relating to the prescription data;
The authorized person setting means sets the authorized person based on the authorized person specifying data associated with the condition when the target prescription data that is the target of the dispensing process satisfies the condition.
Dispensing control system characterized by that. The dispensing control system according to claim 14 or 15,
The authorized person setting means includes means for setting the authorized person based on prescription data that was the object of the dispensing process executed immediately before.
Dispensing control system characterized by that. The dispensing control system according to any one of claims 1 to 16,
Registration for registering in the predetermined storage means in association with the target prescription data that is the subject of the dispensing process, the authorized person data relating to the authorized person who has instructed to start the dispensing process, and the comment data entered by the authorized person Including means,
Dispensing control system characterized by that. The dispensing control system according to any one of claims 1 to 17,
The dispensing execution means includes
(A) Powder automatic dispensing / packaging device or system,
(B) Automatic dispensing / packaging device or system for tablets,
(C) Automatic dispensing / dispensing device or system for liquid medicine,
(D) an automatic anti-cancer agent co-infusion apparatus or system;
(E) Dispensing inspection device or system (f) A mode in which any one of these devices or systems is connected, or
(G) a mode in which a plurality of types of devices or systems among these devices are connected;
A dispensing control system characterized by being one of the following. A prescription data acquisition step for acquiring target prescription data to be subject to dispensing processing;
A determination step for determining whether or not to restrict the automatic start of the dispensing process based on setting data set to determine whether or not to limit the automatic start of the dispensing process;
When it is determined not to limit the automatic start of the dispensing process, a first start control step of automatically causing the dispensing execution means to start the dispensing process of the target prescription data;
When it is determined that the automatic start of the dispensing process is restricted, a second start for causing the dispensing execution unit to start the dispensing process of the target prescription data when an instruction to start the dispensing process is received from a predetermined authority Control steps;
A dispensing control method comprising:

Images