JP2019091509A - Pharmacy information management system - Google Patents

Abstract

To provide: a pharmacy information management system capable of improving workability during the input of a human incident by a user; a pharmacy information management method; a pharmacy information management program; and a computer-readable recording medium in which the pharmacy information management program is recorded.SOLUTION: A prescription information display part D33 for displaying prescription information related to prescriptions of medical products, which is stored and accumulated in prescription information storage means, and an incident input part D34 for inputting any information on incidents related to pharmacy of the medical products, are displayed on the same screen of display means. The incident information input to the incident input part D34 is transmitted to a server device.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a dispensing information management system that manages dispensing information related to dispensing of medicines at a medical institution or pharmacy.

  A system is conventionally known that includes a plurality of client terminals installed in a plurality of medical institutions or pharmacies (hereinafter referred to as "pharmacies etc.") and a server device communicably connected to each of the client terminals. (See, for example, Patent Document 1). Specifically, in the system disclosed in Patent Document 1, inventory management and ordering management of medicines of each pharmacy are performed. By the way, in general, in a pharmacy or the like, a pharmacist dispenses a medicine according to a prescription. An error in the dispensing of medicines in such dispensing operations leads to serious situations related to human life. Therefore, each pharmacy manages the incident that occurred in the dispensing operation to prevent an error in dispensing the medicine. An incident means a situation in which there has been no accident related to the dispensing of medicines, but there has been a possibility of an accident. In addition, incidents include incidents that occur with various dispensing devices used for dispensing (hereinafter referred to as “mechanical incidents”) and incidents that occur due to human errors of dispensing workers (hereinafter referred to as “human incidents”). included. Here, with regard to mechanical incidents, it is possible to collect information on mechanical incidents generated in each dispensing device from the dispensing devices to the server device, thereby aggregating them in the server device. The dispensing device is, for example, a tablet dispensing machine, a powder dispensing machine, or the like. On the other hand, information on human incidents can be integrated into the server device by inputting the information to the client terminal and transmitting it to the server device.

JP 2002-215806 A

  However, in the conventional system, when the user inputs information on a human incident, items such as prescription information that are targets of occurrence of the human incident are not displayed on the input screen. Therefore, the user can not input a human incident while checking prescription information, and there is a problem that the workability at the time of human incident input is bad. The prescription information is, for example, information such as when, where and to which patient what medicine is prescribed. Therefore, the present invention has been made in view of the above circumstances, and the purpose thereof is a dispensing information management system, a dispensing information management method, and a dispensing which can improve the operability at the time of inputting a human incident by a user. An information management program and a computer readable recording medium recording a dispensing information management program.

In order to achieve the above object, according to the present invention, there is provided a read control means for reading out the prescription information from the prescription information storage means in which the prescription information on the prescription of the medicine is accumulated and stored; Display control means for displaying on the same screen of the display means, a prescription information display portion for displaying the information and an incident input portion for arbitrarily inputting information on an incident related to the dispensing of the medicine, and the incident input portion And a storage control means for storing information on the incident in the incident information storage means. According to the present invention, since the prescription information display unit and the incident input unit are displayed on the same screen, the user can input the information of the incident to the incident input unit while confirming the prescription information display unit. It can be carried out. Therefore, the workability at the time of the input of the incident by a user can be improved. Further, in the case where patient information on a patient who has received a prescription of the medicine is further accumulated and stored in the prescription information storage means, the read control means reads out the patient information from the prescription information storage means. It is conceivable that the display control means displays the prescription information and the patient information on the prescription information display unit. Thereby, the user can input the information of the incident to the incident input unit while confirming the patient information in addition to the prescription information.

  Here, after the display control means causes the display means to display a prescription selection screen for selecting any of the prescription information stored in the prescription information storage means, the display control means is selected on the prescription selection screen It is conceivable that the patient information corresponding to the prescription information and the prescription information is displayed on the prescription information display unit. Thereby, the user can display the prescription information and the patient information on the prescription information display unit by a simple operation of selecting the prescription information from the prescription selection screen.

  Furthermore, it is conceivable that the incident input unit includes a target pharmaceutical input unit for inputting a target pharmaceutical of the incident. Further, the prescription information display unit may include a medicine selection unit for selecting a medicine targeted for the incident from among the medicines displayed on the prescription information display unit. In this case, it is preferable that the display control means reflect the medicine selected by the medicine selection unit on the target medicine input unit. Thereby, the user does not need to directly input the medicine into the target medicine input unit, and can input the medicine of the object of the incident quickly and accurately by the operation of the medicine selection unit.

  By the way, the contents of the incident include various types such as wrong prescription, wrong medicine type, wrong number of medicine, etc., and the risk level or the importance is different for each contents of the incident. Therefore, it was not possible to rank and record each of the incidents quickly and accurately according to the danger level or importance. Therefore, it is conceivable that the dispensing information management system comprises level correspondence information storage means in which level correspondence information indicating the correspondence between the content of the incident and the level of the incident is stored. The incident input unit may include a content input unit for inputting the content of the incident and a level input unit for inputting the level of the incident. In this case, the display control means causes the level input unit to reflect the level of the incident corresponding to the content of the incident based on the content of the incident input to the content input unit and the level correspondence information. Is desirable. Thus, the user does not have to directly input the level in the level input unit, and can quickly and accurately input the level corresponding to the content of the incident by the operation of inputting the content of the incident. Therefore, in the dispensing information management system, for example, when referring to the information on the incident, it is also possible to rank and display the information on the incident for each level. It is also conceivable that an input of a level different from the level correspondence information stored in the level correspondence information storage means is required. Therefore, it is conceivable to include a level change unit that arbitrarily changes the level of the incident reflected on the level input unit according to the content of the incident by the display control unit. As a result, after being reflected on the level input unit according to the contents of the incident by the display control means, the level of the incident can be changed by the level changing means, and usability is enhanced.

Also, it is considered that the incident input unit includes a classification selection unit for selecting the content of the incident from a plurality of preset classifications, and an explanation input unit into which an explanation of the content of the incident is input. Be In this case, it is preferable that the display control means reflects the explanation of the format preset for each classification according to the classification selected by the classification selection unit in the explanation input unit. More specifically, the classification selection unit selects one of a large classification selection unit for selecting any of a plurality of large classifications set in advance and a plurality of small classifications set in advance for each of the large classifications. It is conceivable to include a minor classification selection unit for In this case, the display control means causes the small classification selection unit to display a plurality of small classifications corresponding to the large classification selected by the large classification selection unit, and the display control means selects the small classification selection unit. It is conceivable that the explanation of the format corresponding to the minor classification is reflected in the explanation input unit. According to such a configuration, the user does not have to directly input the description of the content of the incident, but inputs the description of the format corresponding to the content of the incident quickly and accurately by the operation of inputting the content of the incident It can be performed. In particular, since an explanation of the same format set in advance according to the content of the incident is input, the information of the incident becomes easy to see.

  Further, the dispensing information management system automatically dispenses the medicine according to the input dispensing data, a picking assist device used when manually dispensing the medicine according to the input dispensing data, and Transfer means for transmitting a part or all of the dispensing data input to the automatic medicine dispensing apparatus to the picking assistance device according to a preset transfer condition, and history for storing transmission history information of the dispensing data by the transfer means It is conceivable to provide a storage means. Thus, by referring to the transmission history information stored in the history storage means, it is possible to grasp the frequency of use of the automatic medicine dispensing device and the picking assistance device. For example, when the transfer condition is a shortage of medicine in the automatic medicine dispensing apparatus, it is possible to grasp the occurrence frequency of the shortage of medicine in the automatic medicine dispensing apparatus. In addition, if there is a large amount of the dispensing data transmitted from the automatic medicine dispensing device to the picking assistance device, it can be grasped that the workload of a pharmacist or the like who uses the picking assistance device is too large. Furthermore, it is preferable that the history storage means further store picking history information on a history of picking performed using the picking assist device. Thereby, it is possible to grasp the history such as the collation result of picking by the picking assistant device 54 with reference to the picking history information stored in the history storage means. Further, it is conceivable that the storage control means stores information of the incident and either or both of the prescription information and the patient information corresponding to the incident in the incident information storage means in association with each other. . Thereby, when referring to the information of the incident, it becomes possible to easily grasp one or both of the prescription information and the patient information which are targets for which the incident has occurred. For example, when performing display output, print output, data output, etc. of the information of the incident by a computer (information processing apparatus), one or both of the prescription information and the patient information that are targets for which the incident has occurred It is conceivable to output at the same time. In addition, when referring to either or both of the prescription information and the patient information, it is possible to easily grasp the information on the incident corresponding to the prescription information or the patient information.

By the way, there can be considered a configuration provided with a plurality of client terminals having the read control means, the display control means, and the storage control means, and a server device having the incident information storage means. In this case, it is conceivable that the storage control means causes the incident storage means to store the information of the incident by transmitting the information of the incident to the server device. The prescription information storage unit is provided in the client terminal or the server device. According to such a configuration, the information on the incident input to each of the client terminals disposed in a plurality of medical institutions, pharmacies, etc. is transmitted to the server device, whereby the information on the incident is transmitted to the server device. Can be consolidated. This makes it easy to effectively use, for example, the information on the incident as statistical information. Further, the present invention is a dispensing information management system comprising a plurality of client terminals and a server device communicably connected to each of the client terminals, wherein the server device is transmitted from each of the client terminals. The incident information storage means for storing and storing the information of the incident related to the dispensing of the medicine, and the statistical information output means for outputting the statistical information of the incident stored in the incident information storage means according to the input statistical display condition; It can also be considered to be configured as a dispensing information management system. Thus, the user can easily grasp the occurrence status of the incident in each of the client terminals by confirming the statistical information of the incident output from the statistical information output unit. More specifically, it is conceivable that the dispensing information management system further includes statistical display condition input means for inputting the statistical display condition into the server device. Then, the display condition input means inputs classification units of each of the client terminals for calculating statistical information of the incident into the server apparatus as the statistical display condition. On the other hand, the statistical information output means outputs statistical information of the incident calculated for each of the selected classification units in accordance with the statistical display condition. Thereby, the user can easily confirm only the occurrence situation of the incident related to the desired classification unit by selecting an arbitrary classification unit by the display condition input means. Preferably, the dispensing information management system comprises classification unit setting means for arbitrarily setting the classification unit. Thereby, the user can set any client terminal as the same or different classification unit. By the way, when the statistical information includes the number of occurrences for each content of the incident, the statistical information output means may be any of a pharmaceutical unit, a prescription unit, or no count set in advance for each content of the incident. It is desirable to count the number of occurrences of the incident. As a result, it is possible to obtain effective statistical information obtained by counting the number of incidents in an appropriate unit. Further, it is conceivable that the server device comprises: user authentication means for authenticating a user; and authority information storage means in which authority information concerning contents of the statistical information which can be displayed for each user is stored in advance. And, in this case, it is conceivable that the statistical information output means changes the output content of the statistical information based on the user authenticated by the user authentication means and the authority information. Thereby, the incident information that can be referred to for each user can be set in advance arbitrarily.

  Further, according to the present invention, there is provided a reading control step of reading out the prescription information from the prescription information storing means in which the prescription information on the prescription of the medicine is accumulated and stored, and a prescription information display unit for displaying the prescription information read out in the reading step. And a display control step for displaying on the same screen of the display means an incident input unit for arbitrarily inputting information on an incident related to the dispensing of the medicine, and information on the incident input to the incident input unit as incident information And a storage control step of storing the information in the storage means. Here, in the case where patient information on a patient who has received a prescription of the medicine is further accumulated and stored in the prescription information storage means, the read control step reads out the patient information from the prescription information storage means. It is conceivable that the display control step is to display the prescription information and the patient information on the prescription information display unit. Further, a dispensing information management program for causing a computer to function as each means provided in the dispensing information management system may be taken as the present invention. Furthermore, the present invention may be regarded as a computer readable recording medium in which the dispensing information management program is recorded.

ADVANTAGE OF THE INVENTION According to this invention, the workability at the time of the input of the human incident by a user can be improved. In particular, the incident input unit includes a target medicine input unit for inputting a medicine targeted for the incident, and the prescription information display unit displays the medicine targeted for the incident on the prescription information display unit. It is conceivable to comprise a drug selection unit for selecting from the aforementioned drugs. In this case, if the display control means reflects the medicine selected by the medicine selection unit in the target medicine input unit, the user does not need to directly input the medicine in the target medicine input unit. By the operation of the medicine selection unit, it is possible to quickly and accurately input medicines targeted for the incident. Further, the information processing apparatus further comprises level correspondence information storage means in which level correspondence information indicating the correspondence relation between the content of the incident and the level of the incident is stored, and the display control means receives the incident entered in the content input unit. A configuration is also conceivable in which the level of the incident corresponding to the content of the incident is reflected in the level input unit based on the content of the content and the level correspondence information. Thus, the user does not have to directly input the level in the level input unit, and can quickly and accurately input the level corresponding to the content of the incident by the operation of inputting the content of the incident. Furthermore, it is also conceivable that the storage control means stores information of the incident and either or both of the prescription information and the patient information corresponding to the incident in the incident information storage means in association with each other. . Thereby, when referring to the information of the incident, it becomes possible to easily grasp one or both of the prescription information and the patient information which are targets for which the incident has occurred. In addition, when referring to either or both of the prescription information and the patient information, it is possible to easily grasp the information on the incident corresponding to the prescription information or the patient information.

