WO2014007302A1 - Système de gestion d'informations sur un composé, procédé de gestion d'informations sur un composé, programme de gestion d'informations sur un composé, et support d'enregistrement - Google Patents

Système de gestion d'informations sur un composé, procédé de gestion d'informations sur un composé, programme de gestion d'informations sur un composé, et support d'enregistrement Download PDF

Info

Publication number
WO2014007302A1
WO2014007302A1 PCT/JP2013/068291 JP2013068291W WO2014007302A1 WO 2014007302 A1 WO2014007302 A1 WO 2014007302A1 JP 2013068291 W JP2013068291 W JP 2013068291W WO 2014007302 A1 WO2014007302 A1 WO 2014007302A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
incident
dispensing
prescription
input
Prior art date
Application number
PCT/JP2013/068291
Other languages
English (en)
Japanese (ja)
Inventor
古賀　淳
浩平 綿谷
Original Assignee
株式会社湯山製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=49882054&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2014007302(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by 株式会社湯山製作所 filed Critical 株式会社湯山製作所
Priority to JP2014523773A priority Critical patent/JP5725261B2/ja
Publication of WO2014007302A1 publication Critical patent/WO2014007302A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G16H20/13—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered from dispensers
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61J—CONTAINERS SPECIALLY ADAPTED FOR MEDICAL OR PHARMACEUTICAL PURPOSES; DEVICES OR METHODS SPECIALLY ADAPTED FOR BRINGING PHARMACEUTICAL PRODUCTS INTO PARTICULAR PHYSICAL OR ADMINISTERING FORMS; DEVICES FOR ADMINISTERING FOOD OR MEDICINES ORALLY; BABY COMFORTERS; DEVICES FOR RECEIVING SPITTLE
    • A61J3/00—Devices or methods specially adapted for bringing pharmaceutical products into particular physical or administering forms
    • A61J3/002—Compounding apparatus specially for enteral or parenteral nutritive solutions

Definitions

  • the present invention relates to a dispensation information management system for managing dispensation information related to the dispensing of pharmaceuticals in medical institutions or pharmacies.
  • incidents include incidents (hereinafter referred to as “mechanical incidents”) that occur in various dispensing devices used for dispensing, and incidents (hereinafter referred to as “human incidents”) that occur due to human error of the dispensing operator. included.
  • the mechanical incidents can be aggregated in the server device by causing each dispensing device to transmit the information on the mechanical incidents generated in each dispensing device to the server device.
  • the dispensing device is, for example, a tablet packaging machine or a powder packaging machine.
  • human incident information can be collected in the server device by being input to the client terminal and transmitted to the server device.
  • the present invention has been made in view of the above circumstances, and the object of the present invention is to provide a dispensing information management system, a dispensing information management method, and a dispensing that can improve the workability at the time of inputting a human incident by a user.
  • An object of the present invention is to provide a computer-readable recording medium in which an information management program and a dispensing information management program are recorded.
  • the present invention provides a read control means for reading out the prescription information from a prescription information storage means in which prescription information relating to a prescription of a pharmaceutical is stored, and the prescription information read out by the read control means
  • Display control means for displaying on the same screen of the display means a prescription information display section for displaying the information and an incident input section for arbitrarily inputting information on incidents related to the dispensing of the pharmaceutical, and input to the incident input section
  • a storage control unit that stores the incident information in an incident information storage unit.
  • the read control means reads out the patient information from the prescription information storage means.
  • the display control means displays the prescription information and the patient information on the prescription information display unit. Accordingly, the user can input the incident information to the incident input unit while confirming the patient information in addition to the prescription information.
  • the display control means displays a prescription selection screen for selecting any of the prescription information stored in the prescription information storage means on the display means, and is selected on the prescription selection screen. It is considered that the prescription information and the patient information corresponding to the prescription information are 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.
  • the incident input unit includes a target drug input unit for inputting a drug targeted for the incident.
  • the prescription information display unit includes a drug selection unit for selecting the drug targeted for the incident from the drugs displayed on the prescription information display unit.
  • the display control means reflects the drug selected by the drug selection unit on the target drug input unit.
  • the dispensing information management system includes level correspondence information storage means in which level correspondence information indicating the correspondence between the contents 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.
  • the display control means reflects the level of the incident corresponding to the content of the incident on the level input unit based on the content of the incident and the level correspondence information input to the content input unit. It is desirable that Thereby, the user does not need to input the level directly into the level input unit, and can input the level corresponding to the content of the incident quickly and accurately by the operation of inputting the content of the incident. Therefore, in the dispensing information management system, for example, when referring to the information of the incident, it is possible to display the information of the incident by ranking for each level. Note that there may be a case where an input of a level different from the level correspondence information stored in the level correspondence information storage means is required.
  • the display control means includes level changing means for arbitrarily changing the level of the incident reflected in the level input unit according to the content of the incident. As a result, after the display control unit reflects the incident on the level input unit according to the content of the incident, the level of the incident can be changed by the level changing unit, and usability is improved.
  • the incident input unit may include a classification selection unit for selecting the content of the incident from a plurality of preset categories and an explanation input unit for inputting the description of the content of the incident. It is done.
  • the display control means is configured to reflect a description of a format preset for each category according to the category selected by the category selection unit on the description input unit.
  • the classification selection unit selects either a large classification selection unit for selecting one of a plurality of preset major classifications or a plurality of small classifications preset for each major classification. It is conceivable to include a small category selection unit for doing this.
  • the display control means causes the minor classification selection unit to display a plurality of the minor classifications corresponding to the major classification selected by the major classification selection unit, and also selects the minor classification selection unit. It is conceivable that the explanation of the format corresponding to the small classification is reflected in the explanation input unit. According to such a configuration, the user does not need to directly input the description of the content of the incident, and input the description in a 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 the description in the same format set in advance according to the contents of the incident is input, the information on the incident becomes easy to see.
  • the dispensing information management system includes an automatic medicine dispensing device that automatically dispenses a medicine according to input dispensing data, a picking auxiliary device that is used when manually dispensing a medicine according to the inputted dispensing data, Transfer means for transmitting a part or all of the dispensing data input to the automatic medicine dispensing device to the picking auxiliary device in accordance with preset transfer conditions, and history for storing transmission history information of the dispensing data by the transfer means It is conceivable to provide storage means. Thereby, 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 auxiliary device.
  • the transfer condition is a missing drug in the automatic medicine dispensing device
  • the frequency of occurrence of a missing medicine in the automatic medicine dispensing device can be grasped.
  • the history storage means further stores picking history information relating to a history of picking performed using the picking auxiliary device. Accordingly, it is possible to grasp a history such as a picking collation result by the picking auxiliary device 54 with reference to the picking history information stored in the history storage unit.
  • the storage control means stores the incident information in association with one or both of the prescription information and the patient information corresponding to the incident and stores them in the incident information storage means. .
  • the information of the incident it is possible to easily grasp either one or both of the prescription information and the patient information that are targets for which the incident has occurred.
  • the computer information processing apparatus
  • the computer performs display output, print output, data output, or the like of the information on the incident
  • either or both of the prescription information and the patient information on which the incident has occurred Can be output at the same time.
  • the storage control unit may be configured to store the incident information in the incident storage unit by transmitting the incident information to the server device.
  • the prescription information storage means is provided in the client terminal or the server device. According to such a configuration, the incident information input to each of the client terminals arranged in a plurality of medical institutions and pharmacies is transmitted to the server device, whereby the incident information is transmitted to the server device. Can be aggregated. Thereby, for example, it becomes easy to effectively use the information of the incident as statistical information.
  • the present invention is also a dispensing information management system comprising a plurality of client terminals and a server device connected to each of the client terminals so as to be communicable, wherein the server device is transmitted from each of the client terminals.
  • Incident information storage means for accumulating and storing information on incidents related to dispensing of pharmaceuticals
  • statistical information output means for outputting statistical information of the incident stored in the incident information storage means in accordance with input statistical display conditions It may be configured as a dispensing information management system. As a result, the user can easily grasp the occurrence status of the incident at each of the client terminals by checking the statistical information of the incident output from the statistical information output means.
  • the dispensing information management system may further include statistical display condition input means for inputting the statistical display conditions to the server device.
  • the display condition input means inputs the classification unit of each of the client terminals for calculating the incident statistical information to the server device as the statistical display condition.
  • the statistical information output means outputs statistical information of the incident calculated for each of the selected classification units according to the statistical display condition.
  • the dispensing information management system preferably includes a classification unit setting means for arbitrarily setting the classification unit. Thereby, the user can set arbitrary client terminals as the same or different classification units.
  • the statistical information output means is either a medicine unit preset for each content of the incident, a prescription unit, or no count. It is desirable to count the number of incidents. Thereby, effective statistical information obtained by counting the number of incidents in an appropriate unit can be obtained.
  • the server device may include user authentication means for authenticating a user, and authority information storage means in which authority information relating to the contents of the statistical information that can be displayed for each user is stored in advance.
  • the statistical information output means may change the output contents 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 arbitrarily set in advance.
  • the present invention provides a read control step for reading the prescription information from the prescription information storage means in which prescription information relating to the prescription of the pharmaceutical is stored, and a prescription information display unit for displaying the prescription information read by the read step
  • a display control step for displaying on the same screen of a display means an incident input unit for arbitrarily inputting incident information relating to the pharmaceutical preparation and incident information input to the incident input unit as incident information
  • a storage control step for storing in the storage means.
  • the reading control step reads the patient information from the prescription information storage means. And it is possible that the said display control process displays the said prescription information and the said patient information on the said prescription information display part.
  • a dispensing information management program for causing a computer to function as each means provided in the dispensing information management system may be regarded as the present invention.
  • the present invention may be understood as a computer-readable recording medium that records the dispensing information management program.
  • the incident input unit includes a target drug input unit for inputting the target drug of the incident
  • the prescription information display unit displays the target drug of the incident on the prescription information display unit.
  • a medicine selection unit for selecting from the medicines. In this case, if the display control unit reflects the drug selected by the drug selection unit in the target drug input unit, the user does not need to input the drug directly into the target drug input unit. Thus, it is possible to quickly and accurately input the target drug for the incident by operating the drug selection unit.
  • the information processing apparatus further comprises level correspondence information storage means for storing level correspondence information indicating a correspondence relationship between the contents of the incident and the level of the incident, and the display control means inputs the incident input to the content input unit.
  • level correspondence information storage means for storing level correspondence information indicating a correspondence relationship between the contents of the incident and the level of the incident
  • the display control means inputs the incident input to the content input unit.
  • a configuration 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 is also conceivable. Thereby, the user does not need to input the level directly into the level input unit, and can input the level corresponding to the content of the incident quickly and accurately by the operation of inputting the content of the incident.
  • the storage control means may associate the information on the incident with the one or both of the prescription information and the patient information corresponding to the incident and store them in the incident information storage means. .
  • the schematic diagram which shows schematic structure of the dispensing information management system which concerns on embodiment of this invention.
  • the flowchart which shows an example of the procedure of the incident master edit process performed with a client terminal.
  • the flowchart which shows an example of the procedure of the incident input process performed with a client terminal.
  • inspection screen is an example of the procedure of the incident master edit process performed with a client terminal.
  • the flowchart which shows an example of the procedure of the incident input process performed with a client terminal.
  • 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 dispensing information management system 1 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 headquarter function that controls a plurality of medical institutions or pharmacies.
  • the management terminal 30 is an information processing apparatus such as a personal computer used for referring to incident information stored in the server apparatus 10.
  • the server device 10 or the management terminal 30 may be arranged in a medical institution or pharmacy together with the client terminal 20.
  • the said dispensing information management system 1 is demonstrated as an example of the dispensing information management system which concerns on this invention in this Embodiment, it is not restricted to this.
  • the client terminal 20 has the functions of the server device 10 and the management terminal 30.
  • 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 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.
  • the server device 10 is a computer including a CPU 11, a ROM 12, a RAM 13, a data storage unit 14, a communication interface 15, an operation input device 16 and a display device 17. Each component provided in the server device 10 is connected by a bus 18.
  • the CPU 11 is a processor that executes various arithmetic processes according to various control programs.
  • the ROM 12 is a non-volatile memory in which programs such as BIOS executed by the CPU 11 are stored in advance.
  • the RAM 13 is a volatile memory or a non-volatile memory used for development of various control programs and temporary storage of data by the CPU 31.
  • the communication interface 15 includes a communication modem 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 input means 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.
  • the operation input device 16 has a keyboard and a mouse (pointing device) used for inputting various information according to 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 that causes the CPU 11 to execute each processing procedure such as incident statistical information output processing (see FIG. 12) described later.
  • the dispensing information management program is written 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, DVD, BD, or flash memory.
  • the data storage unit 14 stores information on incidents to be described later transmitted from each of the client terminals 20 together with a database such as a pharmaceutical master, a pharmacy master, and an incident master.
  • the drug master includes, for example, drug code, drug name, JAN code (or RSS), drug bottle code, classification (drug form: powder, tablet, liquid medicine, topical drug, etc.), specific gravity, drug type (ordinary drug, poison drug) , Narcotics, powerful drugs, antipsychotics, therapeutics, etc.), changes in formulation, excipients, and precautions.
  • the pharmacy master includes, for example, information such as a store name corresponding to each client terminal 20, a group to which the store belongs, a group classification to which the store belongs, a store location, and a pharmacist belonging to the store.
  • the group classification is an area name such as “Kansai” or “Kanto”
  • the group is a name of a prefecture such as “Osaka” or “Hyogo”.
  • the incident master stored in the data storage unit 14 is information that is referred to when incident information is input in the client terminal 20.
  • FIG. 2 shows a part of the data of the incident master.
  • the incident master stores a group number, a group (major classification), a category, an incident content (minor classification), and a level in association with each other regarding incidents related to pharmaceutical dispensing.
  • a part of the incident master can be edited in an incident master editing process (see FIG. 3) to be described later executed on the client terminal 20.
  • the incident group includes “Drug acquisition error”, “Weighing / counting error”, “Packaging error”, “Master error”, “Input error”, “Filling error”, “Other”, “Operation error”.
  • the “user input” group is a group that is arbitrarily set when incident contents are additionally registered by the user, or is selected and set from the existing groups.
  • incident contents are set for each group.
  • the “medicine acquisition error” group includes incident details of “drug acquisition error”, “drug acquisition error”, “standard acquisition error”, and “forgetting drug acquisition”.
  • Each of the contents of the incident is assigned with a classification, and the classification is a numerical value used for input assistance for each of the contents of the incident.
  • a level is set for each incident content.
  • the level of the incident is represented by five stages of “S”, “A”, “B”, “C”, and “D”, and the level “S” is an incident having the highest risk level or importance.
  • the incident level may be a numerical value such as “1” to “5”.
  • the incident master is an example of level correspondence information
  • the data storage unit 14 is an example of level correspondence information storage means.
  • the level correspondence information storage means 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 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, and a dispensing communication unit 28. Each component provided in the client terminal 20 is connected by a bus 29.
  • the communication interface 25 includes a communication modem 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 processes according to various control programs.
  • the ROM 22 is a non-volatile memory in which programs such as BIOS executed by the CPU 21 are stored in advance.
  • the RAM 23 is a volatile memory or a non-volatile memory used for development of various control programs by the CPU 21 and temporary storage of data.
  • the operation input device 26 is input means 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 (pointing device) used for inputting various information according to the display screen of the display device 27.
  • operation “operation”, “selection”, and “input” in the client terminal 20 are performed by a user such as a pharmacist, a doctor, a nurse, a technician, and an office worker using the keyboard or mouse of the operation input device 26. Meaning work.
  • the operation input device 26 may include a touch panel provided on the display device 27 or a voice operation input device that receives input of various types of 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, each of the later-described incident master editing process (see FIG. 3), incident input process (see FIG. 5), incident statistical information output process (see FIG. 12), etc.
  • a dispensing information management program for executing the processing process is stored.
  • the dispensing information management program is C language (Microsoft C / C ++ and Visual C / C ++ (registered trademark)).
  • the said dispensing information management program is installed from recording media, such as CD, DVD, BD, flash memory, for example.
  • the dispensing information management program is stored in the server device 10 or a Web server, and the CPU 21 accesses the server device 10 or the Web server via the communication network 40 and stores the dispensing information management program in the dispensing information management program. It is also conceivable to execute processing according to the above. That is, the dispensing information management program may be a so-called web application that runs on a web browser.
  • the data storage unit 24 stores prescription history information related to prescription data input to the client terminal 20 together with a database such as a pharmaceutical master and a patient master.
  • the drug master includes drug code, drug name, JAN code (or RSS), drug bottle code, classification (drug form: powder, tablet, liquid medicine, topical medicine, etc.), specific gravity, drug type (ordinary drug, poison, Narcotics, powerful drugs, antipsychotics, therapeutics, etc.), compounding changes, excipients, and precautions.
  • the patient master includes information such as the patient ID, name, sex, age, medical history, family information, clinical department, ward, and ward of each patient.
  • the prescription history information includes prescription information related to past prescriptions of pharmaceuticals, patient information related to patients who have received prescriptions of the pharmaceuticals, and the like.
  • the prescription history information includes information such as when and where and how much medicine is prescribed for which patient.
  • the prescription history information includes prescription data reception date and time, exchange ticket number, patient ID, patient name, medical institution, clinical department, audit result, incident information, prescription drug code, prescription drug name, dosage form , Dose, usage, incident information described below, and so on.
  • a prescription drug code and a prescription drug name are examples of the prescription information
  • 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 every time a medicine is dispensed using a dispensing device described later connected to the client terminal 20.
  • the data storage unit 24 is an example of a prescription information storage unit.
  • the prescription information storage means 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 connected to a receiving terminal 51 to which patient prescription data is input, and a dispensing device such as a tablet packaging machine 52, a powder packaging machine 53, and a picking auxiliary device 54 used for dispensing pharmaceuticals.
  • the communication network 50 is connected so as to be communicable.
  • the dispensing communication unit 28 includes a communication modem that performs data communication between the reception terminal 51 and each of the dispensing devices 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 packaging machine 52 (an example of an automatic medicine dispensing device) has a plurality of medicine cassettes in which tablets of a plurality of types of medicines are stored, and follows a control instruction (dispensing data) input from the client terminal 20. Tablets are automatically dispensed from the medicine cassette and packaged in medicine packs or blister packs for each dose.
  • the powder medicine packaging machine 53 wraps the powder medicine in a medicine package for each dose according to a control instruction (dispensing data) input from the client terminal 20. In the powder medicine packaging machine 53, it is also possible to pack the powder together with the tablets for each dose.
  • the picking auxiliary device 54 is used when a pharmacist or the like picks a medicine from a medicine shelf according to a prescription and manually dispenses it, reads a medicine name from a barcode such as a medicine shelf or a medicine bottle, and reads the medicine. And the drug listed on the prescription.
  • the types of the dispensing devices connected to the client terminal 20 are not limited to these.
  • a PTP sheet dispensing device that automatically dispenses a medicine on a PTP sheet
  • an automatic injection dispensing system that automatically dispenses an injection
  • a powder inspection device for weighing and auditing powder and water for dispensing a liquid medicine
  • a drug dispensing device or the like also corresponds to the dispensing device.
  • Each of the dispensing devices may be connected to the client terminal 20 and the server device 10 via the communication network 40 so as to be communicable.
  • Each of the dispensing devices has a function of transmitting an incident that has occurred in the dispensing of the pharmaceutical to the client terminal 20. Thereby, information on incidents occurring in each of the dispensing devices is collected in the client terminal 20. Then, the client terminal 20 transmits the incident information to the server device 10.
  • the CPU 21 selects the dispensing device that dispenses the medicine contained 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.
  • the prescription data includes prescription date of delivery, patient ID, patient name, patient birth date, dosage form information (internal use, topical use, etc.), drug information (drug code, drug name, dose), usage information ( Etc.) after 3 meals a day).
  • said CPU21 produces
  • the control unit of the tablet packaging machine 52 notifies the client terminal 20 to that effect.
  • the CPU 21 of the client terminal 20 transmits dispensing data related to a part or all of the pharmaceutical that satisfies the transfer condition in the dispensing data to the picking auxiliary device 54. Accordingly, the user can dispense a medicine using the picking auxiliary device 54.
  • the CPU 21 when executing the processing corresponds to the transfer means.
  • the main body that transfers the dispensing data by transferring from the tablet packaging machine 52 to the picking auxiliary device 54 is not limited to the client terminal 20 but may be a control unit of the tablet packaging machine 52.
  • the control unit of the tablet packaging machine 52 corresponds to a transfer unit.
  • the picking assisting device 54 stores picking history information related to a history such as a result of collation of picking performed by a pharmacist or the like based on the dispensing data in an internal storage memory and transmits it to the client terminal 20 as well.
  • the CPU 21 of the client terminal 20 transmits the transmission history information related to the dispensing data transmitted from the tablet packaging machine 52 to the picking auxiliary device 54 and the picking history information received from the picking auxiliary 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.
  • each of the data storage unit 24 and the data storage unit 14 corresponds to a history storage unit.
  • the user refers to the transmission history information in the client terminal 20 and the server device 10.
  • the usage frequency of the tablet packaging machine 52 and the picking auxiliary device 54 can be grasped. For example, it is possible to grasp the frequency of occurrence of missing drugs in the tablet packaging machine 52.
  • the user can grasp a history such as a matching result of picking by the picking auxiliary device 54.
  • the CPU 21 of the client terminal 20 or the control unit of the tablet packaging machine 52 includes a two-dimensional barcode or a three-dimensional barcode indicating dispensing data regarding some or all of the pharmaceuticals satisfying the transfer condition in the dispensing data. It is also conceivable for the printer to print out the information as transfer information.
  • the user reads the printed two-dimensional bar code or three-dimensional bar code with the picking auxiliary device 54 and dispenses a medicine using the picking auxiliary device 54.
  • the control unit of the picking auxiliary device 54 may read the dispensing data from the client terminal 20 based on the transfer information.
  • 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 possible to memorize it.
  • Step S1 First, in step S ⁇ b> 1, the CPU 21 determines whether or not the incident master editing start operation has been performed by a user operation of the operation input device 26. When the CPU 21 determines that the incident master editing start operation has been performed (Yes in S1), the CPU 21 shifts the processing to step S2. If the CPU 21 determines that the incident master editing start operation has not been performed (Yes in S1), the CPU 21 causes the process to wait in step S1. Specifically, the CPU 21 displays an initial setting screen related to 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. When the operation is performed (Yes side of S1), the process proceeds to step S2.
  • Step S2 the CPU 21 determines whether or not the data storage unit 14 of the server device 10 is accessible.
  • the CPU 21 shifts the process to step S3.
  • the CPU 21 shifts the process to step S21.
  • Step S21 the CPU 21 causes the display device 27 to display that the data storage unit 14 of the server device 10 is not accessible. For example, it is conceivable that the CPU 21 displays “cannot be accessed because it is currently under maintenance” on the display device 27. Thereafter, the CPU 21 returns the processing 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 side of S3).
  • the CPU 21 determines that the login operation has been performed (Yes side of S3), and the process is performed in step S4. To migrate. Note that various conventional techniques may be adopted as the method of the login operation.
  • Step S4 the CPU 21 causes the display device 27 to display a master registration screen D11 for editing the incident master.
  • FIG. 4 is a view showing a display example of 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 contents of the incident category registered in the incident master Screen D13.
  • a registration key 111, a search key 112, a delete key 113, a condition clear key 114, and a return key 115 are displayed at the lower end of the master registration screen D11.
  • Step S5 the CPU 21 executes an editing process for editing the incident master in accordance with a user operation of the operation input device 26 according to the master registration screen D11.
  • the CPU 21 searches the search conditions for the “classification” and “name”.
  • a list of incident categories satisfying the requirement is extracted from the incident master and displayed on the search screen D12.
  • the CPU 21 displays the setting content of the incident on the setting screen D13.
  • each input column of the setting screen D13 is blank.
  • the CPU 21 edits information in each of the input fields displayed on the setting screen D13 in response to a user operation of the operation input device 26.
  • the setting screen D13 includes “incident category”, “incident category 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.
  • “Incident Category” is a text input field for inputting numerical information for identifying the incident.
  • the “incident category name” is a text input field for inputting the contents of the incident.
  • the “incident group number” is a pull-down input field for selecting and inputting a group to which the incident category belongs, and the group selection candidates are extracted from the incident master (see FIG. 2).
  • “Incident level” is a pull-down input field for selecting and inputting the level of the incident. For example, “incident level” is selected and input from five stages of “S”, “A”, “B”, “C”, and “D”. .
  • “Incident occurrence information” is a pull-down input field for selecting and inputting an incident occurrence information flag.
  • the “incident occurrence information” is an indicator for determining whether or not input can be made to the input units D35 to D37 of the incident screen D31 (see FIG. 7) displayed in the incident input process (see FIG. 5) described later executed by the CPU 21.
  • “Valid flag” is a pull-down input field for selecting whether to count as an incident in the statistical information of the incident.
  • the “pharmacist incident flag” is a pull-down input field for selectively inputting whether or not to add as the number of incidents of the pharmacist in charge of the incident in the statistical information of the incident.
  • “OK number acquisition type (store)” is a pull-down input field in which a unit for counting the number of incident OK cases is selected and input for each store. For example, there is no count, prescription number, or drug number. Selected and input.
  • the “OK number acquisition type (pharmacist)” is a pull-down input field in which a unit for counting the number of incidents for each pharmacist is selected and input. For example, there is no count, prescription number, or drug number.
  • the “target dispensing device” is a list input field for selecting and inputting the type of the target dispensing device that can use the incident category when inputting an incident.
  • the list input field 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 right list and the corresponding incident category can be used When the target dispensing device is selected in the list on the right side and “delete” is operated, the target dispensing device is excluded.
  • the list input column of “target dispensing device” for example, a display area for six lines is secured, and at the same time, six types of target dispensing devices are displayed in the list input column of “target dispensing device”.
  • the “sort number” is a numerical value that determines the sort order when the incident category is displayed as a list. If it is empty, “9999” is set as an initial value.
  • the CPU 21 deletes the contents of the incident category displayed on the setting screen D13 from the incident master.
  • the only incident category that can be deleted by the delete key 113 is the 900-th category (see FIG. 2) corresponding to “user input”.
  • the CPU 21 selects a message for reconfirming the deletion, such as “Delete it? Are you sure?” It is displayed on the display device 26 together with the “OK” and “Cancel” operation units. Then, after the message is displayed, the CPU 21 deletes the contents of the incident category from the incident master on the condition that the operation unit “OK” is operated.
  • the CPU 21 initializes the information displayed on the setting screen D13 and moves the cursor indicating the operation target to “incident category”. As a result, the user can input information according to the setting screen D13 from the beginning.
  • Step S6 the CPU 21 determines whether or not to cancel the incident master editing depending on whether or not the return key 115 is operated.
  • the CPU 21 determines that the editing of the incident master is canceled by performing the operation of the return key 115 (Yes side of S6), the setting contents on the master registration screen D11 are reflected in the incident master. Without letting it go, the process returns to step S1.
  • the return key 115 is not operated and the CPU 21 determines not to cancel the editing of the incident master (No side of S6), the process proceeds to step S7.
  • Step S7 the CPU 21 determines whether or not to confirm the edited content of the incident master depending on whether or not the registration key 111 is operated.
  • the CPU 21 determines that the edited contents of the incident master are to be confirmed by operating the registration key 111 (Yes in S7), the process proceeds to step S8.
  • the CPU 21 returns the process to the step S5 and follows the master registration screen D11. The incident master editing process is continued.
  • Step S8 the CPU 21 reflects the contents of the incident classification input on the setting screen D13 of the master registration screen D11 in the incident master, and then ends the series of incident master editing processing, and performs the processing. Return to step S1. Specifically, the CPU 21 checks whether or not the content of the incident category input on the setting screen D13 is contrary to the prohibited content set in advance. It is displayed on the display device 26. For example, the content of the prohibition is that the incident classification is a number with a predetermined number of digits or a number such as a predetermined 900 number. If the content of the incident category violates the prohibition process, the CPU 21 returns the process to step S5 to prompt the correction of the content of the incident category.
  • the CPU 21 when there is no error in the content of the incident category, the CPU 21 reflects the content of the incident category input on the setting screen D13 in the incident master. At this time, when the incident category already registered in the incident master of the data storage unit 14 is edited, the CPU 21 updates the content of the incident category with the changed content. In addition, when a new setting is made for the contents of an incident category that has not yet been registered in the incident master of the data storage unit 14, the CPU 21 stores the contents of the incident category after the setting in the incident master. Add and remember.
  • Step S101 the CPU 21 determines whether or not an incident input start operation has been performed by a user operation of the operation input device 26. If the CPU 21 determines that the incident input start operation has been performed (Yes in S101), the CPU 21 shifts the processing to step S102. If the CPU 21 determines that the incident input start operation has not been performed (No in S101), the CPU 21 causes the process to wait in step S101.
  • Step S102 the CPU 21 determines whether the data storage unit 14 of the server device 10 is accessible.
  • the CPU 21 shifts the process to step S103.
  • the CPU 21 shifts the process to step S121.
  • Step S121 the CPU 21 causes the display device 27 to display that the data storage unit 14 of the server device 10 is not accessible. For example, it is conceivable that the CPU 21 displays “cannot be accessed because it is currently under maintenance” on the display device 27. Thereafter, the CPU 21 returns the processing to step S101.
  • Step S103 the CPU 21 displays a login screen on the display device 27 and waits for a login operation by the user (No side in S103).
  • the CPU 21 determines that a login operation has been performed when a user ID and password are input and user authentication is performed by a user operation on the operation input device 26 (Yes side of S103), and the process is performed in step S104. To migrate. Note that various conventional techniques may be adopted as the method of the login operation.
  • Step S104 the CPU 21 causes the display device 26 to display a prescription selection screen D21 for displaying a list of past prescriptions stored as the prescription history information in the data storage unit 24.
  • FIG. 6 shows an example of the prescription selection screen D21.
  • a condition input unit D22 for setting a search condition for searching for the prescription history information accumulated and stored in the data storage unit 24, and a search input to the condition input unit D22
  • a prescription list display unit D23 in which the prescription history information extracted according to the conditions is displayed as a list is displayed.
  • the prescription selection screen D21 displays a search key 211, a condition clear key 212, and an end key 213.
  • the CPU 21 extracts the prescription history information stored in the data storage unit 24 according to the search condition, and It is displayed on the prescription list display part D23.
  • the condition input unit D22 “patient name”, “exchange ticket number”, “reception date”, “medical institution”, “clinical department”, “final audit”, “incident”, “display order”, etc.
  • the search condition can be entered.
  • the condition clear key 212 the CPU 21 initializes the search condition displayed on the condition input unit D22.
  • the end key 213 is operated, the CPU 21 closes the prescription selection screen D21 and ends the incident input process.
  • the prescription list display unit D23 displays a list of prescription history information that matches the search condition among the prescription history information stored in the data storage unit 24.
  • “Reception date”, “Time”, “Exchange ticket number”, “Patient ID”, “Patient name”, “Patient Kana”, “Medical institution”, “Medical department” , "Final Audit”, "Incident Input” information is displayed.
  • 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.
  • An audit key 216 is displayed in the “final audit” column.
  • Steps S105 to S107 the CPU 21 waits for any operation 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 S107). No side of S107). If the CPU 21 determines that the new creation key 214 has been operated (Yes in S105), the CPU 21 determines that a new incident creation operation has been performed, and the process proceeds to step S151. If 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 the process proceeds to step S161. Further, when the CPU 21 determines that the audit key 216 has been operated (Yes in S107), the CPU 21 determines that an audit start operation has been performed, and shifts the processing to step S171.
  • step S151 the CPU 21 causes the display device 27 to display an incident screen D31 for registering an incident for the prescription history information corresponding to the newly created key 214 operated in step S105.
  • step S152 the CPU 21 executes an input process for inputting incident information to the incident screen D31 in response to a user operation of the operation input device 26 according to the incident screen D31.
  • the input process executed by the CPU 21 in accordance with the operation input of the operation input device 26 on the incident screen D31 will be described.
  • FIG. 7 shows a display example of the incident screen D31.
  • a patient information display part D32, a prescription information display part D33, and an incident input part 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. Thereby, 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.
  • the incident screen D31 is divided into left and right parts, the patient information display part D32 and the prescription information display part D33 are displayed side by side on the left side, and the incident input part D34 is displayed on the right side. ing.
  • items that do not need to be input are displayed on the left side, and items that require input are displayed on the right side.
  • the item which a user should pay attention to an input omission of aggregation. Can be prevented.
  • patient information related to the patient such as “patient ID”, “patient name”, “medical institution”, “clinical department”, “reception date” is displayed in the patient information display section D32.
  • the prescription information display unit D33 displays prescription information related to prescription of pharmaceuticals such as “prescription drug ID”, “prescription drug name”, “usage”, and “dose”.
  • the CPU 21 determines, based on the prescription history information stored in the data storage unit 24 of the client terminal 20, “patient ID”, “patient name”, “medical institution”, “clinical department”, “reception date / time”. And the like are automatically extracted and displayed on the patient information display unit D32.
  • the CPU 21 automatically sets “prescription drug ID”, “prescription drug name”, “use”, “dose”, and the like from the prescription history information stored in the data storage unit 24 of the client terminal 20. Extracted and displayed on the 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 that is automatically read from the data storage unit 24 by the CPU 21 and displayed.
  • the CPU 21 when executing the readout process corresponds to the readout control means.
  • incident input section D34 “incident occurrence date / time”, “party (pharmacist, etc.)”, “occurrence location”, “discovery point”, “incident”, “level”, “prescription information”, “wrong” Input fields are displayed for entering incident information such as “medicine”, “contents mistaken”, “cause factor”, “case contents / causes”, “solution / guidance contents”.
  • incident input unit D34 the input fields for “contents mistaken”, “case contents / causes”, and “solution / instruction contents” are input fields in which any text can be input as necessary. However, information is input to other input fields by numerical input or selection input.
  • the incident information input to the incident input unit D34 has a structure in which statistical information can be easily obtained.
  • incident content includes a group selection key 321 for selecting an incident group and a content selection key 322 for selecting the content of an incident belonging to the group selected by the group selection key 321.
  • group selection key 321 for selecting an incident group
  • content selection key 322 for selecting the content of an incident belonging to the group selected by the group selection key 321.
  • 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 using a pull-down menu. Then, the CPU 21 reflects the group selected from the pull-down menu in the group input field 321A. Next, when the content selection key 322 is operated, the CPU 21 lists only the content of incidents corresponding to the group selected by the group selection key 321 among the content of incidents registered in the incident master. To display in the pull-down menu.
  • 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).
  • the group selection key 321 and the content selection key 322 are an example of a classification selection unit.
  • 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 enters the level input field 323A (corresponding to a level input unit). To reflect.
  • the CPU 21 changes the incident level 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.
  • the CPU 21 when executing the changing process corresponds to a level changing unit.
  • the incident input unit D34 includes an input unit D35 (corresponding to the target drug input unit) for inputting a drug that is the subject of an incident, and an input unit D36 for inputting a wrong drug.
  • An input part D37 (corresponding to the explanation input part) for inputting or displaying the explanation of the above in text is displayed.
  • 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 can input any one or more of the input units D35 to D37 according to the contents of the incident occurrence information flag, and cannot input the rest by grayout display or the like.
  • the CPU 21 determines whether or not the input units D35 to D37 can be input based on the display switching information shown in FIG. In FIG. 8, “ ⁇ ” indicates that input is possible, and “-” indicates that input is not possible.
  • the incident occurrence information flag is “drug (mistake)”
  • the input units D35 and D36 can be input, and the input unit D37 cannot be input.
  • the incident occurrence information flag is “drug (dose mistake)”
  • the input units D35 and D37 can be input, and the input unit D36 cannot be input. In this way, only the fields that need to be input according to the incident occurrence information flag can be input, so that the user can easily recognize the part that needs to be input and prevent erroneous input of unnecessary information. be able to.
  • the CPU 21 in the display switching information, a description format is set for each incident occurrence information flag, which is input as an error in the input unit D37. Then, the CPU 21 refers to the “wrong content” stored in the display switching information in correspondence with the content of the incident input in the content input field 322A, and the incident in the form of the “wrong content”. Is displayed on the input unit D37.
  • the incident occurrence information flag is “not specified”, “medicine”, “patient error”, “usage”, “medical institution”, “clinical department”, “comment”, the CPU 21 inputs the input unit D37. Display nothing.
  • the CPU 21 determines from the input information of the input unit D35 and the input unit D36 that “the drug name of the input unit D35 ⁇ the drug of the input unit D36.
  • the text “name” is automatically generated and displayed on the input unit D37.
  • the content of the incident entered in the content entry field 322A is “mistake mistake”
  • the medication entered in the input unit D35 is “Actos lock”
  • the wrong medication entered in the input unit D36 In the case of “iTroll tablet”, “actos lock ⁇ iTroll tablet” is displayed on the input unit D37. In this case, since the user does not need to input the input unit D37, the text is displayed in a state where the input unit D37 is grayed out.
  • the CPU 21 inputs text to the input unit D37 in accordance with a manual input operation of the operation input device 26 by the user. Specifically, the user inputs a description of the content of the incident in the format of “prescription dose + unit ⁇ dispensing dose + unit” to the operation input device 26. At this time, it may be considered that the CPU 21 displays a description of the contents of the incident in the form of “prescription dose + unit ⁇ dispensing dose + unit” below the input unit D37.
  • the group input in the group input field 321A is “Weighing / Weighing Mistake”
  • the case where the content of the incident is “Dose Wrong” or “Normal Dose Wrong” is the input unit D37. It is conceivable to change the contents of the explanation to be entered in Specifically, when the content of the incident is “drug (dose mistake)”, the CPU 21 inputs the description of the content of the incident in the form of “prescription dose + unit ⁇ dispensing dose + unit” as described above. A message to the effect is displayed below the input part D37.
  • the CPU 21 determines “prescription dose + unit ⁇ dispensing dose + unit [upper limit]” and “prescription dose + unit ⁇ dispensing dose + unit [lower limit]”. ”,“ Prescription dose + unit ⁇ dispensing dose + unit [over 2.1 times] ”or“ prescription dose + unit ⁇ dispensing dose + unit [0.5 shortage] ” It is conceivable to display that the input is to be performed below the input part D37. As a result, in the case of an error in the normal dose of the drug, the user distinguishes and inputs whether the error is contrary to “upper limit”, “lower limit”, “2.1 times excess”, or “0.5 shortage”. You can know what to do.
  • a “weighing / measurement error” is either a dose error or a normal dose error. It is possible to grasp at a glance whether there is a certain type or the type of normal dose mistake.
  • the CPU 21 grays out all the input units D35 to D37 and disables input. In this case, according to the manual input operation of the operation input device 36 by the user, the CPU 21 inputs the contents of the patient error by text in the input unit D38, the input field 329A, and the input field 329B described later.
  • the prescription information display unit D33 displays a reflection operation key 320 corresponding to each of a plurality of medicines included in the prescription history information.
  • Each of the reflection operation keys 320 is an example of a drug selection unit operated to select a drug to be input to the incident input unit D34 from the drugs displayed on the prescription information display unit D33.
  • the CPU 21 reflects and displays the medicine name corresponding to the reflection operation key 320 in the “prescription medicine” column of the input unit D35.
  • the CPU 21 determines a medicine code (CD), a medicine name, a medicine name corresponding to the medicine name based on the medicine name corresponding to the reflection operation key 320 and the medicine master stored in the data storage unit 24.
  • CD medicine code
  • the YJ code is extracted and automatically displayed on 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.
  • the CPU 21 reflects the drug information on the input unit D35.
  • FIG. 9 is a diagram showing a display example of the medicine list screen D41.
  • medicine codes and medicine names of medicines registered in the medicine master are displayed in a list.
  • the CPU 21 reflects the selected drug name on the input unit D36.
  • the CPU 21 determines the medicine code (CD) and medicine name 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.
  • YJ code is extracted and automatically displayed on the input unit D36.
  • the cancel key 412 is operated on the medicine list screen D41
  • the CPU 21 cancels the selection of medicines and closes the medicine list screen D41.
  • the CPU 21 disables the operation of the wrong medicine selection key 325.
  • the check box is used when a wrong medicine is not registered in the medicine master.
  • the CPU 21 displays the input unit D36 in gray and displays the input unit D37 on the input unit D35.
  • Drug name ⁇ unregistered drug is also considered as other embodiment.
  • the CPU 21 lists the occurrence factors set in advance corresponding to the contents of the incident input in the content input field 322A. Is displayed in the pull-down menu.
  • As the generation factor for example, “insufficient confirmation”, “inappropriate determination”, “because of being busy”, and the like can be considered.
  • the CPU 21 reflects the occurrence factor in the occurrence factor column 326A.
  • the CPU 21 causes the generation factor input in the generation factor column 326A to be reflected in the generation factor input unit D38.
  • a plurality of generation factors can be input to the generation factor input unit D38.
  • the generation factor input to the generation factor input unit D38 is deleted by the CPU 21 by operating the delete key 328.
  • the CPU 21 moves the cursor to the “example content / cause” input field 329A or the “solution / instruction content” input field 329B displayed on the incident input unit D34 by a user operation of the operation input device 26.
  • the text is input to 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 case details of the incident and details of the cause are arbitrarily described.
  • the input field 329B is an area in which a solution or instruction content performed after the occurrence of the incident is arbitrarily described.
  • a registration key 311, a new creation key 312, a past report key 313, a send key 314 315, a delete key 316, a preview key 317, a clear key 318, a return key 319, etc. are displayed at the lower end of the incident screen D 31.
  • Operation keys are displayed.
  • the CPU 21 executes a predetermined check process and then executes a process corresponding to the operation key. For example, in the check process, it is checked whether it is within the system data storage period, whether it has been deleted, or the like as follows.
  • the reception date displayed on the patient information display unit D32 is earlier than the current date and before the dispensing system data storage months set in the dispensing management system 1, “The date has fallen below the system limit.
  • the screen returns to the prescription selection screen.” Is displayed on the display device 26, and then the prescription selection screen D21 is displayed on the display device 26. Further, when the prescription information displayed on the prescription information display unit D33 has already been deleted, the CPU 21 displays a message such as “Already incident information has been deleted. Return 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.
  • the CPU 21 indicates that “the incident information has already been deleted. After the message such as “Returns to the selection screen” is displayed on the display device 26, the prescription selection screen D21 is displayed on the display device 26. Further, if the information on the destination incident has already been deleted when the feed keys 314 and 315 are operated, the CPU 21 returns to the “Prescription selection screen. "Is displayed on the display device 26, and then the prescription selection screen D21 is displayed on the display device 26. *
  • the CPU 21 determines the edited content of the incident input unit D34 as incident information and stores it in the RAM 23 or the like. 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 in the incident input unit D34 has been updated in the other client terminal 20 after the information has been updated in the client terminal 20, the CPU 21 displays that fact. An exclusive control process to be displayed on the device 26 is executed. In addition, the CPU 21 checks whether or not the incident information input to the incident input unit D34 violates preset prohibited contents, and if there is an error, the display device displays the fact. 26 is displayed.
  • the CPU 21 determines that there is an error that violates the prohibition content when a date before “reception date” displayed on the patient information display unit D32 is input as “incident occurrence date”. On the other hand, when there is no error in the incident information, the CPU 21 determines the incident information input to the incident input unit D34 and records it in the RAM 23 or the like.
  • the CPU 21 initializes the editing contents of the incident input unit D34.
  • the CPU 21 switches the incident information displayed on the incident screen D31 to the oldest incident information.
  • the feed keys 314 and 315 are operated, the CPU 21 sequentially switches the incident information displayed on the incident screen D31 to new and old information.
  • the feed key 314 is hidden when displaying the information on the oldest incident, and the feed key 315 is hidden when displaying the information on the latest incident.
  • the CPU 21 deletes the incident information displayed on the incident screen D31 from the data storage unit 14 of the server device 10.
  • the CPU 21 uses a message for reconfirming the deletion such as “Delete it? Are you sure?”
  • the information is displayed on the display device 26 together with the “OK” and “Cancel” operation units.
  • the CPU 21 deletes the incident information on condition that the “OK” operation unit is operated.
  • the delete key 316 is displayed only when past incident information is displayed according to the operation of the past report key 313.
  • the CPU 21 displays a preview screen when the incident information 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 according to the operation of the return key displayed on the preview screen and causes the display device 26 to display the incident screen D31.
  • the CPU 21 initializes incident information displayed on the incident screen D31.
  • the clear key 318 is displayed only when new incident information is registered.
  • the return key 319 the CPU 21 returns the display screen of the display device 26 to the screen that was displayed immediately before the incident screen D31 is displayed.
  • the CPU 21 displays the prescription selection screen D21 on the display device 26. Further, the CPU 21 causes the display device 26 to display the audit screen D51 when the return key 319 is operated after the transition from the audit screen D51 (see FIG. 11) described later to the incident screen D31. .
  • Step S153 the CPU 21 determines whether or not an operation for registering the incident information input in step S152 has been performed, depending on whether or not the registration key 311 has been operated.
  • the CPU 21 determines that the registration key 311 has been operated (Yes in S153)
  • the CPU 21 shifts the processing to step S154.
  • the CPU 21 returns the process to step S152 and continues the incident information input process according to the incident screen D31. .
  • step S154 the CPU 21 transmits the incident information input to the incident input unit D34 in step S152 to the server device 10 via the communication interface 25.
  • the CPU 11 in the server device 10 accumulates and stores the incident information in the data storage unit 14. Therefore, in the dispensing information management system 1, incident information input at each of the client terminals 20 is collected in the server device 10.
  • the CPU 21 when the incident information is stored 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 incident information storage means.
  • the incident information storage means may be a Web server provided on a network accessible from the server device 10, the client terminal 20, or the management terminal 30. FIG.
  • the CPU 21 may transmit the incident information transmitted to the server device 10 to a printer (not shown) and cause the printer to print the incident information as a form.
  • the CPU 21 transmits only the incident information to the server device 10 and stores it in the data storage unit 14, and transmits the prescription information and the patient information to the server device 10. Not done. Therefore, the prescription information and the patient information are not stored in the data storage unit 14 of the server device 10, and the patient information included in the prescription information and the patient information from a plurality of information processing devices such as the management terminal 30. Since the personal information cannot be referred to, the personal information of the patient is protected.
  • the CPU 21 may transmit the incident information and the prescription information corresponding to the incident information and / or the patient information to the server device 10 in association with each other. It can be considered as an embodiment.
  • the information on the incident is stored in the data storage unit 14 in a state associated with either one or both of the prescription information and the patient information that are targets for which the incident has occurred. Therefore, when the information processing apparatus such as the management terminal 30 performs display output, print output, data output, or the like of the information on the incident stored in the data storage unit 14, the incident has occurred. Either or both of the prescription information and the patient information can be output simultaneously.
  • the incident information when the incident information is displayed and output on a display device, either or both of the prescription information and the patient information corresponding to the incident information are displayed simultaneously, or the prescription information corresponding to the incident information
  • a link button for displaying either one or both of the patient information.
  • 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 them. Display on the device.
  • the incident information corresponding to the prescription information or the patient information can be easily grasped.
  • the prescription information and the patient information are stored together with the incident information in the data storage unit 14 of the server device 10, the prescription information and the patient information and the like are transmitted from the information processing device such as the management terminal 30.
  • the included patient's personal information 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. Thereby, the personal information of a patient can be protected by limiting 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 access authority to the data storage unit 14.
  • the CPU 11 specifies a user who is logged in at the management terminal 30 in order to refer to the incident information from the information processing apparatus such as the management terminal 30 to the data storage unit 14.
  • the CPU 11 permits reference to 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.
  • 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 patient personal information, the CPU 11 permits reference to the prescription information and prohibits only reference to the patient information when the user is not a limited user such as an administrator. It is also possible.
  • Step 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 side in S106), the CPU 21 shifts the process to step S161.
  • step S161 the CPU 21 displays information on past incidents already registered for the prescription history information on which the past incident key 215 operated in step S107 is displayed, similar to the incident screen D31 (see FIG. 7). Are displayed on the display device 27. Of course, the past incident information may be displayed on a reference screen different from the incident screen D31.
  • step S162 the CPU 21 determines whether or not the confirmation of past incident information has been completed depending on whether or not the return key 319 displayed on the incident screen D31 has been operated.
  • step S162 If it is determined that the confirmation of past incident information has been completed by operating the return key 319 (Yes in S162), the process proceeds to step S104, and the prescription selection screen D21 is displayed on the display device 26. To display. On the other hand, the CPU 21 returns the processing to step S161 until the return key 319 is operated (No side of S162).
  • Step S171 the CPU 21 shifts the process to step S171.
  • step S171 the CPU 21 displays on the display device 27 an audit screen D51 for auditing the prescription of the medicine displayed in the prescription history information on which the audit key 214 operated in step S107 is displayed.
  • FIG. 11 is a diagram showing a display example of the audit screen D51.
  • 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 an audit completion operation is performed instead of the incident input unit D34.
  • the audit input section D52 is displayed.
  • an incident input key 511 and a return key 512 for starting input of incident information are displayed at the lower end of the audit screen D51.
  • the CPU 21 determines that an incident creation operation has been performed (Yes in S172), and shifts the processing to step S151. Thereby, the CPU 21 shifts the display screen of the display device 26 from the audit screen D51 to the incident screen D31.
  • the return key 512 is operated, the CPU 21 returns the display screen of the display device 26 to the display screen that was displayed before the audit screen D51 was displayed.
  • the audit input unit D52 displays a selection input unit 513 for selecting and inputting an audit pharmacist in charge of the audit and an audit completion key 514 for completing the audit.
  • the selection input unit 513 When the selection input unit 513 is operated, the CPU 21 displays a list of pharmacists registered in advance, and reflects the pharmacist selected from the list in the input column of “inspection pharmacist”. For example, the pharmacist displayed at this time is only a pharmacist registered as a pharmacist belonging to the pharmacy or the like where the client terminal 20 is installed in the pharmacy master of the data storage unit 14.
  • 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 includes the prescription history information.
  • S174 The fact that the audit of the prescription information displayed on the prescription information display unit D33 is completed and the audit pharmacist selected by the selection input unit 511 are registered (S174). Thereafter, the CPU 21 shifts the processing to step S4.
  • incident statistics output processing Next, an example of the procedure of incident statistics output processing 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.
  • 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, thereby accumulating and storing in the server device 10 on the display device 27 of the client terminal 20.
  • Statistics for incidents that have been made are displayed.
  • the case where the 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 or the like connected to the server device 10 so as to be communicable.
  • Statistical information can be displayed.
  • processing steps similar to the following processing steps executed in the client terminal 20 are executed by a control unit such as a CPU.
  • the CPU 11 can display the statistical information of the incident on the display device 17.
  • Steps S201 to S204 Client terminal 20 side
  • the CPU 21 waits for an incident statistical information display start operation in step S201 (No in S201). If the CPU 21 determines that the incident statistical information display operation has been performed (Yes in S201), the CPU 21 shifts the processing to step S202.
  • the CPU 21 executes the dispensing information management program to display the initial screen on the display device 27, and then selects an operation key for requesting display of incident statistical information (in S201). Yes side), the process proceeds to step S202.
  • step S202 the CPU 21 executes a process for setting a statistical display condition when displaying the statistical information of the incident. Specifically, the CPU 21 sets the statistical display condition according to the operation of the operation input device 26.
  • the statistical display condition defines items such as a store, a group, a group division, a dispensing device, a pharmacist, and the like, for example, which are targets for calculation of incident statistical information.
  • the CPU 21 transmits a display request for incident statistical information to the server device 10 together with the statistical display condition set in step S202.
  • the CPU 21 when inputting the statistical display condition to the server device 10 by executing the processing of the steps S202 to S203 corresponds to the statistical display condition input means. Then, the CPU 21 waits for reception of the statistical information of the incident (No side of S204).
  • Steps S301 to S303 Server device 10 side
  • the CPU 11 waits for a display request for incident statistical information in step S301 (No in S301). If it is determined that the incident statistical information display request has been received (Yes in S301), the CPU 11 shifts the processing to step S302.
  • step S301 it is conceivable that the CPU 11 executes a user login process by the client terminal 20.
  • the CPU 11 when performing user authentication by the login process corresponds to the user authentication means.
  • step S302 the CPU 11 calculates the statistical information of the incident stored in the data storage unit 14 according to the statistical display condition corresponding to the display request received in step S301.
  • the CPU 11 receives the incident information from each of the client terminals 20 instead of the step S302, the incident information is sequentially reflected in various statistical information stored in the data storage unit 14. By doing so, it is possible to always update the statistical information to the latest statistical information.
  • the CPU 11 may automatically set or change a part of the display condition according to a login user who has requested display of the statistical information of the incident.
  • search area information in which an area and a prefecture corresponding to each person in charge are determined in advance is stored in the data storage unit 14, and the CPU 11 selects an area and a prefecture corresponding to the person who is currently logged in. It is conceivable to extract from the search area information and make the area and prefecture a calculation target of statistical information.
  • the contents of the search area information are set and changed by the CPU 21 of the client terminal 20 according to the operation of the operation input device 26.
  • step S303 the CPU 11 transmits the incident statistical information calculated in step S303 or the incident statistical information calculated and stored in advance in the data storage unit 14 to the client terminal 20.
  • the CPU 11 when transmitting the statistical information of the incident to the client terminal 20 by executing the steps S302 to S303 corresponds to the statistical information output means.
  • the CPU 11 changes the output contents of the statistical information in the steps S302 to S303 according to the user who is authenticated by the login process performed in the step S301. For example, it is conceivable to limit areas that can be referred to as statistical information for each user.
  • a user may be able to refer to the total of each pharmacist incident for each store, but may impose a restriction that the statistics of incidents for each pharmacist cannot be referenced.
  • the CPU 11 changes the output contents of the statistical information based on the user specified by the user authentication executed in step S301 and the like and the authority information. Note that, as a method of restricting these displays, the CPU 11 may not display the items for which display restrictions are imposed when the statistical information of a plurality of items is displayed in a tree.
  • Steps S204 to S205 Server device 10 side
  • the client terminal 20 determines that the CPU 21 has received the incident statistical information (Yes in S204), and performs processing.
  • the process proceeds to step S205.
  • the CPU 21 causes the display device 27 to display the incident statistical information received in step S204.
  • the statistical information of the incident displayed on the display device 27 conforms to the statistical display condition set in step S202.
  • the CPU 21 changes the display condition set in the step S202 according to the operation of the operation input device 26, and transmits the change to the server device 10. By doing so, the display of the display device 27 is updated in accordance with the incident statistical information received thereafter from the server device 10.
  • step S202 an example of setting the statistical display condition (the step S202) and displaying the statistical information of the incident (the step S205) in the incident statistical output process (see FIG. 12).
  • the CPU 21 sets a statistical display condition for determining a calculation target of the statistical information of the incident in the step S202.
  • step S202 an input screen for statistical display conditions is displayed on the display device 27 of the client terminal 20.
  • the CPU 21 receives the information on the statistical display condition input screen from the server device 10 and causes the display device 27 to display the information. In the input screen shown in FIG.
  • various conditions such as “search area”, “store”, “device”, and “display order” can be set as the statistical display conditions, but these are merely examples. , “Date” and “Person in charge” can be set.
  • the CPU 21 transmits the statistical display condition to the server device 10 (S203). Accordingly, 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).
  • 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.
  • the target specified by the statistical display condition is one store
  • the store name “Akashi store” is displayed, and specified by the statistical display condition as shown in FIG.
  • the target is a plurality of stores
  • the store names “Akashi store”, “Kobe store”, and “Sannomiya store” are listed and displayed.
  • FIG. 13C if the target specified by the statistical display condition is one store, the store name “Akashi store” is displayed, and specified by the statistical display condition as shown in FIG.
  • the target is a plurality of stores, the store names “Akashi store”, “Kobe store”, and “Sannomiya store” are listed and displayed.
  • FIG. 13 (E) if the target specified by the statistical display condition is one division, the division “prefecture” and the number of stores included in the division are displayed.
  • FIG. 13 (F) 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.
  • a plurality of divisions, groups, and stores are specified as the statistical display conditions, a plurality of divisions, the number of stores, a group, the number of stores, and stores are respectively searched as shown in FIG. Is displayed.
  • the number of display characters exceeds the predetermined number of characters, as shown in FIG. 13H, the characters after the predetermined number of characters are omitted and the total number of stores is displayed.
  • FIG. 14A shows an example of the pharmacy master
  • FIGS. 14B to 14D show display examples of the statistical information of the incident.
  • each of “A store”, “B store”, “C store”, and “D store” is stored in the data storage unit 14 of the server device 10 as the pharmacy master. It is assumed that the four client terminals 20 installed in are registered.
  • 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 shall be.
  • the pharmacy master it is assumed that “AA group” and “CC group” belong to “AAA classification” and “DD group” belongs to “DDD classification”, respectively.
  • the store, the group, and the division are examples of the classification unit of each of the client terminals.
  • the classification includes area names such as “Kansai” and “Kanto”, and the group includes names of prefectures such as “Osaka” and “Hyogo”.
  • the CPU 21 has a function of arbitrarily setting a classification unit such as a store, a group, and a division to which the client terminal 20 belongs.
  • the setting of the classification unit is executed by the CPU 21 in accordance with an operation input of the operation input device 26 that is displayed according to the initial setting display screen of the dispensing information management program.
  • the CPU 21 for realizing the function corresponds to the classification unit setting means.
  • the said CPU11 calculates the statistical information of the incident for every store.
  • the client terminal 20 As shown in FIG. 14B, the statistical information of the incident is displayed for each store.
  • “number of prescriptions” indicates the number of prescriptions (prescription data).
  • the “level” indicates statistical information for each of the incident levels “S”, “A”, “B”, “C”, and “D”.
  • “NG” indicates the number of incidents of the corresponding level
  • incident content indicates statistical information for each incident content such as “mistake medicine mistake” and “patient error”.
  • “OK” is the number of normal processes counted in the unit where the relevant incident content occurs
  • “NG” is the number of incidents counted in the unit where the relevant incident content occurs
  • the CPU 11 counts the number of “OK” cases and “NG” cases for each medicine when the incident occurs in the medicine unit, such as when the incident content is “mistake of medicine”. To do.
  • the CPU 11 counts the number of “OK” and “NG” for each prescription when the occurrence of the incident occurs for each prescription as in the case where the incident content is “patient error”. Further, the CPU 11 does not count the number of “OK” and “NG” in the case where the incident occurs regardless of the medicine or the prescription as in the case where the incident content is “filling medicine error”. .
  • the incident count method in advance for each incident content, it is possible to obtain effective statistical information obtained by counting the number of incidents in an appropriate unit.
  • the number of incidents is counted for each drug for all incident contents, if an incident occurs in a prescription unit such as ⁇ patient error '', the number of incidents is the same as the number of drugs included in the prescription. Since it is reflected in the statistical information that it has occurred, it deviates from the number of incidents that should be managed, and effective statistical information cannot be obtained.
  • the CPU 11 calculates the statistical information of the incident for each group.
  • incident statistical information is displayed for each group as shown in FIG.
  • FIG. 14D when the check box of the group division is checked, in the server device 10, the CPU 11 calculates the statistical information of the incident for each group division.
  • the client terminal 20 displays incident statistical information for each group category. Therefore, even after displaying the incident statistical information, the user arbitrarily confirms the incident statistical display condition by using the check box, thereby confirming the desired statistical information on the display device 27. be able to. That is, the range that the user does not want can be excluded from the statistical information displayed on the display device 27.
  • the statistical display condition may be the display of incident statistical information for each pharmacist. In this case, in the setting of the incident master (see FIG. 4), only the number of incident categories whose pharmacist incident flag is ON is calculated as statistical information.
  • the statistical display condition may be a display of incident statistical information for each specified year, month, week, day, day of the week, or time.
  • FIG. 15 shows an example of the statistical display. Specifically, FIG. 15A is a display example when a monthly statistical display condition is selected, FIG. 15B is a display example when a weekly statistical display condition is selected, and FIG. C) shows a display example when the daily statistical display condition is selected.
  • FIG. 15E shows a display example when the day-by-day statistical display conditions are selected
  • FIG. 15F shows a display example when the hourly statistical display conditions are selected.
  • the CPU 11 sets only the time selected (checked) by the check box in the state where the time is selected as the statistical display condition as the statistical information calculation target.
  • the statistical display condition may be a display of incident statistical information for each specified incident type. For example, by specifying the type of the dispensing device in which the incident occurs, statistical information can be obtained only for the incident that may occur in the specified type of the dispensing device. It is desirable that one or more of the incident types can be specified at the same time. In addition, displaying only the incidents pointed out by the patient is also considered as an example of the statistical display condition. Thereby, it is possible to grasp information such as errors that are likely not to be found by the pharmacist and the auditor.
  • the CPU 11 acquires information on the dispensing device connected to the client terminal 20 from each of the client terminals 20 in order to manage the dispensing device connected to each of the client terminals 20. And it memorize
  • the device information includes information such as a device name, a dispensing device type, a system version, an IP address, and a MAC address. Note that each dispensing device may automatically transmit the device information to the client terminal 20 at startup.
  • the CPU 21 transmits the device information of each of the dispensing devices to the server device 10 every predetermined time.
  • the CPU 11 acquires the device information of the dispensing device connected to each of the client terminals 20, and creates a device connection table in which the device information and the client terminal 20 are associated with each other.
  • the data is stored as the pharmacy master in the data storage unit 14.
  • 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.
  • an automatic deletion process for deleting the device information from the device connection table is executed. Thereby, the information regarding the dispensing device separated from the client terminal 20 and the dispensing device that has not been used for a long time is deleted from the device connection table as unnecessary information.
  • the CPU 11 uses the information on the start time and end time of use for each dispensing device as connection history information separately from the device connection table stored in the data storage unit 14.
  • the data is stored in the storage unit 14.
  • the connection history information it becomes possible to confirm the use start time and use end time of each of the dispensing devices afterwards. Therefore, for example, in a pharmacy where the dispensing device was installed, it is possible to check the increase or decrease in the number of incidents and the frequency of occurrence between the period when the dispensing device is used and the period when it is not used. Become. Specifically, when the number of incidents decreases after the introduction of the specific dispensing device and the number of incidents increases after the dispensing device is no longer used, the effect of reducing the incident by introducing the dispensing device can be grasped. .
  • the CPU 11 stores, for example, the latest software version of each dispensing device 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 dispensing device. 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. It is possible to do. Thereby, it is possible to prompt the user to update the software version of each of the dispensing devices connected to the client terminal 20.
  • the CPU 11 may transmit a control instruction for updating the software version of the dispensing device to the latest version to the client terminal 20 to which the dispensing device whose software version is not the latest is connected.
  • a control instruction for updating the software version of the dispensing device to the latest version to the client terminal 20 to which the dispensing device whose software version is not the latest is connected.
  • the software of the dispensing device connected to each of the client terminals 20 is automatically updated by the server device 10.
  • the CPU 21 updates the software version of the dispensing device to the latest version according to the control instruction.
  • the CPU 21 downloads the latest version software of the dispensing device from the server device 10 or the like, and transmits the software to the dispensing device, thereby causing the dispensing device to update the software.
  • the CPU 11 dispenses work from each of the client terminals 20 to the pharmacy or the like where the client terminal 20 is installed in order to manage patient waiting time at the pharmacy or the like where the client terminal 20 is installed. Get the time required for each process. Specifically, the patient's waiting time is the time from when a prescription is received at a pharmacy or the like until the medicine is delivered to the patient.
  • FIG. 16 shows an example of the flow of time for dispensing work in a pharmacy or the like where the client terminal 20 is installed.
  • the CPU 21 of the client terminal 20 acquires the following times T11 to T17 and stores them in the data storage unit 24, and transmits the times T11 to T17 to the server device 10.
  • the time T11 is the time from receipt of the reception terminal 51 installed in a pharmacy or the like until reception of the prescription data is completed and input to the client terminal 20.
  • the CPU 21 of the client terminal 20 acquires the reception time at 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 the prescription data is input to the client terminal 20.
  • Time T12 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.
  • a time T13 from when the dispensing data is input from the client terminal 20 to the dispensing device such as the tablet packaging machine 52, the powder packaging machine 53, and the picking auxiliary device 53 until the dispensing is completed is determined in the dispensing device. It is timed and input to the client terminal 20 from the dispensing device. At this time, the CPU 21 calculates the time T13 based on the time at which dispensing data is first input among the dispensing devices and the dispensing completion time at the dispensing device in which dispensing has been completed last among the dispensing devices. To do.
  • time T14 Thereafter, the time T14 from the completion of dispensing in each of the dispensing devices until the final audit for the dispensing is started is the final audit of dispensing from the dispensing completion time in the dispensing device that has completed dispensing at the end of each of the dispensing devices. This is the time until the auditor performs an operation for starting the final audit on an information processing apparatus such as a personal computer for inputting the result.
  • the audit start time when the final audit start operation is performed in the information processing apparatus is input to the client terminal 20 from the information processing apparatus.
  • the said CPU21 is based on the said dispensing start time in the dispensing apparatus with which dispensing was completed last among each said dispensing apparatus, and the said audit start time input from the said information processing apparatus. T14 is calculated.
  • time T15 Next, the time T15 from the start of the final audit to the end of the final audit is from when the inspector performs the final audit start operation to the information processing apparatus until the final audit end operation is performed. Is the time.
  • the time T15 is measured by the information processing apparatus and transmitted from the information processing apparatus to the client terminal 20. Note that the CPU 21 in the client terminal 20 receives the audit start time, the audit end time, and the audit end time when the final audit end operation is performed from the information processing apparatus. It is also conceivable to calculate the time T15 based on the above.
  • the time T16 from the final audit end time to the start of patient compliance instruction is the patient guidance instruction for the information processing device such as a personal computer for inputting the start of patient compliance instruction from the final audit end time. This is the time until the start operation is performed.
  • the medication instruction start time when the medication instruction start operation is performed in the information processing apparatus is input to the client terminal 20 from the information processing apparatus. Thereby, 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.
  • the time T17 from the start time of the medication instruction to the end of the medication instruction is the time from when the medication instructor performs an operation to start the medication instruction to the information processing apparatus until the completion of the medication instruction. It is.
  • the time T17 is measured by the information processing apparatus and transmitted from the information processing apparatus to the client terminal 20.
  • the medication instruction end time at which the medication instruction end operation was performed is transmitted from the information processing apparatus to the client terminal 20, whereby the CPU 21 in the client terminal 20 causes the CPU 21 to take the medication instruction start time and the medication instruction. It is also conceivable to calculate the time T17 based on the end time.
  • the medication end time is not limited to the time when the medication instruction end operation is performed on the information processing apparatus.
  • the CPU 21 sets the photographing time as the medication instruction end time. It is conceivable to calculate the time T17.
  • the operation or image captured 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 the medicine to the patient afterwards with a moving image or an image.
  • the time T11 to the time T17 are the time required for each step of the dispensing operation from when the prescription is received at the reception terminal 51 to when the medicine is delivered to the patient.
  • the CPU 21 stores the time T11 to the time T17 in the data storage unit 24. Thereby, thereafter, the CPU 21 can calculate the time required for the entire process, that is, the patient waiting time T10 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 each step of the dispensing operation, it is possible to calculate the required time of an arbitrary period in the dispensing operation. It is.
  • the required time from the time T11 to the time T12 that is, the required time from reception at the reception terminal 51 to dispensing data to the dispensing device. Accordingly, the user shortens the waiting time of the patient by using the time T10 to the time T17, for example, by newly introducing the dispensing device or taking various measures such as an increase in the number of personnel in a pharmacy or the like. It becomes possible.
  • the CPU 21 executes a calculation process of a required time in an arbitrary period of the dispensing operation, a display process of the required time on the display device 27, and the like according to a user operation on the operation input unit 26.
  • the CPU 21 transmits the time T10 to the time T17 to the server device 10.
  • work can be managed.
  • the server device 10 can compare the time T10 and the required time in each of the client terminals 20. Therefore, by referring to the time T10 and the required time by the server device 10, the administrator of the dispensing information management system 1 gives instructions to optimize the waiting time of the patient in a specific pharmacy or the like. Is possible.
  • the pharmacies and the like where the client terminals 20 are installed are grouped according to the types of the dispensing devices installed in the pharmacies and the like, and the time required for each step in the dispensing operation is determined. It is possible to manage. For example, a pharmacy or the like in which the tablet packaging machine 52 and the powder medicine packaging machine 53 are connected as the dispensing device to the client terminal 20 is set as a first group, and the CPU 11 sets the time T10 in the first group. It is conceivable to calculate an average value. Thereby, the CPU 11 can determine whether or not the waiting time of the patient among the pharmacies belonging to the first group is equal to or greater than the average value of the time T10. For example, when there is a pharmacy or the like that has a time T10 longer than the average value among pharmacies or the like belonging to the first group by the CPU 11, the CPU 11 Thus, it is possible to warn that the patient has a longer waiting time than other pharmacies.
  • the CPU 11 may acquire information on the number and ratio of new patients from the client terminal 20 installed in a pharmacy or the like whose time T10 is equal to or greater than the average value, and display the information on the display device 16. It is done. Thereby, the administrator who uses the server device 10 has the time T10 that is greater than or equal to the average value because the time required for taking a new patient is relatively long. Can understand that there is no problem. Further, it is conceivable that the CPU 11 acquires the operating status of each of the dispensing devices from the client terminal 20 installed in a pharmacy or the like where the time T10 is equal to or greater than the average value, and displays it on the display device 16.
  • the administrator who uses the server device 10 has the time T10 equal to or higher than the average value due to a high operating rate of the dispensing device, and newly installs the dispensing device in the pharmacy or the like. It is possible to grasp what is desirable to do.
  • the server device 10 manages information on measures that have confirmed the effect of reducing the same incident among measures taken for each piece of incident information, and the client terminal installed in a pharmacy or the like in which the same incident has occurred 20 has a function of notifying. Specifically, when information is input to the solution column as the incident information in each of the client terminals 20, the CPU 11 decreases the number of incident information input from the client terminal 20 thereafter. Determine whether or not. Here, when the number of information on the incident is reduced, it can be determined that the information input in the solution column is effective in reducing the incident. Further, for example, when displaying information on past incidents on the client terminal 20, it may be possible to input the presence or absence of the effect of the solution using a check box or the like. Thereby, in the server device 10, the CPU 11 can determine whether the solution is effective based on whether the check box is checked.
  • the CPU 11 determines that the solution input as incident information is effective, the solution is applied to the client terminal 20 installed only in another store where all the incidents occur or in all stores. To be notified.
  • the CPU 11 determines the solution having the highest effect (incident reduction is large) as the server device. 10 to notify the client terminal 20.
  • the CPU 11 may determine the validity of the information input in the solution column according to the operation input of the administrator to 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 and notifies each of the client terminals 20 only when the administrator has given permission for the operation input device 16. Can be considered.
  • the solution is read out by the CPU 21 when the incident information is input at the client terminal 20. It may be displayed on the display device 27.
  • the CPU 21 prioritizes the solutions in the order of higher effect (increased incident reduction). Can be displayed.
  • 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 packaging machine 53: Powder packaging machine 54: Picking auxiliary devices S1, S2, ...: Processing procedure (step) numbers S101, S102, ...: Processing procedure (step) numbers S201, S202, ...: Processing procedure (step) numbers S301, S302, ...: Processing procedure ( Step) Number

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Chemical & Material Sciences (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Medicinal Chemistry (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

La présente invention a pour objet la fourniture d'un système de gestion d'informations sur un composé, d'un procédé de gestion d'informations sur un composé, d'un programme de gestion d'informations sur un composé, et d'un support d'enregistrement lisible par ordinateur sur lequel est enregistré le programme de gestion d'informations sur un composé, permettant d'améliorer la facilité d'utilisation lors de l'entrée d'un accident de personne par un utilisateur. Pour réaliser ledit objet, une unité d'affichage d'informations d'ordonnance (D33) qui affiche des informations d'ordonnance relatives à l'ordonnance d'un médicament qui sont rassemblées et stockées dans des moyens de stockage d'informations d'ordonnance, et une unité d'entrée d'accident (D34) permettant l'entrée arbitraire d'informations sur un accident lié à un composé du médicament, sont affichées sur un même écran de moyens d'affichage, et les informations sur l'accident qui sont entrées dans l'unité d'entrée d'accident (D34) sont transmises à un dispositif serveur.
PCT/JP2013/068291 2012-07-06 2013-07-03 Système de gestion d'informations sur un composé, procédé de gestion d'informations sur un composé, programme de gestion d'informations sur un composé, et support d'enregistrement WO2014007302A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2014523773A JP5725261B2 (ja) 2012-07-06 2013-07-03 調剤情報管理システム、調剤情報管理方法、調剤情報管理プログラム、記録媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012-152397 2012-07-06
JP2012152397 2012-07-06

Publications (1)

Publication Number Publication Date
WO2014007302A1 true WO2014007302A1 (fr) 2014-01-09

Family

ID=49882054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/068291 WO2014007302A1 (fr) 2012-07-06 2013-07-03 Système de gestion d'informations sur un composé, procédé de gestion d'informations sur un composé, programme de gestion d'informations sur un composé, et support d'enregistrement

Country Status (2)

Country Link
JP (4) JP5725261B2 (fr)
WO (1) WO2014007302A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016045533A (ja) * 2014-08-19 2016-04-04 株式会社湯山製作所 プレボイド報告支援システム
JP2017006238A (ja) * 2015-06-18 2017-01-12 メディケア株式会社 調剤薬局業務処理システム
JP2017139025A (ja) * 2017-05-08 2017-08-10 株式会社トーショー 調剤監督業務支援システム
CN110767284A (zh) * 2019-10-21 2020-02-07 佛山市云壹健康科技服务有限公司 药品分级判断销售方法及应用其的药品销售系统
CN111863179A (zh) * 2019-04-24 2020-10-30 佳能医疗系统株式会社 医用信息处理装置、医用信息处理方法及程序

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6993821B2 (ja) * 2016-11-18 2022-01-14 株式会社ベネッセスタイルケア サービス支援装置、サービス支援方法及びプログラム
WO2019069680A1 (fr) * 2017-10-05 2019-04-11 富士フイルム株式会社 Système de gestion de pharmacie, procédé de gestion de pharmacie et programme de gestion de pharmacie
WO2020230809A1 (fr) 2019-05-14 2020-11-19 東洋紡株式会社 Fibre de polyéthylène
JP7398631B2 (ja) * 2021-02-09 2023-12-15 株式会社湯山製作所 薬剤分包システム

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006302197A (ja) * 2005-04-25 2006-11-02 Hitachi Medical Corp 医療過誤防止システム
JP2006323620A (ja) * 2005-05-19 2006-11-30 Hitachi Ltd 医療事故防止支援システム
WO2009054215A1 (fr) * 2007-10-23 2009-04-30 Konica Minolta Medical & Graphic, Inc. Système et programme de traitement d'informations

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2972094B2 (ja) * 1994-11-07 1999-11-08 株式会社湯山製作所 調剤用トレイ
JP2914650B2 (ja) * 1995-09-29 1999-07-05 株式会社望星薬局 調剤支援システム及び医薬品等販売システム
JPH10198736A (ja) * 1997-01-13 1998-07-31 Yuyama Seisakusho:Kk 医薬品処理システム
JP2002297900A (ja) * 2001-03-30 2002-10-11 Ibm Japan Ltd 業務別応対管理システム、顧客側端末装置、応対側端末装置、管理サーバ、待ち行列監視装置、応対側端末の割り当て方法、および記憶媒体
JP2003009160A (ja) * 2001-06-27 2003-01-10 Pioneer Electronic Corp カラー方式判別装置およびカラー方式判別方法
JP2003104510A (ja) * 2001-09-28 2003-04-09 Sanyo Electric Co Ltd メンテナンス装置、メンテナンス方法及びシステム
JP2004030554A (ja) * 2002-05-08 2004-01-29 Nec Soft Ltd 医療事故防止情報収集システムおよび医療事故防止システム
JP2004171537A (ja) * 2002-10-28 2004-06-17 Fujitsu Ltd 評価基準配信プログラム，評価基準配信方法，評価基準配信装置および記録媒体
JP2004157579A (ja) * 2002-11-01 2004-06-03 Tadanori Munemoto 調剤薬局の業務管理システム
JP2005040214A (ja) * 2003-07-24 2005-02-17 Takazono Sangyo Co Ltd 調剤装置及びそれを備えた調剤情報取得システム
JP2005141370A (ja) * 2003-11-05 2005-06-02 Casio Comput Co Ltd 調剤工程案内システム及び調剤工程案内プログラム
JP4432608B2 (ja) * 2004-05-14 2010-03-17 株式会社日立製作所 医療事故防止情報提示システム
JP3774223B2 (ja) * 2004-08-23 2006-05-10 株式会社湯山製作所 芯管及び長尺材処理装置
JP2007233578A (ja) * 2006-02-28 2007-09-13 Sky Kk 調剤薬局情報提供システム
JP5075465B2 (ja) * 2007-04-20 2012-11-21 株式会社東芝 インシデント・アクシデントレポート分析装置、方法、およびプログラム
JP5248217B2 (ja) * 2007-07-23 2013-07-31 株式会社東芝 医療安全システム
JP2009187414A (ja) * 2008-02-08 2009-08-20 Fujitsu Ltd 分析用属性項目抽出プログラム、分析用属性項目抽出方法、及び情報分析装置
JP2012079189A (ja) * 2010-10-05 2012-04-19 Panasonic Corp 業務改善活動支援方法および業務改善活動支援装置
JP2017201086A (ja) * 2016-05-02 2017-11-09 大成建設株式会社 切羽崩落用防護装置および切羽崩落に対する防護方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006302197A (ja) * 2005-04-25 2006-11-02 Hitachi Medical Corp 医療過誤防止システム
JP2006323620A (ja) * 2005-05-19 2006-11-30 Hitachi Ltd 医療事故防止支援システム
WO2009054215A1 (fr) * 2007-10-23 2009-04-30 Konica Minolta Medical & Graphic, Inc. Système et programme de traitement d'informations

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016045533A (ja) * 2014-08-19 2016-04-04 株式会社湯山製作所 プレボイド報告支援システム
JP2017006238A (ja) * 2015-06-18 2017-01-12 メディケア株式会社 調剤薬局業務処理システム
JP2017139025A (ja) * 2017-05-08 2017-08-10 株式会社トーショー 調剤監督業務支援システム
CN111863179A (zh) * 2019-04-24 2020-10-30 佳能医疗系统株式会社 医用信息处理装置、医用信息处理方法及程序
CN111863179B (zh) * 2019-04-24 2024-01-16 佳能医疗系统株式会社 医用信息处理装置、医用信息处理方法及程序
CN110767284A (zh) * 2019-10-21 2020-02-07 佛山市云壹健康科技服务有限公司 药品分级判断销售方法及应用其的药品销售系统

Also Published As

Publication number Publication date
JP2015144016A (ja) 2015-08-06
JP2019091509A (ja) 2019-06-13
JPWO2014007302A1 (ja) 2016-06-02
JP2018005957A (ja) 2018-01-11
JP6229691B2 (ja) 2017-11-15
JP6969582B2 (ja) 2021-11-24
JP6500962B2 (ja) 2019-04-17
JP5725261B2 (ja) 2015-05-27

Similar Documents

Publication Publication Date Title
JP6229691B2 (ja) 調剤情報管理システム
JP4073976B2 (ja) 薬発注システム
US8407068B2 (en) Medicine management apparatus and medicine management system
JP2019071135A (ja) 配薬支援システム
JP2019093236A (ja) 配薬支援システム
JP4546605B2 (ja) 薬品在庫管理システム
JP2013125377A (ja) 処方データベース、処方データベースを用いた処方監査システム、及び、処方監査システムに用いられる処方データベースの更新方法
JP4398210B2 (ja) 薬品管理装置および薬品管理システム
JPH11282934A (ja) 調剤及び医療診断支援装置
Hincapie et al. A quantitative and qualitative analysis of electronic prescribing incidents reported by community pharmacists
JP6131663B2 (ja) 業務管理装置、業務管理システム、業務管理プログラム
JP4903841B2 (ja) 薬品管理装置
JP2010044783A (ja) Ｉｃｄコード付与装置
JP2016057975A (ja) 医療用事務処理システム
JPWO2017135341A1 (ja) 電子カルテシステム
JP6554813B2 (ja) 検査支援システム、検査支援プログラム
JP6994196B2 (ja) 薬剤のトレーサビリティシステム
JP2009178571A (ja) 薬品管理装置および薬品管理システム
JP7436780B2 (ja) 分包データ生成装置、分包システム、包数決定装置、制限日決定装置、及び分包データ生成プログラム
JP2020187433A (ja) 情報管理システム、情報管理プログラム
JP7348557B2 (ja) 薬剤業務支援システム、薬剤業務支援プログラム及び薬剤業務支援方法
WO2022168172A1 (fr) Dispositif de commercialisation, système de commercialisation, procédé de commercialisation et programme
JP7120640B2 (ja) 服薬指導支援システム、方法、及びコンピュータプログラム
JP2024055808A (ja) 投薬管理システム、管理サーバー、および管理サーバーの制御プログラム
James et al. Patient's Own Drugs and One‐Stop Dispensing: Improving Continuity of Care and Reducing Drug Expenditure

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13813096

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2014523773

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13813096

Country of ref document: EP

Kind code of ref document: A1