BRIEF DESCRIPTION OF THE DRAWINGS The schematic diagram which shows schematic structure of the dispensing information management system which concerns on embodiment of this invention. Diagram showing part of Incident Master data. The flowchart which shows an example of the procedure of the incident master edit process performed by a client terminal. The figure which shows an example of a master registration screen. The flowchart which shows an example of the procedure of the incident input process performed by a client terminal. The figure which shows an example of a prescription selection screen. The figure which shows an example of an incident screen. The figure which shows an example of display switching information. The figure which shows an example of a drug list screen. The figure which shows an example of the information of an incident. A figure showing an example of an audit screen. The flowchart which shows an example of the procedure of the incident statistics output process performed with a client terminal and a server apparatus. The figure which shows an example of the input screen of statistics display conditions of an incident. The figure which shows the example of a display of the statistical information of an incident. The figure which shows the example of a display of the statistical information of an incident. The figure which shows an example of the flow of time of dispensing operation in a pharmacy etc.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings for understanding of the present invention. The following embodiment is an example embodying the present invention, and is not of the nature to limit the technical scope of the present invention.

[Dispensing Information Management System 1]
As shown in FIG. 1, the dispensing information management system 1 according to the embodiment of the present invention includes a server device 10, a plurality of client terminals 20, and a plurality of management terminals 30. Each of the client terminals 20 is provided for each medical institution or pharmacy, and the server device 10 and the management terminal 30 are provided in a facility having a headquarters function that supervises a plurality of medical institutions or pharmacies. The management terminal 30 is an information processing apparatus such as a personal computer used to refer to information on incidents stored in the server apparatus 10. Of course, it is also conceivable that the server device 10 or the management terminal 30 is disposed in a medical institution or a pharmacy along with the client terminal 20. Further, in the present embodiment, the dispensing information management system 1 will be described as an example of the dispensing information management system according to the present invention, but the present invention is not limited to this. For example, it is conceivable that the client terminal 20 has the functions of the server device 10 and the management terminal 30, and in this case, the client terminal 20 alone corresponds to the dispensing information management system according to the present invention. That is, it is conceivable that the client terminal 20 includes the read control unit, the display control unit, the storage control unit, and the incident information storage unit according to the present invention. The server device 10 is communicably connected to the plurality of client terminals 20 and the plurality of management terminals 30 via a communication network 40 such as a LAN or the Internet. The dispensing information management system 1 may include a plurality of the server devices 10 for backup.

[Server device 10]
The server device 10 is a computer provided with a CPU 11, a ROM 12, a RAM 13, a data storage unit 14, a communication interface 15, an operation input device 16, a display device 17, and the like. The components provided in the server device 10 are connected by a bus 18. The CPU 11 is a processor that executes various arithmetic processing in accordance with various control programs. The ROM 12 is a non-volatile memory in which a program such as a BIOS executed by the CPU 11 is stored in advance. The RAM 13 is a volatile memory or a non-volatile memory used for expansion of various control programs by the CPU 31 and temporary storage of data. The communication interface 15 has a communication modem or the like that performs data communication with each of the client terminal 20 and the management terminal 30 via the communication network 40. The operation input device 16 is an input unit used by a user to input various information to the server device 10. The display device 17 is a display means such as a liquid crystal display or an organic EL display having a display screen for displaying various information. Specifically, the operation input device 16 has a keyboard and a mouse (a pointing device) used to input various information in accordance with the display screen of the display device 17.

  The data storage unit 14 is a hard disk or the like in which various application programs executed by the CPU 11 and various data are stored. Specifically, the data storage unit 14 stores a dispensing information management program which causes the CPU 11 to execute processing procedures such as incident statistical information output processing (see FIG. 12) described later. For example, the dispensing information management program is described in C language (such as C / C ++ and Visual C / C ++ (registered trademark) of Microsoft Corporation). The said dispensing information management program is installed from recording media, such as CD, DVD, BD, flash memory, for example. Further, the data storage unit 14 stores information of incidents described later transmitted from each of the client terminals 20 together with databases such as, for example, a pharmaceutical master, a pharmacy master, and an incident master. The drug master includes, for example, drug code, drug name, JAN code (or RSS), vial code, classification (dosage form: powder, tablet, liquid, external medicine, etc.), specific gravity, drug type (conventional drug, poison drug) , Narcotics, potent drugs, antipsychotic drugs, therapeutic drugs, etc.), formulation changes, excipients, information such as precautions, etc. are included. The pharmacy master includes, for example, information such as a store name corresponding to each of the client terminals 20, a group to which the store belongs, a group division to which the store belongs, a place of the store, and a pharmacist belonging to the store. For example, the group classification is an area name such as "Kansai" or "Kanto", and the group is a name of a prefecture such as "Osaka" or "Hyogo".

Incident Master
The incident master stored in the data storage unit 14 is information referred to when the client terminal 20 inputs information on an incident. Here, FIG. 2 shows a part of the data of the incident master. As shown in FIG. 2, in the incident master, the group number, the group (major classification), the classification, the content of the incident (major classification), and the level are stored in association with each other for the medicine dispensing events. Note that part of the incident master can be edited in an incident master editing process (see FIG. 3) described later that is executed by the client terminal 20. Here, to the group of the incident, “chemical acquisition error”, “weighing / counting error”, “separate packing error”, “master error”, “input error”, “fill error”, “other”, “operation error” , "User input" is included. Note that the group of “user input” is a group that is arbitrarily set when the incident content is additionally registered by the user, or a group that is set by being selected from the existing groups. And in the said incident master, the content of the incident is set for every said group. For example, the “drug acquisition error” group includes incident contents of “drug acquisition error”, “drug overlap acquisition”, “standard acquisition error”, and “forgetting medicine”. A category is assigned to each content of the incident, and the category is a numerical value used for input assistance for each content of the incident. Furthermore, in the incident master, a level is set for each content of the incident. The level of the incident is represented by five levels of “S”, “A”, “B”, “C”, and “D”, and the level “S” is an incident with the highest degree of danger or importance. The level of the incident may be indicated by a numerical value such as “1” to “5”. Here, the incident master is an example of level correspondence information, and the data storage unit 14 is an example of a level correspondence information storage unit. The level correspondence information storage unit may be a Web server provided on a network accessible from the server device 10, the client terminal 20, or the management terminal 30.

[Client terminal 20]
The client terminal 20 is a computer including a CPU 21, a ROM 22, a RAM 23, a data storage unit 24, a communication interface 25, an operation input device 26, a display device 27, a dispensing communication unit 28 and the like. The components provided in the client terminal 20 are connected by a bus 29. The communication interface 25 has a communication modem or the like that performs data communication with each of the server device 10 and the management terminal 30 via the communication network 40.

  The CPU 21 is a processor that executes various arithmetic processing in accordance with various control programs. The ROM 22 is a non-volatile memory in which a program such as a BIOS executed by the CPU 21 is stored in advance. The RAM 23 is a volatile memory or a non-volatile memory used for expansion of various control programs by the CPU 21 and temporary storage of data. The operation input device 26 is an input unit used by a user such as a pharmacist to input various information to the client terminal 20. The display device 27 is a display means such as a liquid crystal display or an organic EL display having a display screen for displaying various information. Specifically, the operation input device 26 has a keyboard and a mouse (a pointing device) used to input various information in accordance with the display screen of the display device 27. Hereinafter, “operation”, “selection” and “input” in the client terminal 20 are performed by using a keyboard or a mouse of the operation input device 26 by users such as a pharmacist, doctor, nurse, engineer and clerk. It means work to be done. The operation input device 26 may have a touch panel provided on the display device 27 or a voice operation input device for receiving input of various information by voice recognition.

The data storage unit 24 is a hard disk or the like in which various application programs executed by the CPU 21 and various data are stored. Specifically, in the data storage unit 24, the CPU 21 performs each of an incident master editing process (see FIG. 3), an incident input process (see FIG. 5), and an incident statistical information output process (see FIG. 12) described later. A dispensing information management program for executing the processing steps is stored. For example, the dispensing information management program is described in C language (such as C / C ++ and Visual C / C ++ (registered trademark) of Microsoft Corporation). The dispensing information management program is installed from a recording medium such as a CD, a DVD, a BD, a flash memory, and the like. Furthermore, the dispensing information management program is stored in the server device 10 or the web server, and the CPU 21 accesses the server device 10 or the web server via the communication network 40, and the dispensing information management program It is also conceivable to execute a process that follows. That is, it is also conceivable that the dispensing information management program is a so-called web application operated on a web browser.

  Further, in the data storage unit 24, prescription history information regarding prescription data input to the client terminal 20 is stored together with a database such as a medicine master and a patient master. The drug master includes drug code, drug name, JAN code (or RSS), vial code, division (dosage form: powder, tablet, liquid, external medicine, etc.), specific gravity, drug type (conventional drug, poison, Information such as narcotics, potent drugs, antipsychotic drugs, therapeutic drugs, etc., formulation changes, excipient drugs, precautions, etc. is included. The patient master includes information such as patient ID of each patient, name, sex, age, medical history, family information, medical department, ward and hospital room. On the other hand, the prescription history information includes prescription information on prescription of a past medicine and patient information on a patient who has received the prescription on the medicine. For example, the prescription history information includes information such as when, where and to which patient what medicine has been prescribed. Specifically, the prescription history information includes the date and time of receipt of prescription data, voucher number, patient ID, patient name, medical institution, medical department, audit result, incident information, prescription drug code, prescription drug name, dosage form Dose, usage, information on incidents described later, etc. Here, a prescription drug code and a prescription drug name are examples of the prescription information, and a patient ID and a patient name are examples of the patient information. The prescription history information is accumulated and stored in the data storage unit 24 by the CPU 21 each time a medicine is dispensed using a later-described dispensing device connected to the client terminal 20. Here, the data storage unit 24 is an example of the prescription information storage unit. The prescription information storage unit may be a Web server provided on a network accessible from the server device 10, the client terminal 20, or the management terminal 30.

  The dispensing communication unit 28 is a LAN between the receiving terminal 51 to which patient's prescription data is input, and a dispensing device such as a tablet dispensing device 52, a powder dispensing device 53, and a picking assistance device 54 used for dispensing a medicine. , Etc. are communicably connected via the communication network 50. Specifically, the dispensing communication unit 28 includes a communication modem or the like that performs data communication with the reception terminal 51 and the dispensing device via the communication network 50. The reception terminal 51 is a personal computer or the like for inputting prescription data described in a patient's prescription, and the prescription data input to the reception terminal 51 is input to the client terminal 20. The client terminal 20 may have the function of the reception terminal 51.

The tablet dispensing and packaging machine 52 (an example of an automatic medicine dispensing apparatus) has a plurality of medicine cassettes containing tablets of a plurality of types of medicines, and according to a control instruction (dispensing data) input from the client terminal 20 The tablets are automatically taken out from the medicine cassette and packaged in medicine packs or blister packs for each dose. The powder dispensing and packaging machine 53 packages the powder according to control instructions (dispensing data) input from the client terminal 20 into medicine packages for each dose. In the powder dispensing and packaging machine 53, it is also possible to package the powders together with the tablets for each dose. The picking aid device 54 is used when picking and manually dispensing medicines from the medicine rack according to a prescription by a pharmacist etc., reading the medicine name from a bar code such as a medicine rack or a medicine bottle and reading the medicine And the medicine described in the prescription. The types of the dispensing device connected to the client terminal 20 are not limited to these. For example, PTP sheet dispenser that automatically dispenses PTP sheet drugs, automatic injection dispensing system that automatically dispenses injections, powder medicine inspection device that weighs and checks powders, water that dispenses liquid medicines An agent dispensing apparatus etc. correspond also to the said dispensing apparatus. Each of the dispensing devices may be communicably connected to the client terminal 20 and the server device 10 via the communication network 40. Further, each of the dispensing devices has a function of transmitting to the client terminal 20 an incident that has occurred in dispensing the medicine. Thereby, the information of the incident which generate | occur | produced in each said dispensing apparatus is collected by the said client terminal 20. FIG. Then, the client terminal 20 transmits the information of the incident to the server device 10.

  In the client terminal 20, the CPU 21 selects the dispensing device for dispensing the medicine included in the prescription data according to the prescription data input from the reception terminal 51 or the prescription data input by the operation input device 16. Do. The prescription data includes a prescription delivery date, patient ID, patient name, patient birth date, dosage form information (for internal use, external use, etc.), drug information (drug code, drug name, dose), usage information ( After meals every 3 times a day etc. are included. Then, the CPU 21 generates dispensing data for causing each of the dispensing devices to dispense the medicine, and transmits the dispensing data from the dispensing communication unit 28 to each of the dispensing devices.

However, when the medicine contained in the dispensing data is out of stock in the tablet dispensing machine 52 which has received the dispensing data, or the dispensing waiting time of the medicine in the tablet dispensing machine 52 exceeds a predetermined time, etc. When the predetermined transfer condition is satisfied, the control unit of the tablet dispensing and packaging machine 52 notifies the client terminal 20 to that effect. Then, the CPU 21 of the client terminal 20 transmits, to the picking assistance device 54, dispensing data regarding a part or all of the medicines satisfying the transfer condition among the dispensing data. Thereby, the user can dispense a medicine using the picking aid device 54. Here, the CPU 21 when executing such processing corresponds to the transfer means. The subject that transfers the dispensing data from the tablet packaging machine 52 to the picking assistance device 54 may be not only the client terminal 20 but also the control unit of the tablet packaging machine 52. In this case, the control unit of the tablet packaging machine 52 corresponds to the transfer means. In addition, the picking assistance device 54 stores picking history information related to a history such as a matching result of picking performed by a pharmacist or the like based on the dispensing data in the internal storage memory and also transmits it to the client terminal 20 . At this time, the CPU 21 of the client terminal 20 transfers the transmission history information related to the dispensing data transferred from the tablet packaging machine 52 to the picking assistance device 54 and the picking history information received from the picking assistance device 54. The transmission history information and the picking history information are transmitted to the server device 10 and stored in the data storage unit 14 while being stored in the data storage unit 24. Here, each of the data storage unit 24 and the data storage unit 14 corresponds to a history storage unit. Thus, when the transmission history information and the picking history information are stored in the data storage unit 24 and the data storage unit 14, the user refers to the transmission history information in the client terminal 20 and the server device 10. As a result, the frequency of use of the tablet packaging machine 52 and the picking assistance device 54 can be grasped. For example, the occurrence frequency of the shortage of medicine in the tablet packaging machine 52 can be grasped. In addition, if there is a large amount of the dispensing data transmitted from the tablet dispensing and packaging machine 52 to the picking assistance device 54, it can be grasped that the workload of the pharmacist etc. who uses the picking assistance device 54 is too large. On the other hand, by referring to the picking history information in the client terminal 20 and the server device 10, the user can grasp the history such as the collation result of picking by the picking assistant device 54. Furthermore, the CPU 21 of the client terminal 20 or the control unit of the tablet dispensing machine 52 indicates a two-dimensional barcode or a three-dimensional barcode or the like indicating dispensing data regarding some or all medicines satisfying the transfer condition among the dispensing data. It is also conceivable to print out on the printer as transfer information. In this case, it is conceivable that the user causes the picking assistant device 54 to read the printed two-dimensional barcode or three-dimensional barcode, and uses the picking assistant 54 to dispense a medicine. The control unit of the picking assistance device 54 may read the dispensing data from the client terminal 20 based on the transfer information. Also, the CPU 21 of the client terminal 20 stores the transfer information in the data storage unit 24 instead of the transmission history information, and transmits the transmission history information to the server device 10 to the data storage unit 14. It is conceivable to memorize.

  Hereinafter, in the dispensing information management system 1, processing executed by each of the server device 10 and the client terminal 20 will be described.

Incident Master Editing Process
First, an example of the procedure of the incident master editing process executed by the CPU 21 of the client terminal 20 according to the dispensing information management program will be described with reference to the flowchart of FIG. 3. Note that S1, S2,... Shown in the drawings indicate process procedure (step) numbers executed by the CPU 21.

(Step S1)
First, in step S1, the CPU 21 determines whether or not the editing start operation of the incident master has been performed by the user operation of the operation input device 26. Here, when the CPU 21 determines that the editing start operation of the incident master has been performed (Yes in S1), the CPU 21 shifts the process to step S2. When the CPU 21 determines that the editing start operation of the incident master has not been performed (Yes in S1), the CPU 21 causes the process to stand by in the step S1. Specifically, the CPU 21 displays an initial setting screen for the dispensing information management program according to the operation of the operation input device 26, and then starts editing the incident master according to the operation according to the initial setting screen. If the operation has been performed (Yes in S1), the process proceeds to step S2.

(Step S2)
Next, in step S2, the CPU 21 determines whether the data storage unit 14 of the server device 10 can be accessed. Here, when the data storage unit 14 of the server device 10 is accessible (Yes in S2), the CPU 21 shifts the process to step S3. On the other hand, when the data storage unit 14 of the server device 10 can not be accessed (No in S2), the CPU 21 shifts the process to step S21.

(Step S21)
In step S21, the CPU 21 causes the display device 27 to display that the data storage unit 14 of the server device 10 can not be accessed. For example, it can be considered that the CPU 21 displays on the display device 27 that "the access can not be made because maintenance is currently in progress". Thereafter, the CPU 21 returns the process to step S1.

(Step S3)
On the other hand, in step S3, the CPU 21 displays a login screen on the display device 27 and waits for a login operation by the user (No in S3). Here, when the user ID and the password are input and the user authentication is performed by the user operation on the operation input device 26, the CPU 21 determines that the login operation is performed (Yes in S3), and the process is performed in step S4. Migrate to Note that various conventional techniques may be adopted as the method of the login operation.

(Step S4)
In step S4, the CPU 21 causes the display device 27 to display a master registration screen D11 for editing the incident master. Here, FIG. 4 is a view showing a display example of the master registration screen D11. As shown in FIG. 4, in the master registration screen D11, a search screen D12 for searching for an incident category registered in the incident master, and a setting for setting the content of the incident category to be registered in the incident master Screen D13 is included. At the lower end portion of the master registration screen D11, a registration key 111, a search key 112, a delete key 113, a condition clear key 114, and a return key 115 are displayed.

(Step S5)
Then, in step S5, the CPU 21 executes an editing process for editing the incident master in accordance with the user operation of the operation input device 26 in accordance with the master registration screen D11.

  Specifically, when the search key 112 is operated after the “division” and “name” are input as the search condition on the search screen D12, the CPU 21 searches for the “division” and “name”. A list of incident categories satisfying the above is extracted from the incident master and displayed on the search screen D12. Then, when the incident category is selected on the search screen D12, the CPU 21 displays the setting content of the incident on the setting screen D13. When the contents of the incident classification are newly registered, each input field of the setting screen D13 is blank.

  Thereafter, the CPU 21 edits the information of each of the input fields displayed on the setting screen D13 in accordance with the user operation of the operation input device 26. Specifically, in the setting screen D13, “incident classification”, “incident classification name”, “incident group number”, “incident level”, “incident occurrence information”, “valid flag”, “pharmacist incident flag”, Input fields such as “OK number acquisition type (store)”, “OK number acquisition type (pharmacist)”, “target dispensing device”, and “sort number” are included.

  The “incident classification” is a text input field into which numerical information or the like for identifying the incident is input. “Incident classification name” is a text input field in which the content of the incident is input. The “incident group number” is a pull-down input field for selecting and inputting a group to which the incident classification belongs, and the selection candidate of the group is extracted from the incident master (see FIG. 2). “Incident level” is a pull-down input box in which the level of the incident is selected and input, for example, selected and input from five stages of “S”, “A”, “B”, “C”, “D” . The “incident occurrence information” is a pull-down input field in which an incident occurrence information flag is selected and input. For example, in "incident occurrence information", "drug", "drug (mistake)", "drug (mistake in dose)", "medicine (mistake in normal dose)", "medicine (mistake in specified dose)", "usage" , "Medical institution", "medical department", "comment" etc. are selected and input. And "incident occurrence information" is a judgment index of the possibility of input to the input parts D35 to D37 of the incident screen D31 (refer to FIG. 7) displayed in the later-described incident input process (refer to FIG. 5) executed by the CPU 21. Referred to as

The “valid flag” is a pull-down input field in which whether or not to count as an incident in statistical information of an incident is selected and inputted. The “pharmacist incident flag” is a pull-down input field for selecting whether or not to add the number of incidents of the pharmacist who has handled the incident in the statistical information of the incident. "OK number acquisition type (store)" is a pull-down input field where the unit for counting the number of OK cases of an incident is selected and input for each store, and for example, there is no count, the number of prescriptions, or the number of medicines Selected. "Ok number acquisition type (pharmacist)" is a pull-down input field in which the unit for counting the number of OK cases of an incident is selected and input for each pharmacist. Selected. The “target dispensing device” is a list input field in which the type of the target dispensing device capable of using the incident classification is selected and input when the incident is input. In the list entry column of “target dispensing device”, when the target dispensing device is selected in the list on the left and “add” is operated, the target dispensing device is added to the list on the right and the incident classification can be used When the target dispensing device is selected in the list on the right and "Delete" is operated, the target dispensing device is excluded. In the list input field of “target dispensing device”, for example, a display area for six lines is secured, and six types of target dispensing devices are simultaneously displayed in the list input field of “target dispensing device”. “Sort number” is a numerical value that defines the sort order when listing the incident categories, and when it is empty, “9999” is set as the initial value.

  In addition, when the delete key 113 is operated, the CPU 21 deletes the content of the incident classification displayed on the setting screen D13 from the incident master. However, among the incident categories included in the incident master, an incident category that can be deleted by the delete key 113 is only a 900-series category (see FIG. 2) corresponding to “user input”. Furthermore, in this case, before the CPU 21 deletes the contents of the incident category, for example, a message for reconfirming the deletion, such as "Delete. Are you sure?", For selecting the presence / absence of the deletion. It is displayed on the display device 26 together with the "OK" and "Cancel" operation parts. Then, after the display of the message, the CPU 21 deletes the content of the incident classification from the incident master on condition that the operation unit “OK” is operated. Further, when the condition clear key 114 is operated, the CPU 21 initializes the information displayed on the setting screen D13, and moves the cursor indicating the operation target to the “incident classification”. Thereby, the user can start the input of the information according to the setting screen D13 again from the beginning.

(Step S6)
Then, in step S6, the CPU 21 determines whether to cancel the editing of the incident master according to the presence or absence of the operation of the back key 115. Here, when the CPU 21 determines that the operation of the back key 115 is performed and cancels the editing of the incident master (Yes in S6), the setting content on the master registration screen D11 is reflected on the incident master The process returns to the step S1 without causing the process. On the other hand, when the CPU 21 determines that the return key 115 is not operated and the editing of the incident master is not canceled (No in S6), the process proceeds to step S7.

(Step S7)
In step S7, the CPU 21 determines whether or not the editing content of the incident master is to be determined, according to the presence or absence of the operation of the registration key 111. Here, when the CPU 21 operates the registration key 111 and determines that the editing content of the incident master is to be decided (Yes in S7), the CPU 21 shifts the process to step S8. On the other hand, when the CPU 21 determines that the registration key 111 is not operated and the editing content of the incident master is not determined (No in S7), the process returns to the step S5 and follows the master registration screen D11. Continue the editing process of the incident master.

(Step S8)
In step S8, the CPU 21 sets a setting screen D of the master registration screen D11.
After reflecting the contents of the incident classification inputted in 13 in the incident master, the series of incident master editing processing is ended, and the processing is returned to the step S1. Specifically, the CPU 21 checks whether or not the content of the incident classification inputted in the setting screen D13 violates the preset prohibition content, and if there is an error, the fact is The display 26 is displayed. For example, the content of the prohibition is that the incident classification is a number of a predetermined number of digits, or a predetermined number such as 900s. Then, if the content of the incident classification violates the prohibition processing, the CPU 21 returns the processing to the step S5 to urge correction of the content of the incident classification. On the other hand, when there is no error in the content of the incident classification, the CPU 21 reflects the content of the incident classification input on the setting screen D13 in the incident master. At this time, the CPU 21 updates the contents of the incident class with the contents after the change when the incident class already registered in the incident master of the data storage unit 14 is edited. When the contents of the incident class not yet registered in the incident master of the data storage unit 14 are newly set, the CPU 21 sets the contents of the incident class after the setting to the incident master. Add and memorize.

Incident Input Processing
Next, an example of the procedure of an incident input process executed by the CPU 21 of the client terminal 20 according to the dispensing information management program will be described with reference to the flowchart of FIG. 5. Note that S101, S102, ... shown in the figure indicate process procedure (step) numbers executed by the CPU 21. The CPU 21 at the time of executing the incident input processing corresponds to a display control unit according to the present invention.

(Step S101)
First, in step S101, the CPU 21 determines whether an incident input start operation has been performed by a user operation of the operation input device 26. Here, when the CPU 21 determines that the incident input start operation has been performed (Yes in S101), the CPU 21 shifts the process to step S102. In addition, if the said CPU21 judges that the said incident input start operation is not performed (No side of S101), it will make a process stand by at said step S101.

(Step S102)
Next, in step S102, the CPU 21 determines whether the data storage unit 14 of the server device 10 can be accessed. Here, when the data storage unit 14 of the server device 10 is accessible (Yes in S102), the CPU 21 shifts the process to step S103. On the other hand, when the data storage unit 14 of the server device 10 can not be accessed (No in S102), the CPU 21 shifts the process to step S121.

(Step S121)
In step S121, the CPU 21 causes the display device 27 to display that the data storage unit 14 of the server device 10 can not be accessed. For example, it can be considered that the CPU 21 displays on the display device 27 that "the access can not be made because maintenance is currently in progress". Thereafter, the CPU 21 returns the process to step S101.

(Step S103)
On the other hand, in step S103, the CPU 21 displays a login screen on the display device 27 and waits for a login operation by the user (No in S103). Here, the CPU 21 is a user ID by the user operation on the operation input device 26.
When a password is input and user authentication is performed, it is determined that a login operation has been performed (Yes in S103), and the process proceeds to step S104. Note that various conventional techniques may be adopted as the method of the login operation.

(Step S104)
Then, in step S104, the CPU 21 causes the display device 26 to display a prescription selection screen D21 that displays a list of past prescriptions stored as the prescription history information in the data storage unit 24. Here, FIG. 6 shows an example of the prescription selection screen D21. In the prescription selection screen D21 shown in FIG. 6, a condition input unit D22 for setting a search condition for searching the prescription history information stored and stored in the data storage unit 24, and a search input to the condition input unit D22. A prescription list display section D23 is displayed in which the prescription history information extracted according to the conditions is displayed in a list. Further, on the prescription selection screen D21, a search key 211, a condition clear key 212, and an end key 213 are displayed. Then, when the search condition is set in the condition input unit D22 and the search key 211 is operated, the CPU 21 extracts the prescription history information stored in the data storage unit 24 according to the search condition. It is displayed on the prescription list display part D23. At this time, in the condition input unit D22, “patient name”, “refund ticket number”, “reception date”, “medical institution”, “medical department”, “final audit”, “incident”, “display order”, etc. Search conditions for can be entered. When the condition clear key 212 is operated, the CPU 21 initializes the search condition displayed on the condition input unit D22. When the end key 213 is operated, the CPU 21 closes the prescription selection screen D21 and ends the incident input process. The prescription history information matching the search condition among the prescription history information stored in the data storage unit 24 is displayed in a list on the prescription list display unit D23. At this time, in the prescription list display section D23, "reception date", "time", "refund ticket number", "patient ID", "patient name", "patient kana", "medical institution", "medical department" , “Final audit”, “Incident input” information is displayed. In particular, a newly created key 214 and a past incident key 215 are displayed in the “incident input” column. The past incident key 215 is displayed when there is an incident input in the past. Further, an audit key 216 is displayed in the "final audit" column.

(Steps S105 to S107)
Next, in steps S105 to S107, the CPU 21 waits for operation of any of the new creation key 214, the past incident key 215, and the audit key 216 displayed on the prescription list display unit D23 (S105 to S105). No side of S107). Here, when the CPU 21 determines that the new creation key 214 has been operated (Yes in S105), it determines that a new creation operation of an incident has been performed, and shifts the processing to step S151. When the CPU 21 determines that the past incident key 215 has been operated (Yes in S106), the CPU 21 determines that a past incident confirmation operation has been performed, and shifts the process to step S161. Furthermore, when the CPU 21 determines that the audit key 216 has been operated (Yes in S107), it determines that an audit start operation has been performed, and shifts the processing to step S171.

<New incident creation process>
(Steps S151 to S152)
In step S151, the CPU 21 causes the display device 27 to display an incident screen D31 for registering an incident regarding prescription history information corresponding to the new creation key 214 operated in the step S105. Then, in step S152, the CPU 21 executes an input process of inputting information of the incident on the incident screen D31 in accordance with the user operation of the operation input device 26 in accordance with the incident screen D31. Here, the operation input device 26 in the incident screen D31
An input process executed by the CPU 21 in accordance with the operation input of FIG.

  Here, FIG. 7 shows a display example of the incident screen D31. In the incident screen D31 shown in FIG. 7, a patient information display D32, a prescription information display D33, and an incident input D34 are displayed. That is, in each of the client terminals 20, the patient information display unit D32, the prescription information display unit D33, and the incident input unit D34 are displayed on the same screen of the display device 27. Thus, the user can edit the incident input unit D34 while referring to the display of the patient information display unit D32 and the prescription information display unit D33 displayed on the incident screen D31. In particular, the incident screen D31 is divided into two right and left, the patient information display D32 and the prescription information display D33 are displayed side by side on the left, and the incident input D34 is displayed on the right. ing. As described above, in the incident screen D31, items unnecessary to be input are summarized and displayed on the left, and items requiring input are summarized and displayed on the right. As a result, compared to the case where the display items in the patient information display unit D32, the prescription information display unit D33, and the incident input unit D34 are displayed without distinction, the items to be focused on by the user are input omissions of aggregation. It can be prevented.

  Specifically, patient information on the patient such as “patient ID”, “patient name”, “medical institution”, “medical department”, “reception date and time” is displayed on the patient information display unit D32. Further, on the prescription information display section D33, prescription information on prescription of a medicine such as "prescription medicine ID", "prescription medicine name", "usage", "dose" and the like is displayed. Here, based on the prescription history information stored in the data storage unit 24 of the client terminal 20, the CPU 21 selects "patient ID", "patient name", "medical institution", "medical department", "reception date and time" Are automatically extracted and displayed on the patient information display section D32. In addition, the CPU 21 automatically selects “prescribed medicine ID”, “prescribed medicine name”, “usage”, “dose” and the like from the prescription history information stored in the data storage unit 24 of the client terminal 20. It extracts and displays on the said prescription information display part D33. That is, the information (prescription information and patient information) on the left side of the incident screen D31 is content which is automatically read out from the data storage unit 24 by the CPU 21 and displayed. Here, the CPU 21 at the time of executing such read processing corresponds to the read control means.

  On the other hand, “incident occurrence date”, “party (pharmacist or the like)”, “occurrence location”, “discovery point”, “incident”, “level”, “prescription information”, “mistake” in the incident input unit D34. Input fields for entering information on incidents such as “Drugs”, “Failure contents”, “Causes of occurrence”, “Case contents / Causes”, “Solutions / Instructions” are displayed. Here, in the incident input section D34, the input fields of "incorrect content", "example content / cause", and "solution / instruction content" are input fields where any text can be input as necessary. However, information is input in the other input fields by numerical input or selection input. Specifically, "party (pharmacist, etc.)", "place of occurrence", "at the time of discovery", "incident", "level", "prescription information", "misplaced medicine", "mistaked content", "cause factor" “,” Information registered in advance as an option corresponding to each item in the incident master is selected and input by a user operation of the operation input device 26. Therefore, the information on the incident input to the incident input unit D34 has a structure in which statistical information can be easily obtained.

In particular, “content of incident” includes a group selection key 321 for selecting a group of incidents, and a content selection key 322 for selecting the content of an incident belonging to the group selected by the group selection key 321. It is input according to the operation. Specifically, when the group selection key 321 is operated, the CPU 21 displays a list of groups registered in the incident master by a pull-down menu. Then, the CPU 21 sets a group selected from the pull-down menu into a group input field 321.
Reflect on A. Next, when the content selection key 322 is operated, the CPU 21 lists only the content of the incident corresponding to the group selected by the group selection key 321 among the content of the incident registered in the incident master Display in the pull-down menu with. Then, the CPU 21 reflects the content of the incident selected from the pull-down menu in the content input field 322A (corresponding to the content input unit). Here, the group selection key 321 and the content selection key 322 are an example of the classification and selection unit. Furthermore, the CPU 21 extracts the level of the incident corresponding to the content of the incident from the incident master based on the content of the incident and the incident master, and outputs the level input field 323A (corresponding to the level input unit). To reflect. However, the CPU 21 changes the level of the incident reflected in the level input field 323A according to the content of the incident according to an arbitrary operation of the level selection key 323 by the user. Thereby, the level of the incident set in advance for each content of the incident can be arbitrarily changed at the time of the input of the incident, and the usability (usability) of the dispensing management system 1 is enhanced. Here, the CPU 21 at the time of executing such change processing corresponds to level change means.

Further, the incident input unit D34 includes an input unit D35 (corresponding to a target medicine input unit) for inputting a medicine that is an object of an incident and an input unit D36 for inputting a wrong medicine, and the content that is incorrect And an input unit D37 (corresponding to a description input unit) for inputting or displaying the description of the document in text. At this time, the CPU 21 refers to the incident occurrence information flag of “incident occurrence information” stored in the incident master corresponding to the content of the incident input in the content input field 322A. Then, the CPU 21 enables one or more of the input parts D35 to D37 to be input according to the contents of the incident occurrence information flag, and makes the other part impossible to input by gray out display or the like. For example, the CPU 21 determines whether or not the input parts D35 to D37 can be input based on the display switching information shown in FIG. In FIG. 8, “o” indicates that input can be performed, and “-” indicates that input can not be performed. For example, as shown in FIG. 8, when the incident occurrence information flag is "drug (mistake)", the input parts D35 and D36 can be input and the input part D37 can not be input. Further, when the incident occurrence information flag is "drug (dose error)", the input parts D35 and D37 can be input, and the input part D36 can not be input. As described above, since only the column that requires an input can be input according to the incident occurrence information flag, it is possible to easily make the user recognize a part that needs an input and to prevent an incorrect input of unnecessary information. be able to.

  Further, as shown in FIG. 8, in the display switching information, the format of the description input as the wrong content in the input unit D37 is set for each of the incident occurrence information flags. Then, the CPU 21 refers to the "mistaken content" stored in the display switching information corresponding to the content of the incident inputted in the content input column 322A, and the incident in the form of the "mistaken content" The description of the contents of the above is displayed on the input unit D37. When the incident occurrence information flag is "not specified", "drug", "patient error", "usage", "medical institution", "medical department", "comment", the CPU 21 selects the input unit D37. Show nothing on. For example, when the incident occurrence information flag is "drug (mistake)", the CPU 21 determines from the input information of the input unit D35 and the input unit D36, "pharmaceutical name of input unit D35 医 薬 品 medical product of input unit D36 The text of "name" is automatically generated and displayed on the input unit D37. Specifically, the content of the incident entered in the content entry column 322A is "drug taking error", the drug entered in the input unit D35 is "Actos lock", and the wrong drug entered in the input unit D36 is In the case of "eye troll lock", "actos lock ア イ eye troll lock" is displayed on the input section D37. In this case, since the user's input to the input unit D37 is unnecessary, the text is displayed in a grayed-out state of the input unit D37.

  On the other hand, when the group input in the group input field 321A is "weighing and weighing error" and the content of the incident input in the content input field 322A is "dose error", the incident occurrence information flag is " Drug (mistake in dose). In this case, the CPU 21 inputs a text to the input unit D37 according to the manual input operation of the operation input device 26 by the user. Specifically, the user inputs a description of the content of the incident to the operation input device 26 in the form of "prescribed dose + unit ← dispensing dose + unit". At this time, it is also conceivable that the CPU 21 displays below the input unit D 37 that the explanation of the contents of the incident should be input in the form of “prescribed dose + unit 調 剤 dispensing dose + unit”. Furthermore, when the group input in the group input field 321A is "weighing / weighing error", the input unit D37 corresponds to the case where the content of the incident is "dose error" or "normal dose error". It is possible to change the contents of the explanation which should be input to. Specifically, when the content of the incident is "drug (dose error)", the CPU 21 inputs the description of the content of the incident in the form of "prescribed dose + unit 調 剤 dispensing dose + unit" as described above. A message to the effect should be displayed below the input section D37. On the other hand, when the content of the incident is "drug (normal dose error)", the CPU 21 reads "prescribed dose + unit 調 剤 dispensing dose + unit [upper limit]", "prescribed dose + unit 調 剤 dispensing dose + unit [lower limit] ',' Prescribed dose + unit 形式 dispensing dose + unit [2.1 times excess] ',' prescribed dose + unit 調 剤 dispensing dose + unit [0.5 lack] ' It is conceivable to display a message to be input below the input section D37. This allows the user to distinguish and enter which of the upper limit, lower limit, more than 2.1 times, and less than 0.5 in the case of a common dose error of the drug. We can know that we should do it. When the description of the content of the incident is input according to the input rule set in this way, for example, “weighing and weighing error” is either a dose error or a normal dose error by referring to the description of the content of the incident. At a glance, it is possible to grasp at a glance whether there is a certain dose or the type of the usual dose error. In addition, for example, when the group inputted in the group input column 321A is “patient error”, the CPU 21 grays out all the input parts D35 to D37 to prohibit input. In this case, in response to the manual input operation of the operation input device 36 by the user, the CPU 21 inputs the content of the patient error by text in the input unit D38, input column 329A and input column 329B described later.

  By the way, as shown in FIG. 7, in the prescription information display section D33, the reflection operation key 320 is displayed corresponding to each of the plurality of medicines included in the prescription history information. Each of the reflection operation keys 320 is an example of a medicine selection unit operated to select a medicine to be input to the incident input unit D34 from the medicines displayed on the prescription information display unit D33. Then, when the reflection operation key 320 is operated, the CPU 21 reflects and displays the medicine name corresponding to the reflection operation key 320 in the “prescribed medicine” column of the input unit D35. Further, at this time, the CPU 21 is based on the medicine name corresponding to the reflection operation key 320 and the medicine master stored in the data storage unit 24, and the medicine code (CD) and medicine name corresponding to the medicine name, The YJ code is extracted and automatically displayed on the input unit D35. When the prescription drug selection key 324 is operated in the input unit D35, the CPU 21 displays a list of medicines displayed on the prescription information display unit D33 by a pull-down menu. Then, when a medicine is selected from the pull-down menu, the CPU 21 reflects the information on the medicine on the input unit D35. As described above, in the client terminal 20, the medicine selected from the medicines displayed on the prescription information display unit D33 by the operation of either the reflection operation key 320 or the prescription medicine selection key 324 is targeted for the incident It is selected. Therefore, it is prevented that the medical supplies which are not displayed on the said prescription information display part D33 are accidentally input as an object of an incident.

When the wrong medicine selection key 325 is operated in the input unit D 36, the CPU 21 displays a medicine list screen D 41 of medicines registered in the medicine master stored in the data storage unit 24. Here, FIG. 9 is a view showing a display example of the medicine list screen D41. In the medicine list screen D41 shown in FIG. 9, the medicine code and medicine name of the medicine registered in the medicine master are displayed in a list. When an arbitrary medicine name is selected on the medicine list screen D41 and the OK key 411 is operated, the CPU 21 reflects the selected medicine name on the input unit D36. Further, at this time, the CPU 21 selects a medicine code (CD) corresponding to the medicine based on the medicine name selected by the wrong medicine selection key 325 and the medicine master stored in the data storage unit 24. , And YJ codes are automatically displayed on the input unit D36. When the cancel key 412 is operated in the medicine list screen D41, the CPU 21 cancels the selection of medicines and closes the medicine list screen D41. By the way, when the check box “unregistered medicine” is checked in the input unit D 36, the CPU 21 disables the operation of the wrong medicine selection key 325. The check box is used when the wrong medicine is not registered in the pharmaceutical master. In this case, the CPU 21 grays out the input unit D36, and the input unit D37 displays the input unit D35. Display “Pharmaceutical Name 未 Unregistered Drug”. In addition, the structure which can arbitrarily input the name etc. of the said unregistered medicine in the said input part D36 or the said input part D37 is also considered as another embodiment.

  Further, when the occurrence factor key 326 displayed in the incident input unit D34 is operated, the CPU 21 lists the occurrence factors set in advance corresponding to the content of the incident entered in the content entry column 322A. Is displayed in the pull-down menu. As the cause of the occurrence, for example, “insufficient confirmation”, “inappropriate judgment”, “for busy”, and the like can be considered. Then, when an occurrence factor is selected from the pull-down menu, the CPU 21 reflects the occurrence factor in the occurrence factor column 326A. Thereafter, when the additional key 327 is operated, the CPU 21 causes the occurrence factor input unit D38 to reflect the occurrence factor input in the occurrence factor column 326A. At this time, it is possible to input a plurality of occurrence factors to the occurrence factor input unit D38. The occurrence factor input to the occurrence factor input unit D38 is deleted by the CPU 21 by the operation of the deletion key 328.

  Furthermore, the CPU 21 causes the cursor to be displayed in the “case content / cause” input column 329A or the “solution / instruction content” input column 329B displayed in the incident input unit D34 by the user operation of the operation input device 26. When moved, the text is input in the input field 329A or the input field 329B in accordance with any subsequent text input operation. The input field 329A is an area where the details of the case of the incident and the details of the cause, etc. are arbitrarily described. Further, the input field 329B is an area in which a solution or instruction content performed after the occurrence of the incident is arbitrarily described.

At the lower end of the incident screen D31, a registration key 311, a new creation key 312, a past report key 313, a feed key 314, 315, a delete key 316, a preview key 317, a clear key 318, a back key 319, etc. Operation keys are displayed. When the operation keys are operated, the CPU 21 executes a predetermined check process and then executes a process corresponding to the operation keys. For example, in the check process, it is checked whether or not it is within the system data storage period as follows, whether or not it has been deleted, and the like. Specifically, if the reception date displayed on the patient information display section D32 is less than the number of months of dispensing system data storage preset in the dispensing management system 1 than the current date, the CPU 21 receives “already received”. The date is below the system restriction, and a message such as “Return to prescription selection screen” is displayed on the display unit 26, and then the prescription selection screen D21 is displayed on the display unit 26. In addition, when the prescription information displayed in the prescription information display section D33 has already been deleted, the CPU 21 displays a message such as "The information on the incident has already been deleted. It returns to the prescription selection screen." After being displayed on the display device 26, the prescription selection screen D21 is displayed on the display device 26. Furthermore, when information on the same incident as the information on the incident and the identification information such as the sequence number displayed on the incident input unit D34 has been deleted, the CPU 21 “The information on the incident has already been deleted. Prescription After a message such as “Return to selection screen” is displayed on the display device 26, the prescription selection screen D21 is displayed on the display device 26. In addition, when the information on the destination of the move destination has already been deleted when the feed key 314 or 315 is operated, the CPU 21 returns to the “prescription selection screen,“ The information on the incident has already been deleted. And the like are displayed on the display unit 26, and then the prescription selection screen D21 is displayed on the display unit 26.

  Then, when the registration key 311 is operated, the CPU 21 determines the editing content of the incident input unit D34 as information of an incident and stores the information in the RAM 23 or the like. The information on the incident is transmitted to the server device 10 in step S154 described later. However, if the information of the incident being edited by the incident input unit D34 is updated by another client terminal 20 after the information of the incident being edited by the incident input unit D34 is started by the other client terminal 20, the fact is displayed The exclusive control processing to be displayed on the device 26 is executed. Further, the CPU 21 checks whether the information of the incident input to the incident input unit D 34 violates the preset prohibition content, and if there is an error, the display device Display on 26 For example, when the date and time before the “reception date and time” displayed on the patient information display unit D32 is input in the “incident occurrence date and time”, the CPU 21 determines that there is an error against the content of the prohibition. On the other hand, when there is no error in the information on the incident, the CPU 21 determines the information on the incident input to the incident input unit D34 and records the information on the RAM 23 or the like.

On the other hand, when the new creation key 312 is operated, the CPU 21 initializes the editing content of the incident input unit D34. When the past report key 313 is operated, the CPU 21 switches the information of the incident displayed on the incident screen D31 to the information of the oldest incident. Furthermore, when the feed key 314, 315 is operated, the CPU 21 sequentially switches the information of the incident displayed on the incident screen D31 to the new and old information. The feed key 314 is hidden when displaying the information of the oldest incident, and the feed key 315 is hidden when displaying the information of the latest incident.

  Further, when the delete key 316 is operated, the CPU 21 deletes the information of the incident displayed on the incident screen D31 from the data storage unit 14 of the server device 10. However, in this case, before the CPU 21 deletes the information of the incident, for example, a message for reconfirming the deletion, such as "Delete. Are you sure?" It is displayed on the display device 26 together with the operation parts of “OK” and “cancel”. Then, after the display of the message, the CPU 21 deletes the information of the incident on the condition that the operation unit “OK” is operated. The delete key 316 is displayed only when information on past incidents is displayed according to the operation of the past report key 313.

In addition, when the preview key 317 is operated, the CPU 21 displays a preview screen in the case where the information on the incident displayed on the incident screen D31 is printed. For example, the human incident details shown in FIG. 10 are displayed on the preview screen. The CPU 21 closes the preview screen in response to the operation of the return key displayed on the preview screen and causes the display 26 to display the incident screen D31. When the clear key 318 is operated, the CPU 21 initializes the information of the incident displayed on the incident screen D31. The clear key 318 is displayed only when new registration of information on an incident is performed. When the return key 319 is operated, the CPU 21 returns the display screen of the display unit 26 to the screen displayed one before the incident screen D31. For example, after the transition from the prescription selection screen D21 to the incident screen D31, the CPU 21 causes the display device 26 to display the prescription selection screen D21 when the return key 319 is operated. Further, after the transition from the audit screen D51 (see FIG. 11) described later to the incident screen D31, the CPU 21 causes the display device 26 to display the audit screen D51 when the return key 319 is operated. .

(Step S153)
Then, in step S153, the CPU 21 determines whether or not the registration operation of the information of the incident input in the step S152 is performed according to the presence or absence of the operation of the registration key 311. Here, when the CPU 21 determines that the registration key 311 is operated (Yes in S153), the CPU 21 shifts the process to step S154. On the other hand, until the registration key 311 is operated (No in S153), the CPU 21 returns the process to the step S152 and continues the input process of the information of the incident according to the incident screen D31. .

(Step S154)
In step S154, the CPU 21 transmits the information on the incident input to the incident input unit D34 in step S152 to the server device 10 via the communication interface 25. Thereby, when the information on the incident is transmitted to the server device 10, the CPU 11 in the server device 10 stores and stores the information on the incident in the data storage unit 14. Therefore, in the dispensing information management system 1, the information on the incidents input in each of the client terminals 20 is collected in the server device 10. Here, the CPU 21 when storing the incident information in the data storage unit 14 by executing the transmission process corresponds to a storage control unit. The data storage unit 14 is an example of an incident information storage unit. The incident information storage unit may be a Web server provided on a network accessible from the server device 10, the client terminal 20, or the management terminal 30. Here, FIG. 10 shows an example of the information of the incident transmitted to the server device 10. As shown in FIG. It is also conceivable that the CPU 21 transmits the information of the incident transmitted to the server device 10 to the printer (not shown) in the step S153, and causes the printer to print the information of the incident as a form. By the way, in step S154, the CPU 21 transmits only the incident information to the server device 10 and stores the information in the data storage unit 14, and transmits the prescription information and the patient information to the server device 10. I did not. Therefore, the prescription information and the patient information are not stored in the data storage unit 14 of the server device 10, but are included in the prescription information and the patient information from information processing devices such as the plurality of management terminals 30. Because personal information can not be referenced, patient's personal information is protected.

On the other hand, in the step S154, the CPU 21 transmits the incident information and either the prescription information corresponding to the incident information or the patient information or the patient information to the server apparatus 10 in association with each other. Can be considered as an embodiment of As a result, the information on the incident is stored in the data storage unit 14 in a state associated with either or both of the prescription information and the patient information that are targets for which the incident has occurred. Therefore, when an information processing apparatus such as the management terminal 30 performs display output, print output, data output, etc. of the information of the incident stored in the data storage unit 14, the incident is a target that has occurred. It is possible to simultaneously output either or both of the prescription information and the patient information. For example, when displaying and outputting the incident information on a display device, one or both of the prescription information and the patient information corresponding to the incident information may be simultaneously displayed, or the prescription information corresponding to the incident information It is conceivable to display a link button for displaying one or both of the patient information and the like. In the latter case, when the link button is operated, the information processing apparatus reads out one or both of the prescription information and the patient information corresponding to the incident information from the data storage unit 14 and displays the information Display on the device. In addition, also when referring to either or both of the prescription information and the patient information, it is also possible to easily grasp the information of the incident corresponding to the prescription information or the patient information. However, when the prescription information and the patient information and the like are stored in the data storage unit 14 of the server device 10 together with the incident information, the prescription information and the patient information can be obtained from the information processing device such as the management terminal 30. The personal information of the included patient can be referred to. Therefore, in the dispensing information management system 1, it is desirable that the authority to refer to the prescription information and the patient information stored in the data storage unit 14 can be set in advance. Thus, it is possible to protect the patient's personal information by limiting the users who can refer to the prescription information and the patient information. More specifically, in the dispensing information management system 1, it is conceivable that the CPU 11 of the server device 10 executes an access control process for controlling an access right to the data storage unit 14. In the access control process, the CPU 11 specifies a user who has logged in at the management terminal 30 to refer to the incident information from the information processing apparatus such as the management terminal 30 to the data storage unit 14. Then, the CPU 11 permits the reference of the prescription information and the patient information in addition to the incident information only when the logged-in user is a limited user such as a preset administrator. On the other hand, when the user's authority is not a limited user such as a manager, the CPU 11 can refer only to the incident information and prohibits reference to the prescription information and the patient information. If the prescription information does not include the patient's personal information, the CPU 11 permits the reference to the prescription information when the user is not a limited user such as a manager, and prohibits only the reference to the patient information. It is also conceivable.

<Confirmation process of past incident>
(Steps S161 to S162)
On the other hand, as described above, when the past incident key 215 is operated on the prescription selection screen D21 (Yes in S106), the CPU 21 shifts the process to step S161. In step S161, the CPU 21 performs, similarly to the incident screen D31 (see FIG. 7), information on past incidents already registered for the prescription history information on which the past incident key 215 operated in the step S107 is displayed. The display 27 is displayed on the screen of Of course, the information on the past incident may be displayed on a reference screen different from the incident screen D31. Thereafter, in step S162, the CPU 21 determines whether or not confirmation of information on past incidents has ended, according to the presence or absence of the operation of the return key 319 displayed on the incident screen D31. Here, when it is determined that the return key 319 has been operated and confirmation of the information on the past incident has been completed (Yes in S162), the processing is shifted to the step S104, and the prescription selection screen D21 is displayed on the display device 26. Display on. On the other hand, the CPU 21 returns the process to the step S161 until the return key 319 is operated (No in S162).

<Audit processing>
(Steps S171 to S174)
Further, as described above, when the audit key 216 is operated on the prescription selection screen D21 (Yes in S107), the CPU 21 shifts the process to step S171. In step S171, the CPU 21 causes the display device 27 to display an audit screen D51 for performing an audit on the prescription of the medicine displayed in the prescription history information on which the audit key 214 operated in the step S107 is displayed. Display. Here, FIG. 11 is a view showing a display example of the audit screen D51. In the audit screen D51 shown in FIG. 11, the patient information display unit D32 and the prescription information display unit D33 are displayed in the same manner as the incident screen D31, and instead of the incident input unit D34, an audit completion operation is performed. The audit input section D52 of is displayed.

  Further, at the lower end portion of the audit screen D51, an incident input key 511 and a return key 512 for starting input of information on an incident are displayed. Here, when the incident input key 511 is operated, the CPU 21 determines that an incident creation operation has been performed (Yes in S172), and shifts the process to the step S151. Thereby, the CPU 21 changes the display screen of the display device 26 from the audit screen D51 to the incident screen D31. When the return key 512 is operated, the CPU 21 returns the display screen of the display unit 26 to the display screen displayed before the audit screen D51 is displayed.

  On the other hand, the audit input section D52 displays a selection input section 513 for selecting and inputting an audit pharmacist in charge of the audit, and an audit completion key 514 for completing the audit. Here, when the selection input unit 513 is operated, the CPU 21 displays a list of pharmacists registered in advance, and reflects a pharmacist selected from among the pharmacists in an input field of “audit pharmacist”. For example, the pharmacists displayed at this time are only pharmacists registered as pharmacists belonging to the pharmacy or the like in which the client terminal 20 is installed in the pharmacy master of the data storage unit 14. When the audit completion key 514 is operated, the CPU 21 determines that an audit completion operation has been performed (Yes in step S173), and the prescription history information stored in the data storage unit 24 is stored in the CPU 21. The fact that the inspection of the prescription information displayed on the prescription information display section D33 is completed and the audit pharmacist selected by the selection input section 511 are registered (S174). Thereafter, the CPU 21 shifts the process to step S4.

Incident statistics output processing
Next, an example of the procedure of the incident statistics output process executed by the CPU 11 of the server device 10 and the CPU 21 of the client terminal 20 will be described with reference to the flowchart of FIG. In the dispensing information management system 1, the incident statistics output process is executed by the CPU 11 of the server device 10 and the CPU 21 of the client terminal 20, whereby the display device 27 of the client terminal 20 stores and stores the data in the server device 10. Statistics of the logged incidents are displayed. Here, a case where statistical information of the incident is displayed on the client terminal 20 will be described as an example, but the incident is similarly applied to the management terminal 30 and the like communicably connected to the server device 10. You can view statistical information of In this case, in the management terminal 30, the same processing steps as the following processing steps executed by the client terminal 20 are executed by the control unit such as a CPU. Of course, in the server device 10, the CPU 11 can also display statistical information of the incident on the display device 17.

(Steps S201 to S204: Client terminal 20 side)
First, in the client terminal 20, the CPU 21 waits for an operation to start display of statistical information of an incident in step S201 (No in S201). Here, when it is determined that the display operation of the statistical information of the incident has been performed (Yes in S201), the CPU 21 shifts the process to step S202. For example, after the CPU 21 executes the dispensing information management program to display an initial screen on the display device 27, when an operation key for requesting display of statistical information of an incident is selected (S201 Yes), the process proceeds to step S202. In step S202, the CPU 21 executes a process for setting statistical display conditions when displaying statistical information of the incident. Specifically, the CPU 21 sets the statistical display condition in accordance with the operation of the operation input device 26. The said statistics display conditions define items, such as a store made into calculation object of statistical information on an incident, a group, a group division, a dispensing device, a pharmacist, for example. Next, in step S203, the CPU 21 transmits, to the server apparatus 10, a display request for statistical information of incidents along with the statistical display condition set in step S202. Here, the CPU 21 at the time of inputting the statistical display condition into the server device 10 by executing the processing of the steps S202 to S203 corresponds to a statistical display condition input means. Then, the CPU 21 waits for the reception of the statistical information of the incident (No in S204).

(Steps S301 to S303: server device 10 side)
On the other hand, in the server device 10, the CPU 11 waits for a display request for statistical information of an incident in step S301 (No in S301). Here, if it is determined that the display request for the statistical information of the incident has been received (Yes in S301), the CPU 11 shifts the processing to step S302. Note that, in the step S301, the CPU 11 is considered to execute the login process of the user by the client terminal 20. Here, the CPU 11 at the time of authenticating a user by such login processing corresponds to a user authentication means.

  In step S302, the CPU 11 calculates statistical information of the incident stored in the data storage unit 14 in accordance with the statistical display condition corresponding to the display request received in step S301. When the CPU 11 receives the information on the incident from each of the client terminals 20 instead of the step S302, the information on the incident is sequentially reflected in various statistical information stored in the data storage unit 14. By doing this, it is possible to always update the statistical information to the latest statistical information. Further, it is also conceivable that the CPU 11 automatically sets or changes a part of the display condition in accordance with the login user who has requested the display of the statistical information of the incident. For example, search area information in which an area and a prefecture corresponding to each person in charge are predetermined is stored in the data storage unit 14, and the CPU 11 stores an area and a prefecture corresponding to the person currently in charge. It is conceivable to extract from the search area information and set the area and prefectures as calculation targets of statistical information. The content of the search area information is set and changed by the CPU 21 of the client terminal 20 according to the operation of the operation input device 26.

Then, in step S303, the CPU 11 transmits, to the client terminal 20, the statistical information of the incident calculated in the step S303 or the statistical information of the incident calculated and stored in the data storage unit 14 in advance. . Here, the CPU 11 at the time of transmitting the statistical information of the incident to the client terminal 20 by executing the steps S302 to S303 corresponds to statistical information output means. However, the CPU 11 changes the output content of the statistical information in the steps S302 to S303 in accordance with the user authenticated by the login process performed in the step S301. For example, it is possible to limit the area that can be referred to as statistical information for each user. In addition, the user may refer to the total for each shop about pharmacist incidents, but may impose a restriction that the statistics on the incidents for each pharmacist can not be referred to. In this case, the data storage unit 14 prestores authority information on the contents of the statistical information that can be displayed for each user. Then, the CPU 11 changes the output content of the statistical information based on the user specified by the user authentication executed in the step S301 or the like and the authority information. When the CPU 11 displays a plurality of items of the statistical information as a tree as a method of restricting the display, it is conceivable that the CPU 11 does not display the item to which the display restriction is imposed.

(Steps S204 to S205: server device 10 side)
When statistical information of the incident is transmitted from the server device 10 to the client terminal 20, the client terminal 20 determines that the CPU 21 has received the statistical information of the incident (Yes in S204), The process proceeds to step S205. In step S205, the CPU 21 causes the display device 27 to display the statistical information of the incident received in step S204. At this time, the statistical information of the incident displayed on the display device 27 conforms to the statistical display condition set in the step S202. Further, even after the statistical information of the incident is displayed, the CPU 21 changes the display condition set in the step S202 in accordance with the operation of the operation input device 26, and transmits that effect to the server device 10 By doing this, the display of the display device 27 is updated according to the statistical information of the incident received from the server device 10 thereafter.

  Here, with reference to FIGS. 13 to 15, an example of setting of the statistic display condition (the step S202) and display of the statistic information of the incident (the step S205) in the incident statistic output process (see FIG. 12) Will be explained. First, a method will be described when the CPU 21 sets a statistical display condition for determining a calculation target of statistical information of the incident in the step S202. As shown in FIG. 13A, in the step S202, an input screen of statistical display conditions is displayed on the display device 27 of the client terminal 20. Specifically, the CPU 21 receives information on the input screen of the statistical display condition from the server device 10, and causes the display device 27 to display the information. On the input screen shown in FIG. 13A, various conditions such as “search area”, “store”, “device”, and “display order” can be set as the statistical display condition, but these are merely examples. Items such as "date and time" and "person in charge" can also be set. For example, as shown in FIG. 13 (B), a configuration is conceivable in which the type of contents of a dispensing device or an incident can be set as the statistical display condition on the statistical display condition input screen. Then, when the statistical display condition is input and a search start operation is performed, the CPU 21 transmits the statistical display condition to the server device 10 (S203). Thereby, in the server device 10, the CPU 11 executes a search according to the statistical display condition, and transmits the execution result to the client terminal 20 (S303). Then, the CPU 21 of the client terminal 20 causes the display device 27 to display the search result received from the server device 10 (S205). Here, FIGS. 13C to 13H are examples of title names of statistical information displayed at the top when the statistical information of the incident is displayed as the search result. As shown in FIG. 13C, if the target specified by the statistical display condition is one store, the store name “Akashi shop” is displayed, and as shown in FIG. 13D, it is specified by the statistical display condition If the target is more than one store, the store names “Akashi store”, “Kobe store”, and “Sannomiya store” are listed in a row. Similarly, as shown in FIG. 13E, if the target specified by the statistical display condition is one category, the category “prefecture” and the number of stores included in the category are displayed, and FIG. 13F is displayed. As shown, if the target specified by the statistical display condition is one group, the group “Hyogo prefecture” and the number of stores included in the group are displayed. When a plurality of categories, groups, and stores are specified as the statistical display condition, as shown in FIG. 13G, the plurality of categories and number of stores, the number of groups and stores, and stores are respectively searched. Is displayed. When the number of displayed characters exceeds the predetermined number of characters, characters after the predetermined number of characters are omitted as shown in FIG. 13H, and the total number of stores is displayed.

Subsequently, a display example of statistical information of the incident will be described. Here, FIG. 14A shows an example of the pharmacy master, and FIGS. 14B to 14D show display examples of statistical information of the incident. Here, as shown in FIG. 14A, in the data storage unit 14 of the server device 10, as the pharmacy master, “A store”, “B store”, “C store”, “C store”,
It is assumed that four client terminals 20 installed in each of D stores are registered. Also, in the pharmacy master, it is preset that “A store” and “B store” belong to “AA group”, “C store” belongs to “CC group”, and “D store” belongs to “DD group” respectively. It is assumed that Furthermore, in the pharmacy master, it is assumed that "AA group" and "CC group" belong to "AAA classification", and "DD group" belongs to "DDD classification" in advance. Here, a store, a group, and a classification are examples of the classification unit of each of the client terminals. For example, the division is an area name such as "Kansai" or "Kanto", and the group is a name of a prefecture such as "Osaka" or "Hyogo". Further, the CPU 21 has a function of arbitrarily setting a classification unit such as a store, a group, or a classification to which the client terminal 20 belongs. Specifically, the setting of the classification unit is executed by the CPU 21 displaying the initial setting screen of the dispensing information management program and in accordance with the operation input of the operation input device 26 performed according to the initial setting display screen. Here, the CPU 21 when implementing such a function corresponds to classification unit setting means.

  And as shown to FIG. 14 (B), when the check box of a group division and a group is not checked, in the said server apparatus 10, said CPU11 calculates the statistical information of the incident for every shop. As a result, as shown in FIG. 14B, the client terminal 20 displays statistical information of incidents for each store. In FIG. 14 (B), “prescription number” indicates the number of prescriptions (prescription data). “Level” indicates statistical information for each of the incident levels “S”, “A”, “B”, “C”, and “D”. Here, “NG” indicates the number of occurrences of incidents at the corresponding level, and “%” indicates the ratio of the number of occurrences of incidents at the corresponding level to the number of prescriptions (= NG number / prescription number). Furthermore, “incident content” indicates statistical information for each incident content such as “drug taking error”, “patient error” and the like. Here, "OK" is the number of normal processes counted in the unit where the corresponding incident content occurs, "NG" is the number of incident occurrences counted in the unit where the corresponding incident content occurs, "%" is the incident in the corresponding incident content The ratio of the number of occurrences (= number of NG / (number of OK + number of NG)) is shown. Specifically, the CPU 11 counts the number of "OK" and the number of "NG" per pharmaceutical unit if the occurrence of the incident occurs per pharmaceutical unit as in the case where the content of the incident is "incorrect medicine taking". Do. Further, the CPU 11 counts the number of “OK” and the number of “NG” in units of prescription when occurrence of the incident occurs in units of prescription as in the case where the content of the incident is “patient error”. Furthermore, the CPU 11 does not count as the number of “OK” and “NG” when the incident occurs regardless of either the medicine or the prescription as in the case where the content of the incident is “filling drug error”. . As described above, by previously setting the counting method of the number of incidents for each content of the incident, it is possible to obtain effective statistical information obtained by counting the number of incidents in an appropriate unit. On the other hand, for example, if the number of incidents is counted on a drug basis for all incident contents, if an incident that occurs on a prescription basis such as “patient error” occurs, the number of incidents is the same as the number of medicines included in the prescription. Since it is reflected in statistical information that it occurred, it deviates from the number of incidents that should be managed originally, and it is not possible to obtain effective statistical information.

Further, as shown in FIG. 14C, when the check box of the group is checked, in the server device 10, the CPU 11 calculates statistical information of the incident for each group. As a result, as shown in FIG. 14C, the client terminal 20 displays statistical information of incidents for each group. Furthermore, as shown in FIG. 14D, when the check box of the group division is checked, in the server device 10, the CPU 11 calculates statistical information of incidents for each group division. As a result, as shown in FIG. 14 (D), the client terminal 20 displays the statistical information of the incident for each group division. Therefore, even after displaying the statistical information of the incident, the user confirms desired statistical information by the display of the display device 27 by arbitrarily changing the statistical display condition of the incident using the check box. be able to. That is, the range which the user does not want can be excluded from the statistical information displayed on the display device 27.

  Various conditions can be considered as the statistical display condition set in step S202. For example, it is conceivable that the statistical display condition is display of statistical information of an incident for each pharmacist. In this case, in the setting of the incident master (see FIG. 4), only the number of incident categories for which the pharmacist incident flag is ON is calculated as statistical information. In addition, it is also conceivable that the statistical display condition is display of statistical information of an incident for each designated year, month, week, day, day of the week, or time. Here, FIG. 15 shows an example of the statistical display. Specifically, FIG. 15 (A) is a display example when the monthly statistical display condition is selected, FIG. 15 (B) is a display example when the weekly statistical display condition is selected, FIG. C) shows a display example when the daily statistics display condition is selected. In the case where the daily statistics display condition is selected and the specified range of dates does not overlap and the day of the week can be identified, the date as shown in FIG. It is also conceivable to add the day of the week to the display. Further, FIG. 15 (E) shows a display example when the statistical display condition for each day of the week is selected, and FIG. 15 (F) shows a display example when the statistical display condition according to time is selected. As a result, for example, which day of the week or which time the incident is likely to occur can be easily confirmed, and can be effectively used as a determination index such as the introduction of the dispensing device or the increase in the number of personnel. Further, as shown in FIG. 15 (G), it is conceivable that the time to be displayed can be selected in advance when the statistical information of the incident is displayed by time. Specifically, as shown in FIG. 15 (G), the CPU 11 sets only the time selected (checked) by the check box in the state where the hourly selection is selected as the statistic display condition as the calculation object of the statistical information. Do. Furthermore, it is also conceivable that the statistical display condition is display of statistical information of incidents for each of the designated types of incidents. For example, by specifying the type of the dispensing device in which an incident occurs, statistical information can be obtained only for incidents that may occur in the specified type of the dispensing device. In addition, it is desirable that designation | designated of the classification of the said incident can designate one or multiple simultaneously. In addition, displaying only incidents pointed out by patients is also considered as an example of the statistical display condition. As a result, it is possible to grasp information such as errors that are likely to be undetectable by the pharmacist and the inspector.

[Other features]
Hereinafter, other functions embodied in the dispensing information management system 1 will be described.

[Device information acquisition function]
In the server device 10, the CPU 11 acquires information on the dispensing devices connected to the client terminal 20 from each of the client terminals 20 in order to manage the dispensing devices connected to each of the client terminals 20. And store in the data storage unit 14 as the pharmacy master. Specifically, in each of the client terminals 20, the CPU 21 broadcasts to each of the dispensing devices connected to the client terminal 20 at predetermined time intervals. Thereby, when the dispensing device in operation is connected to the client terminal 20, the dispensing device transmits the device information of itself to the client terminal 20. The device information includes, for example, information such as device name, dispensing device type, system version, IP address, MAC address and the like. Note that each of the dispensing devices may automatically transmit the device information to the client terminal 20 when activated.

  Then, in the client terminal 20, the CPU 21 transmits the device information of each of the dispensing devices to the server device 10 at predetermined time intervals. Thereby, in the server device 10, the CPU 11 acquires the device information of the dispensing device connected to each of the client terminals 20, and the device connection table in which the device information is associated with the client terminal 20 is obtained. It is stored as the pharmacy master of the data storage unit 14. Further, in the server device 10, the CPU 11 is not connected for a preset period (for example, about 3 days) among the dispensing devices connected to each of the client terminals 20 stored in the data storage unit 14. As for the dispensing device, an automatic deletion process is performed to delete the device information from the device connection table. Thereby, the information on the dispensing device separated from the client terminal 20 and the dispensing device not used for a long time is deleted from the device connection table as unnecessary information.

  However, in the server device 10, the CPU 11 uses the information on the use start time and the use end time of each dispensing device as connection history information separately from the device connection table stored in the data storage unit 14. It is stored in the storage unit 14. Thereby, by referring to the connection history information, it becomes possible to confirm the use start time and the use end time of each of the dispensing devices afterward. Therefore, for example, in a pharmacy or the like in which the dispensing device is installed, it is possible to confirm increase or decrease in the number of occurrences and frequency of occurrence of incidents in a period in which the dispensing device is used and a period in which the dispensing device is not used. Become. Specifically, if the number of incidents decreases after the introduction of the specific dispensing device and the number of incidents increases after the dispensation of the dispensing device, it is possible to grasp the effect of the incident reduction due to the introduction of the dispensing device. .

[Automatic version upgrade function]
Further, as described above, in the configuration in which the device information of each of the dispensing devices connected to each of the client terminals 20 is stored in the pharmacy master of the data storage unit 14 of the server device 10, the server device 10 It is conceivable that the CPU 11 manages the software version of each of the dispensing devices.

  Specifically, the CPU 11 stores, for example, the latest software version of each of the dispensing devices input by the operation input device 16 in the data storage unit 14. Then, the CPU 11 compares the latest software version stored in the data storage unit 14 with the software version included in the device information of each of the dispensing devices. Then, when there is a dispensing device whose software version is not the latest software version in each of the dispensing devices, the CPU 11 notifies the client terminal 20 to which the dispensing device is connected to that effect. It is possible to do. This can prompt the user to update the version of the software of each of the dispensing devices connected to the client terminal 20.

  The CPU 11 may also transmit a control instruction for updating the version of the software of the dispensing device to the latest one, to the client terminal 20 to which the dispensing device is connected, the version of the software being not the latest. Conceivable. That is, it is conceivable to automatically update the software of the dispensing device connected to each of the client terminals 20 by the server device 10. Thereby, in the client terminal 20, the CPU 21 updates the version of the software of the dispensing device to the latest one in accordance with the control instruction. For example, in the client terminal 20, the CPU 21 downloads the software of the latest version of the dispensing device from the server device 10 or the like, and transmits the software to the dispensing device to cause the dispensing device to update the software.

[Waiting time management function]
In the server device 10, the CPU 11 performs dispensing operation in each of the client terminals 20 from the client terminal 20 in order to manage the waiting time of the patient in the pharmacy or the like in which each of the client terminals 20 is installed. Get the required time for each process of Specifically, the waiting time of the patient is the time from when the prescription is received at the pharmacy or the like until the medicine is delivered to the patient. Here, FIG. 16 shows an example of the flow of the dispensing operation time in the pharmacy or the like in which the client terminal 20 is installed. The CPU 21 of the client terminal 20 acquires times T11 to T17 shown below and stores them in the data storage unit 24 and transmits the times T11 to T17 to the server device 10.

(Time T11)
As shown in FIG. 16, time T11 is the time from receipt of the prescription data by the receipt terminal 51 installed in the pharmacy etc. to completion of the receipt of prescription data and being inputted to the client terminal 20. . The CPU 21 of the client terminal 20 acquires the reception time of the reception terminal 51 from the reception terminal 51. Then, the CPU 21 calculates the time T11 based on the reception time of the reception terminal 51 and the time when prescription data is input to the client terminal 20.

(Time T12)
Further, a time T12 for generating dispensing data for transmitting the prescription data to each of the dispensing devices in the client terminal 20 is counted by the CPU 21 in the client terminal 20.

(Time T13)
Furthermore, a time T13 from when dispensing data is input from the client terminal 20 to dispensing devices such as the tablet dispensing device 52, the powder dispensing device 53, the picking assistance device 53, etc. until dispensing is completed is the dispensing device. It is clocked and input from the dispensing device to the client terminal 20. At this time, the CPU 21 calculates the time T13 based on the time when the dispensing data is first input among the dispensing devices and the dispensing completion time of the dispensing device the dispensing of which is the last completed among the dispensing devices. Do.

(Time T14)
Thereafter, the time T14 from the completion of dispensing in each of the dispensing devices to the start of the final audit for that dispensing is the final inspection of the dispensing from the dispensing completion time in the dispensing device of the last dispensing of each of the dispensing devices. It is the time until the auditor performs a final audit start operation on an information processing apparatus such as a personal computer for inputting the result. Here, the audit start time at which the final audit start operation is performed in the information processing apparatus is input from the information processing apparatus to the client terminal 20. Thereby, in the client terminal 20, the CPU 21 performs the time based on the dispensing completion time of the dispensing device that has completed dispensing among the dispensing devices and the inspection start time input from the information processing apparatus. Calculate T14.

(Time T15)
Next, from time T15 from the start of the final audit to the end of the final audit, from the time the auditor performs the operation of starting the final audit on the information processing apparatus to the operation of the end of the final audit It's time. The time T15 is counted by the information processing apparatus, and is transmitted from the information processing apparatus to the client terminal 20. Note that the audit end time at which the final audit end operation is performed is transmitted from the information processing apparatus to the client terminal 20, so that the CPU 21 executes the audit start time and the audit end time in the client terminal 20. It is also conceivable to calculate the time T15 on the basis of.

(Time T16)
The time T16 from the final audit end time to the start of medication instruction to the patient is from the final audit end time to medication instruction by the medication instructor to an information processing apparatus such as a personal computer for inputting the start of medication instruction. It is the time until the start operation is performed. Here, the medication instruction start time at which the operation of the medication instruction start is performed in the information processing apparatus is input from the information processing apparatus to the client terminal 20. Thus, in the client terminal 20, the CPU 21 calculates the time T16 based on the final audit end time and the medication instruction start time input from the information processing apparatus.

(Time T17)
Finally, during the time T17 from when the medication instruction start time to the end of the medication instruction, the time from when the medication instructor performs the operation of the medication instruction start to the information processing apparatus until the operation of the medication instruction end is performed. It is. The time T17 is counted by the information processing apparatus, and transmitted from the information processing apparatus to the client terminal 20. The CPU 21 can transmit the medication instruction start time and the medication instruction start time at the client terminal 20 by transmitting from the information processing apparatus to the client terminal 20 the medication instruction end time at which the medication instruction termination operation has been performed. It is also conceivable to calculate the time T17 based on the end time. Moreover, the said medication completion time is not restricted to the time when operation of the medication instruction completion with respect to the said information processing apparatus was performed. For example, when a moving image or an image obtained by photographing a condition for handing over medicine to a patient after the administration instruction is input to the client terminal 20 together with the imaging time, the CPU 21 sets the imaging time as the medication instruction end time. It is conceivable to calculate the time T17. The operation or the image taken by the camera is accumulated and stored in the data storage unit 24 of the client terminal 20 or the data storage unit 14 of the server device 10. In this case, the user can confirm the situation of handing over the medicine to the patient by means of a movie or an image after the fact.

  As described above, the time T11 to the time T17 are taken as the required time in each step of the dispensing operation from receipt of the prescription on the reception terminal 51 to the client terminal 20 until delivery of the medicine to the patient. When input, the CPU 21 stores the time T11 to the time T17 in the data storage unit 24. Thereby, the CPU 21 can thereafter calculate the required time of the entire stroke, that is, the waiting time T10 of the patient based on the time T11 to the time T17. Furthermore, since the CPU 21 can individually refer to the time T11 to the time T17 which are required times in the respective steps of the dispensing work, it is possible to calculate the required time of an arbitrary period in the dispensing work It is. For example, it is possible to calculate the required time from the time T11 to the time T12, that is, the required time from the reception at the reception terminal 51 to the dispensing data to the dispensing device. Therefore, the user shortens the waiting time of the patient by newly introducing the dispensing device or taking various measures such as increasing the number of personnel in the pharmacy etc. using the time T10 to the time T17. It becomes possible. The CPU 21 executes calculation processing of the required time in an arbitrary period of the dispensing operation, display processing of the required time on the display device 27 and the like according to the user operation on the operation input unit 26.

  Furthermore, the CPU 21 transmits the time T10 to the time T17 to the server device 10. Thereby, also in the server device 10, it is possible to manage the time T10 or the required time in an arbitrary period of the dispensing operation and the like. For example, in the server device 10, the time T10 and the required time in each of the client terminals 20 can be compared. Therefore, by referring to the time T10 and the required time by the server device 10, the manager of the dispensing information management system 1 is instructed to optimize the waiting time of the patient in a specific pharmacy or the like. Is possible.

  Further, in the server device 10, the pharmacy or the like in which each of the client terminals 20 is installed is divided into groups according to the type of the dispensing device installed in the pharmacy or the like, and the required time for each step in the dispensing operation is It is conceivable to manage. For example, a pharmacy etc. to which the tablet dispensing machine 52 and the powder dispensing machine 53 are connected as the dispensing device is set as the first group in the client terminal 20, and the CPU 11 sets the time T10 in the first group by the CPU 11. It is conceivable to calculate an average value. Thereby, the CPU 11 can determine whether the waiting time of the patient among the pharmacies belonging to the first group is equal to or more than the average value of the time T10. For example, when there is a pharmacy etc. where the time T10 is longer than the average value by a predetermined value or more among the pharmacies etc. belonging to the first group, the CPU 11 sends the client terminal 20 installed in the pharmacy etc. Therefore, it can warn that the waiting time of the patient is longer than other pharmacies etc.

  Furthermore, it is considered that the CPU 11 obtains information on the number and ratio of new patients from the client terminal 20 installed in a pharmacy or the like in which the time T10 is equal to or more than the average value and causes the display device 16 to display the information. Be Thereby, the manager using the server device 10 has the time T10 equal to or more than the average value because the time required for taking a medication instruction to a new patient is relatively long. It can be understood that there is no problem. In addition, it is conceivable that the CPU 11 acquires the operation status of each of the dispensing devices from the client terminal 20 installed in a pharmacy or the like in which the time T10 is equal to or more than the average value and causes the display device 16 to display it. Thereby, the administrator using the server device 10 has the time T10 equal to or more than the average value due to the high operation rate of the dispensing device, and the dispensing device is newly installed in the pharmacy or the like. It is possible to understand what it is desirable to do.

[Measure effect disclosure function]
The server device 10 manages the information of the measures which can be confirmed the effect of reduction of the similar incident among the measures performed for each information of the incident, and the client terminal installed in the pharmacy or the like where the same incident has occurred Has a function to notify 20. Specifically, when information is input in the solution column as the information on the incident in each of the client terminals 20, the CPU 11 reduces the number of information on the incidents input from the client terminal 20 thereafter. Determine if it is or not. Here, when the number of pieces of information of the incident decreases, it can be determined that the information input in the solution column is effective in reducing the incident. For example, when displaying the information of the past incident in the said client terminal 20, it is also possible to input the presence or absence of the effect of a solution by a check box etc. FIG. Thereby, in the server device 10, the CPU 11 can determine the presence or absence of the effect of the solution based on the presence or absence of the check of the check box.

  Therefore, when the CPU 11 determines that the solution inputted as the information of the incident is effective, the solution is applied to the client terminal 20 installed only in other stores where all the incidents have occurred or in all the stores. To notify. In addition, when information of a plurality of solutions is registered for the information of the same incident, and the effects are recognized for each of the solutions, the CPU 11 is the server device that is the most effective (the reduction of incidents is large) From 10, the client terminal 20 is notified. Further, it is also conceivable that the CPU 11 judges the validity of the information input in the column of the solution in accordance with the operation input of the administrator on the operation input device 16 in the server device 10. That is, the CPU 11 determines that the information input in the solution column is valid only when the administrator of the operation input device 16 permits it, and notifies each of the client terminals 20. Is considered.

  Furthermore, instead of actively notifying each of the client terminals 20 from the server device 10, when the information of the incident is input in the client terminal 20, the solution is read by the CPU 21. It is also conceivable that the information is displayed on the display device 27. In addition, when information of a plurality of solutions is registered for the information of the same incident and the effects are recognized for each of the solutions, the CPU 21 prioritizes in order from the solution having the highest effect (the decrease in incidents is large). Can be displayed.

[Summary of the Invention]
Hereinafter, the summary of the invention extracted from the above-described embodiment will be additionally stated.

[Supplementary Note 1]
Readout control means for reading out the prescription information from the prescription information storage means in which the prescription information on the prescription of the medicine is accumulated and stored, a prescription information display unit for displaying the prescription information read out by the readout control means, and dispensing of the medicine Display control means for displaying on the same screen of the display means an incident input unit for arbitrarily inputting information on incidents related to the group, and storing information on the incident inputted in the incident input unit in the incident information storage means A dispensing information management system comprising storage control means.

[Supplementary Note 2]
Patient information on the patient who has received the prescription of the medicine is further accumulated and stored in the prescription information storage means, and the readout control means reads out the patient information from the prescription information storage means, and the display control The dispensing information management system according to appendix 1, wherein the means displays the prescription information and the patient information on the prescription information display unit.

[Supplementary Note 3]
The display control means causes the display means to display a prescription selection screen for selecting any of the prescription information stored in the prescription information storage means, and then the prescription information selected on the prescription selection screen The dispensing information management system according to appendix 2, wherein the patient information corresponding to the prescription information is displayed on the prescription information display unit.

[Supplementary Note 4]
The incident input unit includes a target pharmaceutical input unit for inputting a target pharmaceutical of the incident, and the prescription information display unit displays the pharmaceutical of the target of the incident on the prescription information display. The medical device selection unit for selecting from medicines, wherein the display control means reflects the medicine selected by the medicine selection unit on the target medicine input unit Dispensing information management system described.

[Supplementary Note 5]
A level correspondence information storage unit storing level correspondence information indicating a correspondence relation between the content of the incident and the level of the incident is provided, and the incident input unit is a content input unit for inputting the content of the incident , And a level input unit for inputting the level of the incident, and the display control means is configured to, based on the content of the incident inputted to the content input unit and the level correspondence information, the content of the incident The dispensing information management system according to any one of appendices 1 to 4, wherein the level of the incident corresponding to is reflected in the level input unit.

[Supplementary Note 6]
The dispensing information management system according to Supplementary Note 5, further comprising: level changing means for arbitrarily changing the level of the incident reflected on the level input unit according to the content of the incident by the display control means.

[Supplementary Note 7]
The incident input unit includes a classification selection unit for selecting the content of the incident from a plurality of preset classifications, and an explanation input unit into which an explanation of the content of the incident is input, and the display control means The dispensing information management according to any one of appendices 1 to 6, wherein the description input unit reflects the description of the format preset for each classification according to the classification selected by the classification selecting unit. system.

[Supplementary Note 8]
The classification and selection unit is a large classification selection unit for selecting any of a plurality of large classifications set in advance, and a small classification for selecting any of a plurality of small classifications set in advance for each of the large classifications. A selection unit, and the display control means causes the small classification selection unit to display a plurality of the small classifications corresponding to the large classifications selected by the large classification selection unit, and the small classification selection unit The dispensing information management system according to appendix 7, wherein the explanation of the format corresponding to the small classification selected in is reflected in the explanation input unit.

[Supplementary Note 9]
An automatic drug dispensing apparatus for automatically dispensing a pharmaceutical product according to input dispensing data, a picking assist apparatus used when manually dispensing a pharmaceutical product according to the input dispensing data, and the above-mentioned input to the drug automatic dispensing apparatus Appendices 1-8 comprising transfer means for transmitting a part or all of the dispensing data to the picking assistance device in accordance with preset transfer conditions, and history storage means for transmitting transmission information of the dispensing data by the transfer means. The dispensing information management system according to any of the above.

[Supplementary Note 10]
The dispensing information management system according to appendix 9, wherein the history storage means further stores picking history information on a history of picking performed using the picking assisting device.

[Supplementary Note 11]
The storage control means associates information of the incident and either or both of the prescription information and the patient information corresponding to the incident and stores the information in the incident information storage means. Dispensing information management system described in.

[Supplementary Note 12]
It comprises: the read control means, the display control means, and a plurality of client terminals having the storage control means; and a server device having the incident information storage means, the storage control means comprising information on the incident The dispensing information management system according to any one of appendices 1 to 11, wherein information on the incident is stored in the incident storage unit by transmitting the information to the server device.

[Supplementary Note 13]
A dispensing information management system comprising a plurality of client terminals and a server device communicably connected to each of the client terminals, wherein the server device is an incident related to the dispensing of medicines transmitted from each of the client terminals. And incident information storage means for accumulating and storing information of the above, and statistical information output means for outputting statistical information of the incident stored in the incident information storage means according to the input statistical display condition. Dispensing information management system.

[Supplementary Note 14]
The server device further includes statistical display condition input means for inputting the statistical display condition, and the display condition input means uses, as the statistical display condition, a classification unit of each of the client terminals for calculating statistical information of the incident. The dispensing information according to appendix 13, wherein the statistical information output means outputs statistical information of the incident calculated for each of the selected classification units in accordance with the statistical display condition. Management system.

[Supplementary Note 15]
The dispensing information management system according to appendix 14, further comprising classification unit setting means for arbitrarily setting the classification unit.

[Supplementary Note 16]
The statistical information includes the number of occurrences for each content of the incident, and the statistical information output means is any one of a pharmaceutical unit, a prescription unit, or no count set in advance for each content of the incident. The dispensing information management system according to any one of appendices 13 to 15, which counts the number of occurrences of an incident.

[Supplementary Note 17]
The server apparatus comprises: user authentication means for authenticating a user; and authority information storage means in which authority information regarding the contents of the statistical information that can be displayed for each user is stored in advance; The dispensing information management system according to any one of appendices 13 to 16, wherein the output content of the statistical information is changed based on the user authenticated by the user authentication means and the authority information.

[Supplementary Note 18]
The reading control step of reading out the prescription information from the prescription information storage means in which the prescription information on the prescription of the medicine is accumulated and stored, the prescription information display unit for displaying the prescription information read out in the reading step A display control step for displaying an incident input unit for arbitrarily inputting information of an incident on the same screen of the display unit, and storage for storing information of the incident input to the incident input unit in the incident information storage unit A control process, and the dispensing information management method characterized by the above-mentioned.

[Supplementary Note 19]
Patient information on the patient who has received the prescription of the medicine is further accumulated and stored in the prescription information storage means, and the readout control step is to read out the patient information from the prescription information storage means, the display control The dispensing information management method according to appendix 18, wherein the process displays the prescription information and the patient information on the prescription information display unit.

[Supplementary Note 20]
A dispensing information management program for causing a computer to function as each unit according to any one of appendices 1-17.

[Supplementary Note 21]
20. A computer readable recording medium recording the dispensing information management program according to appendix 20.

1: Dispensing information management system 10: Server device 11: CPU
12: ROM
13: RAM
14: data storage unit 15: communication interface 16: operation input device 17: display device 18: bus 20: client terminal 21: CPU
22: ROM
23: RAM
24: Data storage unit 25: Communication interface 26: Operation input device 27: Display device 28: Dispensing communication unit 29: Bus 30: Server device 40, 50: Communication network 51: Reception terminal 52: Tablet dispensing machine 53: Powder dispensing machine 54: picking auxiliary device S1, S2, ...: processing procedure (step) number S101, S102, ...: processing procedure (step) number S201, S202, ...: processing procedure (step) number S301, S302, ...: processing procedure ( Step) number

Claims (1)

A dispensing information management system comprising: a plurality of client terminals; and a server device communicably connected to each of the client terminals, the dispensing information management system comprising:
Incident information storage means for accumulating and storing information on incidents related to dispensing of medicines transmitted from each of the client terminals;
Statistical information output means for outputting statistical information of the incident stored in the incident information storage means in accordance with the input statistical display condition;
Equipped with
The dispensing information management system, wherein the statistical information output means can output the operating status of the dispensing device connected to each of the client terminals.